comparison aplcms_macros.xml @ 0:7c80b743a2db draft

"planemo upload for repository https://github.com/RECETOX/galaxytools/tree/master/tools/aplcms commit ecdfe141b4320e754cc9f3673cc33b7673441ed8"
author recetox
date Sun, 18 Oct 2020 10:35:33 +0000
parents
children bcc9f27fea2b
comparison
equal deleted inserted replaced
-1:000000000000 0:7c80b743a2db
1 <macros>
2 <token name="@TOOL_VERSION@">6.6.6</token>
3
4 <xml name="requirements">
5 <requirements>
6 <container type="docker">recetox/aplcms:6.6.6-recetox1</container>
7 </requirements>
8 </xml>
9
10 <xml name="inputs">
11 <inputs>
12 <param name="files" type="data" format="mzdata,mzml,mzxml,netcdf" multiple="true" min="3" label="data"
13 help="Mass spectrometry files for peak extraction." />
14 <yield />
15 </inputs>
16 </xml>
17
18 <xml name="history_db">
19 <param name="known_table" type="data" format="h5" label="known_table"
20 help="A data table containing the known metabolite ions and previously found features. The table must contain these 18 columns: chemical_formula (optional), HMDB_ID (optional), KEGG_compound_ID (optional), neutral.mass (optional), ion.type (the ion form - optional), m.z (either theoretical or mean observed m/z value of previously found features), Number_profiles_processed (the total number of processed samples to build this database), Percent_found (the percentage of historically processed samples in which the feature appeared), mz_min (minimum observed m/z value), mz_max (maximum observed m/z value), RT_mean (mean observed retention time), RT_sd (standard deviation of observed retention time), RT_min (minimum observed retention time), RT_max (maximum observed retention time), int_mean.log. (mean observed log intensity), int_sd.log. (standard deviation of observed log intensity), int_min.log. (minimum observed log intensity), int_max.log. (maximum observed log intensity)." />
21 <section name="history_db" title="Known-Table settings">
22 <param name="match_tol_ppm" type="integer" optional="true" min="0" label="match_tol_ppm (optional)"
23 help="The ppm tolerance to match identified features to known metabolites/features." />
24 <param name="new_feature_min_count" type="integer" value="2" min="1" label="new_feature_min_count"
25 help="The minimum number of occurrences of a historically unseen (unknown) feature to add this feature into the database of known features." />
26 </section>
27 </xml>
28
29 <xml name="noise_filtering">
30 <section name="noise_filtering" title="Noise filtering and peak detection">
31 <param name="min_exp" type="integer" min="1" value="2"
32 label="min_exp"
33 help="If a feature is to be included in the final feature table, it must be present in at least this number of spectra." />
34 <param name="min_pres" type="float" value="0.5"
35 label="min_pres"
36 help="The minimum proportion of presence in the time period for a series of signals grouped by m/z to be considered a peak." />
37 <param name="min_run" type="float" value="12"
38 label="min_run"
39 help="The minimum length of elution time for a series of signals grouped by m/z to be considered a peak." />
40 <param name="mz_tol" type="float" value="1e-05"
41 label="mz_tol"
42 help="The m/z tolerance level for the grouping of data points. This value is expressed as the fraction of the m/z value. This value, multiplied by the m/z value, becomes the cutoff level. The recommended value is the machine's nominal accuracy level. Divide the ppm value by 1e6. For FTMS, 1e-5 is recommended." />
43 <param name="baseline_correct" type="float" value="0" label="baseline_correct"
44 help="After grouping the observations, the highest intensity in each group is found. If the highest is lower than this value, the entire group will be deleted. The default value is NA, in which case the program uses a percentile of the height of the noise groups. If given a value, the value will be used as the threshold, and baseline.correct.noise.percentile will be ignored." />
45 <param name="baseline_correct_noise_percentile" type="float" value="0.05"
46 label="baseline_correct_noise_percentile"
47 help="The percentile of signal strength of those EIC that don't pass the run filter, to be used as the baseline threshold of signal strength." />
48 <param name="intensity_weighted" type="boolean" checked="false" truevalue="TRUE" falsevalue="FALSE"
49 label="intensity_weighted"
50 help="Whether to weight the local density by signal intensities in initial peak detection." />
51 </section>
52 </xml>
53
54 <xml name="feature_detection">
55 <section name="feature_detection" title="Feature detection">
56 <param name="shape_model" type="select" display="radio"
57 label="shape_model"
58 help="The mathematical model for the shape of a peak. There are two choices - bi-Gaussian and Gaussian. When the peaks are asymmetric, the bi-Gaussian is better.">
59 <option value="Gaussian">Gaussian</option>
60 <option value="bi-Gaussian" selected="true">bi-Gaussian</option>
61 </param>
62 <param name="BIC_factor" type="float" value="2.0"
63 label="BIC_factor"
64 help="The factor that is multiplied on the number of parameters to modify the BIC criterion. If larger than 1, models with more peaks are penalized more." />
65 <param name="peak_estim_method" type="select" display="radio"
66 label="peak_estim_method"
67 help="The estimation method for the bi-Gaussian peak model. Two possible values: moment and EM.">
68 <option value="moment" selected="true">Moment</option>
69 <option value="EM">EM</option>
70 </param>
71 <param name="min_bandwidth" type="float" optional="true"
72 label="min_bandwidth (optional)"
73 help="The minimum bandwidth to use in the kernel smoother." />
74 <param name="max_bandwidth" type="float" optional="true"
75 label="max_bandwidth (optional)"
76 help="The maximum bandwidth to use in the kernel smoother." />
77 <param name="sd_cut_min" type="float" value="0.01"
78 label="sd_cut_min"
79 help="The minimum standard deviation of a feature to be not eliminated." />
80 <param name="sd_cut_max" type="float" value="500"
81 label="sd_cut_max"
82 help="The maximum standard deviation of a feature to be not eliminated." />
83 <param name="sigma_ratio_lim_min" type="float" value="0.01"
84 label="sigma_ratio_lim_min"
85 help="The lower limit of the believed ratio range between the left-standard deviation and the right-standard deviation of the bi-Gaussian function used to fit the data." />
86 <param name="sigma_ratio_lim_max" type="float" value="100"
87 label="sigma_ratio_lim_max"
88 help="The upper limit of the believed ratio range between the left-standard deviation and the right-standard deviation of the bi-Gaussian function used to fit the data." />
89 <param name="component_eliminate" type="float" value="0.01"
90 label="component_eliminate"
91 help="In fitting mixture of bi-Gaussian (or Gaussian) model of an EIC, when a component accounts for a proportion of intensities less than this value, the component will be ignored." />
92 <param name="moment_power" type="float" value="1"
93 label="moment_power"
94 help="The power parameter for data transformation when fitting the bi-Gaussian or Gaussian mixture model in an EIC." />
95 </section>
96 </xml>
97
98 <xml name="peak_alignment">
99 <section name="peak_alignment" title="Peak Alignment">
100 <param name="align_chr_tol" type="float" optional="true"
101 label="align_chr_tol (optional)"
102 help="The retention time tolerance level for peak alignment. The default is NA, which allows the program to search for the tolerance level based on the data." />
103 <param name="align_mz_tol" type="float" optional="true"
104 label="align_mz_tol (optional)"
105 help="The m/z tolerance level for peak alignment. The default is NA, which allows the program to search for the tolerance level based on the data. This value is expressed as the percentage of the m/z value. This value, multiplied by the m/z value, becomes the cutoff level." />
106 <param name="max_align_mz_diff" type="float" value="0.01"
107 label="max_align_mz_diff"
108 help="As the m/z tolerance is expressed in relative terms (ppm), it may not be suitable when the m/z range is wide. This parameter limits the tolerance in absolute terms. It mostly influences feature matching in higher m/z range." />
109 </section>
110 </xml>
111
112 <xml name="weak_signal_recovery">
113 <section name="weak_signal_recovery" title="Weak Signal Recovery">
114 <param name="recover_mz_range" type="float" optional="true"
115 label="recover_mz_range (optional)"
116 help="The m/z around the feature m/z to search for observations. The default value is NA, in which case 1.5 times the m/z tolerance in the aligned object will be used." />
117 <param name="recover_chr_range" type="float" optional="true"
118 label="recover_chr_range (optional)"
119 help="The retention time around the feature retention time to search for observations. The default value is NA, in which case 0.5 times the retention time tolerance in the aligned object will be used." />
120 <param name="use_observed_range" type="boolean" checked="true" truevalue="TRUE" falsevalue="FALSE"
121 label="use_observed_range"
122 help="If the value is true, the actual range of the observed locations of the feature in all the spectra will be used." />
123 <param name="recover_min_count" type="integer" value="3"
124 label="recover_min_count"
125 help="The minimum number of raw data points to be considered as a true feature." />
126 </section>
127 </xml>
128
129 <token name="@GENERAL_HELP@">
130 apLCMS is a software which generates a feature table from a batch of LC/MS spectra. The m/z and retention time
131 tolerance levels are estimated from the data. A run-filter is used to detect peaks and remove noise.
132 Non-parametric statistical methods are used to find-tune peak selection and grouping. After retention time
133 correction, a feature table is generated by aligning peaks across spectra. For further information on apLCMS
134 please refer to http://web1.sph.emory.edu/apLCMS.
135 </token>
136
137 <xml name="citations">
138 <citations>
139 <citation type="doi">10.1093/bioinformatics/btp291</citation>
140 <citation type="doi">10.1186/1471-2105-11-559</citation>
141 <citation type="doi">10.1021/pr301053d</citation>
142 <citation type="doi">10.1093/bioinformatics/btu430</citation>
143 </citations>
144 </xml>
145 </macros>