DNA sequencing workflow involving UMIs
1
1
Entering edit mode
3 months ago
ww22runner ▴ 60

Hello everyone,

I currently use a workflow for NGS without UMIs that looks like this upstream:

a. Fastqs
b. Remove sequence adapters
c. Alignment using BWA MEM
d. Index bam
e. Picard MarkDuplicates to remove duplicate reads
f. Recalibrate bam
g. CollectHSMetrics
h. Variant calling tools downstream.

However, now I am trying to modify the above pipeline to include UMI and the workflow suggested to me was:

  1. Fastqs to unaligned bams
  2. Extract UMI bases as an unaligned BAM tag
  3. Unaligned BAM to Fastq
  4. Alignment using BWA MEM
  5. Merge aligned BAM with unaligned BAM that contains UMI tags
  6. Group reads by UMI
  7. Call consensus reads
  8. Align duplex consensus reads (unaligned consensus reads to Fastq & alignment using BWA MEM)
  9. CollectHSMetrics

I am having trouble understanding how I would merge both these workflows together (order of steps to follow). Would a combined workflow look something like this?

  1. ( 1 ) Fastqs to unaligned bams
  2. ( 2 ) Extract UMI bases as an unaligned BAM tag
  3. ( 3 ) Unaligned BAM to Fastq
  4. ( b ) remove sequence adapters
  5. ( c/4 ) Alignment using BWA MEM
  6. ( d ) Index bam
  7. ( 5 ) Merge aligned BAM with unaligned BAM that contains UMI tags
  8. ( 6 ) Group reads by UMI
  9. ( 7 ) Call consensus reads
  10. ( 8 ) Align duplex consensus reads (unaligned consensus reads to Fastq & alignment using BWA MEM)
  11. ( f ) Recalibrate bam
  12. ( g/9 ) CollectHSMetrics
  13. ( h ) Variant calling tools downstream.

Any advice on how to proceed would be appreciated!

Thank you

dna umi sequencing • 467 views
ADD COMMENT
0
Entering edit mode

I've reformatted your post so it's clearer to understand. Italics and bold without formatting were difficult to understand.

ADD REPLY

Login before adding your answer.

Traffic: 2093 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6