A path and name for the simulation results must be given. This file name will be used for all output data files generated by MICRESS®.
In the following example, the base output file name is ReX3D.
Example: Output file names
... # Output Location # =============== # Options: [ <directory path>/ ] <base name> # The default result directory is the driving file location. Results/ReX3D # Overwrite files with the same name? # Options: overwrite write_protected append # [zipped|not_zipped|vtk] # [unix|windows|non_native] overwrite vtk # VTK output file format options? # Options: binary_unzip binary_zip ascii binary_unzip ...
All output files will have the name Rex3D with different file extensions. The different MICRESS® output files and the corresponding extensions are explained in chapter Output - Post Processing.
Three modes for writing outputs are available among which the user has to make a choice in the next line: In
overwrite mode, already existing results with the same name will be overwritten without warning (if the operating system allows the user to do that). With
write_protected, execution of the program will be stopped in this case and a warning is issued.
append option, finally, allows to append the new simulation results to already existing files. This is especially helpful if the restart option is used. A further optional keyword allows changing the file format for example from the native binary format to a standard vtk format, which is especially interesting in case of 3D simulations (see example).
If the user specifies, as outlined in the example, the additional parameter VTK then VTK solution files are written according to the chosen format output option: either
ascii. Note that option
ascii will lead to large result files and is not recommended in the case of large 3-D industrial applications.