Skip to content

Individual parents merge #1125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 28, 2021

Conversation

ivan-krukov
Copy link
Member

Description

Adding a ragged parents column to the individuals table.

Fixes #852

This is a clean version of the #866 PR

PR Checklist:

  • Tests that fully cover new/changed functionality.
  • Documentation including tutorial content if appropriate.
  • Changelogs, if there are API changes.

@benjeffery
Copy link
Member

benjeffery commented Jan 22, 2021

Nice one on getting this rebased, hope it wasn't too much trouble! I'll have a detailed look tomorrow.

@ivan-krukov ivan-krukov mentioned this pull request Jan 22, 2021
@codecov
Copy link

codecov bot commented Jan 22, 2021

Codecov Report

Merging #1125 (8ebfd8b) into main (8370ca7) will decrease coverage by 0.06%.
The diff coverage is 86.30%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1125      +/-   ##
==========================================
- Coverage   93.71%   93.65%   -0.07%     
==========================================
  Files          26       26              
  Lines       21082    21236     +154     
  Branches      900      900              
==========================================
+ Hits        19757    19888     +131     
- Misses       1288     1311      +23     
  Partials       37       37              
Flag Coverage Δ
c-tests 92.36% <75.26%> (-0.16%) ⬇️
lwt-tests 92.78% <92.00%> (-0.03%) ⬇️
python-c-tests 94.89% <100.00%> (+0.03%) ⬆️
python-tests 98.64% <100.00%> (+<0.01%) ⬆️

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

Impacted Files Coverage Δ
c/tskit/tables.c 90.50% <75.26%> (-0.27%) ⬇️
python/_tskitmodule.c 91.37% <100.00%> (+0.06%) ⬆️
python/lwt_interface/tskit_lwt_interface.h 95.04% <100.00%> (+0.12%) ⬆️
python/tskit/tables.py 99.60% <100.00%> (+<0.01%) ⬆️
python/tskit/trees.py 97.47% <100.00%> (+<0.01%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8370ca7...8ebfd8b. Read the comment docs.

@ivan-krukov
Copy link
Member Author

The final rebase was pretty simple - the patching process took care of everything.
Thank you for writing the detailed how-to git guides - they are a treasure.

But it looks like the same test coverage check is failing this time.

There is also an outstanding issue of documenting these changes. Does this need to happen before the merge?

Copy link
Member

@jeromekelleher jeromekelleher left a comment

Choose a reason for hiding this comment

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

LGTM @ivan-krukov! I've gone through fairly carefully, and I don't see any show-stoppers.

There's some collatoral damage here from the merge where you've clobbered some recent metadata changes. You'll need to drop these from the diff (@benjeffery, any thoughts on the easiest way to do this?)

One thing we'll need to do as a follow up is to update simplify to keep track of the individual ID references in parents so that the IDs are correct afterwards.

Other than that, I think we just need to go through the standard steps for bumping file format version numbers and so on. These should all be done as follow ups, though, I think it's best to get these basic changes in soon so we don't have to keep rebasing them.

Copy link
Member

@jeromekelleher jeromekelleher left a comment

Choose a reason for hiding this comment

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

LGTM @ivan-krukov! One tiny nit left I think, otherwise good to squash and merge. The squash should go cleanly, now.

@benjeffery, can you open up some issues to track the remaining things that need to be addressed before we release please?

Copy link
Member

@benjeffery benjeffery left a comment

Choose a reason for hiding this comment

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

Great stuff, I've been through closely and logged issues for follow up work.

@benjeffery
Copy link
Member

benjeffery commented Jan 25, 2021

@ivan-krukov As @jeromekelleher said one nit about a comment that isn't consistent, then a squash and we can merge.
I recently added columns to the data model so I know how much work this is. Nice one!

@jeromekelleher
Copy link
Member

@ivan-krukov, can we get this updated please? There's a significant chance of this PR getting out of date again if we don't merge it ASAP!

@benjeffery benjeffery force-pushed the individual_parents_merge branch from 3196c2b to 3d03c8c Compare January 27, 2021 13:50
@benjeffery
Copy link
Member

I've just force-pushed a fix and squash to this PR. Will merge if all green.

@jeromekelleher
Copy link
Member

Segfault on some C tests - are you looking at this @benjeffery, or should @ivan-krukov pick it up?

@benjeffery
Copy link
Member

I'll check it out.

@benjeffery benjeffery force-pushed the individual_parents_merge branch from 3d03c8c to 0538515 Compare January 28, 2021 00:58
@benjeffery
Copy link
Member

The segfault was in the text parsing code for one of the example trees where the individuals string did not have parents (test_simplest_unary_with_individuals). I've fixed by adding -1,-1 parents to that example.

@AdminBot-tskit AdminBot-tskit force-pushed the individual_parents_merge branch from 0538515 to 8ebfd8b Compare January 28, 2021 01:15
@mergify mergify bot merged commit 6c3fdc4 into tskit-dev:main Jan 28, 2021
@ivan-krukov
Copy link
Member Author

I am so sorry that I am late for this. Thank you for resolving.

@jeromekelleher
Copy link
Member

Woohoo, great to see this merged! Thanks for all the hard work @ivan-krukov, adding new columns is always a marathon. (Thanks too @benjeffery!)

@benjeffery
Copy link
Member

I am so sorry that I am late for this. Thank you for resolving.

No worries @ivan-krukov, it was a very small and quick fix. Thanks for the PR!

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.

Add pedigree data to individual table.
3 participants