Neba
Manage parameters and datasets
- Obtain your parameters from configuration files or command line arguments. Validate them against a structured specification that is easy to write, expandable, and which allows to document every parameter.
- Declare datasets in a flexible way to manage multiple source files and to read and write data easily using different libraries.
Configuration
The configuration framework is:
- strict: parameters are defined beforehand. Any unknown or invalid parameter will raise errors
- structured: parameters can be organized in (nested) sections
- documented: docstrings of parameters are re-used in configuration files, command line help, and static documentation via a plugin for Sphinx
The parameters values can be retrieved from configuration files (TOML, YAML, Python files, JSON), and from the command line.
The framework is based on the existing traitlets library. It allows type-checking, arbitrary value validation and "on-change" callbacks. This package extends it to allow nesting. The objects containing parameters are significantly extended to ease manipulation.
Here is a simple example project:
from neba.config import Application, Section
from traitlets import Enum, Float, List, Unicode
class App(Application):
"""The application will retrieve and store parameters."""
result_dir = Unicode("/data/results", help="Directory containing results")
class model(Section):
"""A nested section."""
coefficients = List(Float(), [0.5, 1.5, 10.0], help="Some coefficients for computation.")
style = Enum(["serial", "parallel"], "serial", help="Only some values are accepted.")
app = App()
print(app.model.style)
Parameters from the example above could be retrieved from the command line with --result_dir "./some_dir" --model.coefficients 0 2.5 10. The application can generate a configuration file, for instance in TOML:
# result_dir = "/data/results"
# ----------
# result_dir (Unicode) default: "/data/results"
# Directory containing results
[model]
# A nested section.
# coefficients = [0.5, 1.5, 10.0]
# ------------
# model.coefficients (List[Float]) default: [0.5, 1.5, 10.0]
# Some coefficients for computation
# style = "serial"
# -----
# model.style (Enum) default: "serial"
# Accepted values: ['serial', 'parallel']
# Only some values are accepted
Data management
Neba tries to ease the creation and management of multiple datasets with different file formats, structures, etc. One dataset can have with multiple source files selected via glob patterns, loaded into pandas, while another could have xarray load a remote data-store.
Each new dataset is specified by creating a subclass of DataInterface which
can then be re-used in various scripts to read or write data easily. The
interface contains interchangeable modules that are tasked with retrieving
data locations, loading and writing data. Their behavior can depend on
parameters held by the interface.
Here is an example of an interface where multiple files are found with a glob pattern, and fed into Xarray:
from neba.data import DataInterface, GlobSource, ParametersDict
from neba.data.xarray import XarrayLoader
class SST(DataInterface):
# store parameters with a simple dict
Parameters = ParametersDict
# load data using xarray
Loader = XarrayLoader
Loader.open_mfdataset_kwargs = dict(parallel=True)
# find files on disk using glob
class Source(GlobSource):
def get_root_directory(self):
# we use the parameters of the interface instance
root = self.parameters["data_dir"]
# this will automatically be joined into a path
return [root, "SST"]
def get_filename_pattern(self):
return f"{self.parameters['year']}/SST_*.nc*"
di = SST(year=2000, data_dir="/data")
sst = di.get_data()
We used the parameters and loader modules as is, but we configured the source module for our needs.
Documentation
https://neba.readthedocs.io/en/latest/
Requirements
- Python >= 3.11
- traitlets >= 5.13
- Levenshtein >= 0.27
Installation
From PyPI:
pip install neba
From source:
git clone https://github.com/Descanonge/neba
cd neba
pip install -e .
or
pip install -e https://github.com/Descanonge/neba.git#egg=neba
Metadata
Release files for neba 0.2.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 | |
|---|---|---|---|
| neba-0.2.0.tar.gz | 128.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| neba-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 208.0 kB
Release files / neba-0.2.0.tar.gz
| Download URL | neba-0.2.0.tar.gz |
|---|---|
| Size | 128.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf4d1f0deb5a2c68caa83882c03e52beb66a5fc56d18ad7dd14fdbbde7ce6e91
|
|
BLAKE2b-256 checksum How to use checksums |
30146a3eb1785def604f6ef3a997224b66190daa6f15f4edc0d0026fa909495b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 26, 2026.
Transparency logRelease files / neba-0.2.0-py3-none-any.whl
| Download URL | neba-0.2.0-py3-none-any.whl |
|---|---|
| Size | 80.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
667340b4163e65d09cbea51e64a52b213b091e0eff9bc03821eae364015e42ab
|
|
BLAKE2b-256 checksum How to use checksums |
97122b520295fdd24dba983283011056fa7ebf6cc2e49cb4e04d5b01dc9c7b73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 26, 2026.
Transparency log