save computational results in different formats
MESHFREE allows to save results to different file formats, see SAVE_format. The user can save multiple formats at once. If multiple values for SAVE_path are specified, everything is stored in all given locations.
The output frequency is defined via SAVE_choose_meth, SAVE_first, and SAVE_interval. In the example below, the output frequency for all three output formats is changed after 999 timesteps.
All file formats will always save the point coordinates. For some formats additional variables like normals are saved through specifications in the SAVE_format. Other simulation variables need to be specified through SAVE_ITEM statements. For more specialized options, see the links at the bottom.
The location for output is specified through SAVE_file and SAVE_path.
Example:For saving different file formats or multiple saves with different SAVE parameters, one can alternatively use the experimental begin_save{ environment, which allows for a more intuitive handling of these cases.
List of members: | |
---|---|
BE_MAP | Define mapping from points to BE |
begin_save{ | Experimental handling of multiple save formats |
SAVE_atEndOfTimestep | choose to save data for visualization at the end of time steps instead of at the start (UCV) |
SAVE_BE_filter | Filtering of boundary elements via expression |
SAVE_BE_ITEM | item of BE surfaces to be saved for visualization |
SAVE_BE_MONITOR_ITEM | monitor item to be saved per BE element for visualization |
SAVE_BE_NODE_ITEM | item of BE nodes to be saved for visualization |
SAVE_choose_meth | save computational results in different formats |
SAVE_CoordinateSystem | saving relative to specified coordinate system (movement) |
SAVE_file | file name for the results |
SAVE_filter | (Experimental) Filtering of saved Pointcloud via expression |
SAVE_first | control first save |
SAVE_format | format to save simulation data |
SAVE_interval | control saving frequency |
SAVE_ITEM | item to be saved for visualization |
SAVE_MONITOR_ITEM | monitor item to be saved for visualization |
SAVE_path | absolute or relative path for the simulation results |
SAVE_PID_ITEM | PID item to be saved for visualization |