Event detection: Difference between revisions
Appearance
Shorten visible site name to Wiki Tag: Reverted |
Restore visible brand name to Nanopore Wiki Tag: Manual revert |
||
| Line 3: | Line 3: | ||
<!--T:1--> | <!--T:1--> | ||
[[File:Detection pics scipy signal find peaks.svg|thumb|right|320px|Peak or event detection concepts support nanopore signal analysis. Source: Wikimedia Commons, CC BY-SA 4.0.]] | [[File:Detection pics scipy signal find peaks.svg|thumb|right|320px|Peak or event detection concepts support nanopore signal analysis. Source: Wikimedia Commons, CC BY-SA 4.0.]] | ||
'''Event detection''' is part of the Wiki learning path. Event detection identifies real blockade or signal-change events in nanopore recordings and extracts comparable features from them. | '''Event detection''' is part of the Nanopore Wiki learning path. Event detection identifies real blockade or signal-change events in nanopore recordings and extracts comparable features from them. | ||
<!--T:2--> | <!--T:2--> | ||
Revision as of 11:48, 30 June 2026
Event detection is part of the Nanopore Wiki learning path. Event detection identifies real blockade or signal-change events in nanopore recordings and extracts comparable features from them.
Core concepts
- Detection thresholds should be tied to baseline and local noise.
- Event boundaries affect dwell time, area, and shape metrics.
- Weak, overlapping, or multi-level events need careful validation.
- False positives can arise from noise, drift, bubbles, clogging, and analysis settings.
Event detection workflow
| Step | Description |
|---|---|
| 1 | Annotate experimental phases and sample addition times. |
| 2 | Estimate local baseline and noise. |
| 3 | Set candidate thresholds and minimum duration rules. |
| 4 | Merge, split, or reject events using documented criteria. |
| 5 | Export event tables and plots for review. |
Typical applications
- Quantifying blockade depth and dwell time.
- Comparing samples or pore variants.
- Building training data for classification models.
Common pitfalls
- Using one threshold for recordings with strong drift.
- Failing to test false positives on blank controls.
- Treating automated output as correct without visual review.