comparison picard_ReplaceSamHeader.xml @ 13:7e6fd3d0f16e draft

planemo upload for repository https://github.com/galaxyproject/tools-devteam/tree/master/tools/picard commit bf94a1505c131fb3f67c867b6e1d886780efa42e

12:05087b27692a

    <import>picard_macros.xml</import>
  </macros>
  <expand macro="requirements" />
  <command detect_errors="exit_code"><![CDATA[
    @java_options@
    
  
    ## Two lines below are due to the fact that picard likes fasta files to have extension .fa  
    #set $fasta_file="local_fasta.fa"
    ln -s "${inputFile}" "${fasta_file}" &&    
    
    picard
    ReplaceSamHeader
    
    INPUT="${inputFile}"
    HEADER="${header}"
    OUTPUT="${outFile}"
    
    QUIET=true
    VERBOSITY=ERROR
  
  ]]></command>
  <inputs>
    <param format="sam,bam" name="inputFile" type="data" label="Select SAM/BAM dataset or dataset collection (header recepient dataset)" help="If empty, upload or import a SAM/BAM dataset"/>
    <param name="header" type="data" format="sam,bam" label="SAM/BAM dataset from which Header will be read (header source dataset)" help="HEADER; If empty, upload or import a SAM/BAM dataset"/>
  </inputs> 
  
  <outputs>
    <data format="bam" name="outFile" label="${tool.name} on ${on_string}: BAM file with replaced header"/>
  </outputs>
  
  <tests>
    <test>
      <param name="inputFile" value="picard_ReplaceSamHeader.bam" ftype="bam"/>
      <param name="header" value="picard_ReplaceSamHeader_header.bam" ftype="bam"/>
      <output name="outFile" file="picard_ReplaceSamHeader_test1.bam" ftype="bam"/>
    </test>
  </tests>
  
  
  <help>

**Purpose**

Replace the SAMFileHeader in a SAM/BAM dataset 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 datasets must be the same.
@dataset_collections@

@description@

  HEADER=File                   SAM file from which SAMFileHeader will be read.  Required. 

@more_info@

  </help>
</tool>

13:7e6fd3d0f16e

    <import>picard_macros.xml</import>
  </macros>
  <expand macro="requirements" />
  <command detect_errors="exit_code"><![CDATA[
    @java_options@
    @symlink_element_identifier@

    ## Two lines below are due to the fact that picard likes fasta files to have extension .fa
    #set $fasta_file="local_fasta.fa"
    ln -s "${inputFile}" "${fasta_file}" &&

    picard
    ReplaceSamHeader

    INPUT='$inputFile.element_identifier'
    HEADER="${header}"
    OUTPUT="${outFile}"

    QUIET=true
    VERBOSITY=ERROR

  ]]></command>
  <inputs>
    <param format="sam,bam" name="inputFile" type="data" label="Select SAM/BAM dataset or dataset collection (header recepient dataset)" help="If empty, upload or import a SAM/BAM dataset"/>
    <param name="header" type="data" format="sam,bam" label="SAM/BAM dataset from which Header will be read (header source dataset)" help="HEADER; If empty, upload or import a SAM/BAM dataset"/>
  </inputs>

  <outputs>
    <data format="bam" name="outFile" label="${tool.name} on ${on_string}: BAM file with replaced header"/>
  </outputs>

  <tests>
    <test>
      <param name="inputFile" value="picard_ReplaceSamHeader.bam" ftype="bam"/>
      <param name="header" value="picard_ReplaceSamHeader_header.bam" ftype="bam"/>
      <output name="outFile" file="picard_ReplaceSamHeader_test1.bam" ftype="bam"/>
    </test>
  </tests>


  <help>

**Purpose**

Replace the SAMFileHeader in a SAM/BAM dataset 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 datasets must be the same.
@dataset_collections@

@description@

  HEADER=File                   SAM file from which SAMFileHeader will be read.  Required.

@more_info@

  </help>
</tool>