ADAMS Command Language Guide 2012

(1)

(2)

Adams/View Commands

2

Using the Command Window

The command window provides text-based way to enter Adams/View commands. It assumes that you understand the Adams/View command language underlying the Adams/View interface.

About Adams/View Commands

The commands that you enter in the command window or select from the Command Navigator are made up of keywords, parameters for the keywords, and parameter values as shown below:

{keywords} {parameters=values} In a command:

• Keywords correspond to menu selections.

• Parameters correspond to dialog box choices.

• Parameter values correspond to values you enter or select in the dialog boxes.

For example, the following command contains the keyword constraint followed by other keywords, then by parameters, such as the name of the joint. In the example, the ! indicates a comment and the & at the end of a line indicates that the command continues onto the next line.

constraint create joint revolute & !{keywords} joint_name=.model_1.JOINT_1 & !{parameter=value}

i_marker_name=.model_1.PART_1.MAR_3 & !”&” for continuation j_marker_name=.model_1.ground.MAR_1 &

friction_enabled = no

Syntax Rules for Entering Commands

The commands that you enter in the command window are made up of keywords, parameters for the keywords, and parameter values as shown below:

{keywords} {parameters=values}

There are several rules that you must follow when you enter commands in the command window. For example, the commands must be entered in the order shown below. Because commands are case insensitive, you can type upper or lowercase letters or a mix of both.

(3)

To help you enter commands correctly, Adams/View checks for syntax errors whenever you enter a space, comma, or equal sign (except in a string or expression) in the command window. If Adams/View detects an error, it displays a message above the command information area. You cannot proceed until you correct the error.

Syntax Rules for Entering Values

The values that you can enter in commands are data that have a particular type. There are four data types that Adams/View commands support: integer, real, string, and database object references. The following table lists the data types and their use.

The rules for entering values are that they:

• Can contain letters, numbers, and underscore characters.

• Must begin with a letter or underscore character.

• Can contain any characters that are enclosed by double quotation marks.

• Have separators (blank space or tab) between keywords and parameters. Placing separators between parameters and their values is optional.

