Skip to main content

⚡ Open-source framework for sequential decision problems in the energy sector

Project description

emflow

⚡ Open-source Python framework for modelling sequential decision problems in the energy sector

License: MIT PyPI version Join us on Slack All Contributors GitHub Repo stars

emflow is an open-source Python framework that enables energy data scientists and modellers to write modular and reproducible energy models that solves sequential decision problems. It is based on both OpenAI Gym (now Gymnasium) and Warran Powell's universal sequential decision framework. emflow lets you:

  • 🛤️ Structure your code as modular and reusable components and adopt the "model first, then solve"-mantra;
  • 🌱 Forumate your problems with datasets, environments and objectives;
  • 🏗️ Build agents, predictors, optimizers and simulators to solve sequential decision problems;
  • 🧪 Run parametrized experiments that generate reproducible results (code, data and parameters); and
  • ➿ Run sweeps for benchmarking, scenario analysis and parameter tuning.

⬇️ Installation  |  📖 Documentation  |  🚀 Try out now in Colab  |  👋 Join Slack Community

The Sequential Decision Loop

emflow allows to model sequential decison problems, where state information $S_t$ is provided, an action $a_t=A^{\pi}(S_t)$ is taken, exogenous information $W_{t+1}$ is revealed, whereby a new state $S_{t+1} = S^M(S_t, a_t, W_{t+1})$ is encountered and a cost/contribution $C(S_t,a_t,W_{t+1})$ can be calculated. The sequential decision loop then repeats until the end of the evaluation/problem time.

Sequential decision loop

The goal is to find an agent policy $\pi$ that maximizes the contribution (or minimizes the cost) over the full time horizon $t \in [0, T]$. Mathematically formulated as:

$$ \begin{equation*} \begin{aligned} \max_{\pi \in \Pi} \quad & \mathbb{E}^{\pi} \bigg[ \sum_{t=0}^T C(S_t,A^{\pi}(S_t),W_{t+1}) \bigg| S_0 \bigg] \ \textrm{s.t.} \quad & S_{t+1} = S^M(S_t,a_t,W_{t+1})\ \end{aligned} \end{equation*} $$

Modules and Components

emflow consists of a set of components that serve as building blocks to create modular and reusable energy models. One of the main dependencies is EnergyDataModel that provides functionality to represent energy systems. The table below gives a summary of the available modules and concepts.

Module Components
🔋 assets All energy asset and concept components defined by EnergyDataModel
🗄️ data Field, Dataset, DataPortal — point-in-time data access with availability semantics (leak-proof by construction)
🧩 problems Problem, IssueSchedule, Objective, metrics (pinball, MAE, RMSE, peak timing, trading revenue)
🌍 envs ForecastEnv, TradingEnv — rolling-origin evaluation on the gymnasium API
🧮 features Lag, Rolling, ForecastField, Calendar — declarative, point-in-time-correct feature specs
🤖 models Model, Predictor, Simulator, Optimizer, Agent
♻️ run Experiment, Result, Verifier, analyzers
🏆 benchmarks Historical competition problems: heftcom2024 (forecasting + trading), gefcom2012/2014/2017, bfcom2018, bigdeal2022

Below is a diagram of the components' relation to each other and how they together enable creation of reproducible results from energy models.

emflow Framework Structure

Framework 6-Step Approach

emflow is about adopting a problem-centric, stepwise approach that follows the "model first, then solve"-mantra. The idea is to first gain a deep problem understanding before rushing to the solution. Or as Albert Einstien expressed it:

"If I had an hour to solve a problem I'd spend 55 minutes thinking about the problem and five minutes thinking about solutions."

Concretely, this means that problems are solved through the following steps:

  1. Define the considered energy system;
  2. Define state, action and exogenous variables;
  3. Create the environment and the transition function;
  4. Define the objective (cost or contribution);
  5. Create the model (simulator, predictor, optimizer and/or agent) to operate in environment; and
  6. Run the sequential decision loop and evaluate performance.

Steps 1-4 are about understanding the problem and steps 5-6 are about creating and evaluating the solution.

Basic Usage

A benchmark problem bundles a dataset, an environment factory, a schedule, an objective and temporal splits. Load one, run a model through an Experiment, and inspect the Result:

import emflow as ef
from emflow.benchmarks.heftcom2024.baseline import BinnedQuantileBaseline

problem = ef.load_problem("heftcom2024:forecasting")   # a real competition
result = ef.Experiment(problem, BinnedQuantileBaseline()).run()

print(result.score)                          # pinball loss on the validation split
print(result.analysis["PersistenceSkill"])   # skill vs the persistence baseline
print(result.rank_against(problem))          # place on the official 2024 leaderboard

Every observation a model sees is served through the point-in-time DataPortal, so look-ahead leakage is impossible by construction — which is what makes the scores trustworthy for agent benchmarking. Untrusted submissions are scored with the Verifier on a held-out split whose labels live in a private repo (see submissions/README.md).

Installation

We recommend installing using a virtual environment like venv, poetry or uv.

Install the stable release:

pip install emflow

Install the latest release:

pip install git+https://github.com/rebase-energy/emflow.git

Install in editable mode for development:

git clone https://github.com/rebase-energy/EnergyDataModel.git
git clone https://github.com/rebase-energy/emflow.git
cd emflow
pip install -e .[dev]
pip install -e ../EnergyDataModel[dev]

Ways to Contribute

We welcome contributions from anyone interested in this project! Here are some ways to contribute to emflow:

  • Create a new environment;
  • Create a new energy model (simulator, predictor, optimizer or agent);
  • Create a new objective function; or
  • Create an integration with another energy modelling framework.

If you are interested in contributing, then feel free to join our Slack Community so that we can discuss it.

Contributors

This project uses allcontributors.org to recognize all contributors, including those that don't push code.

Sebastian Haglund
Sebastian Haglund

💻
dimili
dimili

💻
Mihai Chiru
Mihai Chiru

💻
Nelson
Nelson

🤔

Licence

This project uses the MIT Licence.

Acknowledgement

The authors of this project would like to thank the Swedish Energy Agency for their financial support under the E2B2 program (project number P2022-00903)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

emflow-0.3.0.tar.gz (5.4 MB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

emflow-0.3.0-py3-none-any.whl (5.4 MB view details)

Uploaded Python 3

File details

Details for the file emflow-0.3.0.tar.gz.

File metadata

  • Download URL: emflow-0.3.0.tar.gz
  • Upload date:
  • Size: 5.4 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.2

File hashes

Hashes for emflow-0.3.0.tar.gz
Algorithm Hash digest
SHA256 80831965c2d1bffc0b94ff66ebc90e66bf63fd0a12bf7f13502928f666625dd9
MD5 65c54e02fb85006648ea91b6350a681f
BLAKE2b-256 177d22b4cde948e3adb0e209213ae969c3d85dfc3b4cda91e9205a38ca52b522

See more details on using hashes here.

File details

Details for the file emflow-0.3.0-py3-none-any.whl.

File metadata

  • Download URL: emflow-0.3.0-py3-none-any.whl
  • Upload date:
  • Size: 5.4 MB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.2

File hashes

Hashes for emflow-0.3.0-py3-none-any.whl
Algorithm Hash digest
SHA256 7ea9f91d547da45082e29a039689e8baac6050b538c7e453a16ef4ce63a8c073
MD5 8e8145794a4b5fdc8547756ce1c8ff76
BLAKE2b-256 02beddd64a493c070fc0cd77b131369ee80296a1ef2cebc2c1a25fd35833cb40

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page