Ed Baker FLS ARCS

Picture of Ed Baker.

I am an interdisciplinary researcher investigating how technology can be used to monitor biodiversity, in particular using bioacoustic and ecoacoustic approaches.

GitHub Profile | CV | Media

Latest publications

Good practice guidelines for long-term ecoacoustic monitoring in the UK

Google Scholar

Talks

08/11/2024 - Digital Dimensions of Nature Recovery

05/10/2024 - BNA Encaenia

04/10/2024 - Soundings: The River

04/09/2024 - TDWG 2024

11/07/2024 - Ecoacoustic Congress

All talks

Notes

Prophalangopsis obscura

Linux audio recipes

Acoustics figures

SANE defaults

All notes

Some thoughts on:

SANE defaults

The default behaviour of functions, APIs, applications, etc is often specified or designed to be ‘sane’ - but does this actually mean? Use the SANE default acronym.

Simple

The default options should give usable and useful output for the majority of use cases. Little-used functionality is for non-default behaviours.

Aligned

Align default values both internally and externally. All functions in a package should have consistent and compatible default values. If there is consistency in prevailing usage externally, follow it.

Neat

The default options should be neat and tidy. This applies whether the goal is a visualisation, data, a composition of functions, etc.

Expected

Many disciplines have expected norms. If your code reflects these disciplines then use the expected norms. Follow the principle of least surprise.