dump mesh/vtm command

Purpose

Dumps fix mesh/surface geometries to VTM files

Syntax

dump ID group-ID style N file meshes mesh-ids mesh_properties properties

  • ID = user-assigned name for the dump

  • group-ID = ID of the group of atoms to be dumped

  • style = mesh/vtm

  • N = dump every this many timesteps

  • file = name of file to write dump info to

  • meshes = obligatory keyword followed by

  • mesh-ids = either keyword ‘all’ or a list of IDs of fix mesh/surface or fix wall/gran of type ‘primitive’

  • mesh_properties = optional keyword followed by

  • properties = a space-separated list containing: ‘stress’ or ‘id’ or ‘wear’ or ‘vel’ or ‘stresscomponents’ or ‘owner’ or ‘area’ or ‘aedges’ or ‘acorners’ or ‘nneigs’

Examples

dump dmpMyMeshVTM all mesh/vtm 100 mesh*.vtm meshes my_mesh_id mesh_properties vel area
dump dmpAllMeshesVTM all mesh/vtm 100 mesh*.vtm meshes all mesh_properties stress wear

Description

The mesh/vtk style can be used to dump active mesh geometries defined via fix mesh/surface or primitive walls, defined via fix wall/gran commands to a series of VTK files. The mesh/vtm style currently only allows the .vtm file ending and writes in parallel only. Different keywords can be used to dump the per-triangle averaged stress in normal and shear direction, id, velocity, wear, stress components (fx / element area, fy / element area, fz / element area), area (area of each element) or the process which owns the element (visualisation of the parallel decomposition) into the specified file using a VTK file format. The ‘meshes’ keyword (only for mesh/vtm) and the list of mesh IDs is optional. As with the stl style, all active meshes are dumped if you do not supply the optional list of mesh IDs. By specifying list of mesh IDs you can explicitly choose which meshes to dump. The group-ID is ignored. Again, a series of files can be post-processed in Paraview , www.paraview.org Keywords aedges and acorners* dump the number of active edges/corners per face. Keyword nneighs dumps the number of face neighbors Aspherix® has recognized for each face.

Note

Note that you have to link against VTK libraries to use mesh/vtm.

mesh/vtm is similar to mesh/vtk but only the arguments are different. The former requires the use of the keyword meshes which has to be followed either by a list of mesh-ids or the keyword ‘all’. After the mesh specification mesh/vtm can be provided with the optional keyword mesh_properties that needs to be followed by the dump identifiers. The list of such identifiers is identical to mesh/vtk.

By providing the ‘meshes’ keyword and any ID (or a list of IDs) of fix mesh/surface or a fix wall/gran with type ‘primitive’, you can specify which meshes to dump. If no meshes are specified, all meshes and primitive walls used in the simulation are dumped.

Dumps are performed on timesteps that are a multiple of N (including timestep 0) and on the last timestep of a minimization if the minimization converges. Note that this means a dump will not be performed on the initial timestep after the dump command is invoked, if the current timestep is not a multiple of N. This behavior can be changed via the dump_modify first command, which can also be useful if the dump command is invoked after a minimization ended on an arbitrary timestep. N can be changed between runs by using the dump_modify every command. The dump_modify every command also allows a variable to be used to determine the sequence of timesteps on which dump files are written. In this mode a dump on the first timestep of a run will also not be written unless the dump_modify first command is used.

The specified filename determines how the dump file(s) is written. The default is to write one large text file, which is opened when the dump command is invoked and closed when an undump command is used or when Aspherix® exits.

Dump filenames can contain one wildcard character. If a “*” character appears in the filename, then one file per snapshot is written and the “*” character is replaced with the timestep value. For example, tmp.dump.* becomes tmp.dump.0, tmp.dump.10000, tmp.dump.20000, etc. Note that the dump_modify pad command can be used to ensure all timestep numbers are the same length (e.g. 00010), which can make it easier to read a series of dump files in order with some post-processing tools.

Dump_modify:

This keyword can be influenced by several dump_modify options. Additionally it supports the remove_mesh keyword, followed by an id of a fix mesh/surface or a fix wall/gran with type ‘primitive’. This will remove a specific mesh or primitive wall from the output.

Restrictions

None.

Default

None.