VTK Export Issue
Posted: Thu Feb 18, 2021 8:15 pm
Hi,
I'm having some difficulty exporting results from GiD's postprocessing environment. I'm trying to export results in .VTK format so I can view them in Paraview. The export seems to run fine, but then when I open the .vtk file in paraview, part of the results file appears to be corrupted; elements in only part of the model show a 'speckled' pattern as shown in the right hand image below. If I import the .vtk file back into GiD I get the same issue, so it's not related to Paraview.
Can anyone help?
To be honest even if I can get this fixed, the .vtk export isn't ideal, as the sets are lost on export so I'm no longer able to view sub-components in isolation within my model. If anyone can suggest a better way of moving results from GiD to paraview I'd be very grateful. It looks like Paraview isn't able to naturally read any of the other GiD export formats. I might consider creating a script so that Paraview can read GiD postprocessing ASCII files but I'd rather find a solution that doesn't involve in depth coding.
Many thanks
James
I'm having some difficulty exporting results from GiD's postprocessing environment. I'm trying to export results in .VTK format so I can view them in Paraview. The export seems to run fine, but then when I open the .vtk file in paraview, part of the results file appears to be corrupted; elements in only part of the model show a 'speckled' pattern as shown in the right hand image below. If I import the .vtk file back into GiD I get the same issue, so it's not related to Paraview.
Can anyone help?
To be honest even if I can get this fixed, the .vtk export isn't ideal, as the sets are lost on export so I'm no longer able to view sub-components in isolation within my model. If anyone can suggest a better way of moving results from GiD to paraview I'd be very grateful. It looks like Paraview isn't able to naturally read any of the other GiD export formats. I might consider creating a script so that Paraview can read GiD postprocessing ASCII files but I'd rather find a solution that doesn't involve in depth coding.
Many thanks
James