Mercurial > repos > pieterlukasse > prims_proteomics
annotate napq.xml @ 22:ac357ec3e08e
fix
author | pieter.lukasse@wur.nl |
---|---|
date | Mon, 26 Jan 2015 06:50:39 +0100 |
parents | 46f568202d46 |
children | b1f68fcb7d99 |
rev | line source |
---|---|
17
40ec8770780d
* Added support for pepxml (and more specifically for
pieter.lukasse@wur.nl
parents:
16
diff
changeset
|
1 <tool name="NapQ" id="napq" version="0.0.3"> |
5 | 2 <description>'no alignment' (alignment-free) peptide quantification</description> |
0 | 3 <!-- |
4 For remote debugging start you listener on port 8000 and use the following as command interpreter: | |
5 java -jar -Xdebug -Xrunjdwp:transport=dt_socket,address=D0100564.wurnet.nl:8000 | |
6 ////////////////////////// | |
7 --> | |
8 <command interpreter="java -jar "> | |
9 NapQ.jar | |
10 -identificationsConfigFile $identificationsConfigFile | |
6 | 11 -namingConventionCodesForSamples "$namingConventionCodesForSamples" |
0 | 12 #if $is2D_LC_MS.fractions == True |
6 | 13 -namingConventionCodesForFractions "$is2D_LC_MS.namingConventionCodesForFractions" |
0 | 14 #end if |
15 -outputApml $outputApml | |
16 -outputTsv $outputTsv | |
17 -outReport $htmlReportFile | |
18 -outReportPicturesPath $htmlReportFile.files_path | |
19 </command> | |
20 | |
21 <inputs> | |
22 | |
16 | 23 <repeat name="identificationFileList" title="Peptide identification files" help="Set of MS/MS peptide identification files that have some form of quantification data coupled to it (e.g. MSE identifications&intensity)."> |
0 | 24 <param name="identificationsFile" type="data" format="apml,mzidentml,prims.fileset.zip" label="Identifications file (APML or MZIDENTML or MZIDENTML fileSet)" /> |
25 </repeat> | |
26 | |
27 <param name="namingConventionCodesForSamples" type="text" size="100" value="" | |
28 label="Part of run/file name that identifies the sample" | |
29 help="Add the CSV list of codes that occur in the file names | |
19 | 30 and that stand for a sample code. E.g. '_S1,_S2,_S3,etc.' "> <!-- could do regular expressions as well but this would be hard for biologists, e.g. _F\d\b --> |
31 <sanitizer> | |
32 <!-- adding more characters to the set of "valid" ones: --> | |
33 <valid> | |
34 <add value="#"/> | |
35 <add value="@"/> | |
36 <add value="$"/> | |
37 <add value="%"/> | |
38 <add value="&"/> | |
39 <add value="*"/> | |
40 <add value="["/> | |
41 <add value="]"/> | |
42 <add value="|"/> | |
43 <add value="{"/> | |
44 <add value="}"/> | |
45 </valid> | |
46 </sanitizer> | |
47 </param> | |
0 | 48 |
49 <conditional name="is2D_LC_MS"> | |
50 <param name="fractions" type="boolean" truevalue="Yes" falsevalue="No" checked="false" | |
51 label="Data is from 2D LC-MS" | |
52 help="Data acquisition was done in multiple fractions."/> | |
53 <when value="Yes"> | |
54 <param name="namingConventionCodesForFractions" type="text" size="100" value="" | |
55 label="Part of run/file name that identifies the 2D LC-MS fraction" | |
56 help="Add the CSV list of codes that occur in the file names | |
57 and that stand for a fraction code. E.g. '_F1,_F2,_F3,etc.' Use this to avoid | |
19 | 58 that each (fraction) file is seen as a separate run."> <!-- could do regular expressions as well but this would be hard for biologists, e.g. _F\d\b --> |
59 <sanitizer> | |
60 <!-- adding more characters to the set of "valid" ones: --> | |
61 <valid> | |
62 <add preset="string.printable"/> | |
63 <add value="#"/> | |
64 <add value="@"/> | |
65 <add value="$"/> | |
66 <add value="%"/> | |
67 <add value="&"/> | |
68 <add value="*"/> | |
69 <add value="["/> | |
70 <add value="]"/> | |
71 <add value="|"/> | |
72 <add value="{"/> | |
73 <add value="}"/> | |
74 </valid> | |
75 </sanitizer> | |
76 </param> | |
77 | |
0 | 78 </when> |
6 | 79 <when value="No"> |
80 </when> | |
0 | 81 </conditional> |
82 | |
83 </inputs> | |
84 <configfiles> | |
85 <configfile name="identificationsConfigFile">## start comment | |
86 ## iterate over the selected files and store their names in the config file | |
87 #for $i, $s in enumerate( $identificationFileList ) | |
16 | 88 ${s.identificationsFile} |
0 | 89 ## also print out the datatype in the next line, based on previously configured datatype |
90 #if isinstance( $s.identificationsFile.datatype, $__app__.datatypes_registry.get_datatype_by_extension('apml').__class__): | |
91 apml | |
92 #else: | |
93 mzid | |
94 #end if | |
95 #end for | |
96 ## end comment</configfile> | |
97 </configfiles> | |
98 <outputs> | |
99 <data name="outputApml" format="apml" label="${tool.name} on ${on_string}: peptide quantifications (APML)"/> | |
100 <data name="outputTsv" format="tabular" label="${tool.name} on ${on_string}: peptide quantifications (TSV)"/> | |
101 <!-- in tsv we can have cols like: pep, avg_m/z, avg rt, m/z window, rt window, i_s1, i_s2, ...--> | |
102 <data name="htmlReportFile" format="html" label="${tool.name} on ${on_string} - HTML report"/> | |
103 <!-- here we show the samples extracted and the files used to 'build up' each sample --> | |
104 </outputs> | |
105 <tests> | |
106 </tests> | |
107 <help> | |
108 | |
109 .. class:: infomark | |
110 | |
111 This tool takes in multiple peptide identification result files that have peptide identifications | |
112 coupled to some quantification (e.g. precursor intensity information or for example data coming | |
113 from MS^E acquisition where peptide identification and quantification are done in the same run and reported together). | |
114 Then, based on the given experiment design parameters (i.e. how the result files related back to | |
115 replicate runs and samples), it produces a new file in which the peptides are reported with | |
116 their calculated quantifications at the sample level. | |
117 | |
118 The figure below explains this: | |
119 | |
120 .. image:: $PATH_TO_IMAGES/napq_overview.png | |
121 | |
4 | 122 . |
0 | 123 |
124 | |
125 | |
126 | |
127 </help> | |
128 </tool> |