Ed Baker FLS ARCS

Picture of Ed Baker.

Interdisciplinary researcher using sensor networks and acoustics to monitor biodiversity and environments.

GitHub | CV | Media | Social

Latest publications

A Gateway to Nature: The Urban Research Station at London’s Natural History Museum

Catalysts for change: Museum gardens in a planetary emergency

Bioacoustic and Ecoacoustic Data in Audiovisual Core

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

Google Scholar

Co-authorship Cloud

Latest blog posts

All blog posts

Talks

10/2025 - Living Data

22/04/2025 - Urban Research Station

03/03/2025 - Impacts of Urban Noise

22/01/2025 - TDWG Kingston Biodiversity Network

05/12/2024 - NHM x Natural England

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.