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

Support for UMI FASTQ #871

Open
adamrtalbot opened this issue Nov 28, 2022 · 2 comments
Open

Support for UMI FASTQ #871

adamrtalbot opened this issue Nov 28, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@adamrtalbot
Copy link
Contributor

Description of feature

UMI data is sometimes stored in a third FASTQ file, typically because the UMI is embedded in the index and bcl2fastq2 cannot combine it into forward/reverse. This produces three files:
R1: Forward
R2: UMI
R3: Reverse

We can support UMI processing using this method. Key points:

  • Allow the samplesheet to include optional 3rd FASTQ
  • Ignore/handle UMI FASTQ when sending to modules that expect 2 FASTQ files to ensure compatibility
  • Allow/enforce --umi_read_structure to support >2 masks.

See nf-core/fastquorum#11 for an example implementation. Could be implemented as part of NF-Core subworkflow.

@adamrtalbot adamrtalbot added the enhancement New feature or request label Nov 28, 2022
@FriederikeHanssen
Copy link
Contributor

Nice, yes I think this is already in the planning as soon as we have the shared subworkflow. ( I think there is a PR in modules repo somewhere, we should cross check it includes this)

@maxulysse maxulysse added this to the 3.3 milestone Feb 21, 2023
@maxulysse maxulysse modified the milestones: 3.3, 3.4, 3.5 Feb 8, 2024
@lauren-tjoeka
Copy link

lauren-tjoeka commented Jul 25, 2024

Hi! Has there been any updates or current workarounds for this?

I was thinking of appending the UMI sequence to R1 and R2 using this method: OpenGene/fastp#23

@FriederikeHanssen FriederikeHanssen removed this from the 3.5 milestone Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants