about summary refs log tree commit diff
path: root/test/python/test_openapi.py
diff options
context:
space:
mode:
authorPjotr Prins <pjotr.public01@thebird.nl>2026-11-16 11:04:35 +0000
committerPjotr Prins <pjotr.public01@thebird.nl>2026-11-16 11:04:35 +0000
commit9ff458ee52079a2385b231f0b7b629170ecfc6a1 (patch)
treea74229aaa15a1bd9ecee63d4c8c374f6c4d1d293 /test/python/test_openapi.py
parent71878e9ff616b8a74ff21eb3a54203069b7a8e23 (diff)
downloadgenenetwork4-9ff458ee52079a2385b231f0b7b629170ecfc6a1.tar.gz
gemma-compare: make the parity gate run, and say what it is measuring
The script could not have caught anything: it posted without an Authorization
header (401 against a token-protected server), asked for a trait's values as
`{"name": n, "values": [<trait name>]}` (422: samples need numbers), read
`columns`/`rows` from the envelope's top level (they are under `meta` and
`data`), and compared relatively -- which calls beta 0.0131 against 0.0157 a
16% disagreement on a marker where both runs agree to three decimals.

Now: `--token`/`$GN4_TOKEN`, trait values fetched from the API, the envelope
shape handled, and an ABSOLUTE `--tolerance` (default 0 = exact). It fetches,
compares and reports through the server as deployed.

Verdict on the current deployment, BXDPublish 10001 over 34 individuals:

  rows: gemma-wrapper 21055, ravanan+gemma 21055, shared 21055
  worst absolute difference: rs230640887 beta -1.015599 vs -1.018739 (0.00314)
  --tolerance 0.005 -> agree; --tolerance 0 -> 63 163 values beyond it

So the row difference this started from is gone: same markers, same count. The
residual is that the two paths run *different GEMMA builds* -- the wrapper's
log names gemma-gn2-0.98.5-8cd4cdb, the ravanan manifest gemma 0.98.6 -- which
moves beta/se/p_lrt in the third decimal while leaving af, n_miss, l_mle and
the marker set identical (and the top hits in the same order).
Diffstat (limited to 'test/python/test_openapi.py')
0 files changed, 0 insertions, 0 deletions