ESyS-Particle: HPC Discrete Element Modelling Software

dump2vtk with ESyS 2.2

Asked by AndyRathbun on 2012-09-28

Hello All,

We just upgraded our version of ESyS. When I do dump2vtk now, I get some odd results. Has the usage changed with the version 2.2? It looks like the command is finding the wrong things in the _0.txt file.

I run it with:
$ dump2vtk -i cpt -o shear -t 0 100 10000 -rot

The old screen output is:

version : 2
infilename : snaps/cpt_t=1980000_0.txt
nr. of filenames: 6
snaps/cpt_t=1980000_1.txt , 1
snaps/cpt_t=1980000_2.txt , 2
snaps/cpt_t=1980000_3.txt , 3
snaps/cpt_t=1980000_4.txt , 4
snaps/cpt_t=1980000_5.txt , 5
snaps/cpt_t=1980000_6.txt , 6

But now:
version : 3
infilename : snaps/cpt_t=0_0.txt
nr. of filenames: 8
Dimension , 1
3D , 2
snaps/cpt_t=0_1.txt , 3
snaps/cpt_t=0_2.txt , 4
snaps/cpt_t=0_3.txt , 5
snaps/cpt_t=0_4.txt , 6
snaps/cpt_t=0_5.txt , 7
snaps/cpt_t=0_6.txt , 8

The cpt_0.txt file is:
V 3
2000000
0.03
0
ESyS-Particle_2.2_beta_bzr_rev. -1
BoundingBox 0 0 0 40 60 12.5
PeriodicBoundaries 1 0 0
Dimension 3D
snaps/cpt_t=0_1.txt snaps/cpt_t=0_2.txt snaps/cpt_t=0_3.txt snaps/cpt_t=0_4.txt snaps/cpt_t=0_5.txt snaps/cpt_t=0_6.txt

And the old version pre-update is:
V 2
2000000
0.03
0
LSMGeometry 1.2
BoundingBox 0 0 0 80 60 25
PeriodicBoundaries 1 0 0
Dimension 3D
snaps/cpt_t=0_1.txt snaps/cpt_t=0_2.txt snaps/cpt_t=0_3.txt snaps/cpt_t=0_4.txt snaps/cpt_t=0_5.txt snaps/cpt_t=0_6.txt

Thanks for you help
Andy R

Question information

Language:
English Edit question
Status:
Solved
For:
ESyS-Particle Edit question
Assignee:
No assignee Edit question
Solved by:
SteffenAbe
Solved:
2012-10-02
Last query:
2012-10-02
Last reply:
2012-10-01
Best SteffenAbe (s-abe) said : #1

Hi Andy,

you found a bug in dump2vtk. Fix is committed (rev. 1073). A workaround to make the snapshot readable for pre-1073 versions is change the line "ESyS-Particle_2.2_beta_bzr_rev. -1" in the _0.txt files to "ESyS-Particle_2.2_beta_bzr_rev. 2"

AndyRathbun (andy-p-rathbun) said : #2

Thanks SteffenAbe, that solved my question.