Serial Analysis¶
Execution Flow¶
Figure 3.1.2 shows the execution flow for single-processor serial processing using FrontISTR.
Figure 3.1.2 Serial-processing execution flow
Input Files to Prepare¶
(1) Overall Control Data (extension dat)¶
This file specifies the mesh-data and Analysis Control Data input files and the analysis-result output file. The file name is fixed as hecmw_ctrl.dat.
An example of Overall Control Data is shown below. In this example, FrontISTR reads the single-domain mesh data model.msh and Analysis Control Data model.cnt and writes the analysis result data model.res.0.1. In addition, hecmw_vis reads the single-domain mesh data model.msh and analysis result data model.res.0.1 and writes model_vis_psf.0000.(extension) according to the output specification. For details, see the Keyword Reference (Overall Control Data).
(2) Single-Domain Mesh Data (extension msh)¶
This file defines the complete mesh configuration of the analysis model, material data, group data used in the Analysis Control Data, and related information. For details, see the Keyword Reference (Mesh Data).
(3) Analysis Control Data (extension cnt)¶
This file defines the analysis type, displacement boundary conditions, load boundary conditions, and other settings. It also specifies solver control data and visualization control data. Chapter 3 provides examples of Analysis Control Data. For details, see the Keyword Reference (Analysis Control Data).
(4) Visualization Control Data (extension ini)¶
This file specifies control data for hecmw_vis. The default file name is hecmw_vis.ini. An example of visualization control data is shown below. In this example, unstructured-grid data for MicroAVS (extension inp) is output. For details, see !visual and !OUTPUT_VIS in the keyword reference.
Execution Procedure¶
Run FrontISTR from the directory containing the input files using the following command line.
Visualization can be performed in two ways. To run it automatically as FrontISTR post-processing, specify the following in the Analysis Control Data:
In this case, the visualization control data must be included in the Analysis Control Data.
To perform visualization after FrontISTR has finished, first specify the following in the Analysis Control Data:
and run FrontISTR.
After FrontISTR has finished, run hecmw_vis from the directory containing the input files and analysis result files using the following command line.
Output File Descriptions¶
(1) Analysis Result Message File (extension msg)¶
This file contains messages such as the progress of the FrontISTR analysis. One file is created per execution, and its file name is fixed as FSTR.msg.
(2) Analysis Result Log File (extension log)¶
This file contains analysis results for physical quantities at each FrontISTR node and element. It also contains maximum and minimum values of physical quantities and modal-analysis results. For dynamic analysis, the results for all steps are output to this file. One file is created per execution, and its file name is fixed as 0.log.
(3) Analysis Result File (no extension)¶
This file is output when the !WRITE, RESULT option is specified.
This file contains analysis results for physical quantities at each FrontISTR node and element. A file is generated for each step, and its file name is formed using the file header specified in the Overall Control Data as follows.
Naming rule: (file header specified by !RESULT).0.(step number)
Example: model.res.0.1
(4) Analysis Result Bitmap File (extension bmp)¶
This file is output when specified in the visualization control data.
This file contains bitmap data generated by visualization processing. Its file name is formed using the file header specified in the Overall Control Data. For details of the naming rule, see the hecmw1 documentation (0803_001f_hecmw_PC_cluster_201_vis.pdf).
(5) Analysis Result Unstructured-Grid Data File (extension inp)¶
This file is output when specified in the visualization control data.
This file can be used for post-processing with REVOCAP_PrePost, MicroAVS, and similar software. Its file name is formed using the file header specified in the Overall Control Data as follows.
Naming rule: (file header specified by !RESULT)_psf.(step number).inp
Example: model_vis_psf.0000.inp
(6) Analysis Result Neutral File (extension neu)¶
This file is output when specified in the visualization control data.
This file can be used for post-processing with Femap. Its file name is formed using the file header specified in the Overall Control Data as follows.
Naming rule: (file header specified by !RESULT)_psf.(step number).neu
Example: model_vis_psf.0000.neu
Note: FSTR.dbg is also output, but it is used for debugging and normally does not need to be referenced.