Releases: precice/config-graph
Releases · precice/config-graph
Minor bug fix
Fixed a missing \" in AccelerationDataNode
v2.0.2
Fixed wrong to_xml() of CouplingSchemeNode. Also added tag directory to M2NNode.
Full Changelog: v2.0.1...v2.0.2
v2.0.1
Updated README.md to reflect new preCICE configuration validation tools.
v2.0.0
Welcome to config-graph EVO (version 2.0.0), the best version of config graph we've ever built!
This new version features several life-changing new features:
- Did you ever want to create a
precice-config.xmlfrom our graph? Well, now you can! - Did you ever wonder where other config element-tags were? They have just arrived, fresh from the drawing board
- Do not worry, none of these parameters are needed for creating a graph to validate an existing
precice-precice-config.xml - The usage of
[Multi]CouplingSchemeNodes got even better! Their previous list-attributeaccelerationshas been changed to allow only a single AccelerationNode - Additionally, to improve readability, we moved all the enums for creating nodes to the new "enums.py" file.
Will you validate precise-config.xml's more fiercely than ever before? Or are you going to build the greatest precice-config.xml ever? The choice is now yours!
Stay tuned for what's to come next!
November 22, 2025
Breaking Changes
- Enums like
MappingTypeorExportFormathave been moved to fileprecice_config_graph/enums.py, right next to thenodes.pyfile (#1). - The
CouplingSchemeNode's attributeaccelerations: list[AccelerationNode]has been updated toacceleration: AccelerationNode(#1). - The
MultiCouplingSchemeNode's attributeaccelerations: list[AccelerationNode]has been updated toacceleration: AccelerationNode(#1).