ctdcast
Processing and reporting for shipboard CTD and LADCP data: raw Sea-Bird files → per-cast
netCDF at each stage (read, trim, process/QC) → a compiled profiles.nc aligned with CF and
CCHDO naming → self-contained HTML reports. Built for use at sea: every output works offline,
with no external requests.
Documentation: https://ocean-uhh.github.io/ctdcast/ · example report
Installation
pip install ctdcast
Reading raw .cnv files needs seasenselib (pip install seasenselib). Python 3.10–3.13 is
supported. See the installation notes
for isolated-environment and from-source options.
Quick start
Raw CNV files fresh off the instrument — one command gives station pages, an index and a map:
ctdcast draft /path/to/cnv/ --cruise odb2026 # writes ./ctd_draft/index.html
For the full pipeline — sections, time series, LADCP, the sensor inventory — write a config and process stage by stage:
ctdcast init --interactive # guided config.yaml
ctdcast validate config.yaml # check paths before the first run
ctdcast process config.yaml --stage 1 2 3 profiles
ctdcast run config.yaml # the report; --force rebuilds, --only 42 one cast
ctdcast clock config.yaml diagnoses the acquisition-clock error and prints a paste-ready
processing.clock block. See the quickstart
for the recommended first-cruise workflow, the config reference
and the CLI reference.
To check an installation, run the bundled demo against the committed fixture casts:
ctdcast run config_demo.yaml # writes demo_report/index.html
Python API
import ctdcast
ctdcast.report("ctd_nc", "report", profiles_path="profiles.nc",
groupings_yaml="ctd_groupings.yaml")
See the API reference for process,
stage1, profiles and the full interface.
Acknowledgements
Development of this package started during the Odón de Buen cruise of AEI-DFG DS-MIXSED. DS-MIXSED is funded by the Agencia Estatal de Investigación (AEI) through the PCI 2024 call — projects PCI2024-155022-2 and PCI2024-155084-2 — and the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation) — Projektnummer 541914507.
Development was assisted by Claude Code (Anthropic) and GitHub Copilot code review.
License
MIT License
Metadata
Release files for ctdcast 0.3.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 | |
|---|---|---|---|
| ctdcast-0.3.0.tar.gz | 505.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ctdcast-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 941.5 kB
Release files / ctdcast-0.3.0.tar.gz
| Download URL | ctdcast-0.3.0.tar.gz |
|---|---|
| Size | 505.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c450f98237cb21169fcbd50e7d9b478189c3bbec025bee5d4c4ef30360d9581
|
|
BLAKE2b-256 checksum How to use checksums |
fde3a8833e85128cb65bde05ddac46ec2486468e089c5895781566af80fcba89
|
| 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 Oct 12, 2026.
Transparency logRelease files / ctdcast-0.3.0-py3-none-any.whl
| Download URL | ctdcast-0.3.0-py3-none-any.whl |
|---|---|
| Size | 436.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4c0ef1f081ea05c41e2b4a52a366ce6da8499958c83919ab79f1b0d128e46f81
|
|
BLAKE2b-256 checksum How to use checksums |
f11b44aeac2967090d85765364c29699d74dfa5a45f0bca4ee490e758b140868
|
| 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 Oct 12, 2026.
Transparency log