-
Notifications
You must be signed in to change notification settings - Fork 46
Fastp sc #331
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
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
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.
good point. I removed the R1_001.fastq.gz part.
However, I think since we only allow 10x right now, the user should give the right naming for now. Also considering lane numbering. I dont know how we could catch the line otherwise
|
|
||
| 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?
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.
just to show that those are the files that were run through fastp. In accordance to the fastp module adding ".fastp.fastq.gz" which is not possible for cellranger
|
Hi! |
It's still necessary, just missed Giselas review |
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 2.14.1. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
On the note of this PR. We use fastp quite a lot here, but as far as I can see it requires the fastqs to be gzipped, right? |
|
@mapo9 how is this PR looking? Is it ready for review? Regarding your question, I think it's fair to assume that all users will use gzipped fastq files |
This pr adds the fastp module to the raw single cell based subworkflow.