BAEC Model Generator SDK
Python SDK to create Model Generators and add them into the BAEC platform.
This repository is created by CEMS BV.
Installation
To install a package in this repository run:
$ pip install baec
ENV VARS
To use baec with FitCore to fit and predict settlements, add the follow ENV vars to your environment. Or provide them when asked.
* NUCLEI_TOKEN
- Your NUCLEI user token
You can obtain your NUCLEI_TOKEN on NUCLEI.
Go to personal-access-tokens and create a new user token.
GUI
set -a; source ./*.env; set +a
marimo edit ./notebooks/gui_notebook.py
#marimo run ./notebooks/gui_notebook.py
#marimo export html-wasm ./notebooks/gui_notebook.py -o build/marimo --mode run
Contribution
Environment
We recommend developing in Python 3.12 with a clean virtual environment (using virtualenv or conda), installing the requirements from the requirements.txt file:
Example using virtualenv and pip to install the dependencies in a new environment .env on Linux:
python -m venv .env
source .env/bin/activate
python -m pip install --upgrade pip setuptools
uv pip install -r requirements.txt
uv pip install -e .
Documentation
Build the docs:
python -m pip install --upgrade pip setuptools
uv pip install -r requirements.txt
uv pip install .
sphinx-build -b html docs public
Format
We format our code with black and isort.
black --config "pyproject.toml" src/baec tests example
isort --settings-path "pyproject.toml" src/baec tests example
Lint
To maintain code quality we use the GitHub super-linter.
To run the linters locally, run the run_super_linters.sh bash script from the root directory.
UnitTest
Test the software with the use of coverage:
set -a; source ./*.env; set +a
python -m pip install --upgrade pip setuptools
uv pip install -r requirements.txt
uv pip install -e .
coverage run -m pytest
Requirements
Requirements are autogenerated by the uv command with python 3.13
Install uv with:
curl -LsSf https://astral.sh/uv/install.sh | sh
Generate requirements.txt file with:
uv pip compile --python-version 3.13 --extra=test --extra=docs --extra=aws --extra=gui --output-file=requirements.txt pyproject.toml
Update the requirements within the defined ranges with:
uv pip compile --python-version 3.13 --upgrade --extra=test --extra=docs --extra=aws --extra=gui --output-file=requirements.txt pyproject.toml
Metadata
Release files for baec 0.2.2
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 |
|---|---|---|---|---|
| baec-0.2.2.tar.gz | 30.0 kB | With provenance | Details for baec-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| baec-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for baec-0.2.2-py3-none-any.whl |
Total release size: 63.1 kB
Release files / baec-0.2.2.tar.gz
| Download URL | baec-0.2.2.tar.gz |
|---|---|
| Size | 30.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
998e6d00dfd1463f6d753f87e18f0726b96ff80d8bf4b548c7d6879445a83eb6
|
|
BLAKE2b-256 checksum How to use checksums |
76df61b74bdb9c2991599ee541325a58da0c4efdb78cdccafcb3ab30a49787dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 2, 2025.
Transparency logRelease files / baec-0.2.2-py3-none-any.whl
| Download URL | baec-0.2.2-py3-none-any.whl |
|---|---|
| Size | 33.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0874f354468e066e1b71e93dfa76f5a45bbe8c4c9ed0b530d248f32a74e03c6d
|
|
BLAKE2b-256 checksum How to use checksums |
5010bf1c3b79613a1c2eb6a84c8202678352df14fb1a2d6983c1906095728315
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 2, 2025.
Transparency logSecurity for baec 0.2.2
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 baec-0.2.2.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 Sep 2, 2025.
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.