-
Notifications
You must be signed in to change notification settings - Fork 3
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
suggestions with big data #16
Comments
also i noticed in your pipeline, you set inonclust |
Hi thank you very much again for reporting your findings.
I have fixed this in commit 2f40387 and also changed the name of the run_mode to ont instead of analysis to make clearer what the mode is used for. The parameters k and w were used in our analyses to alleviate any possible impacts of isONclust on the final results but are not recommended to be run with with ONT data sets.
If you refer to the number of clusters (isONclust and isONcorrect), one thing you could try is to set a higher value for iso_abundance when running the pipeline. This would require more reads per cluster to be formed (for isONclust and isONcorrect) as well as a higher number of reads supporting an isoform to be called and should reduce the number of clusters. This, however, might mean that some isoforms with very low read support might not be called. If this is not what you meant could you explain a bit more? |
Hi, sorry for the late reply. Thanks for your suggestions. Cheers, |
Hi Alex,
I found your tool generating a lot of intermedia files (also from isonclust and isoncorrect). It consumes my inodes quickly.
Any suggestions how to alleviate this for big dataset?
Would increase (or decrease)
--max_seqs
or--max_seqs_to_spoa
help?Thank you so much.
Cheers,
The text was updated successfully, but these errors were encountered: