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
Is your feature request related to a problem? Please describe.
Currently, the WriteVTK subroutine does not return an error status to alert the user if vtk files couldn't be written. This becomes more of an issue when attempting to create mode-shape files, introduced in #373, when the code may exit "normally" without actually generating any of the desired vtk files. @ebranlard pointed out this issue would occur if the user has deleted the vtk subdirectory between running the simulation and restarting it.
Describe the solution you'd like
Add ErrStat and ErrMsg arguments to WriteVTK, WrVTK_Surfaces, WrVTK_BasicMeshes, and WrVTK_AllMeshes routines. This involves adding error handling after every call to MeshWrVTK in those routines.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the
WriteVTK
subroutine does not return an error status to alert the user if vtk files couldn't be written. This becomes more of an issue when attempting to create mode-shape files, introduced in #373, when the code may exit "normally" without actually generating any of the desired vtk files. @ebranlard pointed out this issue would occur if the user has deleted the vtk subdirectory between running the simulation and restarting it.Describe the solution you'd like
Add
ErrStat
andErrMsg
arguments toWriteVTK
,WrVTK_Surfaces
,WrVTK_BasicMeshes
, andWrVTK_AllMeshes
routines. This involves adding error handling after every call toMeshWrVTK
in those routines.The text was updated successfully, but these errors were encountered: