# HG changeset patch # User devteam # Date 1391028758 18000 # Node ID 70b3d18820494923b461eb05ecc5e0e999efef42 # Parent 245d730d4e643e234fc59810bbd7af56b128c1a3 Uploaded diff -r 245d730d4e64 -r 70b3d1882049 picard_ReorderSam.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/picard_ReorderSam.xml Wed Jan 29 15:52:38 2014 -0500 @@ -0,0 +1,166 @@ + + picard + + picard_wrapper.py + --input="${inputFile}" + #if $source.indexSource == "built-in" + --ref="${source.ref.fields.path}" + #else + --ref-file="${refFile}" + --species-name="${source.speciesName}" + --build-name="${source.buildName}" + --trunc-names="${source.truncateSeqNames}" + #end if + --allow-inc-dict-concord="${allowIncDictConcord}" + --allow-contig-len-discord="${allowContigLenDiscord}" + --output-format="${outputFormat}" + --output="${outFile}" + --tmpdir "${__new_file_path__}" + -j "\$JAVA_JAR_PATH/ReorderSam.jar" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +.. class:: infomark + +**Purpose** + +Reorder SAM/BAM to match contig ordering in a particular reference file. Note that this is +not the same as sorting as done by the SortSam tool, which sorts by either coordinate +values or query name. The ordering in ReorderSam is based on exact name matching of +contigs/chromosomes. Reads that are mapped to a contig that is not in the new reference file are +not included in the output. + +**Picard documentation** + +This is a Galaxy wrapper for ReorderSam, a part of the external package Picard-tools_. + + .. _Picard-tools: http://www.google.com/search?q=picard+samtools + +------ + +.. class:: infomark + +**Inputs, outputs, and parameters** + +For the file that needs to be reordered, either a sam file or a bam file must be supplied. +If a bam file is used, it must be coordinate-sorted. A reference file is also required, +so either a fasta file should be supplied or a built-in reference can be selected. + +The output contains the same reads as the input file but the reads have been rearranged so +they appear in the same order as the provided reference file. The tool will output either +bam (the default) or sam, according to user selection. Bam is recommended since it is smaller. + +The only extra parameters that can be set are flags for allowing incomplete dict concordance +and allowing contig length discordance. If incomplete dict concordance is allowed, only a +partial overlap of the bam contigs with the new reference sequence contigs is required. By +default it is off, requiring a corresponding contig in the new reference for each read contig. +If contig length discordance is allowed, contig names that are the same between a read and the +new reference contig are allowed even if they have different lengths. This is usually not a +good idea, unless you know exactly what you're doing. It's off by default. + +.. class:: warningmark + +**Warning on SAM/BAM quality** + +Many SAM/BAM files produced externally and uploaded to Galaxy do not fully conform to SAM/BAM specifications. Galaxy deals with this by using the **LENIENT** +flag when it runs Picard, which allows reads to be discarded if they're empty or don't map. This appears +to be the only way to deal with SAM/BAM that cannot be parsed. + + + + + + + + + + + + + + + +