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

fastqc results don't always line up in summary file #148

Closed
erinyoung opened this issue Apr 12, 2023 · 4 comments · Fixed by #347
Closed

fastqc results don't always line up in summary file #148

erinyoung opened this issue Apr 12, 2023 · 4 comments · Fixed by #347
Labels
bug Something isn't working

Comments

@erinyoung
Copy link
Member

If the sample name doesn't match what fastqc and multiqc thinks it should be, then the fastqc results don't get linked to the right sample in the final summary file.

This is annoying.

@erinyoung erinyoung added the bug Something isn't working label Apr 12, 2023
@erinyoung
Copy link
Member Author

In principle, what needs to happen is some sort of file or key with the sample and corresponding fastq files that can be used for matching.

@erinyoung
Copy link
Member Author

vadr results have similar issues (see kitchen sink test to replicate)

nextflow run ~/sandbox/Cecret \
    -profile singularity,artic_V3 \
    --reads /home/eriny/sandbox/test_files/cecret/reads \
    --single-reads /home/eriny/sandbox/test_files/cecret/single-reads \
    --fastas /home/eriny/sandbox/test_files/cecret/fastas \
    --multifastas /home/eriny/sandbox/test_files/cecret/multifasta \
    --outdir kitchen_sink  \
    -with-tower

@erinyoung
Copy link
Member Author

FastQC results now line up, but there wasn't time to check vadr for 3.6.20230418

@erinyoung
Copy link
Member Author

Fixed in #157

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

Successfully merging a pull request may close this issue.

1 participant