-
Notifications
You must be signed in to change notification settings - Fork 61
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
fix: zero length branches can still have aa mutations even without nu… #1249
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
regarding your concern on the order of union and difference. I don't think this is an issue because in |
by checking first whether the candidate_node equals the current best node, the set of conditionals gets simplified and multiple previous conditions are combined into one. There are now three possible results: - move to the parent node. Happens whenever best_node==candidate_node and all mutations that lead to the candidate_node are also found in the private mutations of best_node - move to a child (candidate_node!=best_node). This only happens when there is at least one mutation shared. - stay: in this case, the final placing is either a direct child of candidate_node, or splits the branch leading to it.
- replace `.left.nuc_muts.is_empty()` with a check for `n_left_muts==0` which is calculated using the same function as `n_shared_muts`. - fix left/right error is split result when attaching to the root
…c muts
This problem arose when we are moving the attachment point across a branch of a node that had aa mutations that didn't correspond to any nucleotide mutations. The problem arose only in the specific case when the branch length of a terminal node is zero.