about summary refs log tree commit diff
path: root/test/python
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-07 17:44:05 +0000
committerPjotr <wrk@bosa.lan>2026-11-07 17:44:05 +0000
commit2e3f0845d789f624f9e974af0595639d96cc1279 (patch)
treea633c819bb15fa3847d1c44ca9819971c8719741 /test/python
parent632cf0c61ee4602ee8423593a8aa8fd8a4373c41 (diff)
downloadgenenetwork4-2e3f0845d789f624f9e974af0595639d96cc1279.tar.gz
compute: suggest a PheWAS at the peak, and the plot that follows
A mapping's job is not finished when the rows come back: the next two
questions are "what else peaks here?" and "show me". So a group-scoped
mapping response now ends with both --

- `next`: `/groups/{group}/phewas?locus=<peak>&window=10000`, the peak
  being the strongest LOD (R/qtl, column 4) or the smallest p_lrt (GEMMA,
  last column). A GET that resolves 200, which is what `next` promises;
  measured: R/qtl's peak rs48756159 -> 3 traits, GEMMA's
  rsm10000005700 -> 12.
- a note saying which two columns to plot: chr against LOD (R/qtl) or
  against -log10 of p_lrt (GEMMA). Rows are positional with meta.columns
  naming them, so plotting needs no reshaping -- the API does not render
  images, and saying exactly what to plot is more useful than pretending
  to.

Path-based requests get neither: without a `group` there is no group to
PheWAS over, and the note alone would be noise.

* src/rqtl.rs, src/gemma.rs (peak_marker): strongest LOD / smallest
  p_lrt, with unit tests for both shapes and the empty cases.
* src/routes/{rqtl,gemma}.rs: the `next` link and the plot note, when the
  request named a group.
* docs/www/ai-instruction.md: 4b rewritten around what a reader does with
  a PheWAS -- where the position comes from (a mapping's `next`, a
  trait's `locus`, or chr+mb), the parameter table, what a hit contains,
  and how to read it (the 460 LRS cap, `traits: []` versus `markers: []`,
  peak-only and published-only limits, several traits on one marker),
  with the chr 9 example; 4a points at the new forward.
Diffstat (limited to 'test/python')
0 files changed, 0 insertions, 0 deletions