Visualization Module (-V)

Module -V is the module for visualizing tessellations, meshes and simulation results as publication-quality PNG images or VTK files, for interactive visualization. Results can be defined from internal data, data loaded from external files or a simulation directory as generated by module -S. For the PNG images, it is possible to set different attributes of the tessellations and meshes such as the node coordinates, or the colors and transparencies of the different entities. Point data can also be represented, using symbols of specified sizes and colors. Slice views can also be generated.

Contrary to other modules, module -V processes the command arguments one after the other. Typically, module -V can be used to visualize tessellations, meshes, points, or results of a simulation directory (on the mesh). The aspects of all entities (tessellation polyhedra, faces, edges, vertices, seeds and crystals, 3D, 2D, 1D and 0D mesh elements and nodes, and points) can be set in detail (options -data*). A crystal is plotted at the center of its cell, shaped according to the Crystal Symmetry and has the same volume as its cell. In the case of a PNG output file, the scene itself can also be set in detail: visibility of the different entities (options -show*), camera position and angle, projection type, image size, etc. (options -camera* or -image*). The coordinate system can also be added.

Here is what a typical run of module -V looks like:

$ neper -V n10-id1.tess,n10-id1.msh -dataelsetcol id -print img

========================    N   e   p   e   r    =======================
Info   : A software package for polycrystal generation and meshing.
Info   : Version 4.0.0
Info   : Built with: gsl|muparser|opengjk|openmp|nlopt|libscotch (full)
Info   : Running on 8 threads.
Info   : <https://neper.info>
Info   : Copyright (C) 2003-2021, and GNU GPL'd, by Romain Quey.
Info   : No initialization file found (`/home/rquey/.neperrc').
Info   : ---------------------------------------------------------------
Info   : MODULE  -V loaded with arguments:
Info   : [ini file] (none)
Info   : [com line] n10-id1.tess,n10-id1.msh -dataelsetcol id -print img
Info   : ---------------------------------------------------------------
Info   : Loading tessellation...
Info   :     [i] Parsing file `n10-id1.tess'...
Info   :     [i] Parsed file `n10-id1.tess'.
Info   : Loading mesh...
Info   :     [i] Parsing file `n10-id1.msh'...
Info   :     [i] Parsed file `n10-id1.msh'.
Info   : Reconstructing mesh...
Info   : Reading data (elset3d, col)...
Info   : Printing image...
Info   :     [o] Writing file `img.pov'...
Info   :   - Printing mesh...
Info   :     > Reducing data...
Info   :       . 3D...
Info   :       . 2D...
Info   :       . Number of 3D elt faces reduced by  90% (to 418).
Info   :       . Number of 3D elt edges reduced by  50% (to 627).
Info   :       . Number of 0D elts      reduced by 100% (to 0).
Info   :     [o] Wrote file `img.pov'.
Info   :   - Generating png file (1200x900 pixels)...
Info   :     [o] Writing file `img.png'...
Info   :     [o] Wrote file `img.png'.
Info   : Printing scale...
Info   : Elapsed time: 1.546 secs.
========================================================================

Arguments

Prerequisites

-povray <binary>

Specify the POV-Ray command or the path to the POV-Ray binary (for generating PNG images).

Default value: povray.

Input Data

<file_name1>,<file_name2>,...

Specify the names of the input file(s) or directory. The file(s) can be a Tessellation File (.tess), a Raster Tessellation File (.tesr), a Mesh File (.msh), or a Position File (for points), and the directory can be a Simulation Directory (.sim).

Default value: -.

When a simulation directory is loaded as input, it is possible to specify the simulation step to consider.

-step <step>

Specify the simulation step (0 for the initial state).,

Default value: 0.

The data internal to the simulation directory have the same status as internal data (such as, for instance, the nominal element orientations stored in the mesh file) and can therefore be loaded (with options -data*) more simply than with standard external files. For example, coloring elements from orientations can be done using -step 2 -dataeltcol ori.

Space Options

The following option enables the definition of the space which the input data (tessellation, mesh, point, etc.) are defined in. The space is most generally real (physical) space, but can be defined as Rodrigues orientation space, which makes it possible to account for its distortion 1.

-space <space> (secondary option)

Specify the space which the input data are defined in, which can be:

  • real for real space;

  • rodrigues for Rodrigues orientation space.

Default value: real.

Tessellation Data Loading and Rendering

The following options enable the definition of the properties (color and size) of the tessellation cells or entities (polyhedra, faces, edges and vertices), seeds and crystals. This can be done either directly, by providing one or several values (e.g. the RGB channel values for color) or indirectly, e.g. using scalar values that are converted in color using a given color scheme. In this case (and for real-type data), a scale image is also generated, and its properties (minimum, maximum and tick values) can be set.

-data{cell,poly,face,edge,ver,seed,crystal,vox,voidvox,voxedge}col <color>

Specify the colors, which can be done in two main different ways.

Colors can be specified directly:

Colors can be set from data using an argument of the general form <data_type>:<data_value>, which can be shortened to <data_value> in the frequent case where the data type can be unambiguously determined from the data value. The possibilities are:

  • int:<data_value>: integer values represented using a color palette, which can be:

  • real:<data_value>: real values represented using a smooth color scale, which can be:

  • ori:<data_value>: crystal orientations (when applicable), which can be:

  • disori:<data_value> (only for vox): crystal disorientations (the rotation with respect to the nominal cell orientation, when applicable), which can be:

See also option -data...colscheme.

Default value: id for cells and crystals, white for faces, black for edges and vertices, gray for seeds, voxels and void voxels, black for voxel edges.

-data{cell,poly,face,edge,ver,seed,crystal,vox}colscheme <col_scheme>

Specify the color scheme used to get colors from the data loaded with option -data...col. The type of color scheme depends on the type of data.

  • For integer values, the color scheme is palette (see Colors and Color Maps);

  • For real values, the available color schemes are described in Colors and Color Maps;

  • For crystal orientations (cubic symmetry is assumed), the color scheme can be:

    • ipf[(<dir>)]: IPF coloring using direction <dir>, which can be x, y or z (default z);

    • rodrigues[(<max>)]: Rodrigues vector coloring, where <max> is the half-length along a direction (default is the fundamental region);

    • axis: rotation axis coloring;

    • angle[(<max>)]: rotation angle coloring, where <max> is the maximum angle (in radian (default is the fundamental region);

    • axis-angle[(<max>[,absolute])] for rotation axis / angle coloring, where <max> is the maximum angle (in radian) and absolute makes it so that the absolute values of the axis components are used.

Default value: palette for integer values, viridis for real values, and rodrigues for crystal orientations.

-data{cell,poly,face,edge,ver,seed,crystal}trs <transparency>

Specify the transparencies (values from 0 to 1), which can be:

-data{edge,ver,seed,crystal,voxedge}rad <rad>

Specify the radii, which can be:

Default value: tessellation dependent.

-data{cell,poly,face,edge,ver,seed,crystal,vox}scale <scale>

Specify the scale relative to the -data...col real data, which can be:

  • <min>:<max>: minimal and maximal values;

  • <min>:<inter1>:...:<max>: minimal, intermediate and maximal values.

When only minimal and maximal values are specified, the scale ticks are set automatically. When intermediate values are specified, the scale ticks are the specified values.

The scale ticks have the same format as the minimal value.

Default value: <data_minimum>:<data_maximum>.

-data{cell,poly,face,edge,ver,seed,crystal,vox}scaletitle <title>

Specify the title of the scale relative to the -data...col real data.

Default value: -.

-datacrystaledgerad <rad>

Specify the radius of the crystals edges, which can be any real value (\(\geq0\)).

Default value: 0.

-datacrystaledgecol <color>

Specify the color of the crystal edges, which can be a color as described in Colors and Color Maps.

Default value: tessellation dependent.

Mesh Data Loading and Rendering

The following options enable the definition of the properties (color, size, etc.) of the mesh entities (3D, 2D, 1D and 0D elements and elsets, nodes, and full mesh). elt and elset refer to the elements and elsets of higher dimensions. The dimension can be also be specified explicitly, as in elt2d or elset2d. node represents all nodes, and mesh the full mesh. This can be done either directly, by providing one or several values (e.g. the RGB channel values for color) or indirectly, e.g. using scalar values that are converted in color using a given color scheme. In this case (and for real-type data), a scale image is also generated, and its properties (minimum, maximum and tick values) can be set.

-data{elt,elset,node,elt{0-3}d,elset{0-3}d,elt{2,3}dedge,mesh}col <color>

Specify the colors, which can be done in two main different ways.

Colors can be specified directly:

Colors can be set from data using an argument of the general form <data_type>:<data_value>, which can be shortened to <data_value> in the frequent case where the data type can be unambiguously determined from the data value. The possibilities are:

  • int:<data_value>: integer values represented using a color palette, which can be:

  • real:<data_value>: real values represented using a smooth color scale, which can be:

  • vector:<data_value>: vectorial values (only for VTK output), which can be:

  • tensor:<data_value>: tensorial values (only for VTK output), which can be:

    • a simulation result (see Simulation Results);

    • file(<file_name>): individual values to load from a Data File. The file can contain either 9 components or only 6 components, in which case Voigt notation is assumed.

  • ori:<data_value>: crystal orientations (when applicable), which can be:

The color schemes used to determine the colors from the data can be fine-tuned using options -dataeltcolscheme or -dataelsetcolscheme.

Default value: -dataelsetcol id (elsets of higher dimension colored, other elsets white, element edges black)

-data{elt,elset,node,elt{0-3}d,elset{0-3}d}colscheme <col_scheme>

Specify the color scheme used to get colors from the data loaded with option -data...col. The type of color scheme depends on the type of data.

  • For integer values, the color scheme is palette (see Colors and Color Maps);

  • For real values, the available color schemes are described in Colors and Color Maps;

  • For crystal orientations (cubic symmetry is assumed), the color scheme can be:

    • ipf[(<dir>)]: IPF coloring using direction <dir>, which can be x, y or z (default z);

    • rodrigues[(<max>)]: Rodrigues vector coloring, where <max> is the half-length along a direction (default is the fundamental region);

    • axis: rotation axis coloring;

    • angle[(<max>)]: rotation angle coloring, where <max> is the maximum angle (in radian (default is the fundamental region);

    • axis-angle[(<max>[,absolute])] for rotation axis / angle coloring, where <max> is the maximum angle (in radian) and absolute makes it so that the absolute values of the axis components are used.

Default value: palette for integer values, viridis for real values, and rodrigues for crystal orientations.

-data{elt,elset,node,elt{0-3}d,elset{0-3}d}scale <scale>

Specify the scale relative to the -data...col real data, which can be:

  • <min>:<max>: minimal and maximal values;

  • <min>:<inter1>:...:<max>: minimal, intermediate and maximal values.

When only minimal and maximal values are specified, the scale ticks are set automatically. When intermediate values are specified, the scale ticks are the specified values.

The scale ticks have the same format as the minimal value.

Default value: <data_minimum>:<data_maximum>.

-data{elt,elset,node,elt{0-3}d,elset{0-3}d}scaletitle <title>

Specify the title of the scale relative to the -data...col real data.

Default value: -.

-data{elt{0,1}d,node,elt{2,3}dedge,elset{0,1}d}rad <rad>

Specify the radii, which can be:

  • a real value;

  • file(<file_name>): individual values to load values from a Data File (not for *edge*).

Default value: mesh dependent.

The following options enable the loading of node positions.

-datanodecoo <coo>

Specify the coordinates of the nodes, which can be done in two main different ways.

Coordinates can be specified directly as follows:

  • file(<file_name>): individual coordinates to load from a Position File.

Coordinates can be set from data using an argument of the general form <data_type>:<data_value>:

  • disp:file(<file_name>): individual displacements to load from a Data File (formatted as a Position File);

  • coo: load coordinates from the simulation directory and step specified in input.

Default value: -.

-datanodecoofact <fact>

Specify the value of the scaling factor to apply to the displacements of the nodes.

Default value: 1.

Point Data Loading and Rendering

The following options enable the definition of the properties (color, shape, size, etc.) of points loaded as input. This can be done either directly, by providing one or several values (e.g. the RGB channel values for color) or indirectly, e.g. using scalar values that are converted in color using a given color scheme. In this case (and for real-type data), a scale image is also generated, and its properties (minimum, maximum and tick values) can be set.

-datapointcol <color>

Specify the colors of the points, which can be done in two main different ways.

Colors can be specified directly:

Colors can be set from data using an argument of the general form <data_type>:<data_value>, which can be shortened to <data_value> in the frequent case where the data type can be unambiguously determined from the data value. The possibilities are:

  • int:<data_value>: integer values represented using a color palette, which can be:

    • an integer value;

    • an expression based on the variables defined in Point Keys, such as id or cell, which allows to define individual values;

    • file(<file_name>): individual values to load from a Data File.

  • real:<data_value>: real values represented using a smooth color scale, which can be:

    • a real value;

    • an expression based on the variables described in Point Keys, such as x or y, which allows to define individual values;

    • file(<file_name>): individual values to load from a Data File.

See also option -datapointcolscheme.

Default value: gray.

-datapointcolscheme <col_scheme>

Specify the color scheme used to get colors from the data loaded with option -datapointcol. The type of color scheme depends on the type of data.

Default value: palette for integer values and viridis for real values.

-datapointtrs <transparency>

Specify the transparency of the points (a value from 0 to 1), which can be:

  • a real value;

  • file(<file_name>): individual values to load from a Data File.

Default value: 0.

-datapointscale <scale>

Specify the scale relative to the -datapointcol real data, which can be:

  • <min>:<max>: minimal and maximal values;

  • <min>:<inter1>:...:<max>: minimal, intermediate and maximal values.

When only minimal and maximal values are specified, the scale ticks are set automatically. When intermediate values are specified, the scale ticks are the specified values.

The scale ticks have the same format as the minimal value.

Default value: <data_minimum>:<data_maximum>.

-datapointscaletitle <title>

Specify the title of the scale relative to the -datapointcol real data.

Default value: -.

-datapointcoo <coo>

Specify the coordinates of the points, which can be done in two main different ways.

Coordinates can be specified directly as follows:

  • file(<file_name>): individual coordinates to load from a Position File.

Coordinates can be set from data using an argument of the general form <data_type>:<data_value>:

  • disp:file(<file_name>): individual displacements to load from a Data File (formatted as a Position File);

  • coo: load coordinates from the simulation directory and step specified in input.

Default value: -.

-datapointcoofact <fact>

Specify the value of the scaling factor to apply to the displacements of the points.

Default value: 1.

-datapointrad <rad>

Specify the radii (and shapes) of the points, which can be:

  • a real value;

  • file(<file_name>): individual values to load from a Data File (not for *edge*).

  • cube:file(<file_name>): cubes of properties to load from a Data File. The file must contain, for each point, the radius (half of the edge length) and the coordinates of the three axes (which also is the rotation matrix that brings the reference axes into coincidence with the cube axes).

  • cylinder:file(<file_name>): cylinders of properties to load from a Data File. The file must contain, for each point, the radius, the length and the coordinates of the axis.

  • arr:file(<file_name>): arrows of properties to load from a Data File. The file must contain, for each point, the radius, the length and the coordinates of the axis.

  • disc:file(<file_name>): discs of properties to load from a Data File. The file must contain, for each point, the radius and the coordinates of the axis.

  • ell:file(<file_name>): ellispoids of properties to load from a Data File. The file must contain, for each point, the three radii and the coordinates of the three axes.

  • tor:file(<file_name>): torus of properties to load from a Data File. The file must contain, for each point, the major radius (center to center line), the minor radius and the coordinates of the normal axis.

Default value: point set dependent.

-datapointedgerad <rad>

Specify the radius of the point edges (represented as symbols), which can be any real value (\(\geq0\)).

Default value: 0.

-datapointedgecol <color>

Specify the color of the point edges (represented as symbols), which can be a color as described in Colors and Color Maps.

Default value: black.

Coordinate System Rendering

-datacsyscoo <coo_x>:<coo_y>:<coo_z>

Specify the coordinates of the origin of the coordinate system.

Default value: 0:0:0.

-datacsyslength <length>

Specify the length of the coordinate system axes.

Default value: 0.2.

-datacsysrad <rad>

Specify the radius of the coordinate system axes.

Default value: 0.01.

-datacsyslabel <label_x>:<label_y>:<label_z>

Specify the labels of the coordinate system axes.

Default value: X1:X2:X3.

-datacsyscol <color>

Specify the color of the coordinate system, which can be a color as described in Colors and Color Maps.

Default value: 32:32:32.

-datacsysfontsize <size>

Set the font size of the labels of the coordinate system axes.

Default value: 1.

Slice Settings

-slicemesh <plane1>,<plane2>,...

Plot one (or several) slice(s) of the mesh. A slicing plane is defined by its equation, such as x=0 or 0.12*x+0.34*y+0.56*z=0.78.

Default value: -.

Show Settings

The following options apply to the full tessellations, mesh or points.

-show{tess,tesr,mesh,meshslice,point,csys} <logical>

Show or hide a full tessellation, mesh, etc.

Default value: 1 for the more informative data (mesh slice \(>\) mesh \(>\) tessellation) and 0 for others.

The following option applies to a tessellation or a raster tessellation.

-show{cell,poly,face,edge,ver,seed,crystal,faceinter,vox} <logical>

Specify the entities to show. The argument can be:

For faces, etc., cell_shown and poly_shown can also be used.

Default value: all for cells and edges, none for others.

The following options apply to the entities of the mesh. The options apply to 3D elements (elt3d) and element sets (elset3d), 2D elements (elt2d) and element sets (elset2d), 1D elements (elt1d) and element sets (elset1d), 0D elements (elt0d) and element sets (elset0d), and nodes (nodes). Also note that the elt and elset can be used to denote the highest-dimension elements and elsets.

-show{elt,elset,elt{0-3}d,elset{0-3}d,node} <logical>

Specify the entities to show. The argument can be:

  • 1 or all for all;

  • an expression based on the keys listed in Mesh Keys, which allows to define individual values;

  • file(<file_name>): individual values to load from a Data File;

  • 0 or none: none.

Default value: 1 if highest mesh dimension is 3 and 0 otherwise.

Camera Settings

-cameracoo <coo_x>:<coo_y>:<coo_z>

Specify the coordinates of the camera. The coordinates can be defined as expressions based on the following variables:

  • x, y and z: the center of the tessellation or mesh (if both a tessellation and a mesh have been loaded, the mesh is considered);

  • length: the average length of the domain (1 for a unit cube);

  • vx, vy and vz: the coordinates of the shift vector, which are equal to 3.462, -5.770 and 4.327, respectively in 3D, and 0, 0 and 8, respectively, in 2D.

Default value: x+length*vx:y+length*vy:z+length*vz.

-cameralookat <coo_x>:<coo_y>:<coo_z>

Specify the coordinates of the camera look-at point. The coordinates can be defined as expressions based on the following variables:

  • x, y and z: the center of the tessellation or mesh (if both a tessellation and a mesh have been loaded, the mesh is considered).

Default value: x:y:z.

-cameraangle <angle>

Specify the opening angle of the camera along the horizontal direction (in degrees).

The opening angle along the vertical direction is determined from the opening along the horizontal direction and the image size ratio.

Default value: 25.

-camerasky <dir_x>:<dir_y>:<dir_z>

Specify the sky vector of the camera (vertical direction of the image).

Default value: 0:1:0 in 2D and 0:0:1 in 3D.

-cameraprojection <projection>

Specify the type of projection of the camera, which can be perspective or orthographic.

Default value: orthographic for 2D and perspective for 3D.

Scene Settings

-scenebackground <color>

Specify the color of the background, which can be any color as described in Colors and Color Maps.

Default value: white.

-sceneshadow <logical>

Specify whether the scene should include shadows.

Default value: 0 in 2D and 1 in 3D.

Output Image Settings

-imagesize <size_x>,<size_y>

Specify the size of the image (in pixels).

Default value: 1200:900.

-imageantialias <logical>

Specify whether antialiasing (which produces a smoother image) should be used.

Default value: 1.

-imageformat <format1>,<format2>,...

Specify the format(s) of the output image(s), which can be:

  • png: the PNG format;

  • pov: the POV-Ray format;

  • pov:objects: the POV-Ray format, but containing only the objects (the resulting file can be loaded with -includepov, not compatible with png);

  • vtk: the VTK format.

Default value: png.

Scripting

-loop <variable> <initial_value> <increment_value> <final_value> <commands> -endloop

Create a loop of commands, as in -loop Z 0.1 0.1 0.9 -slicemesh "z=Z" -print zZ -endloop.

Default value: -.

Output Options

-outdir <dir1>,<dir2>,...

Specify the output directories (the first valid one is used), which can be:

  • a custom directory;

  • sim_dir: the standard location of the simulation directory, <dir.sim>/images/, where <format> is the image format (see option -imageformat). sim_dir is only valid if a simulation directory is loaded as input.

For example, to write to a simulation directory when loaded as input and to the local directory in other cases, sim_dir,. (which may be placed in the initialization file).

Default value: ..

Advanced Options

-includepov <file_name1>[:<transformation1>:<transformation2>:...],<file_name2>,...

Include objects to the image under the form of POV-Ray files and optionally apply it a transformation. A transformation can be:

  • translate(<dist_x>,<dist_y>,<dist_z>): translate by distances <dist_x>, <dist_y> and <dist_z> along x, y and z, respectively;

  • scale(<fact_x>,<fact_y>,<fact_z>): scale by <fact_x>, <fact_y> and <fact_z> along x, y and z, respectively;

  • rotate(<theta_x>,<theta_y>,<theta_z>): rotate by angles thetax, thetay and thetaz about x, y and z.

    The rotation is read in POV-Ray style; i.e., according to the POV-Ray documentation:

    Note that the order of the rotations does matter.  Rotations occur about the x-axis
    first, then the y-axis, then the z-axis.  If you are not sure if this is what you
    want, then you should only rotate on one axis at a time using multiple rotation
    statements to get a correct rotation.  Rotation is always performed relative to the
    axis. Thus, if an object is some distance from the axis of rotation, it will not only
    rotate but it will orbit about the axis as though it was swinging around on an
    invisible string.  POV-Ray uses a left-handed rotation system. Using the famous
    "Computer Graphics Aerobics" exercise, you hold up your left hand and point your thumb
    in the positive direction of the axis of rotation.  Your fingers will curl in the
    positive direction of rotation.  Similarly, if you point your thumb in the negative
    direction of the axis, your fingers will curl in the negative direction of
    rotation.
    

Default value: -.

Output Files

  • .png: PNG file, a bitmapped image (the alpha channel is off);

  • .pov: POV-Ray file, a POV-Ray script file;

  • .vtk: a VTK file, for interactive visualization.

A PNG image can be obtained from a POV-Ray file by invoking POV-Ray as follows (see the POV-Ray documentation for details and further commands):

$ povray <file.pov> +W<image_width>+H<image_height> -D +A0.2

Examples

Below are some examples of use of neper -V.

  • Print out tessellation n10-id1.tess with cells colored from their identifiers and an image size of 900 x 450 pixels:

    $ neper -V n10-id1.tess -datacellcol id -imagesize 900:450 -print img
    
  • Print out tessellation n10-id1.tess with cells colored from crystal orientations and semi-transparency:

    $ neper -V n10-id1.tess -datacellcol ori -datacelltrs 0.5 -print img
    
  • Print out mesh n10-id1.msh with elements colored from scalar values written in file v and a scale ranging from 0 to 100:

    $ neper -V n10-id1.msh -dataeltcol "real:file(v)" -dataeltscale 0:100 -print img
    
  • Print out mesh n10-id1.msh with elements colored from nodal scalar values written in file v and a scale ranging from 0 to 100:

    $ neper -V n10-id1.msh -datanodecol "real:file(v)" -dataeltcol from_nodes -dataeltscale 0:100 -print img
    
  • Print out the 10 first cells of a 100-cell tessellation, colored from their identifiers and semi-transparency, and with edges shown in red and vertices shown as green spheres of radius 0.01:

    $ neper -V n100-id1.tess -showcell "id<=10" -datacellcol id -datacelltrs 0.5 -showedge cell_shown -showver cell_shown -dataverrad 0.01 -dataedgecol red -datavercol green -print img
    
  • Print out the interior element sets of mesh n100-id1.msh and show the 1D elements:

    $ neper -V n100-id1.tess,n100-id1.msh -dataelsetcol id -showelset 'body>0' -showelt1d elt3d_shown -print img
    
  • Print out 3 slices of mesh n100-id1.msh:

    $ neper -V n100-id1.msh -dataelsetcol id -slicemesh "x=0.5:y=0.5:z=0.5" -print img
    
  • Print out slices of mesh n100-id1.msh, at z coordinates ranging from 0.1 to 0.9 by step of 0.1, each slice being printed in a separate file:

    $ neper -V n100-id1.msh -dataelsetcol id -loop Z 0.1 0.1 0.9 -slicemesh "z=Z" -print imgZ -endloop
    
  • Print out a deformed mesh colored by orientations, defined from a simulation directory:

    $ neper -V mysim.sim -step 10 -datanodecoo coo -dataeltcol ori -print img
    
  • Print out a deformed mesh colored by orientations, defined from a simulation directory; generate an image at each deformation step:

    $ neper -V mysim.sim -loop STEP 0 1 10 -step STEP -datanodecoo coo -dataeltcol ori -print imgSTEP -endloop
    
1

It currently only affects the arguments of -datapointrad.