Skip to main content
ATLAS

CI codecov Python License

Status: under active development — no stable release yet.

Overview

ATLAS simulates electricity market mechanisms across the full trading horizon. It models the sequential decisions of market participants — from order formulation ahead of the auction to market clearing and portfolio optimisation — using a modular, configurable architecture.

Each module is an independent computation unit that reads from a shared dataset and produces structured changes applied by the orchestrator. Modules are chained into workflows, where the output of each step feeds into the next.

Market Chains

Modules are grouped into market chains, each representing a full simulation cycle.

Day-Ahead — available

Module Description
Day-Ahead Orders Generates market orders for all equipment types based on asset characteristics and cost structure.
Market Clearing Determines market equilibrium by matching supply and demand across interconnected areas, under ATC or flow-based network constraints.
Portfolio Optimisation Optimises energy asset portfolios (thermal, hydro, storage, solar, wind, load) to maximise profit under market conditions.

Intraday — available

Module Description
Intraday Price Forecast Forecasts intraday prices per market area from the deviation between the latest load, wind and solar forecasts and the day-ahead baseline, using a price sensitivity ratio and price caps.
Portfolio Optimisation Re-optimises the portfolio against the forecast prices, starting from the day-ahead cleared position.
Intraday Orders Formulates intraday orders (thermal, hydro, storage, solar, wind, load, non-dispatchable) from the gap between the optimised schedule and the current engagement.
Market Clearing Clears the intraday market over the remaining horizon.
Portfolio Optimisation Final re-optimisation against the intraday cleared position.

Both chains reuse the same Market Clearing and Portfolio Optimisation modules — only the parameters and the position they hold in the workflow differ.

Stack

  • Python 3.13+, managed with uv
  • OR-Tools for optimisation, Pydantic for data models, Polars for data processing
  • Typer for the CLI, Ruff for linting, mypy for type checking, pytest for tests

Installation

pip install atlas-model

# or with uv
uv add atlas-model

Quick Example

1. Build a dataset

from atlas import AtlasDataset, ControlBlock, MarketArea, Node, Portfolio, Thermal, Timeseries

cb = ControlBlock(name="cb_fr")
area = MarketArea(name="fr", control_block=cb)
node = Node(name="node_fr", control_block=cb, market_area=area)
portfolio = Portfolio(name="gen_fr", control_block=cb, market_area=area)

variable_cost = Timeseries.from_index(
    start_date="2024-01-01 00:00:00",
    frequency="1h",
    end_date="2024-01-02 00:00:00",
    default_value=45.0,
)

nuclear = Thermal(
    name="fr_nuclear",
    node=node,
    portfolio=portfolio,
    installed_capacity=1584.0,
    variable_cost=variable_cost,
)

dataset = AtlasDataset(
    control_block=[cb],
    market_area=[area],
    node=[node],
    portfolio=[portfolio],
    thermal=[nuclear],
)
dataset.to_directory("./data/input/")

2. Configure parameters

# parameters.yaml
temporal:
  start_date: "2024-01-01 00:00:00"
  end_date: "2024-01-02 00:00:00"
  execution_date: "2023-12-31 12:00:00"
  timestep: "PT1H"
solver:
  solver_name: "SCIP"
load_price: 3000

3. Run a module

atlas module list # See available modules

atlas module run DayAheadOrders -p parameters.yaml -d ./data/input/

Or from Python:

from atlas import AtlasDataset, ModuleRun

result = ModuleRun(
    module="DayAheadOrders",
    dataset="./data/input/",
    parameters="parameters.yaml",
).run()

4. Run a full day-ahead workflow

# workflow.yaml
name: day-ahead
dataset_path: ./data/input/
output_dataset_path: ./data/output/
output_dir: ./results/
steps:
  - module: DayAheadOrders
    parameters_path: ./parameters/day_ahead_orders.yml
  - module: MarketClearing
    parameters_path: ./parameters/market_clearing.yml
  - module: PortfolioOptimisation
    parameters_path: ./parameters/portfolio_optimisation.yml
atlas workflow list workflow.yaml # List all workflow steps

atlas workflow run workflow.yaml

5. Run a full intraday workflow

The intraday chain starts from a price forecast and re-optimises the portfolio twice — once against the forecast prices, once against the intraday cleared position. The same module can appear several times in a workflow with different parameters.

# intraday_workflow.yaml
name: intraday
dataset_path: ./data/input/
output_dataset_path: ./data/output/
output_dir: ./results/
steps:
  - module: IntradayPriceForecast
    parameters_path: ./parameters/intraday_price_forecast.yml
  - module: PortfolioOptimisation
    parameters_path: ./parameters/portfolio_optimisation_1.yml
  - module: IntradayOrders
    parameters_path: ./parameters/intraday_orders.yml
  - module: MarketClearing
    parameters_path: ./parameters/market_clearing.yml
  - module: PortfolioOptimisation
    parameters_path: ./parameters/portfolio_optimisation_2.yml
atlas workflow run intraday_workflow.yaml

A runnable example is available in the test dataset:

uv run atlas workflow run tests/dataset/parameters/intraday/workflow.yml

Documentation

Full documentation: atlas-model.readthedocs.io

Contributing

See CONTRIBUTING.

Changelog

See CHANGELOG.

Authors

See AUTHORS.

Metadata

Release files for atlas-model 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for atlas-model 0.1.2
File Size Uploaded
atlas_model-0.1.2.tar.gz 316.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for atlas-model 0.1.2
File Interpreter ABI Platform
atlas_model-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 802.3 kB

Release files / atlas_model-0.1.2.tar.gz

Download URL atlas_model-0.1.2.tar.gz
Size 316.9 kB
Tags Source
SHA-256 checksum
How to use checksums
ca323d1a7d89b489e90fdd061fffeb15f0317bac0ba96e2ec827288df126d6a4
BLAKE2b-256 checksum
How to use checksums
e2d22bd26b2736ac45659bcfce56ea49c55dfd7eef0bcde398b8c427376262a9
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 Oct 5, 2026.

Transparency log

Release files / atlas_model-0.1.2-py3-none-any.whl

Download URL atlas_model-0.1.2-py3-none-any.whl
Size 485.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
19c3d31bf6bbd6c717743b1c7f70d26867bcab170d50bc1843ece3a18f52d688
BLAKE2b-256 checksum
How to use checksums
f11b5d68b050beb98f90598d4a1d016d177729972c79e16599d83923dbd6dcd3
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 Oct 5, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page