diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-07 16:33:13 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-07 16:33:26 +0000 |
| commit | 3babef5d4596d94f3d6d200e4b7bd9815d288b9f (patch) | |
| tree | 46b955e06966189556dea577846a62e39c689375 /test/python/test_hello_world.py | |
| parent | 14dc58f070c2950c13ae822c4a371cf3d303b16a (diff) | |
| download | genenetwork4-3babef5d4596d94f3d6d200e4b7bd9815d288b9f.tar.gz | |
docs: parents and F1s are excluded by default, measured both ways
Asked whether the BXD mappings ran GN2/GN3's default (no parents, no F1s): they did not. BXD.8's panel is 198 RI strains + 37 F1s and no parent columns at all, and the runs passed all 235 with `null` for the F1s -- phenotypes right, but GEMMA's kinship and R/qtl's cross spanning 235 individuals instead of 198. Measured on trait 10001, both engines, both panels: identical answers (GEMMA p 5.9e-07 at rsm10000005700 chr 8, R/qtl LOD 2.9320 at rs48756159 chr 8), so nothing published from those runs is wrong. The lesson is that null-filling excludes an individual from the fit but not from the model; excluding it means subsetting the genotype file. * docs/genotypes.md: "Parents and F1s are excluded by default" -- the GN2 (`incparentsf1`) and GN3 (`get_sample_list(inc_par=False, inc_f1=False)`) mechanisms, what each panel actually holds, the both-ways measurement, and the rule for the alignment work. * docs/www/ai-instruction.md (4a), docs/www/operator-checklist.md: the same, in a sentence and a paragraph respectively.
Diffstat (limited to 'test/python/test_hello_world.py')
0 files changed, 0 insertions, 0 deletions
