Skip to content

Add MED mesh format backend - #90

Merged
jorgensd merged 14 commits into
mainfrom
dokken/med-backend
Oct 23, 2026
Merged

jorgensd merged 14 commits into
mainfrom
dokken/med-backend

Conversation

@jorgensd

@jorgensd jorgensd commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Resolves #4.

Can read time dependent meshes and meshtags.

@jorgensd jorgensd changed the title Add medcoupling. Add MED mesh format backend Oct 22, 2026
jorgensd and others added 7 commits October 22, 2026 18:38
CMake 4 rejects MEDCoupling's cmake_minimum_required(VERSION 2.8.11).
Setting CMAKE_POLICY_VERSION_MINIMUM=3.5 lets it configure, and keeps
the legacy FindPythonInterp/FindPythonLibs modules that Salome's CMake
configuration uses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Salome's salome_install_scripts compiles the SWIG-generated
MEDCoupling.py to .pyc, but UseSWIG does not declare the .py as a build
output, so Ninja rejects the rule. Makefiles order it after the SWIG
module target instead, which is how Salome builds MEDCoupling.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MEDFilterEntity passes MEDCoupling ids to MEDfilterEntityCr as med_int,
which only compiles when both are 64-bit. Ubuntu's MED-fichier has a
32-bit med_int, so build MEDCoupling with 32-bit ids to match.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jorgensd and others added 6 commits October 23, 2026 09:16
MEDCoupling 9.15 uses MEDfileObjectDescription* from MED-fichier 4.2,
while Ubuntu packages 4.1.0. Build 4.2 from the copy conda-forge uses
(Salome's server blocks automated downloads), verified by checksum,
against the image's MPI HDF5, and point MEDCoupling at it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MED-fichier 4.2 only accepts HDF5 1.10.x at configure and compile time.
Apply the edits Debian uses for HDF5 1.14 (relax the version checks,
turn the version #errors into #warnings); files are still written in
the HDF5 1.8 format.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MED-fichier 4.2 calls H5Oget_info with its HDF5 1.10 signature; compile
with H5_USE_110_API, as Debian does. Skip the Fortran API, which
MEDCoupling does not use, so med_int defaults to int.

Read MEDCoupling coordinates with getValues in the permutation test, as
toNumPyArray only exists in MEDCoupling builds with NumPy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jorgensd
jorgensd merged commit e67bed2 into main Oct 23, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support reading meshes and meshtags from .med format

1 participant