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

Transcript sources and isoforms #459

Open
14zac2 opened this issue Oct 31, 2024 · 0 comments
Open

Transcript sources and isoforms #459

14zac2 opened this issue Oct 31, 2024 · 0 comments

Comments

@14zac2
Copy link

14zac2 commented Oct 31, 2024

Hello!

I have noticed that when running Mikado, it tends to prefer transcripts from various sources (found by grepping the different alias transcripts in the final GFF). For example, Mikado generally prefers transcripts from StringTie, followed by LiftOff, then BRAKER3, then TOGA. StringTie and LiftOff often have close to 10,000 transcripts from each source, whereas BRAKER3 and TOGA are often around or below 1000. I was thinking this may be related to StringTie and LiftOff having more unique transcripts as input compared to the other sources, but the number of unique transcripts is not high enough to explain this difference. Do you have any idea as to why Mikado might be preferring these two transcript sources over the others?

Also, I was comparing the effects of BLAST and Diamond, and found that no matter the database used, BLAST ends up contributing to a GFF file that has way more isoform possibilities than when Diamond is used for the search. I tried Diamond in "ultra sensitive" mode but found the same result. I notice that BLAST always finds more hits for more of the candidate transcripts and that using the parameter "-max_target_seqs 5" restricts the number of hits-per-transcript-ID to five in Diamond, but not in BLAST (sometimes a single transcript ID has up to 20 hits). Not sure how much this matters.

I'd love your thoughts on both of these observations!

Many thanks,
Zoe

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

1 participant