Yoshimi's fix has been merged into VTK and will be in ParaView 5.5 due out in November.
https://gitlab.kitware.com/vtk/vtk/merge_requests/3090/diffs Thank you for the report, Eric, and for the fix, Yoshimi. Cory On Wed, Aug 2, 2017 at 12:28 AM, kenichiro yoshimi <[email protected]> wrote: > Hello Eric, > > If the number of blocks in dataset decreases over time steps then > vtkMultiBlockPLOT3DReader seems to fail to count it. For your > information, I tried commenting out the line 822 in > ParaView-v5.4.0/VTK/IO/Parallel/vtkMultiBlockPLOT3DReader.cxx and this > worked with your data. > ----- > if ( numGrid > (int)this->Internal->Dimensions.size() ) > { > this->Internal->Dimensions.resize(numGrid); > } > > => > > //if ( numGrid > (int)this->Internal->Dimensions.size() ) > { > this->Internal->Dimensions.resize(numGrid); > } > ----- > > Thanks, > yoshimi > > 2017-08-02 2:16 GMT+09:00 Eric Lynch <[email protected]>: >> I believe there is a bug in the PLOT3D metafile reader. I've attached two >> PLOT3D meshes and a metafile. Version 5.4.1 appears to read the metafile >> successfully. After reading it, I can see the outline of the two blocks in >> the first mesh file. If I advance to the next time step, I can see the >> outline of the three blocks in the second mesh. If I then go back to the >> previous time step, I get an error message saying: >> >> >> >> ERROR: In >> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/IO/Parallel/vtkMultiBlockPLOT3DReader.cxx, >> line 1397 vtkMPIMultiBlockPLOT3DReader (0x6b53260): Encountered premature >> end-of-file while reading the geometry file (or the file is corrupt). >> >> >> >> ERROR: In >> /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkExecutive.cxx, >> line 784 vtkCompositeDataPipeline (0x6946da0): Algorithm >> vtkMPIMultiBlockPLOT3DReader(0x6b53260) returned failure for request: >> vtkInformation (0x68935b0) >> >> Debug: Off >> >> Modified Time: 982828 >> >> Reference Count: 1 >> >> Registered Events: (none) >> >> Request: REQUEST_DATA >> >> ALGORITHM_AFTER_FORWARD: 1 >> >> FROM_OUTPUT_PORT: 0 >> >> FORWARD_DIRECTION: 0 >> >> >> >> To my knowledge, the last version without this bug was 4.3.1. >> >> >> >> Thanks, >> >> Eric >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -- Cory Quammen Staff R&D Engineer Kitware, Inc. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
