search

LLNL / conduit

Simplified Data Exchange for HPC Simulations
https://software.llnl.gov/conduit/
Other
208 stars 64 forks source link

mesh bp: add version number to schema #342

Open xjrc opened 5 years ago

xjrc commented 5 years ago

In order to support backwards compatibility as Blueprint evolves, the schema should be augmented to include version information.

xjrc commented 4 years ago

This issue will become crucial once #504 is resolved as the associated refactoring will break compatibility with Conduit-Blueprint meshes from versions before the change. In order to mitigate the cost of migrating, helper functions should be provided to users to upgrade their mesh to a more recent version of Conduit-Blueprint (e.g. in the case of #504, update their polygonal/polyhedral topologies to the new format).

cyrush commented 4 years ago

Pushing this to 0.7.0