generateComponentsOpenMS | R Documentation |
Uses the MetaboliteAdductDecharger utility (see http://www.openms.de) to generate components.
generateComponentsOpenMS(fGroups, ...)
## S4 method for signature 'featureGroups'
generateComponentsOpenMS(
fGroups,
ionization = NULL,
chargeMin = 1,
chargeMax = 1,
chargeSpan = 3,
qTry = "heuristic",
potentialAdducts = NULL,
minRTOverlap = 0.66,
retWindow = 1,
absMzDev = 0.005,
minSize = 2,
relMinAdductAbundance = 0.75,
adductConflictsUsePref = TRUE,
NMConflicts = c("preferential", "mostAbundant", "mostIntense"),
prefAdducts = c("[M+H]+", "[M-H]-"),
extraOpts = NULL
)
## S4 method for signature 'featureGroupsSet'
generateComponentsOpenMS(
fGroups,
ionization = NULL,
chargeMin = 1,
chargeMax = 1,
chargeSpan = 3,
qTry = "heuristic",
potentialAdducts = NULL,
...
)
fGroups |
|
... |
\setsWF Further arguments passed to the non-sets workflow method. |
ionization |
Which ionization polarity was used to generate the data: should be This parameter is not supported for sets workflows, as the ionization will always be detected automatically. |
chargeMin , chargeMax |
The minimum/maximum charge to consider. Corresponds to the
|
chargeSpan |
The maximum charge span for a single analyte. Corresponds to
|
qTry |
Sets how charges are determined. Corresponds to |
potentialAdducts |
The adducts to consider. Should be a Should be a |
minRTOverlap , retWindow |
Sets feature retention tolerances when grouping features. Sets the
|
absMzDev |
Maximum absolute m/z deviation. Sets the |
minSize |
The minimum size of a component. Smaller components than this size will be removed. See note below. |
relMinAdductAbundance |
The minimum relative abundance (‘0-1’) that an adduct should be assigned to
features within the same feature group. See the |
adductConflictsUsePref |
If set to |
NMConflicts |
The strategies to employ when not all neutral masses within a component are equal. Valid options
are: |
prefAdducts |
A |
extraOpts |
Named character vector with extra command line parameters directly passed to
|
This function uses OpenMS to generate components. This function is called when calling generateComponents
with
algorithm="openms"
.
Features that show highly similar chromatographic elution profiles are grouped, and subsequently annotated with their adducts.
A componentsFeatures
derived object.
The returned components are based on so called feature components. Unlike other algorithms, components are first made on a feature level (per analysis), instead of for complete feature groups. In the final step the feature components are converted to 'regular' components by employing a consensus approach with the following steps:
If an adduct assigned to a feature only occurs as a minority compared to other adduct assigments within the
same feature group, it is considered as an outlier and removed accordingly (controlled by the
relMinAdductAbundance
argument).
For features within a feature group, only keep their adduct assignment if it occurs as the most frequent or
is preferential (controlled by adductConflictsUsePref
and prefAdducts
arguments).
Components are made by combining the feature groups for which at least one of their features are jointly present in the same feature component.
Conflicts of neutral mass assignments within a component (i.e. not all are the same) are dealt with.
Firstly, all feature groups with an unknown neutral mass are split in another component. Then, if conflicts still
occur, the feature groups with similar neutral mass (determined by absMzDev
argument) are grouped. Depending
on the NMConflicts
argument, the group with one or more preferential adduct(s) or that is the largest or
most intense is selected, whereas others are removed from the component. In case multiple groups contain
preferential adducts, and ‘>1’ preferential adducts are available, the group with the adduct that matches
first in prefAdducts
'wins'. In case of ties, one of the next strategies in NMConflicts
is tried.
If a feature group occurs in multiple components it will be removed completely.
the minSize
filter is applied.
In a sets workflow the componentization is first performed for each
set independently. The resulting components are then all combined in a componentsSet
object. Note that
the components themselves are never merged. The components are renamed to include the set name from which they were
generated (e.g. "CMP1"
becomes "CMP1-positive"
).
generateComponentsOpenMS uses multiprocessing to parallelize computations. Please see the parallelization section in the handbook for more details and patRoon options for configuration options.
Bielow2010patRoon
generateComponents
for more details and other algorithms.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.