about summary refs log tree commit diff
path: root/test/python/test_group_datasets.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-10-12 06:38:08 +0000
committerPjotr <wrk@bosa.lan>2026-10-12 06:38:08 +0000
commita60d3a1bc21e355b5342747be0ede3654d2cce41 (patch)
treec3e6ce6195b451dda76d0ff83854313743c8c9c8 /test/python/test_group_datasets.py
parent53ae1b4cbf8bd68278e7a59cd41a4c145f8362ab (diff)
downloadgenenetwork4-a60d3a1bc21e355b5342747be0ede3654d2cce41.tar.gz
gemma: document the endpoint in README; put the actual gemma-wrapper
commands in the response notes

README: added /compute/gemma to the endpoint table and a dedicated
section with a real example response, and the explicit caveat the
user asked for -- not feasible past roughly 100,000 markers at this
point (synchronous, sequential, no parallel LOCO jobs; the BXD
fixtures, 7,320 markers, already take ~19s, and real datasets go up to
~1M markers).

notes: the response now carries the exact gemma-wrapper invocations
used for the kinship and GWA steps ("Kinship: gemma-wrapper ... -gk",
"GWA: gemma-wrapper ... -lmm 9"), not just a generic description.
kinship_args/gwa_args build the argument list once and feed both the
actual subprocess call and the note text, so the two can't drift
apart. Added unit tests asserting -gk and -lmm never appear together,
and extended the real end-to-end test to check both notes' shape.

Verified: cargo test passes in full, including the real gemma-wrapper/
GEMMA run, with the notes field inspected directly against the actual
command lines used.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Diffstat (limited to 'test/python/test_group_datasets.py')
0 files changed, 0 insertions, 0 deletions