diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-07 15:33:28 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-07 15:33:28 +0000 |
| commit | 2fcb57a627ed261b6650522b256cc509ebd65ddd (patch) | |
| tree | dc356cc6fa962a3ec89eb393dbd9a0f4b15ca2fd /test/python/test_version.py | |
| parent | e5c333959af6675a0d80934c8cf76275d5571ef8 (diff) | |
| download | genenetwork4-2fcb57a627ed261b6650522b256cc509ebd65ddd.tar.gz | |
rqtl: refuse a phenotype whose sample count is not the cross's
Asked to map a 9-strain trait, the wrapper scanned it against the 6-individual fixture cross and returned six markers with LOD scores and `state: complete` -- a plausible answer belonging to nobody. R recycled and truncated the values silently, and nothing downstream could tell. GeneNetwork3's copy of this script has the same hole. The cross-file format carries no per-sample names, so the count is the only check available; order remains the caller's responsibility (and the reason values and genotype file must come from the same panel). With the check, the same request is a 502 rqtl_failed quoting both counts, and the correctly-shaped request still returns the documented LODs. * scripts/rqtl_wrapper.R: compare the pheno file's rows with nind() of the cross, and stop. * README.md (/compute/rqtl): the second fix relative to gn3, and what stays the caller's job. * docs/www/ai-instruction.md (4a): values and genotypes must describe the same individuals, one for one, in the same order. * docs/www/operator-checklist.md (Compute): what genotype files actually exist on this box (test fixtures, 198 BXD individuals) and why a database trait, with its own strain subset, cannot be mapped against them.
Diffstat (limited to 'test/python/test_version.py')
0 files changed, 0 insertions, 0 deletions
