batdetect2/docs/source/explanation/preprocessing-consistency.md
mbsantiago 67aee0b79c
Some checks failed
CI / Checks (push) Has been cancelled
Docs Pages / Build Docs (push) Has been cancelled
CI / Tests (Python ${{ matrix.python-version }}) (3.10) (push) Has been cancelled
CI / Tests (Python ${{ matrix.python-version }}) (3.11) (push) Has been cancelled
CI / Tests (Python ${{ matrix.python-version }}) (3.12) (push) Has been cancelled
Docs Pages / Deploy Docs (push) Has been cancelled
Update structure
2026-06-02 13:42:05 +01:00

1.0 KiB

Preprocessing consistency

Preprocessing consistency is one of the biggest factors behind stable model performance.

Why consistency matters

The detector is trained on spectrograms produced by a specific preprocessing pipeline. If inference uses different settings, the model can see a shifted input distribution and performance may drop.

Typical mismatch sources:

  • sample-rate differences,
  • changed frequency crop,
  • changed STFT window/hop,
  • changed spectrogram transforms.

Practical implication

When possible, keep preprocessing settings aligned between:

  • training,
  • evaluation,
  • deployment inference.

If you intentionally change preprocessing, treat this as a new experiment and re-validate on reviewed local data.

  • Configure audio preprocessing: {doc}../how_to/data/configure-audio-preprocessing
  • Configure spectrogram preprocessing: {doc}../how_to/data/configure-spectrogram-preprocessing
  • Preprocessing config reference: {doc}../reference/configs/data/preprocessing-config