-
Notifications
You must be signed in to change notification settings - Fork 22
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
Error with uncompressed FASTA files #309
Comments
Thanks @tavareshugo ! Much of the team is either on parental leave (myself) or at conferences this week, so we might be slow in replying currently! The first is definitely a bug (from me, my bad!), if you've already patched it - would you be willing to open a PR? The second also I agree would be worth supplying, but it would be important to test to make sure all the screening tools accept this as input (some are fickly with file naming...). If you had time, would you be able to do this? Otherwise one of us can test once we are back next week :) |
fix input schema to accept uncompressed fasta; fix #309
Closed by #310 |
Description of the bug
When supplying uncompressed FASTA files in the samplesheet, I now get an error:
I've locally patched it by changing the regular expression in the schema_input.json:
To make
.gz
optional.In addition, I believe the current expression doesn't accept
.fas
, which is also sometimes used for FASTA files.Perhaps the expression could be changed to:
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: