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

Losing unmapped reads after alignment #92

Open
anoronh4 opened this issue Sep 13, 2023 · 0 comments
Open

Losing unmapped reads after alignment #92

anoronh4 opened this issue Sep 13, 2023 · 0 comments

Comments

@anoronh4
Copy link
Collaborator

anoronh4 commented Sep 13, 2023

STAR_ALIGN process is not keeping the unmapped reads in the BAM. as a result, kallisto is not attempting to map any reads that STAR was unable to map and we may be losing some of the advantages of kallisto. in addition, when a sample does not have UMI the reads that STAR is not able to map are included in kallisto, which means the two workflows are somewhat inconsistent.

umitools dedup does not handle read pairs where r1 is unmapped, so one way to address this issue is to set aside the unmapped reads in a separate set of fastqs (which STAR can probably do) and add them to Kallisto's input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant