-
Notifications
You must be signed in to change notification settings - Fork 59
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
Dorado correct for R9 data #1032
Comments
Hi @asan-emirsaleh, To answer your questions;
To the best of my knowledge we have not tested the experimental r9.4.1 model and have done no verification if it does or does not work. Please feel free to give it a try and let us know what happens, but at this time we don't support the experimental R9.4.1 model in dorado correct.
No, they will not be compatible as the error profiles will be different between the two conditions.
I don't know - I'm not familiar with
We currently don't plan to add support for the R9.4.1 condition / models in Kind regards, |
@asan-emirsaleh, have your questions been answered satisfactorily / is this issue resolved? Kind regards, |
Thank you a lot. My questions were partially resolved. I have two questions in relation Thank you for your attention to this topic on objectively discontinued lineage. |
Hi Asan,
Yes - at this time the models are the exact same.
Yes - Technically it's possible - I can't see anything in the HERRO codebase that suggests that they're different models which is encouraging. Rich |
Hello!
Thank you for you efforts in developing open-source tools for genome data analyses.
I am looking for the best workflow with r9.4.1 data (I have only this kind of data).
Can I use experimental r9.4.1 model from HERRO project for
dorado correct
? Is the r10.4.1 model compatible with r9.4.1 data? And finally, can I use the output ofvechat
withdorado correct
and the r10.4.1 model?Can you please provide me with some information when the dorado team plan to release the r9.4.1 model for
dorado correct
pipeline?Best regards
Asan
The text was updated successfully, but these errors were encountered: