W: Annotate mass spectra (single-dataset)
Brief description
Annotate selected mass spectra within a single dataset. These could be mass spectra from different masks, clustering results, or all of the above etc. Action will be performed on each processed dataset individually.
Parameters
Spectrum source (type - string)
Source of the mass spectra.
Molecule type (type - string)
Molecule type to annotate.
Database (type - array)
Database to use for annotation.
Adducts (type - array)
Adducts to use for annotation.
PPM limit (type - number)
PPM limit for annotation.
m/z min (type - number)
Minimum m/z to annotate.
m/z max (type - number)
Maximum m/z to annotate.
Automatic SNR (type - boolean)
Automatically determine SNR value which will use knee-based method to estimate appropriate SNR. This will also override the 'Min. peaks' parameter.
SNR (type - number)
Signal-to-noise ratio. Value of 0 will enable automatic SNR selection which will use knee-based method to estimate appropriate SNR. This will also override the min_peaks parameter.
Min. peaks (type - integer)
Minimum number of peaks.
Deisotope (type - boolean)
Deisotope spectra.
No. of decoys (type - integer)
Number of decoys to use for FDR estimation.
FDR mode (type - string)
FDR mode to use for annotation.
Help
Annotine offers two FDR methods, one based on mass spectra and one based on ion images.
The spectrum method is substantially faster (around 100-500x!) but might be considered slightly less robust because it uses only the mass spectral information when estimating FDR.
The image method uses ion images to estimate FDR which is more akin to Metaspace approach but it is substantially slower.
We recommend trying out the spectrum method first and can always try again using the image method if you are not satisfied with the results.
Enable filtering rules (type - boolean)
Enable filtering rules that remove unlikely lipid classes or lipid+adduct combinations.
Resolution (type - integer)
Resolution of the data - this setting might change how we generate theoretical isotope patterns.
Export peaklist (type - boolean)
Export peaklist to CSV file after annotation.
Filename (type - string)
Filename to use for the object.
Diagnostic information (type - boolean)
Generate diagnostic information which might with figuring out why certain annotations are not getting picked up or if there are issues with the data.
Warning
You shouldn't enable this option unless you are having issues with the annotations. This will
generate many more figures, many of which might not be useful. This option has substantial computational
cost, especially if the number of annotations is high!
Plot style (type - array)
Style of the generated figures.
Export images as (type - string)
Export figures as image or within a single PDF or PowerPoint.
Dependencies (other tasks that this task might depend on)
| Depends on | Required/Optional |
|---|---|
| P: Average mass spectrum (single-dataset) | required |
| W: Average mass spectrum / mask (single-dataset) | required |
| W: Average mass spectrum / cluster (single-dataset) | required |
Attributes
| Attribute | Value | Description |
|---|---|---|
| Multiple allowed | True | Allow multiple instances of this task in a workflow. |
| Task can fail | False | Task is optional and can fail without causing the entire workflow to fail. |
| Step can fail | True | Sub-tasks of this task can fail without causing the entire task (and workflow) to fail. |
| Requires ion mobility | False | Task requires ion mobility data. |
| Task can fail (with ion mobility) | False | This task uses ion mobility data but it is allowed to fail, without causing the entire workflow to fail. |
| Allowed in reference dataset | True | Task is to be performed on a 'reference' dataset. This will allow for multiple analyses to be performed on the same dataset, without cluttering or duplicating certain tasks (unused at the moment). |