group instead of the global group. The global group is used only
to create the blueprint index group and the global group may be shared
between multiple users; it is easier to manage if the sdc only creates
groups and views under unshared groups.
The blueprint index was only being genererated for the boundary mesh when
rank 0 had boundary elements. We need to generate the boundary mesh
group and associated blueprint index if any of the domains have boundary
elements.
Uses a NamedFieldMap to associate the attribute data with an Array<int>* whose underlying data
is stored by Sidre. The mesh and mesh boundary attributes are now added to the datastore using
this mechanism.
In this version, the Axom project merged the spio (sidre parallel I/O)
component into sidre. This simplifies Axom's configuration.
Earlier versions of Axom/Sidre are no longer supported.
Checking for a sidre::View by calling sidre::Group::getView()
triggers a warning when the View is not present.
Using sidre::Group::hasView() and returning NULL avoids this warning.
Sidre warns when trying to access a non-existent group or view.
The preferred access/creation pattern is to check for the existence of a group/view
before allocating, rather than checking if accessing returns a null pointer.
Stowell, Mark L