Blue Pebble
Blue Pebble is a research-oriented simulation framework for underwater acoustic sensing, built as a plugin for Stone Soup. It currently focuses on passive sonar: acoustic propagation modelling, beamforming, detection and multi-target tracking.
Installation
pip install blue-pebble
The package installs as blue-pebble and imports as bluepebble.
Getting Started
Start with the Getting Started tutorial, which simulates a towed array and beamforms, detects and tracks a single target. The documentation also has further tutorials, worked examples and the API reference.
Features
- Towed-array kinematics for the ownship, targets and array elements
- Acoustic propagation, from analytical spreading laws to ray tracing with rtrs
- Environments built from analytical profiles or measured bathymetry and sound-speed data
- Source and noise synthesis, including biological, anthropogenic and ownship noise
- Delay-and-sum and MVDR (Minimum Variance Distortionless Response) beamforming
- CFAR (Constant False Alarm Rate) detection, calibrated from noise or with a fixed threshold
- Detections that feed straight into Stone Soup trackers
Contributing
See CONTRIBUTING.md for the development setup and workflow, and the roadmap for planned extensions.
Citation
If you use Blue Pebble in academic work, please cite the associated conference paper and the software release (via DOI when available).
@inproceedings{wakefield2026sonar,
title={A Sonar Signal Processing Plugin for Stone Soup},
author={Wakefield, Joshua J and Boulton, Finley and Colquitt, Daniel J. and Ralph, Jason F. and Williams, Duncan P.},
booktitle={2026 29th International Conference on Information Fusion (FUSION)},
pages={1--8},
year={2026},
organization={IEEE}
}
Licence
Blue Pebble is released under the MIT licence; see LICENSE and NOTICE.md. Its ray-tracing dependency, rtrs, is also MIT-licensed and installs automatically. The package includes no external data, so users are responsible for complying with the licences of any data they use with it.
Release files for blue-pebble 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| blue_pebble-0.4.0.tar.gz | 323.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| blue_pebble-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 495.2 kB
Release files / blue_pebble-0.4.0.tar.gz
| Download URL | blue_pebble-0.4.0.tar.gz |
|---|---|
| Size | 323.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
acab3cf8cfc60ed3588657da6c11aa3965cf2e373cdaace44e10980e42abaecf
|
|
BLAKE2b-256 checksum How to use checksums |
2f90ed7f2ee795beeca422ae35ba5f7233a6c7567d818770da46aedcd4c5b795
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / blue_pebble-0.4.0-py3-none-any.whl
| Download URL | blue_pebble-0.4.0-py3-none-any.whl |
|---|---|
| Size | 172.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d64d3ca5e1f0f36f564c405d8596c2c66dd8c2cb30e74842298605aa03212cf5
|
|
BLAKE2b-256 checksum How to use checksums |
c44db77baaecdbde68272edfa438285123a57f39f2bbf7da6223f1713b9f635b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log