# HG changeset patch # User devteam # Date 1392345384 18000 # Node ID 67d9a5a686ecc6a8c06af7711f1139938d3f44e0 # Parent 70c2d93ea2175653f3465a18a1d64ecdd0b59506 Uploaded diff -r 70c2d93ea217 -r 67d9a5a686ec picard_ReplaceSamHeader.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/picard_ReplaceSamHeader.xml Thu Feb 13 21:36:24 2014 -0500 @@ -0,0 +1,104 @@ + + + picard + + picard_wrapper.py + --input "$inputFile" + -o $outFile + --header-file $headerFile + --output-format $outputFormat + -j "\$JAVA_JAR_PATH/ReplaceSamHeader.jar" + --tmpdir "${__new_file_path__}" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +.. class:: infomark + +**Purpose** + +Replace Sam Header with the header from another sam file. The tool does not do any +significant validation, so it's up to the user to make sure that the elements in +the header are relevant and that the new header has all the required things. + +Replace the SAMFileHeader in a SAM file with the given header. Validation is +minimal. It is up to the user to ensure that all the elements referred to in the +SAMRecords are present in the new header. Sort order of the two input files must +be the same. + +**Picard documentation** + +This is a Galaxy wrapper for ReplaceSamHeader, a part of the external package Picard-tools_. + + .. _Picard-tools: http://www.google.com/search?q=picard+samtools + +------ + +.. class:: infomark + +**Inputs and outputs** + +Either a sam file or a bam file is required as the file whose header will be replaced. +The header file is also required and can also be either sam or bam (it does not have +to be the same type as the other file). In both cases, if a bam file is used, it must +be coordinate-sorted. Galaxy currently coordinate-sorts all bam files. + +The tool will output either bam (the default) or sam. Bam is recommended since it is smaller. + +.. 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. + + + + +