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-11 13:31:44 +0000
committerPjotr <wrk@bosa.lan>2026-11-11 13:31:44 +0000
commit25f376a8d9e7b5511e0799fd3b09898bb682a202 (patch)
treebc411982035d1300f9195c3f20f9f8881694454b /test/python/test_groups.py
parentca7efa231bbd818b5166e38b59e3c81ea30821b3 (diff)
downloadgenenetwork4-25f376a8d9e7b5511e0799fd3b09898bb682a202.tar.gz
bulklmm: report the variance components, and say what a boundary means
"is the kinship term doing anything?" should be answerable from the reply.
The driver now prints h2 and the residual variance under the null model, and
the reply carries both:

  Variance components: h2 = 0.000000, sigma2_e = 0.402171, estimated once
  under the null (intercept) model from y and K, not per marker. With a few
  dozen phenotyped individuals these estimates pile up at the boundaries 0
  and 1 -- the likelihood is flat there -- so read h2 as "kinship matters a
  lot / not at all" rather than as a precise proportion. At a boundary
  (h2 ~ 0 the model is ordinary regression, which is why its LODs can match
  R/qtl's to the digit).

Checked with a strain-ID-driven trait (values = rank of strain), which has
h2 ~ 1 by construction: BulkLMM reports h2 = 1.000000, sigma2_e = 3e-06 and
a peak of LOD 3.1 -- the kinship term absorbs the strain structure -- while
R/qtl, which has no kinship term at all, reports a spurious peak of 5.06 on
the same values. That is the discrimination the h2 column was missing.
Diffstat (limited to 'test/python/test_groups.py')
0 files changed, 0 insertions, 0 deletions