diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-11 15:24:10 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-11 15:24:10 +0000 |
| commit | e1b4f1aeda64b355f68124b196eb8547ca0e26ab (patch) | |
| tree | 2af7168d2bc084b5e26c9b778902acd4cd397241 /test/python/test_mapping_methods.py | |
| parent | 8a0b4059114d2628fe3362c816efcfc4262fc897 (diff) | |
| download | genenetwork4-e1b4f1aeda64b355f68124b196eb8547ca0e26ab.tar.gz | |
docs: how far the GEMMA pve route got
Tried it: passing -pve through gemma-wrapper after -- crashes the wrapper (Ruby backtrace, no output), and the logs the wrapper keeps are the kinship step's -- 223 .log.txt in the cache dir, none containing a pve block, because the per-chromosome LMM logs live in the wrapper's temp dirs and are not retained. Two routes remain, both written down: run GEMMA ourselves (-gk for a text K matrix, then -lmm 1 -pve on one marker, seconds each) and parse 'pve estimate in the null model'; or get -pve into the wrapper's allowlist upstream. The first needs the kinship as plain text, which the wrapper only caches as JSON.
Diffstat (limited to 'test/python/test_mapping_methods.py')
0 files changed, 0 insertions, 0 deletions
