about summary refs log tree commit diff
path: root/test/python/test_get_test_token.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-07 16:28:14 +0000
committerPjotr <wrk@bosa.lan>2026-11-07 16:28:14 +0000
commit14dc58f070c2950c13ae822c4a371cf3d303b16a (patch)
tree60799fc8b97344f496205dd3fea59edff0d307d1 /test/python/test_get_test_token.py
parentb5f5209642f422e87a4d0041471c5654491a8d0c (diff)
downloadgenenetwork4-14dc58f070c2950c13ae822c4a371cf3d303b16a.tar.gz
docs: name the real genotype files, panels and timings everywhere
docs/genotypes.md explained the convention; the endpoint docs still left
a caller guessing which file to pass and how big the panel is. So:

* README.md (/compute/gemma): GEMMA wants the BIMBAM pair
`genotype/bimbam/<file>_geno.txt` + `<file>_snps.txt`, not the `.geno`
file; `trait_values` is one entry per individual in that file's column
order; BXD's current panel stated (235 x 21056), with the 17.1 s
measurement against the 19 s the 7 320-marker fixtures take.
* README.md (/compute/rqtl): the file is `genotype/<file>.geno`
(BXD.8: 235 x 21057; HET3-ITP.12: 6447 x 894), `MappingMethodId`
decides the engine, and the two measured runs with the UM-HET3 peak.
* README.md (/compute/gemma/ravanan): same input convention as gemma.
* docs/genotypes.md: how each measurement was made, step by step, so
they can be repeated; and that step 3 (expanding values onto the panel)
is the API's job in the next iteration.
* docs/www/ai-instruction.md (4a): a table of the BXD files per engine
with panel sizes, the UM-HET3 file, "ask the operator for any other
panel" with where GN2 records which one is current, and the measured
times. Values must be one per individual, in file order -- position, not
name -- and the API does not re-index yet, so a mapping is prepared for
the caller rather than guessed.
* docs/www/operator-checklist.md: MappingMethodId per group, and the
three measurements.
Diffstat (limited to 'test/python/test_get_test_token.py')
0 files changed, 0 insertions, 0 deletions