-
Notifications
You must be signed in to change notification settings - Fork 113
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
fastq filename convention and sample name parsing #182
Comments
This behaviour reflects how QIIME2 parses file names. For other file name patterns, you can use the Documentation in |
Thank you, Daniel! Perfect :) 👍 |
Actually, I think it should work with edit: |
Fixed in dev. |
Hi Everyone!
Sample name is parsed by splitting the filename on
_
.This breaks when the sample names are different from
xxxx_L001_R{1,2}_001fastq.gz
or has an unexpected lack of_
In the documentation it is not obvious, that one should have the
_L001_
in the filename.I had samples named
G0-3-2_R1_001.fastq.gz
with theG0-3-2
being different sample names (only the numbers varied, single digits in all cases).Running with default parameters:
./nextflow run nf-core/ampliseq -profile singularity --input reads --FW_primer GTGCCAGCMGCCGCGGTAA --RV_primer GGACTACHVGGGTWTCTAAT --metadata metadata.txt
Resulted in:
notice the absence of the sample name in the file
cutadapt_log_.txt
I renamed the input samples to:
G032_L001_R1_001.fastq.gz
and it went through.G0-3-2_L001_R1_001.fastq.gz
also tested and also worked.Proposed change:
Altering the documentation to reflect this, or changing the way the filenames are parsed in main.nf
Hope this helps 😄
Thank you for your amazing work!
All the best,
Jan
The text was updated successfully, but these errors were encountered: