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

Only a single dedup.log file is exported to final deduplication/dedup directory #154

Closed
jfy133 opened this issue Mar 1, 2019 · 3 comments
Labels
bug Something isn't working minor

Comments

@jfy133
Copy link
Member

jfy133 commented Mar 1, 2019

Describe the bug
Presumably due to having the same name, only a single dedup.log file is present in the deduplication/dedup output directory. Note that the .hist files are correctly there for every sample. Just the .log is not.

To Reproduce
Run a pipeline (-r dev) with DeDup included.

Expected behavior
A dedup.log file is presented for every sample

@jfy133 jfy133 added bug Something isn't working minor labels Mar 1, 2019
@apeltzer
Copy link
Member

apeltzer commented Mar 1, 2019

Ah that should be an easy fix .... its just not yet published the file, they're all there. Never thought anybody wants them to be able to see them ;-)

@jfy133
Copy link
Member Author

jfy133 commented Mar 1, 2019

Yeah exactly, they are in work/* but I have a feeling when 'publishing' them to the main output directory each one overwrites the other. If that's what you mean.

Me neither, very much an edge case when trying to fix the DamageProfiler/Qualimap issue from 2.0.5, and I re-ran MultiQC. Would never have had noticed otherwise 😆

@apeltzer
Copy link
Member

apeltzer commented Mar 1, 2019

Ah its not a problem to have multiple output folders based on sample names in the $outdir folder at all, can do that 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working minor
Projects
None yet
Development

No branches or pull requests

2 participants