-
Notifications
You must be signed in to change notification settings - Fork 1
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
How to set --min_candidate_support should be appropriate? #5
Comments
It depends primarily on the characteristics of your data, but also on your goals. In general, the lower the cutoff, the more sensitive the algorithm will be (that is, detect more low expressed sequences but also predict more erroneous sequences).
|
Thank you very much for your quick reply! Should I trim these blast out flnc reads at the same start and end position? |
Trimming the start and ends at the same locations will greatly help IsoCon at finding the variants and work as it was designed for. This is the very much preferred option! Let's see if you get the same variability after this. You can do some post analysis of IsoCon's results by looking at the read support of each final candidate (could be done as sanity check for results both with or without trimming ends). The support can be observed by counting the number of reads that were assigned to each consensus in the |
Hi,when I run IsoCon,I found the results vary greatly with different --min_candidate_support set. So I wonder how to set this parameter is ok?
The text was updated successfully, but these errors were encountered: