Mercurial > repos > iuc > snpsift

diff snpSift_rmInfo.xml @ 11:b884686a80dc draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tool_collections/snpsift/snpsift commit 344140b8df53b8b7024618bb04594607a045c03a
author iuc
date Mon, 04 May 2015 22:37:06 -0400
parents f0faaa4d6ee5
children ed810da439cc
line wrap: on
line diff
--- a/snpSift_rmInfo.xml	Wed Apr 29 11:55:50 2015 -0400
+++ b/snpSift_rmInfo.xml	Mon May 04 22:37:06 2015 -0400
@@ -1,9 +1,10 @@
 <tool id="snpSift_rmInfo" name="SnpSift rmInfo" version="4.0.0">
     <description>remove INFO field annotations</description>
-    <expand macro="requirements" />
     <macros>
         <import>snpSift_macros.xml</import>
     </macros>
+    <expand macro="requirements" />
+    <expand macro="stdio" />
     <command>
       java -Xmx2G -jar \$SNPEFF_JAR_PATH/SnpSift.jar rmInfo $input ' '.join($info_fields.split(',')) > $output
     </command>
@@ -17,7 +18,6 @@
     <outputs>
         <data format="vcf" name="output" />
     </outputs>
-    <expand macro="stdio" />
     <tests>
         <test>
             <param name="input" ftype="vcf" value="test-data/test_rmInfo.vcf"/>
@@ -42,10 +42,10 @@
     <help>
 This command removes INFO fields from a VCF file (i.e. removes annotations)
 
-Removing INFO fields is usually done because you want to re-annotate the VCF file, thus removing old INFO fields in order to add new ones later. 
+Removing INFO fields is usually done because you want to re-annotate the VCF file, thus removing old INFO fields in order to add new ones later.
 
-SnpEff &amp; SnpSift only add annotations and do not change current ones. So, in order to re-annotate a file, you should first remove the old annotations and then re-annotate. 
-The reason for this behavior is simply because replacing annotation values is considered a bad practice. Imagine that you have a VCF entry  in your re-annotated file having the value "AA=1": How do you know if this is from the old annotations or from the new ones? This confusion often leads to problems in downstream steps of your pipelines, so it's better to avoid the problem by first removing all the previous annotations and then adding the new ones. 
+SnpEff &amp; SnpSift only add annotations and do not change current ones. So, in order to re-annotate a file, you should first remove the old annotations and then re-annotate.
+The reason for this behavior is simply because replacing annotation values is considered a bad practice. Imagine that you have a VCF entry  in your re-annotated file having the value "AA=1": How do you know if this is from the old annotations or from the new ones? This confusion often leads to problems in downstream steps of your pipelines, so it's better to avoid the problem by first removing all the previous annotations and then adding the new ones.
 
 @EXTERNAL_DOCUMENTATION@
     http://snpeff.sourceforge.net/SnpSift.html#rmInfo