-
Notifications
You must be signed in to change notification settings - Fork 16
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
File name collision due to "." in the file name #193
Labels
bug
Something isn't working
Comments
see also #192 |
ah, nice @MarieLataretu , thx ;) |
We can do basename instead of simplename. But then every sample name has
still the .fastq at the end.
There is also a filename collision if we have the same fasta headers.
Martin Hölzer ***@***.***> schrieb am Do., 13. Jan. 2022,
14:40:
… ah, nice @MarieLataretu <https://github.com/MarieLataretu> , thx ;)
—
Reply to this email directly, view it on GitHub
<#193 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIQSLLXD4B75C6AV5CXJZL3UV3I3FANCNFSM5L33M7KQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
closing this as its referenced in #192 |
Yes thx for closing, we just opened the issues simultaneously ;) lets continue the discussion in #192 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We run poreCov directly on some provided FASTQ files w/o checking the file names in detail. The pipeline failed then because of
The issue is very likely the FASTQ file names:
and it seems that in the pipeline everything after the first "." gets removed. And then we end up with a channel that has non-unique entries
foobar2
.Can we fix this, or include something to test the file names before the pipeline really starts?
The text was updated successfully, but these errors were encountered: