Skip to content

Conversation

@benjeffery
Copy link
Member

Extracted from #3329

@codecov
Copy link

codecov bot commented Nov 20, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.76%. Comparing base (25a26a7) to head (09541c4).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3330   +/-   ##
=======================================
  Coverage   89.76%   89.76%           
=======================================
  Files          29       29           
  Lines       31292    31292           
  Branches     5738     5738           
=======================================
  Hits        28089    28089           
  Misses       1794     1794           
  Partials     1409     1409           
Flag Coverage Δ
c-tests 86.77% <ø> (ø)
lwt-tests 80.38% <ø> (ø)
python-c-tests 87.12% <ø> (ø)
python-tests 98.85% <ø> (ø)
python-tests-no-jit 33.51% <ø> (ø)
python-tests-numpy1 50.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
python/tskit/tables.py 99.77% <ø> (ø)
python/tskit/trees.py 98.89% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@petrelharp
Copy link
Contributor

I made the changes above and did some more here. I think it could of course be better but is good enough to go unless someone sees typos/errors.

Copy link
Contributor

@petrelharp petrelharp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are all changes I implemented in my commit, but some of these comments have explanation so I'm putting them in still.

docs/ibd.md Outdated
Comment on lines 76 to 80
segments returned are the longest possible ones: for a fixed pair
``(u, v)`` we follow the ancestral paths from ``u`` and ``v`` up the
trees and merge together adjacent genomic intervals whenever both the
MRCA ``a`` and the full ancestral paths from ``u`` and ``v`` to ``a``
are identical.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: double-check this is true. I suspect this might need some nuance at least.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

None of the things I checked that might be "merged" are merged - even if I split an edge, that also splits the IBD segment.

docs/ibd.md Outdated
Comment on lines 86 to 87
by genealogical path) the IBD segments are obtained by merging together
adjacent MRCA intervals that share the same ancestor and paths to that
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
by genealogical path) the IBD segments are obtained by merging together
adjacent MRCA intervals that share the same ancestor and paths to that
by genealogical path) the IBD segments are those
that share the same ancestor and paths to that

docs/ibd.md Outdated
Comment on lines 205 to 206
- Passing an empty list, e.g. ``within=[]``, is allowed and simply
yields a result with zero pairs and zero segments.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unnecessary detail.

Suggested change
- Passing an empty list, e.g. ``within=[]``, is allowed and simply
yields a result with zero pairs and zero segments.

docs/ibd.md Outdated
Comment on lines 242 to 243
no greater than ``max_time`` are returned. The time is measured in
the same units as the node times in the tree sequence (e.g., generations).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What else would it be measured in?

Suggested change
no greater than ``max_time`` are returned. The time is measured in
the same units as the node times in the tree sequence (e.g., generations).
no greater than ``max_time`` are returned.

@petrelharp petrelharp requested a review from hyanwong December 6, 2025 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants