Pelagos-py
Pelagos-py provides a flexible, modular pipeline framework for defining, executing, and visualising multi-step data-processing workflows for oceanographic data.
Each pipeline is composed of a series of steps that are automatically built from a central user-defined YAML configuration file. As Pelagos-py only depends on the config file to construct a pipeline, processing can be easily reproduced by others through sharing of configs.
Documentation
The documentation for this package is available here.
Please note that the documentation is still under construction.
Overview
The Pipeline class orchestrates the flow of data through a sequence of modular “steps.”
Each step performs a specific processing task (e.g., data loading, quality control, profile detection, export).
Key characteristics:
| Component | Description |
|---|---|
| Configuration-driven | Users define the workflow in a YAML file describing each step, its parameters, and diagnostics options. |
| In-build Quality Control | Pre-build quality control tests can be specified in the config by the user to flag bad data. |
| Diagnostics | Where possible, data is can be visualized to see the effect of each component of the pipeline. |
Installation
Pelagos-py is not yet and installable package, so for the moment you have to make a local copy to run it:
git clone https://github.com/NOC-OBG-Autonomy/pelagos-py.git
cd pelagos-py
# create/activate a virtual environment
pip install -e .
See Getting Started for more details.
How to run
-
Initialization
Import the 'Pipeline' class and create a pipeline using your config (see below for example)from pelagos_py.pipeline import Pipeline pipeline = Pipeline(config_path="my_pipeline.yaml")
-
Pipeline Execution
Running the pipeline executes each step defined by the config in orderresults = pipeline.run()
-
Diagnostics & Visualization
Steps can optionally include diagnostic plots or summaries by setting:diagnostics: true
-
Exporting Pipeline Configuration
The entire pipeline configuration can be exported to a YAML file for reproducibility:pipeline.export_config("exported_pipeline.yaml")
🧩 Example Configuration
An example YAML configuration for a simple pipeline. See examples/notebooks/pipeline_demo.ipynb for a full demo.
# Pipeline Configuration
pipeline:
name: Example CTD Processing Pipeline
description: A pipeline for processing CTD data
visualisation: false
steps:
- name: Load OG1
parameters:
file_path: ../examples/data/OG1/Nelson_646_R.nc # Path to the input NetCDF file
diagnostics: false
- name: Derive CTD
parameters:
to_derive: [
DEPTH,
PRAC_SALINITY,
ABS_SALINITY,
CONS_TEMP,
DENSITY
]
diagnostics: false
- name: "Data Export"
parameters:
export_format: "netcdf"
output_path: "../examples/data/OG1/Nelson_646_R_Processed.nc"
🔁 Extending the Pipeline
A full breakdown can be found here: Developer Guide.
License
Copyright 2025-2026 The National Oceanography Centre and contributors.
Metadata
Release files for pelagos-py 0.0.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 | Provenance | Actions |
|---|---|---|---|---|
| pelagos_py-0.0.0.tar.gz | 227.6 kB | With provenance | Details for pelagos_py-0.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pelagos_py-0.0.0-py3-none-any.whl | Python 3 | none | any | Details for pelagos_py-0.0.0-py3-none-any.whl |
Total release size: 364.0 kB
Release files / pelagos_py-0.0.0.tar.gz
| Download URL | pelagos_py-0.0.0.tar.gz |
|---|---|
| Size | 227.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a397a4dde0c37d717dcc5b3eee1ac40e713f22626566fa17a0083224eee8991d
|
|
BLAKE2b-256 checksum How to use checksums |
f12ff047f6bc2a034a63013fd6c3b7005ef5b586c14d1fd680b8ed1941f1b668
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 11, 2026.
Transparency logRelease files / pelagos_py-0.0.0-py3-none-any.whl
| Download URL | pelagos_py-0.0.0-py3-none-any.whl |
|---|---|
| Size | 136.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1dafa2f61609b685158f3a6ebc186fa76c72c6a2fc2c5ed22d209faf96361400
|
|
BLAKE2b-256 checksum How to use checksums |
9fd23b2026ad9a8814b6888028ec4866d6e22421b9ab661c850fd4705ec066fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 11, 2026.
Transparency logSecurity for pelagos-py 0.0.0
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 2 files in this release have been uploaded with provenance metadata.
Attestation for pelagos_py-0.0.0.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 Jun 11, 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.