find_peaks — ONED `signal` op

• Data kinds: signal → indices

• Call: import fullseye as fs; fs.ledger.find_peaks(x, height=None, distance=None) (to call the implementation directly, import dsp; dsp.find_peaks(x, height=None, distance=None); from the registry, ops1d.get("find_peaks"))

Usage

Peak indices (scipy.signal.find_peaks) — impacts / defect echoes.

References (sample data, literature)

• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).

• Operator provenance and references — the sources of the research/methods this op family came from.

• The canonical algorithm (author, year) and its uses are named in the family usage guide above.

Runnable examples (verified samples that actually call this op)

• poc_multibeam_bathymetry — py -3.11 examples/poc_multibeam_bathymetry.py

• poc_tree_ring_dendro — py -3.11 examples/poc_tree_ring_dendro.py

• poc_web_roll_periodicity — py -3.11 examples/poc_web_roll_periodicity.py

Ops the type connects to (they accept `indices` as input)

peak_subbin

Same category (`signal`)

lowpass · highpass · bandpass · envelope · rms · local_std · quantize · companding_mu_law

*Provenance: dsp.py — ONED operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

find_peaks — ONED signal op