The simplest solution is to use the HyperWorks Solver Run Manager. Several runs can be chained one after each other by creating a script file with all the commands to execute; when executing the script, these commands will execute one after each other. In case of a UNIX or Linux system, write on the first line of a file: #! /bin/csh This means that this script will be read by the csh interpreter. Then write the commands for running the computations. Below is an example of a so-called “my_script” script file.
#!/bin/csh
setenv RADFLEX_PATH $ALTAIR_HOME/hwsolvers/bin/linux32/
cd case1 s_11.0_p4linux9 -i CASE1_0000.rad e_11.0_p4linux9 -i CASE1_0001.rad e_11.0_p4linux9 -i CASE1_0002.rad
cd case2 s_11.0_p4linux9 -i CASE2_0000.rad e_11.0_p4linux9 -i CASE2_0001.rad
Then provide the rights for executing this file, as follows: chmod +x my_script Finally, execute the script file with the command: ./my_script The same method applies for Windows. Write the commands to execute into a script file (do not set the line #! /bin/csh which stands for UNIX), rename the script file with the extension .bat and set the rights to execute it. |
Check the RADIOSS version used in the listing file (Runname_0000.out from V9; Runname_0000.lis in V5; RunnameL00 in V4) for RADIOSS Starter and in the listing file (Runname_nnnn.out from V9; Runname_nnnn.lis in V5; RunnameLnn in V4) for RADIOSS Engine. In the header of these files, the RADIOSS version used, few key hints on hardware and the parallelism type are mentioned. Example:************************************************************************ ** ** ** ** ** RADIOSS ENGINE 11.0 ** ** ** ** Non-linear Finite Element Analysis Software ** ** from Altair Engineering, Inc. ** ** ** ** ** ** LINUX 64 bits, Intel compiler, Platform MPI ** ** ** ** ** ** ** ** Build tag: 0520876_87230000_20010 ** ************************************************************************ ** COPYRIGHT (C) 1986-2010 Altair Engineering, Inc. ** ** All Rights Reserved. Copyright notice does not imply publication. ** ** Contains trade secrets of Altair Engineering Inc. ** ** Decompilation or disassembly of this software strictly prohibited. ** ************************************************************************
NUMBER OF SPMD DOMAINS 2NUMBER OF THREADS PER DOMAIN 2NUMBER OF HMPP PROCESSES 4COMPUTATION HARDWARE DESCRIPTIONCPU# HOSTNAME CPU TYPE, FREQUENCY AND MEMORY1 neo Genuine Intel(R) CPU 000 @ 3.07GHz (x86_64), 3066 MHz, 11880 MB RAM, 32765 MB swap2 neo Genuine Intel(R) CPU 000 @ 3.07GHz (x86_64), 3066 MHz, 11880 MB RAM, 32765 MB swap************************************************************************
Comments
|
On *_0000.out file: See Also: |
|
For RADIOSS SPMDThe number of processors has to be defined in command line argument (see Command Line Arguments) by option –nspmd (or –np). It is used by RADIOSS Starter for the "Domain Decomposition". The same number of processors must be input as a MPI parameter when RADIOSS Engine is launched. Example:[user@machine]$ ./s_11.0_linux964 -nspmd 4 [user@machine]$ mpirun -np 4 ./e_11.0_linux64 plmpi -nt 2 -input CRA2V51_0001.rad
For RADIOSS SMPDefine the number of SPMD domains to 1, and then define the number of threads by domain to a value > 1 (see Command Line Arguments for details). Check if the number of processor is correctly set by looking at the RADIOSS Engine display (standard output or listing file (Runname_0001.out, Runname_0001.lis or RunnameLnn):
************************************************************************ ** ** ** ** ** RADIOSS ENGINE 11.0 ** ** ** ** Non-linear Finite Element Analysis Software ** ** from Altair Engineering, Inc. ** ** ** ** ** ** Linux 64 bits, Intel compiler, Platform MPI ** ** ** ** ** ** ** ** Build tag: 0520876_87230000_20010 ** ************************************************************************ ** COPYRIGHT (C) 1986-2010 Altair Engineering, Inc. ** ** All Rights Reserved. Copyright notice does not imply publication. ** ** Contains trade secrets of Altair Engineering Inc. ** ** Decompilation or disassembly of this software strictly prohibited. ** ************************************************************************
NUMBER OF SPMD DOMAINS 1 NUMBER OF THREADS PER DOMAIN 2 NUMBER OF HMPP PROCESSES 2 COMPUTATION HARDWARE DESCRIPTION CPU# HOSTNAME CPU TYPE, FREQUENCY AND MEMORY 1 neo Genuine Intel(R) CPU 000 @ 3.07GHz (x86_64), 3066 MHz, 11880 MB RAM, 32765 MB swap 2 neo Genuine Intel(R) CPU 000 @ 3.07GHz (x86_64), 3066 MHz, 11880 MB RAM, 32765 MB swap ************************************************************************
The number of processors has to be defined in Command Line Arguments by option: -nthread [INTEGER] or -nt [INTEGER] at starter.
Example:[user@machine]$ ./s_11.0_linux964 -nt 2 -i CRA2V51_0000.rad
The number of processors must be the same when launch engine and is defined in command line argument (see Command Line Arguments) by option: -nthread [INTEGER] or -nt [INTEGER] at starter.
[user@machine]$ mpirun -np 1 ./e_11.0_linux64 -nt 2 -input CRA2V51_0001.rad |
OUT OF SPACE IN DOMAIN DECOMPOSITION(8) PLEASE INCREASE MEMORY FOR THE DOMAIN DECOMPOSITIONThis message means that RADIOSS Starter is not able to process domain decomposition with the default amount of memory allocated (SPMD computation). The needed memory is computed by RADIOSS Starter before the model decomposition. In most cases it is enough; but for complex meshes and a lot of connectivity (for example: a model with a lot of solid elements), this memory allocation has to be increased. This can be done by setting the Dkword value in the fourth field of the option /SPMD: /SPMD
|
Before running RADIOSS it is important to properly define the amount of stacksize memory. Under Linux and UNIX, stacksize must be defined as unlimited.
limit stacksize unlimited
ulimit –s unlimited Additionally, in case of running RADIOSS SMP with more than one thread (OMP_NUM_THREADS is greater than one), it is important to define an additional environment variable KMP_STACKSIZE, which defines the per thread stacksize. Under Linux and UNIX, the recommended value is 512 Mbytes.
setenv KMP_STACKSIZE 512m
export KMP_STACKSIZE=512m Under Windows, the recommended value is 64 Mbytes.
Then, any new shell running RADIOSS will have the environment variable KMP_STACKSIZE defined to 64m. Below is a summary of the recommended values automatically set by HyperWorks when running RADIOSS from a standard HyperWorks installation:
|
HyperWorks installs a Start menu option for the HyperWorks Solver Run Manager, which can be copied to the desktop or to a Quick Start Toolbar (right-click and copy from the Start menu). It does not matter which menu item is copied (OptiStruct, RADIOSS, or MotionSolve); the same utility will be called, and any solver can be launched with it. The desktop icon can then be used to:
|
The same utility which is available on Windows to start HyperWorks Solver Run Manager is also available on all supported platforms, but there is no interactive menu to start it from. There is the option to start this utility from the command line: $ALTAIR_HOME/scripts/radioss -gui It is possible to create a desktop icon with the same functionality as on Windows (used for double-click launch and for drag-and-drop launch). The exact procedure is system-dependent, and details will be provided in your UNIX/Linux manual, but it should be similar on most hosts. Here is an example showing Linux with the Gnome desktop environment:
The following form will appear:
<install_dir>/scripts/hw_wish <install_dir>hwsolvers/scripts/hwsolver.tcl -icon where, <install_dir> is the top directory path to HyperWorks installation.
Higher resolution images are also available from <install_dir>/hwsolvers/scripts/.
You can move this icon to a preferred position, and even copy it to the toolbar. When creating the icon directly on the toolbar, the menu choices are Add to panel > Custom Application Launcher, and the same form is used, as shown above. |
If a RADIOSS Optimization problem has are more than 1 engine (multiple engines) in the RADIOSS model, running the RADIOSS model completely during optimization iteration with option –rnt is recommended. In the absence of the –rnt option, hwsolver.tcl forces the RADIOSS_STARTER and RADIOSS_ENGINE environment variables to point to the specific executables. Then only the first RADIOSS Engine file will be executed. Example: |