diff options
| author | Pjotr Prins <pjotr.public01@thebird.nl> | 2026-11-14 13:57:41 +0000 |
|---|---|---|
| committer | Pjotr Prins <pjotr.public01@thebird.nl> | 2026-11-14 13:57:41 +0000 |
| commit | dc40e89ce72b3213d227a1ee90df701aa17a1c7f (patch) | |
| tree | 0665da1af8fdd3823f33c739c9572e9c8837e3f5 /test/python/test_group_datasets.py | |
| parent | f64a7084694fc28fc2069e39778a83716c1b858e (diff) | |
| download | genenetwork4-dc40e89ce72b3213d227a1ee90df701aa17a1c7f.tar.gz | |
ravanan: key the kinship step on the animal set, so K is shared across traits
gemma -gk reads the phenotype file only to learn which individuals are analysed -- the matrix comes from the genotypes -- so the workflow now gives the kinship step a constant-valued pheno file carrying just the trait's missing-data pattern, and gives gwa the real values. Verified byte-for-byte: -gk on a real trait and on its constant-valued twin produce identical .cXX.txt files, and trait 2's assoc checksums are identical whether K came from the constant pheno or the real one. Consequence, measured on the BXD fixture: a second trait over the same animals costs +1.0 MB of store and 7.5 s (20 GWA jobs) instead of +13 MB and 14.6 s (a second kinship scatter), because the 20 K matrices are identical inputs for both traits. Three keys now: workflow (the ccwl source), kinship (genotype + snps + lmm + the NA pattern) and trait (kinship key + the values), so the compiled CWL and the kinship pheno file are shared and only the trait's pheno file and inputs YAML are per-trait. This is also stricter than gemma-wrapper's own key, which ignores the phenotype entirely and would reuse a K computed for a different set of animals.
Diffstat (limited to 'test/python/test_group_datasets.py')
0 files changed, 0 insertions, 0 deletions
