# HG changeset patch # User devteam # Date 1392162161 18000 # Node ID c2f6ec2fee7e3ac3bcc669c87475296e4eb958c0 # Parent 7a6490baa53a8c7d3cf9cc92340a13e6f02ef35c Uploaded diff -r 7a6490baa53a -r c2f6ec2fee7e picard_SamFormatConverter.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/picard_SamFormatConverter.xml Tue Feb 11 18:42:41 2014 -0500 @@ -0,0 +1,74 @@ + + picard + + picard_wrapper.py + --input="$inputFile" + --output-format=$outputFormat + --output=$outFile + -j "\$JAVA_JAR_PATH/SamFormatConverter.jar" + + + + + + + + + + + + + + + + + + + + + + + + + + + +.. class:: infomark + +**Purpose** + +Convert a BAM file to a SAM file, or BAM to SAM. + +This is a Galaxy wrapper for SamFormatConverter, a part of the external package Picard-tools_. + + .. _Picard-tools: http://www.google.com/search?q=picard+samtools + +------ + +.. class:: infomark + +**Inputs, outputs, and parameters** + +Either a sam file or a bam file must be supplied. If a bam file is used, it must +be coordinate-sorted. Galaxy currently coordinate-sorts all bam files. + +The output file is either bam (the default) or sam, according to user selection, +and contains the same information as the input file except for the appropraite +additional (or modified) read group tags. Bam is recommended since it is smaller. + +**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. + + + + +