Skip to content

peak_metrics(bridge_dropouts=k) and a public bridge_dropouts() - #19

Merged
lfu46 merged 1 commit into
mainfrom
peak-metrics-bridge
Oct 11, 2026
Merged

lfu46 merged 1 commit into
mainfrom
peak-metrics-bridge

Conversation

@lfu46

@lfu46 lfu46 commented Oct 11, 2026

Copy link
Copy Markdown
Owner

peak_metrics(bridge_dropouts=k) and a public bridge_dropouts()

…aries agree with find_peaks

find_peaks bridged one-scan dropouts; peak_metrics did not, so on the same
zero-filled trace the enclosing peak ended at the first empty scan while the peak
list ran through it. On NGlycoM012 F21 that was most of the "partial overlap"
between the QC's peak and IonQuant's feature (880 of 1,354: IonQuant's wider
feature held our apex, our dropout-cut peak missed its apex).

bridge_dropouts(intensity, max_gap) is the one implementation both use. With
bridge_dropouts > 0 every peak_metrics value comes from the bridged trace except
n_signal, which counts scans with the ion in the original. Default 0 is R.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lfu46
lfu46 merged commit d6367fb into main Oct 11, 2026
2 checks passed
@lfu46
lfu46 deleted the peak-metrics-bridge branch October 11, 2026 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant