Pelagic
Pelagic runs the classic two-dimensional underwater acoustics models from Python, MATLAB/Octave or the command line, without building the Fortran Acoustics Toolbox:
- BELLHOP: ray traces, eigenrays, arrivals and pressure fields.
- KRAKEN / KRAKENC: real and complex normal modes, plus FIELD pressure.
It reads your existing .env/.flp files or a self-contained JSON case. It
writes the familiar .ray/.arr/.shd/.mod files, structured HDF5, or both.
Results are checked against the official Acoustics Toolbox v2023.5 release.
Install
| You use | Install |
|---|---|
| Python 3.9+ | python -m pip install pelagic |
| MATLAB R2023a+ | Download pelagic-vX.Y.Z.mltbx from Releases and open it in MATLAB |
| GNU Octave 7+ | See Getting started |
| The command line | Download pelagic-vX.Y.Z-<platform> from Releases |
Prebuilt packages cover Windows x64, macOS (Apple silicon and Intel) and Linux (x86-64 and ARM64). Nothing else needs to be installed: HDF5 is built in. To build from source, see CONTRIBUTING.
Quick start
These use munk-tl.json,
deep-water transmission loss. examples/
has 24 cases, from rays and arrivals to elastic seabeds, range-dependent modes
and broadband pulses, each with Python, MATLAB and command-line scripts.
Python
import pelagic as pg
result = pg.bellhop.load("munk-tl.json").run()
pressure = result.field.pressure # complex64, [source, depth, range]
loss_db = result.field.transmission_loss()
result.write_native("results/munk-tl") # .shd and friends, no re-solve
MATLAB / Octave
c = pelagic.bellhop.load('munk-tl.json');
c.frequency_hz = 200;
r = pelagic.bellhop.run(c);
imagesc(r.ranges_m, r.depths_m, 20*log10(abs(squeeze(r.pressure(1,:,:)))));
Command line
pelagic bellhop run munk-tl.json --format both --output results/munk-tl
pelagic kraken run case.env --solver krakenc --output results/case
What it can and cannot do
Pelagic covers a large, tested part of 2D BELLHOP and KRAKEN/KRAKENC, but not every option combination in the Toolbox. Three-dimensional programs (BELLHOP3D, FIELD3D) and BOUNCE table generation are not included. Unsupported input is rejected with a clear error rather than approximated. Before starting a study, check your options against:
Documentation
- Getting started: install, first run and choosing an interface
- Guides: Python · MATLAB/Octave · Command line · HTTP service
- Examples: 24 cases with Python, MATLAB, command-line and HTTP scripts
- Troubleshooting and error codes
- Full documentation index, including file formats and JSON schemas
- Changelog
Questions and bug reports are welcome in Issues. To contribute, start with CONTRIBUTING.
Citing Pelagic
If Pelagic contributes to published work, cite the exact release you used. See CITATION.cff, or use "Cite this repository" on GitHub. Each result also records its Pelagic version and an input hash for reproducibility.
License
Metadata
Release files for pelagic 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pelagic-0.4.1.tar.gz | 2.1 MB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| pelagic-0.4.1-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details |
| pelagic-0.4.1-cp39-abi3-manylinux_2_28_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.28+ x86-64 | Details |
| pelagic-0.4.1-cp39-abi3-manylinux_2_28_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.28+ ARM64 | Details |
| pelagic-0.4.1-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
| pelagic-0.4.1-cp39-abi3-macosx_10_12_x86_64.whl | CPython 3.9 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 8.3 MB
Release files / pelagic-0.4.1.tar.gz
| Download URL | pelagic-0.4.1.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
43ce959bf83821b66a070d3bf15a9429744200389bbfda67ac5084238b9dfd25
|
|
BLAKE2b-256 checksum How to use checksums |
713be6c87fc3e2788be7b6e8fdad763fe03271b813eb1ed23d42cd4fb62c321a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / pelagic-0.4.1-cp39-abi3-win_amd64.whl
| Download URL | pelagic-0.4.1-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
1c41db891e6762f4652a360923816cd926b5f07807bae3a8df4128e9f3433ad2
|
|
BLAKE2b-256 checksum How to use checksums |
9382ebd2cd484f61ccadf7e93a2a6b6204dda92a1ffdab1724c2da6de830a389
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / pelagic-0.4.1-cp39-abi3-manylinux_2_28_x86_64.whl
| Download URL | pelagic-0.4.1-cp39-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.9 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
ac730d82bc765373c92bc9d6afd6102b6504265d04b0663bae9c2576133f7689
|
|
BLAKE2b-256 checksum How to use checksums |
855bb4ad11ef03a40405eed02e1028fa52f1cb24401243fc1a44f1d0531fe2c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / pelagic-0.4.1-cp39-abi3-manylinux_2_28_aarch64.whl
| Download URL | pelagic-0.4.1-cp39-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.9 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
3e7ea643a04de947aa3ed7d37b4f5599502be99de81f404cdffef06c04f746ca
|
|
BLAKE2b-256 checksum How to use checksums |
150a3a2838be99f1b6d3c7e684a3e519a2eebbfe30bc720cc4258e35714e08ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / pelagic-0.4.1-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | pelagic-0.4.1-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1ef5ce5a32df453574cdcb1f5dd546a4324fceb2d518a11f91237b1e0a8d2f82
|
|
BLAKE2b-256 checksum How to use checksums |
38a6b5a561467bd5f96c70ba16cf8feddef085a39aa55748db2a484711714bb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / pelagic-0.4.1-cp39-abi3-macosx_10_12_x86_64.whl
| Download URL | pelagic-0.4.1-cp39-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.9 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
d710d3ba9c10ec6befe6c74936e70e085e599b17424f91f77873db69fa0d4d53
|
|
BLAKE2b-256 checksum How to use checksums |
e23df11f5c57cfca69adc84b49bcc46076115708b84bb12b5adb1c89924cf1dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logSecurity for pelagic 0.4.1
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.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for pelagic-0.4.1.tar.gz
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 Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.