-
Notifications
You must be signed in to change notification settings - Fork 127
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
Valid --mirtrace_species
is required even with --mirgenedb
when --mirgenedb_species
is given
#348
Comments
I believe this is a structural issue. The statements using MirGeneDB is in an |
It shouldnt break functionality per se, but agree this should be fixed. |
is this still a problem in dev? I ran with this options, and mirtop ran with mirgenedb and mirtrace worked fine.
Happy to know more so I can help to fix this if I misunderstood. |
just to add more context, |
I was able to reproduce the error.
Instead of exiting with the error The fix is to make this check conditional, based on whether I am working on this. |
Adding this #131 as it has the same source of error. |
Closed via #378 |
Description of the bug
According to the documentation, it appears that the miRNA databases miRBase (used by default) and MirGeneDB are alternative sources of reference files, and either can be used. However, the parameter
--mirtrace_species
, which sets the species of the miRBase reference files, is required and there is no way to only use MirGeneDB.Command used and terminal output
Relevant files
No response
System information
The text was updated successfully, but these errors were encountered: