about summary refs log tree commit diff
path: root/test/python/test_groups.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-10 18:43:24 +0000
committerPjotr <wrk@bosa.lan>2026-11-10 18:43:24 +0000
commitd614b073351773fa5b698a3c8a4374191e9341b9 (patch)
treef4cb313af8a81531a26699f30fa79e281d125b9e /test/python/test_groups.py
parent9ea2fa0f0d5336814a0c62020b20f55f4394874f (diff)
downloadgenenetwork4-d614b073351773fa5b698a3c8a4374191e9341b9.tar.gz
docs: four analysis gotchas, with DOL trait 10003 as the worked example
SKILL.md told an agent how to call the endpoints, not how to read them
when two engines disagree -- which is the question the last round of
analysis actually asked. A note in "Gotchas that cost time":

  * Count the animals in the peak's genotype class before believing it
    (.../markers/{marker}/classes?trait=<id>). DOL 10003's GEMMA peak is
    A n=2 mean 1.8 against B n=171 mean 3.95, with its next two hits the
    same pattern mirrored: a haplotype carried by a handful of extreme
    animals, not a population effect.
  * H is dropped for R/qtl2 on a riself panel (kept by GEMMA as dosage
    0.5); its HMM re-imputes, so the observation is lost, not the animal.
    A mostly-H marker becomes nearly monomorphic for R/qtl2 -- 2 A vs 171
    B -- which is why the two engines can name different markers of one
    region. Neither is wrong.
  * GEMMA's af is mean(dosage)/2 under B=1, H=0.5, A=0, not an allele
    frequency (0.469 is half of 0.935); allele frequencies come from
    .../markers/{marker}/frequencies, and allele1/allele0 are the BIMBAM
    X, Y placeholders, so the sign of beta is not a strain.
  * Do not compare scores across engines as one scale: GEMMA -log10 p,
    R/qtl/rqtl2 LOD, qtlreaper LRS (lod = lrs / 4.604).
Diffstat (limited to 'test/python/test_groups.py')
0 files changed, 0 insertions, 0 deletions