Mercurial > repos > iuc > snpsift

comparison snpSift_rmInfo.xml @ 1:98708b88af9f 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 21b46ae2c90ba7e569b2b3a9eaf938f8dedb2c31
author iuc
date Tue, 07 Jun 2016 10:04:09 -0400
parents 9e8280e19338
children bf8c1526871b
comparison
equal deleted inserted replaced
0:9e8280e19338 1:98708b88af9f
1 <tool id="snpSift_rmInfo" name="SnpSift rmInfo" version="4.0.0"> 1 <tool id="snpSift_rmInfo" name="SnpSift rmInfo" version="@WRAPPER_VERSION@.0">
2 <description>remove INFO field annotations</description> 2 <description>remove INFO field annotations</description>
3 <expand macro="requirements" />
4 <macros> 3 <macros>
5 <import>snpSift_macros.xml</import> 4 <import>snpSift_macros.xml</import>
6 </macros> 5 </macros>
7 <command> 6 <expand macro="requirements" />
8 java -Xmx2G -jar \$SNPEFF_JAR_PATH/SnpSift.jar rmInfo $input ' '.join($info_fields.split(',')) > $output 7 <expand macro="stdio" />
8 <expand macro="version_command" />
9 <command><![CDATA[
10 java -Xmx2G -jar "\$SNPEFF_JAR_PATH/SnpSift.jar" rmInfo "$input" ' '.join($info_fields.split(',')) > "$output"
11 ]]>
9 </command> 12 </command>
10 <inputs> 13 <inputs>
11 <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"/>
12 <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">
13 <help>Separate multiple INFO fields with a comma, e.g.: EFF,DP</help> 16 <help>Separate multiple INFO fields with a comma, e.g.: EFF,DP</help>
15 </param> 18 </param>
16 </inputs> 19 </inputs>
17 <outputs> 20 <outputs>
18 <data format="vcf" name="output" /> 21 <data format="vcf" name="output" />
19 </outputs> 22 </outputs>
20 <expand macro="stdio" />
21 <tests> 23 <tests>
22 <test> 24 <test>
23 <param name="input" ftype="vcf" value="test-data/test_rmInfo.vcf"/> 25 <param name="input" ftype="vcf" value="test-data/test_rmInfo.vcf"/>
24 <param name="info_fields" value="EFF"/> 26 <param name="info_fields" value="EFF"/>
25 <output name="output"> 27 <output name="output">
37 <not_has_text text="DP=29;EFF=EXON" /> 39 <not_has_text text="DP=29;EFF=EXON" />
38 </assert_contents> 40 </assert_contents>
39 </output> 41 </output>
40 </test> 42 </test>
41 </tests> 43 </tests>
42 <help> 44 <help><![CDATA[
43 This command removes INFO fields from a VCF file (i.e. removes annotations) 45 This command removes INFO fields from a VCF file (i.e. removes annotations)
44 46
45 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. 47 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.
46 48
47 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. 49 SnpEff & 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.
48 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.
49 51
50 @EXTERNAL_DOCUMENTATION@ 52 @EXTERNAL_DOCUMENTATION@
51 http://snpeff.sourceforge.net/SnpSift.html#rmInfo 53 http://snpeff.sourceforge.net/SnpSift.html#rmInfo
52 54
53 @CITATION_SECTION@ 55 ]]>
54
55 </help> 56 </help>
57 <expand macro="citations" />
56 </tool> 58 </tool>