Skip to content
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

conflict of library names for tecnical replicates #664

Closed
ChristopherBarrington opened this issue Jun 30, 2021 · 1 comment
Closed

conflict of library names for tecnical replicates #664

ChristopherBarrington opened this issue Jun 30, 2021 · 1 comment
Labels
bug Something isn't working WIP Work in progress
Milestone

Comments

@ChristopherBarrington
Copy link

Description of the bug

Technical replicates must have different FastQ file names for the pipeline to work. In my case the same pool of libraries was sequenced on two flow cells and had the exact same file names. The pipeline then tries to cat the files together (I think this was the step that failed) but nextflow can't produce the symlinks in the work directory because the multiple files have the same file name.

In the meantime I have changed the file name of the FastQ so that I have _00{1,2}.fastq.gz to distinguish the flow cells on which the libraries were sequenced and the pipeline seems happy with that.

@drpatelh
Copy link
Member

Will be fixed when the changes here are merged and re-installed into the pipeline nf-core/modules#1107

@drpatelh drpatelh added the WIP Work in progress label Dec 13, 2021
drpatelh added a commit to drpatelh/nf-core-rnaseq that referenced this issue Dec 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working WIP Work in progress
Projects
None yet
Development

No branches or pull requests

2 participants