ESyS-Particle 2.2 CheckPointer doesn't mention 2D dimension

Bug #1116022 reported by Nikita Tropin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ESyS-Particle
Fix Released
Critical
Unassigned

Bug Description

In ESyS-Particle 2.2 if you are running 2D simulation with CheckPointer output, the resulting files doesn't contain the line "Dimension 2D" and so dump2vtk doesn't convert them to vtu files.

My checkpointer file in 2.1:

V 2
150000
1e-06
0
LSMGeometry 1.2
BoundingBox -20 -20 -20 20 20 20
PeriodicBoundaries 0 0 0
Dimension 2D
coords_t=0_1.txt

My checkpointer file in 2.2:

V 3
150000
1e-06
0
ESyS-Particle_2.2_bzr_rev. 1080
BoundingBox -15 0 -1 15 50 1
PeriodicBoundaries 0 0 0
coords_t=0_1.txt

When I run dump2vtk with the latter file, I have an empty vtu files and output like

version : 3
infilename : coords_t=0_0.txt
nr. of filenames: 0

But when I add the line 'Dimension 2D', dump2vtk works fine.

version : 3
infilename : coords_t=0_0.txt
nr. of filenames: 1
coords_t=0_1.txt , 1

Related branches

Revision history for this message
Dion Weatherley (d-weatherley) wrote :

This bug has been independantly confirmed by another ESyS-Particle user. It is likely the bug was introduced in rev. 1078. The bug possibly arises only for scripts using in-simulation geometry creation. Correct checkpoint file headers are produced when using readGeometry().

Changed in esys-particle:
importance: Undecided → Critical
status: New → Triaged
Revision history for this message
SteffenAbe (s-abe) wrote :

A Bugfix has been committed in rev. 1088

Changed in esys-particle:
status: Triaged → Fix Committed
Vince Boros (v-boros)
Changed in esys-particle:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.