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
When writing a CI test for IntersectionShaper replacement rules, I had been trying to save an MFEMSidreDataCollection that included volume fraction arrays. These were mfem::GridFunctions allocated using code that I don't recall modifying other than splitting it out into a method. The following program makes a MFEMSidreDataCollection like what might be seen as output from the IntersectionShaper and writes it out and then reads it back in. On readback, sidre claims that the fields do not meet Blueprint standards. So, is the data wrong before writing it out? There was no apparent failure during Save(). Or, is there a problem in Load() that messes up these fields?
When writing a CI test for IntersectionShaper replacement rules, I had been trying to save an MFEMSidreDataCollection that included volume fraction arrays. These were mfem::GridFunctions allocated using code that I don't recall modifying other than splitting it out into a method. The following program makes a MFEMSidreDataCollection like what might be seen as output from the IntersectionShaper and writes it out and then reads it back in. On readback, sidre claims that the fields do not meet Blueprint standards. So, is the data wrong before writing it out? There was no apparent failure during Save(). Or, is there a problem in Load() that messes up these fields?
This code was built using an Axom on rzgenie that used the rzgenie-toss_3_x86_64_ib-gcc@8.3.1.cmake host config.
Running "sidredebug > output.txt" works fine as there are no fields.
Running "sidredebug -fields > output.txt" produces the errors below.
CMake
Program output
The text was updated successfully, but these errors were encountered: