dump2vtk: empty vtk files due to invalid snapshot headers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ESyS-Particle |
New
|
High
|
Unassigned |
Bug Description
This is to document a known bug affecting some ESyS-Particle users, that results in production of "empty" vtk files when using the 'dump2vtk' tool. Most users notice this when trying to visualise simulations using Paraview.
It would appear to only affect users who have installed ESyS-Particle using pre-built packages (e.g. version 2.3.5) rather than installing from source obtained via the launchpad repository.
The problem appears to be a missing revision number in the headers of the ESyS-Particle snapshot/
V 3
10000
0.001
0
ESyS-Particle_
BoundingBox -20 -20 -20 20 20 20
PeriodicBoundaries 0 0 0
Dimension 3D
snapshot_t=0_1.txt
The offending line is "ESyS-Particle_
$ dump2vtk -i snapshot -o test_ -t 0 1 100
version : 3
infilename : snapshot_t=0_0.txt
nr. of filenames: 0
The generated vtk file contains no points/cells e.g.
$head test_0.vtu
<VTKFile type="Unstructu
<UnstructuredGrid>
<Piece NumberOfPoints="0" NumberOfCells="0">
<Points>
<DataArray NumberOfCompone
</DataArray>
</Points>
<PointData Scalars="radius">
<DataArray type="Float64" Name="radius" NumberOfCompone
</DataArray>
[Note that NumberofPoints="0" and NumberOfCells="0" above]
Workarounds:
1) uninstall the pre-built version of ESyS-Particle (sudo apt-get remove esys-particle) and install the latest version from the source code repository. Instructions for that are available here:
https:/
2) In the folder containing faulty snapshot files, a quick fix is possible with this command:
$ sed -i -e 's/rev./rev. 1080/g' *_0.txt
This bug will be triaged and fixed prior to the next stable release of ESyS-Particle.
description: | updated |
information type: | Public → Public Security |
information type: | Public Security → Public |
information type: | Public → Public Security |