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

MirTrace uses untrimmed fastq input #242

Closed
apeltzer opened this issue May 8, 2023 · 0 comments
Closed

MirTrace uses untrimmed fastq input #242

apeltzer opened this issue May 8, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@apeltzer
Copy link
Member

apeltzer commented May 8, 2023

Description of the bug

The Fastqc reports are available for both before and after trimming (as intended).

Mirtrace however uses the untrimmed fastq file:

// SUBWORKFLOW: mirtrace QC
//
FASTQC_FASTP.out.adapterseq
.join( ch_cat_fastq )
.map { meta, adapterseq, fastq -> [adapterseq, meta.id, fastq] }
.groupTuple()
.set { ch_mitrace_inputs }
MIRTRACE(ch_mitrace_inputs)
ch_versions = ch_versions.mix(MIRTRACE.out.versions.ifEmpty(null))

This should be adjusted I think to match expectations here ...

Command used and terminal output

No response

Relevant files

No response

System information

No response

@apeltzer apeltzer added the bug Something isn't working label May 8, 2023
@apeltzer apeltzer closed this as completed May 8, 2023
apeltzer added a commit that referenced this issue May 8, 2023
Proposed fix for MirTrace uses untrimmed fastq input #242
nschcolnicov pushed a commit that referenced this issue Oct 10, 2024
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

No branches or pull requests

1 participant