control_print_gmsh

Syntax:

control_print_gmsh index switch

We discuss as an example the printed file naming convention if the input file name is excavation.dat.

If switch is set to -yes the results are printed into the excavation.msh file. In case the mesh (elements and nodes) have not been printed before in this file, the file will be emptied, and the mesh will be printed. This will also be done if the mesh is changed.

If index is 100 and switch is set to -separate_index then the mesh and results are printed in the file is excavation_100.msh.

If switch is set to -separate_sequential then the mesh and results are printed in the files excavation_0.msh, excavation_1.msh, etc. So each time that a control_print_gmsh with -separate_sequential is evaluated a new file is generated with number increased by one.

A dummy point element is put in each node in the gmsh file. Gmsh needs that for plotting vector fields in the nodes. The dummy element group 1234 is used for these dummy point elements.

You can suppress these dummy point elements by setting control_print_gmsh_dummy to -no.

All element data starts with element_ in the plots. All node data starts with node_ in the plots.

Scalar data with more then one value is given the extension _0, _1 etc. for each of the values. For example the record node (which contains coordinates in each space direction) is plotted as scalar node_0, node_1 and node_2 which contain the \(x\)-coordinate, \(y\)-coordinate and \(z\)-coordinate respectively. For example the record group_groundflow_permeability (which contains permeability in each space direction) is plotted as scalar group_groundow_0, group_groundow_1 and group_groundow_2 which contain the \(x\)-permeability, \(y\)-permeability and \(z\)-permeability respectively.

For nodes, the presence in geometries is plotted as node_geometry_*. For elements, the presence in geometries is plotted as element_geometry_*.

You can plot this file with the program Gmsh; see https://www.gmsh.info. You can also plot this file with the program Mecway; see https://mecway.com.

control_print_history

Syntax:

control_print_history index data_item_name_0 data_item_index_0 number_0 …

Print the time history for each of the sets data_item_name_0 data_item_index_0 number_0 …

For example, if -node_dof is used, number_0 is one of the names of dof_label (eg -velx).

For example, if -node_dof_calcul is used, number_0 is one of the names of post_calcul_label (eg -aept).

Otherwise, number_0 should be an integer specifying the number of the value in the record (for instance number 2 means the third value).

The following history is printed in the file node_dof_112_temp.his

Example:

control_print_history 0 -node_dof 112 -temp