For strings, you must use a backslash (\) in front of special characters to ensure that Adams/View does not try to interpret the characters. These characters include quotation marks (") and backslashes. For example, to be sure to include the quotation marks in the string: This is a "string", you would enter:

Data type: Use:

Integer Whole numbers in the range -maxint ... +maxint, where maxint is machine dependent (usually around two billion)

Real Most numeric values, truncated to +/- 1E25 String Character strings of varying length

(4)

Adams/View Commands

4

"This is a \"string\"."

To get a single backslash into the string, you, therefore, enter double backslashes. For example, to specify This ia a \string\, you would enter:

"This is a \\string\\"

Note also for path names on Windows, you can use backslashes as the separators, but you are not required to do so. You can write portable path names by using the forward slash so Adams/View interprets the following as the same path:

"d:/users/efhl/some.file" "d:\users\efhl\some.file"

If the file name is to be stored in a string variable, the backslashes would need to be doubled to preserve the file path:

"d:\\users\\efhl\\some.file"

Note that the forward slash is much preferred over the backslash.

Miscellaneous Command Information

Continuing Commands

You can continue an Adams/View command you enter in the command window for as many lines as necessary. To continue a command, place an ampersand (&) at the end of a line and then continue the command on the next line. Note that a command must be entered all at once.

Keywords, strings, and expressions cannot be broken across lines.

Mixing Comments and Commands

If you want to mix comments and commands (so that your comments appear in the log file), use one of the formats below:

To create: Enter:

A comment alone on one line !comment <CR> A command followed by a comment on one line command !comment<CR> A command followed by a comment on one line, with the command continuing

on the next line command

&!comment<CR> continue command A command followed by a comment on one line, with the comment continuing

on the next line, and the command continuing on the following line command

&!comment<CR> &!comment<CR> continue command

(5)

Entering Abbreviations

You can enter abbreviations for commands and parameters when you are entering commands directly in the command window. You should always use full keywords for macros and command files to avoid any future compatibility problems. Also note that if you use abbreviations, Adams/View takes longer to execute your commands because it must substitute an abbreviation with its full command.

Verifying Command Input

Adams/View verifies command input whenever you enter a space, comma, or equal sign (except in a string or expression) in the command window. If Adams/View detects an error, it displays a message above the command information area. You cannot proceed until you correct the error.

Reviewing Commands

You can use the scroll bar at the side of the command information area to view the last 50 commands that were entered.

Recalling Commands

Use the arrow keys to recall and edit commands. After entering a command, in the command entry area, press the up arrow to display it in the command entry area again. Use the left and right arrows to edit it, and then press Enter.

Getting Help Completing Command Parameters

In the command window, you can get help with keywords and parameter name completion. In addition, you can get help with possible parameter values for modeling objects and files. For example, you can get a list of possible marker names in your model or you can display the File Browser to help you find a file.

To get assistance with keywords:

1. Enter the beginning of a keyword. For example, enter f. 2. Type ?.

The command window displays all the keywords that begin with letter or letters. For example, for f it displays file, floating_marker, and so on.

To view all parameter names associated with a keyword:

1. Enter the keyword. For example, enter file. 2. Type ?.

The command window displays all the parameter names associated with the keyword.

To get assistance with values for a parameter:

1. Enter the parameter name but do not include the parameter value. For example, enter the command mar del mar=.

(6)

Adams/View Commands

6

2. Type ?.

If the parameter value requires a modeling object, the command window displays a list of possible objects in your current model. If the parameter value requires a file, the File Browser appears. 3. Copy or select the desired object and place it in the parameter value.

Grouping Operations into an Undo Block

As you issue Adams/View commands from the command window, you can group them into undo blocks. By grouping them into undo blocks, you can use a single undo command to reverse all the operations in the block. You can define undo blocks around macros, command files, or any group of Adams/View commands. You can nest them to any level.

To create an undo block:

1. Enter the following command in the command window to mark the beginning of the block: UNDO BEGIN_BLOCK

2. Issue all the commands to be included in the undo block. 3. To close the block, enter the command:

UNDO END_BLOCK

Once you have closed the undo block, any individual commands that you issue that are not in the undo block or any nested undo blocks within the undo block are not affected by an Undo command. Once you close the undo block, you cannot open it again.

The following is an example of an undo block with individual commands surrounding it and several undo operations that were issued. The undo commands reverse all operations that were performed to create the model and part.

MODEL CREATE... UNDO BEGIN_BLOCK

PART CREATE... MARKER CREATE...

UNDO BACKWARD ! Undo the MARKER CREATE above, not entire undo block

MARKER CREATE... GEOM CREATE... UNDO END_BLOCK

PART DELETE...

UNDO BACKWARD ! Undo the PART DELETE command UNDO BACKWARD ! Undo the entire undo block UNDO FORWARD ! Restore the entire undo block UNDO BACKWARD ! Undo the entire undo block again UNDO BACKWARD ! Undo the MODEL CREATE command Note the following about the example:

• The first UNDO BACKWARD within the undo block undoes only the preceding MARKER CREATE command.

(7)

• The third UNDO BACKWARD command after the Undo block undoes the entire contents of the undo block.

• The UNDO FORWARD reverses the undo of the entire undo block as if the undo block were a single command.

The limit on the number of commands Adams/View remembers does not apply to commands within an undo block. You may notice slowed system performance if you store too many commands in a single undo block or if you have the number of undo steps set too high using the undo set command.

(8)

Adams/View Commands

(9)

(10)

Adams/View Commands analysis collate_contacts 2

analysis collate_contacts

Sets the tolerance value for track data and reference marker with respect to which contact data is computed.

Format:

Example:

Description:

Extended Definition:

1. A track is a sequence of individual impacts between two particular geometries specified by a single contact object. The two geometries for a particular track should always be the same at every impact along that track.

analysis collate_contacts

analyis_name = existing analysis contact_name = new contact

tolerance = real

reference_marker = existing marker

analysis collate_contacts & analysis_name = last_run &

contact_name = contact_between_part_1_and_2 & tolerance = 0.1 &

reference_marker = marker_3

Parameter Value Type Description

analysis_name Existing analysis Specifies an existing analysis. Contact_name Existing contact Specifies an existing contact.

tolerance Real Specifies the distance used to decide if two successive impacts of two geometries used by the same contact belong to the same track. If you do not provide it, Adams/Solver computes the tolerance, which can take a long time.

reference_marker Existing marker Specifies the marker with respect to which the track data is computed. Otherwise, the track data is in the global reference frame.

(11)

It is possible for a contact object and two of its geometries to have more than one track. For example, if a contact and two of its geometries have more than one impact at the same time, each separate impact must belong to a separate track to remove ambiguity. Also, when the separation between impacts is great enough according to either an automatic or given criteria, the impacts may be assembled into separate tracks.

There is an experimental method of specifying a delta value for the separation criteria that will make the program skip the automatic criteria, sometimes saving a significant amount of time. This can be done by setting the tolerance parameter using the analysis collate_contacts command. By using a large tolerance value, you can coerce tracks together that may have been separated by the automatic criteria. See Knowledge Base Article 10523 for more information.

Automatic criteria for a contact and an I and J geometry:

• The geometric center (centroid) of all the impacts over the entire simulation is found in three frames: the global frame and the I and J part frames.

• The average distance of the impacts from the centroid is computed, again in each of the three frames.

• The standard deviation of the impacts from this average distance is computed in the three frames. This value for the standard deviation is used as a delta to decide if any two impacts are close enough to be considered to belong to the same track. The frame with the minimum distance is used for the comparison.

To force a pair of locations on two different parts to belong to separate tracks you can place a small separate piece of geometry at that particular point on each part. For example, instead of making a table out of a single piece of geometry and letting the algorithm try to find the separate legs as four separate tracks, placing a cap at the end of each leg will force separate tracks. 2. You can identify an entity, such as a marker or force, by typing its name or by picking it from the

screen. If the entity is not visible on the screen, you must type the name. You may also find it convenient to type the name even if the element is displayed.

If an entity is available by default, you can identify it by entering its name only. If it is not, you must enter its full name. To identify a entity under a different part, you may need to enter the model and part names as well. For example, you can specify marker 'pivot' from model 'links', part 'lower_arm' by entering ".links.lower_arm.pivot".

If you type a "?", Adams/View lists the entity available by default.

You must separate multiple entity names by commas. If the entity is visible in one of your views, you can identify it by picking it. You need not separate multiple element picks by commas.

(12)

Adams/View Commands analysis collate_contacts 4

Note: • If you created a marker by reading an Adams/Solver dataset or graphics file, the marker name is the letters MAR followed by the dataset marker ID number. For example, the name of MARKER/101 is MAR101. If you created the marker during preprocessing, you gave it a name at that time.

• You may have explicitly named an analysis when you created it by reading one or more Adams output files (graphics (.gra), request (.req), or results (.res)). By default, the name of the analysis is the root name of the Adams output files without the extension. If you created the analysis by reading an Adams graphics file, for example, the analysis name is the name of the graphics file without the .gra extension

• You need to be using the XML Results File (XRF) format in order for the contact incident data to be available for collation.

(13)

analysis create

Allows you to create an empty analysis. This is useful for reading spreadsheet data into a results set, using the numeric_results read_from_file command.

Format:

Example:

Description:

1. When using the Adams/View command language and naming entities, you can use the name later to refer to this entity. Adams/View does not allow you to have two entities with the same name, so you must provide a unique name. Normally, entity names are composed of alphabetic, numeric, or '_' (underscore) characters, and start with an alphabetic or '_' character. They may be of any length.

By enclosing the name in double quotes, you can use other printable characters, or start the name with a numeral. If a name contains characters, or starts with a numeral, you must always quote the name when entering it.

Note that you can specify the parentage of an entity (for example, what part "owns" a marker or a geometry element) when you create it by changing the name. If you enter just the entity name, then Adams/View assigns the default parent. If you type in the full name, then you can override the default parent. In most cases, when creating an entity, Adams/View provides a default name. The default name that Adams/View provides specifies the parentage that it has assumed. You can, of course, delete this name and use your own. The form of a full name is:

"...._NAME.GRAND_PARENT_NAME.PARENT_NAME.ENTITY_NAME"

The number of levels used varies from case to case and the parentage must exist before an entity can be assigned to it.

analysis create

analysis_name = new analysis

analysis create &

analysis_name = my_analysis

(14)

Adams/View Commands analysis delete

6

analysis delete

Allows you to delete an existing analysis. You must enter the name of the analysis you want to delete by specifying the name of an analysis on the default model or the full name.

You can reverse this modification by issuing an undo command.

Format:

Example:

Description:

analysis delete

analysis_name = existing analysis

analysis delete &

analysis_name = my_analysis

(15)

analysis modify

Allows you to modify an existing analysis. You must enter the name of the analysis you want to modify by specifying the name of an analysis on the default model or the full name.

You can reverse this modification by issuing an undo command.

Format:

Example:

Description:

analysis modify

analysis_name = existing analysis new_analysis_name = new name of analysis

analysis modify &

analysis_name = .model_1.analysis_1 & new_analysis_name = .model.my_analysis

analysis_name Existing Analysis Specifies the name of the analysis in which to store output files

(16)

Adams/View Commands analysis modify

8

(17)

analysis reload_files

Allows you to read the specified analysis file into Adams/View again, reloading any files that were read when creating the analysis. The analysis files then update any existing plots or analysis results.

Format: :

Example:

Description:

2. By enclosing the name in double quotes, you can use other printable characters, or start the name with a numeral. If a name contains characters, or starts with a numeral, you must always quote the name when entering it.

analysis reload_files

analysis_name = existing analysis

analysis reload_files & analysis_name = my_analysis

(18)

Adams/View Commands analysis reload_files

(19)

(20)

Adams/View Commands animation add_simulation 2

animation add_simulation

Allows you to add a simulation to an existing animation.

Format: : Example: : Description: Extended Definition:

1. This command is useful when you need to compare two animations side by side. For example, if you want to compare the animation of two cars side by side and see which is faster, you can add the simulation of one car to the other car’s animation.

2. Normally, entity names are composed of alphabetic, numeric, or '_' (underscore) characters, and start with an alphabetic or '_' character. They may be of any length.

By enclosing the name in double quotes, you may use other printable characters, or start the name with a numeral. If a name contains characters, or starts with a numeral, you must always quote the name when entering it.

animation add_simulation

animation_name = an existing animation

page_name = an existing page old_analysis_name = an existing analysis

new_analysis_name = a new analysis

animation add_simulation & animation_name = anim__1 & old_analysis_name = Last_Run & new_analysis_name = ana__1

animation_name An Existing Animation

Specifies the name of an existing animation.

page_name An Existing Page Instead of animation_name, you can specify the page name containing the animation.

old_analysis_name An Existing Analysis Specifies the name of the existing analysis. new_analysis_name A New Analysis Specifies a name for the new analysis

(21)

Note that you can specify the parentage of an entity (e.g. what part "owns" a marker or a geometry element) when you CREATE it by changing the name. If you enter just the entity name, then the default parent will be assigned by Adams/View. If you type in the full name, then you may override the default parent. In most cases, when creating an entity, Adams/View will provide a default name. The default name that Adams/View provides will specify the parentage that it has assumed.

You may, of course, delete this name and use your own. The form of a full name is: "...._NAME.GRAND_PARENT_NAME.PARENT_NAME.ENTITY_NAME"

(22)

Adams/View Commands animation create

4

animation create

Allows you to create a model

Format:

Example:

animation create

animation_name = a new animation analysis_name = an existing analysis

view_name = an existing view number_of_cycles = integer time_range = time frame_range = integer frame_number = integer time = time configuration = display_frame increment_frame_by = integer superimposed = on_off

base_marker = an existing marker camera_ref_marker = an existing marker point_trace_marker = an existing marker

icon_visibility = on_off offset = location

colors = an existing color

animation create &

analysis_name = Hood_1 & view_name = View_1 & component = Plot_1 & number_of_cycles = 10 &

animation_name = Animation__1 & time = 50 &

(23)

Description:

point_trace_marker = Marker_71 & icon_visibility = On

animation_name A New Animation Specifies the name of a new animation analysis_name An Existing Analysis Specifies the name of an existing analysis

view_name An Existing View Specifies the name of the view that you would like to view the animation from

number_of_cycles Integer Specifies the number of complete cycles to be animated time_range Time Specifies the analysis output Adams simulation output time steps at which to start and stop the animation (in that order).

frame_range Integer Specifies the analysis frame number (output time step) at which to start and stop the animation (in that order). Frame_number Integer Specifies the frame number (adams simulation output

time step) at which to configure a model during the single_frame_display command.

Time Time Specifies the time as a real number greater than or equal to zero

Configuration Display_frame Specifies what output frame, or output time step, of the simulation results is to be displayed for the

single_frame_display command

Increment_frame_by Integer Specifies the number of frames to skip between each animation step

Superimposed On_off Parameter used with the animation command to specify whether or not to show each frame of the animation individually or superimposed on top of another Base_marker An Existing Marker Specifies a marker whose position will be frozen in the

view as the model gets animated

Camera_ref_marker An Existing Marker Identifies a marker which specifies the viewing direction as the model gets animated

Point_trace_marker An Existing Marker Specifies marker(s) whose position will be traced in the view as the model animates

Icon_visibility On_off Specifies whether or not to display icons during an animation

(24)

6

1. You may reverse this creation at a later time with an UNDO command.

2. When Adams/View reads a request, graphics, and results files (.req, .gra, and .res, respectively) with the file analysis read command, it stores it in an analysis. By default, the name of the analysis is the file name, excluding the extension.

3. Each view created has a name associated with it. The view_name parameter is used to identify a view for a particular operation. In most cases, view_name=all is also a valid entry. The all option indicates "all displayed views". There are eight standard views available when the Adams/View is started. These views are: front, top, right, iso, bottom, left, and back. The first four of these standard views are displayed by default when Adams/View is started.

The user may create new views using the 'VIEW MANAGEMENT CREATE' command, and save/restore their attributesIf the VIEW_NAME parameter is used, the desired view can be identified by picking in the window or entering the name from the keyboard.

4. This means, based on number_of_cycles parameter, the animation will continuously run through all the specified frames the specified number of times.

f entered, the NUMBER_OF_CYCLES parameter must be a positive integer.This value will be remembered and will be the default the next time an animation is performed. This parameter is optional, and if not entered, will default initially to 1 (until updated by the user).

5. If entered, time_range parameter must be two real numbers (separated by commas) where the second is greater than the first and the default values are initially 0.0,1000.0. If new values are entered, these values will be remembered and be the default next time the parameter is used. If a value greater than the simulation endint time is entered for the second value, the system will stop at the last frame.

These time values will be rounded to the nearest simulation output time step value.This parameter is optional and mutually exclusive with the FRAME_RANGE parameter. If neither is entered, the previous values to TIME_RANGE will be used (0,0,1000.0, if they have not been changed by the user

Special Note: Even if only one view_name is provided, the time range will be applied to the specified view and any other views that contain the same model (the model indicated by analysis_name parameter). If only analysis_name is provided (view_name parameter is omitted), any views that contain the model indicated by analysis_name will be affected

6. If entered, this parameter must be two positive integers (separated by commas) where the second is greater than the first and the default values are initially 1,10000. If new values are entered, these values will be remembered and be the default next time the parameter is used.

If a value greater than the last frame number is entered for the second value, the system will stop at the last frame. This parameter is optional and mutually exclusive with the TIME_RANGE Offset Location Specifies the offset of the axis line from the plot border Colors An Existing Color Modifies the red, green, and blue components of

existing colors.

(25)

parameter. If neither is entered, the previous values to FRAME_RANGE will be used (1,10000 if they have not been changed by the user .Special Note: Even if only one view_name is provided, the frame range will be applied to the specified view and any other views that contain the same model (the model indicated by analysis_name parameter). If only analysis_name is provided (view_name parameter is omitted), any views that contain the model indicated by analysis_name will be affected

7. If entered the frame_number must be a positive integer corresponding to the desired frame (output time step) and the default value is initially 1. If a new value is entered, this value will be remembered and be the default next time the command is used. If a value greater than the last frame number is entered, the system will display the last frame.

This parameter is optional and mutually exclusive with the CONFIGURATION and TIME parameters. If none of the three are entered, the first frame will be displayed .Special Note: Even if only one view_name is provided, the frame number will be applied to the specified view and any other views that contain the same model (the model indicated by analysis_name parameter). If only analysis_name is provided (view_name parameter is omitted), views that contain the model indicated by analysis_name will be affected

8. The legal values for this parameter are:

MODEL_INPUT, the configuration as input to Adams before analysis, INITIAL_CONDITIONS, the configuration after initial conditions are met, EQUILIBRIUM, the configuration after an equilibrium analysis,

FORWARD, one frame forward from the current one displayed, and BACKWARD, one frame backward from the current one displayed.

Therefore, this parameter is not used to specify a particular time or frame_number. In fact, this parameter is mutually exclusive with the FRAME_NUMBER and TIME parameters. These two parameters are used to specify the time dependent frames of the simulation output.

The CONFIGURATION parameter is optional and if not entered, the system will display the first time dependent frame in the graphics file (assuming its mutually exclusive counterparts are not entered either).

9. This allows the user to speed up the viewing of motions that take many frames to develop (that move slowly). If a negative value is entered, the animation will play in the reverse.

If entered, the INCREMENT_FRAMES_BY parameter must have an absolute value less than the maximum number of frames in the analysis. This parameter is optional and if not entered, will default to 1.

10. The superimposed view is sometimes referred to as a fan diagram. Superimposing frames is useful to show the relationship of the models parts between frames but often obscures the view of the motion.

This is an optional parameter and if not entered, then no superimposed frames will be drawn. The legal values of this parameter are ON and OFF. ON indicates that frames will be superimpose during the animation. OFF, the default, indicates that frames will not be superimpose during the animation.

(26)

8

11. This is particularly useful when a relatively small object undergoes both, small configuration changes as well as large overall gross motion. For example, the flight path of a jet is very large over time relative to the motion of the control surfaces on the jet. In this case, selecting the BASE_MARKER to be on the jet would be appropriate.

This parameter can be used with the CAMERA_REF_MARKER to create a different effect on the viewing direction. When the CAMERA_REF_MARKER and the BASE_MARKER are specified together, the viewing direction is "from" the CAMERA_REF_MARKER position "to" the BASE_MARKER position.

In addition, the "up" direction of the view is computed based on the direction of the

CAMERA_REF_MARKER "y" axis (i.e. the y axis is projected into a direction perpendicular to the viewing direction defined by the two markers). This viewing direction is recomputed between each frame of the animation. This feature allows the effect of watching an object come from a distance, pass by, and proceed into the distance.

12. camera_ref_marker parameter is used to identify a marker which specifies the viewing direction as the model gets animated.

13. point_trace_marker parameter is particularly useful when a marker undergoes complicated motion, or has motion that is easily obscured by other model graphics. For example, the path of a chain link being whipped, or a car wheel center's 3D motion. In this case, selecting the

BASE_MARKER to be on the wheel center would be appropriate.

14. Entering 'ON' will cause Adams/View to display the icons during animation. This will cause slower animation times. For this reason, 'OFF' is the default value.

Cautions:

1. Typing the name is the only way to identify a stored view that is not displayed.

2. The model graphics need not be displayed to trace the path of a marker in a view. Up to 10 markers can be traced simultaneously.

(27)

animation delete

Allows you to delete an existing animation.

Format:

Example:

Description:

1. Normally, entity names are composed of alphabetic, numeric, or '_' (underscore) characters, and start with an alphabetic or '_' character. They may be of any length.

Note that you can specify the parentage of an entity (e.g. what part "owns" a marker or a geometry element) when you CREATE it by changing the name. If you enter just the entity name, then the default parent will be assigned by Adams/View. If you type in the full name, then you may override the default parent. In most cases, when creating an entity, Adams/View will provide a default name. The default name that Adams/View provides will specify the parentage that it has assumed.

You may, of course, delete this name and use your own. The form of a full name is: "...._NAME.GRAND_PARENT_NAME.PARENT_NAME.ENTITY_NAME"

animation delete

animation_name = an existing animation

animation delete &

animation_name = ani__1

(28)

Adams/View Commands animation display

10

animation display

Allows you to display the model in the specified view.

Format:

Example:

Description:

1. If no view has been specified, the model will be displayed in the active view.

This command can be useful when the the entire model is no longer visible in the current view space. MODEL DISPLAY will "fit" the model to the current view space.

2. The view_name parameter is used to identify a view for a particular operation. In most cases, view_name=all is also a valid entry. The all option indicates "all displayed views". There are eight standard views available when the Adams/View is started. These views are: front, top, right, iso, bottom, left, and back. The first four of these standard views are displayed by default when Adams/View is started. The user may create new views using the 'VIEW MANAGEMENT CREATE' command, and save/restore their attributes.

If the VIEW_NAME parameter is used, the desired view can be identified by picking in the window or entering the name from the keyboard.

Typing the name is the only way to identify a stored view that is not displayed. animation display

animation_name = an existing animation view_name = an existing view

animation display &

animation_name = animation_1 & view_name = view_1

animation_name An Existing Animation Specifies an existing animation name that is to be run view_name An Existing View Specifies the name associated with the view created

(29)

animation log

Allows you to specify whether or not cache information is to be maintained on the physical disk.

Format:

Example:

Description:

1. By default, cache information necessary for animations containing flexible bodies is maintained on the disk in files with a .fcf extension. Adams/PostProcessor can also maintain this information in physical memory, which can result in significantly less disk input/output, higher CPU utilization, and, consequently, faster performance. If you work in an environment with remote disk servers (accessed across a network), you should see a dramatic improvement in performance if you select to maintain the cache in memory. Users using local disk will see improvements on a smaller scale.

The disadvantage of memory caching is the increased process size and the risk that it will exceed your computer's physical memory. If your computer has enough physical memory, then this approach is more efficient. If your computer does not have enough physical memory, then its operating system will begin swapping and the animation performance may be worse than when using the .fcf file. We recommend that you test each model with this setting and monitor the process size using the Task Manager on Windows or the equivalent tool on UNIX (for example, gmemusage -s on SGI).

animation log

flex_caching = boolean object_caching = boolean

animation log &

flex_caching = on & object_caching = on

flex_caching Boolean

(30)

Adams/View Commands animation log

12

Cautions:

1. If the cache is turned on, performance will be improved but will use up the computer’s physical memory.

(31)

animation modify

Allows you to modify an existing model

Format:

Example:

animation modify

animation_name = a new animation

analysis_name = an existing analysis view_name = an existing view number_of_cycles = integer time_range = time frame_range = integer frame_number = integer time = time configuration = display_frame increment_frame_by = integer superimposed = on_off

base_marker = an existing marker camera_ref_marker = an existing marker point_trace_marker = an existing marker

icon_visibility = on_off offset = location

colors = an existing color

animation modify &

analysis_name = Hood_1 & view_name = View_1 & component = Plot_1 & number_of_cycles = 10 &

animation_name = Animation__1 & time = 50 &

(32)

Adams/View Commands animation modify

14

Description:

point_trace_marker = Marker_71 & icon_visibility = On

Parameter Value type Description

animation_name A New Animation Specifies the name of a new animation analysis_name An Existing Analysis Specifies the name of an existing analysis

view_name An Existing View Specifies the name of the view that you would like to view the animation from

number_of_cycles Integer Specifies the number of complete cycles to animate time_range Time Specifies the analysis output Adams simulation output

time steps at which to start and stop the animation (in that order).

frame_range Integer Specifies the analysis frame number (output time step) at which to start and stop the animation (in that order). frame_number Integer Specifies the frame number (Adams simulation output

time step) at which to configure a model during the single_frame_display command.

time Time Specifies the time as a real number greater than or equal to zero

configuration Display_frame Specifies what output frame, or output time step, of the simulation results is to be displayed for the

single_frame_display command

increment_frame_by Integer Specifies the number of frames to skip between each animation step

superimposed On_off Parameter used with the animation command to specify whether or not to show each frame of the animation individually or superimposed on top of another base_marker An Existing Marker Specifies a marker whose position will be frozen in the

view as the model gets animated

camera_ref_marker An Existing Marker Identifies a marker which specifies the viewing direction as the model animates

point_trace_marker An Existing Marker Specifies marker(s) whose position will be traced in the view as the model gets animated

icon_visibility On_off Specifies whether or not to display icons during an animation

(33)

1. You must enter the name of the model you wish to modify either by picking it from the screen or specifying the full name.

2. You may reverse this modification at a later time with an UNDO command.

3. When Adams/View reads a request, graphics, and results files (.req, .gra, and .res, respectively) with the file analysis read command, it stores it in an analysis. By default, the name of the analysis is the file name, excluding the extension.

4. Each view created has a name associated with it. The view_name parameter is used to identify a view for a particular operation. In most cases, view_name=all is also a valid entry. The all option indicates "all displayed views". There are eight standard views available when the Adams/View is started. These views are: front, top, right, iso, bottom, left, and back. The first four of these standard views are displayed by default when Adams/View is started.

The user may create new views using the 'VIEW MANAGEMENT CREATE' command, and save/restore their attributes.

If the VIEW_NAME parameter is used, the desired view can be identified by picking in the window or entering the name from the keyboard.

5. This means, based on number_of_cycles parameter, the animation will continuously run through all the specified frames the specified number of times.

If entered, the NUMBER_OF_CYCLES parameter must be a positive integer.

This value will be remembered and will be the default the next time an animation is performed. This parameter is optional and if not entered, will default initially to 1 (until updated by the user). 6. If entered, time_range parameter must be two real numbers (separated by commas) where the

second is greater than the first and the default values are initially 0.0,1000.0. If new values are entered, these values will be remembered and be the default next time the parameter is used. If a value greater than the simulation endint time is entered for the second value, the system will stop at the last frame.

These time values will be rounded to the nearest simulation output time step value.

This parameter is optional and mutually exclusive with the FRAME_RANGE parameter. If neither is entered, the previous values to TIME_RANGE will be used (0,0,1000.0, if they have not been changed by the user)

Special Note: Even if only one view_name is provided, the time range will be applied to the

specified view and any other views that contain the same model (the model indicated by analysis_name parameter). If only analysis_name is provided (view_name parameter is omitted), any views that contain the model indicated by analysis_name will be affected

offset Location Specifies the offset of the axis line from the plot border colors An Existing Color Modifies the red, green, and blue components of

existing colors.

(34)

Adams/View Commands animation modify

16

7. If entered, this parameter must be two positive integers (separated by commas) where the second is greater than the first and the default values are initially 1,10000. If new values are entered, these values will be remembered and be the default next time the parameter is used.

If a value greater than the last frame number is entered for the second value, the system will stop at the last frame.

This parameter is optional and mutually exclusive of the TIME_RANGE parameter. If neither is entered, the previous values to FRAME_RANGE will be used (1,10000, if they have not been changed by the user)

Special Note: Even if only one view_name is provided, the frame range will be applied to the

8. If entered, the frame_number must be a positive integer corresponding to the desired frame (output time step) and the default value is initially 1. If a new value is entered, this value will be remembered and be the default next time the command is used. If a value greater than the last frame number is entered, the system will display the last frame.

This parameter is optional and mutually exclusive with the CONFIGURATION and TIME parameters. If none of the three are entered, the first frame will be displayed.

Special Note: Even if only one view_name is provided, the frame number will be applied to the

9. The legal values for this parameter are:

MODEL_INPUT, the configuration as input to Adams before analysis, INITIAL_CONDITIONS, the configuration after initial conditions are met, EQUILIBRIUM, the configuration after an equilibrium analysis,

FORWARD, one frame forward from the current one displayed, and BACKWARD, one frame backward from the current one displayed.

Therefore, this parameter is not used to specify a particular time or frame_number. In fact, this parameter is mutually exclusive with the FRAME_NUMBER and TIME parameters. These two parameter are used to specify the time dependent frames of the simulation output.

The CONFIGURATION parameter is optional and if not entered the system will display the 1st time dependent frame in the graphics file (assuming it's mutually exclusive counterparts are not entered either).

10. This allows the user to speed up the viewing of motions that take many frames to develop (that move slowly). If a negative value is entered, the animation will play in reverse.

If entered, the INCREMENT_FRAMES_BY parameter must have an absolute value less than the maximum number of frames in the analysis. This parameter is optional and if not entered, will default to 1.

(35)

11. The superimposed view is sometimes referred to as a fan diagram. Superimposing frames is useful to show the relationship of the models parts between frames but often obscures the view of the motion.

This is an optional parameter and if not entered then no superimposed frames will be drawn. The legal values of this parameter are ON and OFF. ON indicates that frames will be superimpose during the animation. OFF, the default, indicates that frames will not be superimpose during the animation.

12. This is particularly useful when a relatively small object undergoes both small configuration changes as well as large overall gross motion. For example, the flight path of a jet is very large over time relative to the motion of the control surfaces on the jet. In this case selecting the BASE_MARKER to be on the jet would be appropriate.

This parameter can be used with the CAMERA_REF_MARKER to create a different effect on the viewing direction. When the CAMERA_REF_MARKER and the BASE_MARKER are specified together, the viewing direction is "from" the CAMERA_REF_MARKER position "to" the BASE_MARKER position.

In addition, the "up" direction of the view is computed based on the direction of the

CAMERA_REF_MARKER "y" axis (i.e. the y axis is projected into a direction perpendicular to the viewing direction defined by the two markers). This viewing direction is recomputed between each frame of the animation. This feature allows the effect of watching an object come from a distance, pass by, and proceed into the distance.

13. camera_ref_marker parameter is used to identify a marker which specifies the viewing direction as the model gets animated

14. point_trace_marker parameter is particularly useful when a marker undergoes complicated motion, or has motion that is easily obscured by other model graphics. For example, the path of a chain link being whipped, or a car wheel center's 3D motion. In this case, selecting the

BASE_MARKER to be on the wheel center would be appropriate.

15. Entering 'ON' will cause Adams/View to display the icons during animation. This will cause slower animation times. For this reason, 'OFF' is the default value.

Cautions:

1. Typing the name is the only way to identify a stored view that is not displayed.

2. The model graphics need not be displayed to trace the path of a marker in a view. Up to 10 markers can be traced simultaneously.

(36)

Adams/View Commands animation pause

18

animation pause

Allows you to pause/stop an animation while it is running.

Format:

Example:

Description:

1. The parameter supplied to this command could be either an animation name or a page name (run from the post processor)

animation pause

animation_name = an existing animation page_name = an existing page

animation pause &

animation_name = animation_1 & page_name = page_1

animation_name An Existing Animation Specifies an existing animation name that is to be run page_name An Existing Page Specifies the page in the Adams/Postprocessor that is to

(37)

animation play

Allows you to play an animation.

Format:

Example:

Description:

1. The parameter supplied to this command could either be an animation name or a page name (run from the post processor)

animation play

animation play &

animation_name = animation_1 & page_name = page_1

animation_name An Existing Animation Specifies an existing animation name that has to be run page_name An Existing Page Specifies the page in the Adams/Postprocessor that is to

(38)

Adams/View Commands animation record start 20

animation record start

Allows you to record the animation. The video file is saved in the current working directory.

Format:

Example:

Description:

animation record start

image_prefix = string image_type = string avi_frames_per_sec = integer avi_compression = boolean avi_quality = integer avi_keyframe_every = integer mpeg_ngop = integer mpeg_round_size = boolean window_size = integer

animation record start &

image_prefix = ".jpg" & image_type = jpg & avi_frames_per_sec = 15 & avi_compression = no & avi_quality = 10 & avi_keyframe_every = 25 & mpeg_ngop = 2 & mpeg_round_size = yes &

window_size = 2

image_prefix String Set the prefix used to name the set of files.

image_type String Select the format: .avi, .tif, .jpg, .bmp, .mpg, .png, and .xpm avi_frames_per_sec Integer Enter the number of frames per second used in the recording.

(39)

1. Adams/PostProcessor appends a unique number to the prefix to form the name of each file. For example, if you specify a prefix of suspension, then each .tif file is named suspension_0001.tif, suspension_0002.tif, and so on. If you do not specify a name, the prefix is frame (for example, frame_001.tif).

2. When a digital movie stream is encoded with compression, the pixels of each frame are evaluated against previous frames (those designated as key) and only pixels that changed are stored. For example, a movie of a car traveling along a road can have many pixels in the image background that do not change during the entire movie. Therefore, storing only the pixels that change allows for significant compression. In many cases, however, it can degrade movie quality, especially with movies where a large percentage of pixels are changing from frame-to-frame, such as with wireframe graphics. Because Adams/PostProcessor lets you set the key frame rates, you control both, the compression factor and the movie quality.

3. Movies with many key frames will have high quality, while movies with few key frames, such as the default every 5000 frames, will have lower quality. For a typical 20-second AVI movie of a shaded Adams model, a key frame rate would be 12.

4. Some playback programs require the pixel height and width to be multiples of 16. Turning the mpeg_round_size option ‘on’ ensures that your movie plays in many playback programs. avi_compression Boolean Enters yes or no depending on whether or not the avi needs to

be compressed.

avi_quality Integer Enters a value or use the slider to set the image quality. avi_keyframe_every Integer Sets the interval between key frames. The default is a key frame

every 5000 frames. mpeg_ngop Integer Enters an integer number.

mpeg_round_size Boolean Specifies yes or no if size is to be rounded to multiples of 16. window_size Integer Enters an integer number to specify window size.

Caution: (AVI format is only available on Windows).

Tip: 1. Turn off compression to improve the quality of the images.

2. When you set use compression when recording in AVI format, the playback program may restrict the size of image frames, usually to a multiple of 2 or 4. Therefore, your recording may appear cut off on one or more sides. The workaround is to change the animation window size before recording.

(40)

Adams/View Commands animation record stop 22

animation record stop

Stop the animation recording

Format:

animation record stop

Example:

(41)

animation replace_simulation

Replace an existing analysis/page name with another in the animation.

Format:

Example:

Description:

1. This command is useful when you need to compare two animations side by side. For example if you want to compare the animation of two cars side by side and see which is faster, you can add the simulation of one car to the other cars animation.

2. Normally, entity names are composed of alphabetic, numeric, or '_' (underscore) characters, and start with an alphabetic or '_' character. They may be any length.

animation replace_simulation

animation_name = an existing animation page_name = an existing page old_analysis_name = an existing analysis new_analysis_name = a new analysis

animation replace_simulation & animation_name = anim__1 & old_analysis_name = last_run & new_analysis_name = ana__1

animation_name An Existing Animation

Specify name of an existing animation.

page_name An Existing Page Instead of animation_name, you can specify the page name containing the animation.

old_analysis_name An Existing Analysis Specify name of the existing analysis. new_analysis_name A New Analysis Specify name of the new analysis

(42)

Adams/View Commands animation replace_simulation 24

Note: You can specify the parentage of an entity (e.g. what part "owns" a marker or a geometry element) when you CREATE it by changing the name. If you enter just the entity name, then the default parent will be assigned by Adams/View. If you type in the full name, then you may over ride the default parent. In most cases, when creating anentity, Adams/View will provide a default name. The default namethatAdams/View provides will specify the parentage that it has assumed.

You may, or course, delete this name and use your own. The form of a full name is: "...._NAME.GRAND_PARENT_NAME.PARENT_NAME.ENTITY_NAME"

(43)

animation reset

Allows you to reset an animation.

Format: :

Example:

Description:

1. The parameter supplied to this command could either be an animation name or a page name (run from the post processor)

animation reset

animation reset &

animation_name = an existing animation & page_name = an existing page

(44)

Adams/View Commands animation step

26

animation step

Allows you to step the animation either forward or backwards as needed.

Format:

Example:

Description:

1. When you play an animation, Adams/View plays every frame by default. You can rewind an animation and play the animation at various speeds. During fast-forward and fast-backward play modes, Adams/View plays only every fifth frame.

animation step

direction = animation_direction animation_name = an existing animation

page_name = an existing page

animation step &

direction = forward & animation_name = animation_1 &

page_name = page_1

direction Animation_direction Specifies whether you want the animation to step in the forward or backward direction

(45)

break

Allows you to exit the innermost FOR or WHILE loop immediately and stop execution of the loop. When Adams/View encounters a BREAK command inside a loop, it immediately exits the loop without executing the remaining commands for that iteration.

The BREAK command affects only the innermost FOR or WHILE loop.

Format:

BREAK

Example:

variable create variable_name=ip integer_value=0 while condition=(ip < 5)

variable modify variable_name=ip integer_value(eval(ip+1)) if condition=(eval(DB_EXISTS ("MAR"//ip)))

break end

marker create marker_name=(eval("MAR"//ip)) & location=(eval(ip-1)),0,0

end

variable delete variable_name=ip

In this example, Adams/View creates markers, named MAR1, MAR2, MAR3, MAR4, and MAR5, unless a marker already exists with one of those names. As soon as it encounters an existing marker, Adams/View exits the loop and does not create any more.

(46)

Adams/View Commands 2

(47)

check_messages

This command provides you with a way to monitor an Adams simulation while it is running in batch mode. This is done by querying the Adams message data base using some filter and sorting parameters. The FAULTS, ERRORS, WARNINGS, and INFO parameters allow you to filter out only the messages that you want to see. All messages will be reported with like messages grouped according to message type, unless the SORT_BY_TIME parameter is set to YES.

The SORT_BY_TIME parameter specifies in what order the messages of all types are to be reported. When SORT_BY_TIME is set to YES, all message types will be merged together and reported in the order in which they occurred during the simulation (i.e. sorted on the base of simulation time). The FILE_NAME parameter specifies the name of the Adams message file that is to be read. This parameter will default to the message file for the default analysis unless you override it by providing another FILE_NAME with this parameter is specified. The proper extension is ".mdb", the default, but can be overridden by simply supplying a different extension.

You do not need to enclose the file name in quotes if it only contains alpha-numeric characters and starts with a letter. If you want to include other characters, such as a '.' for an extension or '/' or '[]' for directory paths, you must enclose the name in quotes.

Format: Example: check_messages file_name = string faults = boolean errors = boolean warnings = boolean info = boolean sort_by_time = boolean check_messages &

faults = yes & errors = yes & warnings = no &

info = no & sort_by_time = yes

(48)

Adams/View Commands 2

When the above command is executed, all the messages related to faults and errors will be displayed in the order in which they occur during the simulation.

Description:

1. The FILE_NAME parameter will default to the file for the default analysis unless this parameter is specified. The proper extension is ".mdb", the default, but can be overridden by simply supplying a different extension.

You do not need to enclose the file name in quotes if it only contains alpha-numeric characters and starts with a letter. If you want to include other characters, such as a '.' for an extension or '/' or '[]' for directory paths, you must enclose the name in quotes.

2. All messages of type FAULTS, ERROR, WARNINGS and INFO will be reported together unless the SORT_BY_TIME parameter is set to yes. In this case, all message types will be merged together and reported in the order in which they occurred during the simulation (i.e. sorting based on simulation time).

Parameter Value Type Description

file_name String Specifies the name of the Adams message file that is to be read. faults boolean Specifies that the messages of type PROGRAM FAULT are to be

reported.

errors boolean Specifies that the messages of type ERROR are to be reported. warnings boolean Specifies that the messages of type WARNING are to be reported. info boolean Specifies that the messages of type INFO are to be reported. sort_by_time boolean Specifies in what order the messages of all types are to be reported.

(49)

(50)

Adams/View Commands clearance compute

2

clearance compute

Allows you to carry out the specified clearance study for post-processing clearances. Use the menu items

Tools → Clearance → Compute in Adams/PostProcessor, to execute a clearance study.

Format:

Example:

Description:

1. The clearance study which is being carried out uses the analysis specified by the existing_analysis parameter as the basis of the study.

clearance compute

analysis_name = existing analysis treat_flex_as_rigid = yes/no

clearance compute &

analysis_name = Last_Run & treat_flex_as_rigid = yes

analysis_name Existing Analysis This parameter gets assigned the name of an existing simulation analysis.

treat_flex_as_rigid Boolean Decides if the flexible bodies should be treated as rigid bodies while executing the clearance study.

Note: This command is for computing post-processing clearances only. Run-time clearances will not be computed using this command.

(51)

clearance create

Creates a new clearance study. There are two kinds of clearances in Adams, Run-time clearances and Post-processing clearances. Use the menu items Tools → Clearance→ Create in Adams/PostProcessor, to create a clearance study for post-processing clearance.

Format:

Example:

clearance create

clearance_name = string

comments = string

i_geometry = existing geometry

i_part = existing part

i_flex = existing flexible body j_geometry = existing geometry

j_part = existing part

j_flex = existing flexible body

i_region = existing matrix j_region = existing matrix i_exclude = boolean maximum = real threshold = real

method = selection list run_time = boolean

clearance create &

clearance_name = .testdb.CLEARANCE_1 &

comments = " test comment for post-processing clearances " &

i_geometry = LINK_2 & j_geometry = BOX_1 &

maximum = 90 & method = polygon

(52)

Adams/View Commands clearance create

4

Description:

comments = " test run-time clearance comment" & i_flex = FLEX_BODY_1,FLEX_BODY_2 &

j_geometry = BOX_1 &

i_region = MATRIX_1,MATRIX_2 & i_exclude = no,yes &

threshold = 20 & run_time = yes

clearance_name String Specifies the name of the clearance study.

comments String Any accompanying extra information that the user wishes to store with the clearance study.

i_geometry Existing Geometry The first selected entity if it is a geometry.

i_part Existing Part The first selected entity if it is a part. This option is only available for post-processing clearances.

i_flex Existing Flexible Body

The first selected entity if it is a flexible body j_geometry Existing Geometry The second selected entity if it is a geometry

j_part Existing Part The second selected entity if it is a part. This option is only available for post-processing clearances..

j_flex Existing Flexible Body

The first selected entity if it is a flexible body

i_region Existing Matrix If the i_flex parameter is specified, then i_region parameter specifies the list of matrices to be excluded/included in the clearance computations. This option is only available for post-processing clearances.

j_region Existing Matrix If the j_flex parameter is specified, then j_region parameter specifies the list of matrices to be excluded/included in the clearance computations. This option is only available for post-processing clearances.

i_exclude Boolean A list of Boolean values that specifies whether the regions listed in the i_region parameter are to be excluded from the clearance computation. This option is only available for run-time clearances.