HyperWorks Solvers

Syntax of Starter Keywords

Syntax of Starter Keywords

Previous topic Next topic Expand/collapse all hidden text  

Syntax of Starter Keywords

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

This section describes the general syntax rules for writing a RADIOSS Block Format input deck:

compulsory keywords
types of keywords
input format according to the type of keyword and data

These rules apply to all the options, which are individually defined in this manual.

Block Format


The first line of the input deck must be the header line. All other blocks may be input in any order.

It is possible to use the free block input format.

Each block defines one option, a set of flags or switches, or a set of nodes or elements.

Each block begins with a forward slash (/), followed by a keyword and ends at the beginning of the next block.

The input deck finishes with the /END keyword.

The order in which the blocks are entered is completely free; except for:

//SUBMODEL (all what is between //SUBMODEL and //ENDSUB)
/TRANSFORM (applied in the order of the input, in case of multiple transform)
/END option

The content of each block is entered in fixed format (see below).

Blank lines at the end of each block are ignored.

Lines with a # in the first column are comment lines.

If the second line of a block is a comment line, HyperCrash will take it into account, keep it and rewrite it as a full part of the block.

There are four types of keywords described below.

General flags, switches, global parameters or title


Syntax

/KEYWORD

flag1            flag2           flag3 ...

 

Example:

/IOFLAG

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

Ipri

Irtyp

Igtyp

Ioutp

OutyyFMT

Irootyy

 

 

 

Irtyp_r

 

Option Definition

Syntax

/OPTION_KEYWORD[/SUBKEYWORD/…]/option_ID[/unit_ID]

option_title

option input …

The option_ID is defined and the option_title is associated to this option_ID in the first line.

If the same option is used several times, a different option_ID and a different option_title have to be used each time.

The option_title can have a maximum of 100 characters and must not start with a forward slash ( / ).

 

Example:

/IMPVEL/impvel_ID/unit_ID

impvel_title

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

fct_ID

Dir

skew_ID

sens_ID

grnd_ID

frame_ID

 

 

 

 

Fscalex

Fscaley

Tstart

Tstop

 

 

Options Without Self Identifier

Syntax

/OPTION_KEYWORD[/SUBKEYWORD/…]/reference_ID[/unit_ID]

option input

hmtoggle_plus1Example 1

/NODE/unit_ID

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

node_ID

Xc

Yc

Zc

 

 

 

The nodes can be defined in one or more blocks.

hmtoggle_plus1Example 2

/SHELL/part_ID

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

Ishell

node_ID1

node_ID2

node_ID3

node_ID4

 

 

 

Thick

In the above syntax, the part_ID is only used for element definition; but it is not defined in this block.

The part_ID's are defined in /PART option.

The list of elements belonging to one part can be defined in one or more blocks.

hmtoggle_plus1Example 3

/FAIL/Key/mat_ID/unit_ID

Submodel option

 

//SUBMODEL/submodel_ID/unit_ID

submodel_title

option input

//ENDSUB

 

Block Content Format


The content of any block is formatted in lines of 100 characters, divided into 10 fields of 10 characters. A typical input line is described in this manual as follows:

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

 

 

 

 

 

 

 

 

 

 

The first row of the table gives the fields number. The second row shows the variables description.

The fields used have a white background. All other fields and blank formats are reserved and must not be used. Users should not put comments in the unused fields, but instead should use comment cards beginning with a “#” or “$”.

All integers are given in one 10 digit field with a maximum of 9 digits.
All reals are entered in two fields with a maximum of 20 digits.
Characters can have variable length, the maximum length is given for each entry.
For boundary conditions, single-digit booleans (value 0 or 1) are used. The format is in this case, given by showing the place of each boolean in the field (see table below).

For example, on the line below the first field is defined as an integer, followed by six booleans, and then one real. The last six fields are unused. The position of the six booleans is given in the second table. A text is defined on a line (10 fields, 100 characters maximum).

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

Integer

Boolean

Real

 

 

 

 

 

 

 

(2)-1

(2)-2

(2)-3

(2)-4

(2)-5

(2)-6

(2)-7

(2)-8

(2)-9

(2)-10

 

 

 

VX

VY

VZ

 

symbol_w_14X

symbol_w_14Y

symbol_w_14Z

 

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

Character