Serial Analysis¶

Execution Flow¶

Figure 3.1.2 shows the execution flow for single-processor serial processing using FrontISTR.

Figure 3.1.2 Serial execution flow

Input Files to Prepare¶

(1) Global Control Data (dat extension)¶

This file specifies the input files for mesh data and analysis control data, as well as the output file for analysis results. The filename is fixed as hecmw_ctrl.dat.

An example of global 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 the 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 (Global Control Data).

(2) Single-domain Mesh Data (msh extension)¶

This file defines the overall mesh configuration of the analysis model, material data, group data used by the analysis control data, and related information. For details, see the Keyword Reference (Mesh Data).

(3) Analysis Control Data (cnt extension)¶

This file defines the analysis type, displacement boundary conditions, load boundary conditions, and other settings. It also specifies solver control data and visualizer control data. Examples of analysis control data are presented in Chapter 3. For details, see the Keyword Reference (Analysis Control Data).

(4) Visualization Control Data (ini extension)¶

This file specifies control data for hecmw_vis. The default filename is hecmw_vis.ini. An example of visualization control data is shown below. In this example, unstructured-grid data for MicroAVS (inp extension) 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.

fistr1

Visualization can be performed in two ways. One is to run it as post-processing from FrontISTR by specifying the following in the analysis control data:

!WRITE, VISUAL

This causes visualization to run automatically. 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:

!WRITE, RESULT

Then run FrontISTR.

After FrontISTR finishes, run hecmw_vis from the directory containing the input files and analysis result files using the following command:

hecmw_vis1

Output Files¶

(1) Analysis Result Message File (msg extension)¶

This file contains messages such as the progress of the FrontISTR analysis. One file is created per run, and its filename is fixed as FSTR.msg.

(2) Analysis Result Log File (log extension)¶

This file contains analysis results for physical quantities at each node and element in FrontISTR. It also includes maximum/minimum values of physical quantities and modal-analysis results. For dynamic analysis, the results of all steps are output to this file. One file is created per run, and its filename 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 node and element in FrontISTR. A file is generated for each step, and its filename is formed using the file header specified in the global control data as follows.

Naming convention: (file header specified by !RESULT).0.(step number)

Example: model.res.0.1

(4) Analysis Result Bitmap File (bmp extension)¶

This file is output when specified in the visualization control data.

This file contains bitmap data generated by visualization processing. The filename is formed using the file header specified in the global control data. For details of the naming convention, see the hecmw1 document (0803_001f_hecmw_PC_cluster_201_vis.pdf).

(5) Analysis Result Unstructured-grid Data File (inp extension)¶

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 tools. Its filename is formed using the file header specified in the global control data as follows.

Naming convention: (file header specified by !RESULT)_psf.(step number).inp

Example: model_vis_psf.0000.inp

(6) Analysis Result Neutral File (neu extension)¶

This file is output when specified in the visualization control data.

This file can be used for post-processing with Femap. Its filename is formed using the file header specified in the global control data as follows.

Naming convention: (file header specified by !RESULT)_psf.(step number).neu

Example: model_vis_psf.0000.neu

Note: FSTR.dbg is also output, but it is intended for debugging and normally does not need to be referenced.