You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ReviewedSidreIssues related to Axom's 'sidre' componentSpioIssues related to paralle I/O for Axom's Sidre componentTPLIssues related to Axom's third party librariesWindowsRelated to Windows development
#318 moves the SidreDataCollection class from MFEM into Axom, but the feature is not enabled by default. Before this can be enabled, the following issues need to be addressed (per @kennyweiss):
Resolve an issue with sidre::IOManager not writing the protocol used to the file when saving, preventing visualization with VisIt when running in parallel 2020-10-15: This appears to be working as expected - the provided example can be read in with VisIt when running in parallel
Need to ensure that the convert_sidre_protocol example builds on Windows
The text was updated successfully, but these errors were encountered:
joshessman-llnl
added
Sidre
Issues related to Axom's 'sidre' component
TPL
Issues related to Axom's third party libraries
Spio
Issues related to paralle I/O for Axom's Sidre component
Windows
Related to Windows development
labels
Sep 25, 2020
Once reconstruction for parallel meshes is implemented we should look at ensuring coherency between the mfem::Mesh object and the contents of the datastore as refinement can cause them to diverge.
ReviewedSidreIssues related to Axom's 'sidre' componentSpioIssues related to paralle I/O for Axom's Sidre componentTPLIssues related to Axom's third party librariesWindowsRelated to Windows development
#318 moves the
SidreDataCollection
class from MFEM into Axom, but the feature is not enabled by default. Before this can be enabled, the following issues need to be addressed (per @kennyweiss):Resolve an issue with2020-10-15: This appears to be working as expected - the provided example can be read in with VisIt when running in parallelsidre::IOManager
not writing the protocol used to the file when saving, preventing visualization with VisIt when running in parallelconvert_sidre_protocol
example builds on WindowsGridFunction
andMesh
objects when an MFEMSidreDataCollection is loaded from a file such that the state of the object is identical to the object that was saved - see Sidre data collection and reloading data mfem/mfem#1776 - Add support for mesh/field reconstruction in MFEMSidreDataCollection #379 and Add support for parallel mesh reconstruction in MFEMSidreDataCollection #445The text was updated successfully, but these errors were encountered: