diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-11 15:42:40 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-11 15:42:40 +0000 |
| commit | 54d704ab7a6ec6e39ccb66e08c2334652a437cfa (patch) | |
| tree | 12fdfd2b3e56d5a6cdfdf9d65739b55c26b97cb9 /test/python/test_dev_token.py | |
| parent | 48e33540c4a00f0077963c3410628a6258448558 (diff) | |
| download | genenetwork4-54d704ab7a6ec6e39ccb66e08c2334652a437cfa.tar.gz | |
docs: GEMMA's pve is one flag away, not a dead end
Tested -lmm 9 with -pve on a synthetic BIMBAM trio (40 individuals, 60 markers, GEMMA 0.98.6): the flag is accepted and the log carries ## pve estimate in the null model = ... ## se(pve) in the null model = -nan ## vg estimate in the null model = 0 ## ve estimate in the null model = 0 So what was missing is plumbing, not support. Two gemma-wrapper changes are in its working tree (5eb53fa): the per-run logs are copied beside the archive -- they were only inside the .tar.xz -- and a failing child's own ERROR lines are printed before the Ruby backtrace. Once pushed and pinned, /compute/gemma can pass -pve and report pve/vg/ve per chromosome beside l_mle, which is what the 16627 and 16769 comparison needs. Also recorded: on random data GEMMA returns se(pve) = -nan with vg = ve = 0, so a boundary pve is a direction rather than a proportion -- the same caveat as BulkLMM's h2, from the other engine.
Diffstat (limited to 'test/python/test_dev_token.py')
0 files changed, 0 insertions, 0 deletions
