about summary refs log tree commit diff
path: root/test/python/server_test_case.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-11 13:07:03 +0000
committerPjotr <wrk@bosa.lan>2026-11-11 13:07:03 +0000
commitf4d2d719f90774e85bc47eca041bc469f0f0951d (patch)
treeb31f206be9e954cc11de6db5523438e9521e1164 /test/python/server_test_case.py
parentc9db07f6d372b0b8812e5f6698257a9df94dc1ef (diff)
downloadgenenetwork4-f4d2d719f90774e85bc47eca041bc469f0f0951d.tar.gz
gemma: the permutation refusal names both routes, including running GEMMA itself
We do not run GEMMA permutations -- each repeats the whole LOCO scan and the
gate gives GEMMA one slot -- but "not supported here" is not the same as
"not available". The refusal now says both:

  1. POST /compute/bulklmm with nperm: 1000 -- an LMM whose thresholds come
     from rotations that keep the kinship (R/qtl's nperm does not, and is
     anti-conservative on a structured panel);
  2. run GEMMA's own permutation locally. The reply's notes already name the
     bimbam pair and the phenotype file, so `gemma-wrapper --permutate` or
     `gemma -lmm 9 --permutate` on those inputs reproduces exactly the null
     GEMMA would have used -- hours instead of seconds, which is the honest
     price of that particular null.

docs/bulklmm.md gains the table this belongs in: three ways to get a
threshold, ordered by how honest the null is for a structured panel
(rotation with kinship; GEMMA's own LOCO permutation run locally; R/qtl's
nperm as a sanity check only). SKILL.md says the same in two lines.

tests/gemma.rs now asserts both halves of the refusal, and the earlier
assertion on /compute/rqtl -- which stopped being true when the refusal was
rewritten -- is replaced rather than left passing by accident.
Diffstat (limited to 'test/python/server_test_case.py')
0 files changed, 0 insertions, 0 deletions