Installation

There are three ways to install ctddump. Pick the first one that applies:

Prebuilt binary

Each release ships an archive per platform. It contains the ctddump executable with HDF5 and netCDF built in, so no Rust toolchain and no system libraries are required:

Download, extract, and put the binary somewhere on your PATH:

VERSION=v0.27.0
TARGET=x86_64-unknown-linux-gnu

curl -LO "https://github.com/AIQC-Hub/ctddump/releases/download/$VERSION/ctddump-$VERSION-$TARGET.tar.gz"
tar -xzf "ctddump-$VERSION-$TARGET.tar.gz"
cd "ctddump-$VERSION-$TARGET"

./ctddump --version

To install it for your user, move it onto your PATH:

mkdir -p ~/.local/bin
mv ctddump ~/.local/bin/

If ctddump is still not found afterwards, ~/.local/bin is not on your PATH; add export PATH="$HOME/.local/bin:$PATH" to your shell profile.

Every archive is listed in SHA256SUMS on the same release page. To verify a download before trusting it:

curl -LO "https://github.com/AIQC-Hub/ctddump/releases/download/$VERSION/SHA256SUMS"
sha256sum -c SHA256SUMS --ignore-missing

What else is in the archive

Alongside the binary are the helper scripts, plus README.md, LICENSE, and CHANGELOG.md. The four pipeline scripts (convert_data.sh, clean_data.sh, dedup_data.sh, summary_data.sh) need only ctddump on your PATH, so they work as soon as the step above is done. Three others call external tools that are not bundled and must be installed separately: download_data.sh needs copernicusmarine, summary_site.sh needs mdbook, and fetch_test_data.sh needs gh and unzip.

The scripts are bash, so on Windows they need WSL or Git Bash.

System dependencies

The two routes below compile ctddump themselves and link the HDF5 C library, so the development headers must be installed first. (The prebuilt binaries above need none of this.)

# Ubuntu / Debian
sudo apt-get install libhdf5-dev libnetcdf-dev

# macOS (Homebrew)
brew install hdf5

Install from crates.io

With the system dependencies in place, install the published crate:

cargo install ctddump

This builds the binary and puts it in ~/.cargo/bin, which is normally already on your PATH. Check it works:

ctddump --help

If the build stops with “A system version of libnetcdf could not be found”, the development headers are missing or are somewhere the build script does not look. Install them as shown above, or point at them explicitly:

NETCDF_DIR=/path/to/netcdf HDF5_DIR=/path/to/hdf5 cargo install ctddump

Failing that, the static-netcdf feature builds HDF5 and netCDF from source instead of looking for system ones. It is much slower but needs no headers:

cargo install ctddump --features static-netcdf

Build from source

To work on ctddump itself, or to run a version that is not published yet:

git clone https://github.com/AIQC-Hub/ctddump.git
cd ctddump
cargo build --release

The binary is placed at target/release/ctddump. Copy it somewhere on your PATH (or run it directly) and check it works:

ctddump --help

Every command and subcommand supports -h / --help, so you can always discover the available options interactively:

ctddump convert --help
ctddump batch convert nrt_ar --help

Note: On systems with HDF5 ≤ 1.10 you may see harmless HDF5-DIAG messages in the output. The data is read correctly and results are unaffected.