about summary refs log tree commit diff
path: root/test/python/test_mapping_methods.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-08 15:49:17 +0000
committerPjotr <wrk@bosa.lan>2026-11-08 15:49:17 +0000
commitb5b425a850b2f892ae931f6298c336b1d5ce9e0c (patch)
treef89b12daed5cfd96ab26c5994c86dad8e763cf66 /test/python/test_mapping_methods.py
parentfc0e8fff3c1bed8d40e982a0a5e808180e772590 (diff)
downloadgenenetwork4-b5b425a850b2f892ae931f6298c336b1d5ce9e0c.tar.gz
compute: say what each covariate note is actually about
The shared covariate note promised "5 dummy column(s) named Status.<level>"
on both compute endpoints, but only one of them gets dummies: GEMMA is
handed k-1 columns and R/qtl's wrapper is handed the single level column
and expands it itself. On `/compute/rqtl` the sentence described something
that never appears -- caught by reading a live response on production,
where the note said "5 dummy column(s) named Status." one line above the
Rscript command line that passes no such thing.

The note is now engine-neutral -- `... 90 of 93 samples have a value, 34
with both the trait and the covariate; 6 levels` -- and GEMMA says what it
was handed in its own note, which is the part a reader comparing two runs
wants: `GEMMA fits 4 covariate column(s): Status.Live, Status.UTHSC,
Status.UTHSC2, ...`. The unit test asserts the level count, and the
end-to-end test asserts the columns note names `Status.` columns twice or
more, so a covariate silently fitted as one ordinal number fails it.

* src/covariates.rs (resolve), src/gemma.rs (compute), tests/gemma.rs,
  docs/www/ai-instruction.md (the example note).
Diffstat (limited to 'test/python/test_mapping_methods.py')
0 files changed, 0 insertions, 0 deletions