v1.13.0

Features

• Support for availability events. (#523).
  See Mesh availability for more information.
• Support for Python 3.13 (#558).

Fixes

• Async delete_object was missing an await on an internal async call (#551).

Requirements

• Mesh >= 2.18

Notes

• Python 3.9 support will dropped in the next Mesh Python SDK release.

v1.12.0

Changes

• Support for new way of sending empty time series (#538).

  This introduces breaking change for use cases with reading time series with
  no points.

  Starting from Mesh 2.17 when an empty time series is read (e.g.: break point
  time series with no values), instead of raising an ValueError with message
  No data in time series reply for the given interval, we will now return
  volue.mesh.Timeseries instance with an empty Arrow table and start/end
  timestamps set to None. Other time series metadata like resolution will be
  set as usual.

• Support for undefined time series resolution (#535).

• Do not include tests and examples in the volue.mesh package (#529).

Requirements

• Mesh >= 2.17

v1.11.0

Fixes

• Broken installation of volue.mesh package via pip (#526).

Requirements

• Mesh >= 2.15

v1.10.0

Fixes

• Processing time series objects with unknown curve types (#519).

Requirements

• Mesh >= 2.15

v1.9.0

Features

• Support for updating versioned one-to-many link relations (#476). See update_versioned_one_to_many_link_relation_attribute.
• Configurable gRPC inbound message size (#421). See gRPC Communication.
• Support for creating physical time series (#383). See create_physical_timeseries.

Changes

• Changes for Mesh server 2.15 gRPC interface compatibility (#470). It introduces breaking API change: update_versioned_link_relation_attribute is renamed to update_versioned_one_to_one_link_relation_attribute.

Fixes

• Example with searching calculation expressions (#508).

Requirements

• Mesh >= 2.15

v1.8.0

Mesh Python SDK release for Mesh server 2.14

Features

• It’s now possible to specify the resolution of a hydro simulation or inflow calculation using the optional resolution argument to run_simulation and run_inflow_calculation. See HydSim for more information.

Changes

• Changes for Mesh server 2.14 gRPC interface compatibility (#464)

Requirements

• Mesh >= 2.14

See https://volue-public.github.io/energy-mesh-python/versions.html.

v1.7.0

Mesh Python SDK release for Mesh server 2.13

Features

• It's now possible to get Marginal Cost input files from Mesh using the new get_mc_file method.
• run_simulation, run_inflow_calculation and get_mc_file now includes log messages from the server in the response.
• It's now possible to specify which scenario to run when using run_simulation.

See https://volue-public.github.io/energy-mesh-python/hydsim.html for more information.

Changes

• Handle MIN30 resolution. (#431)
• Changes for Mesh server 2.13 gRPC interface compatibility (#427, #430, #433, #384, #385, #405, #423)

Requirements

• Mesh >= 2.13

See https://volue-public.github.io/energy-mesh-python/versions.html.

v1.6.0

Features

• Support for Python 3.12 (#413)

Changes

• Add example and documentation on removing time series points using write_timeseries_points (#422)
• Add example with searching calculation expressions (#418)

Requirements

• Mesh >= 2.12

v1.5.0

Features

• Experimental support for running hydro simulations and inflow calculations on the Mesh Server. See HydSim.

Changes

• Use prebuilt winkerberos wheel for Python 3.11 (#378)
• Python 3.8 support will dropped in the next Mesh Python SDK release.

Requirements

• Mesh >= 2.12

v1.4.0

Features

• Implement automatic session lifetime extension (#368)
• Implement functionality to get model names (#356)

Changes

• Versions must be sorted in update_rating_curve_versions (#358)

Fixes

• Fixed handling of simple attributes without any values. (#364)

Requirements

• Mesh >= 2.10