[replay] Meshlane - How to move meshes and results reliably between simulation codes?

"Moving meshes and simulation results between codes should be simple. In practice, lost groups, missing metadata, unsupported formats, parser failures, or memory issues with large meshes can turn a quick conversion into hours of debugging.

In this webinar, the Simvia team presents meshlane, our open-source fork of meshio, actively maintained and extended to handle the mesh conversions industrial workflows actually need.

In this session: 0:00 : Introduction 1:39 : Historic 9:57 : New features 19:46 : Roadmap 28:07 : Q&A

• Does meshlane transfer result fields, or only meshes? Both, where the formats allow it. Point and cell data travel through every conversion, and MED files keep multi-timestep result fields with their time-step metadata, units and component names. Note it's a format conversion, not field interpolation between different meshes.

• Are node/element groups preserved (e.g. .inp MED)? Yes in current releases: .inp node/element sets are converted to MED groups and back. If you saw groups dropped, update to the latest meshlane and open a GitHub issue with your file if it persists.

• How are time steps handled in MED files? Multi-timestep fields are read and written with their time-step metadata preserved, and files stay readable by Salome and MED tools.

• Is the VMAP format supported? Not yet. If you need it, open a feature request on GitHub, community demand drives the roadmap.

• What about CGNS for large CFD meshes? Current CGNS support is minimal (inherited from meshio). A full CGNS reader and writer is on the roadmap.

Useful Links:

• meshlane on GitHub: https://github.com/simvia-tech/meshlane
• meshlane on PyPI: https://pypi.org/project/meshlane/
• Open Simulation Center (softwares download): https://open-simulation-center.org/