v0.15.0

Release date: 2025-05-19

Early Access

The Luminary Cloud API and Python SDK are Early Access features that are still under development. View the Luminary Cloud Early Access Terms. The interface may change, and you may need to migrate or discard scripts and configuration files multiple times before v1.0.0 is released. In the future, migrations may also be necessary when upgrading to new major versions of the SDK (e.g. v2.0.0).

Release Notes

This release has breaking changes and some sweet new features.

Breaking Changes

Features

Bug Fixes / Improvements

Deprecations

Migration Guide

Migrating from Geometry.modify()

It’s unlikely that you were using Geometry.modify() directly, but if you were, you’ll need to switch to using the methods in Geometry or VolumeSelection that are equivalent to whichever modification operation you were using.

Migrating to SimulationParam

get_parameters() now returns a SimulationParam object instead of a raw proto message. It’s unlikely that you were accessing methods and attributes of the proto message directly, but if you were, you’ll need to switch to using the methods and attributes of the SimulationParam object instead.

The params argument of create_simulation_template() also now takes a SimulationParam object instead of a raw proto message, so if you were passing it the result of get_parameters(), there’s no need to change anything.

Also, if you were using get_simulation_param() to get a SimulationParam object, you should switch to get_parameters() (which is identical) since get_simulation_param() is now deprecated.

Migrating to MeshMetadata

It’s again unlikely that you were accessing the protos returned by get_mesh_metadata() directly, but if you were, the returned values are now instances of MeshMetadata instead of raw protos, so you’ll need to switch to using the methods and attributes of the MeshMetadata object instead. Fortunately, the interface should be largely the same.