Parallel Analysis¶
Execution Flow¶
Figure 3.1.3 shows the execution flow for multiprocessor parallel processing using FrontISTR.
Figure 3.1.3 Parallel-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, hecmw_part first reads the single-domain mesh data model.msh and writes the distributed-domain mesh data model_8.0 through n. FrontISTR reads the distributed-domain mesh data model_8.0 through n and 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) 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) Partitioning Utility Control Data (extension dat)¶
This file specifies control data for hecmw_part. The file name is fixed as hecmw_part_ctrl.dat. An example of partitioning utility control data is shown below. In this example, the PMETIS partitioning method divides a single domain into eight domains. The file model_8.inp is also output for displaying the partitioned mesh. For details, see the hecmw1 documentation (0803_001x_hecmw_part_201_users.pdf).
(5) 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 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 for launching MPI processes must be adjusted to the execution environment.
Visualization can be performed in two ways. To run it automatically as FrontISTR post-processing, specify
!WRITE, VISUAL
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
!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 for launching MPI processes must be adjusted to the execution environment.
Output File Descriptions¶
(1) Partitioning Utility Log File (extension log)¶
This file contains messages such as the progress of hecmw_part processing. Its file name is fixed as hecmw_part.log.
(2) Distributed-Domain Mesh Files (no extension)¶
These files contain the partitioned mesh configuration, material data, group data used in the Analysis Control Data, and related 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) Partitioned-Mesh Display File (extension inp)¶
This file contains unstructured-grid data for displaying the partitioned 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 the FrontISTR analysis. One file is created per execution, and its 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 and minimum values of physical quantities and modal-analysis results. For dynamic analysis, the results for all steps are output to these files. One file is created for each distributed domain, and its 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 visualization processing. Their file names are 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).
(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 post-processing with REVOCAP_PrePost, MicroAVS, and similar software. Their file names are 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
(9) Analysis Result Neutral Files (extension neu)¶
These files are output when specified in the visualization control data.
These files can be used for post-processing with Femap. Their file names are 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.0 through n files are also output, but they are used for debugging and normally do not need to be referenced.