We've moved!
This site is now read-only. You can find our new documentation site and support forum for posting questions here.
Be sure to read our welcome blog!

MuTect2 --filter_reads_with_N_cigar VS SplitNCigarReads

mattqdeanmattqdean CAMember
edited February 2016 in Ask the GATK team

I am calling variants in RNA-seq data. From the guide posted here, I know that Split'N'Trim is part of the workflow which has ALLOW_N_CIGAR_READS.

I am wondering if I simply use Mutect2 --filter_reads_with_N, would I be losing out on anything during downstream analysis?

I do not have to reassign MQ to unique mappers as I have set it to 60 (instead of 255) in STAR. By chance, does TopHat2 preserve MQ of each read bases? Ideally I'd like to filter variants using MQ down the road.

Issue · Github
by Sheila

Issue Number
625
State
closed
Last Updated
Assignee
Array
Milestone
Array
Closed By
vdauwera

Answers

  • Geraldine_VdAuweraGeraldine_VdAuwera Cambridge, MAMember, Administrator, Broadie admin

    Hi Matt,

    You'd lose all reads spanning splice junctions from your analysis, which would probably dramatically lower your power to discover mutations in a lot of places. I wouldn't recommend doing this.

    No idea about TopHat behavior, sorry.

Sign In or Register to comment.