Parallel Analysis¶
Execution Flow¶
Figure 3.1.3 shows the execution flow for multiprocessor parallel processing using FrontISTR.
Figure 3.1.3 Execution flow for parallel processing
Input Files to Prepare¶
(1) Overall Control Data (extension dat)¶
This file specifies the input files for mesh data and analysis control data, as well as the analysis result output file. The file name is fixed as hecmw_ctrl.dat.
An example of the overall control data is shown below. In this example, hecmw_part first reads the single-domain mesh data model.msh and writes the distributed-domain mesh data model_8.0 through n. FrontSTR reads the distributed-domain mesh data model_8.0 through n and the analysis control data model.cnt, and writes the analysis result data model.res.0 through n.1. In addition, hecmw_vis reads the distributed-domain mesh data model_8.0 through n and analysis result data model.res.0 through n.1, and writes model_vis_psf.0000.(extension) corresponding to the specified output. For details, see the Keyword Reference (Overall Control Data).
(2) Single-Domain Mesh Data (extension msh)¶
This file defines the overall mesh configuration of the analysis target, material data, group data used in the analysis control data, and other 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 visualizer control data. Examples of analysis control data are shown in Chapter 3. For details, see the Keyword Reference (Analysis Control Data).
(4) Domain Decomposition Utility Control Data (extension dat)¶
This file specifies the control data for hecmw_part. The file name is fixed as hecmw_part_ctrl.dat. An example of domain decomposition utility control data is shown below. In this example, a single domain is divided into 8 domains using the PMETIS domain decomposition method. The file model_8.inp is also output for displaying the mesh after domain decomposition. For details, see the hecmw1 documentation (0803_001x_hecmw_part_201_users.pdf).
(5) Visualization Control Data (extension ini)¶
This file specifies the 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) are output. For details, see !visual and !OUTPUT_VIS in the keyword reference.
Execution Method¶
Run hecmw_part from the directory containing the input files using the following command line.
Run FrontISTR from the directory containing the input files using the following command line. The method used to launch MPI processes must be adjusted to suit the execution environment.
Visualization can be executed in two ways. One is to run it as FrontISTR postprocessing. In this case, specify
!WRITE, VISUAL
in the analysis control data, and visualization is executed automatically. In this case, the visualization control data must be included in the analysis control data.
To perform visualization after FrontISTR execution has finished, first specify
!WRITE, RESULT
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. The method used to launch MPI processes must be adjusted to suit the execution environment.
Output File Descriptions¶
(1) Domain Decomposition Utility Log File (extension log)¶
This file contains messages such as the progress of hecmw_part processing. The file name is fixed as hecmw_part.log.
(2) Distributed-Domain Mesh Files (no extension)¶
These files contain the domain-decomposed mesh configuration, material data, group data used in the analysis control data, and other information. One file is created for each distributed domain, and the files are named using the file header specified in the overall control data as follows.
Naming rule: (file header specified by !MESH).(distributed-domain number)
Example: model_8.0 through model_8.7
(3) Domain-Decomposed Mesh Display File (extension inp)¶
This file contains unstructured-grid data for displaying the domain-decomposed mesh. It can be displayed with MicroAVS and similar software.
(4) Analysis Result Message File (extension msg)¶
This file contains messages such as the progress of FrontISTR analysis. One file is created per execution, and the file name is fixed as FSTR.msg.
(5) Analysis Result Log Files (extension log)¶
These files contain analysis results for physical quantities at each FrontISTR node and element. They also contain maximum/minimum values of physical quantities and modal-analysis results. For dynamic analysis, the analysis results for all steps are output to these files. One file is created for each distributed domain, and the file name is fixed as n.log (where n is the distributed-domain number).
(6) Analysis Result Files (no extension)¶
These files are output when the !WRITE, RESULT option is specified.
These files contain analysis results for physical quantities at each FrontISTR node and element. A file is generated for each distributed domain and each step, and the files are named using the file header specified in the overall control data as follows.
Naming rule: (file header specified by !RESULT).(distributed-domain number).(step number)
Example: model_8.res.0.1 through model_8.res.7.1
(7) Analysis Result Bitmap Files (extension bmp)¶
These files are output when specified in the visualization control data.
These files contain bitmap data generated by the visualization processing. File names are assigned 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).
(8) Analysis Result Unstructured-Grid Data Files (extension inp)¶
These files are output when specified in the visualization control data.
These files can be used for postprocessing with REVOCAP_PrePost, MicroAVS, and similar software. They are named 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
(9) Analysis Result Neutral Files (extension neu)¶
These files are output when specified in the visualization control data.
These files can be used for postprocessing with Femap. They are named 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.0 through n files are also output, but these are for debugging and normally do not need to be referenced.