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

[URGENT] Use BLAST start/stop data to understand whether two ORFs are a duplication or fragments #15

Closed
lucventurini opened this issue Sep 18, 2015 · 1 comment
Assignees
Milestone

Comments

@lucventurini
Copy link
Collaborator

Currently, the BLAST algorithm is quite stupid ... we only look whether two ORFs share a hit, without considering whether they hit the same region of the target. This means that two duplicated genes, fused by one method, will end up being considered as fragments of the same gene and therefore the ORFs will not get splitted.

This should be easily fixable by considering whether the hits shared by two ORFs are or are not overlapping. Target: "check_split_by_blast" in Transcript.

@lucventurini
Copy link
Collaborator Author

At the moment, this feature can be controlled using the following parameter (float, percentage between 0 and 1) in the "chimera_split" section:

  • "min_overlap_duplication" (default 90%)

This means that if the overlap between HSPs on two different ORFs have an overlap that is greater than 90% of the length of the target, the hit should be considered a tandem duplication and therefore split.

lucventurini pushed a commit that referenced this issue Oct 3, 2015
…ripts (#15), finally implemented BLAST score (#5)!
lucventurini pushed a commit that referenced this issue Oct 6, 2015
lucventurini pushed a commit to lucventurini/mikado that referenced this issue Feb 11, 2021
lucventurini pushed a commit to lucventurini/mikado that referenced this issue Feb 11, 2021
…ding for split transcripts (EI-CoreBioinformatics#15), finally implemented BLAST score (#5)!
lucventurini pushed a commit to lucventurini/mikado that referenced this issue Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant