dump custom/vtk

Submitted by NTT1508 on Wed, 10/07/2015 - 00:38

Dear all,

I am struggling with dump custom/vtk (3.2.0 and 3.3.0) that always results in an error: Invalid dump style (output.cpp: 591). I have not tried this command before. I usually use lpp to convert to vtk. An example of my using dump custom/vtk as below:

dump dmp all custom/vtk 10000 dump.liggghts_init id type type x y z ix iy iz vx vy vz fx fy fz omegax omegay omegaz radius

Thank for concern,

Regards,

Forums:

richti83's picture

richti83 | Wed, 10/07/2015 - 08:54

you need to compile liggghts with VTK support (using makefile ubuntuVTK or ubuntuVTK6 (_fpic for coupling)
alternativly you can use dump custom, change dump file ending to *.liggghts and use my ParaView Reader for liggghts dump files:
https://github.com/richti83/ParaView_Reader_for_LIGGGHTS/tree/master/pre...
In this case you need to dump the results as file series:

dump dmp all custom 10000 dump*.liggghts id type x y z vx vy vz fx fy fz omegax omegay omegaz radius

I'm not an associate of DCS GmbH and not a core developer of LIGGGHTS®
ResearchGate | Contact

aaigner's picture

aaigner | Wed, 10/07/2015 - 13:26

Hi,

as richti83 mentioned you need to compile it with VTK support.

In case of Ubuntu just install the vtk libraries with
sudo apt-get install libvtk5-dev (I am not sure if you need libvtk5.8 too, I think it is already a dependency for the dev-version)

This will install the vtk - library on your system. If you compare [src]/MAKE/Makefile.fedora with [src]/MAKE/Makefile.ubuntuVTK, you see that it is more or less the same. It just adds the VTK_INC, VTK_PATH and VTK_LIB compiler settings and the -DLAMMPS_VTK compiler flag.

If you are not using Ubuntu, most probably you have to modify the VTK_INC path. Fedora, for instance, uses the path /usr/include/vtk instead of /usr/include/vtk-5.8 (compare Makefile.fedora_vtk_fpic with Makefile.ubuntuVTK).

I recommend strongly to use the VTK libraries. The output files are of the same size as the original dump-files and you can skip all that LPP stuff.

Bests
Andreas

Daniel Queteschiner | Wed, 10/07/2015 - 13:35

In addition to compiling LIGGGHTS with VTK support, you should use a VTK filename extension to indicate which VTK file format is to be used for the output (legacy VTK or XML) as illustrated in the following example:

original dump custom command:
dump dmp all custom 1000 post/dump_pack_*.fill id type x y z ix iy iz vx vy vz fx fy fz

dump as legacy VTK:
dump dmpvtk all custom/vtk 1000 post/dump*.vtk id type ix iy iz vx vy vz fx fy fz

dump as poly data XML:
dump dmpvtp all custom/vtk 1000 post/dump*.vtp id type ix iy iz vx vy vz fx fy fz

dump as unstructured grid XML:
dump dmpvtu all custom/vtk 1000 post/dump*.vtu id type ix iy iz vx vy vz fx fy fz

Since this naming scheme conflicts with the way you usually specify whether the output should be binary or not, you can use the dump_modify command for this task, e.g.
dump_modify dmpvtk binary yes # or 'no' for ascii

aaigner's picture

aaigner | Wed, 10/07/2015 - 17:36

Thanks ... I always forget to mention that.

NTT1508 | Thu, 10/08/2015 - 05:16

Dear all,

Many thanks for your responds. It works fine now. custom/vtk is clearly save a lot of time for post-processing.
Obviously Paraview Readers of Christian, especially bond_reader are also great that I have used many times.

Best regards,