Handling minor extensions to Xdmf data format #19914
markcmiller86
started this conversation in
Share cool stuff
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ultimately, the Xdmf is implemented as XML. This means we can easily extend the Xdmf format in small ways by supporting additional XML attributes on the main XML tags that Xdmf defines. XML attributes are those
name = value
pairs that occur inside an XML tag as in...For example, in a recent update to VisIt's Xdmf plugin to support xy-curves (which are topologically 1 dimensional things), we added support for a
GridPurpose
attribute to the<Grid>
tag. Currently, the only supported value for that attribute in VisIt is"Curve"
. So, an Xdmf file with that new attribute in it might look like...To handle introspection for this newly defined attribute, In the plugin code below,
grid
is anXdmfGrid*
and one of the key Xdmf data modeling *elements.But, all of Xdmf's data modeling elements inheret from a base type of
XdmfElement
which supportGet()
for an attribute name which may be defined on the associated tag in the Xdmf XML file.visit/src/databases/Xdmf/avtXdmfFileFormat.C
Lines 1692 to 1706 in 2b36a3e
A similar approach could be taken to define other small metadata tidbits such as whether a mesh variable is intensive or extensive or handling cycle or state index in addition to time, or for defining VisIt expressions.
Beta Was this translation helpful? Give feedback.
All reactions