-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fix bcl2fastq
and bclconvert
publishDir
#157
Conversation
There should be no space after a comma when using `{xx,yy}` in a glob. This also fixes the bcl2fastq test snapshot
RunInfo.xml is not an output file of bclconvert nor bcl2fastq, it is generated by the instrument.
|
Looking good, thanks @Aratz |
Can you maybe update the modules to close #156 while you're at it? |
Yes, I have it ready on my work computer actually, but decided to just start with these commits to make reviewing this PR easier since the module update affects many different files and snapshots. Will push tomorrow 👍 |
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.
Looks good to me! Let's leave the version bump to seperate PR.
This PR addresses the following issues:
publishDir
was set to{Reports, Stats}
(note the space beforeStats
), which caused theStats
folder to be excluded (see here for more details on globs).RunInfo.xml
is not listed as an output of the bcl2fastq/bclconvert modules and will not appear in the output directory, even if it is specified inpublisDir
(which is fine becauseRunInfo.xml
is actually an input file generated by the instrument for the demultiplexer). This PR removes this file frompublishDir
.PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).CHANGELOG.md
is updated.