| 1. | All /PARAMETER/GLOBAL cards should be defined between the #RADIOSS Starter and /BEGIN cards of a master Starter file. |
| 2. | /PARAMETER/LOCAL cards can be specified and used only inside of a submodel (//SUBMODEL). Local parameter overwrites a global parameter definition with the same name inside of the submodel, where it is specified. Local parameters can be specified in any part of submodel, not necessary at the beginning. |
| 3. | Parameters with a name “ParName” can be referenced after /BEGIN card for global parameters and in any place of submodel for local parameters, using the syntax, &ParName. Multiple references of such parameters are possible. Comment lines, names of include files, and keywords cannot be used as parameters. |
| 4. | The &ParName input found after /BEGIN is replaced by the corresponding parameter value starting at “&” position and using: |
| • | 10 digits for an integer |
| • | 20 digits for a real value |
The character '&' can be used in the model only for referring parameters. It should not be used in card titles.
In the example below, a parameter named “TTF” is defined in the /PARAMETER card. The value of the parameter (10) is aligned to the left of the field. The parameter is used with an additional prefix “&”, in the /SENSOR card.
#RADIOSS STARTER
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/PARAMETER/GLOBAL/REAL/1
Time to fire
TTF 10
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
. . .
/BEGIN
. . .
/SENSOR/TIME/1
Airbag fire time use global parameter TTF=10.0
&TTF
. . .
//SUBMODEL/1
# sub-model title
submodel
# Off_dft Off_nod Off_elt Off_part Off_mat Off_prop
0 0 0 0 0 0
#include airbag_submodel.inc
//ENDSUB
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
. . .
/END
| ✍ | In include file “airbag_submodel.inc”: |
/PARAMETER/LOCAL/REAL/1
Time to fire
TTF 20
. . .
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/SENSOR/TIME/2
Use local parameter TTF, it is now covered to 20.0 inside include file
&TTF
. . .
#ENDDATA
|
| 5. | If the minus (-) sign is used before the prefix “&”, as follows: |
“-&ParName”
Then, the value of the parameter is multiplied by -1. In this case, ParName must not exceed 8 digits.
For example, if you need exchange external surface normal for airbag:
| • | Set parameter s_part=4 and specific “-&s_part” in surface definition, then a value of “-4” will be substituted for “-&s_part”. -> shell normal reversed. |
| • | Set parameter s_part=-4 and specific “&s_part” in surface definition, then a value of “-4” will be substituted for “&s_part”. -> shell normal reversed. |
| • | Set parameter s_part=-4 and specific “-&s_part” in surface definition, then a value of “4” will be substituted for “-&s_part”. -> shell normal not reversed. |
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/PARAMETER/GLOBAL/INTEGER/8
surf part for airbag
s_part 4
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
. . .
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/SURF/PART/4
Airbag - surf normal of part 4 reversed with -4
2-&s_part 5 6 7 8
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/END
|
| 6. | The expression parameter cards, type /INT_EXPR or /REAL_EXPR accept parameters as arguments. These argument parameters should be defined before these expression parameter cards in the input deck. The expression results are calculated to a maximum accuracy of 12 digits. |
In the example below, parameters “MW” and “CPM” are defined before the expression parameter card type /REAL_EXPR. The expression parameter card (/4) calculates the value of CP which is equal to “CPM/MW”. The value MW1 cannot be used in this expression parameter card (/4) because it is defined after the /REAL_EXPR card. If “CPM/MW1” is specified in the expression parameter card (/4), the program runs into an error.
RADIOSS STARTER
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/PARAMETER/GLOBAL/REAL/2
Molar mass of inflating gas
MW .025
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/PARAMETER/GLOBAL/REAL/3
Cp heat constant molar
CPM 13
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/PARAMETER/GLOBAL/REAL_EXPR/4
Cp heat constant mass
CP CPM/MW
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/PARAMETER/GLOBAL/REAL/9
Molar mass of inflating gas
MW1 .024
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
|
| 7. | During the execution of the expression parameter types INT_EXPR or REAL_EXPR, RADIOSS Starter calls an external executable: templex. This program is available in the standard HyperWorks installation. The call to templex.exe is automatically managed by the RADIOSS Graphical User Interface (GUI) in the installation. |
| 8. | If the RADIOSS GUI is not used, the following environment variables need to be defined: |
| • | ALTAIR_HOME which points to the Altair directory, for example:
Windows: C:\Program Files\Altair\[version]
Linux: /opt/altair/[version]/altair |
| • | TEMPLEX_PATH
Windows: =%ALTAIR_HOME%\hw\bin\[win64]\
Linux: $ALTAIR_HOME/hw/bin/linux64/ |
| • | On Linux, update LD_LIBRARY_PATH with the following path: |
$ALTAIR_HOME/hw/tcl/tcl[version]/linux64/lib;$ALTAIR_HOME/hw/bin/linux64; $ALTAIR_HOME/hw/lib/linux64
Note: The fields within [] need to be updated with the correct values.
Create a text file mytest containing:
{test=1}
results={test}
Launch the newly created text file mytest using the templex executable:
Windows: %ALTAIR_HOME%\hw\bin\win64\templex.exe mytest
Linux: $ALTAIR_HOME/scripts/templex mytest
If it returns " results = 1", the environment has been correctly setup.
|
| 9. | Type could also be TEXT. |
In the example below, the string “ 1 1 0” is defined for TEXT parameter “var”. This parameter is used in part definition. The property ID 1 and material ID 1 have been set for part 5.
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/PARAMETER/GLOBAL/TEXT/7
text parameter for part 5
var
1 1 0
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
. . .
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/PART/5
Chamber_2_lower
&var
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
|
| 10. | TEXT type parameter can be stitched together with character “$”: |
 Example
Text parameter definition:
/PARAMETER/GLOBAL/TEXT/1
Update output
Name 12
EXAMPLE_TEXT
…….
Text parameter reference. Text parameter is stitched with text string “123456”:
/TH/NODE/2
&Name$123456
# var1 var2 var3 var4 var5 var6 var7 var8 var9 var10
DEF
# NODid Iskew NODname
5 0&Name$123456
After parameter replacement:
TH GROUP: 2,EXAMPLE_TEXT123456 , 6 VAR, 1 NODE :
-------------------
DX DY DZ VX VY VZ
NODE SKEW(OR FRAME) NAME
5 0 0EXAMPLE_TEXT123456
|
|
