about summary refs log tree commit diff
path: root/test/python
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-14 03:45:38 +0000
committerPjotr <wrk@bosa.lan>2026-11-14 03:45:38 +0000
commitf8b34ca82b40f9eda65fa3abab580a0ca8e66f49 (patch)
tree3c4acb2d5cf4d8694c0851441a0ba51f6707b180 /test/python
parent5c6f36f6d0155d73e3fb8d24aee1a6827a77ae97 (diff)
downloadgenenetwork4-f8b34ca82b40f9eda65fa3abab580a0ca8e66f49.tar.gz
groups: the design in /groups/{group}, and a drift check against GN2's ParInfo
Two follow-ups to the parental-design endpoint.

/groups/{group} now carries the headline in its notes -- "Parental design:
C57BL/6J (maternal) x DBA/2J (paternal), F1s B6D2F1 / D2B6F1; a mapping excludes
the parents and F1s by default" -- plus a next link to the full design. "Which
cross is this?" is two strain names, and needing a second request to see them
was the only reason the endpoint had to be called first. A group with no
metadata says so in the same note, pointing at parents_and_f1s.json and at
`individuals.exclude`, rather than leaving the reader to wonder why nothing was
dropped.

The metadata is the same fact in two places (GN2's ParInfo, our JSON) and it
drifted once already, silently: the paternal/maternal labels were swapped
against GN2's unpacking, and nothing noticed because the exclusion rule takes
both strains regardless of role. scripts/check-parental-metadata.py parses
ParInfo with ast (no gn2 import) and compares it group by group, reporting
disagreements per role and treating groups the JSON knows but GN2 does not as
informational. tests/parental_metadata.rs runs it while a GN2 checkout is
present (GN2_CHECKOUT, or a sibling path) and skips once GN2 is retired -- at
which point the JSON is the only copy and there is nothing to drift from. It
reports 23 groups reproduced, 1 extra (BXD-Longevity).
Diffstat (limited to 'test/python')
0 files changed, 0 insertions, 0 deletions