-
Notifications
You must be signed in to change notification settings - Fork 38
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
Fastp sc #331
base: dev
Are you sure you want to change the base?
Fastp sc #331
Conversation
|
tuple val(meta_2), path(orig_r1), path(orig_r2) | ||
|
||
output: | ||
tuple val(meta), path('*R1_001.fastq.gz'), path('*R2_001.fastq.gz') , emit: reads |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The files won't necessarily end with R1_001.fastq.gz
unless we force them to be named this way. Would it be a possibility to rename at this step the fastq files so that they have the name that cellranger expects? We have to be careful with different files from the same sample that correspond to different lanes though
|
||
script: | ||
""" | ||
mv ${R1} fastp_${orig_r1} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why adding fastp
at the beginning of the filenames?
This pr adds the fastp module to the raw single cell based subworkflow.