BUG: unguarded use of globalIndex in vtk writers (fixes #1110)
- the problem occurred when running the writers in a parallel solver or utility but requesting output on the master only. Adjusted the logic to avoid globalIndex for these cases. Previously the if (parallel_) checks were happening later, after the globalIndex had already been created.
Showing
- src/conversion/vtk/output/foamVtkInternalWriter.C 20 additions, 26 deletionssrc/conversion/vtk/output/foamVtkInternalWriter.C
- src/conversion/vtk/output/foamVtkInternalWriter.H 6 additions, 4 deletionssrc/conversion/vtk/output/foamVtkInternalWriter.H
- src/conversion/vtk/output/foamVtkPatchWriter.C 16 additions, 17 deletionssrc/conversion/vtk/output/foamVtkPatchWriter.C
- src/conversion/vtk/output/foamVtkPatchWriter.H 4 additions, 6 deletionssrc/conversion/vtk/output/foamVtkPatchWriter.H
- src/fileFormats/vtk/file/foamVtkFileWriter.C 0 additions, 1 deletionsrc/fileFormats/vtk/file/foamVtkFileWriter.C
- src/meshTools/output/foamVtkIndPatchWriter.C 15 additions, 17 deletionssrc/meshTools/output/foamVtkIndPatchWriter.C
- src/meshTools/output/foamVtkIndPatchWriter.H 4 additions, 6 deletionssrc/meshTools/output/foamVtkIndPatchWriter.H
- src/meshTools/output/foamVtkSurfaceWriter.C 16 additions, 17 deletionssrc/meshTools/output/foamVtkSurfaceWriter.C
- src/meshTools/output/foamVtkSurfaceWriter.H 4 additions, 6 deletionssrc/meshTools/output/foamVtkSurfaceWriter.H
- src/meshTools/output/foamVtkWriteCellSetFaces.C 21 additions, 22 deletionssrc/meshTools/output/foamVtkWriteCellSetFaces.C
- src/meshTools/output/foamVtkWriteFaceSet.C 11 additions, 3 deletionssrc/meshTools/output/foamVtkWriteFaceSet.C
- src/meshTools/output/foamVtkWritePointSet.C 2 additions, 2 deletionssrc/meshTools/output/foamVtkWritePointSet.C
Please register or sign in to comment