Skip to content
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

Closed
lucventurini opened this issue Oct 4, 2018 · 1 comment
Closed

Prevent loci from being lost due to chaining #131

lucventurini opened this issue Oct 4, 2018 · 1 comment
Assignees
Milestone

Comments

@lucventurini
Copy link
Collaborator

Currently, due to the architecture of Mikado, it can happen that loci get lost in scenarios like the following:

  • Real loci to find: transcript A, transcript B
  • Transcript C spans both loci and shares an intron with A but not with B. C is not a valid alternative splicing event for B.
  • Sublocus stage: C wins over A, B wins as singleton
  • Monosublocus stage: B wins over C
  • Locus stage: We only have B as transcript, as C is discarded.
  • A is lost because no transcript has been retained for that locus.

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.

lucventurini added a commit that referenced this issue Oct 4, 2018
@lucventurini lucventurini added this to the 1.3 milestone Oct 5, 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.
@lucventurini
Copy link
Collaborator Author

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
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants