|
1 | 1 | SmartPeak Features
|
2 | 2 | =============================================================================
|
3 | 3 |
|
4 |
| -SmartPeak provides a plethora of features for analytical chemistry data processing. An incomplete set of features are described below. |
| 4 | +SmartPeak provides a plethora of features for analytical chemistry data processing. |
| 5 | +An incomplete set of features are described below. |
5 | 6 |
|
6 | 7 | Audit trail and data provenance
|
7 | 8 | -----------------------------------------------------------------------------
|
8 | 9 |
|
9 |
| -A complete record of all actions and data processing steps invoked by the user is often required in regulated environments. In addition, for debugging, it is useful to have a record of all actions the software has taken. |
| 10 | +A complete record of all actions and data processing steps invoked by the user is often required in regulated environments. |
| 11 | +In addition, for debugging, it is useful to have a record of all actions the software has taken. |
10 | 12 |
|
11 | 13 | SmartPeak records all actions and data processing steps for audit trail and debugging purposes at two levels: 1) an application log, and 2) feature log.
|
12 | 14 |
|
@@ -292,41 +294,54 @@ Optimize workflow step algorithm parameters
|
292 | 294 | Usage
|
293 | 295 | ~~~~~
|
294 | 296 |
|
295 |
| -.. todo:: |
296 |
| - Describe the usage. |
| 297 | +The algorithms behind each workflow step can be optimized and fine-tuned for each particular use case. |
| 298 | +The parameters used in a workflow can be viewed and modified through ``View | Workflow settings | Parameters``. |
297 | 299 |
|
298 |
| -Example |
299 |
| -~~~~~~~ |
| 300 | +.. image:: ../images/workflow_parameters_view.png |
300 | 301 |
|
301 |
| -.. todo:: |
302 |
| - Provide an example. |
| 302 | +The parameters that have been specified by the user are shown in white, defaults not set by the user are shown in grey, and unused paramters are shown in blue. |
| 303 | +Hovering over the name of the parameter displays a tooltip that provides a brief explanation of what the paramter does. |
303 | 304 |
|
304 |
| -Debug feature picking, selection, and filtering (and acquisition methods) |
305 |
| ------------------------------------------------------------------------------ |
| 305 | +.. image:: ../images/workflow_parameters_edit.png |
306 | 306 |
|
307 |
| -Usage |
308 |
| -~~~~~ |
| 307 | +Examples of optimized parameters for different acquisition methods are provided in the :ref:`tutorials`. |
309 | 308 |
|
310 |
| -.. todo:: |
311 |
| - Describe the usage. |
| 309 | +Example 1: Debug feature finding, selection, and filtering |
| 310 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
312 | 311 |
|
313 |
| -Example |
314 |
| -~~~~~~~ |
| 312 | +The first part of developing an automated data processing method is to optimize the feature finding, selection, and filtering paramters. |
| 313 | +We recommend using the bulk statistics in ``View | Statistics`` and visualizations provided in ``View | Chromatograms`` to gain intuition about how each of the parameter changes affect feature finding, selection, and filtering. |
| 314 | +We also recommend using the feature reports in ``Actions | Report`` and exporting the long (Feature DB) or matrix (Feature Table) formats to get a more fine-grained view of how each of the parameter changes affect feature finding, selection, and filtering. |
315 | 315 |
|
316 |
| -.. todo:: |
317 |
| - Provide an example. |
| 316 | +**Feature Finding** |
| 317 | +The feature finding step entails (optionally) smoothing and integrating the features (also called peaks or convex hulls) in 2D (e.g., XIC chromatogram of intensity vs time or XIC spectrum of time vs m/z) or 3D (e.g., intensity vs time vs m/z). |
| 318 | +Note that multiple features are found in any given chromatogram or spectrum. |
| 319 | +Additional steps including baseline normalizing, windowing, etc. are available to preprocess the data before running the feature finding step. |
| 320 | +For single reaction monitoring (SRM/MRM) or data independent (DIA) methods, the ``MRMFeatureFinderScoring`` functions are the ones to be manipulated. |
| 321 | +For data dependent (DDA) or full scan methods, the ``FeatureFindingMetabo``, ``ElutionPeakDetection``, ``MassTraceDetection`` functions are the ones to be manipulated. |
| 322 | +*Check that all features are being found and properly integrated prior to moving on to Feature Selection!* |
318 | 323 |
|
319 |
| -Enable automated QC/QA of workflows |
320 |
| ------------------------------------------------------------------------------ |
| 324 | +**Feature Selection** |
| 325 | +The feature selection step entails aligning the retention time of features and selecting the most probable feature. |
| 326 | +Feature alignment is one of the biggest bottlenecks in targeted and non-targeted chromatography-based mass spectrometry. |
| 327 | +SmartPeak provides an advanced feature alignment algorithm that is based on relative retention time instead of absolute retention time to allow for accurate feature alignment even when retention time shifts of several minutes occur. |
| 328 | +For single reaction monitoring (SRM/MRM) or data independent (DIA) methods, the ``MRMFeatureSelector.schedule_MRMFeatures_qmip` functions are the ones to be manipulated. |
| 329 | +*Check that all features are being properly selected prior to moving on to Feature Filtering!* |
321 | 330 |
|
322 |
| -Usage |
323 |
| -~~~~~ |
| 331 | +**Feature Filtering** |
| 332 | +The feature filtering step removes features from a chromatogram or spectrum based on user specified criteria. |
| 333 | +Feature filtering can be performed before or after feature selection. |
| 334 | +The feature filters are specified in the ``ComponentGroupFilters.csv`` and ``ComponentFilters.csv`` files for filtering at the ComponentGroup (TransitionGroup in SRM) and Component (Tansition in SRM) levels, respectively. |
| 335 | +It is our experience that if the feature finding and selection parameters have been well optimized, the feature filtering step is not needed. |
| 336 | +However, there are use cases where there are only a few components (transitions in SRM) that make optimal feature selection difficult, and feature filtering can come in handy. |
324 | 337 |
|
325 |
| -.. todo:: |
326 |
| - Describe the usage. |
| 338 | +Example 2: Debug automated QC/QA of workflows |
| 339 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
327 | 340 |
|
328 |
| -Example |
329 |
| -~~~~~~~ |
| 341 | +The next part of developing an automated data processing method is to optimize the QC/QA reporting metrics. |
| 342 | +We recommend using the feature reports in ``Actions | Report`` and exporting the long (Feature DB) or matrix (Feature Table) formats after checking ``QC_transition_message``, ``QC_transition_score``, ``QC_transition_group_message``, and ``QC_transition_group_score`` to get a more fine-grained view of how each of the parameter changes affect feature finding, selection, and filtering. |
330 | 343 |
|
331 |
| -.. todo:: |
332 |
| - Provide an example. |
| 344 | +**Feature QC** |
| 345 | +The feature QC step flags features from a chromatogram or spectrum based on user specified criteria (same algorithm and similar format to Feature Filtering above). |
| 346 | +Feature QC can be performed at anytime during a data processing workflow. |
| 347 | +The feature QCs are specified in the ``ComponentGroupQCs.csv`` and ``ComponentQCss.csv`` files for QC/QA at the ComponentGroup (TransitionGroup in SRM) and Component (Tansition in SRM) levels, respectively. |
0 commit comments