comparison snpSift_rmInfo.xml @ 8:2f40467536cf draft

planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tool_collections/snpsift/snpsift commit 93465571cf180554c3548338a68fa0f1604985dc-dirty
author jjohnson
date Sat, 09 Apr 2016 11:53:30 -0400
parents baf6602903e1
children
comparison
equal deleted inserted replaced
7:c29f29a6f26c 8:2f40467536cf
5 </macros> 5 </macros>
6 <expand macro="requirements" /> 6 <expand macro="requirements" />
7 <expand macro="stdio" /> 7 <expand macro="stdio" />
8 <expand macro="version_command" /> 8 <expand macro="version_command" />
9 <command><![CDATA[ 9 <command><![CDATA[
10 java -Xmx2G -jar \$SNPEFF_JAR_PATH/SnpSift.jar rmInfo $input ' '.join($info_fields.split(',')) > $output 10 java -Xmx2G -jar "\$SNPEFF_JAR_PATH/SnpSift.jar" rmInfo "$input" ' '.join($info_fields.split(',')) > "$output"
11 ]]> 11 ]]>
12 </command> 12 </command>
13 <inputs> 13 <inputs>
14 <param format="vcf" name="input" type="data" label="Variant input file in VCF format"/> 14 <param format="vcf" name="input" type="data" label="Variant input file in VCF format"/>
15 <param name="info_fields" type="text" value="" label="Info fields to remove, e.g. EFF"> 15 <param name="info_fields" type="text" value="" label="Info fields to remove, e.g. EFF">
50 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. 50 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.
51 51
52 @EXTERNAL_DOCUMENTATION@ 52 @EXTERNAL_DOCUMENTATION@
53 http://snpeff.sourceforge.net/SnpSift.html#rmInfo 53 http://snpeff.sourceforge.net/SnpSift.html#rmInfo
54 54
55 @CITATION_SECTION@
56
57 ]]> 55 ]]>
58 </help> 56 </help>
57 <expand macro="citations" />
59 </tool> 58 </tool>