damast: Creation of reproducible data processing pipelines
The main purpose of this library is to faciliate the reusability of data and data processing pipelines. For this, damast introduces a means to associate metadata with data frames and enables consistency checking.
To ensure semantic consistency, transformation steps in a pipeline can be annotated with allowed data ranges for inputs and outputs, as well as units.
class LatLonTransformer(PipelineElement):
"""
The LatLonTransformer will consume a lat(itude) and a lon(gitude) column and perform
cyclic normalization. It will add four columns to a dataframe, namely lat_x, lat_y, lon_x, lon_y.
"""
@damast.core.describe("Lat/Lon cyclic transformation")
@damast.core.input({
"lat": {"unit": "deg"},
"lon": {"unit": "deg"}
})
@damast.core.output({
"lat_x": {"value_range": MinMax(-1.0, 1.0)},
"lat_y": {"value_range": MinMax(-1.0, 1.0)},
"lon_x": {"value_range": MinMax(-1.0, 1.0)},
"lon_y": {"value_range": MinMax(-1.0, 1.0)}
})
def transform(self, df: AnnotatedDataFrame) -> AnnotatedDataFrame:
lat_cyclic_transformer = CycleTransformer(features=["lat"], n=180.0)
lon_cyclic_transformer = CycleTransformer(features=["lon"], n=360.0)
_df = lat_cyclic_transformer.fit_transform(df=df)
_df = lon_cyclic_transformer.fit_transform(df=_df)
return _df
Pipeline can also be designed with join / merge operations:
class JoinByTimestamp(PipelineElement):
def __init__(self):
pass
@damast.core.describe("Join data for matching timestamp")
@damast.core.input({
"timestamp": {},
"lon": {},
"lat": {},
})
@damast.core.input({
"timestamp": {},
"lat": {},
"lon": {},
"event_type": {}
}, label='other'
)
@damast.core.output({ "event_type": {}})
def transform(self, df: AnnotatedDataFrame, other: AnnotatedDataFrame) -> AnnotatedDataFrame:
other_timestamp = self.get_name('timestamp', datasource='other')
df_timestamp = self.get_name('timestamp')
df.lazyframe = df.join(other.lazyframe, left_on=df_timestamp, right_on=other_timestamp)
return df
For detailed examples, check the documentation at: https://simula.github.io/damast
Installation and Development Setup
Firstly, you will want to create you an isolated development environment for Python, that being conda or venv-based. The following will go through a venv based setup.
Let us assume you operate with a 'workspace' directory for this project:
cd workspace
Here, you will create a virtual environment. Get an overview over venv (command):
python -m venv --help
Create your venv and activate it:
python -m venv damast-venv
source damast-venv/bin/activate
From PyPi
To install the package from pypi use:
pip install damast
Note that machine-learning related elements required additional dependencies, and to install keras and all supported backends (jax, torch, tensorflow) you can use:
pip install damast[ml]
From Source
Clone the repo and install:
git clone https://github.com/simula/damast
cd damast
pip install -e ".[test,dev]"
or alternatively:
pip install damast[test,dev]
Docker Container
If you prefer to work or start with a docker container you can build it using the provided Dockerfile
docker build -t damast:latest -f Dockerfile .
To enter the container:
docker run -it --rm damast:latest /bin/bash
Usage
To get the usage documentation it is easiest to check the published documentation here.
Otherwise, you can also locally generate the latest documentation once you installed the package:
tox -e build_docs
Then open the documentation with a browser:
<yourbrowser> _build/html/index.html
Testing
Install the project and use the predefined default test environment:
tox -e py
Contributing
This project is open to contributions. For details on how to contribute please check the Contribution Guidelines
License
This project is licensed under the BSD-3-Clause License.
Copyright
Copyright (c) 2023-2026 Simula Research Laboratory, Oslo, Norway
Acknowledgments
This work has been derived from work that is part of the T-SAR project Some derived work is mainly part of the specific data processing for the 'maritime' domain.
The development of this library is part of the EU-project AI4COPSEC which receives funding from the Horizon Europe framework programme under Grant Agreement N. 101190021.
Release files for damast 0.3.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| damast-0.3.7.tar.gz | 148.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| damast-0.3.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 322.7 kB
Release files / damast-0.3.7.tar.gz
| Download URL | damast-0.3.7.tar.gz |
|---|---|
| Size | 148.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa77f15adfebae333688c097f5bee025b121948dd0fd5f97ec108ebfb682e55d
|
|
BLAKE2b-256 checksum How to use checksums |
f47a2d9ae9b5e583eb51b599368fc5b972066422556082f350881669decc3775
|
| 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 17, 2026.
Transparency logRelease files / damast-0.3.7-py3-none-any.whl
| Download URL | damast-0.3.7-py3-none-any.whl |
|---|---|
| Size | 174.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11084be01a109a2d4b62622cb974120e7f30a9431c7a3433978c646f680e2c60
|
|
BLAKE2b-256 checksum How to use checksums |
bcb1bb38d4e82e2a642d6c9cc9cf50c026d7a65a244ad87ff72702ea73e074d5
|
| 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 17, 2026.
Transparency log