s9-1 adm704-705, section 9, august 2005 copyright 2005 msc.software corporation section 9 command...

S9-1ADM704-705, Section 9, August 2005Copyright 2005 MSC.Software Corporation

SECTION 9

COMMAND LANGUAGE


COMMAND LANGUAGE

What’s in this section: General Structure Getting Familiar with Commands Types of Commands


GENERAL STRUCTURE

Syntax rules for commands

Comment lines are allowed by placing an exclamation point (!) as the first character on the line.

Continuation of a command is denoted by an ampersand (&) at the end of a line.

Abbreviations are allowed, as long as they are unique.


GENERAL STRUCTURE (CONT.)

Examples: One “gotcha” when writing command files is that the last line might not

get executed. Therefore, make it a habit of making the last line a comment character (!).

marker delete marker_name=.mod1.par4.mar27 marker delete & marker_name=.mod1.part4.mar27 mar del mar=.mod1.par4.mar27 mar del mar=mar27


GENERAL STRUCTURE (CONT.)

Syntax rules for values The rules for entering values are:

Values can contain letters, numbers, and underscore characters.

They must begin with a letter or underscore character.

Values can contain any characters that are enclosed by double quotation marks.

They must have separators (blank space or tab) between keywords and parameters. Placing separators between parameters and their values is optional.

All parameter values of type string should be enclosed in double-quotes (“).

All parameter values of type object will accept the full database name or the relative object name, provided it is unique in the database.


GETTING FAMILIAR WITH COMMANDS

Command Navigator

Command Window

Log file



Command Navigator Enables you to browse through the ADAMS/View command

language and execute commands. The entire ADAMS/View command language is accessible through the

Command Navigator.

Use the Command Navigator to navigate on keywords.

Double-clicking the last keyword of a command displays a dialog box of parameter names and parameter values.



Example:



Command Window Text-based way to enter commands. Assumes that you understand

the ADAMS/View command language.



Command History Use the up and down arrows on your keyboard to scroll through

previously executed commands.

Command Expansion Use a question mark (?) or the Esc key for help with completing

commands: Completes keywords or parameter names.

Prompts for keywords or parameter names.

Prompts for parameter values.



Log file A file named aview.log is saved during each ADAMS/View session. In

the vertical applications, it is called acar.log, aengine.log, and arail.log.

Contains commands that you entered and messages you received. The log file for the previous session is aview.log% on UNIX and

aview.log on Windows.


TYPES OF COMMANDS

ADAMS/View commands can be categorized as follows:

Model-based Examples:

marker create marker_name=mar1 location=2,0,0 marker modify marker=mar1 orientation=0d,90d,0d

Interface-based (GUI) Example:

interface dialog_box display &

dialog_box_name = .gui.db_beam_size &

parameters=”$f_beam_name”


TYPES OF COMMANDS (CONT.)

Conditional constructs ADAMS/View command language contains commands for creating

conditional constructs and loops. BREAK CONTINUE IF/ELSEIF/ELSE/END FOR/END RETURN WHILE/END


TYPES OF COMMANDS (CONT.)

file text write This command writes information from ADAMS/View into a text file.

You control the format of the output and, using database access expressions, you can write any model or simulation data from the ADAMS/View database.

Note: For more information on the file text write command, see Knowledge Base Article 7017 available at: http://support.adams.com/kb/faq.asp?ID=7017. This command is also documented in the online help.

s9-1 adm704-705, section 9, august 2005 copyright 2005 msc.software corporation section 9 command...

Documents