-
Notifications
You must be signed in to change notification settings - Fork 18
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
Names for forwards and reverse reads does not match. Cannot continue #42
Comments
The code is seroba/seroba/tasks/sero_run.py Lines 10 to 12 in 37a5737
Is this operating on the read FILENAMES or the READ IDs ? Mine are |
This operates on FILENAMES Looking at the code as it is written, it has the assumption that read filenames are in the format _{R1,R2,1,2}.fastq.gz
A fudge solution would be to make softlinks that remove the _001 until the sanger-pathogens team have bandwidth to correct the code |
Thanks once again @aunderwo |
Argh. Our other system is to use |
I was implementing a seroba component on flowcraft and getting this error when some particular components came before seroba. Thank you @tseemann and @aunderwo for your discussion! Without it I could not have figured it out! And @tseemann, I'm renaming all the input files to ${sample_id}_{1,2}.fq.gz to make it work. :) Thanks!!! |
I don't feel I should have to rename my files for a tool to work :( |
Even I have the same issue. I am using Docker image and renamed files as read_1.fq.gz and read_2.fq.gz as suggested by @cimendes. The issue isn't resolved. Any suggestions on how to resolve this? |
renaming the files to $name_1.fastq.gz and $name_2.fastq.gz worked. |
I tried this, but still no luck. Has anybody come across another workaround?
|
Hey @fgonzalez3 - I haven't used it in a while. I think I actually made changes in the Python code of Seroba to recognize the filenames we use. I will try to find it and share it here. Also, you can always try using other tools. |
I am getting this error:
My R1 file:
My R2 file:
CC: @aunderwo
The text was updated successfully, but these errors were encountered: