-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Allow multiple trim lengths or read structure in TrimFastq #927
Comments
@bkohrn wouldn't be too hard to change this line to take in multiple lengths:
|
* feat: allow TrimFastq to specify a length per input FASTQ See: #927 Co-authored-by: Clint Valentine <[email protected]>
+1 for read structure, so that 5' ends can be modified without having to run DemuxFastqs or FastqToBam |
What's the objection to just using |
Only that it requires bam output, so if you have downstream steps that require fastq input (e.g. 3' quality or dovetail trimming, and certain aligners e.g. BWA), you need to perform the additional step to convert the ubam back to fastq, that's all. Probably lower on the triage list than some other things, especially if there's a faster/easier means to implement the op's request. |
Mostly if the end goal is fastq files to use in further analysis (say, I have a 10X run that was sequenced as 150 x 10 x 10 x 150 bp reads, and I need to trim it down as fastq files to 26 x 10 x 10 x 90 bp reads). If I use |
I'd just pipe into |
It would be nice if we could either give multiple output read lengths (one per file) or a read structure (similar to what exists in FastqToBam) in TrimFastq.
The text was updated successfully, but these errors were encountered: