-
Notifications
You must be signed in to change notification settings - Fork 77
canonical sorting #715
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
canonical sorting #715
Conversation
Looks great @mufernando, this is exatctly the right approach. Ping me when you'd like some feedback. |
Codecov Report
@@ Coverage Diff @@
## master #715 +/- ##
=======================================
Coverage 87.46% 87.46%
=======================================
Files 24 24
Lines 18162 18162
Branches 3609 3609
=======================================
Hits 15886 15886
Misses 1099 1099
Partials 1177 1177
Continue to review full report at Codecov.
|
@mufernando - is this something that we want to get in for the C API release, or will having it done for the next Python release be enough? We'd really like to get the C API shipped soon, and I think just getting the sorting requirement done will be enough for that. Is that OK, or do you want the |
I don't need this in SLiM and probably won't be able to get to this over the next week or two, so we can wait for the next release. |
@mufernando Just pinging as this PR has been inactive for a while - do you plan to pick it up? |
I don't think I'll have the time to work on this for a while. But it seems the work I did with validating the C sort with a Python implementation could be incorporated. Is it bad to leave this hanging here? |
It's no problem to leave it - just useful for planning releases to know which PRs are still active. |
Superseded by #1108 |
Currently, sort does not put a Table Collection in canonical form (given the order of nodes) -- see #705 .
Here I am working on adding mutation time, mutation parent and node to the mutation sorting key.
(still very early, working on a python impl of sort first!)