-
Notifications
You must be signed in to change notification settings - Fork 18
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
Prevent loci from being lost due to chaining #131
Milestone
Comments
lucventurini
added a commit
that referenced
this issue
Oct 4, 2018
lucventurini
added a commit
that referenced
this issue
Oct 4, 2018
lucventurini
added a commit
that referenced
this issue
Oct 4, 2018
lucventurini
added a commit
that referenced
this issue
Oct 4, 2018
lucventurini
added a commit
that referenced
this issue
Oct 5, 2018
…than a for cycle, to find the missing loci. This also ensures coherence in terms of the overlapping parameters.
Correctly implemented. Closing. |
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
…e relevant tests
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
lucventurini
added a commit
to lucventurini/mikado
that referenced
this issue
Feb 11, 2021
…sed function, rather than a for cycle, to find the missing loci. This also ensures coherence in terms of the overlapping parameters.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, due to the architecture of Mikado, it can happen that loci get lost in scenarios like the following:
This tends not to happen too much due to the specifics of scoring, but it is an issue.
Ideally, Mikado should realise it has lost transcripts, backtrack, and rebuild loci for them.
The text was updated successfully, but these errors were encountered: