SplitNCigarReads

Splits reads that contain Ns in their cigar string (e.g.

Category Sequence Data Processing Tools

Traversal ReadWalker

PartitionBy READ


Overview

spanning splicing events). Identifies all N cigar elements and creates k+1 new reads (where k is the number of N cigar elements). The first read includes the bases that are to the left of the first N element, while the part of the read that is to the right of the N (including the Ns) is hard clipped and so on for the rest of the new reads. User: ami Date: 11/14/13 Time: 11:52 AM

Additional Information

Read filters

This Read Filter is automatically applied to the data by the Engine before processing by SplitNCigarReads.

Downsampling settings

This tool does not apply any downsampling by default.


Command-line Arguments

Inherited arguments

The arguments described in the entries below can be supplied to this tool to modify its behavior. For example, the -L argument directs the GATK engine restricts processing to specific genomic intervals (this is an Engine capability and is therefore available to all GATK walkers).

SplitNCigarReads specific arguments

This table summarizes the command-line arguments that are specific to this tool. For more details on each argument, see the list further down below the table or click on an argument name to jump directly to that entry in the list.

Argument name(s) Default value Summary
Optional Outputs
--out
 -o
stdout Write output to this BAM filename instead of STDOUT
Optional Flags
--doNotFixOverhangs
false do not have the walker hard-clip overhanging sections of the reads
Advanced Parameters
--maxBasesInOverhang
 -maxOverhang
40 max number of bases allowed in the overhang
--maxMismatchesInOverhang
 -maxMismatches
1 max number of mismatches allowed in the overhang
--maxReadsInMemory
 -maxInMemory
150000 max reads allowed to be kept in memory at a time by the BAM writer

Argument details

Arguments in this list are specific to this tool. Keep in mind that other arguments are available that are shared with other tools (e.g. command-line GATK arguments); see Inherited arguments above.


--doNotFixOverhangs / -doNotFixOverhangs

do not have the walker hard-clip overhanging sections of the reads

boolean  false


--maxBasesInOverhang / -maxOverhang

max number of bases allowed in the overhang
If there are more than this many bases in the overhang, we won't try to hard-clip them out

int  40  [ [ -?  ? ] ]


--maxMismatchesInOverhang / -maxMismatches

max number of mismatches allowed in the overhang
If there are more than this many mismatches within the overhang regions, the whole overhang will get hard-clipped out. It is still possible in some cases that the overhang could get clipped if the number of mismatches do not exceed this value, e.g. if most of the overhang mismatches.

int  1  [ [ -?  ? ] ]


--maxReadsInMemory / -maxInMemory

max reads allowed to be kept in memory at a time by the BAM writer
For expert users only! To minimize memory consumption you can lower this number, but then the tool may skip overhang fixing in regions with too much coverage. Just make sure to give Java enough memory! 4Gb should be enough with the default value.

int  150000  [ [ -?  ? ] ]


--out / -o

Write output to this BAM filename instead of STDOUT

GATKSAMFileWriter  stdout


See also Guide Index | Tool Documentation Index | Support Forum

GATK version 3.2-2-gec30cee built at 2014/07/17 17:54:48. GTD: NA