Exodus writer is failing with sidesets/ nodesets.
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The exodus writer is failing writing sidesets and nodesets. There are two cases.
Windows, local server, 4.3.1.
- If the blocks, sidesets and nodesets have the same name (such as block 1, sideset 1 and edgeset 1), when you write it as an Exodus file, you will get the following warnings:
Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIWriter.cxx, line 960 vtkPExodusIIWriter (0000000016865EC0): Array in input field data has Null name, cannot output it
Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIWriter.cxx, line 960 vtkPExodusIIWriter (0000000016865EC0): Array in input field data has Null name, cannot output it
Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIWriter.cxx, line 960 vtkPExodusIIWriter (0000000016865EC0): Array in input field data has Null name, cannot output it
Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIWriter.cxx, line 960 vtkPExodusIIWriter (000000000DFA8AE0): Array in input field data has Null name, cannot output it
When you try to read this file back into ParaView, ParaView will crash.
I am attaching datset - UUR-test.g.
- If the names are unique (block 1, sideset 2 and nodeset 3), you will get the following warnings:
Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIWriter.cxx, line 960 vtkPExodusIIWriter (000000000F5659A0): Array in input field data has Null name, cannot output it
Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIWriter.cxx, line 960 vtkPExodusIIWriter (000000000F5659A0): Array in input field data has Null name, cannot output it
Warning: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\IO\Exodus\vtkExodusIIWriter.cxx, line 960 vtkPExodusIIWriter (000000000F5659A0): Array in input field data has Null name, cannot output it
If you then read in the file, it appears to read correctly. Upon inspection, however, all of the sidesets and nodesets have been read in as blocks.
I am attaching datset - UUR-test_uniqut.g.