Skip to content

Reads strand after predictions #3

Description

@akramdi

Hi,

I was able to run reorientexpress and map the stranded reads using mnimap2:

minimap2 -ax splice -G 30k -u f $CHRLEN $strandedFASTQ

Minimap2 reports the transcript strand in the ts tag of alignment files. I noticed that, for some reads, the strand reported in ts tag does not match strand of the read reported by sam flags. This usually occurs when we deal with unstranded libraries, but here the fastq files are supposed to be stranded.

Here a snapshot of two genes that should produce transcripts in the forward orientation.

  1. If I color the reads using the ts tag, they agree with the gene orientation in both cases:

reorient_question-color-ts

  1. But if I keep the default coloring (read strands), the orientation is off:

reorient_question

Because the libraries are stranded now, shouldn't we expect that the read strands to match the actual transcript orientation? Can you help me understand why is not the case?

Thanks for the help,
Amira

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions