Release Notes

Release 0.4.0 (2026-06-04)

  • Add a distance to surface data fit measure for contact points

  • Gempy model cells are getting mislabelled

  • Allow asymmetric octree extents with cell size enforcement

  • Have consistency in output labels: name, vs data name vs data group name

  • Post-process surface normals of gempy surfaces

  • No orientations fails before validator raises

  • Migrate gempy-drivers from Poetry/conda-lock env management to pixi

Release 0.3.0 (2026-01-09)

  • Add nugget as input to control points (FloatData or float)

  • Add range as input value to ui json (float)

  • Rename the basement layer generated automatically by gempy

  • Add data scaling parameters in all three dimensions

  • Support 3D vector orientations

  • Add data channel for orientation magnitude (gradient) constraint

  • Add option to export scalar field

  • Make input mesh optional with base cell size - convert gempy to geoh5 octree

  • Add a data layer to control which events are conformal/non-conformal

  • Support nugget values per observation point

  • Validate that there is an orientation per conformal group

  • Add a data fit measure on the observation points based on gradient direction and distance from surface

  • Update docs for new unconformity, meshing, and orientation options

  • Need to export all scalar fields when multiple conformal groups modelled

  • Investigate why gempy example not reproducing results from website

  • Use ReferenceData as input for the definition of StructuralGroup

  • Add runtest with unconformity and verify if scalar field and gradient exports work

  • Move column stack to ensure it’s scalar_field_gradient is not None

  • Basement added to the referenced value map not visible in GA

Release 0.2.0 (2025-06-20)

  • Environment for coming pre-release

  • Allow users to switch between conformal/non-comformal layers.

  • Bring back adjusted ui.json from Analyst

Release 0.1.0 (2025-02-07)

(First release)

  • Create first connection point with gempy

  • Create gempy-drivers repo

  • Update package with python-poetry-template

  • Use single points object for both markers and orientation

  • Reuse colormap for unit colors and names

  • Add faults to gempy driver/ui.json

  • Investigate/Add pytorch as solver option

  • Fill value errors

  • Add topography to gempy driver/ui.json

  • Use logging to give feedback on driver operations

  • Group results into UIJson group

  • Fixup README by using regular double quotes

  • Create docs for gempy-drivers

  • Find strategy to clean out isolate unit cells from model

  • Exclude RUF005

  • Update input variables in github shared workflows

  • Automatically publish python package on Artifactory

  • Add examples folder to gempy-drivers and add demo workspace

  • Prepare Gempy tutorial for docs

  • Test version consistency

  • Add third party file

  • Add third party file for gempy-drivers

  • Update copyright 2025