Adams 2020 Adams View Command User Guide

Adams 2020
Adams View Command User's Guide

Corporate Europe, Middle East, Africa
MSC Software Corporation MSC Software GmbH
4675 MacArthur Court, Suite 900 Am Moosfeld 13
Newport Beach, CA 92660 81829 Munich, Germany
Telephone: (714) 540-8900 Telephone: (49) 89 431 98 70
Toll Free Number: 1 855 672 7638 Email: europe@mscsoftware.com
Email: americas.contact@mscsoftware.com
Japan Asia-Pacific
MSC Software Japan Ltd. MSC Software (S) Pte. Ltd.
Shinjuku First West 8F 100 Beach Road
23-7 Nishi Shinjuku #16-05 Shaw Tower
1-Chome, Shinjuku-Ku Singapore 189702
Tokyo 160-0023, JAPAN Telephone: 65-6272-0082
Telephone: (81) (3)-6911-1200 Email: APAC.Contact@mscsoftware.com
Email: MSCJ.Market@mscsoftware.com
Worldwide Web
www.mscsoftware.com
Support
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx
Disclaimer
This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with the
terms of such license.
MSC Software Corporation reserves the right to make changes in specifications and other information contained in this document
without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not intended
to be exhaustive or to apply to any particular engineering problem or design. MSC Software Corporation assumes no liability or
responsibility to any person or company for direct or indirect damages resulting from the use of any information contained herein.
User Documentation: Copyright © 2020 MSC Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this
document, in whole or in part, without the prior written consent of MSC Software Corporation is prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from MSC Software suppliers.
Additional terms and conditions and/or notices may apply for certain third party software. Such additional third party software terms
and conditions and/or notices may be set forth in documentation and/or at http://www.mscsoftware.com/thirdpartysoftware (or successor
website designated by MSC from time to time). Portions of this software are owned by Siemens Product Lifecycle Management, Inc.
© Copyright 2020
The MSC Software logo, MSC, MSC Adams, MD Adams, and Adams are trademarks or registered trademarks of MSC Software
Corporation in the United States and/or other countries. Hexagon and the Hexagon logo are trademarks or registered trademarks of
Hexagon AB and/or its subsidiaries. FLEXlm and FlexNet Publisher are trademarks or registered trademarks of Flexera Software.
Parasolid is a registered trademark of Siemens Product Lifecycle Management, Inc. All other trademarks are the property of their
respective owners.
ADAM:V2020:Z:Z:Z:DC-COM
Documentation Feedback
At MSC Software, we strive to produce the highest quality documentation and welcome your feedback.
If you have comments or suggestions about our documentation, write to us at: documentation-
feedback@mscsoftware.com.
Please include the following information with your feedback:
 Document name
 Release/Version number
 Chapter/Section name
 Topic title (for Online Help)
 Brief description of the content (for example, incomplete/incorrect information, grammatical
errors, information that requires clarification or more details and so on).
 Your suggestions for correcting/improving documentation
You may also provide your feedback about MSC Software documentation by taking a short 5-minute
survey at: http://msc-documentation.questionpro.com.
Note: The above mentioned e-mail address is only for providing documentation specific
feedback. If you have any technical problems, issues, or queries, please contact Technical
Support.
Overview 1
Overview
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.
2 Adams View Commands
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.
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
Object Database objects
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:
"This is a \"string\"."
Overview 3
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 &!comment<CR>
the next line command continue command
A command followed by a comment on one line, with the comment continuing on &!comment<CR>
the next line, and the command continuing on the following line command &!comment<CR>
continue command
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=.
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.
Overview 5
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.
 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.
analysis 1
analysis collate_contacts
analysis
Sets the tolerance value for track data and reference marker with respect to which contact data is computed.
Format:
analyis_name = existing analysis
contact_name = new contact
tolerance = real
reference_marker = existing marker
Example:
analysis collate_contacts &
analysis_name = last_run &
contact_name = contact_between_part_1_and_2 &
tolerance = 0.1 &
reference_marker = marker_3
Description:
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.
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.
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 KB8015944 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.
analysis 3
analysis create
Notes:  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.
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:
analysis create
analysis_name = new analysis
Example:
analysis create &
analysis_name = my_analysis
Description:

analysis_name New Analysis Specifies the name of the analysis in which to store output files.
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.
analysis delete
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 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:
analysis delete
analysis_name = existing analysis
Example:
analysis delete &
Description:

analysis_name existing analysis Specifies the name of the analysis to be deleted
when entering it.
analysis 5
analysis modify
be assigned to it.
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:
analysis modify
new_analysis_name = new name of analysis
Example:
analysis modify &
analysis_name = .model_1.analysis_1 &
new_analysis_name = .model.my_analysis
Description:

analysis_name Existing Analysis Specifies the name of the analysis in which to store output
files
New_analysis_name New Analysis Name Specifies the name of the new analysis
analysis reload_files
when entering it.
be assigned to it.
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:
analysis reload_files &
Description:

analysis_name Existing analysis Specifies the name of an existing analysis to be loaded
2. By enclosing the name in double quotes, you can use other printable characters, or start the name with
when entering it.
analysis 7
be assigned to it.
animation 1
animation add_simulation
animation
Allows you to add a simulation to an existing animation.
Format:
:
animation_name = an existing animation
page_name = an existing page
old_analysis_name = an existing analysis
new_analysis_name = a new analysis
Example:
:
animation add_simulation &

animation_name = anim__1 &
old_analysis_name = Last_Run &
new_analysis_name = ana__1
Description:

animation_name An Existing Specifies the name of an existing animation.
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
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.
animation create
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.
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:
be assigned to it.
animation create
Allows you to create a model
Format:
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 3
animation create
Example:
animation create &
analysis_name = Hood_1 &
view_name = View_1 &
component = Plot_1 &
number_of_cycles = 10 &
animation_name = Animation__1 &
time = 50 &
configuration = Model_input &
point_trace_marker = Marker_71 &
icon_visibility = On
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 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
animation create

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
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.
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
animation 5
animation create
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 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.
animation delete
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.
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.
animation delete
Allows you to delete an existing animation.
Format:
animation delete
animation 7
animation display
Example:
animation delete &
animation_name = ani__1
Description:

animation_name An Existing Animation Specifies an existing animation
be assigned to it.
animation display
Allows you to display the model in the specified view.
Format:
animation display
Example:
animation display &
animation_name = animation_1 &
view_name = view_1
animation log
Description:

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
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 log
Allows you to specify whether or not cache information is to be maintained on the physical disk.
Format:
animation log
flex_caching = boolean
object_caching = boolean
Example:
animation log &
flex_caching = on &
object_caching = on
animation 9
animation modify
Description:

flex_caching Boolean
object_caching Boolean Specifies if information for rigid/non flexible bodies is to be cached
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 Linux (for example, gmemusage -s on SGI).
Cautions:
1. If the cache is turned on, performance will be improved but will use up the computer’s physical
memory.
animation modify
Allows you to modify an existing model
Format:
animation modify
animation_name = a new animation
time_range = time
time = time
animation modify
animation modify
offset = location
Example:
animation modify &
analysis_name = Hood_1 &
view_name = View_1 &
component = Plot_1 &
animation_name = Animation__1 &
time = 50 &
configuration = Model_input &
point_trace_marker = Marker_71 &
icon_visibility = On
Description:
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).
animation 11
animation modify
Parameter Value type Description

frame_number Integer Specifies the frame number (Adams simulation output
time step) at which to configure a model during the
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
individually or superimposed on top of another
base_marker An Existing Marker Specifies a marker whose position will be frozen in the
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
icon_visibility On_off Specifies whether or not to display icons during an
animation
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.
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.
displayed by default when Adams View is started.
animation modify
The user may create new views using the 'VIEW MANAGEMENT CREATE' command, and
save/restore their attributes.
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
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 specified
8. If entered, the frame_number must be a positive integer corresponding to the desired frame (output
parameters. If none of the three are entered, the first frame will be displayed.
animation 13
animation modify
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), any
views that contain the model indicated by analysis_name will be affected
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.
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
to 1.
This is an optional parameter and if not entered then no superimposed frames will be drawn. The
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.
In addition, the "up" direction of the view is computed based on the direction of the
CAMERA_REF_MARKER "y" axis (that is, 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.
animation pause
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,
on the wheel center would be appropriate.
15. Entering 'ON' will cause Adams View to display the icons during animation. This will cause slower
Cautions:
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.
animation pause
Allows you to pause/stop an animation while it is running.
Format:
animation pause
Example:
animation pause &
page_name = page_1
Description:

page_name An Existing Page Specifies the page in the Adams Postprocessor that is to be
run
1. The parameter supplied to this command could be either an animation name or a page name (run
from the post processor)
animation 15
animation play
animation play
Allows you to play an animation.
Format:
animation play
Example:
animation play &
page_name = page_1
Description:

animation_name An Existing Animation Specifies an existing animation name that has to be run
run
type [time_marker, Specifies the type of the animation to play on a plot. The
advancing_curve] default is time_marker animation. In order to specify an
animation where the curves advance on the plot with the
animation time, specify the advancing_curve option
time_window Real value This parameter is applicable only to the advancing_curve
animation option and controls the width of the moving
time window on the plot, as the animation proceeds.
When one of the axes on the plot is time, then the axis limits
change with each frame of the animation according to the
time_window specified. For data vs data plots, the axis
limits stay unchanged during the animation and only the
time-sliced portion of the curve advances on the plot.
1. The parameter supplied to this command could either be an animation name or a page name (run
animation record start

Allows you to record the animation. The video file is saved in the current working directory.
Format:
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
Example:
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
Description:

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.
avi_compression Boolean Enters yes or no depending on whether or not the avi needs to be
compressed.
animation 17

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 "1" is the same as not using "Compress using P Frames", and
setting it to "12" means using "Compress using P Frames". Turn
off the compression using P frames to ensure your movie plays in
many playback programs, including xanim. It results, however, in
a much larger file (up to 4 times as large).
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.
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.
5. One can successfully record .avi movies of animations even if during the recording other windows are
placed in the foreground over top of the Adams PostProcessor window or if the Adams PostProcessor
window is moved (for example, to another monitor) or if it is minimized. Though, in the case of
window minimization, only the model animation records successfully; any adjacent panes of plot
tracking animation will not appear correctly.
Caution: AVI format is only available on Windows.

animation record stop
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.

Stop the animation recording
Format:
Example:
animation replace_simulation
Replace an existing analysis/page name with another in the animation.
Format:
animation replace_simulation
old_analysis_name = an existing analysis
new_analysis_name = a new analysis
Example:
animation replace_simulation &
animation_name = anim__1 &
old_analysis_name = last_run &
new_analysis_name = ana__1
animation 19
animation reset
Description:

animation_name An Existing Specify name of an existing animation.
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
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.
with an alphabetic or '_' character. They may be any length.
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:
be assigned to it.
animation reset
Allows you to reset an animation.
animation step
Format:
:
animation reset
Example:
animation reset &
animation_name = an existing animation &
Description:

run
1. The parameter supplied to this command could either be an animation name or a page name (run
animation step
Allows you to step the animation either forward or backwards as needed.
Format:
animation step
direction = animation_direction
Example:
animation step &
direction = forward &
page_name = page_1
animation 21
animation step
Description:

direction Animation_direction Specifies whether you want the animation to step in the
forward or backward direction
run
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.
putenv
toolkit
putenv
Allows you to set or change the value of an environment variable.
Format:
aview toolkit putenv
env = string
value = string
Example:
aview toolkit putenv &
env = "MY_VARIABLE" &
value = "1"
Description:

env string Character string denoting an environment variable.
value string Character string to be stored as the value of the environment
variable.
See view function PUTENV for more information.
break 1
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.
callback 1
callback copy
callback
callback copy
Allows you to copy an existing callback routine.
Format:
Callback copy
callback_name = Existing callback name
New_callback_name = String
Example:
callback copy &
callback_name = callback_1 &
New_callback_name = my_copy
Description:

Callback_name Existing callback Specifies the name of the callback to be modified.
New_callback_name String Specifies the new contact which will be a copy of the
existing one.
Tip: On typing "callback copy" followed by a "?" in the command window, the option
"callback_name =" is automatically displayed. If you need to find out the various contacts
already present, type ? once again. This will result in all the existing callback names that can be
copied being displayed in the command window.
callback create
Allows you to create multiple callback routines within a single model. This allows the design of HPC
solutions in the user space. It provides a clear framework for users who implement complex user subroutines
to design memory management and parallel simulations running along Adams simulation.
callback delete
Format:
Callback create
callback_name = New callback name
Adams_id = Integer
Routine = String
Priority = Integer
Example:
Callback create
routine = callback05::myCbksub &
priority = 1
Description:

Callback_name New callback Specifies the name of the callback to be created.
Adams_id Integer Assigns an unique id to the callback entity.
Routine String Specifies an alternative library and user subroutine name.
Priority Integer Used by the Solver to order existing CBKSUBS and call
subroutines according to their priority. Solver will sort from
higher to lower priority.
User-written subroutines are used primarily for modeling specialized phenomena or calculating nonstandard
results. Many simulations require the modeling of special phenomena that are not a part of the standard
Adams software. These phenomena may be expressed mathematically as differential equations, algebraic
equations, applied forces, constraints, motion inputs to system, or a combination of these general modeling
entities.
Adams Solver can accept user-specified descriptions of phenomena. You define the governing relationships
for the phenomena in the user-written subroutines. Adams then evaluates these relationships as part of the
solution process.
For more information about user-written subroutines and details about each of the user-written subroutines,
see User-Written Subroutines.
callback delete
Allows you to delete an existing callback routine.
callback 3
callback modify
Format:
Callback delete
Example:
Callback_delete &
Callback_name = CALLBACK_1
Description:

Callback_name Existing callback Specifies the name of an existing callback to be deleted
Tip: 1. On typing "calback delete" followed by a "?" in the command window, the option
"callback_name =" is automatically displayed. If you need to find out the various
contacts already present, type ? once again. This will result in all the existing callback
names that can be deleted being displayed in the command window.
2. You may reverse this deletion at a later time with an UNDO command.
callback modify
Allows you to modify an existing callback routine.
Format:
Callback modify
Adams_id = Integer
Routine = String
Priority = Integer
Example:
callback modify &
routine = “callback05::myCbksub” &
priority = 1
callback modify
Description:

Callback_name Existing callback Specifies the name of the callback to be modified.
Adams_id Integer Assigns an unique id to the callback entity.
Routine String Specifies an alternative library and user subroutine name.
Priority Integer Used by the Solver to order existing CBKSUBS and call
subroutines according to their priority. Solver will sort from
higher to lower priority.
User-written subroutines are used primarily for modeling specialized phenomena or calculating nonstandard
results. Many simulations require the modeling of special phenomena that are not a part of the standard
Adams software. These phenomena may be expressed mathematically as differential equations, algebraic
equations, applied forces, constraints, motion inputs to system, or a combination of these general modeling
entities.
Adams Solver can accept user-specified descriptions of phenomena. You define the governing relationships
for the phenomena in the user-written subroutines. Adams then evaluates these relationships as part of the
solution process.
For more information about user-written subroutines and details about each of the user-written subroutines,
see User-Written Subroutines.
check_messages 1
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:
check_messages
file_name = string
faults = boolean
errors = boolean
warnings = boolean
info = boolean
sort_by_time = boolean
Example:
check_messages &
faults = yes &
errors = yes &
warnings = no &
info = no &
sort_by_time = yes
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:

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.
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).
clearance 1
clearance compute
clearance
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:
clearance compute
treat_flex_as_rigid = yes/no
Example:
clearance compute &
analysis_name = Last_Run &
treat_flex_as_rigid = yes
Description:

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.
 The clearance study which is being carried out uses the analysis specified by the existing_analysis
parameter as the basis of the study.
Note: This command is for computing post-processing clearances only. Run-time clearances will not
be computed using this command.
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.
clearance create
Format:
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
Example:
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
clearance_name = .testdb.CLEARANCE_run_time &
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 3
clearance create
Description:

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 The first selected entity if it is a flexible body
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 The first selected entity if it is a flexible body
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.
j_exclude Boolean A list of Boolean values that specifies whether the regions listed
in the j_region parameter are to be excluded from the clearance
computation. This option is only available for run-time
clearances.
maximum Real To reduce the calculations in the clearance study, you can also
define a maximum distance above which Adams PostProcessor
does not calculate the clearance
clearance create

threshold Real For run-time clearances, specifies the threshold distance. When
the clearance distance exceeds the threshold value, the precise
check is skipped and the gross clearance value is returned.
method Selection List The calculation method used by the Adams PostProcessor for
clearance studies.
run_time Boolean Specifies whether the clearance is a run-time clearance or not. If
this parameter is not specified then the clearance is treated as a
post-processing clearance.
1. There are two distinct types of clearances supported in Adams, Run time clearances and Post
Processing clearances. If the run_time parameter is not specified or specified as "no" then, the
clearance is treated as a post-processing clearance. The parameters threshold, i_region, j_region,
i_exclude and j_exclude are available only with run-time clearances. The parameters method and
maximum are only available with post-processing clearances.
2. The information entered in the comments parameter is displayed as the title on the post-processing
clearance plot which can be generated by the Adams Postprocessor.
3. Clearance can be found out between two bodies which can be parts, flexible bodies or geometries. If
the first selected body happens to be a geometry, i_geometry should be selected as the parameter which
holds the first body for clearance create.
the second selected body happens to be a geometry, j_geometry should be selected as the parameter
which holds the second body for clearance create.
the first selected body happens to be a part, i_part should be selected as the parameter which holds
the first body for clearance create.
Note: Clearances between parts is allowed only for post-processing clearances.
the second selected body happens to be a part, j_part should be selected as the parameter which holds
the second body for clearance create.
Note: Clearances between parts is allowed only for post-processing clearances.
the second selected body happens to be a flexible body, i_flex should be selected as the parameter
clearance 5
clearance delete
Note: Only a single flexible body can be specified for post-processing clearance whereas
multiple flexible bodies separated by commas, can be specified for run-time clearances.
the second selected body happens to be a flexible body, j_flex should be selected as the parameter
Note: Only a single flexible body can be specified for post-processing clearance whereas
multiple flexible bodies separated by commas, can be specified for run-time clearances.
9. To reduce the calculations in the clearance study for post processing clearances, you can also define a
maximum distance above which Adams PostProcessor does not calculate the clearance. When you
play an animation, if the distance between the pair of objects is greater than the maximum distance
specified by you, Adams PostProcessor does not display a line between the objects. In addition, in the
clearance study reports, if the distance between two selected bodies exceeds the maximum distance
specified by you, Adams PostProcessor records the distance as the maximum distance and not the
actual distance.
10. For run-time clearances, the threshold parameter specifies a double precision distance. If the gross
clearance check is greater than this value, then the precise check is skipped and the gross value is
returned. By default, the threshold parameter has value 0.0, indicating that the precise check is always
to be done.
11. Adams PostProcessor uses two different calculations for clearance studies - polygon and vertex.
• Polygon
In the Polygon method, Adams PostProcessor calculates the minimum distance between the
surfaces of the triangles that make up the geometry. This is the most accurate method but requires
the most time and calculations. See also, Vertex.
• Vertex
In Vertex method, Adams PostProcessor calculates only the minimum distances between the
vertices of the triangles that make up the geometry. This method is less accurate than Polygon,
but calculates faster.
clearance delete
Allows you to delete an existing clearance study.
Format:
clearance delete
clearance_name = an existing clearance
clearance export_results
Example:
clearance delete &
clearance_name = Clearance_1
Description:

clearance_name An Existing Clearance Specifies an existing clearance to delete
Allows you to export the results of an existing post-processing clearance study to the specified file.
Format:
file_name = any file
Example:
clearance export_results &
file_name = "c:/testdir/test.out" &
analysis_name = Last_Run
Description:

file_name Any File Specifies the file to which the output is expected to be written
analysis_name An Existing This parameter gets assigned the name of any existing simulation
Simulation Analysis analysis.
1. This parameter gets assigned the name of the output file to which the results of the current clearance
study should be written.
2. This analysis specified by the analysis_name parameter is used as the basis for the clearance study
being carried out.
clearance 7
clearance modify
Note: This command is for exporting post-processing clearances only. Run-time clearances will not
be exported using this command.
clearance modify
Enables the user to modify an existing clearance study.
Format:
clearance modify
clearance_name = an existing clearance
new_clearance_name = a new clearance
comments = comment string
maximum = real value
threshold = real value
method = selection list
Example:
clearance modify &
clearance_name = clearance_4 &
new_clearance_name = clearance_4_new_1 &
comments = "clearace_4 modified &
maximum = 120.0
Description:

clearance_name Existing Clearance Specifies the name of an existing clearance study
new_clearance_name New Clearance Specifies the name of a new clearance study
comments String Comment string
clearance modify

maximum Real Value To reduce the calculations in the clearance study, you can
also define a maximum distance above which Adams
PostProcessor does not calculate the clearance. This
parameter can be specified only for post-processing
clearances.
threshold Real Value For run-time clearances, specifies the threshold distance.
When the clearance distance exceeds the threshold value,
the precise check is skipped and the gross clearance value is
returned.
method Selection List Specifies the calculation method for the clearance study.
This parameter can be specified only for post-processing
clearances.
1. When you play an animation, if the distance between the pair of objects is greater than the maximum
distance specified by you, Adams PostProcessor does not display a line between the objects. In
addition, in the clearance study reports, if the distance between two selected bodies exceeds the
maximum distance specified by you, Adams PostProcessor records the distance as the maximum
distance and not the actual distance. This parameter can only be specified in case the clearance was
defined to be of type post-processing clearance.
2. For run-time clearances, when the clearance distance exceeds the threshold value, the precise check is
skipped and the gross clearance value is returned. This parameter can only be specified in case the
clearance was defined to be of type run-time clearance.
3. Adams PostProcessor uses two different calculations for clearance studies - polygon and vertex.
• Polygon
In the Polygon method, Adams PostProcessor calculates the minimum distance between the
surfaces of the triangles that make up the geometry. This is the most accurate method but requires
the most time and calculations. See also Vertex.
• Vertex
In Vertex method, Adams PostProcessor calculates only the minimum distance between the
vertices of the triangles that make up the geometry. This method is less accurate than Polygon,
but calculates faster.
color 1
color create
color
Allows you to select a basic color or create a custom color to be used for displaying objects, the background
of the main window and any view windows that you create.
color create
Allows you to create a new color by specifying the red, blue and green components of the color.
Format:
color create
color_name = a new color
red_component = real
green_component = real
blue_component = real
Example:
color create &
Color_name = MY_COLOR &
Red_component = 0.98 &
Green_component = 0.89 &
Blue_component = 0.66
Description:

color_name A New Color Specifies the name of the new color to be created
red_component Real Specifies the amount of red in a color
green_component Real Specifies the amount of green in a color
blue_component Real Specifies the amount of blue in a color
1. Color_name should be different from the names of any of the existing colors present. If you need to
modify the hue of an existing color, then use the modify keyword within the command color.
2. Red_component can be a real value greater than or equal to zero and less than or equal to one. You
can use any combination of red, green, or blue to define a color.
color modify
3. Green_component can be a real value greater than or equal to zero and less than or equal to one. You
Blue_component can be a real value greater than or equal to zero and less than or equal to one. You
color modify
This command allows you to modify an existing color by changing the red, blue and green components of
the color.
Format:
color modify
color_name = an existing color
new_color_name = a new color
red_component = real
green_component = real
blue_component = real
Example:
color modify &
Color_name = MY_COLOR &
New_color_name = MODIFIED_COLOR &
Red_component = 0.99 &
Green_component = 0.89 &
Blue_component = 0.56
Description:

color_name An Existing Color Specifies an existing color
new_color_name A New Color Changes the name of the existing color
red_component Real Specifies the amount of red in a color
green_component Real Specifies the amount of green in a color
blue_component Real Specifies the amount of blue in a color
color 3
color modify
1. The new_color_name parameter allows the user to change the name of the existing color. For
example, if you make an existing color, RED, lighter by reducing its red component, you could
rename it as, say, LT_RED.
2. Red_componenet can be a real value greater than or equal to zero and less than or equal to one. You
3. Green_component can be a real value greater than or equal to zero and less than or equal to one. You
4. Blue_component can be a real value greater than or equal to zero and less than or equal to one. You
color modify
constraint 1
constraint attributes
constraint
Allows the specification of attributes to be set on an individual constraint or a group of constraints.
Format:
constraint_name = existing constraint
scale_of_icons = real
size_of_icons = length
visibility = on/off/no_opinion/toggle
name_visibility = on/off/no_opinion/toggle
color = existing color
active = on/off/no_opinion
dependents_active = on/off/no_opinion
Example:
constraint attributes &
constraint_name = joint_1 &
scale_of_icons = 1.2 &
visibility = on &
name_visibility = off &
active = on &
dependents_active = off
The above statement will set the new size of the icons by multiplying the current icon size by 1.2. The Joint_1
will be visible since its visibility parameter is turned ON. The visibility of the view name displayed at the top
center position of a given view will be turned OFF since the name_visibility parameter is turned OFF.
If JOINT_1 has a marker MAR1 which is the I marker of a joint JOI1 (which has a J marker MAR2), then
JOI1 will be deactivated as well because the dependants_active parameter being turned OFF.
Also, if the joint JOI1 is referenced in a request function, or if the I marker is referenced by a request, then
the request will be deactivated.
Description:

constraint_name Existing constraint Specifies the constraint to modify.
name
scale_of_icons Real Specifies a unit-less scale factor to apply to the current icon
size.
size_of_icons Length Specifies the size, in modeling units, the Adams View icons
will appear.
visibility On/Off/No_optinion/ Specifies the visibility of graphic entities.
Toggle
name_visibility On/Off/No_optinion/ The Name_Visibility parameter provides control over the
Toggle visibility of the view name displayed at the top center
position of a given view.
color Existing color Specifies the color the modeling entity should be drawn in.
active On/Off/No_opinion When you set Active=No, that element is written to the data
set as a comment. When you set the Active attribute on an
object, you are also setting it on the children of the object.
dependents_active On/Off/No_opinion Sets the active parameters for all the dependants of the
constraint.
1. You may identify a constraint by typing its name or by picking it from the screen.
• If the constraint is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the constraint is displayed.
• If you created the constraint by reading an Adams data set, the constraint name is the first three
letters of the Adams statement type followed by the Adams data set constraint ID number. The
name of ADAMS JOINT/101 is JOI101, for example. If you created the constraint during
preprocessing, you gave it a name at that time.
• If a constraint is available by default, you may identify it by entering its name only. If it is not,
you must enter its full name. To identify a constraint under a different model, for instance, you
may need to enter the model name as well. For example, you may specify constraint 'servo_motor'
from model 'test' by entering ".test.servo_motor". If you type a "?", Adams View will list the
constraints available by default.
• You must separate multiple constraint names by commas.
• If the constraint is visible in one of your views, you may identify it by picking on any of the
graphics associated with it.
• You need not separate multiple constraint picks by commas.
constraint 3
2. If no initial size is specified for Adams View icons, the default size will be one modeling LENGTH
unit. For example, if the modeling units are K/M/S, a part axes icon will have triad legs of one meter
in length.
When you specify SCALE_OF_ICONS, a new size is calculated by multipling the current size, by
the scale, and storing the product as the new ICON_SIZE.
in length.
When you set SIZE_OF_ICONS at the model level, all Adams View icons used in creating a model
will use the size specified.
If the model has an SIZE_OF_ICONS set, and a part under that model has a different
SIZE_OF_ICONS, the model's ICONS_SIZE will take precedence.
An Example:
.model ---------------------- SIZE_OF_ICONS = .15 meters
.constraint -------------------- SIZE_OF_ICONS = .125 meters
The constraint's icon will be 1.5 meters is size.
If the model has SIZE_OF_ICONS of set to 0.0 , and a constraint under that model has a
SIZE_OF_ICONS set to .125, the constraint's icon size will be used.
An Example:
.model ---------------------- SIZE_OF_ICONS = 0.0 meters
.constraint -------------------- SIZE_OF_ICONS = .125 meters
The constraint's icon will be .125 meters is size.
4. The visibility parameter is used to control whether graphic entities, such as markers, joints, and parts,
are to be drawn in an Adams View viewport. The legal values for this parameter are: ON, OFF, and
TOGGLE. ON will make the desired entity visible. OFF will make the desired entity invisible.
TOGGLE will take the current state of an entities visibility and reverse it.
5. The legal values of the visibility parameter are ON and OFF. This is an optional parameter and if not
entered the name will be visible (i.e. will be ON).
6. Adams View allows you to specify the following colors for modeling entities: BLACK, WHITE,
RED, GREEN, BLUE, CYAN, MAGENTA, YELLOW, and NO_COLOR
Specifying 'NO_COLOR' for a modeling entity, instructs Adams View to use the default color for
this entity, if there is no color present in its parent modeling entity.
Example 1:
.model -------------------------NO_COLOR
.part---------------------- RED
.geometry(circle) ------- NO_COLOR
The circle will be RED.
Example 2:
.model -------------------------NO_COLOR
.part---------------------- RED
.geometry(circle) ------- BLUE
If a parent modeling entity has a color previously specified, that color takes precedence. Adams View
will issue a warning message about color precedence. The circle will be RED.
Example 3:
.model -------------------------NO_COLOR
.part---------------------- NO_COLOR
The circle will be BLUE.
7. If you set ACTIVE=NO on a part, but wish for a marker on that part to be on, then you must
explicitly set ACTIVE=YES on the marker, after setting activation on the part.
The DEPENDENTS_ACTIVE parameter acts in the same fashion, but sets the ACTIVE attribute
for the dependents, all the way down the dependency chain. For example, if you execute the following
command:
PART ATTRIBUTES PART=PAR1 DEPENDENTS_ACTIVE=NO
Where PAR1 has a marker MAR1 which is the I marker of a joint JOI1 (which has a J marker MAR2),
then JOI1 will be deactivated.
Also, if the joint JOI1 is referenced in a request function, or if the I marker is referenced by a request,
then the request will be deactivated.
Propagation of activation status through groups is as if each element were to have its activation status
changed indvidually.
Elements affected are:
• Group
• Part
• Differential Equation
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
8. You can set the following attributes on a constraint.
 SIZE_OF_ICONS / SCALE_OF_ICONS: These two parameters are mutually exclusive. You may
set a size of the icon used for the constraint representation in modeling units, or you may scale the
size of the icon by a non-unit scale factor.
 VISIBILITY. You may set a constraint's visibility ON, OFF or TOGGLE the current setting. When
you set a constraint's visibility OFF, the constraint will not be drawn. When you set a constraint's
visibility ON, you allow that constraint to be drawn.
 NAME_VISIBILITY: You may set a constraint's name label visibility ON, OFF or TOGGLE the
current setting with this parameter.
constraint 5
constraint copy
 COLOR: You may set the color of a constraint with this parameter.
If an entity does not have a GRAPHICS ATTRIBUTE setting, the value for that GRAPHIC
ATTRIBUTE may be inherited from another entity. INHERITANCE may be either TOP_DOWN
or BOTTOM_UP.
BOTTOM_UP and TOP_DOWN refer to the natural hierarchy of the Adams model. The hierarchy
is a tree structure with the model at the apex. Parts exist beneath the model, and markers exist beneath
the parts. If the icon size of the model is set to 0.1, and the default INHERITANCE is set to
TOP_DOWN, then all icons displayed within the model will be displayed at this size. However, if
the icon size of a model is set to 0.1, and then the default INHERITANCE is set to BOTTOM_UP,
then any icons set to a size other than the model's icon size will be displayed at their own size.
Caution: Note that if the visibility of the view name is turned off the only indication that a view is
"active" will be the color of the viewport border. This would be a problem on a black and white
monitor.
Tip: Use the constraint_name parameter to identify the existing constraint to affect with this
command.
constraint copy
Allows you to create a replica constraint within the same model.
Format:
constraint copy
new_constraint_name = new constraint name
Example:
constraint copy &
new_constraint_name = copy_joint_1
Description:

Constraint_name Existing constraint Specifies the constraint to delete.
new_constraint_name New constraint name Specifies the name of the new constraint.
constraint copy
1. Any Adams View object you delete, may be "undeleted" by using the UNDO commands. If you have
deleted something you would like back, enter the command "undo backward", or pick on the fixed
menu entry 'UNDO'.
• You may identify a constraint by typing its name or by picking it from the screen.
name of Adams joint/101 is JOI101, for example. If you created the constraint during
you must enter its full name.
• To identify a constraint under a different model, for instance, you may need to enter the model
name as well. For example, you may specify constraint 'servo_motor' from model 'test' by
entering ".test.servo_motor". If you type a "?", Adams View will list the constraints available by
default.
2. Adams View will not allow you to have two constraints with the same full name, so you must provide
a unique name.
Normally, entity names are composed of alphabetic, numeric, or '_' (underscore) characters, and start
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 an entity, Adams View will provide a default
name. The default name that Adams View provides will specify the parentage that it has assumed.
be assigned to it.
3. This replica constraint will be identical to the original with the exception of the constraint name.
Constraints must have unique names relative to other constraints in a given model. The replica will
be completely independent of the original, and may be modified without effecting the original.
constraint 7
constraint create complex_joint coupler
When the new constraint is created, it uses the same markers or joints as the original. A first step after
the copy of a joint constraint might be to modify the I and J markers on the replica.
Constraints may not be copied from model to model.
Tip: You may use the new_constraint_name later to refer to the constraint.

Allows the creation of a coupler.
Format:
coupler_name = a new coupler
adams_id = adams_id
comments = string
joint_name = an existing joint
type_of_freedom = coupler_freedom
motion_multipliers = real
first_angular_scale_factor = angle
first_scale_factor = real
second_angular_scale_factor = angle
second_scale_factor = real
third_angular_scale_factor = angle
third_scale_factor = real
user_function = real
Example:
constraint create complex_joint coupler &
coupler_name = coupler__1 &
adams_id = 1 &
comments = "comment string" &
joint_name = joint_1 , joint_1 &
motion_multipliers = 0.1 , 0.2 &
type_of_freedom = rot_rot_rot
Description:

coupler_name A New Coupler Specifies the name of the new coupler. You may use
this name later to refer to this coupler.
adams_id Adams_id Specifies an integer used to identify this element in
the Adams data file.
comments String Specifies comments for the object being created or
modified.
joint_name An Existing Joint Specifies the translational, revolute, or cylindrical
joint associated with this entity. Some entities
constrain motion at, or are otherwise associated with,
specific joints. You use this parameter to identify that
joint.
type_of_freedom Coupler_freedom Specifies whether cylindrical joints transfer
translational or rotational motion.
motion_multipliers Real Specifies the relative motion of the joints you identify
with joints
first_angular_scale_factor Angle Specifies the angular motion of the first joint you
identify with JOINT_NAME relative to the motion
of the second and third joints you identify with
Joint_Name.
first_scale_factor Real Specifies the non-angular motion of the first joint
you identify with JOINT_NAME relative to the
motion of the second and third joints you identify
with Joint_Name.
second_angular_scale_factor Angle Specifies the angular motion of the second joint you
identify with Joint_Name relative to the motion of
the first and third joints you identify with
JOINT_NAME
second_scale_factor Real Specifies the non-angular motion of the second joint
you identify with Joint_Name relative to the motion
of the first and third joints you identify with
Joint_Name.
constraint 9

third_angular_scale_factor Angle Specifies the angular motion of the third joint you
identify with Joint_Name relative to the motion of
the first and second joints you identify with
Joint_Name.
third_scale_factor Real Specifies the non-angular motion of the third joint
you identify with Joint_Name relative to the motion
of the first and second joints you identify with
Joint_Name.
user_function Real Specifies up to 30 values for Adams to pass to a
userwritten subroutine. See the Adams User's
Manual for information on writing user-written
subroutines.
1. A coupler creates the coupling of the translational and/or the rotational motion of two or three joints.
With this constraint, you can deliver or relate motion from one area of a mechanism to another.
Components whose behavior you might approximate with this statement include combinations of
hydraulic generators, motors, and pistons and include flexible, rotational transmission cables.
2. Normally, entity names like the coupler name are composed of alphabetic, numeric, or '_'
(underscore) characters, and start with an alphabetic or '_' character. They may be any length. By
enclosing the name in double quotes, you may use other printable characters, or start the name with
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 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 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, or course, delete this name and use your own. The form of a full name is:
be assigned to it.
3. When you use the File Adams_data_set write command, Adams View writes an Adams data file
for your model. Adams requires that each modeling element be identified by a unique integer
identifier. If you use this parameter to specify a non-zero identifier, Adams View will use it in the
corresponding statement in the Adams data file. You may also enter zero as an identifier, either
explicitly or by default. The next time you write an Adams file, Adams View will replace the zero with
a unique, internally-generated identifier. Adams View will permanently store this identifier with the
element just as if you had entered it yourself. Normally, you would let all identifiers default to zero,
and Adams View would generate the identifiers for you. You are never required to enter a non-zero
identifier. You only need to specify it if, for some reason, you wish to control the Adams file output.
4. When an Adams Solver data file (.adm) is read into Adams View, all comments associated with a
statement (from the end of the previous statement through the end of the current statement) are
stored with the object. Comments in the data file can be associated with model. These comments
must follow the title statement and be followed by the comment 'END OF MODEL
COMMENTS'. This string must be uppercase. When an Adams Solver data file is written, the
comments for an object are written before the statement corresponding to the object.
5. You may identify a joint by typing its name or by picking it from the screen. If the joint is not visible
on the screen, you must type the name. You may also find it convenient to type the name even if the
joint is displayed. If you created the joint by reading an data set or graphics file, the joint name is the
letters JOI followed by the Adams data set joint ID number. The name of Adams JOINT/101 is
JOI101, for example. If you created the joint during preprocessing, you gave it a name at that time.
If a joint is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a joint under a model, for instance, you may need to enter the model
name as well. For example, you may specify joint 'lower_pivot' in model 'links' by entering
".links.lower_pivot". You must separate multiple joint names by commas. If the joint is visible in one
of your views, you may identify it by picking on any of the graphics associated with it. You need not
separate multiple joint picks by commas.
6. Adams assumes that translational joints transfer translational motion and that revolute joints transfer
rotational motion. A cylindrical joint permits both translational and rotational motion, however. If
your coupler includes cylindrical joints, you must use this parameter to indicate which motion is
transferred at each joint.
7. Adams uses the values in the SCALES argument in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
where r1, r2, and r3 are the scale factors for the three joints and q1, q2, and q3 are the translational
or the rotational displacements of the joint I markers with respect to their J markers. Suppose you are
coupling two joints, and SCALES=1,-2. The equation that relates the two joints is
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
The displacement (q1) of the I marker with respect to the J marker in the first joint is twice that of
the displacement (q2) of the I marker with respect to the J marker in the second joint; the two
displacements have the same sign. If you specify two joints in the JOINTS argument, you must
specify r2. If you specify only one value, Adams assumes it is r2 and uses the default value of 1 for r1.
8. Adams uses the first_angular_scale_factor (r1) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
coupling two joints, and r1=1 and r2=-2. The equation that relates the two joints is
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
displacements have the same sign.
constraint 11
9. Adams uses the first_scale_factor (r1) in the following equation:

(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
10. Adams uses the second_angular scale_factor (r2) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
11. Adams uses the second_scale_factor (r2) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
12. Adams uses the third_angular_scale_factor (r3) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
or the rotational displacements of the joint I markers with respect to their J markers.
13. adams uses the third_scale_factor (r3) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
constraint create complex_joint gear
Caution: Adams View will not allow you to have two couplers with the same full name, so you must
provide a unique name.
Tip: If you type a "?", Adams View will list the joints available by default.

Allows the creation of a gear pair.
Format:
joint_name = a new gear
adams_id = integer
comments = string
common_velocity_marker = an existing marker
Example:
constraint create complex_joint gear &
gear_name = gear__1 &
adams_id = 3 &
joint_name = joint_1 &
common_velocity_marker = marker_1
Description:

gear_name A New Gear Specifies the name of the new gear.
constraint 13

modified.
joint associated with this entity.
common_velocity_ marker An Existing Marker Specifies the marker that designates the point of
contact and determines the ratio of the two gears.
1. A gear pair relates the motion of three parts and two joints. The three parts are the two gear parts and
a third part, the carrier, to which the gears are attached by the two joints. The joints must be
translational, revolute, or cylindrical. Different combinations of joint types and orientations allow
you to model spur, helical, planetary, bevel, and rack-and-pinion gear pairs.
2. The gear element uses the location of the common velocity marker to determine the point of contact
of the two gear pitch circles. The direction of the z-axis of the common velocity marker indicates the
direction of the common velocity of points on the gear teeth in contact. This is also the direction in
which gear tooth forces act. The location of the common velocity marker is constant with respect to
the carrier part.
3. Normally, entity names like the gear name are composed of alphabetic, numeric, or '_' (underscore)
characters, and start with an alphabetic or '_' character. They may be 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. Note that you can specify the parentage of an entity (for example, what part "owns" a marker or a
be assigned to it.
4. When you use the FILE Adams_data_set write command, Adams View writes an Adams data file for
your model. Adams requires that each modeling element be identified by a unique integer identifier.
If you use this parameter to specify a non-zero identifier, Adams View will use it in the corresponding
statement in the Adams data file. You may also enter zero as an identifier, either explicitly or by
default. The next time you write an Adams file, Adams View will replace the zero with a unique,
internally-generated identifier. Adams View will permanently store this identifier with the element
just as if you had entered it yourself. Normally, you would let all identifiers default to zero, and Adams
View would generate the identifiers for you. You are never required to enter a non-zero identifier. You
only need to specify it if, for some reason, you wish to control the Adams file output.
constraint create general_constraint
joint is displayed. If you created the joint by reading an Adams data set or graphics file, the joint name
is the letters JOI followed by the Adams data set joint ID number. The name of Adams joint/101 is
JOI101, for example. If you created the joint during preprocessing, you gave it a name at that time.
7. You define the constant-velocity (CV) marker on the carrier part to which the J markers of the joints
belong. The z-axis of this marker must point in the direction of common velocity at the point of
contact. The direction of common velocity is tangent to both pitch circles and would be normal to
the tooth surfaces of the gears if the pressure angle was zero. (Adams always assumes a pressure angle
of zero.) The CV marker has constant position and orientation in the carrier LPRF and does not
change when the direction of power flow through the gear changes.
Tip: 1. If you type a "?", Adams View will list the joints available by default.
2. You may use the gear_name later to refer to this gear. Adams View will not allow you
to have two gears with the same full name, so you must provide a unique name.
3. Some entities constrain motion at, or are otherwise associated with, specific joints. You
use the joint_name parameter to identify that joint.
4. The common_velocity_marker also determines the direction of the reaction forces
developed by the joints in the gear pair.

Format:
general_constraint_name = new gen_constraint name
adams_id = geom. _id
comments = string,
constraint 15

i_marker_name = existing marker
function = function
Example:
constraint create general_constraint &
general_constraint_name = gcon_1 &
i_marker_name = marker_11 &
function = time
Description:

general_constraint_name New name Specify a name for the GCON
adams_id integer Specifies an integer used to identify this element in the
Adams data file.
modified.
I_marker_name Existing marker Specify an existing marker name.
function Function Specifies an expression or defines and passes constants to a
user-written subroutine to define the motion.
1. When you use the File Adams_data_set write command, Adams View writes an Adams data file for
statement in the Adams data file.
You may also enter zero as an identifier, either explicitly or by default. The next time you write an
Adams file, Adams View will replace the zero with a unique, internally-generated identifier. Adams
View will permanently store this identifier with the element just as if you had entered it yourself.
Normally, you would let all identifiers default to zero, and Adams View would generate the identifiers
for you. You are never required to enter a non-zero identifier. You only need to specify it if, for some
reason, you wish to control the Adams file output.
2. You may identify a joint by typing its name or by picking it from the screen.
If the joint is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the joint is displayed.
If you created the joint by reading an Adams data set or graphics file, the joint name is the letters JOI
followed by the Adams data set joint ID number. The name of Adams JOINT/101 is JOI101, for
example. If you created the joint during preprocessing, you gave it a name at that time.
".links.lower_pivot". If you type a "?", Adams View will list the joints available by default.
You must separate multiple joint names by commas.
If the joint is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple joint picks by commas.
3. While the JOINT statement describes a physically recognizable combination of constraints that are
used to connect bodies together, the GCON statement enables you to define an arbitrary constraint
specific to a particular model. The GCON statement is more general and can be used to equivalently
define the existent JOINT elements. Therefore, the spherical joint
JOINT/11, SPHERICAL, I=1,J=3
could be equivalently replaced by the following set of three GCONs:
GCON/111, I=2, FUNC=DX(2,3)
GCON/112, I=2, FUNC=DY(2,3)
GCON/113, I=2, FUNC=DZ(2,3)
The GCON statement allows you to define both holonomic and non-holonomic constraints.
Holonomic constraints only depend on position measures, like GCON/111 through GCON/113
above. A constraint is non-holonomic if (a) its expression exp1 contains velocity measures, and (b)
there is no expression exp2 that is the time integral of exp1. An example of a non-holonomic constraint
is a roll without slip condition
GCON/34, FUNC=VX(2) - WZ(2)*DY(2)
The GCON statement introduces a constraint to Adams Solver (C++) that is guaranteed to be
handled correctly as long as the FUNCTION is in Pfaffian form. In this context, note that any
holonomic expression is automatically in Pfaffian form. In the case of non-holonomic constraints, a
Pfaffian constraint requires that the FUNCTION is limited to expressions that are linear in velocity
quantities. In other words, if there are velocity quantities in the definition of the FUNCTION (as is
the case in the previous GCON), a partial derivative of the FUNCTION with respect to any velocity
quantity present in its definition should lead to an expression that does not depend on velocity
∂FUNC
quantities. The previous GCON is therefore in Pfaffian form, since -------------------- = 1
∂FUNC
∂FUNC
and -------------------- = – DX ( 2 ) which makes the FUNC linear in velocity quantities.
∂WZ ( 2 )
Another example of a Pfaffian non-holonomic constraint is the perpendicularity condition
GCON/25, FU=VX(2,3)*DX(2,1)+ VY(2,3)*DY(2,1)+ VZ(2,3)*DZ(2,1)
that indicates that the velocity V(2,3) is orthogonal to the distance vector between markers I=2 and
J=1.
constraint 17
An example of a non-Pfaffian GCON is

GCON/25,FU=VX(2,3)*VX(2,3)*DX(2,1)+VY(2,3)*DY(2,1)+
VZ(2,3)*DZ(2,1)
∂FU
For this example, ------------------------ = 2 ⋅ VX ( 2, 3 ) ⋅ DX ( 2, 1 ) which is an expression that depends on the
∂VX ( 2, 3 )
velocity measure VX(2,3).
The FUNCTION expression exp can reference variables defined in the .adm file through the
VARVAL construct. It should be stressed again that correct handling of the GCON requires that the
expression defining the VARIABLE only depends on time, and position and velocity measures; in
other words, the Pfaffian character of the GCON is not undermined by the presence of the VARVAL.
Cautions:
1. Objects of type General_Constraint are not compatible with Adams Solver (FORTRAN).
2. The topology of the model has changed so .model_1.GCON__1 is no longer connected in a way that
is compatible with Adams Solver (FORTRAN).
3. An attribute of .model_1.GCON__1 is no longer compatible with Adams Solver (FORTRAN).
If you intend to use Adams Solver (FORTRAN), you must change your model to eliminate the
incompatibility. For more information, see the online help for the object listed.
If you do not want to use Adams Solver (FORTRAN), then be sure that you set your preferences so
Adams Solver (C++) is the default as follows:
a. From the Settings menu, point to Solver and then select either Solver Executable or Preferences,
depending on the product you are using.
b. To learn more, press F1 in the dialog box.
 Correct handling of a GCON element assumes a FUNCTION defined in Pfaffian form.
 Kinematic models are incompatible with velocity constraints. If a model is rendered kinematic by
displacement constraints, any additional velocity constraints will be either redundant or conflicting.
In either case, version 2003 of Adams Solver (C++) is incapable of analyzing the model as explained
below:
Currently, there is no redundancy check for user constraints defined at the velocity level. Therefore,
you can impose constraints that are not redundant at the position level, but lead to a set of redundant
constraints when their time derivative is considered with other velocity level constraints during the
velocity Initial Conditions (IC) analysis. Consider the situation when two constraints are defined as
GCON/1, FU=DX(1,2), and GCON/2, FU=VX(1,2). Because the redundant constraint analysis
only includes position level constraints, Adams Solver (C++) will not identify that a velocity-level
constraint (GCON/2) induces a redundant constraint during the velocity computation. As a result,
a model that contains these two user constraints will fail during the velocity analysis with a singular
Jacobian error.
 GCON is a new modeling element only available in the Adams Solver (C++). Currently there is no
support for defining GCON through Adams View, so you need to edit the .adm file to add user-
defined constraints. Adams View correctly imports the edited .adm file, and the internal Adams
Solver (C++) from within Adams View correctly handles the simulation of the model.
constraint create higher_pair_contact curve_curve
 If you use GCON to constrain the values of DIFF, LSE, and TFSISO elements, note that they will
not contribute degrees of freedom that are considered removed by a GCON element. The GCON
statement functions properly for Pfaffian expressions depending on position and velocity measures
and time, or as mentioned earlier, on VARVALs measures for VARIABLEs that only depend on
position and velocity measures and time.
 Consequently, a model that contains velocity constraints can only be simulated using the dynamic
solver.
 For a position-level GCON, the FUNCTION must be at least three times differentiable. If the
GCON introduces a velocity-level constraint, then the FUNCTION should be at least twice
differentiable. This requirement ensures that internally Adams Solver (C++) can take the necessary
derivatives to perform certain types of analyses such as Acceleration/Force reconciliation, dynamic
analysis, and so on. Note that if the expression provided for GCON is not continuously
differentiable for the required number of times, the integrator will either fail, or have a difficult time
finding the numerical solution.
 The ability of the Adams Solver (C++) to handle function expressions to provide the necessary
derivatives required by the GCON does not extend to user subroutines. Consequently, a
VARIABLE can only be referenced in a GCON provided it is defined using function expressions,
rather than a VARSUB subroutine.
 Use the RESULTS/XRF statement in order to get the reaction force on marker I reported in the
results file. This is the only output format currently able to handle GCON output.
Tip: There is no dedicated function that returns the reaction force induced by a user constraint on
a marker. You can invoke an existing function such as FX(I[; J][;K]) for this purpose. Note that
FX(I[; J][;K]) reports the force that acts on the I marker as a result of both constraint and
external forces applied to this marker. To only obtain the contribution of the the GCON, the
markers that appear in FX(I[; J][;K]) should be exclusively used to define the GCON, and no
other elements such as applied forces, joints, or motions should refer them.

Allows you to create a curve_curve constraint.
Format:
curve_curve_name = new ccurve
adams_id = geom._id
comments = string
i_curve_name = existing acurve
J_curve_name = existing acurve
I_ref_marker_name = existing marker
constraint 19

J_ref_marker_name = Existing marker
i_marker_id = integer
J_marker_id = integer
I_displacement_ic = length
no_i_displacement_ic = true
j_displacement_ic = length
no_j_displacement_ic = true
i_ velocity_ic = velocity
no_i_velocity_ic = true
j_velocity_ic = velocity
no_j_velocity_ic = true
i_ ic_ref_marker_name = existing marker
ji_ ic_ref_marker_name = existing marker
Description:

curve_curve_name New ccurve Specifies the name of the new curve_curve. You may
use this name later to refer to this curve_curve.
adams_id Integer Specifies an integer used to identify this element in
the Adams data File.
Comments String Specifies comments for the object being created or
modified.
i_curve_name Existing Acurve name Specifies the name of a CURVE from which Adams
constructs the first Curve
J_curve_name Existing acurve Specifies the name of a CURVE from which Adams
constructs the second curve.
I_ref_marker_name Existing marker Specifies the name of a fixed MARKER on the part
containing I_CURVE.
J_ref_marker_name Existing marker Specifies the name of a fixed MARKER on the part
containing J_CURVE.
I_floating_marker_name Existing marker Specify an existing floating marker.
J_floating_marker_name Existing marker Specify an existing floating marker.

I_marker_id Integer Specifies the Adams ID for the floating marker
which is automatically created on the I part by
Adams View.
J_marker_id Integer Specifies the ID for the floating marker which is
automatically created on the J part by Adams View.
This allows you to reference the floating marker in a
request or function by the id you specify, instead of
letting Adams View generate one.
I_displacement_ic Length Specifies the initial point of contact on the first
curve.
J_displacement_ic Length Specifies the initial point of contact on the second
curve.
No_i_displacement_ic True Specifies that if an I_DISPLACEMENT_IC has
been set via any means, to "UNSET" the
displacement initial condition.
No_j_displacement_ic True Specifies that if an J_DISPLACEMENT_IC has
I_velocity_ic Velocity Specifies the initial velocity of the contact point
along I_CURVE.
J_velocity_ic Velocity Specifies the initial velocity of the contact point
along J_CURVE.
No_i_velocity_ic True Specifies that if an I_VELOCITY_IC has been set
via any means, to "UNSET" the velocity initial
condition.
No_j_velocity_ic True Specifies that if an J_VELOCITY_IC has been set
condition.
I_ic_ref_marker_name An existing marker Specifies the name of a fixed MARKER defining the
coordinate system in which the values for
I_DISPLACEMENT_IC are defined. The
I_IC_REF_MARKER must be on the same part as
the I_REF_MARKER.
J_ic_ref_marker_name An existing marker Specifies the name of a fixed MARKER defining the
coordinate system in which the values for
J_DISPLACEMENT_IC are defined. The
J_IC_REF_MARKER must be on the same part as
the J_REF_MARKER.
constraint 21
1. Adams View will not allow you to have two point_curves with the same full name, so you must
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 an entity, Adams View will provide a default
be assigned to it.
3. The I_REFERENCE_MARKER marker specifies the coordinate system in which the x, y, z
coordinates of I_CURVE are specified. The curve is attached rigidly to the part specified in the
I_PART_NAME parameter and containing the I_REFERENCE_MARKER marker. The z
component of the CURVE must be zero. As a result, the curve will lie in the x-y plane of the
I_REFERENCE_MARKER marker.
4. The J_REFERENCE_MARKER specifies the coordinate system in which the x, y, z coordinates of
J_CURVE are specified. The curve is attached rigidly to the part specified in the J_PART_NAME
parameter and containing the J_REFERENCE_MARKER. The z component of the CURVE must
be zero. As a result, the curve will lie in the x-y plane of the J_REFERENCE_MARKER.
5. The I_REF_MARKER marker identifies the coordinate system in which the coordinates of ICURVE
are specified. Adams constructs the I_CURVE in the I_REF_MARKER marker coordinate system.
Adams View will automatically create the I "floating" marker. The I "floating marker" and
I_REF_MARKER markers must lie on the same part.
6. The J_REF_MARKER marker identifies the coordinate system that the coordinates of J_CURVE are
specified. Adams constructs the J_CURVE in the J_REF_MARKER coordinate system. The J
"floating" and J_REF_MARKER markers must lie on the same part.
7. For the i_displacement_ic parameter, if the point specified is not exactly on the curve, Adams will use
a point on the curve nearest to that specified. By default, the contact point is specified in the
I_REF_MARKER coordinate system. If another coordinate system is more convenient, you may
supply the I_IC_REF_MARKER argument and enter I_DISPLACEMENT_IC in
I_IC_REF_MARKER coordinates.
If you supply I_DISPLACEMENT_IC, Adams assembles the system with the contact at the specified
point on the curve, even if it must override part initial conditions in order to do so. If you do not
supply I_DISPLACEMENT_IC, Adams assumes the initial contact is at the point on the first curve
closest to J_CURVE in the input configuration. In this case, Adams may adjust that contact point to
maintain other part or constraint initial conditions.
8. For the j_displacement_ic parameter, if the point specified is not exactly on the curve, Adams uses a
point on the curve nearest to that specified. By default, the contact point is specified in the
J_REF_MARKER coordinate system. If another coordinate system is more convenient, you may
supply the J_IC_REF_MARKER and enter J_DISPLACEMENT_IC in J_IC_REF_MARKER
coordinates.
If you supply J_DISPLACEMENT_IC, Adams assembles the system with the contact at the specified
supply J_DISPLACEMENT_IC, Adams assumes the initial contact is at a point on the second curve
closest to ICURVE in the input configuration. In this case, Adams may adjust that contact point to
9. The i_velocity_ic is the speed at which the contact point is initially moving relative to the curve.
I_VELOCITY_IC is negative if the contact point is moving towards the start of the curve, positive if
the contact point is moving toward the end of the curve, and zero if the contact point is stationary on
the curve.
If you supply I_VELOCITY_IC, Adams gives the contact point the specified initial velocity along
the first curve, even if it must override part initial conditions in order to do so. If you do not supply
I_VELOCITY_IC, Adams assumes the initial velocity is zero, but may adjust that velocity to
10. The j_velocity_ic is the speed at which the contact point is initially moving relative to the curve.
J_VELOCITY_IC is negative if the contact point is moving towards the start of the curve, positive if
the curve.
If you supply J_VELOCITY_IC, Adams gives the contact point the specified initial velocity along
the second curve, even if it must override part initial conditions in order to do so. If you do not supply
J_VELOCITY_IC, Adams assumes the initial velocity is zero, but may adjust that velocity to
11. The CURVE_CURVE defines a curve-curve constraint, which restricts a planar curve on one part
to be in contact with, and tangent to, a planar curve on a second part. The curves must lie in parallel
planes.
constraint 23
Adams constructs the first curve from the I_CURVE curve and the I_REF_MARKER, the second
curve from the J_CURVE value and the J_REF_MARKER. In both cases, the CURVE command
(I_CURVE or J_CURVE) defines x and y coordinates along the curve as a function of the
independent parameter (u). The z coordinates of the curves must be zero. The reference marker
(I_REF_MARKER or J_REF_MARKER) defines the part the constraining curve is attached to and
the coordinate system in which Adams applies the coordinates from the CURVE statement. Both
I_CURVE and J_CURVE may be open or closed, defined analytically or as a set of discrete data
points.
The CURVE_CURVE constraint removes three degrees-of-freedom from the system. Adams restricts
the motion of the parts such that the curves are always in contact and the curves are tangent at the
contact point. Although Adams requires that the curves lie in parallel planes, the CURVE_CURVE
command does not enforce this. You must build the model in such a way that the curves are held in
parallel planes, which will remove another three degrees of freedom. Assuming the curves are held in
parallel planes, a CURVE_CURVE leaves two relative degrees of freedom between the curves. The
first curve may slide or roll on the second, but may not move perpendicular to the curve tangents at
the contact.
Internally, Adams actually generates five constraint equations, but also adds two new system variables
and equations for a net decrease of one degree-of-freedom. The added system variables are the two
curve parameters at the contact points on the curves. Two of the constraints restrict the x and y
coordinates at the contact point on the first curve to match the x and y coordinates at the the contact
point on the second curve. The third constraint restricts the tangent at the contact point on the first
curve to be parallel to the tangent at the contact point on the second curve.
More than one POINT_CURVE or CURVE_CURVE statement may reference the same CURVE
statement. If the mechanism contains several similar contacts, you may enter just one CURVE
statement, then use it with several POINT_CURVE or CURVE_CURVE constraints, each with a
different REF_MARKER.
The I_VELOCITY_IC and J_VELOCITY_IC are specified in the reference frame of the part
containing the I_REF_MARKER or J_REF_MARKER marker, respectively. In other words, the
I_VELOCITY_IC is the speed of the contact point specified from the standpoint of an observer on
the part containing the first curve. This means if the contact point is not moving globally, but the
first curve is, then I_VELOCITY_IC is still non-zero.
Adams detects a fatal user error if the contact point moves off the end of an open curve. You should
make sure the CURVE statement defines the curve over the expected range of motion. The initial
conditions arguments, I_DISPLACEMENT_IC, J_DISPLACEMENT_IC, I_VELOCITY_IC and
J_VELOCITY_IC, impose constraints that are active only during an initial conditions analysis.
Adams does not impose these initial conditions during subsequent analyses.
For a kinematic analysis, the initial conditions are redundant. Do not use the
I_DISPLACEMENT_IC, J_DISPLACEMENT_IC, I_VELOCITY_IC or J_VELOCITY_IC
arguments on the CURVE_CURVE statements for systems with zero degrees of freedom.
Adams requires that there be a unique contact point in the vicinity of the I floating and J floating
markers during simulation. If this condition is violated, Adams may be unable to find the correct
contact point or may even jump from one contact point to the next.
constraint create higher_pair_contact point_curve
One way to ensure that contact points are unique is to specify curve shapes that are convex. Note that
for a convex curve, any line segment connecting two points on the curve lie in the domain of the
curve. The same is not true for non-convex curves.
Caution: For the no_i_displacement_ic,no_j_displacement_ic,no_i_velocity and no_j_velocity

parameters, setting these parameters to true is not the same as setting the value to zero. A zero
displacement/velocity is not the same as "no" displacement/velocity. Therefore, by setting this
parameter to true there is no longer a displacement/velocity initial condition for this element.
Note: The I- and J- marker id allow you to reference the floating marker in a request or function by
the id you specify, instead of letting Adams View generate one.

Allows you to create a point_curve.
Format:
point_curve_name = new pcurve
adams_id = geom._id
comments = string
curve_name = existing acurve
i_part_name = existing body
location = location
relative_to = an existing model, part or marker
i_marker_name = An existing marker
j_floating_marker_name = An existing fmarker
j_marker_id = integer
ref_marker_name = existing marker
displacement_ic = length
no_displacement_ic = true
velocity_ic = velocity
no_velocity_ic = true
ic_ref_marker_name = existing marker
constraint 25
Description:

point_curve_name New Pcurve Specifies the name of the new point_curve. You may
use this name later to refer to this point_curve.
modified.
curve_name Existing Acurve name Specifies the name of a CURVE that defines the
contour or shape on which the fixed marker can
move.
i_part_name Existing body Specifies the name of the part which will have a point
location constrained to lie on the curve defined by
CURVE and REF_MARKER.
location Location Specifies the point location on the i part that will be
constrained to lie on the curve defined by CURVE
and REF_MARKER.
relative_to Existing part, body or Specifies the coordinate system that location
marker coordinates and orientation angles are with respect to.
i_marker_name Existing marker name Specifies the name of a fixed MARKER that Adams
constrains to lie on the curve defined by CURVE and
REF_MARKER.
j_floating_marker_name Existing floating Specify an existing floating marker name.
marker name
j_marker_id Integer Specifies the Adams ID for the floating marker which
is automatically created on the J part by Adams View.
request or function by the id you specify, instead of
ref_marker_name Existing marker Specifies the name of a MARKER fixed on the part
containing the curve on which the I_MARKER must
move.
displacement_ic Length Specifies the initial point of contact on the curve.
no_displacement_ic true Specifies that if a DISPLACEMENT_IC has been set
via any means, to "UNSET" the displacement initial
condition.

velocity_ic Velocity Specifies the initial tangential velocity of the
I_MARKER along the curve.
no_velocity_ic True Specifies that if a VELOCITY_IC has been set via
any means, to "UNSET" the velocity initial
condition.
ic_ref_marker_name Existing marker Specifies the name of a the fixed MARKER defining
the coordinate system in which the values for
DISPLACEMENT_IC values are specified.
The IC_REF_MARKER must be on the same part as

the REF_MARKER.
be assigned to it.
2. When you use the FILE Adams_DATA_SET WRITE command, Adams View writes an Adams data
file for your model. Adams requires that each modeling element be identified by a unique integer
corresponding statement in the Adams data file.
constraint 27
3. The specfied part and the curve must belong to different parts. You may identify a part by typing its
name or by picking it from the screen.
If the part is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the part is displayed.
If you created the part by reading an Adams data set or graphics file, the part name is the letters PAR
followed by the Adams data set part ID number. The name of Adams PART/101 is PAR101, for
example. If you created the part during preprocessing, you gave it a name at that time.
If a part is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a part under another model, for instance, you may need to enter the
model name as well. For example, you may specify part 'arm' from model 'robot' by entering
".robot.arm". If you type a "?", Adams View will list the parts available by default.
You must separate multiple part names by commas.
If the part is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple part picks by commas.
4. The "floating" marker is automatically created by Adams View on the part specified in the
J_PART_NAME parameter. Adams will orient the J floating marker so that its x-axis is along the
tangent vector at the contact point, its y-axis is along the gradient vector at the contact point in the
plane containing the tangent vector and the center of curvature, and its z-axis is along the binormal
at contact point.
You may identify a part by typing its name or by picking it from the screen.
followed by the Adams data set part ID number. The name of Adams PART/101 is PAR101, for
example. If you created the part during preprocessing, you gave it a name at that time.
associated with it.
5. If this parameter is not specified, the default coordinate system is used. The default coordinate system
is initially your model, i.e. the global coordinate system. You may change the default coordinate
system using the 'defaults coordinate_system' command.
6. The REF_MARKER is used to associate the shape defined by the CURVE to the part on which the
REF_MARKER lies. The curve coordinates are therefore specified in the coordinate system of the
REF_MARKER. The floating J marker and REF_MARKER must belong to the same PART.
You may identify a marker by typing its name or by picking it from the screen.
If the marker is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the marker is displayed.
If you created the marker by reading an Adams data set or graphics file, the marker name is the letters
MAR followed by the Adams data set marker ID number. The name of Adams MARKER/101 is
MAR101, for example. If you created the marker during preprocessing, you gave it a name at that
time.
If a marker is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a marker under a different part, for instance, you may need to enter
the model and part names as well. For example, you may specify marker 'pivot' from model 'links',
part 'lower_arm' by entering ".links.lower_arm.pivot". If you type a "?", Adams View will list the
markers available by default.
You must separate multiple marker names by commas.
If the marker is visible in one of your views, you may identify it by picking on it.
You need not separate multiple marker picks by commas.
7. If the point specified is not exactly on the curve, Adams uses a point on the curve nearest to that
specified. By default, DISPLACEMENT_IC is specified in the REF_MARKER marker coordinate
system. If another coordinate system is more convenient, you may supply the IC_REF_MARKER
argument and enter DISPLACEMENT_IC in IC_REF_MARKER marker coordinates. If you
supply DISPLACEMENT_IC values, Adams assembles the system with the I_MARKER at the
specified point on the curve, even if it must override part initial conditions in order to do so. If you
do not supply DISPLACEMENT_IC, Adams assumes the initial contact is at the point on the curve
closest to the initial I_MARKER position. However, it may adjust that contact point to maintain
other part or constraint initial conditions.
8. The velocity_ic parameter specified the speed at which the I_MARKER is initially moving relative to
the curve. The VELOCITY_IC is negative if the I_MARKER is moving towards the start of the
curve, positive if the I_MARKER is moving toward the end of the curve, and zero if the I_MARKER
is stationary on the curve.
If you supply the VELOCITY_IC, 1 gives the I_MARKER the specified initial tangential velocity
along the curve, even if it must override part initial conditions in order to do so. If you do not supply
VELOCITY_IC, Adams assumes the initial tangential velocity is zero, but may adjust that velocity to
The I_MARKER and REF_MARKER must belong to different parts.
9. The POINT_CURVE command defines a point-to-curve constraint, which restricts a fixed point
defined on one part to lie on a curve defined on a second part. This is an instance of a higher pair
constraint.
10. The part containing the I_MARKER is free to roll and slide on the curve that is fixed to a second
part. Lift-off is not allowed, i.e., the I_MARKER must always lie on the curve.
1
constraint 29
constraint create joint convel
11. The curve itself may be planar or spatial, open or closed. The "floating J" marker origin defines the
contact point on the curve; its orientation defines the tangent, normal, and binormal at the contact
point. A POINT_CURVE constraint removes two translational degrees-of-freedom from the system.
Adams restricts the origin of the I_MARKER to always lie on the curve. The I_MARKER may
translate only in one direction relative to the curve, along the instantaneous tangent. The I marker is
free to rotate in all three directions.
12. More than one POINT_CURVE or CURVE_CURVE element may reference the same CURVE
13. The VELOCITY_IC is specified in the reference frame of the part containing the REF_MARKER.
In other words, the VELOCITY_IC is the speed of the I_MARKER specified from the standpoint of
an observer on the part containing the curve. This means that if the I_MARKER is not moving
globally but the curve is, then VELOCITY_IC is still non-zero.
14. The initial conditions arguments, DISPLACEMENT_IC and VELOCITY_IC, impose constraints
that are active only during an initial conditions analysis. Adams does not impose these initial
conditions during subsequent analyses.
For a kinematic analysis, the initial conditions are redundant. Do not use the DISPLACEMENT_IC
or VELOCITY_IC arguments on the POINT_CURVE command for systems with zero degrees of
freedom.
Caution: 1. For the no_displacement_ic and no_velocity parameters, setting these parameters to
true is not the same as setting the value to zero. A zero displacement/velocity is not the
same as "no" displacement/velocity. Therefore, by setting this parameter to true there
is no longer a displacement initial condition for this element.
2. The I_MARKER and REF_MARKER must belong to different parts.
3. Adams aborts the simulation if the contact point moves off the end of an open curve.
The user should make sure the CURVE statement defines the curve over the expected
range of motion.
Tip: The x, y, z values associated with the CURVE are the coordinates of points lying on the
CURVE and are calculated in the coordinate system of the REF_MARKER.

Allows the creation of a constant velocity joint.
Format:
joint_name = a new joint
adams_id = integer
comments = string
i_part_name = an existing body
j_part_name = an existing body
location = location
orientation = location
along_axis_orientation = location
in_plane_orientation = location
i_marker_name = an existing marker
j_marker_name = an existing marker
Example:
constraint create joint convel &
joint_name = JOINT__1 &
adams_id = 2 &
i_part_name = part_1 &
j_part_name = part_2 &
location = 10 , 10 , 5 &
orientation = 1 , 2 , 1 &
relative_to = ground &
j_marker_name = marker_2
constraint 31
Description:

joint_name A New Joint Specifies the name of the new joint. You may use this
name later to refer to this joint. Adams View will not
allow you to have two joints with the same full name, so
you must provide a unique name.
adams_id Adams_id Specifies an integer used to identify this element in the
Adams data file.
modified.
i_part_name An Existing Body Specifies the part that is the first of two parts connected
by this joint. Adams View connects one part at the I
marker to the other at the J marker. These markers are
automatically generated using this method of joint
creation.
j_part_name An Existing Body Specifies the part that is the second of two parts
connected by this joint. Adams View connects one part
at the J marker to the other at the I marker. These
markers are automatically generated using this method
of joint creation.
location Location Specifies the locations to be used to define the position
of a constraint during its creation. The I and J markers
will be automatically created at this location on the
I_PART_NAME and J_PART_NAME respectively.
orientation Orientation Specifies the orientation of the J marker for the
constraint being created using three rotation angles. The
I marker is oriented based on the J marker orientation
and the requirements of the particular constraint being
created. These markers are created automatically.
along_axis_orientation Location Specifies the orientation of a coordinate system (for
example, marker or part) by directing one of the axes.
Adams View will assign an arbitrary rotation about the
axis.
in_plane_orientation Location Specifies the orientation of a coordinate system (for
example, marker or part) by directing one of the axes
and locating one of thecoordinate planes.

relative_to An Existing Model, Specifies the coordinate system that location coordinates
Part Or Marker and orientation angles are with respect to.
i_marker_name An Existing Marker Specifies a marker on the first of two parts connected by
this joint. Adams View connects one part at the I marker
to the other at the J marker.
j_marker_name An Existing Marker Specifies a marker on the second of two parts connected
marker to the other at the J marker.
1. A CONVEL joint is a two-degree-of-freedom joint that superimposes the origin of two markers while
constraining the local z-rotation of the I marker to match the local z-rotation of the J marker.
2. Normally, entity names like the joint name are composed of alphabetic, numeric, or '_' (underscore)
be assigned to it.
constraint 33
constraint create joint cylindrical
5. Adams View will orient the coordinate system by starting from the initial coordinate system and
applying three successive rotations. Depending on the convention you have selected, the rotations
may occur about space-fixed or bodyfixed axes in any meaningful combination of the x, y, and z axes.
By default, you supply Euler (body313, or body-fixed z, x, z) angles. You may change this convention
with the 'DEFAULTS UNITS ORIENTATION_TYPE=' command. For example, selecting
SPACE123 means you will subsequently be supplying space-fixed x, y, and z angles. Adams View
applies your orientation angles starting from the coordinate system you identify with the
RELATIVE_TO parameter. The default for the RELATIVE_TO parameter is the default coordinate
system.
6. For the along_axis_orientation parameter you may enter either one or two locations to direct the axis.
If you enter one location, the axis will point toward the location. If you specify two locations, the axis
will be parallel to, and pointing the same way as, the vector from the first location to the second. Note
that this does not completely dictate the orientation of the coordinate system. Adams View will
osition the coordinate system with an arbitrary rotation about the axis. If you must completely control
the coordinate system orientation, use ORIENTATION or IN_PLANE_ORIENTATION. By
default, you direct the Z axis of the coordinate system.
You may change this convention with the 'DEFAULTS ORIENT_AXIS_AND_PLANE
AXIS_AND_PLANE_SETTING=' command. For example, selecting either X_AXIS_XY_PLANE
or X_AXIS_XZ_PLANE means you will subsequently be directing the X axis. The plane-convention
setting does not affect this parameter. Adams View applies your location coordinates in the coordinate
system you identify with the RELATIVE_TO parameter. The default for the RELATIVE_TO
parameter is the default coordinate system.
7. For the in_plane_orientation parameter you may enter either two or three locations. If you enter two
locations, the axis will point toward the first location and the plane will fall on the second. If you
specify three locations, the axis will be parallel to, and pointing the same way as, the vector from the
first location to the second and the plane will be parallel to the plane defined by the three locations.
By default, you direct the Z axis of the coordinate system and locate the ZX plane. You may use the
'DEFAULTS ORIENT_AXIS_AND_PLANE AXIS_AND_PLANE_SETTING=' command to
change this convention. For example, selecting X_AXIS_XY_PLANE means you will subsequently
be directing the X axis and locating the XY plane. Adams View applies your location coordinates in
the coordinate system you identify with the RELATIVE_TO parameter. The default for the
RELATIVE_TO parameter is the default coordinate system.
8. If the relative_to parameter is not specified, the default coordinate system is used. The default
coordinate system is initially your model, i.e. the global coordinate system. You may change the
default coordinate system using the 'defaults coordinate_system' command.
9. The pitch diameter relates the rotational motion of the pinion to the translational motion of the rack.
When the pinion turns in the positive direction around the z-axis of the I marker, a positive pitch
diameter moves the rack in the positive direction along the z-axis of the J marker and a negative pitch
diameter moves the rack in the negative direction along the z-axis of the J marker.

Allows the creation of a cylindrical joint.
Format:
joint_name = new joint name
adams_id = Geom_id
comments = String
translational_ic = length
no_translational_ic = true
rotational_ic = angle
no_rotational_ic = true
angular_velocity_ic = angular_velocity
no_angular_velocity_ic = true
j_part_name = existing body
Location = location
orientation = orientation
relative_to = existing model, part or marker
j_marker_name = existing marker
Example:
constraint create joint Cylindrical &
joint_name = .model_1.JOINT_2 &
adams_id = 2 &
i_part_name = PART_2 &
j_part_name = PART_3
constraint 35
Description:

joint_name New joint name Specifies the name of the new joint.
adams_id Integer Specifies an integer used to identify this element in the
Adams data file.
modified.
translational_ic Length Specifies the initial translational displacement on a
translational or cylindrical joint.
no_translational_ic True Specifies to "UNSET" the "translational" velocity initial
condition for the specified constraint, if set.
velocity_ic Velocity Specifies the initial translational velocity on a
no_velocity_ic True Specifies to "UNSET" the velocity initial condition, if a
VELOCITY_IC is set via any means.
rotational_ic Real Specifies the initial rotational displacement on a revolute
or cylindrical joint.
no_rotational_ic True Specifies to "UNSET" the "rotational" velocity initial
angular_velocity_ic Angular_velocity Specifies the initial angular velocity on a revolute or
cylindrical joint.
no_angular_velocity_ic True Specifies to "UNSET" the "angular_velocity" initial
i_part_name Existing body Specifies the part that is the first of two parts connected
by this joint.
j_part_name Existing body Specifies the part that is the second of two parts
connected by this joint.
location location Specifies the locations to be used to define the position
of a constraint during its creation.
constraint being created using three rotation angles.
axis.
example, marker or part) by directing one of the axes and
locating one of the coordinate planes.

relative_to Existing model, part Specifies the coordinate system that location coordinates
or marker and orientation angles correspond to.
i_marker_name Existing marker Specifies a marker on the first of the two parts connected
by this joint.
j_marker_name Existing marker Specifies a marker on the second of the two parts
1. Adams View will not allow you to have two joints with the same name, so you must provide a unique
name.
override the default parent. In most cases, when creating an entity, Adams View will provide a default
be assigned to it.
2. When you use the FILE ADAMS_DATA_SET WRITE command, Adams View writes an Adams
data file for your model. Adams requires that each modeling element be identified by a unique integer
Adams file, Adams View will replace the zero with a unique, internally-generated identifier.
Adams View will permanently store this identifier with the element just as if you had entered it
yourself.
3. Adams View measures the translational displacement of the origin of the I marker along the common
z-axis of the I and the J markers with respect to the origin of the J marker.
If you specify TRANSLATIONAL_IC, but not VELOCITY_IC, Adams View will set
VELOCITY_IC to zero.
constraint 37
Joint initial conditions impose constraints that are active only during initial conditions analysis (not
at the time of the initial configuration). Adams does not impose initial conditions during subsequent
analyses.
If you impose initial conditions on the joint that are inconsistent with those on a part in the joint, the
initial conditions take precedence. However, if you impose initial conditions on the joint that are
inconsistent with imparted motions on the joint, the initial conditions, as specified by the motion
generator, take precedence.
4. Adams View measures the translational velocity of the origin of the I marker along the common z-
axis of the I and the J markers with respect to the origin of the J marker.
If you specify VELOCITY_IC, but not TRANSLATIONAL_IC, Adams View will set
TRANSLATIONAL_IC to zero.
analyses.
5. Adams View measures the rotational displacement of the x-axis of the I marker about the common z-
axis of the I and the J markers with respect to the x-axis of the J marker.
If you specify ROTATIONAL_IC, but not ANGULAR_VELOCITY_IC, Adams View will set
ANGULAR_VELOCITY_IC to zero.
analyses.
6. Adams View measures the angular velocity of the x-axis of the I marker about the common z-axis of
the I and the J markers with respect to the x-axis of the J marker.
If you specify ANGULAR_VELOCITY_IC, but not ROTATIONAL_IC, Adams View will set
ROTATIONAL_IC to zero.
analyses.
7. By default, you supply Cartesian (x, y, z) coordinates. You may use the 'defaults units
coordinate_system_type =' command to change this convention. For example, selecting 'cylindrical'
means you will subsequently be supplying r, theta, and z coordinates.
Adams View applies your location coordinates in the coordinate system you identify with the
system.
(See the RELATIVE_TO parameter for this command.)
8. For the parameter “orientation”, the I marker is oriented based on the J marker orientation and the
requirements of the particular constraint being created. These markers are created automatically.
Adams View will orient the coordinate system by starting from the initial coordinate system and
applying three successive rotations.
Depending on the convention you have selected, the rotations may occur about space-fixed or body-
fixed axes in any meaningful combination of the x, y, and z axes.
By default, you supply Euler (body313, or body-fixed z, x, z) angles.
You may change this convention with the 'DEFAULTS UNITS ORIENTATION_TYPE='
command. For example, selecting SPACE123 means you will subsequently be supplying space-fixed
x, y, and z angles.
Adams View applies your orientation angles starting from the coordinate system you identify with the
system.
9. For the “along_axis_orientation” parameter, you may enter either one or two locations to direct the
axis. If you enter one location, the axis will point towards the location. If you specify two locations,
the axis will be parallel to, and pointing the same way as, the vector from the first location to the
second.
Note that this does not completely dictate the orientation of the coordinate system. Adams View will
position the coordinate system with an arbitrary rotation about the axis. If you must completely
control the coordinate system orientation, use ORIENTATION or IN_PLANE_ORIENTATION.
By default, you direct the Z axis of the coordinate system. You may change this convention with the
'DEFAULTS ORIENT_AXIS_AND_PLANE AXIS_AND_PLANE_SETTING=' command. For
example, selecting either X_AXIS_XY_PLANE or X_AXIS_XZ_PLANE means you will
subsequently be directing the X axis. The plane-convention setting does not affect this parameter.
system.
10. For the “in_plane_orientation” parameter, you may enter either two or three locations. If you enter
two locations, the axis will point toward the first location and the plane will fall on the second. If you
constraint 39
constraint create joint fixed
be directing the X axis and locating the XY plane.
system.
11. If the “relative_to” parameter is not specified, the default coordinate system is used. The default
12. A cylindrical joint is a two-degree-of-freedom joint that allows both relative translational and relative
rotational displacement of one part with respect to another. For a cylindrical joint, Adams keeps the
z-axis of the I marker parallel to, and co-directed with, the z-axis of the J marker and confines the
origin of the I marker to the z-axis of the J marker so that the I and the J markers have a common z-
axis. To determine translational motion, Adams measures the movement of the origin of the I marker
along the z-axis and with respect to the J marker. To determine rotational motion, Adams measures
the rotation of the x-axis of the I marker about the common z-axis and with respect to the x-axis of
the J marker.
Caution: For the parameters,

“no_translational_ic”,”no_velocity_ic”,”no_rotational_ic”,”no_angular_velocity_ic”, setting
the values to true is not the same as setting them to zero. A zero velocity is not the same as "no"
velocity. Therefore, by setting this parameter to true, there is no longer a velocity initial
condition for this element.
Tip: 1. You may use the joint_name later to refer to this joint.
2. Adams View connects one part at the J marker to the other at the I marker. These
markers are automatically generated using this method of joint creation.
The I and J markers will be automatically created at this location on the

Allows the creation of a fixed joint.
Format:
Adams_id = integer

comments = string
location = location
Example:
constraint create joint fixed &
Adams_id = 2 &
location = 10 , 10 , 5 &
Description:

joint_name A New Joint Specifies the name of the new joint.
Adams_id Adams_id Specifies an integer used to identify this element in the
Adams data file.
modified.
by this joint.
constraint 41

along_axis_orientation Location Specifies the orientation of a coordinate system (e.g.
marker or part) by directing one of the axes. Adams
View will assign an arbitrary rotation about the axis.
in_plane_orientation Location Specifies the orientation of a coordinate system (e.g.
marker or part) by directing one of the axes and locating
one of the coordinate planes.
relative_to An Existing Model, Specifies the coordinate system that location
Part Or Marker coordinates and orientation angles are with respect to.
this joint. Adams View connects one part at the I
by this joint.
1. A fixed joint essentially locks two parts together. It can be used as a placeholder for another joint or
in conjunction with the ACTIVATE and DACTIVATE commands in Adams to model special
effects.
be assigned to it.
3. When you use the FILE_ADAMS_DATA_SET WRITE command, Adams View writes an Adams
system.
constraint 43
constraint create joint hooke
10. A FIXED joint is a zero-degree-of-freedom joint that superimposes the origins of the I and J markers
while also constraining the X, Y, and Z axes of the I marker to remain parallel to the respective X, Y,
and Z axes of the J marker.
Tip: 1. You may use this name later to refer to this joint. Adams View will not allow you to
have two joints with the same full name, so you must provide a unique name.
2. Adams View connects one part at the I marker to the other at the J marker. These
3. The I and J markers will be automatically created at this location on the
4. The I marker is oriented based on the J marker orientation and the requirements of the
particular constraint being created. These markers are created automatically.

Allows the creation of a hooke joint.
Format:
joint_name = A New Joint
adams_id = Integer
comments = String
i_part_name = An Existing Body
j_part_name = An Existing Body
location = Location
orientation = Location
along_axis_orientation = Location

in_plane_orientation = Location
relative_to = An Existing Model, Part Or Marker
i_marker_name = An Existing Marker
j_marker_name = An Existing Marker
Example:
constraint create joint hooke &
adams_id = 2 &
location = 10 , 10 , 5 &
Description:

joint_name A NEW JOINT Specifies the name of the new joint.
adams_id ADAMS_ID Specifies an integer used to identify this element in the
Adams data file.
comments STRING Specifies comments for the object being created or
modified.
i_part_name AN EXISTING Specifies the part that is the first of two parts connected
BODY by this joint.
j_part_name AN EXISTING Specifies the part that is the second of two parts
BODY connected by this joint.
location LOCATION Specifies the locations to be used to define the position of
a constraint during its creation.
orientation ORIENTATION Specifies the orientation of the J marker for the
constraint 45

along_axis_orientation LOCATION Specifies the orientation of a coordinate system (for
axis.
in_plane_orientation LOCATION Specifies the orientation of a coordinate system (for
relative_to AN EXISTING Specifies the coordinate system that location coordinates
MODEL, PART OR and orientation angles are with respect to.
MARKER
i_marker_name AN EXISTING Specifies a marker on the first of two parts connected by
MARKER this joint.
j_marker_name AN EXISTING Specifies a marker on the second of two parts connected
MARKER by this joint.
1. The UNIVERSAL joint required the Z-axis of the I marker to be perpendicular to the Z-axis of the
J marker, whereas the HOOKE joint requires THE X-axis of the I marker to be perpendicular to the
Y-axis of the J marker, so that they outline the crosspiece of the joint. A valid HOOKE joint may be
properly defined with two coincident markers and can better take advantage of the automatic marker
generation capabilities of Adams View.
it. Note that you can specify the parentage of an entity (e.g. what part "owns" a marker or a geometry
default parent will be assigned by Adams View. If you type in the full name, then you may over ride
The default name that Adams 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:
be assigned to it.
system.
constraint 47
constraint create joint planar
10. A HOOKE joint is a two-degree-of-freedom joint that is that same as the UNIVERSAL joint with
the exception that the marker orientations have been modified.
Tip: 1. You may use the joint_name later to refer to this joint. Adams View will not allow you
to have two joints with the same full name, so you must provide a unique name.

Allows the creation of a planar joint. A planar joint is a three-degree-of-freedom joint that allows the x-y plane
of one part to slide in the x-y plane of another part.
Format:
adams_id = integer
comments = string
location = location
Example:
constraint create joint planar &
adams_id = 2 &
location = 10 , 10 , 5 &
Description:

Adams data file.
modified.
by this joint.
constraint 49

this joint.
by this joint.
1. For a planar joint, Adams keeps the origin of the I marker in the x-y plane of the J marker and keeps
the z axis of the I marker perpendicular to the x-y plane of the J marker.
be assigned to it.
system.
Tip: 1. You may use the joint_name later to refer to the joint. Adams View will not allow you
constraint 51
constraint create joint rackpin

A rack-and-pinion joint is a five-degree-of-freedom joint that constrains the rotational and translational
displacement of the I marker as it rolls along the z-axis of the J marker.
Format:
adams_id = integer
comments = string
location = location
diameter_of_pitch = real number
Example:
constraint create joint rackpin &
adams_id = 2 &
location = 10 , 10 , 5 &
j_marker_name = marker_2 &
diameter_of_pitch = 0.2
Description:

Adams data file.
modified.
creation.
of joint creation.
relative_to An Existing Model, Specifies the coordinate system that location coordinates
Part Or Marker and orientation angles are with respect to.
constraint 53

diameter_of_pitch Length Specifies the pitch diameter of the pinion gear of a rack-
andpinion joint.
1. For a rack-and-pinion joint, the x-axis of the pinion must be parallel to and pointed in the same
direction as the z (translational) axis of the rack. The separation between the two axes should be one-
half the pitch diameter of the pinion. The rack-and-pinion joint itself does not enforce the position
and orientation it requires, but the chain of both parts and joints that connects markers I and J should
enforce the position and orientation. A common approach for enforcing the position and the
orientation is to support the rack with a translational joint and to support the pinion with a revolute
joint.
be assigned to it.
system.
constraint 55
constraint create joint revolute
Tip: The I marker is at the center of the pinion, and the J marker is in the rack.

Allows the creation of a revolute joint.
Format:
Constraint create joint revolute
joint_name = new joint
adams_id = geom._id
comments = string
angular_velocity_ic = angular_vel
friction_enabled = enable_friction
delta_v = real
maximum_deformation = real
mu_dyn_rot = real
mu_stat_rot = real
max_fric_rot = torque
preload_radial = force
preload_axial = force
inner_radius = length
outer_radius = length
location = location
orientation = orienatation
Constraint create joint revolute

Example:
constraint create joint Revolute &
adams_id = 1 &
i_marker_name = .model_1.PART_2.MARKER_5 &
j_marker_name = .model_1.PART_3.MARKER_6
Description:

joint_name New joint Specifies the name of the new joint. You may use
this name later to refer to this joint.
modified.
rotational_ic Real Specifies the initial rotational displacement on a
revolute or cylindrical joint.
no_rotational_ic True Specifies that if a "rotational" velocity initial
condition has been set, to "UNSET" the
"rotational" velocity initial condition for the
specified constraint.
angular_velocity_ic Real Specifies the initial angular velocity on a revolute or
cylindrical joint.
no_angular_velocity_ic True Specifies that if an "angular_velocity" initial
"angular_velocity" initial condition for the
Friction_enabled Yes/No/Preload_only The constant default value will be used if this
parameter is omitted
delta_v Real Real number should be greater than zero.
maximum_deformation Real Real number should be greater than zero.
mu_dyn_rot Real A real number greater than or equal to 0
constraint 57

mu_stat_rot Real A real number greater than or equal to 0
max_fric_rot Torque A real number greater than or equal to 0
preload_radial Force A real number greater than or equal to 0
preload_axial Force A real number greater than or equal to 0
inner_radius Length A real number greater than or equal to 0
outer_radius Length A real number greater than or equal to 0
i_part_name Existing body Specifies the part that is the first of two parts
connected by this joint. Adams View connects one
part at the I marker to the other at the J marker.
part at the J marker to the other at the I marker.
These markers are automatically generated using

this method of joint creation.
Location Location Specifies the locations to be used to define the
position of a constraint during its creation.
Orientation orientation Specifies the orientation of the J marker for the
constraint being created using three rotation
angles.
along_axis_orientation Location Specifies the orientation of a coordinate system
(e.g. marker or part) by directing one of the axes.
in_plane_orientation Location Specifies the orientation of a coordinate system
(e.g. marker or part) by directing one of the axes
and locating one of the coordinate planes.
relative_to Existing model, part or Specifies the coordinate system that location
marker coordinates and orientation angles are with respect
to.
i_marker_name Existing marker Specifies a marker on the first of two parts
j_marker_name Existing marker Specifies a marker on the second of two parts
1. Adams View will not allow you to have two joints with the same full name, so you must provide a
unique name.
be assigned to it.
yourself.
analyses.
initial conditions on the joint have precedence over those on the part. However, if you impose initial
conditions on the joint that are inconsistent with imparted motions on the joint, the initial conditions
as specified by the motion generator have precedence over those here.
If you specify ANGULAR_VELOCITY_IC, but not ROTATIONAL_IC, Adams View ill set
Joint initial conditions impose constraints that are active only uring initial conditions analysis (not at
the time of the initial onfiguration). Adams does not impose initial conditions during subsequent
analyses.
constraint 59
5. The I and J markers will be automatically created at this location on the I_PART_NAME and
J_PART_NAME respectively.
By default, you supply Cartesian (x, y, z) coordinates. You may use the 'defaults units
system. (See the RELATIVE_TO parameter for this command).
6. The I marker is oriented based on the J marker orientation and the requirements of the particular
constraint being created. These markers are created automatically.
x, y, and z angles.
system.
7. Adams View will assign an arbitrary rotation about the axis.
You may enter either one or two locations to direct the axis. If you enter one location, the axis will
point toward the location. If you specify two locations, the axis will be parallel to, and pointing the
same way as, the vector from the first location to the second.
system.
constraint create joint screw
system.
10. A revolute joint is a single-degree-of-freedom joint that allows rotation of one part with respect to
another about a common axis. For a revolute joint, Adams superimposes the origins of the I and J
markers and keeps their z-axes parallel and co-directed. Relative motion occurs about the common z-
axis. Adams measures the angle of the x-axis of the I marker relative to the x-axis of the J marker to
determine the rotational displacement. Adams measures positive rotation according to the right-hand
rule.
Caution: “No_rotational_ic” and “no_angular_velocity_ic” being set to True is not the same as setting
the value to zero. A zero velocity is not the same as "no" velocity. Therefore, by setting this
parameter to true there is no longer a velocity initial condition for this element.
Tip: 1. The I- and J- markers are automatically generated using this method of joint creation.
2. Adams View connects one part at the I marker to the other at the J marker.

Allows the creation of a screw joint. A screw joint is a five-degree-of-freedom joint that constrains the
rotational and translational displacement of the I marker as it spins about the z-axis of the J marker.
Format:
adams_id = integer
comments = string
constraint 61

location = location
pitch = real number
Example:
constraint create joint screw &
joint_name = joint__1 &
adams_id = 2 &
location = 10 , 10 , 5 &
pitch = 0.2
Description:

Adams data file.
modified.
creation.
of joint creation.
axis.
and locating one of the
coordinate planes.
constraint 63

pitch Length Specifies the pitch of the joint.
1. For a screw joint, the z-axis of the I marker and the z-axis of the J marker must always be parallel and
co-directed. Although the screw joint does not enforce this parallelism, the chain of parts and joints
that connects the two markers should. During simulation, the I marker displacement along the J
marker z-axis is a function of the relative angle of the x-axis of the I marker with respect to the x-axis
of the J marker. Adams measures a positive rotation according to the right-hand rule. For every full
rotation, the displacement of the I marker along the z-axis of the J marker is equal to the value of the
screw pitch. If phi is zero, the translational displacement may be zero or any multiple of the pitch.
be assigned to it.
system.
constraint 65
constraint create joint spherical

Allows the creation of a spherical joint.
Format:
adams_id = geom._id
comments = string
location = location
Orientation = orientation
relative_to = existing part, body or marker
Example:
constraint create joint Spherical &
adams_id = 6 &
Description:

joint_name New joint name Specifies the name of the new joint. You may use this name later
to refer to this joint.
adams_id Integer Specifies an integer used to identify this element in the Adams
data file.
comments String Specifies comments for the object being created or modified.
i_part_name Existing body Specifies the part that is the first of two parts connected by this
joint. Adams View connects one part at the I marker to the other
at the J marker. These markers are automatically generated using
this method of joint creation.
j_part_name Existing body Specifies the part that is the second of two parts connected by
this joint. Adams View connects one part at the J marker to the
other at the I marker. These markers are automatically generated
using this method of joint creation.
location Location Specifies the locations to be used to define the position of a
constraint during its creation. The I and J markers will be
automatically created at this location on the I_PART_NAME
and J_PART_NAME respectively.
orientation Orientation Specifies the orientation of the J marker for the constraint being
created using three rotation angles. The I marker is oriented
based on the J marker orientation and the requirements of the
particular constraint being created. These markers are created
automatically.
along_axis_orienta Location Specifies the orientation of a coordinate system (for example,
tion marker or part) by directing one of the axes. Adams View will
assign an arbitrary rotation about the axis.
in_plane_orientati Location Specifies the orientation of a coordinate system (for example,
on marker or part) by directing one of the axes and locating one of
the coordinate planes.
constraint 67

relative_to Existing body, part Specifies the coordinate system that location coordinates and
or marker orientation angles are with respect to.
i_marker_name Existing marker Specifies a marker on the first of two parts connected by this
joint.
Adams View connects one part at the I marker to the other at the
J marker.
j_marker_name Existing marker Specifies a marker on the second of two parts connected by this
joint.
Adams View connects one part at the I marker to the other at the
J marker.
unique name.
be assigned to it.
may occur about space-fixed or body-fixed axes in any meaningful combination of the x, y, and z axes.
x, y, and z angles.
system.
axis. If you enter one location, the axis will point toward the location. If you specify two locations,
second.
system.
system.
constraint 69
constraint create joint translational
8. A spherical joint is a three-degree-of-freedom joint. While permitting all three rotations, a spherical
joint superimposes the I and the J markers.

Allows the creation of a translational joint. A translational joint is a single-degree-of-freedom joint that allows
translational displacement of one part relative to another.
Format:
adams_id = integer
comments = string
velocity_ic = real
delta_v = real
mu_dyn_trans = real
mu_stat_trans = real
max_fric_trans = real
preload_x = real
preload_y = real
height = real
width = real
location = location

Example:
constraint create joint translational &
joint_name = joint__1 &
adams_id = 2 &
translational_ic = 1.2 &
velocity_ic = 1.4 &
friction_enabled = preload_only &
delta_v = 1.4 &
maximum_deformation = 0.02 &
mu_dyn_trans = 0.4 &
mu_stat_trans = 0.8 &
max_fric_trans = 0.15 &
preload_x = 1 &
preload_y = 1.2 &
height = 1.5 &
width = 0.8 &
location = 10 , 10 , 5 &
constraint 71
Description:

Adams data file.
modified.
no_translational_ic True_only Specifies that if a "translational" velocity initial
"translational" velocity initial condition for the
no_velocity_ic True_only Specifies that if a VELOCITY_IC has been set via any
means, to "UNSET" the velocity initial condition.
friction_enabled Enable_friction
delta_v Real
maximum_deformation Real
mu_dyn_trans Real
mu_stat_trans Real
max_fric_trans Real
preload_x Force
preload_y Force
height Real Specify a height for the info window.
width Real Specify a width for the info window.
by this joint.

axis.
i_marker_name An Existing Marker Specifies a marker on the first of two parts connected
by this joint.
j_marker_name An Existing Marker Specifies a marker on the second of two parts
1. For a translational joint, Adams keeps all the axes of the I and the J markers parallel and keeps the
origin of the I marker on the z-axis of the J marker so that the two markers have a common z-axis. To
determine the translational displacement of the I marker with respect to the J marker, Adams
measures the origin of the I marker with respect to the origin of the J marker along their common z-
axis.
be assigned to it.
constraint 73
z-axis of the I and the J markers with respect to the origin of the J marker. If you specify
TRANSLATIONAL_IC, but not VELOCITY_IC, Adams View will set VELOCITY_IC to zero.
analyses. If you impose initial conditions on the joint that are inconsistent with those on a part in the
joint, the initial conditions on the joint have precedence over those on the part. However, if you
impose initial conditions on the joint that are inconsistent with imparted motions on the joint, the
initial conditions as specified by the motion generator have precedence over those here.
6. Setting the no_translational_ic is not the same as setting the value to zero. A zero velocity is not the
same as "no" velocity. Therefore, by setting this parameter to true there is no longer a velocity initial
axis of the I and the J markers with respect to the origin of the J marker. If you specify
VELOCITY_IC, but not TRANSLATIONAL_IC, Adams View will set TRANSLATIONAL_IC to
zero. Joint initial conditions impose constraints that are active only during initial conditions analysis
(not at the time of the initial configuration). Adams does not impose initial conditions during
subsequent analyses. If you impose initial conditions on the joint that are inconsistent with those on
a part in the joint, the initial conditions on the joint have precedence over those n the part. However,
if you impose initial conditions on the joint that are inconsistent with imparted motions on the joint,
the initial conditions as specified by the motion generator have precedence over those here.
8. Setting the no_velocity_ic parameter is not the same as setting the value to zero. A zero velocity is not
the same as "no" velocity. Therefore, by setting this parameter to true there is no longer a velocity
initial condition for this element.
9. The height and the width values should be a real number between 0.0 and 2.0, where 2.0 represents
the height of the Adams View window. Therefore, a value of 1.0 will set the info window to be one
half as high as the Adams View window.
10. By default, you supply Cartesian (x, y, z) coordinates for the location parameter. You may use the
'defaults units coordinate_system_type =' command to change this convention. For example,
selecting 'cylindrical' means you will subsequently be supplying r, theta, and z coordinates. Adams
View applies your location coordinates in the coordinate system you identify with the
system.
coordinate system is initially your model, that is, the global coordinate system. You may change the
constraint 75
constraint create joint universal
Tip: 1. You may use the joint_name later to refer to this joint. Adams View will not allow you

Allows you to create a universal joint.
Format:
:

adams_id = geom_id
comments = string
location = location
relative_to = existing part,body or marker
Example:
constraint create joint universal &
adams_id = 4 &
i_marker_name = MARKER_11 &
j_marker_name = MARKER_12
Description:

joint_name New joint name Specifies the name of the new joint. You may use
modified.
location Location Specifies the locations to be used to define the
orientation orientation Specifies the orientation of the J marker for the
along_axis_orientation location Specifies the orientation of a coordinate system (for
example, marker or part) by directing one of the
axes. Adams View will assign an arbitrary rotation
about the axis.
in_plane_orientation location Specifies the orientation of a coordinate system (for
to.
Adams View connects one part at the I marker to

the other at the J marker.
unique name.
constraint 77
be assigned to it.
SPACE123 means you will subsequently be supplying space-fixed x, y, and z angles.
system.
second.
system.
system.
8. A universal joint is a joint that allows two degrees of rotational freedom.
For a universal joint, Adams superimposes the origins of I and J and keeps their z-axes perpendicular,
so that they outline the crosspiece of the joint. The origins of the I and the J markers are at the center
of the crosspiece.
constraint 79
constraint create motion_generator
Tip: 1. Adams View connects one part at the I marker to the other at the J marker. These
2. Adams View connects one part at the J marker to the other at the I marker. These

Allows the creation of a motion generator in a model.
Format:
motion_name = a new motion
adams_id = geom._id
comments = string
joint_name = existing joint
type_of_freedom = freedom type
axis = motion_axes
function = function
time_derivative = displacement/ velocity/ acceleration
rotational_displacement_ic = angle
rotational_velocity_ic = angular_velocity
Routine = string
Example:
constraint create motion_generator &
motion_name = ROT_MOTION &
joint_name = JOINT_1 &
type_of_freedom = rotational &
function = time &
rotational_velocity_ic = 25.9 &
rotational_displacement_ic = 25.4
The above command will apply a rotational motion to the specified joint which is a function of time. Its
rotational velocity would be 25.9 and its rotational displacement would be 25.4.
Description:

motion_name New Motion Name Specifies the name of the new motion generator. You
may use this name later to refer to this motion
generator.
Adams data file.
modified.
joint_name Existing Joint Specifies the translational, revolute, or cylindrical
constrain motion at, or are otherwise associated with,
specific joints. You use this parameter to identify that
joint.
type_of_freedom Translational/rotational Specifies translational or a rotational motion if you
attach this motion generator to a cylindrical joint.
i_marker_name Existing Marker Specify an existing I marker
j_marker_name Existing Marker Specify an existing J marker
axis X/y/ Z/ B1/ B2/ B3 Allows you to create and modify additional axes on a
plot to effect multiple axis plotting.
function Function Specifies an expression or defines and passes constants
to a user-written subroutine to define the motion.
user_function Real Specifies up to 30 values for Adams to pass to a user-
written subroutine.
Routine String
constraint 81

time_derivative Velocity/displacement/a Specifies that the FUNCTION argument defines the
cceleration motion displacement, velocity, or acceleration.
displacement_ic Length Specifies the initial displacement of the motion, when
the motion is defined in terms of velocity or
acceleration.
velocity_ic Velocity Specifies the initial velocity of the motion, when the
motion is defined in terms of acceleration.
rotational_displacemen Angle Specifies the rotational displacement.
t_ic
rotational_velocity_ic Real Specifies the rotational velocity.
1. Adams View will not allow you to have two motion generators with the same full name, so you must
be assigned to it.
associated with it.
4. The “type_of_freedom” parameter is necessary only when you apply motion to a cylindrical joint. For
a translational joint or a revolute joint, Adams assumes you want translational motion or rotational
motion, respectively.
5. When you create a plot template, Adams View creates two axes by default, one horizontal and one
vertical. These are the plot's primary axes which Adams View uses to perform cursor tracking and to
draw the grid. The plot TEMPLATE commands also operate on the plot's primary axes.
Each axis consists of an axis line, tic marks, numbers and a label. Use the axis ATTRIBUTES to
change visibility and color attributes for the axis entities.
To plot a curve against the new axes, specify the axis names when you create the curve.
You can make the new axes the plot's primary axes by modifying the plot's template and specifying
the desired axes as the PRIMARY_HAXIS and PRIMARY_VAXIS. The grid will then reflect the
divisions of the new axes and cursor tracking will reflect the new axes' coordinate system.
6. The motion must be a function of time only and not a function of the state variables.
Adams View treats this parameter as a series of literal strings. When you write an Adams data set,
Adams View writes these strings, just as you enter them here, after the 'FUNCTION=' argument.
If you want to define the motion with an expression, enclose the expression in quotes and enter it just
as you would in the data set. See the Adams User's Manual for information on writing function
expressions. If your expression is longer than 65 characters, you should break it up into separate
strings so it does not extend past the Adams 80-character line-length limit. Adams View will write
each string on a separate line in the data set.
If you want to define the motion with a user-written subroutine, enter the character string
"USER(r1[,...,r30])", where r1[,...,r30] are the values you want Adams to pass to your user-written
subroutine MOTSUB. If you enter "USER(1.,2.,3.)", for instance, Adams will call your MOTSUB
with values 1, 2, and 3. See the Adams User's Manual for more information on using MOTSUBs.
7. A MOTION_GENERATOR determines a translational or a rotational motion as a function of time.
In Adams you can apply a motion to a translational, to a revolute, or to a cylindrical joint. You can
define the motion with a FUNCTION expression or with a user-written subroutine.
constraint 83
constraint create primitive_joint at_point
You can assign a translational motion at either a translational or a cylindrical joint, and you can assign
a rotational motion at either a revolute or a cylindrical joint. Adams uses the two markers that specify
the joint to define the motion. In other words, Adams controls the rotational or the translational
displacement of the I marker in the joint with respect to the J marker in the joint.
For a translational motion, Adams moves the I marker along the z-axis of the J marker. The J marker
origin represents zero displacement, while the z-axis of the J marker defines the positive direction. For
a rotational motion, Adams rotates the I marker about the z-axis of the J marker. Positive rotations
are positive according to the right-hand rule. The z-axis of the I marker must be collinear with the z-
axis of the J marker at all times. The angle is zero when the x-axis of the I marker is also collinear with
the x-axis of the J marker.

Allows the creation of an at_point joint primitive.
Format:
jprim_name = new primitive joint
adams_id = integer
comments = string
location = location
Example:
constraint create primitive_joint at_point &
jprim_name = JPRIM__1 &
Description:

jprim_name New primitive joint name Specifies the name of the new jprim. You may use
this name later to refer to this jprim.
modified.
about the axis.
axes and locating one of the coordinate planes.
to.
1. Adams View will not allow you to have two jprims with the same full name, so you must provide a
unique name.
constraint 85
be assigned to it.
3. For the location parameter, the I and J markers will be automatically created at this location on the
system.
constraint create primitive_joint inline
5. You may enter either one or two locations to direct the axis. If you enter one location, the axis will
system.
system.
Tip: Adams View connects one part at the I marker to the other at the J marker. These markers are
automatically generated using this method of joint creation.

Allows the creation of an inline joint primitive.
Format:
jprim_name = new primitive joint
adams_id = integer
comments = string
constraint 87

location = location
Example:
constraint create primitive_joint inline &
Description:

adams_id Integer Specifies an integer used to identify this element
in the Adams data file.
modified.
angles.

Adams View will assign an arbitrary rotation
about the axis.
marker coordinates and orientation angles are with
respect to.
unique name.
be assigned to it.
constraint 89
system.
system.
constraint create primitive_joint inplane
system.
8. An inline joint primitive indicates a four-degree-of-freedom joint primitive that allows one
translational and three rotational motions of one part with respect to another.
For an inline primitive, Adams imposes two translational constraints, which confine the translational
motion of the I marker to the line defined by the z-axis of the J marker.

Allows the creation of an inplane joint primitive.
Format:
jprim_name = a new primitive joint name
adams_id = integer
comments = string
location = location
constraint 91
Example:
constraint create primitive_joint inplane &
adams_id = 2&
location = 10 , 10 , 5 &
Description:

jprim_name A NEW Specifies the name of the new jprim.
PRIMITIVE
JOINT
Adams data file.
comments STRING Specifies comments for the object being created or
modified.
i_part_name AN EXISTING Specifies the part that is the first of two parts connected by
BODY this joint.
j_part_name AN EXISTING Specifies the part that is the second of two parts connected
BODY by this joint.
location LOCATION Specifies the locations to be used to define the position of a
constraint during its creation.
orientation ORIENTATION Specifies the orientation of the J marker for the constraint
being created using three rotation angles.
along_axis_orientation LOCATION Specifies the orientation of a coordinate system (for
Adams View will assign an arbitrary rotation about the axis.
in_plane_orientation LOCATION Specifies the orientation of a coordinate system (for

relative_to AN EXISTING Specifies the coordinate system that location coordinates
MODEL, PART and orientation angles are with respect to.
OR MARKER
i_marker_name AN EXISTING Specifies a marker on the first of two parts connected by this
MARKER joint.
j_marker_name AN EXISTING Specifies a marker on the second of two parts connected by
MARKER this joint.
1. For an inplane primitive, Adams imposes one translational constraint, which confines the
translational motion of the I marker to the x-y plane of the J marker.
2. Normally, entity names like the jprim_name are composed of alphabetic, numeric, or '_' (underscore)
be assigned to it.
constraint 93
system.
9. An inplane joint primitive indicates a five-degree-of-freedom joint primitive that allows both
translational and rotational motion of one part with respect to another.
constraint create primitive_joint orientation
Tip: 1. You may use the jprim_name later to refer to this jprim. Adams View will not allow
you to have two jprims with the same full name, so you must provide a unique name.

Allows the creation of an orientation joint primitive.
Format:
adams_id = integer
comments = string
location = location
Example:
constraint create primitive_joint orientation &
adams_id = 2 &
constraint 95
constraint create primitive_joint orientation &

location = 10 , 10 , 5 &
Description:

jprim_name A New Primative Specifies the name of the new jprim.
Joint
Adams data file.
modified.
by this joint.
axis.
and locating one of thecoordinate planes.
by this joint.
1. For an orientation primitive, Adams imposes three rotational constraints to keep the orientation of
the I marker identical to the orientation of the J marker.
be assigned to it.
system.
constraint 97
constraint create primitive_joint parallel_axis
9. An orientation joint primitive indicates a three-degree-of-freedom joint primitive that allows only
translational motion of one part with respect to another.

Allows creation of a parallel axis joint primitive.
Format:
adams_id = integer
comments = string
location = location
Example:
constraint create primitive_joint parallel_axis &
adams_id = 2 &
location = 10 , 10 , 5 &
orientation = 1 , 2 , 1
constraint 99
Description:

jprim_name A New Primative Specifies the name of the new jprim.
Joint
Adams data file.
modified.
by this joint.
axis.
by this joint.
1. For a parallel axis primitive, Adams imposes two rotational constraints so that the z-axis of the I
marker stays parallel to the z-axis of the J marker. This primitive permits relative rotation about the
common z-axis of I and J and permits all relative displacements.
be assigned to it.
system.
constraint 101
constraint create primitive_joint perpendicular

9. A parallel joint primitive is a four-degree-of-freedom joint primitive that allows both translational and
rotational motion of one part with respect to another.

Allows the creation of a perpendicular joint primitive.
Format:
Constraint create primitive_joint perpendicular
jprim_name = new primitive joint name
adams_id = geom_id
comments = string
Constraint create primitive_joint perpendicular

j_part_name = Existing body
location = location
relative_to = existing part, body or marker
i_marker_name = existing marker name
j_marker_name = existing marker name
Example:
constraint create primitive_joint perpendicular &
Description:

Jprim_name New primitive joint name Specifies the name of the new jprim. You may use
modified.
constraint 103

angles. The I marker is oriented based on the J
marker orientation and the requirements of the
particular constraint being created. These markers
are created automatically.

about the axis.
(for example, marker or part) by directing one of
the axes and locating one of the coordinate planes.
relative_to Existing part, body or Specifies the coordinate system that location
to.
i_marker_name Existing marker name Specifies a marker on the first of two parts

j_marker_name Existing marker name Specifies a marker on the second of two parts

unique name.
be assigned to it.
yourself.
system.
second.
constraint 105
constraint create primitive_joint point _point
system.
system.
8. A perpendicular joint primitive is a five-degree-of-freedom joint primitive that allows both
For a perpendicular primitive, Adams imposes a single rotational constraint on the I and the J markers
so that their z-axes remain perpendicular. This allows relative rotations about either z-axis, but does
not allow any relative rotation in the direction perpendicular to both z-axes.
Tip: 1. Adams View connects one part at the I marker to the other at the J marker. These

Allows the creation of an point_point joint primitive.
Format:
constraint create primitive_joint point_point
prim_name = new primitive joint
adams_id = integer
comments = string
location = location
offset = length
Example:
constraint create primitive_joint point_point &
j_marker_name = MARKER_12 &
offset = 2
constraint 107
Description:

modified.
about the axis.
axes and locating one of the coordinate planes.
to.
offset Length Specifies the prescribed distance between the two
points.
unique name.
geometry element) when you CREATE it by changing the name. If you enter just the entity name, then
"...._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.
2. When you use the FILE ADAMS_DATA_SET WRITE command, Adams View writes an Adams data
fixed axes in any meaningful combination of the x, y, and z axes. By default, you supply Euler
(body313, or body-fixed z, x, z) angles. You may change this convention with the 'DEFAULTS UNITS
ORIENTATION_TYPE=' command. For example, selecting SPACE123 means you will subsequently
be supplying space-fixed x, y, and z angles.
system.
constraint 109
constraint create user_defined
example, selecting either X_AXIS_XY_PLANE or X_AXIS_XZ_PLANE means you will subsequently
be directing the X axis. The plane-convention setting does not affect this parameter. Adams View
applies your location coordinates in the coordinate system you identify with the RELATIVE_TO
parameter. The default for the RELATIVE_TO parameter is the default coordinate system.
'DEFAULTS ORIENT_AXIS_AND_PLANE AXIS_AND_PLANE_SETTING=' command to change
this convention. For example, selecting X_AXIS_XY_PLANE means you will subsequently be
directing the X axis and locating the XY plane.
system.

Allows the user to create a USER DEFINED constraint.
Format:
user_constraint_name = new user constraint
adams_id = geom._id
comments = string
user_function = function
constraint delete
Description:

user_constraint_name New user defined Allows the user to create a USER DEFINED constraint.
constraint
Adams data file.
modified.
user_function Real Specifies up to 30 values for Adams to pass to a user-written
subroutine.
yourself.
2. A user-defined constraint describes a system constraint as a function of time and as many as thirty
variables. Each of these variables must be the displacement or the velocity of a part. For any part at
any point in time, six displacements define its position, and six velocities define its velocity. The six
displacements are the x, y, and z translations and the three Euler angle rotations. The six velocities are
the x, y, and z translational velocities and the time derivatives of the three Euler angles. Adams
measures all of these displacements and velocities at the origin of the principal axes with respect to the
global coordinate system. A USER DEFINED constraint is only used when a constraint is needed
that is not definable by any of the other constraint types.
constraint delete
Allows you to delete an existing constraint.
Format:
constraint delete
constraint 111
constraint modify complex_joint coupler
Example:
constraint delete &
constraint_name = joint_1
Description:

Constraint_name Existing constraint Specifies the constraint to delete.
menu entry 'UNDO'.
• You may identify a constraint by typing its name or by picking it from the screen.
name of Adams JOINT/101 is JOI101, for example. If you created the constraint during
you must enter its full name. To identify a constraint under a different model, for instance, you
may need to enter the model name as well. For example, you may specify constraint 'servo_motor'
from model 'test' by entering ".test.servo_motor". If you type a "?", Adams View will list the
constraints available by default.
2. You must enter the name of the constraint you wish to delete by either picking it from the screen or
You may reverse this deletion at a later time with an UNDO command.

Allows the modification of an existing coupler.
Format:
coupler_name = an existing coupler
new_coupler_name = a new coupler
adams_id = adams_id
comments = string
type_of_freedom = coupler_freedom
motion_multipliers = real
first_angular_scale_factor = angle
first_scale_factor = real
second_angular_scale_factor = angle
second_scale_factor = real
third_angular_scale_factor = angle
third_scale_factor = real
Example:
constraint modify complex_joint coupler &
coupler_name = coupler__1 &
new_coupler_name = coupler__2 &
adams_id = 1 &
joint_name = JOINT_1 , JOINT_1 &
motion_multipliers = 0.1 , 0.2 &
type_of_freedom = rot_rot_rot
Description:

coupler_name An Existing Coupler Specifies the coupler to modify.
new_coupler_name A New Coupler Specifies the name of the new coupler.
adams_id Adams_id Specifies an integer used to identify this element
constraint 113

modified.
type_of_freedom Coupler_freedom Specifies whether cylindrical joints transfer
translational or rotational motion.
motion_multipliers Real Specifies the relative motion of the joints you
identify with JOINTS
first_angular_scale_factor Angle Specifies the angular motion of the first joint you
identify with JOINT_NAME relative to the
with JOINT_NAME.
first_scale_factor Real Specifies the non-angular motion of the first joint
with JOINT_NAME.
second_angular_scale_factor Angle Specifies the angular motion of the second joint
motion of the first and third joints you identify
with JOINT_NAME
second_scale_factor Real Specifies the non-angular motion of the second
joint you identify with JOINT_NAME relative to
the motion of the first and third joints you
identify with JOINT_NAME.
third_angular_scale_factor Angle Specifies the angular motion of the third joint you
identify with JOINT_NAME relative to the
motion of the first and second joints you identify
with JOINT_NAME.
third_scale_factor Real Specifies the non-angular motion of the third
joint you identify with JOINT_NAME relative to
the motion of the first and second joints you
identify with JOINT_NAME.
userwritten subroutine.
1. A coupler creates the coupling of the translational and/or the rotational motion of two or three joints.
With this constraint, you can deliver or relate motion from one area of a mechanism to another.
Components whose behavior you might approximate with this statement include combinations of
hydraulic generators, motors, and pistons and include flexible, rotational transmission cables.
2. You may identify a coupler by typing its name or by picking it from the screen.
If the coupler is not visible on the screen, you must type the name. You may also find it convenient
to type the name even if the coupler is displayed. If you created the coupler by reading an Adams data
set, the coupler name is the letters COU followed by the Adams data set coupler ID number. The
name of Adams COUPLER/101 is COU101, for example. If you created the coupler during
preprocessing, you gave it a name at that time. If a coupler is available by default, you may identify it
by entering its name only. If it is not, you must enter its full name. To identify a coupler under a
different model, for instance, you may need to enter the model name as well. For example, you may
specify coupler 'differential' from model 'test' by entering ".test.differential". You must separate
multiple coupler names by commas.
3. Normally, entity names like the coupler name are composed of alphabetic, numeric, or '_'
(underscore) characters, and start with an alphabetic or '_' character. They may be any length. By
enclosing the name in double quotes, you may use other printable characters, or start the name with
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 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 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, or course, delete this name and use your own. The form of a full name is:
be assigned to it.
is the letters JOI followed by the Adams data set joint ID number. The name of Adams JOINT/101
is JOI101, for example. If you created the joint during preprocessing, you gave it a name at that time.
constraint 115
7. AdamsAdams assumes that translational joints transfer translational motion and that revolute joints
transfer rotational motion. A cylindrical joint permits both translational and rotational motion,
however. If your coupler includes cylindrical joints, you must use this parameter to indicate which
motion is transferred at each joint.
8. Adams uses the values in the SCALES argument in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
or the rotational displacements of the joint I markers with respect to their J
markers. Suppose you are coupling two joints, and SCALES=1,-2. The equation that relates the two
joints is
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
displacements have the same sign. If you specify two joints in the JOINTS argument, you must
specify r2. If you specify only one value, Adams assumes it is r2 and uses the default value of 1 for r1.
9. Adams uses the first_angular_scale_factor (r1) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
10. Adams uses the first_scale_factor (r1) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
11. Adams uses the second_angular scale_factor (r2) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
12. Adams uses the second_scale_factor (r2) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
q1 + (-2 * q2) = 0, or
q1 = 2 * q2.
13. Adams uses the third_angular_scale_factor (r3) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
14. Adams uses the third_scale_factor (r3) in the following equation:
(r1 * q1) + (r2 * q2) + (r3 * q3) = 0,
constraint 117
constraint modify complex_joint gear
Tip: 1. If you type a "?", Adams View will list the couplers available by default.
2. If the coupler is visible in one of your views, you may identify it by picking on any of
the graphics associated with it.
3. You need not separate multiple coupler picks by commas.
4. You use the coupler_name parameter to identify the existing coupler to affect with this
command.
5. You may use the new_coupler_name later to refer to this coupler. Adams View will not
allow you to have two couplers with the same full name, so you must provide a unique
name.
6. Some entities constrain motion at, or are otherwise associated with, specific joints. You
use this parameter to identify that joint.
7. See the Adams User's Manual for information on writing user-written subroutines.

Allows the modification of an existing gear pair.
Format:
gear_name = an existing joint
new_gear_name = a new joint
adams_id = integer
comments = string
common_velocity_marker = an existing marker
Example:
constraint modify complex_joint gear &
gear_name = GEAR__1 &
new_gear_name = GEAR__2 &
adams_id = 2 &
common_velocity_marker = marker_1
Description:

gear_name An existing gear Specifies the gear to modify.
new_gear_name A new gear Specifies the name of the new gear. .
adams_id ADAMS_ID Specifies an integer used to identify this element in
modified.
common_velocity_marker An Existing Marker Specifies the marker that designates the point of
contact and determines the ratio of the two gears.
1. The gear element uses the location of the common velocity marker to determine the point of contact
of the two gear pitch circles. The direction of the z-axis of the common velocity marker indicates the
direction of the common velocity of points on the gear teeth in contact. This is also the direction in
which gear tooth forces act. The location of the common velocity marker is constant with respect to
the carrier part.
2. You may identify a gear pair by typing its name or by picking it from the screen.
If the gear pair is not visible on the screen, you must type the name. You may also find it convenient
to type the name even if the gear is displayed. If you created the gear by reading an Adams data set,
the gear name is the letters GEA followed by the Adams data set gear ID number. The name of Adams
GEAR/101 is GEA101, for example. If you created the gear during preprocessing, you gave it a name
at that time. If a gear is available by default, you may identify it by entering its name only. If it is not,
you must enter its full name. To identify a gear under another model, for instance, you may need to
enter the model name as well. For example, you may specify gear 'spur1' from model 'train' by
entering ".train.spur1". You must separate multiple gear names by commas. If the gear is visible in
one of your views, you may identify it by picking on any of the graphics associated with it. You need
not separate multiple gear picks by commas.
3. Normally, entity names like the gear name are composed of alphabetic, numeric, or '_' (underscore)
name. The defaultname that Adams 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:
constraint 119
be assigned to it.
".links.lower_pivot". If you type a "?", Adams View will list the joints available by default. You must
separate multiple joint names by commas. If the joint is visible in one of your views, you may identify
it by picking on any of the graphics associated with it. You need not separate multiple joint picks by
commas.
7. You define the constant-velocity (CV) marker on the carrier part to which the J markers of the joints
belong. The z-axis of this marker must point in the direction of common velocity at the point of
contact. The direction of common velocity is tangent to both pitch circles and would be normal to
the tooth surfaces of the gears if the pressure angle was zero. (Adams always assumes a pressure angle
of zero.)
The CV marker has constant position and orientation in the carrier LPRF and does not change when
the direction of power flow through the gear changes.
8. A gear pair relates the motion of three parts and two joints. The three parts are the two gear parts and
a third part, the carrier, to which the gears are attached by the two joints. The joints must be
translational, revolute, or cylindrical. Different combinations of joint types and orientations allow
you to model spur, helical, planetary, bevel, and rack-and-pinion gear pairs.
constraint modify general_constraint
Tip: 1. If you type a "?", Adams View will list the gears available by default.
2. You use the joint_name parameter to identify the existing gear to affect with this
command.
3. You may use the new_gear_name later to refer to this gear. Adams View will not allow
you to have two gears with the same full name, so you must provide a unique name.
4. Some entities constraint motion at, or are otherwise associated with, specific joints.
You use this parameter to identify that joint.
5. The common_velocity_marker also determines the direction of the reaction forces
developed by the joints in the gear pair.

The GCON statement introduces a constraint equation that must be satisfied by Adams Solver (C++) during
the simulation. This allows you to specify both holonomic and non-holonomic constraints.
Format:
general_constraint_name = existing gen_constraint name
new_general_constraint_name = new gen_constraint name
adams_id = geom. _id
comments = string,
function = function
Example:
constraint modify general_constraint &
general_constraint_name = GCON_1 &
new_general_constraint_name = MY_GCON &
function = time
constraint 121
Description:

general_constraint_name Existing GCON name Specify a name of the GCON to be modified
New_general_constraint_n New GCON name Specify the new name for the GCON
ame
adams_id integer Specifies an integer used to identify this element
modified.
I_marker_name Existing marker Specify an existing marker name.
function Function Specifies an expression or defines and passes
constants to a user-written subroutine to define
the motion.
associated with it.

3. While the JOINT statement describes a physically recognizable combination of constraints that are
used to connect bodies together, the GCON statement enables you to define an arbitrary constraint
specific to a particular model. The GCON statement is more general and can be used to equivalently
define the existent JOINT elements. Therefore, the spherical joint
JOINT/11, SPHERICAL, I=1,J=3
could be equivalently replaced by the following set of three GCONs:
GCON/111, I=2, FUNC=DX(2,3)
GCON/112, I=2, FUNC=DY(2,3)
GCON/113, I=2, FUNC=DZ(2,3)
The GCON statement allows you to define both holonomic and non-holonomic constraints.
Holonomic constraints only depend on position measures, like GCON/111 through GCON/113
above. A constraint is non-holonomic if (a) its expression exp1 contains velocity measures, and (b)
there is no expression exp2 that is the time integral of exp1. An example of a non-holonomic constraint
is a roll without slip condition
GCON/34, FUNC=VX(2) - WZ(2)*DY(2)
The GCON statement introduces a constraint to Adams Solver (C++) that is guaranteed to be
handled correctly as long as the FUNCTION is in Pfaffian form. In this context, note that any
holonomic expression is automatically in Pfaffian form. In the case of non-holonomic constraints, a
Pfaffian constraint requires that the FUNCTION is limited to expressions that are linear in velocity
quantities. In other words, if there are velocity quantities in the definition of the FUNCTION (as is
the case in the previous GCON), a partial derivative of the FUNCTION with respect to any velocity
quantity present in its definition should lead to an expression that does not depend on velocity
∂FUNC
quantities. The previous GCON is therefore in Pfaffian form, since -------------------- = 1
∂FUNC
∂FUNC
and -------------------- = – DX ( 2 ) which makes the FUNC linear in velocity quantities.
∂WZ ( 2 )
Another example of a Pfaffian non-holonomic constraint is the perpendicularity condition
GCON/25, FU=VX(2,3)*DX(2,1)+ VY(2,3)*DY(2,1)+ VZ(2,3)*DZ(2,1)
that indicates that the velocity V(2,3) is orthogonal to the distance vector between markers I=2 and
J=1.
An example of a non-Pfaffian GCON is
GCON/25,FU=VX(2,3)*VX(2,3)*DX(2,1)+VY(2,3)*DY(2,1)+
VZ(2,3)*DZ(2,1)
∂FU
For this example, ------------------------ = 2 ⋅ VX ( 2, 3 ) ⋅ DX ( 2, 1 ) which is an expression that depends on the
∂VX ( 2, 3 )
velocity measure VX(2,3).
The FUNCTION expression exp can reference variables defined in the .adm file through the
VARVAL construct. It should be stressed again that correct handling of the GCON requires that the
expression defining the VARIABLE only depends on time, and position and velocity measures; in
other words, the Pfaffian character of the GCON is not undermined by the presence of the VARVAL.
constraint 123
Cautions:
1. Objects of type General_Constraint are not compatible with Adams Solver (FORTRAN).
2. The topology of the model has changed so .model_1.GCON__1 is no longer connected in a way that
is compatible with Adams Solver (FORTRAN).
3. An attribute of .model_1.GCON__1 is no longer compatible with Adams Solver (FORTRAN).
If you intend to use Adams Solver (FORTRAN), you must change your model to eliminate the
incompatibility. For more information, see the online help for the object listed.
If you do not want to use Adams Solver (FORTRAN), then be sure that you set your preferences so
Adams Solver (C++) is the default as follows:
a. From the Settings menu, point to Solver and then select either Solver Executable or Preferences,
depending on the product you are using.
b. To learn more, press F1 in the dialog box.
• Correct handling of a GCON element assumes a FUNCTION defined in Pfaffian form.
• Kinematic models are incompatible with velocity constraints. If a model is rendered kinematic by
displacement constraints, any additional velocity constraints will be either redundant or
conflicting. In either case, version 2003 of Adams Solver (C++) is incapable of analyzing the
model as explained below:
Currently, there is no redundancy check for user constraints defined at the velocity level.
Therefore, you can impose constraints that are not redundant at the position level, but lead to a
set of redundant constraints when their time derivative is considered with other velocity level
constraints during the velocity Initial Conditions (IC) analysis. Consider the situation when two
constraints are defined as GCON/1, FU=DX(1,2), and GCON/2, FU=VX(1,2). Because the
redundant constraint analysis only includes position level constraints, Adams Solver (C++) will
not identify that a velocity-level constraint (GCON/2) induces a redundant constraint during the
velocity computation. As a result, a model that contains these two user constraints will fail during
the velocity analysis with a singular Jacobian error.
• GCON is a new modeling element only available in the Adams Solver (C++). Currently there is
no support for defining GCON through Adams View, so you need to edit the .adm file to add
user-defined constraints. Adams View correctly imports the edited .adm file, and the internal
Adams Solver (C++) from within Adams View correctly handles the simulation of the model.
• If you use GCON to constrain the values of DIFF, LSE, and TFSISO elements, note that they
will not contribute degrees of freedom that are considered removed by a GCON element. The
GCON statement functions properly for Pfaffian expressions depending on position and velocity
measures and time, or as mentioned earlier, on VARVALs measures for VARIABLEs that only
depend on position and velocity measures and time.
• Consequently, a model that contains velocity constraints can only be simulated using the dynamic
solver.
constraint modify higher_pair_contact curve_curve
• For a position-level GCON, the FUNCTION must be at least three times differentiable. If the
GCON introduces a velocity-level constraint, then the FUNCTION should be at least twice
differentiable. This requirement ensures that internally Adams Solver (C++) can take the
necessary derivatives to perform certain types of analyses such as Acceleration/Force
reconciliation, dynamic analysis, and so on. Note that if the expression provided for GCON is
not continuously differentiable for the required number of times, the integrator will either fail, or
have a difficult time finding the numerical solution.
• The ability of the Adams Solver (C++) to handle function expressions to provide the necessary
derivatives required by the GCON does not extend to user subroutines. Consequently, a
VARIABLE can only be referenced in a GCON provided it is defined using function expressions,
rather than a VARSUB subroutine.
• Use the RESULTS/XRF statement in order to get the reaction force on marker I reported in the
results file. This is the only output format currently able to handle GCON output.
Tips:
1. There is no dedicated function that returns the reaction force induced by a user constraint on a
marker. You can invoke an existing function such as FX(I[; J][;K]) for this purpose. Note that FX(I[;
J][;K]) reports the force that acts on the I marker as a result of both constraint and external forces
applied to this marker. To only obtain the contribution of the the GCON, the markers that appear
in FX(I[; J][;K]) should be exclusively used to define the GCON, and no other elements such as
applied forces, joints, or motions should refer them.

Allows you to modify a curve_curve constraint.
Format:
curve_curve_name = existing ccurve
new curve_curve_name = new cccurve name
adams_id = geom._id
comments = string
i_curve_name = existing acurve
J_curve_name = existing acurve
I_ref_marker_name = existing marker
J_ref_marker_name = existing marker
I_displacement_ic = length
no_i_displacement_ic = true
j_displacement_ic = length
constraint 125

no_j_displacement_ic = true
i_ velocity_ic = velocity
no_i_velocity_ic = true
j_velocity_ic = velocity
no_j_velocity_ic = true
i_ ic_ref_marker_name = existing marker,
ji_ ic_ref_marker_name = existing marker
Description:

curve_curve_name New ccurve Specifies the name of an existing curve_curve
New_curve_curve_name New ccurve name Specifies the name of the new curve_curve. You
may use this name later to refer to this
curve_curve.
the Adams data File.
modified.
i_curve_name Existing Acurve name Specifies the name of a CURVE from which
Adams constructs the first Curve
J_curve_name Existing acurve Specifies the name of a CURVE from which
Adams constructs the second curve.
I_ref_marker_name Existing marker Specifies the name of a fixed MARKER on the
part containing I_CURVE.
J_ref_marker_name Existing marker Specifies the name of a fixed MARKER on the
part containing J_CURVE.
I_floating_marker_name Existing marker Specify an existing floating marker.
J_floating_marker_name Existing marker Specify an existing floating marker.
I_displacement_ic Length Specifies the initial point of contact on the first
curve.
J_displacement_ic Length Specifies the initial point of contact on the second
curve.
No_i_displacement_ic True Specifies that if an I_DISPLACEMENT_IC has

No_j_displacement_ic True Specifies that if an J_DISPLACEMENT_IC has
I_velocity_ic Velocity Specifies the initial velocity of the contact point
along I_CURVE.
J_velocity_ic Velocity Specifies the initial velocity of the contact point
along J_CURVE.
No_i_velocity_ic True Specifies that if an I_VELOCITY_IC has been set
condition.
No_j_velocity_ic True Specifies that if an J_VELOCITY_IC has been set
condition.
I_ic_ref_marker_name An existing marker Specifies the name of a fixed MARKER defining
the coordinate system in which the values for
I_DISPLACEMENT_IC are defined. The
I_IC_REF_MARKER must be on the same part
as the I_REF_MARKER.
J_ic_ref_marker_name An existing marker Specifies the name of a fixed MARKER defining
the co ordinate system in which the values for
J_DISPLACEMENT_IC are defined. The
J_IC_REF_MARKER must be on the same part
as the J_REF_MARKER.
constraint 127
be assigned to it.
3. The I_REFERENCE_MARKER marker specifies the coordinate system in which the x, y, z
coordinates of I_CURVE are specified. The curve is attached rigidly to the part specified in the
I_PART_NAME parameter and containing the I_REFERENCE_MARKER marker. The z
component of the CURVE must be zero. As a result, the curve will lie in the x-y plane of the
I_REFERENCE_MARKER marker.
4. The J_REFERENCE_MARKER specifies the coordinate system in which the x, y, z coordinates of
J_CURVE are specified. The curve is attached rigidly to the part specified in the J_PART_NAME
parameter and containing the J_REFERENCE_MARKER. The z component of the CURVE must
be zero. As a result, the curve will lie in the x-y plane of the J_REFERENCE_MARKER.
5. The I_REF_MARKER marker identifies the coordinate system in which the coordinates of ICURVE
are specified. Adams constructs the I_CURVE in the I_REF_MARKER marker coordinate system.
Adams View will automatically create the I "floating" marker. The I "floating marker" and
I_REF_MARKER markers must lie on the same part.
6. The J_REF_MARKER marker identifies the coordinate system that the coordinates of J_CURVE are
specified. Adams constructs the J_CURVE in the J_REF_MARKER coordinate system. The J
"floating" and J_REF_MARKER markers must lie on the same part.
7. For the i_displacement_ic parameter, if the point specified is not exactly on the curve, Adams will use
a point on the curve nearest to that specified. By default, the contact point is specified in the
I_REF_MARKER coordinate system. If another coordinate system is more convenient, you may
supply the I_IC_REF_MARKER argument and enter I_DISPLACEMENT_IC in
I_IC_REF_MARKER coordinates.
If you supply I_DISPLACEMENT_IC, Adams assembles the system with the contact at the specified
supply I_DISPLACEMENT_IC, Adams assumes the initial contact is at the point on the first curve
closest to J_CURVE in the input configuration. In this case, Adams may adjust that contact point to
8. For the j_displacement_ic parameter, if the point specified is not exactly on the curve, Adams uses a
point on the curve nearest to that specified. By default, the contact point is specified in the
J_REF_MARKER coordinate system. If another coordinate system is more convenient, you may
supply the J_IC_REF_MARKER and enter J_DISPLACEMENT_IC in J_IC_REF_MARKER
coordinates.
If you supply J_DISPLACEMENT_IC, Adams assembles the system with the contact at the specified
supply J_DISPLACEMENT_IC, Adams assumes the initial contact is at a point on the second curve
closest to ICURVE in the input configuration. In this case, Adams may adjust that contact point to
9. The i_velocity_ic is the speed at which the contact point is initially moving relative to the curve.
I_VELOCITY_IC is negative if the contact point is moving towards the start of the curve, positive if
the curve.
If you supply I_VELOCITY_IC, Adams gives the contact point the specified initial velocity along
the first curve, even if it must override part initial conditions in order to do so. If you do not supply
I_VELOCITY_IC, Adams assumes the initial velocity is zero, but may adjust that velocity to
10. The j_velocity_ic is the speed at which the contact point is initially moving relative to the curve.
J_VELOCITY_IC is negative if the contact point is moving towards the start of the curve, positive if
the curve.
If you supply J_VELOCITY_IC, Adams gives the contact point the specified initial velocity along
the second curve, even if it must override part initial conditions in order to do so. If you do not supply
J_VELOCITY_IC, Adams assumes the initial velocity is zero, but may adjust that velocity to
11. The CURVE_CURVE defines a curve-curve constraint, which restricts a planar curve on one part to
be in contact with, and tangent to, a planar curve on a second part. The curves must lie in parallel
planes.
Adams constructs the first curve from the I_CURVE curve and the I_REF_MARKER, the second
curve from the J_CURVE value and the J_REF_MARKER. In both cases, the CURVE command
(I_CURVE or J_CURVE) defines x and y coordinates along the curve as a function of the
independent parameter (u). The z coordinates of the curves must be zero. The reference marker
(I_REF_MARKER or J_REF_MARKER) defines the part the constraining curve is attached to and
the coordinate system in which Adams applies the coordinates from the CURVE statement. Both
I_CURVE and J_CURVE may be open or closed, defined analytically or as a set of discrete data
points.
The CURVE_CURVE constraint removes three degrees-of-freedom from the system. Adams restricts
the motion of the parts such that the curves are always in contact and the curves are tangent at the
contact point. Although Adams requires that the curves lie in parallel planes, the CURVE_CURVE
command does not enforce this. You must build the model in such a way that the curves are held in
constraint 129
parallel planes, which will remove another three degrees of freedom. Assuming the curves are held in
parallel planes, a CURVE_CURVE leaves two relative degrees of freedom between the curves. The
first curve may slide or roll on the second, but may not move perpendicular to the curve tangents at
the contact.
Internally, Adams actually generates five constraint equations, but also adds two new system variables
and equations for a net decrease of one degree-of-freedom. The added system variables are the two
curve parameters at the contact points on the curves. Two of the constraints restrict the x and y
coordinates at the contact point on the first curve to match the x and y coordinates at the contact
point on the second curve. The third constraint restricts the tangent at the contact point on the first
curve to be parallel to the tangent at the contact point on the second curve.
More than one POINT_CURVE or CURVE_CURVE statement may reference the same CURVE
The I_VELOCITY_IC and J_VELOCITY_IC are specified in the reference frame of the part
containing the I_REF_MARKER or J_REF_MARKER marker, respectively. In other words, the
I_VELOCITY_IC is the speed of the contact point specified from the standpoint of an observer on
the part containing the first curve. This means if the contact point is not moving globally, but the
first curve is, then I_VELOCITY_IC is still non-zero.
Adams detects a fatal user error if the contact point moves off the end of an open curve. You should
make sure the CURVE statement defines the curve over the expected range of motion. The initial
conditions arguments, I_DISPLACEMENT_IC, J_DISPLACEMENT_IC, I_VELOCITY_IC and
J_VELOCITY_IC, impose constraints that are active only during an initial conditions analysis.
Adams does not impose these initial conditions during subsequent analyses.
For a kinematic analysis, the initial conditions are redundant. Do not use the
I_DISPLACEMENT_IC, J_DISPLACEMENT_IC, I_VELOCITY_IC or J_VELOCITY_IC
arguments on the CURVE_CURVE statements for systems with zero degrees of freedom.
Adams requires that there be a unique contact point in the vicinity of the I floating and J floating
markers during simulation. If this condition is violated, Adams may be unable to find the correct
contact point or may even jump from one contact point to the next.
One way to ensure that contact points are unique is to specify curve shapes that are convex. Note that
for a convex curve, any line segment connecting two points on the curve lie in the domain of the
curve. The same is not true for non-convex curves.
Cautions:
1. For the no_i_displacement_ic,no_j_displacement_ic,no_i_velocity and no_j_velocity parameters,
setting these parameters to true is not the same as setting the value to zero. A zero
displacement/velocity is not the same as "no" displacement/velocity. Therefore, by setting this
parameter to true there is no longer a displacement/velocity initial condition for this element.
constraint modify higher_pair_contact point_curve

Allows you to modify a point_curve.
Format:
point_curve_name = existing pcurve
new_point_curve_name = new name for pcurve
adams_id = geom._id
comments = string
curve_name = existing acurve
i_marker_name = An existing marker
j_floating_marker_name = An existing fmarker
no_displacement_ic = true
ic_ref_marker_name = existing marker
Description:

point_curve_name Existing Pcurve Specifies the name of an existing point_curve.
New_point_curve_name New pcurve name Specifies the name of the new point_curve. You
point_curve.
modified.
curve_name Existing Acurve name Specifies the name of a CURVE that defines the
contour or shape on which the fixed marker can
move.
i_marker_name Existing marker name Specifies the name of a fixed MARKER that
Adams constrains to lie on the curve defined by
CURVE and REF_MARKER.
constraint 131

j_floating_marker_name Existing floating marker Specify an existing floating marker name.
name
ref_marker_name Existing marker Specifies the name of a MARKER fixed on the
part containing the curve on which the
I_MARKER must move.
displacement_ic Length Specifies the initial point of contact on the curve.
no_displacement_ic true Specifies that if a DISPLACEMENT_IC has been
set via any means, to "UNSET" the displacement
initial condition.
velocity_ic Velocity Specifies the initial tangential velocity of the
I_MARKER along the curve.
no_velocity_ic True Specifies that if a VELOCITY_IC has been set via
any means, to "UNSET" the velocity initial
condition.
ic_ref_marker_name Existing marker Specifies the name of a the fixed MARKER
defining the coordinate system in which the values
for DISPLACEMENT_IC values are specified.
be assigned to it.
data file for your model. AdamsAdams requires that each modeling element be identified by a unique
integer identifier. If you use this parameter to specify a non-zero identifier, Adams View will use it in
the corresponding statement in the Adams data file.
yourself.
3. The REF_MARKER is used to associate the shape defined by the CURVE to the part on which the
REF_MARKER lies. The curve coordinates are therefore specified in the coordinate system of the
REF_MARKER. The floating J marker and REF_MARKER must belong to the same PART.
If the marker is not visible on the screen, you must type the name. You may also find it convenient
to type the name even if the marker is displayed.
time.
4. If the point specified is not exactly on the curve, Adams uses a point on the curve nearest to that
specified. By default, DISPLACEMENT_IC is specified in the REF_MARKER marker coordinate
system. If another coordinate system is more convenient, you may supply the IC_REF_MARKER
argument and enter DISPLACEMENT_IC in IC_REF_MARKER marker coordinates. If you
supply DISPLACEMENT_IC values, Adams assembles the system with the I_MARKER at the
specified point on the curve, even if it must override part initial conditions in order to do so. If you
do not supply DISPLACEMENT_IC, Adams assumes the initial contact is at the point on the curve
closest to the initial I_MARKER position. However, it may adjust that contact point to maintain
other part or constraint initial conditions.
5. The velocity_ic parameter specified the speed at which the I_MARKER is initially moving relative to
the curve. The VELOCITY_IC is negative if the I_MARKER is moving towards the start of the
curve, positive if the I_MARKER is moving toward the end of the curve, and zero if the I_MARKER
is stationary on the curve.
constraint 133
If you supply the VELOCITY_IC, Adams gives the I_MARKER the specified initial tangential
velocity along the curve, even if it must override part initial conditions in order to do so. If you do
not supply VELOCITY_IC, Adams assumes the initial tangential velocity is zero, but may adjust that
velocity to maintain other part or constraint initial conditions.
6. The POINT_CURVE command defines a point-to-curve constraint, which restricts a fixed point
defined on one part to lie on a curve defined on a second part. This is an instance of a higher pair
constraint.
The part containing the I_MARKER is free to roll and slide on the curve that is fixed to a second part.
Lift-off is not allowed, i.e., the I_MARKER must always lie on the curve.
The curve itself may be planar or spatial, open or closed. The "floating J" marker origin defines the
contact point on the curve; its orientation defines the tangent, normal, and binormal at the contact
point. A POINT_CURVE constraint removes two translational degrees-of-freedom from the system.
Adams restricts the origin of the I_MARKER to always lie on the curve. The I_MARKER may
translate only in one direction relative to the curve, along the instantaneous tangent. The I marker is
free to rotate in all three directions.
More than one POINT_CURVE or CURVE_CURVE element may reference the same CURVE
The VELOCITY_IC is specified in the reference frame of the part containing the REF_MARKER.
In other words, the VELOCITY_IC is the speed of the I_MARKER specified from the standpoint of
an observer on the part containing the curve. This means that if the I_MARKER is not moving
globally but the curve is, then VELOCITY_IC is still non-zero.
The initial conditions arguments, DISPLACEMENT_IC and VELOCITY_IC, impose constraints
that are active only during an initial conditions analysis. Adams does not impose these initial
conditions during subsequent analyses.
For a kinematic analysis, the initial conditions are redundant. Do not use the DISPLACEMENT_IC
or VELOCITY_IC arguments on the POINT_CURVE command for systems with zero degrees of
freedom.
Cautions:
1. For the no_displacement_ic and no_velocity parameters, setting these parameters to true is not the
same as setting the value to zero. A zero displacement/velocity is not the same as "no"
displacement/velocity. Therefore, by setting this parameter to true there is no longer a displacement
2. The I_MARKER and REF_MARKER must belong to different parts.
3. Adams aborts the simulation if the contact point moves off the end of an open curve. The user should
make sure the CURVE statement defines the curve over the expected range of motion.
4. The IC_REF_MARKER must be on the same part as the REF_MARKER.
constraint modify joint cylindrical
Tip: The x, y, z values associated with the CURVE are the coordinates of points lying on the
CURVE and are calculated in the coordinate system of the REF_MARKER.

Allows the modifcation of a cylindrical joint.
Format:
joint_name = existing joint name
new_joint_name = new joint name
adams_id = Geom_id
comments = String
angular_velocity_ic = angular_velocity
Example:
constraint modify joint Cylindrical &
new_joint_name = My_Cylinderical_joint &
adams_id = 2 &
constraint 135
Description:

joint_name New joint name Specifies the name of an existing joint.
New_joint_name New joint name Specifies new name of the joint. You may use this name
later to refer to this joint.
Adams data file.
modified.
no_translational_ic True Specifies that if a "translational" velocity initial condition
has been set, to "UNSET" the "translational" velocity
initial condition for the specified constraint.
velocity_ic Velocity Specifies the initial translational velocity on a translational
no_velocity_ic True Specifies that if a VELOCITY_IC has been set via any
rotational_ic Real Specifies the initial rotational displacement on a revolute
no_rotational_ic True Specifies that if a "rotational" velocity initial condition has
been set, to "UNSET" the "rotational" velocity initial
condition for the specified constraint.
angular_velocity_ic Angular_velocity Specifies the initial angular velocity on a revolute or
cylindrical joint.
no_angular_velocity_ic True Specifies that if an "angular_velocity" initial condition has
been set, to "UNSET" the "angular_velocity" initial
i_marker_name Existing marker Specifies a marker on the first of two parts connected by
this joint.
j_marker_name Existing marker Specifies a marker on the second of two parts connected by
this joint.
unique name.
be assigned to it.
corresponding statement in the AdamsAdams data file.
z-axis of the I and the J markers with respect to the origin of the J marker.
If you specify TRANSLATIONAL_IC, but not VELOCITY_IC, Adams View will set
VELOCITY_IC to zero.
analyses.
axis of the I and the J markers with respect to the origin of the J marker.
If you specify VELOCITY_IC, but not TRANSLATIONAL_IC, Adams View will set
TRANSLATIONAL_IC to zero.
analyses.
constraint 137
analyses.
analyses.
7. A cylindrical joint is a two-degree-of-freedom joint that allows both relative translational and relative
rotational displacement of one part with respect to another. For a cylindrical joint, Adams keeps the
z-axis of the I marker parallel to, and co-directed with, the z-axis of the J marker and confines the
origin of the I marker to the z-axis of the J marker so that the I and the J markers have a common z-
axis. To determine translational motion, Adams measures the movement of the origin of the I marker
along the z-axis and with respect to the J marker. To determine rotational motion, Adams measures
the rotation of the x-axis of the I marker about the common z-axis and with respect to the x-axis of
the J marker.
Caution: For the parameters “no_translational_ic”,”no_velocity_ic”,”no_rotational_ic”,setting it to true

is not the same as setting the value to zero. A zero velocity is not the same as "no" velocity.
Therefore, by setting this parameter to true there is no longer a velocity initial condition for
this element.
constraint modify joint fixed
Tip: Adams View connects one part at the I marker to the other at the J marker.

Allows the modification of an existing fixed joint.
Format:
new_joint_name = a new joint
adams_id = integer
comments = string
Example:
constraint modify joint fixed &
new_joint_name = JOINT__2 &
adams_id = 2 &
Description:

joint_name An existing joint Specifies the joint to modify.
new_joint_name A new joint Specifies the name of the new joint.
adams_id ADAMS_ID Specifies an integer used to identify this element in the Adams
data file.
constraint 139

i_marker_name An Existing Marker Specifies a marker on the first of two parts connected by this
joint. Adams View connects one part at the I marker to the
other at the J marker.
j_marker_name An Existing Marker Specifies a marker on the second of two parts connected by this
1. A fixed joint essentially locks to parts together. It can be used as a placeholder for another joint or in
conjunction with the ACTIVATE and DACTIVATE commands in Adams to model special effects.
be assigned to it.
constraint modify joint hooke
6. A FIXED joint is a zero-degree-of-freedom joint that superimposes the origins of the I and J markers
while also constraining the X, Y, and Z axes of the I marker to remain parallel to the respective X, Y,
and Z axes of the J marker.
2. Use the joint name parameter to identify the existing joint to affect with this
command.
3. You may use the new_joint_name later to refer to this joint. Adams View will not allow
you to have two joints with the same full name, so you must provide a unique name.

Allows the modification of an existing hooke joint.
Format:
adams_id = integer
comments = string
Example:
constraint modify joint hooke &
adams_id = 2 &
constraint 141
constraint modify joint hooke &

Description:

joint_name An existing joint Specifies the joint to modify. You use this parameter to identify
the existing joint to affect with this command.
new_joint_name A new joint Specifies the name of the new joint. You may use this name
later to refer to this joint. Adams View will not allow you to
have two joints with the same full name, so you must provide
a unique name.
data file.
1. The UNIVERSAL joint required the Z-axis of the I marker to be perpendicular to the Z-axis of the
J marker, whereas the HOOKE joint requires THE X-axis of the I marker to be perpendicular to the
Y-axis of the J marker, so that they outline the crosspiece of the joint. A valid HOOKE joint may be
properly defined with two coincident markers and can better take advantage of the automatic marker
generation capabilities of Adams View.
constraint modify joint planar
be assigned to it.
6. A HOOKE joint is a two-degree-of-freedom joint that is that same as the UNIVERSAL joint with
the exception that the marker orientations have been modified.

Allows the modification of an existing planar joint.
Format:
adams_id = integer
comments = string
constraint 143

Example:
constraint modify joint planar &
adams_id = 2 &
Description:

joint_name An Existing Joint Specifies the joint to modify.
new_joint_name A New Joint Specifies the name of the new joint.
adams_id Adams_id Specifies an integer used to identify this element in the Adams
data file.
joint.
joint.
constraint modify joint rackpin
be assigned to it.
5. A planar joint is a three-degree-of-freedom joint that allows the x-y plane of one part to slide in the
x-y plane of another part. For a planar joint, Adams keeps the origin of the I marker in the x-y plane
of the J marker and keeps the z axis of the I marker perpendicular to the x-y plane of the J marker.
2. Use the joint_name parameter to identify the existing joint to affect with this
command.

Allows modification of an existing rack-and-pinion joint.
constraint 145
Format:
adams_id = integer
comments = string
diameter_of_pitch = real number
Example:
:
constraint modify joint rackpin &

adams_id = 2 &
j_marker_name= marker_2 &
diameter_of_pitch = 0.22
Description:

new_joint_name A New Joint Specifies the name of the new joint.
data file.
joint.
j_marker_name An Existing Marker Specifies a marker on the second of two parts connected by
this joint.
diameter_of_pitch Length Specifies the pitch diameter of the pinion gear of a rack-and-
pinion joint.
1. For a rack-and-pinion joint, the x-axis of the pinion must be parallel to and pointed in the same
direction as the z (translational) axis of the rack. The separation between the two axes should be one-
half the pitch diameter of the pinion. The rack-and-pinion joint itself does not enforce the position
and orientation it requires, but the chain of both parts and joints that connects markers I and J should
enforce the position and orientation. A common approach for enforcing the position and the
orientation is to support the rack with a translational joint and to support the pinion with a revolute
joint.
be assigned to it.
constraint 147
constraint modify joint revolute
7. A rack-and-pinion joint is a five-degree-of-freedom joint that constrains the rotational and
translational displacement of the I marker as it rolls along the z-axis of the J marker. The I marker is
at the center of the pinion, and the J marker is in the rack.
Tip: 1. If you type a "?", AdamsAdams View will list the joints available by default.
2. Use the joint_name parameter to identify the existing joint to affect with this
command.

Allows the modifcation of a revolute joint.
Format:
new_joint_name = new joint
adams_id = geom._id
comments = string
angular_velocity_ic = angular_vel
delta_v = real

mu_dyn_rot = real
mu_stat_rot = real
max_fric_rot = torque
preload_radial = force
preload_axial = force
inner_radius = length
outer_radius = length
location = location
orientation = orienatation
Example:
constraint modify joint Revolute &
neW_joint_name = MY_REVOLUTE_JOINT &
adams_id = 1 &
Description:

joint_name Existing joint Specifies the name of the joint to be modified. You may use
New_joint_name New joint name Specified the name of the new joint.
Adams data file.
constraint 149

modified.
rotational_ic Real Specifies the initial rotational displacement on a revolute or
cylindrical joint.
no_rotational_ic True Specifies that if a "rotational" velocity initial condition has
been set, to "UNSET" the "rotational" velocity initial
angular_velocity_ic Real Specifies the initial angular velocity on a revolute or
cylindrical joint.
no_angular_velocity True Specifies that if an "angular_velocity" initial condition has
_ic been set, to "UNSET" the "angular_velocity" initial
friction_enabled Yes/No/Preload_only The constant default value will be used if this parameter is
omitted.
delta_v Real Real number should be greater than zero.
maximum_deformati Real Real number should be greater than zero.
on
mu_dyn_rot Real A real number greater than or equal to 0
mu_stat_rot Real A real number greater than or equal to 0
max_fric_rot Torque A real number greater than or equal to 0
preload_radial Force A real number greater than or equal to 0
preload_axial Force A real number greater than or equal to 0
inner_radius Length A real number greater than or equal to 0
outer_radius Length A real number greater than or equal to 0
i_part_name Existing body Specifies the part that is the first of two parts connected by
this joint. Adams View connects one part at the I marker to
the other at the J marker. These markers are automatically
generated using this method of joint creation.
j_part_name Existing body Specifies the part that is the second of two parts connected
by this joint. Adams View connects one part at the J marker
to the other at the I marker. These markers are
creation.
Location Location Specifies the locations to be used to define the position of a
constraint during its creation.
orientation orientation Specifies the orientation of the J marker for the constraint
being created using three rotation angles.

along_axis_orientatio Location Specifies the orientation of a coordinate system (for
n example, marker or part) by directing one of the axes.
relative_to Existing model, part Specifies the coordinate system that location coordinates
or marker and orientation angles are with respect to.
i_marker_name Existing marker Specifies a marker on the first of two parts connected by
this joint.
Adams View connects one part at the I marker to the other

at the J marker.
this joint.
Adams View connects one part at the I marker to the other

at the J marker.
unique name.
be assigned to it.
constraint 151
analyses.
analyses.

x, y, and z angles.
system.
7. Adams View will assign an arbitrary rotation about the axis.
You may enter either one or two locations to direct the axis. If you enter one location, the axis will
system.
system.
10. A revolute joint is a single-degree-of-freedom joint that allows rotation of one part with respect to
another about a common axis. For a revolute joint, Adams superimposes the origins of the I and J
markers and keeps their z-axes parallel and co-directed. Relative motion occurs about the common z-
axis. Adams measures the angle of the x-axis of the I marker relative to the x-axis of the J marker to
determine the rotational displacement. Adams measures positive rotation according to the right-hand
rule.
constraint 153
constraint modify joint screw
Cautions:
1. “No_rotational_ic” and “no_angular_velocity_ic” being set to True is not the same as setting the
value to zero. A zero velocity is not the same as "no" velocity. Therefore, by setting this parameter to
true there is no longer a velocity initial condition for this element.

Allows the modification of an existing screw joint.
Format:
adams_id = integer
comments = string
pitch = real number
Example:
constraint modify joint screw &
adams_id = 2 &
pitch = 0.22
Description:

new_joint_name A New Joint Specifies the name of the new joint. You may use this name
data file.

this joint. Adams View connects one part at the I marker to the
pitch Length Specifies the pitch of the scew joint.
1. For a screw joint, the z-axis of the I marker and the z-axis of the J marker must always be parallel and
co-directed. Although the screw joint does not enforce this parallelism, the chain of parts and joints
that connects the two markers should.
During simulation, the I marker displacement along the J marker z-axis is a function of the relative
angle of the x-axis of the I marker with respect to the x-axis of the J marker. Adams measures a positive
rotation according to the righthand rule. For every full rotation, the displacement of the I marker
along the z-axis of the J marker is equal to the value of the screw pitch. If phi is zero, the translational
displacement may be zero or any multiple of the pitch.
constraint 155
constraint modify joint spherical
be assigned to it.
6. A screw joint is a five-degree-of-freedom joint that constrains the rotational and translational
displacement of the I marker as it spins about the z-axis of the J marker.
Tips:
1. If you type a "?", Adams View will list the joints available by default.
2. Use the joint_name parameter to identify the existing joint to affect with this command.
unique name.

Allows the modification of a spherical joint.
Format:
new_joint_name = new_joint
adams_id = geom._id
comments = string
i_marker_name = Existing marker
Example:
constraint modify joint Spherical &
new_joint_name = My_joint &
adams_id = 6 &
Description:

joint_name Existing joint name Specifies the name of an existing joint.
New_joint_name New joint Specifies new name of the joint. You may use this name later
to refer to this joint.
Adams data file.
modified.
joint.
this joint.
unique name.
constraint 157
constraint modify joint translational
be assigned to it.
3. A spherical joint is a three-degree-of-freedom joint. While permitting all three rotations, a spherical
joint superimposes the I and the J markers.
Tips:

Allows the modification of an existing translational joint.
Format:
new_joint_name = a new joint name
adams_id = integer
comments = string
velocity_ic = real
delta_v = real
mu_dyn_trans = real
mu_stat_trans = real
max_fric_trans = real

preload_x = real
preload_y = real
height = real
width = real
location = location
Example:
constraint modify joint translational &
adams_id = 2 &
translational_ic = 1.2 &
velocity_ic = 1.4 &
friction_enabled = preload_only &
delta_v = 1.4 &
maximum_deformation = 0.02 &
mu_dyn_trans = 0.4 &
mu_stat_trans = 0.8 &
max_fric_trans = 0.15 &
preload_x = 1 &
preload_y = 1.2 &
height = 1.5 &
width = 0.8 &
constraint 159
constraint modify joint translational &

location = 10 , 10 , 5 &
Description:

joint_name An Existing Joint Specifies the joint to modify. You use this parameter to
identify the existing joint to affect with this command.
new_joint_name A New Joint
Adams data file.
modified.
no_translational_ic True_only Specifies that if a "translational" velocity initial
"translational" velocity initial condition for the
no_velocity_ic True_only Specifies that if a VELOCITY_IC has been set via any
friction_enabled Enable_friction
delta_v Real
maximum_deformation Real
mu_dyn_trans Real
mu_stat_trans Real
max_fric_trans Real
preload_x Force
preload_y Force
height Real Specify a height for the info window.
width Real Specify a width for the info window.

i_part_name An Existing Body Specifies the part that is the first of two parts
part at the I marker to the other at the J marker. These
of joint creation.
part at the J marker to the other at the I marker. These
of joint creation.
The I marker is oriented based on the J marker
orientation and the requirements of the particular
constraint being created. These markers are created
automatically.
axis.
part at the I marker to the other at the J marker.
constraint 161
1. A translational joint is a single-degree-of-freedom joint that allows translational displacement of one
part relative to another. For a translational joint, Adams keeps all the axes of the I and the J markers
parallel and keeps the origin of the I marker on the z-axis of the J marker so that the two markers have
a common z-axis. To determine the translational displacement of the I marker with respect to the J
marker, Adams measures the origin of the I marker with respect to the origin of the J marker along
their common z-axis.
type the name even if the joint is displayed. If you created the joint by reading an Adams data set or
graphics file, the joint name is the letters JOI followed by the Adams data set joint ID number. The
name of Adams JOINT/101 is JOI101, for example. If you created the joint during preprocessing,
you gave it a name at that time. If a joint is available by default, you may identify it by entering its
name only. If it is not, you must enter its full name. To identify a joint under a model, for instance,
you may need to enter the model name as well. For example, you may specify joint 'lower_pivot' in
model 'links' by entering ".links.lower_pivot". You must separate multiple joint names by commas.
associated with it. You need not separate multiple joint picks by commas.
3. For a translational joint, Adams keeps all the axes of the I and the J markers parallel and keeps the
origin of the I marker on the z-axis of the J marker so that the two markers have a common z-axis. To
determine the translational displacement of the I marker with respect to the J marker, Adams
measures the origin of the I marker with respect to the origin of the J marker along their common z-
axis.
be assigned to it.
explicitly or by default. The next time you write an Adams file, AdamsAdams View will replace the
zero with a unique, internally-generated identifier. Adams View will permanently store this identifier
with the element just as if you had entered it yourself. Normally, you would let all identifiers default
to zero, and Adams View would generate the identifiers for you. You are never required to enter a
non-zero identifier. You only need to specify it if, for some reason, you wish to control the Adams file
output.
z-axis of the I and the J markers with respect to the origin of the J marker. If you specify
TRANSLATIONAL_IC, but not VELOCITY_IC, Adams View will set VELOCITY_IC to zero.
analyses. If you impose initial conditions on the joint that are inconsistent with those on a part in the
joint, the initial conditions on the joint have precedence over those on the part. However, if you
impose initial conditions on the joint that are inconsistent with imparted motions on the joint, the
initial conditions as specified by the motion generator have precedence over those here.
8. Setting the no_translational_ic is not the same as setting the value to zero. A zero velocity is not the
same as "no" velocity. Therefore, by setting this parameter to true there is no longer a velocity initial
axis of the I and the J markers with respect to the origin of the J marker. If you specify
VELOCITY_IC, but not TRANSLATIONAL_IC, Adams View will set TRANSLATIONAL_IC to
zero. Joint initial conditions impose constraints that are active only during initial conditions analysis
(not at the time of the initial configuration). Adams does not impose initial conditions during
subsequent analyses. If you impose initial conditions on the joint that are inconsistent with those on
a part in the joint, the initial conditions on the joint have precedence over those n the part. However,
if you impose initial conditions on the joint that are inconsistent with imparted motions on the joint,
the initial conditions as specified by the motion generator have precedence over those here.
10. Setting the no_velocity_ic parameter is not the same as setting the value to zero. A zero velocity is not
the same as "no" velocity. Therefore, by setting this parameter to true there is no longer a velocity
11. The height and the width values should be a real number between 0.0 and 2.0, where 2.0 represents
the height of the Adams View window. Therefore, a value of 1.0 will set the info window to be one
12. By default, you supply Cartesian (x, y, z) coordinates for the location parameter. You may use the
'defaults units coordinate_system_type =' command to change this convention. For example,
selecting 'cylindrical' means you will subsequently be supplying r, theta, and z coordinates. Adams
View applies your location coordinates in the coordinate system you identify with the
constraint 163
constraint modify joint universal
system.
Tips:
1. If you type a "?", Adams View will list the joints available by default.

Allows you to modify a universal joint.
Format:
new_joint_name = new joint name
adams_id = geom_id
comments = String
Example:
constraint modify joint universal &
new_joint_name = MY_JOINT &
adams_id = 4 &
Description:

joint_name Existing joint name Specifies the name of an existing joint.
New_joint_name New joint name Specifies a new name for the joint. You may use this name
Adams data file.
Comments String Specifies comments for the object being created or modified.
joint.
this joint.
unique name.
constraint 165
constraint modify motion_generator
be assigned to it.
reason, you wish to control the Adams file output system.
3. A universal joint is a joint that allows two degrees of rotational freedom.
For a universal joint, Adams superimposes the origins of I and J and keeps their z-axes perpendicular,
so that they outline the crosspiece of the joint. The origins of the I and the J markers are at the center
of the crosspiece.
Tips:

Allows the modifcation of a motion generator in a model.
Format:
motion_name = an existing motion
new_motion_name = new name for the motion
adams_id = geom._id

comments = string,
type_of_freedom = freedom type
axis = motion_axes
function = function
time_derivative = displacement/ velocity/ acceleration
rotational_displacement_ic = angle
rotational_velocity_ic = angular_velocity
Routine = string
Example:
constraint modify motion_generator &
motion_name = ROT_MOTION &
new_motion_name = ROTATIONAL_MOT &
type_of_freedom = rotational &
function = time &
rotational_velocity_ic = 25.9 &
rotational_displacement_ic = 25.4
The above command will apply a rotational motion to the specified joint which is a function of time. Its
rotational velocity would be 25.9 and its rotational displacement would be 25.4.
constraint 167
Description:

motion_name Existing motion name Specifies the name of the motion generator to be
modified.
New_motion_nameAda New motion Specifies the new name for the motion. You may
ms use this name later to refer to this motion
generator.
modified.
joint_name Existing joint Specifies the translational, revolute, or cylindrical
constrain motion at, or are otherwise associated
with, specific joints. You use this parameter to
identify that joint.
type_of_freedom Translational/rotational Specifies translational or a rotational motion if you
attach this motion generator to a cylindrical joint.
i_marker_name Existing marker Specify an existing I marker
j_marker_name Existing marker Specify an existing J marker
axis X/Y/ Z/ B1/ B2/ B3 Allows you to create and modify additional axes
on a plot to effect multiple axis plotting.
function Function Specifies an expression or defines and passes
constants to a user-written subroutine to define
the motion.
user-written subroutine.
Routine String
time_derivative VELOCITY/DISPLACE Specifies that the FUNCTION argument defines
MENT/ACCELERATIO the motion displacement, velocity, or acceleration.
N
displacement_ic Length Specifies the initial displacement of the motion,
when the motion is defined in terms of velocity or
acceleration.

velocity_ic Velocity Specifies the initial velocity of the motion, when
the motion is defined in terms of acceleration.
rotational_displacement Angle Specifies the rotational displacement.
_ic
rotational_velocity_ic Real Specifies the rotational velocity.
1. Adams View will not allow you to have two motion generators with the same full name, so you must
be assigned to it.
corresponding statement in the AdamsAdams data file.
constraint 169
associated with it.
4. The “type_of_freedom” parameter is necessary only when you apply motion to a cylindrical joint. For
a translational joint or a revolute joint, Adams assumes you want translational motion or rotational
motion, respectively.
5. When you create a plot template, Adams View creates two axes by default, one horizontal and one
vertical. These are the plot's primary axes which Adams View uses to perform cursor tracking and to
draw the grid. The plot TEMPLATE commands also operate on the plot's primary axes.
Each axis consists of an axis line, tic marks, numbers and a label. Use the axis ATTRIBUTES to
change visibility and color attributes for the axis entities.
To plot a curve against the new axes, specify the axis names when you create the curve.
You can make the new axes the plot's primary axes by modifying the plot's template and specifying
the desired axes as the PRIMARY_HAXIS and PRIMARY_VAXIS. The grid will then reflect the
divisions of the new axes and cursor tracking will reflect the new axes' coordinate system.
6. The motion must be a function of time only and not a function of the state variables.
Adams View treats this parameter as a series of literal strings. When you write an Adams data set,
Adams View writes these strings, just as you enter them here, after the 'FUNCTION=' argument.
If you want to define the motion with an expression, enclose the expression in quotes and enter it just
as you would in the data set. See the Adams User's Manual for information on writing function
expressions. If your expression is longer than 65 characters, you should break it up into separate
strings so it does not extend past the Adams 80-character line-length limit. Adams View will write
each string on a separate line in the data set.
If you want to define the motion with a user-written subroutine, enter the character string
"USER(r1[,...,r30])", where r1[,...,r30] are the values you want Adams to pass to your user-written
subroutine MOTSUB. If you enter "USER(1.,2.,3.)", for instance, Adams will call your MOTSUB
with values 1, 2, and 3. See the Adams User's Manual for more information on using MOTSUBs.
7. A MOTION_GENERATOR determines a translational or a rotational motion as a function of time.
In Adams you can apply a motion to a translational, to a revolute, or to a cylindrical joint. You can
define the motion with a FUNCTION expression or with a user-written subroutine.
You can assign a translational motion at either a translational or a cylindrical joint, and you can assign
a rotational motion at either a revolute or a cylindrical joint. Adams uses the two markers that specify
the joint to define the motion. In other words, Adams controls the rotational or the translational
displacement of the I marker in the joint with respect to the J marker in the joint.
constraint modify primitive_joint inplane
For a translational motion, Adams moves the I marker along the z-axis of the J marker. The J marker
origin represents zero displacement, while the z-axis of the J marker defines the positive direction. For
a rotational motion, Adams rotates the I marker about the z-axis of the J marker. Positive rotations
are positive according to the right-hand rule. The z-axis of the I marker must be collinear with the z-
axis of the J marker at all times. The angle is zero when the x-axis of the I marker is also collinear with
the x-axis of the J marker.

Allows the modification of an existing inplane joint primitive.
Format:
jprim_name = an existing primitive joint name
new_jprim_name = a new primitive joint name
adams_id = integer
comments = string
Example:
constraint modify primitive_joint inplane &
new_jprim_name = JPRIM__2 &
adams_id = 2 &
Description:

jprim_name An Existing Primitive Specifies the jprim to modify.
Joint
new_jprim_name A New Primitive Joint Specifies the name of the new jprim.
constraint 171

modified.
i_marker_name An Existing Marker Specifies a marker on the first of two parts
1. An inplane joint primitive indicates a five-degree-of-freedom joint primitive that allows both
translational and rotational motion of one part with respect to another.For an inplane primitive,
Adams imposes one translational constraint, which confines the translational motion of the I marker
to the x-y plane of the J marker.
2. You may identify a jprim by typing its name or by picking it from the screen. If the jprim is not visible
jprim is displayed. If you created the jprim by reading an Adams data set or graphics file, the jprim
name is the letters JPR followed by the Adams data set jprim ID number. The name of Adams
JPRIM/101 is JPR101, for example. If you created the jprim during preprocessing, you gave it a name
at that time. If a jprim is available by default, you may identify it by entering its name only. If it is
not, you must enter its full name. To identify a jprim under an analysis, for instance, you may need
to enter the analysis name as well. For example, you may specify jprim 101 from the analysis named
test by entering ".test.jpr101". You must separate multiple jprim names by commas. If the jprim is
visible in one of your views, you may identify it by picking on any of the graphics associated with it.
You need not separate multiple jprim picks by commas.
be assigned to it.
constraint modify primitive_joint orientation
Tips:
1. If you type a "?", Adams View will list the jprims available by default.
2. You use the jprim_name parameter to identify the existing jprim to affect with this command.
3. You may use the newjprim_name later to refer to this jprim. Adams View will not allow you to have
two jprims with the same full name, so you must provide a unique name.

Allows the modification of an existing orientation joint primitive.
Format:
adams_id = integer
comments = string
Example:
constraint modify primitive_joint orientation &
adams_id = 2 &
constraint 173
constraint modify primitive_joint orientation &

Description:

Joint
new_jprim_name A New Primitive Joint Specifies the name of the new jprim. You may use
modified.
1. An orientation joint primitive indicates a three-degree-of-freedom joint primitive that allows only
translational motion of one part with respect to another. For an orientation primitive, Adams imposes
three rotational constraints to keep the orientation of the I marker identical to the orientation of the
J marker.
constraint modify primitive_joint parallel_axis
be assigned to it.
Tips:
2. You use this parameter to identify the existing jprim to affect with this command.
unique name.

Allows modification of an existing parallel axis joint primitive.
Format:
adams_id = integer
constraint 175

comments = string
Example:
constraint modify primitive_joint parallel_axis &
adams_id = 2 &
Description:

Joint
data file.
joint.
this joint.
1. A parallel joint primitive is a four-degree-of-freedom joint primitive that allows both translational and
rotational motion of one part with respect to another. For a parallel axis primitive, Adams imposes
two rotational constraints so that the z-axis of the I marker stays parallel to the z-axis of the J marker.
This primitive permits relative rotation about the common z-axis of I and J and permits all relative
displacements.
be assigned to it.
Tips:
3. You may use the new_jprim_name later to refer to the jprim. Adams View will not allow you to have
constraint 177
constraint modify primitive_joint perpendicular

Allows the modifcation of a perpendicular joint primitive.
Format:
Constraint modify primitive_joint perpendicular
jprim_name = existing primitive joint name
new_jprim_name = new name for existing jprim
adams_id = geom_id
comments = string
Example:
constraint modify primitive_joint perpendicular &
new_jprim_name = MY_JPRIM &
Description:

Jprim_name Existing primitive joint Specifies the name of the jprim to be modified.
name
New_jprim_name New name for jprim Specifies the name of the new jprim. You may use this
name later to refer to this jprim.
Adams data file.
modified.
i_marker_name Existing marker name Specifies a marker on the first of two parts connected by
this joint.
j_marker_name Existing marker name Specifies a marker on the second of two parts connected
by this joint.
unique name.
be assigned to it.
yourself.
3. A perpendicular joint primitive is a five-degree-of-freedom joint primitive that allows both
For a perpendicular primitive, Adams imposes a single rotational constraint on the I and the J markers
so that their z-axes remain perpendicular. This allows relative rotations about either z-axis, but does
not allow any relative rotation in the direction perpendicular to both z-axes.
Tips:
constraint 179
constraint modify primitive_joint point_point

Allows the modification of an existing point_point joint primitive.
Format:
adams_id = integer
comments = string
offset = length
Example:
constraint modify primitive_joint point_point &
adams_id = 2 &
offset = 2
Description:

Joint
Adams data file.
modified.

this joint.
by this joint.
offset Length Specifies the prescribed distance between the two points.
1. An point_point joint primitive constrains three translational DOF and allows three rotational DOF.
This jprim is diferent from a conventional spherical joint as it allows a constant non-zero distance
between i_marker and j_marker. This is similar to a dummy bar having spherical and hookes joint at
respective ends, but it does not specifically constrain any direction, just the total distance between I
and J.
JPRIM/101 is JPR101, for example. If you created the jprim during preprocessing, you gave it a
name at that time. If a jprim is available by default, you may identify it by entering its name only. If
it is not, you must enter its full name. To identify a jprim under an analysis, for instance, you may
need to enter the analysis name as well. For example, you may specify jprim 101 from the analysis
named test by entering ".test.jpr101". You must separate multiple jprim names by commas. If the
jprim is visible in one of your views, you may identify it by picking on any of the graphics associated
with it. You need not separate multiple jprim picks by commas.
geometry element) when you CREATE it by changing the name. If you enter just the entity name, then
"...._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.
4. When you use the FILE ADAMS_DATA_SET WRITE command, Adams View writes an Adams data
constraint 181
constraint modify user_defined
must follow the title statement and be followed by the comment 'END OF MODEL COMMENTS'. This
string must be uppercase. When an Adams Solver data file is written, the comments for an object are
written before the statement corresponding to the object.
Tips:

Allows the user to modify a USER DEFINED constraint.
Format:
user_constraint_name = existing user constraint
new_user_constraint_name = new name for the user constraint
adams_id = geom._id
comments = string
user_function = function
Description:

user_constraint_name Existing user defined Allows the user to modify a USER DEFINED
constraint constraint.
New_user_constraint_na New name for the user Specify the new name for the user defined
me defined constraint constraint.
modified.
2. A user-defined constraint describes a system constraint as a function of time and as many as thirty
variables. Each of these variables must be the displacement or the velocity of a part. For any part at
any point in time, six displacements define its position, and six velocities define its velocity. The six
displacements are the x, y, and z translations and the three Euler angle rotations. The six velocities are
the x, y, and z translational velocities and the time derivatives of the three Euler angles. Adams
measures all of these displacements and velocities at the origin of the principal axes with respect to the
global coordinate system. A USER DEFINED constraint is only used when a constraint is needed
that is not definable by any of the other constraint types.
contact 1
contact copy
contact
contact copy
Allows you to copy an existing contact and creates an identical new contact with a different name, which is
to be specified by the user.
Format:
contact copy
contact_name = An existing contact
new_contact_name = A new contact
Example:
contact copy &
contact_name = contact__1 &
new_contact_name = contact__2
Description:

Contact_name An Existing Specifies the contact to be deleted.
Contact
New_contact_name A New Contact Specifies the new contact which will be a copy of the existing
one.
Tips:
1. On typing “contact delete” followed by a “?” in the command window, the option “contact_name =”
is automatically displayed. If you need to find out the various contacts already present, type ? once
again. This will result in all the existing contact names that can be deleted being displayed in the
command window.
contact create
Allows you to create a contact force between two geometries. You will need to specify the two
parts/geometries/flexible bodies using their marker, geometry or flexible body names.
contact create
Format:
contact create
contact_name = a new contact
adams_id = integer
comments = string
type = string
i_geometry_name = an existing geometry
j_geometry_name = an existing geometry
i_flex = an existing flexible body
j_flex = an existing flexible body
i_edge = an existing edge
j_edge = an existing edge
i_edge_index = an existing edge index
j_edge_index = an existing edge index
i_flip_normal = string
j_flip_normal = string
i_flip_geometry_name = existing contact_curve
j_flip_geometry_name = existing contact_curve
face_contact_bottom = True/False
face_contact_top = True/False
geometry_routines = string
stiffness = real
damping = real
dmax = real
exponent = real
penalty = real
restitution_coefficient = real
normal_function = real
normal_routine = string
augmented_lagrangian_formulation = yes/no
coulomb_friction = real
mu_static = real
mu_dynamic = real
contact 3
contact create
contact create
friction_transition_velocity = real
friction_function = real
friction_routine = string
no_friction = true_value
stiction_transition_velocity = real
Example:
contact create &
adams_id = 1 &
j_geometry_name = link_1 &
i_flip_normal = yes &
j_flip_normal = no &
geometry_routines = "routine 1" &
stiffness = 0.12 &
damping = 0.18 &
dmax = 0.11 &
exponent = 0.13 &
augmented_lagrangian_formulation = no &
mu_static = 0.15 &
mu_dynamic = 0.16 &
coulomb_friction = dynamics_only &
friction_transition_velocity = 0.15 &
stiction_transition_velocity = 0.15
Description:
Parameter Value Description

contact_name A New Contact Specifies the name of the contact to be created.
adams_id Integer If this ID is not entered, Adams View will automatically create
an Adams ID for the contact.
comments String Enters any relevant comments to describe the contact.
contact create

type String Specifies contact type as:
 solid_to_solid
 curve_to_curve
 point_to_curve
 point_to_plane
 curve_to_plane
 sphere_to_plane
 sphere_to_sphere
 flex_to_solid
 flex_to_flex
 flex_edge_to_curve
 flex_edge_to_flex_edge
 flex_edge_to_plane
 cylinder_to_cylinder
i_marker_name An Existing Either the I marker or the I geometry name needs to be
Marker specified to indicate the geometry participating in the contact.
i_geometry_name An Existing Specifies the name of the geometry participating in the
Geometry contact.
j_geometry_name An Existing Specifies the name of the other geometry participating in the
Geometry contact.
i_flex An Existing Specifies the name of the first flexible body participating in the
Flexible Body contact. This parameter should be used only with Adams
Solver (C++).
j_flex An Existing Specifies the name of the other flexible body participating in
Flexible Body the contact. This parameter can only exist if the I_flex
parameter is specified and used with Adams Solver (C++).
i_edge An Existing Specifies the name of the edge on the first flexible body
edge on participating in the contact. This parameter should be used
Flexible Body only with Adams Solver C++.
j_edge An Existing Specifies the name of the edge on the other flexible body
edge on participating in the contact. This parameter can only exist if
Flexible Body the i_edge parameter is specified and used with Adams Solver
C++.
i_edge_index An Existing Specifies edge index of the first edge participating in the
edge index contact. This parameter can only exist if the i_edge parameter
is specified and used with Adams Solver C++.
contact 5
contact create

j_edge_index An Existing Specifies edge index of the other edge participating in the
edge index contact. This parameter can only exist if the j_edge parameter
i_flip_normal String Boolean value, specifying whether the normal is to be flipped
or not. Takes values, Yes or No.
j_flip_normal String Boolean value, specifying whether the normal is to be flipped
i_flip_geometry_name Existing Specifies the geometry name at which the contact should be
Contact_curve flipped on the I body.
j_flip_geometry_name Existing Specifies the geometry name at which the contact should be
Contact_curve flipped on the J body.
face_contact_bottom True/False Specific to cylinder-to-cylinder contacts where one of the
cylinders is using its internal surface for contact (that is,
i/j_flip_normal = yes). “Bottom” face is defined as the one on
which the cylinder geometry’s reference marker is located. If
set to “true” then this face will enforce contact.
face_contact_top True/False Specific to cylinder-to-cylinder contacts where one of the
i/j_flip_normal = yes). “Top” face is defined as the one on
which the cylinder geometry’s reference marker is NOT
located. If set to “true” then this face will enforce contact.
geometry_routines String Takes a string value
stiffness Real Specifies a material stiffness that you can use to calculate the
normal force for the impact model.
damping Real Used when you specify the IMPACT model for calculating
normal forces. DAMPING defines the damping properties of
the contacting material. You should set the damping
coefficient to about one percent of the stiffness coefficient.
Range: DAMPING >0
dmax Real Used when you specify the IMPACT model for calculating
normal forces.
Range: DMAX > 0
exponent Real Used when you specify the IMPACT model for calculating
normal forces.
Range: EXPONENT >1
penalty Real Used when you specify a restitution model for calculating
normal forces. PENALTY defines the local stiffness properties
between the contacting material.
contact create

restitution_coefficient Real The coefficient of restitution models the energy loss during
contact. This field is not available when I_flex and J_flex
parameters are specified. Range: 0 <
RESTITUTION_COEFFICIENT < 1
normal_function Real Specifies up to thirty user-defined constants to compute the
contact normal force components in a user-defined subroutine
normal_routine String Specifies a library and a user-written subroutine in that library
that calculates the contact normal force.
augmented_lagrangian_ Boolean Refines the normal force between two sets of rigid geometries
formulation that are in contact.
coulomb_friction Real Models friction effects at the contact locations using the
Coulomb friction model to compute the frictional forces.
mu_static Real Specifies the coefficient of friction at a contact point when the
slip velocity is smaller than the
STICTION_TRANSITION_VELOCITY. Range:
MU_STATIC > 0
mu_dynamic Real Specifies the coefficient of friction at a contact point when the
slip velocity is larger than the
FRICTION_TRANSITION_VELOCITY. Range:0 <
MU_DYNAMIC < MU_STATIC
friction_transition_velo Real Used in the COULOMB_FRICTION model for calculating
city frictional forces at the contact locations. Range:
FRICTION_TRANSITION_VELOCITY >
STICTION_TRANSITION_VELOCITY > 0
friction_function Real Specifies up to thirty user-defined constants to compute the
contact friction force components in a user-defined
subroutine
friction_routine String Specifies a library and a user-written subroutine in that library
that calculates the contact friction force.
no_friction True Will take Boolean values of true or false, based on whether
friction is present or not.
stiction_transition_velo Real Used in the COULOMB_FRICTION model for calculating
city frictional forces at the contact locations. Range: 0 <
STICTION_TRANSITION_VELOCITY <
FRICTION_TRANSITION_VELOCITY
1. For solids and curves, you can select more than one geometry as long as the geometry belongs to the
same part.
contact 7
contact create
2. For sphere-to-sphere and cylinder-to cylinder contacts, you can specify whether the contact should
be inside or outside the sphere or cylinder.
3. In general, the higher the stiffness, the more rigid or hard are the bodies in contact. Also note that the
higher the stiffness, the harder it is for an integrator to solve through the contact event.
4. Parameter dmax defines the penetration at which Adams Solver turns on full damping. Adams Solver
uses a cubic STEP function to increase the damping coefficient from zero, at zero penetration, to full
damping when the penetration is dmax. A reasonable value for this parameter is 0.01 mm. For more
information, refer to the IMPACT function.
5. Adams Solver (FORTRAN) models normal force as a nonlinear spring-damper. If PEN is the
instantaneous penetration between the contacting geometry, Adams Solver calculates the
contribution of the material stiffness to the instantaneous normal forces as STIFFNESS *
(PENALTY)**EXPONENT. For more information, see the IMPACT function. Exponent should
normally be set to 1.5 or higher.
6. A large value of PENALTY ensures that the penetration, of one geometry into another, will be small.
Large values, however, will cause numerical integration difficulties. A value of 1E6 is appropriate for
systems modeled in Kg-mm-sec. For more information on how to specify this value, see Extended
Definition. Range: PENALTY > 0
7. A value of zero for the restitution_coefficient specifies a perfectly plastic contact between the two
colliding bodies. A value of one specifies a perfectly elastic contact. There is no energy loss. The
coefficient of restitution is a function of the two materials that are coming into contact. For
information on material types versus commonly used values of the coefficient of restitution, see the
Material Contact Properties table.
8. The augmented_lagrangian_formulation parameter uses iterative refinement to ensure that
penetration between the geometries is minimal. It also ensures that the normal force magnitude is
relatively insensitive to the penalty or stiffness used to model the local material compliance effects.
You can use this formulation only with the POISSON model for normal force.
9. The friction model in CONTACT models dynamic friction but not stiction. The argument values,
on/off/dynamics_only, specify at run time whether the friction effects are to be included.
10. For information on material types versus commonly used values of the coefficient of static friction,
see the Material Contact Properties table. Excessively large values of mu_static can cause integration
difficulties.
11. For information on material types versus commonly used values of the coefficient of the dynamic
coefficient of friction, see the Material Contact Properties table. Excessively large values of mu_dynamic
can cause integration difficulties.
12. Adams Solver gradually transitions the coefficient of friction from mu_static to mu_dynamic as the
slip velocity at the contact point increases. When the slip velocity is equal to the value specified for
friction_transition_velocity, the effective coefficient of friction is set to mu_dynamic. For more
details, see Extended Definition.
13. Specifying i_flex and j_flex parameters for Adams Solver (FORTRAN) will result in a warning
message that the created contact is no longer compatible with the solver.
contact delete
14. i_edge and j_edge are the matrices consisting of the nodes of the free edges identified by the edge
index. You have to first, select a flexible body and then you will be asked to pick one of the free edges
generated (more than one free edge can exists) on the flexible body.
15. edge_index is an optional parameter. If you do not specify, it will be calculated internally.
16. If contact_type "solid-to-solid" is specified and the geometry supplied is capable of analytical contact
detection then Adams will automatically treat them analytically. See the Adams Solver CONTACT
statement documentation for details on which types of geometry are treated analytically.
17. Solid-to-solid contact is limited to external contact surfaces. So, to take advantage of analytical
contact detection for sphere or cylinder geometry and use an internal surface for contact one must
specify type = sphere_to_sphere or cylinder_to_cylinder.
Tips:
1. Small values for FRICTION_TRANSITION_VELOCITY cause the integrator difficulties. You
should specify this value as:
FRICTION_TRANSITION_VELOCITY > 5 * ERROR
where ERROR is the integration error used for the solution. Its default value is 1E-3.
contact delete
Allows you to delete an existing contact.
Format:
contact delete
contact_name = An existing contact
Example:
contact delete &
contact_name = contact_1
Description:

Contact_name An Existing Contact Specifies the contact to be deleted
Tips:
1. On typing “contact delete” followed by a “?” in the command window, the option “contact_name =”
is automatically displayed. If you need to find out the various contacts already present, type ? once
again. This will result in all the existing contact names that can be deleted being displayed on the
command window.
contact 9
contact modify
contact modify
Allows you to modify a contact force between two geometries/flexible bodies.
Format:
contact modify
contact_name = existing contact
new_contact_name = a new contact
type = contact type
adams_id = integer
comments = string
i_geometry_name = an existing geometry
j_geometry_name = an existing geometry
i_flex = an existing flexible body
j_flex = an existing flexible body
i_edge = an existing edge
j_edge = an existing edge
i_edge_index = an existing edge index
j_edge_index = an existing edge index
i_flip_normal = string
j_flip_normal = string
i_flip_geometry_name = existing contact_curve
j_flip_geometry_name = existing contact_curve
face_contact_bottom = True/False
face_contact_top = True/False
geometry_routines = string
stiffness = real
damping = real
dmax = real
exponent = real
penalty = real
restitution_coefficient = real
normal_function = real
normal_routine = string
contact modify
contact modify
augmented_lagrangian_formulation = yes/no
coulomb_friction = real
mu_static = real
mu_dynamic = real
friction_transition_velocity = real
friction_function = real
friction_routine = string
no_friction = true_value
Example:
contact modify &
new_contact_name = contact__2 &
adams_id = 1 &
i_marker_name = Marker_1 &
j_geometry_name = Link_1 &
i_flip_normal = yes &
j_flip_normal = no &
geometry_routines = "routine 1" &
stiffness = 0.12 &
damping = 0.18 &
dmax = 0.11 &
exponent = 0.13 &
augmented_lagrangian_formulation = no &
mu_static = 0.15 &
mu_dynamic = 0.16 &
coulomb_friction = dynamics_only &
friction_transition_velocity = 0.15 &
stiction_transition_velocity = 0.15
contact 11
contact modify
Description:

contact_name Existing Specifies the name of the contact to be created.
Contact
new_contact_name A New Contact Specify a new contact name
adams_id Integer If this ID is not entered, Adams View will automatically create
an Adams ID for the contact.
type String Specifies contact type as:
 solid_to_solid
 curve_to_curve
 point_to_curve
 point_to_plane
 curve_to_plane
 sphere_to_plane
 sphere_to_sphere
 flex_to_solid
 flex_to_flex
 flex_edge_to_curve
 flex_edge_to_flex_edge
 flex_edge_to_plane
 cylinder_to_cylinder
comments String Enters any relevant comments to describe the contact.
i_marker_name An Existing Either the I marker or the I geometry name needs to be
Marker specified to indicate the geometry participating in the contact.
i_geometry_name An Existing Specifies the name of the geometry participating in the
Geometry contact.
j_geometry_name An Existing Specifies the name of the other geometry participating in the
Geometry contact.
i_flex An Existing Specifies the name of the first flexible body participating in the
Flexible Body contact. This parameter should be used only with Adams
Solver (C++).
j_flex An Existing Specifies the name of the other flexible body participating in
Flexible Body the contact. This parameter can only exist if the I_flex
parameter is specified and used with Adams Solver (C++).
contact modify

i_edge An Existing Specifies the name of the edge on the first flexible body
edge on participating in the contact. This parameter should be used
Flexible Body only with Adams Solver C++.
j_edge An Existing Specifies the name of the edge on the other flexible body
edge on participating in the contact. This parameter can only exist if
Flexible Body the i_edge parameter is specified and used with Adams Solver
C++.
i_edge_index An Existing Specifies edge index of the first edge participating in the
edge index contact. This parameter can only exist if the i_edge parameter
j_edge_index An Existing Specifies the edge index of the other edge participating in the
edge index contact. This parameter can only exist if the j_edge parameter
i_flip_normal String Boolean value, specifying whether the normal is to be flipped
j_flip_normal String Boolean value, specifying whether the normal is to be flipped
i_flip_geometry_name Existing Specifies the geometry name at which the contact should be
Contact_curve flipped on the I body.
j_flip_geometry_name Existing Specifies the geometry name at which the contact should be
Contact_curve flipped on the J body.
face_contact_bottom True/False Specific to cylinder-to-cylinder contacts where one of the
i/j_flip_normal = yes). “Bottom” face is defined as the one on
which the cylinder geometry’s reference marker is located. If
set to “true” then this face will enforce contact.
face_contact_top True/False Specific to cylinder-to-cylinder contacts where one of the
i/j_flip_normal = yes). “Top” face is defined as the one on
which the cylinder geometry’s reference marker is NOT
located. If set to “true” then this face will enforce contact.
geometry_routines String Takes a string value
stiffness Real Specifies a material stiffness that you can use to calculate the
normal force for the impact model.
damping Real Used when you specify the IMPACT model for calculating
normal forces. DAMPING defines the damping properties of
the contacting material. You should set the damping
coefficient to about one percent of the stiffness coefficient.
Range: DAMPING >0
contact 13
contact modify

dmax Real Used when you specify the IMPACT model for calculating
normal forces.
Range: DMAX > 0
exponent Real Used when you specify the IMPACT model for calculating
normal forces.
Range: EXPONENT >1
penalty Real Used when you specify a restitution model for calculating
normal forces. PENALTY defines the local stiffness properties
between the contacting material.
restitution_coefficient Real The coefficient of restitution models the energy loss during
contact. This field is not available when I_flex and J_flex
parameters are specified. Range: 0 <
RESTITUTION_COEFFICIENT < 1
normal_function Real Specifies up to thirty user-defined constants to compute the
contact normal force components in a user-defined subroutine
normal_routine String Specifies a library and a user-written subroutine in that library
that calculates the contact normal force.
augmented_lagrangian_ Boolean Refines the normal force between two sets of rigid geometries
formulation that are in contact.
coulomb_friction Real Models friction effects at the contact locations using the
Coulomb friction model to compute the frictional forces.
mu_static Real Specifies the coefficient of friction at a contact point when the
slip velocity is smaller than the
STICTION_TRANSITION_VELOCITY. Range:
MU_STATIC > 0
mu_dynamic Real Specifies the coefficient of friction at a contact point when the
slip velocity is larger than the
FRICTION_TRANSITION_VELOCITY. Range:0 <
MU_DYNAMIC < MU_STATIC
friction_transition_velo Real Used in the COULOMB_FRICTION model for calculating
city frictional forces at the contact locations. Range:
FRICTION_TRANSITION_VELOCITY >
STICTION_TRANSITION_VELOCITY > 0
friction_function Real Specifies up to thirty user-defined constants to compute the
contact friction force components in a user-defined
subroutine
contact modify

friction_routine String Specifies a library and a user-written subroutine in that library
that calculates the contact friction force.
no_friction True Will take Boolean values of true or false, based on whether
friction is present or not.
stiction_transition_velo Real Used in the COULOMB_FRICTION model for calculating
city frictional forces at the contact locations. Range: 0 <
STICTION_TRANSITION_VELOCITY <
FRICTION_TRANSITION_VELOCITY
1. For solids and curves, you can select more than one geometry as long as the geometry belongs to the
same part.
2. For sphere-to-sphere and cylinder-to cylinder contacts, you can specify whether the contact should
be inside or outside the sphere or cylinder.
3. In general, the higher the stiffness, the more rigid or hard are the bodies in contact. Also note that the
higher the stiffness, the harder it is for an integrator to solve through the contact event.
4. Parameter dmax defines the penetration at which Adams Solver turns on full damping. Adams Solver
uses a cubic STEP function to increase the damping coefficient from zero, at zero penetration, to full
damping when the penetration is dmax. A reasonable value for this parameter is 0.01 mm. For more
information, refer to the IMPACT function.
5. Adams Solver (FORTRAN) models normal force as a nonlinear spring-damper. If PEN is the
instantaneous penetration between the contacting geometry, Adams Solver calculates the
contribution of the material stiffness to the instantaneous normal forces as STIFFNESS *
(PENALTY)**EXPONENT. For more information, see the IMPACT function. Exponent should
normally be set to 1.5 or higher.
6. A large value of PENALTY ensures that the penetration, of one geometry into another, will be small.
Large values, however, will cause numerical integration difficulties. A value of 1E6 is appropriate for
systems modeled in Kg-mm-sec. For more information on how to specify this value, see Extended
Definition. Range: PENALTY > 0
7. A value of zero for the restitution_coefficient specifies a perfectly plastic contact between the two
colliding bodies. A value of one specifies a perfectly elastic contact. There is no energy loss. The
coefficient of restitution is a function of the two materials that are coming into contact. For
information on material types versus commonly used values of the coefficient of restitution, see the
Material Contact Properties table.
8. The augmented_lagrangian_formulation parameter uses iterative refinement to ensure that
penetration between the geometries is minimal. It also ensures that the normal force magnitude is
relatively insensitive to the penalty or stiffness used to model the local material compliance effects.
You can use this formulation only with the POISSON model for normal force.
9. The friction model in CONTACT models dynamic friction but not stiction. The argument values,
on/off/dynamics_only, specify at run time whether the friction effects are to be included.
contact 15
contact modify
10. For information on material types versus commonly used values of the coefficient of static friction,
see the Material Contact Properties table. Excessively large values of mu_static can cause integration
difficulties.
11. For information on material types versus commonly used values of the coefficient of the dynamic
coefficient of friction, see the Material Contact Properties table. Excessively large values of mu_dynamic
can cause integration difficulties.
12. Adams Solver gradually transitions the coefficient of friction from mu_static to mu_dynamic as the
slip velocity at the contact point increases. When the slip velocity is equal to the value specified for
friction_transition_velocity, the effective coefficient of friction is set to mu_dynamic. For more
details, see Extended Definition.
13. Specifying i_flex and j_flex parameters for Adams Solver (FORTRAN) will result in a warning
message that the created contact is no longer compatible with the solver.
14. i_edge and j_edge are the matrices consisting of the nodes of the free edges identified by the edge
index. You have to first, select a flexible body and then you will be asked to pick one of the free edges
generated (more than one free edge can exists) on the flexible body.
15. edge_index is an optional parameter. If you do not specify, it will be calculated internally.
16. If contact_type "solid-to-solid" is specified and the geometry supplied is capable of analytical contact
detection then Adams will automatically treat them analytically. See the Adams Solver CONTACT
statement documentation for details on which types of geometry are treated analytically.
17. Solid-to-solid contact is limited to external contact surfaces. So, to take advantage of analytical
contact detection for sphere or cylinder geometry and use an internal surface for contact one must
specify type = sphere_to_sphere or cylinder_to_cylinder.
Tips:
1. Small values for FRICTION_TRANSITION_VELOCITY cause difficulties for the integrator . You
should specify this value as:
FRICTION_TRANSITION_VELOCITY > 5 * ERROR
where ERROR is the integration error used for the solution. Its default value is 1E-3.
contact modify
continue 1
continue
Allows you to skip commands inside the innermost FOR or WHILE loop and continue with the next
iteration of the loop.
When Adams View encounters a CONTINUE command inside a loop, it skips over the remaining
commands of the loop and goes directly to the END of the innermost loop. Adams View tests the loop
condition and continues looping if the condition is still valid.
The CONTINUE command affects only the innermost FOR or WHILE loop.
Format:
CONTINUE
Example:
while condition=(ip < 5)
variable modify variable_name=ip integer_value=(eval(ip+1))
if condition=(ip == 3)
continue
end
marker create marker_name=(eval("MAR"//ip)) &
location=(eval(ip-1)),0,0
end
In this example, Adams View creates four markers on the default part: MAR1, MAR2, MAR4, and MAR5.
Adams View skips MAR3, because when IP evaluates to 3, Adams View encounters the CONTINUE
command and skips to the END of the WHILE loop.
Results of CONTINUE Example
Name Loc_X Loc_Y Loc_Z

MAR1 0.0 0.0 0.0
MAR2 1.0 0.0 0.0
MAR4 3.0 0.0 0.0
MAR5 4.0 0.0 0.0
contour_plot legend 1
contour_plot legend create
contour_plot legend
Allows you to create a legend in the animation dashboard for a contoured plot of deformation, stress/strain
or modal forces while in Adams Flex, Adams Vibration or Adams Durability.
The dashboard in animation mode lets you play and control time and frequency_domain animations, record
them, and view contour and vector plots.
Depending on the Adams product you use to create and simulate your model, you display different types of
data as contour or vector plots: deformations, stress/strain, or modal forces. Contour plots display scalar data
a component at a time, such as a stress. You can select to animate the deformations, modal forces
(MFORCEs), or the stresses and strain acting on the flexible body as contour plots to better visualize a result
that is defined by its position on a body.
For example, when you analyze flexible bodies using Adams Flex, you can contour deformations using Adams
View or Adams PostProcessor.
In the Animation Dashboard - Contour Plots setting, you can set up the options for displaying contour_plots.
For each viewport, you can change the way contour plots display colors and values. Note that this allows you
to display different viewports at the same time but with different color values, which can be confusing because
a color value in one viewport may not be the same as in another.
Format:
legend_name = a new contour_plot legend
title = string
placement = placement_option
minimum_value = real
maximum_value = real
gradients = integer
colors = integer
visibility = on_off
scientific_notation = sci_notation
trailing_zeros = boolean
decimal_places = integer
Example:
contour_plot legend create &
legend_name = contour_legend__1 &
title = this_is_title &
placement = bottom &
minimum_value = 0.1 &
maximum_value = 10 &
gradients = 10 &
colors = 255 &
visibility = on &
scientific_notation = 10 , 10 &
trailing_zeros = on &
decimal_places = 2
Description:

legend_name A New Contour_plot Legend Specifies the name of a new contour_plot legend
animation_name An Existing Animation Specifies an existing animation
title String Specifies title for the legend
placement Placement_options Specifies the placement location of the legend
minimum_value Real Specifies the minimum value of the legend
maximum_value Real Specifies the maximum value of the legend
gradient Integer Specifies the number of gradients for the legend
to be split
colors Integer Specifies the number of colors used to display
legend contours
visibility On_off Specifies the default visibility of the legend
scientific_notation Sci_notation Specifies the exponential form of scientific
notation
trailing_zeros On_off Sets the default status for displaying trailing zeros
decimal_places Integer Specifies the number of decimal places to display
legend numbers
contour_plot legend delete
1. The title name to appear on the top of the legend can be specified by ‘title’. The existing animation
for which the contoured plot is to be shown is entered as ‘animation_name’. The legend_name should
be specified for creating a new legend.
2. The placement of the legend on the animation window can be on the left, right, top, or bottom,
specified by the parameter, ‘placement’.
3. Specify the minimum and maximum numbers for the legend range to be shown.
4. Similarly, the legend can be split into gradients where the number of gradients can be more than two
and less than or equal to 255. The number of colors used to show the contour can be chosen by the
parameter, ‘color’, which cannot be more than 255.
5. The default visibility of the legend bar is set to ON or OFF by the parameter ‘visibility’.
6. The scientific notation specifies the exponential form for scientific notation.
7. Adams PostProcessor display zeros after the numbers in the legend, if the ‘trailing_zeros’ is set to ‘yes’.
The number of zeros depends on the number of decimal points you selected for ‘decimal_places’.

Allows you to delete a legend in the animation dashboard for a contoured plot of deformation, stress/strain
This command deletes an existing contour_plot legend.
Format:
legend_name = an exisitng contour_plot legend
Example:
contour_plot legend delete &
legend_name = contour_legend__1
Description:

legend_name An Existing Contour_plot Specifies the name of an existing
Legend contour_plot legend
This command deletes an existing contour_plot legend.
contour_plot legend modify

Allows you to modify a legend in the animation dashboard for a contoured plot of deformation, stress/strain
them, and view contour and vector plots.
Depending on the Adams product you use to create and simulate your model, you display different types of
data as contour or vector plots: deformations, stress/strain, or modal forces. Contour plots display scalar data,
one component at a time, such as a stress. You can select to animate the deformations, modal forces
(MFORCEs), or the stresses and strain acting on the flexible body as contour plots to better visualize a result
that is defined by its position on a body.
View or Adams PostProcessor.
In the Animation Dashboard - Contour Plots setting, you can set up the options for displaying contour_plots.
For each viewport, you can change the way contour plots display colors and values. Note that this allows you
to display different viewports at the same time but with different color values, which can be confusing because
a color value in one viewport may not be the same as in another.
Format:
new_legend_name = a new contour_plot legend
title = string
placement = placement_option
minimum_value = real
maximum_value = real
gradients = integer
colors = integer
visibility = on_off
scientific_notation = sci_notation
trailing_zeros = boolean
Example:
contour_plot legend modify &
legend_name = contour_legend__1 &
new_legend_name = modified_legend &
title = new_legend &
contour_plot legend modify &

placement = right &
minimum_value = 0 &
minimum_value = 2.5 &
gradients = 5 &
colors = 10 &
visibility = on &
scientific_notation = 1,2 &
decimal_places = 2
Description:

legend_name An Existing Contour_plot Legend Specifies the name of an existing
contour_plot legend
new_legend_name A New Contour_plot Legend Specifies a new name for the contour plot
legend
title String Specifies title for the legend
placement Placement_options Specifies the placement location of the
legend
minimum_value Real Specifies the minimum value of the legend
maximum_value Real Specifies the maximum value of the legend
gradient Integer Specifies the number of gradients for the
legend to be split
colors Integer Specifies the number of colors used to display
legend contours
visibility On_off Specifies the default visibility of the legend
scientific_notation Sci_notation Specifies the exponential form of scientific
notation
trailing_zeros On_off Sets the default status for displaying trailing
zeros
decimal_places Integer Specifies the number of decimal places to
display legend numbers
contour_plot legend reset
1. The title name to appear on the top of the legend can be specified by ‘title’. The ‘new_legend_name’,
if specified, replaces the existing legend name.
2. The placement of the legend on the animation window can be on the left, right, top, or bottom,
specified by the parameter, ‘placement’.
3. Specify the minimum and maximum numbers for the legend range to be shown.
4. Similarly, the legend can be split into gradients where the number of gradients can be more than two
and les than or equal to 255. The number of colors used to show the contour can be chosen by
parameter, ‘color’, which cannot be more than 255.
5. The default visibility of the legend bar is set to ON or OFF by the parameter, ‘visibility’.
6. The scientific notation specifies the the exponential form for scientific notation.
7. Adams PostProcessor displays zeros after the numbers in the legend, if the ‘trailing_zeros’ is set to
‘yes’. The number of zeros depends on the number of decimal points you selected for
‘decimal_places’.

Allows you to modify a legend in the animation dashboard for a contoured plot of deformation, stress/strain
This command reset the legend values based on the flexible bodies in the active view.
them, and view contour and vector plots. Depending on the MSC ADAMS product you use to create and
simulate your model, you display different types of data as contour or vector plots: deformations, stress/strain,
or modal forces. Contour plots display scalar data a component at a time, such as a stress. You can select to
animate the deformations, modal forces (MFORCEs), or the stresses and strain acting on the flexible body
as contour plots to better visualize a result that is defined by its position on a body.
View or Adams PostProcessor. In the Animation Dashboard - Contour Plots setting, you can set up the
options for displaying contour_plots. For each viewport, you can change the way contour plots display colors
and values. Note that this allows you to display different viewports at the same time but with different color
values, which can be confusing because a color value in one viewport may not be the same as in another.
Format:
Example:
contour_plot legend reset &
legend_name = contour_legend__1
Description:

legend_name An Existing Contour_plot Legend Specifies the name of an existing contour_plot
legend
This command resets the legend values based on the flexible bodies in the active view.
data_element 1
data_element attributes
data_element
Allows the specification of attributes to be set on an individual data_elements or a group of data_elements.
Format:
data_element_name = an existing var
visibility = on_off_with_toggle
color = an existing color
active = on_off_no_opinion
dependents_active = on_off_no_opinion
Example:
data_element attributes &
data_element_name = shaft_genstiff &
visibility = on &
color = blue &
active = on &
dependents_active = on
Description:

data_element_name An Existing Var Specifies an existing data_element.
visibility On_off_with_toggle Specifies the visibility of graphic entities.
color An Existing Color Specifies the color the modeling entity should be drawn
in.
active On_off_no_opinion Set the activation of the element
dependents_active On_off_no_opinion Set the activation of the dependants of an element
1. You can set the following attributes on a data_element.
VISIBILITY. You may set a data_element's visibility ON, OFF or TOGGLE the current setting.
When you set a data_element's visibility OFF, the data_element will not be drawn.
When you set a data_element's visibility ON, you allow that data_element to be drawn.
COLOR. You may set the color of a data_element with this parameter.
ATTRIBUTE may be inherited from another entity. INHERITANCE may be either TOP_DOWN
or BOTTOM_UP.
2. BOTTOM_UP and TOP_DOWN refer to the natural hierarchy of the Adams model. The hierarchy
3. You may identify a data_element by typing its name or by picking it from the screen.
Since data_element do not have a geometric position, Adams View displays data_element icons at or
near the model origin. If the data_element icon is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the data_element icon is displayed.
You must separate multiple data_element names by commas.
If the data_element is visible in one of your views, you may identify it by picking on any of the
You need not separate multiple data_element picks by commas.
are to be drawn in an Adams View viewport.The legal values for this parameter are: ON, OFF, and
Example 1:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3:
.model -------------------------NO_COLOR
data_element 3
data_element copy
.part ---------------------- NO_COLOR

6. When you set ACTIVE=NO, that element is written to the data set as a comment. When you set the
ACTIVE attribute on an object, you are also setting it on the children of the object. If you set
ACTIVE=NO on a part, but wish for a marker on that part to be on, then you must explicitly set
ACTIVE=YES on the marker, after setting activation on the part.
command:
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
data_element copy
Allows you to create a replica DATA_ELEMENT within the same model.
Format:
data_element copy
data_element_name = an existing data_element
new_data_element_name = a new data_element
data_element copy
Example:
data_element copy &
data_element_name = string__1 &
new_ data_element_name = string__2
Description:

new_data_element_name A New Var Specifies the name of the new data_element. You may
use this name later to refer to this data_element.
1. The replica DATA_ELEMENT will be identical to the original with the exception of the
DATA_ELEMENT name. DATA_ELEMENTs must have unique names relative to other
DATA_ELEMENTs in a given model. The replica will be completely independent of the original,
and may be modified without effecting the original.
2. Since data_element do not have a geometric position, Adams View displays data_element icons at or
be assigned to it.
Tips:
data_element 5
data_element create array general_array
2. If the data_element is visible in one of your views, you may identify it by picking on any of the
3. You need not separate multiple data_element picks by commas.

Allows you to create a general_array. Creates a one-dimensional array of real numbers that can be accessed in
user-written subroutines. This array is identical in definition to the IC_ARRAY. The GENERAL_ARRAY
has been provided to maintain consistency with the ARRAY available in Adams version 5.2.1.
Format:
array_name = array_name
adams_id = integer
comments = string
size = integer
numbers = real
Example:
data_element create array general_array &
array_name = .model_1.array_1 &
adams_id = 1 &
size = 3 &
numbers = 2.1,3.4,5
Description:

array_name, Array name Specifies the name of the new array. You may use this name later to
refer to this array.
adams_id Integer Specifies an integer used to identify this element in the Adams data
file.
Size Integer Specifies the size of an array.
numbers Real Allows you to enter a one dimensional array of real numbers when
using the IC_ARRAY of the GENERAL_ARRAY. The number of
entries should match the value of the SIZE parameter.
1. Adams View will not allow you to have two arrays with the same full name, so you must provide a
unique name.
be assigned to it.
yourself.
3. In cases where Adams calculates the SIZE differently from the SIZE that the user supplies, Adams
returns an error or warning message.
For the X_STATE_ARRAYs and Y_OUTPUT_ARRAYs, the corresponding systems modeling
element automatically determines the size of the array and checks it against the ARRAY command
SIZE parameter value (if given).
For the IC_ARRAY, the SIZE parameter is optional and Adams determines the actual size of the array
during parsing, as it counts the NUMBERS values. However, if you provide a value for SIZE , Adams
checks the count for consistency.
The SIZE argument, if used, should match the number of entries in the VARIABLE_NAME
parameter, the NUMBERS parameters, or the size needed for the associated systems element. Adams
View provides the SIZE parameter mainly for user convenience in model creation (it is not required).
For LINEAR_STATE_EQUATION arrays, the X_STATE_ARRAY size is the row dimension of the
data_element 7
data_element create array ic_array
A_STATE_MATRIX, and the Y_OUTPUT_ARRAY size is the row dimension of the

C_OUTPUT_MATRIX or the D_FEEDFORWARD_MATRIX. For TRANSFER_FUNCTION
arrays, the transformation from polynomial ratio type to canonical state space type internally
determines the X_STATE_ARRAY size; the Y_OUTPUT_ARRAY size is always 1. For
GENERAL_STATE_EQUATION arrays, the X_STATE_ARRAY size is the
STATE_EQUATION_COUNT as defined in the matching GENERAL_STATE_EQUATION
definition and Y_OUTPUT_ARRAY size is the OUTPUT_EQUATION_COUNT, as defined in
the same GENERAL_STATE_EQUATION definition.

Allows you to create an ic_array. This element creates a one-dimensional array of real numbers that can be
accessed in user-written subroutines. You can use an IC_ARRAY to designate define initial conditions array
for an LINEAR_STATE_EQUATION or GENERAL_STATE_EQUATION. In that case, you should
ensure that the value of the SIZE parameters the same as the X_STATE_ARRAY (state variable) of the
associated LINEAR_STATE_EQUATION or GENERAL_STATE_EQUATION.
Format:
adams_id = integer
comments = string
size = integer
numbers = real
Example:
data_element create array ic_array &
adams_id = 1 &
size = 3 &
numbers = 2.1,3.4,5
Description:

array_name, Array name Specifies the name of the new array. You may use this name later to refer
to this array.
adams_id Integer Specifies an integer used to identify this element in the Adams data file.

numbers Real Allows you to enter a one dimensional array of real numbers when using
the IC_ARRAY of the GENERAL_ARRAY. The number of entries
should match the value of the SIZE parameter.
unique name.
be assigned to it.
data file for your model. Adams requires that each modeling element be identified by a unique
integer identifier. If you use this parameter to specify a non-zero identifier, Adams View will use it
in the corresponding statement in the Adams data file.
data_element 9
data_element create array u_input_array

Allows you to create a u_input_array.
Format:
array_name = a new array
adams_id = adams_id
comments = string
size = integer
variable_name = an existing variable
Example:
data_element create array u_input_array &
array_name = array__2 &
adams_id = 2 &
comments = " a new u_input array" &
size = 1 &
variable_name = variable_1
Description:

array_name A New Array Specifies the name of the new array. You may use this name later
to refer to this array.
data file.
size Integer Specifies the size of an array. In cases where Adams calculates the
SIZE differently from the SIZE that the user supplies, Adams
variable_name An Existing Variable Specifies an existing variable.
1. The U_INPUT_ARRAY command groups together a set of VARIABLE_NAMEs, normally to
define the inputs for a systems element, either LINEAR_STATE_EQUATION,
GENERAL_STATE_EQUATION , or TRANSFER_FUNCTION. When the you create a
U_INPUT_ARRAY, SIZE and VARIABLE_NAME are the only parameters available.
unique name.
be assigned to it.
data_element 11
stored with the object. Comments in the data file can be associated with model.
These comments must follow the title statement and be followed by the comment 'END OF
MODEL COMMENTS'. This string must be uppercase.
When an Adams Solver data file is written, the comments for an object are written before the
statement corresponding to the object.
5. For the X_STATE_ARRAYs and Y_OUTPUT_ARRAYs, the corresponding systems modeling
6. You enter variable names as input parameters for array elements (U_INPUT_ARRAY), plant input
and output definitions, and in function expressions. You may identify a variable by typing its name
or by picking it from the screen.
Since variable do not have a geometric position, Adams View displays variable icons at or near the
model origin. If the variable icon is not visible on the screen, you must type the name. You may also
find it convenient to type the name even if the variable icon is displayed.
If you created the variable by reading an Adams data set, the variable name is the letters VAR followed
by the Adams data set variable ID number. The name of Adams VARIABLE/101 is VAR101, for
example. If you created the variable during preprocessing, you gave it a name at that time.
data_element create array x_state_array
If a variable is owned by the default model, you may identify it by entering its name only. If it is not,
you must enter its full name. To identify a variable under a different model, for instance, you may
need to enter the model name as well. For example, you may specify variable 'fluid_volume' from
model 'hydro' by entering ".hydro.fluid_volume'". If you type a "?", Adams View will list the variable
available by default.
You must separate multiple variable names by commas.
Tips:
1. If the variable is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple variable picks by commas.

Allows you to create an x_state_array.
Format:
adams_id = adams_id
comments = string
size = integer
Example:
data_element create array x_state_array &
adams_id = 1 &
comments = "a new x-state array" &
size = 4
Description:

array_name A New Array Specifies the name of the new array. You may use this name later
data_element 13

data file.
1. An X_STATE_ARRAY defines a list of state variables (X) associated with system modeling elements
such as GSE, LSE, and TFSISO. To use this array, you must reference the array name as the state
variable array in a system element definition. You can use each X_STATE_ARRAY with only one
systems element in your model. When you define an X_STATE_ARRAY, the only other parameter
is SIZE. When you do not specify SIZE, the associated systems element automatically sets the size.
unique name.
be assigned to it.
3. When you use the FILE ADAMS_DATA_SET WRITE command, Adams View
writes an Adams data file for your model. Adams requires that each modeling element be identified
by a unique integer identifier. If you use this parameter to specify a non-zero identifier, Adams View
will use it in the corresponding statement in the Adams data file.
data_element create array y_output_array
during parsing, as it counts the NUMBERS values. However, if you provide a value for SIZE, Adams

Allows you to create a y_output_array.
Format:
adams_id = adams_id
comments = string
size = integer
data_element 15
Example:
data_element create array y_output_array &
adams_id = 2 &
comments = "a new y_output_array" &
size = 1
Description:

array_name A New Array Specifies the name of the new array. You may use this name later to refer
to this array.
adams_id Adams_id Specifies an integer used to identify this element in the Adams data file.
size Integer Specifies the size of an array. In cases where Adams calculates the SIZE
differently from the SIZE that the user supplies, Adams returns an error
or warning message.
1. A Y_OUTPUT_ARRAY specifies the output array for a systems element, either a
LINEAR_STATE_EQUATION, GENERAL_STATE_EQUATION, or
TRANSFER_FUNCTION. To use these arrays, the user must reference the array name as the output
array in the system element definition in the model. When you create a Y_OUTPUT_ARRAY, SIZE
is the only other parameter available. You can use each Y_OUTPUT_ARRAY with only a single
systems element. The SIZE value, if supplied, must be consistent with the associated systems element.
When you do not specify SIZE , the associated systems element automatically sets it.
unique name.
data_element create curve
be assigned to it.
during parsing, as it counts the NUMBERS values. However, if you provide a value for SIZE, Adams

Allows you to create a curve.
data_element 17
Format:
curve_name = a new acurve
adams_id = adams_id
comments = string
closed = boolean
matrix_name = an existing matrix
fit_type = fit_type
segment_count = integer
minimum_parameter = real
maximum_parameter = real
Example:
data_element create curve &
curve_name = curve__1 &
adams_id = 1 &
comments = "a new curve" &
closed = yes &
matrix_name = biele_selnod &
fit_type = curve_points &
segment_count = 10
Description:

curve_name A New Acurve Specifies the name of the new curve. You may use this
name later to refer to this curve.
Adams data file.
modified.
closed Boolean Specifies if the curve meets at the ends.
matrix_name An Existing Matrix Specifies the name of an existing MATRIX containing the
data for the curve.

fit_type Fit_type Specifies the way the curve is to be fit through the points
contained in the MATRIX.
segment_count Integer Specifies the number of polynomial segments Adams uses
for fitting the curve points when FIT_TYPE is set to
CURVE_POINTS.
written subroutine.
minimum_parameter Real Specifies the minimum value of the curve parameter only
for a user-written curve.
maximum_parameter Real Specifies the maximum value of the curve parameter only
1. A CURVE element defines a three-dimensional parametric curve that may be referenced by
POINT_CURVE or CURVE_CURVE constraints, a geometry element called a BSPLINE, as well
as by FUNCTION expressions.
The x, y, and z coordinates of a point on a parametric curve are functions of an independent
parameter, u. As u varies from its minimum value to its maximum value, the functions x(u), y(u),
and z(u) sweep out points on the curve. A simple example of a parametric curve is the helix defined
by the following equations:
x = cos(u)
y = sin(u)
z = u
2. Adams View allows you to create curves in three ways: by entering control points for a uniform cubic
B-spline (FIT_TYPE=CONTROL_POINTS), by entering curve points that Adams will fit a curve
to (FIT_TYPE=CURVE_POINTS), or by writing a CURSUB evaluation subroutine to compute the
curve coordinates and derivatives.
3. A uniform B-spline is a piecewise cubic polynomial spline used in many CAD (computer-aided-
design) applications. A uniform B-spline is defined by control points which form a polygon in space.
The curve starts at the first control point and ends at the last. In between, it is attracted to, but does
not necessarily hit the intermediate control points. Adams parameterizes a B-spline starting at -1 and
ending at +1.
Generally, you will not create control points directly, but will construct the curve in another
application, such as a CAD program, and then transfer the control points to Adams.
4. A more direct way to define the curve is to supply curve points.
Adams will compute a uniform B-spline that will fit the curve points.
data_element 19
Again, Adams parameterizes the curve from -1 to +1. If you specify the number of spline segments
(SEGMENT_COUNT) as three less than the number of curve points, the computed curve will
exactly match the curve points. If you specify fewer segments, Adams will use a least-squares fit to
compute the closest fit to the points. In general, fewer segments give a smoother curve, but do not
come as close to the data points.
5. In order to use a different type of curve, or to model an analytically-defined curve such as the helix,
you may write a CURSUB evaluation subroutine. When providing a CURSUB, you may also specify
MINPAR and MAXPAR to define the limits of the curve. These default to -1 and +1, respectively.
A curve can be open or closed. A CLOSED curve meets at the ends, connecting the curve at minimum
and maximum parameter values. Note for a closed curve defined by curve points, you can specify a
maximum of 5 segments less that the number of curve points. Note that because three segments less
than the number of curve points are required for an exact fit, a closed curve will not exactly fit the
curve points.
Adams will automatically move a POINT_CURVE or CURVE_CURVE contact point across the
closure of a CLOSED curve, if needed. For instance, you may model a cam profile as a CLOSED
curve, and Adams will allow the follower to move across the closure as the cam rotates.
Adams will stop the simulation if a POINT_CURVE or CURVE_CURVE contact point moves off
the end of curve. You should ensure that the curve defined includes the expected range of contact.
be assigned to it.
yourself.
9. If you set the parameter CLOSED to YES and you use the CURVE_POINTS FIT_TYPE,
AdamsAdams will attempt to compute a curve that meets at the ends and has continuous first and
second derivatives across the closure. If you set CLOSED to YES and use the CONTROL_POINTS
FIT_TYPE or a user-defined FUNCTION is specified, you must ensure that the defined curve meets
at the ends and has continuous first and second derivatives across the closure. During a simulation,
Adams will move a POINT_CURVE or CURVE_CURVE contact point across the closure, if
necessary. Any discontinuity could cause integration failure.
By setting CLOSED to NO, you specify that the curve does not meet at the ends. Adams will not
allow a POINT_CURVE or CURVE_CURVE contact point to move beyond the end of the curve.
10. If CONTROL_POINTS is specified, the matrix contains the x, y, and z coordinates of control
points for a uniform B-spline. (Adams uses a uniform knot vector with quadruple multiplicity at both
ends, ensuring that the curve will pass through starting and ending points.)
If CURVE_POINTS is specified, the matrix contains the x, y, and z coordinates of curve points
which the curve will pass through or near.
The matrix should have a row for each point and three columns containing the x, y, and z, coordinates
of the points. You must supply at least four control points or curve points.
You may identify a matrix by typing its name or by picking it from the screen.
Since a matrix does not have a geometric position, Adams View displays matrix icons at or near the
model origin. If the convenient to type the name even if the matrix icon is displayed.
If you created the matrix by reading an Adams data set or graphics file, the matrix name is the letters
MAT followed by the Adams data set matrix ID number. The name of Adams MATRIX/101 is
MAT101, for example. If you created the matrix during preprocessing, you gave it a name at that
time.
If a matrix is owned by the default model, you may identify it by entering its name only. If it is not,
To identify a matrix under a different model, for instance, you may need to enter the model name as
well. For example, you may specify matrix 'control_points' from model 'road_surface' by entering
".road_surface.control_points'". If you type a "?", Adams View will list the matrix available by
default.
You must separate multiple matrix names by commas.
data_element 21
data_element create matrix file
11. If FIT_TYPE=CONTROL_POINTS then the MATRIX contains control points to will not
necessarily pass through the points). Specifically, the matrix contains the x, y, and z coordinates of
control points for a uniform B-spline. (Adams uses a uniform knot vector with quadruple multiplicity
at both ends, ensuring that the curve will pass through starting and ending points.)
If FIT_TYPE=CURVE_POINTS then the MATRIX contains data points on the curve and the curve
will be fit directly through the points (depending on the value of the SEGMENT_COUNT
parameter). Specifically, the matrix contains the x, y, and z coordinates of curve points which the
curve will pass through or near. The matrix should have a row for each point and three columns
containing the x, y, and z, coordinates of the points. You must supply at least four control points or
curve points.
12. Adams will default the segment_count to three segments less than the number of curve points, which
gives an exact fit to the curve points. Specifying fewer segments will result in a smoother curve, but
the curve will not pass exactly through the curve points.
More specifically, if you specify the SEGMENT_COUNT such that the spline segments is three less
than the number of curve points, the computed curve will exactly match the curve points. If you
specify fewer segments, Adams will use a least-squares fit to compute the closest fit to the points. In
general, fewer segments give a smoother curve, but do not come as close to the data points.
13. Adams uses the minimum_parameter value when drawing a curve graphic. For curves defined by
control points or curve points, the minimum parameter value is always -1.0.
Adams uses the maximum_parameter value when drawing a curve graphic. For curves defined by
control points or curve points, the maximum parameter value is always 1.0.
Cautions:
1. Adams View will not allow you to have two curves with the same full name, so you must provide a
unique name.
Tips:
1. If the matrix is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple matrix picks by commas.

Allows you to direct Adams to read a MATRIX definition from a file.
The FILE keyword allows you to read large matrices into Adams using an external file. There is no limit on
the size of an array read from a file.
The first record in the file contains an 80 character header of which the first seven or eight characters are
meaningful. If the first record begins with the characters ADAMSMAT, then the file is assumedto be in a
format used by Adams. If the first record begins with the characters MATRIXx, then the file is assumed to be
in the FSAVE format of the MATRIXx software package. If the first record begins with the characters
MATSAVE, then the file is assumed to be in the MATSAVE format of the MATRIXx software package.
No other kinds of files are currently supported. However, the ADAMSMAT option is fairly general since the
format for reading in the data is specified within the file. See the section in the Adams Reference Manual on
the MATRIX statement for a description of the file format.
Format:
matrix_name = new matrix
adams_id = integer
comments = string
file_name = string
name_of_matrix_in_file = string
units = string
Example:
data_element create matrix file &
matrix_name = matrix_read_from_file &
adams_id = 12 &
comments = ”example of a matrix read from a file” &
file_name = /home/staff/demo/prob.dat &
name_of_matrix_in_file = “trf” &
units = string
In the above command, the prob.dat is in the directory, /home/staff/demo, and contains the following data:
1 2 3 4 5 6 7 8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
ADAMSMAT Floating platform example
3
TRF VALK STL
TRF FULL RORDER 4 2 8 ( 8F8.5 )
1.36400 0.00000 0.00000 0.00000 -3.54600 4.00800 0.00000 0.79900
VALK FULL CORDER 3 3 9 ( 3F6.3 )
1.970 0.000-3.440
0.000 4.510 6.020
-3.440 6.020 2.110
STL SPARSE 6 1 4 ( 2( 2I5, E14.6 ) )
1 1 0.169805E+02 2 1 -0.230745E+02
4 1 0.016390E+00 5 1 0.011271E+00
The second and third records are read with format I5 and 4(A8,10X), respectively. Then, the first record of
each of the blocks corresponding to the three matrices TRF, VALK, and STL is read with the format 3A8,
3I5, A41. Finally, as can be seen in the copy of the file shown above between the two strings of 80 characters
that mark the columns (which, of course, are not part of the file), the single record of data for the matrix TRF
data_element 23
is read with the format 8F8.5; the three records for VALK are read with 3F6.3; and the two records for STL
with 2(2I5,E14.6).
Description:

matrix_name New matrix Specifies the name of the new matrix.
data file.
file_name String Specifies the name of a file that contains the values of the
matrix.
name_of_matrix_in_file String Specifies the name of a MATRIX to be read from the file
identified by the FILE_NAME parameter.
units String Allows you to specify the type of units to be used for this object.
1. You may use this name later to refer to this matrix. Adams View will not allow you to have two
matrices with the same full name, so you must provide a unique name.
name. The default name that AdamsAdams View provides will specify the parentage that it has
assumed.
be assigned to it.
data_element create matrix full
yourself.
3. The FILE argument may be used to read large matrices into Adams. There is no limit on the size of
an array read from a file.
The proper extension is the default but can be overridden by simply supplying a different extension.
The first record in the file contains an 80 character header of which the first seven or eight characters
are meaningful. If the first record begins with the characters ADAMSMAT, then the file is assumed
to be in a format used by Adams. If the first record begins with the characters MATRIXx, then the
file is assumed to be in the FSAVE format of the MATRIXx software package. If the first record
begins with the characters MATSAVE, then the file is assumed to be in the MATSAVE format of the
MATRIXx software package.
Note that the three specifications for the format of the data file are case sensitive. Capital letters and
a lower case x must be used to make a selection.
No other kinds of files are currently supported. However, the ADAMSMAT option is fairly general
since the format for reading in the data is specified within the file. See the section in the Adams
Reference Manual on the MATRIX statement for a description of the file format.
4. All three kinds of files, ADAMSMAT, MATRIXx, and MATSAVE, can contain data for more than
one matrix. The NAME_OF_MATRIX_IN_FILE parameter is used to select a particular matrix
from a file even if the file contains only one MATRIX. You must create additional MATRIX elements
in your Adams View model if multiple matrices are to be read from the same file.

Allows you to create a FULL MATRIX.
The MATRIX to be defined is FULL therefore, the VALUES parameter specifies all of the M times N entries
in the matrix. The sequence of the values depends on the value of the INPUT_ORDER parameter. If
BY_ROW is specified, you enter the values row-by-row. If BY_COLUMN is specified, you enter the values
column-by-column.
Format:
matrix_name = new matrix
adams_id = integer
comments = string
data_element 25

row_count = integer
column_count = integer
values = real
result_set_component_names = existing component
input_order = matrix_input_order
units = string
Example:
If you want to enter the following matrix of values in full format:
data_element create matrix full &

matrix_name = matrix_1 &
comments = "matrix example in full format" &
row_count = 4 &
column_count = 2 &
values = 1.364,0.000,0.000,0.000,-3.546,4.008,0.000,0.7999 &
input_order = by_column
Description:

matrix_name Matrix name Specifies the name of the new matrix. You may
use this name later to refer to this matrix.
comments String Specifies comments for the object being created
or modified.
row_count Integer Specifies the number of rows (M) in the
matrix.Used in the definition of a full matrix.

column_count Integer Specifies the number of columns (N) in the
matrix used in the definition of a full matrix.
values Real Specifies the real number values that you enter to
populate a FULL MATRIX.
result_set_component_names Existing component You can only use a result set component as
matrix values using full format and entering all
the values stored in the result set component.
input_order By_column,by_row Specifies the order the values that you input will
appear in for a FULL MATRIX format (all of
the M by N entries will be specific numeric
values
units String Allows you to specify the type of units to be used
for this object.
1. A data element matrix is a general M x N array that can be a rectangular or square two-dimensional
matrix or a row or column matrix. You can enter the data in:
Full format - You list all the M x N values or specify the results of a simulation (result set
components).
Sparse format - You list the row position, column position, and value for only nonzero entry values.
External file - Enter a file containing a matrix.
If one-third or more of the entries in a matrix are nonzero, we recommend that you use full format
since it takes less time to create. If the matrix is mostly empty and entering each nonzero entry's row
position, column position, and value takes less time than entering all of the values, you should use the
sparse format.
2. Adams View will not allow you to have two matrices with the same full name, so you must provide a
unique name.
over ride the default parent. In most cases, when creating an entity, Adams View will provide a
assumed.
data_element 27
data_element create matrix sparse
be assigned to it.
3. The MATRIX to be defined is FULL therefore, the VALUES parameter specifies all of the M times
N entries in the matrix. The sequence of the values depends on the value of the INPUT_ORDER
parameter. If BY_ROW is specified, you enter the values row-by-row.
If BY_COLUMN is specified, you enter the values column-by-column.
4. A result set is a basic set of state variable data that Adams Solver calculates during a simulation. Adams
Solver outputs the data at each simulation output step. A component of a result set is a time series of
a particular quantity (for example, the x displacement of a part or the y torque in a joint).
5. The input_order parameter can take two values:
a. BY_ROW indicates the values are listed by row in the VALUES parameter (that is, starting with
the first row and proceeding to the second, and so on until the entire matrix is completely
defined).
b. BY_COLUMN indicates the values are listed by column (that is, starting with the first column
and proceeding to the second, and so on).
Default value is BY_COLUMN
6. Since this object can be used in a variety of contexts, Adams View can not determine what type of
units it should have. By telling Adams View what the unit type for this object is Adams View can
perform the proper conversions on the values you specify.

Allows you to create a SPARSE MATRIX.
The MATRIX to be defined is SPARSE therefore, the VALUES parameter specifies only the entries that may
be non zero. That is, all entries in the M by N array not assigned values by the ROW_INDEX,
COLUMN_INDEX, and VALUES parameters are assumed to be equal to zero in ADAMS. Therefore, the
kth entry in the VALUES parameter is assigned to the row identified by the kth entry in ROW_INDEX and
to the column identified by the kth entry in COLUMN_INDEX for k=1,2,...,n.
Format:
matrix_name = New Sparse matrix
adams_id = integer
comments = String
row_index = integer
column_index = integer

values = real
units = String
Example:
data_element create matrix sparse &
matrix_name = MATRIX__1 &
row_index = 2,3 &
column_index = 1,1 &
values = 3.456,4.567
This will create a matrix will looks like the following:

0.000, 0.000 ,0.000
3.456, 0.000, 0.000
4.567, 0.000, 0.000
Description:

matrix_name Matrix_name Specifies the name of the new matrix.
adams_id Integer Specifies an integer used to identify this element in the ADAMS data
file.
row_index Integer Specifies the row position of each of the N entries in the VALUES
parameter for a SPARSE MATRIX.
column_inde Integer Specifies the column position of each of the M entries in the VALUES
x parameter for a SPARSE MATRIX.
Values Real Specifies the real number values that you enter to populate a SPARSE
MATRIX.
units String Allows you to specify the type of units to be used for this object.
unique name.
data_element 29
data_element create plant input
be assigned to it.
COMMENTS'. This string must be uppercase.
3. For each non-zero value in the SPARSE MATRIX each entry for this parameter defines to the
position in the matrix of the corresponding entry in the VALUES parameter. For example, the third
value entered for the ROW_INDEX parameter defines what matrix row the third value entered for
the VALUES parameter is located on.
position in the matrix of the corresponding entry in the VALUES parameter. For example, the forth
value entered for the COLUMN_INDEX parameter defines what matrix column the forth value
entered for the VALUES parameter is located on.
5. The MATRIX to be defined is SPARSE therefore, the VALUES parameter specifies only the entries
that may be non zero. That is, all entries in the M by N array not assigned values by the
ROW_INDEX, COLUMN_INDEX, and VALUES parameters are assumed to be equal to zero in
ADAMS. Therefore, the kth entry in the VALUES parameter is assigned to the row identified by the
kth entry in ROW_INDEX and to the column identified by the kth entry in COLUMN_INDEX
for k=1,2,...,n.

Allows you to create a PLANT INPUT element.
Format:
plant_input_name = a new pinput
adams_id = adams_id
comments = string
Example:
data_element create plant input &
plant_input_name = pinput__1 &
adams_id = 1 &
comments = " a new plant input" &
Description:
:

plant_input_name A New Pinput Specifies the name of the new plant_input. You may use this
name later to refer to this plant_input.
Adams data file.
1. A PLANT INPUT element, along with a PLANT OUTPUT element, is required by the Adams
LINEAR/STATEMAT analysis.
\
Note: This analysis can be requested in Adams View through the use of the
ADAMS_COMMAND_FILE parameter with the analysis SUBMIT command. Use the
"ACF" button on the text editor and select the GENERATE_STATE_MATRIX option. You
will finally use a panel to select the PLANT INPUTs, PLANT OUTPUTs, and the format that
the state matrices should be generated in
data_element 31
A PLANT INPUT defines a set of inputs to the mechanical system and PLANT OUTPUT defines
the set of measured outputs from the system. The LINEAR/STATEMAT analysis linearizes the
system equations to the following form:
{x}= [A] {x} + [B] {u}
{y}= [C] {x} + [D] {u}
where x is the linearized system state, u is the system inputs defined by the PLANT INPUT element,
and y is the system outputs defined by the PLANT OUTPUT element. This form is commonly
referred to as the state space form of the system equations in control theory. Adams outputs the A,
B, C, and D matrices for use in a control-system design or any other linear system analysis software.
When you run an analysis type other than LINEAR/STATEMAT , the PLANT INPUT element acts
only as a pointer to the list of the specified VARIABLEs.
2. Both FUNCTION expressions and user-written subroutines can access the PLANT INPUT
information. FUNCTION expressions access the values by using the internal Adams function
PINVAL(i1 ,i2) where i1 specifies the PLANT INPUT name, and i2 specifies the i2-th VARIABLE
in the PLANT INPUT statement list. Note that i2 is not the name of the VARIABLE.
User-written subroutines call the subroutine SYSFNC to access single elements of the PLANT
INPUT list and call the subroutine SYSARY to access all values for a PLANT INPUT.
be assigned to it.
data_element create plant output
and output definitions, and in function expressions
You may identify a variable by typing its name or by picking it from the screen.
To identify a variable under a different model, for instance, you may need to enter the model name
as well. For example, you may specify variable 'fluid_volume' from model 'hydro' by entering
".hydro.fluid_volume'". If you type a "?", Adams View will list the variable available by default.
Cautions:
1. Adams View will not allow you to have two plant_inputs with the same full name, so you must
Tips:
associated with it.

Allows you to create a PLANT OUTPUT element.
data_element 33
Format:
plant_output_name = a new poutput
adams_id = adams_id
comments = string
Example:
data_element create plant output &
plant_output_name = poutput__1 &
adams_id = 1 &
comments = "a new plant output element" &
Description:
:

plant_output_name A New Poutput Specifies the name of the new plant_output. You may use this
name later to refer to this plant_output.
data file.
variable_name An Existing Specifies an existing variable.
Variable
1. A PLANT OUTPUT element, along with a PLANT INPUT element, is required by the Adams
ADAMS_COMMAND_FILE parameter with the analysis SUBMIT command. Use the
"ACF" button on the text editor and select the GENERATE_STATE_MATRIX option. You
will finally use a panel to select the PLANT INPUTs, PLANT OUTPUTs, and the format that
the state matrices should be generated in
PLANT OUTPUT defines the set of measured outputs from the mechanical system and PLANT
INPUT defines a set of inputs to the mechanical system. The LINEAR command linearizes the
{x}= [A] {x} + [B] {u}
{y}= [C] {x} + [D] {u}
where x is the linearized system state (X_STATE_ARRAY), u is the system inputs defined by the
PLANT INPUT element (U_INPUT_ARRAY), and y is the system outputs defined by the PLANT
OUTPUT element (Y_OUTPUT_ARRAY). This form is commonly referred to as the state space
form of the system equations in control theory. Adams outputs the A, B, C, and D matrices (i.e.
A_STATE_MATRIX, B_INPUT_MATRIX, C_OUTPUT_MATRIX, and
D_FEEDFORWARD_MATRIX) for use in a control-system design or any other linear system
analysis software.
When the user runs an analysis type other than LINEAR , the PLANT OUTPUT element acts only
as a pointer to the list of VARIABLE specified.
2. Both FUNCTION expressions and user-written subroutines can access the PLANT OUTPUT
element. FUNCTION expressions access the values by using the internal Adams function
POUVAL(i1 ,i2) where i1 specifies the PLANT OUTPUT name , and i2 specifies the i2-th
VARIABLE entry in the PLANT INPUT parameter list. Note that i2 is not the name of the
VARIABLE.
User-written subroutines access single elements of the PLANT OUTPUT list and call the subroutine
SYSFNC to access all values for a PLANT OUTPUT by calling the subroutine SYSARY.
be assigned to it.
data_element 35
data_element create plant state
yourself.
for you. You are never required to enter a non-zero identifier. You only need to specify it
if, for some reason, you wish to control the Adams file output.
Cautions:
1. Adams View will not allow you to have two plant_outputs with the same full name, so you must
Tips:
associated with it.

Allows you to create a PLANT STATE element.
Format:
plant_state_name = a new plant state
adams_id = adams_id
comments = string
Example:
data_element create plant state &
plant_state_name = pstate__1 &
adams_id = 1 &
comments = "a new plant state element " &
Description:

plant_state_name A New Plant State Specifies the name of the new plant_state. You may use this
name later to refer to this plant_state.
data file.
Variable
data_element 37
be assigned to it.
yourself.
and output definitions, and in function expressions You may identify a variable by typing its name or
by picking it from the screen.
Cautions:
1. Adams View will not allow you to have two plant_states with the same full name, so you must provide
a unique name.
data_element create spline
Tips:
associated with it.

Allows for creation of the spline object.
Format:
spline_name = a new spline
adams_id = adams_id
comments = string
x_result_set_component_name = an existing component
x = real
y_result_set_component_name = an existing component
y= real
z_result_set_component_name = an existing component
z = real
linear_extrapolate = boolean
x_units = string
y_units = string
z_units = string
file_name = string
Example:
data_element create spline &
spline_name = spline__1 &
adams_id = 2 &
comments = "a new spline" &
linear_extrapolate = yes &
x_units = mm &
y_units = mm &
data_element 39
data_element create spline &

z_units = degree &
file_name = "c:\spline.txt"
Description:

spline_name A New Spline Specifies the name of the new spline. You may use
this name later to refer to this spline.
modified.
x_result_set_component_name An Existing Specifies the result set component containing values
Component for the spline X (independent) variable.
x Real
y_result_set_component_name An Existing Specifies the result set component containing values
Component for the spline Y (dependent) variable.
y Real
z_result_set_component_name An Existing Specifies the result set component containing values
Component for the spline Z (independent) variable.
z Real
linear_extrapolate Boolean
units String Allows you to specify the type of units to be used for
this object.
x_units String Allows you to specify the type of X units to be used
for this object.
y_units String Allows you to specify the type of Y units to be used
for this object.
z_units String Allows you to specify the type of Z units to be used
for this object.
file_name String
1. A spline interpolates between discrete data for a user-provided function or a utility subroutine called
by a user-written subroutine.
You use the spline to provide one or two independent variables and one dependent variable for each
data point you want to enter. Adams uses curve fitting techniques to interpolate between data points
to create a continuous function. If the spline data has one independent variable, Adams uses a cubic
polynomial to interpolate between points.
If the spline data has two independent variables, Adams first uses a cubic interpolation method to
interpolate between points of the first independent variable and then uses a linear method to
interpolate between curves of the second independent variable.
2. To use the discrete data input with a spline, you must write either a function expression that includes
one of the two Adams spline functions (AKISPL function and CUBSPL function) or a user-written
subroutine that calls one of the two spline utility subroutines (AKISPL subroutine and CUBSPL
subroutine).
3. These spline functions and utility subroutines use two different interpolation methods. The AKISPL
function and the AKISPL subroutine use the Akima method of interpolation. The Akima method is
a local cubic curve fitting technique. The CUBSPL function and the CUBSPL subroutine use the
traditional cubic method of interpolation. The traditional cubic method is a global cubic curve fitting
technique.
Both the Akima method and the traditional cubic method use cubic polynomials to interpolate values
that fall between two adjacent points on a curve. Both provide closer approximations than other curve
fitting techniques (for example, Lagrange polynomials, difference tables, and Fourier series). For data
with two independent variables, Adams uses a linear interpolation technique to interpolate values that
fall between curves.
4. If you have created a spline in Adams View, you may wish to plot the data points or the interpolated
curve to verify that you entered the data correctly and that the spline interpolates smoothly. To do
this, first use the 'NUMERIC_RESULTS CREATE SPLINE' command to create a result set from
the spline. This result set will contain components composed of the spline data points. You can then
plot the result set (that is, the spline data points) with the XY_PLOTS command. You may also use
the 'NUMERIC_RESULTS CREATE INTERPOLATION' command to interpolate more points
from the data-point result set, and then plot those.The Adams View CUBIC and AKIMA
interpolation options use the same methods as the Adams CUBSPL and AKISPL functions,
respectively.
assumed.
data_element 41
data_element create string
be assigned to it.
yourself.
8. You must supply a Y value corresponding to each combination of X and Z values. First list the
component with values for each X value at the first Z value, then the component with values for each
X value at the second Z value, and so on.
9. Since this object can be used in a variety ov contexts, AdamsAdams View can not determine what
type of units it should have. By telling Adams View what the unit type for this object is Adams View
can preform the proper conversions on the values you specify.
10. In the Adams View database and command language, units specification for splines can be done in
either of two ways: via parameters "x_units", "y_units" and "z_units"; or by a single "units"
parameter. If the Spline has this "units" parameter defined, it will be mapped to the Y Units field in
this dialog.
Cautions:
1. Adams View will not allow you to have two splines with the same full name, so you must provide a
unique name.

Allows you to create a character string.
Format:
string_name = a new astring
adams_id = adams_id
comments = string
string = string
Example:
data_element create string &
string_name = string__1 &
adams_id = 1 &
comments = " a new string" &
string = "sample string"
Description:

string_name A New Astring Specifies the name of the new string. You may use this name later to refer
to this string.
adams_id Adams_id Specifies an integer used to identify this element in the Adams data file.
string String A STRING element defines a character string that may be referred to
later in the execution of Adams.
1. A STRING element defines a character string that may be referred to later in the execution of Adams.
The character string cannot be broken and continued on the following line; however, the STRING
element can be longer than a single line. A GTSTRG subroutine can be used to retrieve this character
string in a user-written subroutine.
data_element 43
data_element create variable
be assigned to it.
yourself.
5. The character string cannot be broken and continued on the following line; however, the STRING
element can be longer than a single line. An Adams interactive STRING command can be used to
alter or review this character string. A GTSTRG subroutine can be used to retrieve this character
Cautions:
1. Adams View will not allow you to have two strings with the same full name, so you must provide a
unique name.

Allows you to create a variable.
Format:
variable_name = a new solvar
adams_id = adams_id
comments = string
initial_condition = real
function = function
routine = string
Example:
data_element create variable &
variable_name = variable__10 &
adams_id = 5 &
initial_condition = 0.121 &
function = cos( 10 )
Description:

variable_name A New Solvar Specifies the name of the new variable. You may use this name
later to refer to this variable.
adams_id Adams_id Specifies an integer used to identify this element in the Adams data
file.
initial_condition Real Specifies the initial value of the user_defined differential variable
and, optionally, an approximate value of the initial time derivative.
function Function Specifies the function expression definition that is used to
compute the value of this variable.
subroutine.
routine String
data_element 45
1. You create VARIABLEs to define scalar algebraic equations for independent use, or as part of the
PLANT INPUT, PLANT OUTPUT, or ARRAY elements. The computed value of the VARIABLE
may depend on almost any Adams system variable. Note that you cannot access reaction forces from
user defined, POINT_CURVE, and CURVE_CURVE constraints (Adams UCONs, PTCV, CVCV
statements). You can define the computed value of a VARIABLE by either writing a FUNCTION
expression in the model or by calling a VARSUB user-written subroutine. The Adams Reference
Manual chapter on "Function Expressions," discusses the attributes of FUNCTION expressions, and
the chapter on "Subroutines," discusses user-written subroutines and accessible utility subroutines.
2. FUNCTION expressions and user-written subroutines can access the computed value of the
VARIABLE with the Adams View function VARVAL(variable_name) to represent the value, where
variable_name specifies the name you gave the VARIABLE when it was created. User-written
subroutines access single VARIABLE statement values by calling the subroutine SYSFNC.
Caution should be used when defining VARIABLEs that are dependent on other VARIABLEs or on
Adams View elements that contains functions. If a defined system of equations does not have a stable
solution, convergence may fail for the entire Adams model. The following example refers to this type
of VARIABLE statement:
VARIABLE/1, FUNCTION= VARVAL(1)+1
When looked at as an algebraic equation, it looks like the following:
V=V+1.
However, when Adams tries to solve this equation using the Newton-Raphson iteration, the solution
diverges and a message appears on the screen indicating that the solution has failed to converge.
3. Adams View will not allow you to have two variables with the same full name, so you must provide
a unique name.
be assigned to it.
data_element delete
yourself.
5. When an Adams Solver data file (.adm) is read into AdamsAdams View, all comments associated with
a statement (from the end of the previous statement through the end of the current statement) are
6. The first value is the value of the user- defined variable at the start of the simulation. If you have
entered an implicit equation, the second value may also need to be specified, which is an approximate
value of the time derivative of the user-defined variable at the start of the simulation. Adams may
adjust the value of the time derivative when it performs an initial conditions analysis. Entering an
initial value for the time derivative may help Adams converge to an initial
conditions solution. If you enter an explicit equation, you do not need to supply the second value
since Adams can compute the initial time derivative directly from the equation.
7. To enter a function expression you enter a series of quoted strings.
The easiest way to enter a function expression in Adams View is to use the text editor in combination
with the function builder. To invoke the text editor for entering a function expression, highlight the
function field and then either pick the "EDIT" button at the top of the panel or type a ^t (control-
t). The Adams View "function builder" is discussed below.
The syntactical correctness of a function expression can be investigated by using the "VERIFY"
button at the upper right of the text editor. If there is a syntax error, a message is printed and the
cursor is put near the problem. Proper unit consistency is not checked during function expression
verification.
Tips:
data_element delete
Allows you to delete an existing DATA_ELEMENT.
data_element 47
data_element modify array general_array
Format:
data_element delete
data_element_name = an existing data_element
Example:
data_element delete &
data_element_name = string__1
Description:

1. You must enter the name of the DATA_ELEMENT you wish to delete by either picking it from the
screen or specifying the full name.
2. Since data_element do not have a geometric position, Adams View displays data_element icons at or
Tips:
2. If the data_element is visible in one of your views, you may identify it by picking on any of the
3. You need not separate multiple data_element picks by commas.

Allows you to modify a general_array.
Modifies a one-dimensional array of real numbers that can be accessed in user-written subroutines. This array
is identical in definition to the IC_ARRAY. The GENERAL_ARRAY has been provided to maintain
consistency with the ARRAY available in Adams version 5.2.1.
Format:
new_array_name = new array_name

adams_id = integer
comments = string
size = integer
numbers = real
Example:
data_element modify array general_array &
new_array_name = .model.real_array_1 &
adams_id = 1 &
size = 3 &
numbers = 2.1,3.4,5
Description:

array_name, Array name Specifies the name of the array to be modified.
new_array_name Array name Specifies the new name of the array. You may use this name later to
refer to this array.
adams_id Integer Specifies an integer used to identify this element in the Adams data
file.
using the IC_ARRAY of the GENERAL_ARRAY. The number of
entries should match the value of the SIZE parameter.
unique name.
data_element 49
be assigned to it.
yourself.
data_element modify array ic_array

Allows you to modify an ic_array.
This element creates a one-dimensional array of real numbers that can be accessed in user-written
subroutines. You can use an IC_ARRAY to designate define initial conditions array for an
LINEAR_STATE_EQUATION or GENERAL_STATE_EQUATION. In that case, you should ensure that
the value of the SIZE parameters the same as the X_STATE_ARRAY (state variable) of the associated
LINEAR_STATE_EQUATION or GENERAL_STATE_EQUATION.
Format:
new_array_name = new array_name
adams_id = integer
comments = string
size = integer
numbers = real
Example:
data_element modify array ic_array &
new_array_name = .model.real_array_1 &
adams_id = 1 &
size = 3 &
numbers = 2.1,3.4,5.9
Description:

array_name Array name Specifies the name of the array that has to be modified.
new_array_name New Array name Specify the new name for the array. You may use this name later
adams_id Integer Specifies an integer used to identify this element in the ADAMS
data file.
data_element 51

using the IC_ARRAY of the GENERAL_ARRAY. The number
of entries should match the value of the SIZE parameter.
unique name.
assumed.
be assigned to it.
2. When you use the FILE ADAMS_DATA_SET WRITE command, Adams View writes an ADAMS
data file for your model. ADAMS requires that each modeling element be identified by a unique
in the corresponding statement in the ADAMS data file.
ADAMS file, Adams View will replace the zero with a unique, internally-generated identifier.
yourself.
reason, you wish to control the ADAMS file output.
3. In cases where ADAMS calculates the SIZE differently from the SIZE that the user supplies, ADAMS
data_element modify array u_input_array

For the IC_ARRAY, the SIZE parameter is optional and ADAMS determines the actual size of the
array during parsing, as it counts the NUMBERS values. However, if you provide a value for SIZE ,
ADAMS checks the count for consistency.

Allows you to modify an existing u_input_array.
Format:
array_name = an existing array
new_array_name = a new array
adams_id = adams_id
comments = string
size = integer
Example:
data_element modify array u_input_array &
new_array_name = array__2 &
adams_id = 2 &
comments = " a modified u_input array" &
data_element 53
data_element modify array u_input_array &

size = 1 &
Description:

array_name An Existing Array Specifies the name of an existing array.
new_array_name A New Array Specifies the name of the new array. You may use this name
later to refer to this array.
Adams data file.
modified.
size Integer Specifies the size of an array. In cases where Adams
calculates the SIZE differently from the SIZE that the user
supplies, Adams returns an error or warning message.
Variable
1. The U_INPUT_ARRAY command groups together a set of VARIABLE_NAMEs , normally to
define the inputs for a systems element, either LINEAR_STATE_EQUATION,
GENERAL_STATE_EQUATION , or TRANSFER_FUNCTION. When the you create a
U_INPUT_ARRAY, SIZE and VARIABLE_NAME are the only parameters available.
unique name.
be assigned to it.
yourself.
SIZE parameter value (if given). For the IC_ARRAY, the SIZE parameter is optional and Adams
determines the actual size of the array during parsing, as it counts the NUMBERS values. However,
if you provide a value for SIZE , Adams checks the count for consistency.
data_element 55
data_element modify array x_state_array
Tips:
associated with it.

Allows you to modify an existing x_state_array.
Format:
new_array_name = an existing array
adams_id = adams_id
comments = string
size = integer
Example:
data_element modify array x_state_array &
adams_id = 1 &
comments = "modified x-state array" &
size = 4
Description:
::

array_name An Existing Array Specifies the name of an existing array
new_array_name A New Array Specifies the name of the new array. You may use this name later
data file.
1. An X_STATE_ARRAY defines a list of state variables (X) associated with system modeling elements
such as GSE , LSE , and TFSISO. To use this array, you must reference the array name as the state
variable array in a system element definition. You can use each X_STATE_ARRAY with only one
systems element in your model. When you define an X_STATE_ARRAY , the only other parameter
is SIZE. When you do not specify SIZE , the associated systems element automatically sets the size.
unique name.
assumed.
be assigned to it.
data_element 57
data_element modify array y_output_array
yourself.
STATE_EQUATION_COUNT as defined in the matching ENERAL_STATE_EQUATION

Allows you to modify an existing y_output_array.
Format:
array_name = an existing array
new_array_name = a new array

adams_id = adams_id
comments = string
size = integer
Example:
data_element modify array y_output_array &
new_array_name = array__2 &
adams_id = 2 &
comments = "a modified y_output_array" &
size = 2
Description:

array_name An Existing Array Specifies the name of an existing array.
new_array_name A New Array Specifies the name of the new array. You may use this name later
data file.
1. A Y_OUTPUT_ARRAY specifies the output array for a systems element, either a
LINEAR_STATE_EQUATION, GENERAL_STATE_EQUATION, or
TRANSFER_FUNCTION. To use these arrays, the user must reference the array name as the
output array in the system element definition in the model. When you create a
Y_OUTPUT_ARRAY, SIZE is the only other parameter available. You can use each
Y_OUTPUT_ARRAY with only a single systems element. The SIZE value, if supplied, must be
consistent with the associated systems element. When you do not specify SIZE , the associated
systems element automatically sets it.
unique name.
data_element 59
assumed.
be assigned to it.
yourself.
data_element modify curve

Allows you to modify an existing curve.
Format:
curve_name = an existing curve
new_curve_name = a new acurve
adams_id = adams_id
comments = string
closed = boolean
matrix_name = an existing matrix
fit_type = fit_type
minimum_parameter = real
maximum_parameter = real
Example:
data_element modify curve &
curve_name = curve__1 &
new_curve_name = curve__2 &
adams_id = 1 &
comments = "a modified curve" &
closed = yes &
data_element 61
data_element modify curve &

matrix_name = biele_selnod &
fit_type = curve_points &
segment_count = 10
Description:

curve_name An Existing Curve Specifies an existing curve object
new_curve_name A New Acurve Specifies the name of the new curve. You may use this
name later to refer to this curve.
Adams data file.
modified.
closed Boolean Specifies if the curve meets at the ends.
matrix_name An Existing Matrix Specifies the name of an existing MATRIX containing the
data for the curve.
fit_type Fit_type Specifies the way the curve is to be fit through the points
contained in the MATRIX.
segment_count Integer Specifies the number of polynomial segments Adams uses
for fitting the curve points when FIT_TYPE is set to
CURVE_POINTS.
subroutine.
minimum_parameter Real Specifies the minimum value of the curve parameter only
maximum_parameter Real Specifies the maximum value of the curve parameter only
1. A CURVE element defines a three-dimensional parametric curve that may be referenced by
parameter, u. As u varies from its minimum value to its maximum value, the functions x(u), y(u),
and z(u) sweep out points on the curve. A simple example of a parametric curve is the helix defined
by the following equations:
x = cos(u)
y = sin(u)
z = u
2. Adams View allows you to create curves in three ways: by entering control points for a uniform cubic
3. A uniform B-spline is a piecewise cubic polynomial spline used in many CAD (computer-aided-
ending at +1.
4. A more direct way to define the curve is to supply curve points.
5. In order to use a different type of curve, or to model an analytically-defined curve such as the helix,
A curve can be open or closed. A CLOSED curve meets at the ends, connecting the curve at
minimum and maximum parameter values. Note for a closed curve defined by curve points, you can
specify a maximum of 5 segments less that the number of curve points. Note that because three
segments less than the number of curve points are required for an exact fit, a closed curve will not
exactly fit the curve points.
data_element 63
assumed.
be assigned to it.
yourself.
8. When an Adams Solver data file (.adm) is read into Adams View,all comments associated with a
9. If you set the parameter CLOSED to YES and you use the CURVE_POINTS FIT_TYPE, Adams
will attempt to compute a curve that meets at the ends and has continuous first and second derivatives
across the closure. If you set CLOSED to YES and use the CONTROL_POINTS FIT_TYPE or a
user-defined FUNCTION is specified, you must ensure that the defined curve meets at the ends and
has continuous first and second derivatives across the closure. During a simulation, Adams will move
a POINT_CURVE or CURVE_CURVE contact point across the closure, if necessary. Any
discontinuity could cause integration failure.
By setting CLOSED to NO, you specify that the curve does not meet at the ends. Adams will not
allow a POINT_CURVE or CURVE_CURVE contact point to move beyond the end of the curve.
10. If CONTROL_POINTS is specified, the matrix contains the x, y, and z coordinates of control
points for a uniform B-spline. (Adams uses a uniform knot vector with quadruple multiplicity at both
ends, ensuring that the curve will pass through starting and ending points.)
If CURVE_POINTS is specified, the matrix contains the x, y, and z coordinates of curve points
which the curve will pass through or near.
The matrix should have a row for each point and three columns containing the x, y, and z, coordinates
of the points. You must supply at least four control points or curve points.
You may identify a matrix by typing its name or by picking it from the screen.
Since a matrix does not have a geometric position, Adams View displays matrix icons at or near the
model origin. If the matrix icon is not visible on the screen, you must type the name. You may also
find it convenient to type the name even if the matrix icon is displayed.
If you created the matrix by reading an Adams data set or graphics file, the matrix name is the letters
MAT followed by the Adams data set matrix ID number. The name of Adams MATRIX/101 is
MAT101, for example. If you created the matrix during preprocessing, you gave it a name at that
time.
If a matrix is owned by the default model, you may identify it by entering its name only. If it is not,
To identify a matrix under a different model, for instance, you may need to enter the model name as
well. For example, you may specify matrix 'control_points' from model 'road_surface' by entering
".road_surface.control_points'". If you type a "?", Adams View will list the matrix available by
default.
You must separate multiple matrix names by commas.
11. If FIT_TYPE=CONTROL_POINTS then the MATRIX contains control points to define a
uniform B-spline based on cubic polynomials (i.e. the curve will not necessarily pass through the
points). Specifically, the matrix contains the x, y, and z coordinates of control points for a uniform
B-spline. (Adams uses a uniform knot vector with quadruple multiplicity at both ends, ensuring that
the curve will pass through starting and ending points.)
If FIT_TYPE=CURVE_POINTS then the MATRIX contains data points on the curve and the
curve will be fit directly through the points (depending on the value of the SEGMENT_COUNT
parameter). Specifically, the matrix contains the x, y, and z coordinates of curve points which the
curve will pass through or near. The matrix should have a row for each point and three columns
containing the x, y, and z, coordinates of the points. You must supply at least four control points or
curve points.
12. Adams will default the segment_count to three segments less than the number of curve points, which
gives an exact fit to the curve points. Specifying fewer segments will result in a smoother curve, but
the curve will not pass exactly through the curve points.
than the number of curve points, the computed curve will exactly match the curve points. If you
specify fewer segments, Adams will use a least-squares fit to compute the closest fit to the points. In
general, fewer segments give a smoother curve, but do not come as close to the data points.
13. Adams uses the minimum_parameter value when drawing a curve graphic. For curves defined by
control points or curve points, the minimum parameter value is always -1.0.
Adams uses the maximum_parameter value when drawing a curve graphic. For curves defined by
control points or curve points, the maximum parameter value is always 1.0.
data_element 65
data_element modify matrix file
Cautions:
 Adams View will not allow you to have two curves with the same full name, so you must provide a
unique name.
Tips:
1. If the matrix is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple matrix picks by commas.

Allows you to modify the name of the MATRIX or FILE_NAME which Adams is to read.
The FILE keyword allows you to read large matrices into Adams using an external file. There is no limit on
the size of an array read from a file.
The first record in the file contains an 80 character header of which the first seven or eight characters are
meaningful. If the first record begins with the characters ADAMSMAT, then the file is assumed to be in a
format used by Adams. If the first record begins with the characters MATRIXx, then the file is assumed to
be in the FSAVE format of the MATRIXx software package. If the first record begins with the characters
MATSAVE, then the file is assumed to be in the MATSAVE format of the MATRIXx software package.
No other kinds of files are currently supported. However, the ADAMSMAT option is fairly general since the
format for reading in the data is specified within the file. See the section in the Adams Reference Manual on
the MATRIX statement for a description of the file format.
Format:
matrix_name = existing matrix
new_matrix_name = new matrix name
adams_id = integer
comments = string
file_name = string
name_of_matrix_in_file = string
units = string
Example:
:
data_element modify matrix file &

matrix_name = MATRIX_READ_FROM_FILE &
adams_id = 12 &
data_element modify matrix file &

comments = ”Example of a matrix read from a file” &
file_name = /home/staff/demo/prob.dat &
name_of_matrix_in_file = “VALK” &
Units = String
In the above command, the prob.dat is in the directory, /home/staff/demo, and contains the following data:
1 2 3 4 5 6 7 8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
ADAMSMAT Floating platform example
3
TRF VALK STL
TRF FULL RORDER 4 2 8 ( 8F8.5 )
1.36400 0.00000 0.00000 0.00000 -3.54600 4.00800 0.00000 0.79900
VALK FULL CORDER 3 3 9 ( 3F6.3 )
1.970 0.000-3.440
0.000 4.510 6.020
-3.440 6.020 2.110
STL SPARSE 6 1 4 ( 2( 2I5, E14.6 ) )
1 1 0.169805E+02 2 1 -0.230745E+02
4 1 0.016390E+00 5 1 0.011271E+00
The second and third records are read with format I5 and 4(A8,10X), respectively. Then, the first record of
each of the blocks corresponding to the three matrices TRF, VALK, and STL is read with the format 3A8,
3I5, A41. Finally, as can be seen in the copy of the file shown above between the two strings of 80 characters
that mark the columns (which, of course, are not part of the file), the single record of data for the matrix TRF
is read with the format 8F8.5; the three records for VALK are read with 3F6.3; and the two records for STL
with 2(2I5,E14.6).
Description:

matrix_name Existing matrix Specifies the name of the existing matrix.
New_matrix_name New matrix name Specifies the new name of the matrix.
Adams data file.
modified.
file_name String Specifies the name of a file that contains the values of
the matrix.
name_of_matrix_in_file String Specifies the name of a MATRIX to be read from the
file identified by the FILE_NAME parameter.
units String Allows you to specify the type of units to be used for
this object.
data_element 67
1. You may use this name later to refer to this matrix. Adams View will not allow you to have two
matrices with the same full name, so you must provide a unique name.
be assigned to it.
yourself.
3. The FILE argument may be used to read large matrices into Adams. There is no limit on the size of
an array read from a file.
The proper extension is the default but can be overridden by simply supplying a different extension.
The first record in the file contains an 80 character header of which the first seven or eight characters
are meaningful. If the first record begins with the characters ADAMSMAT, then the file is assumed
to be in a format used by Adams. If the first record begins with the characters MATRIXx, then the
file is assumed to be in the FSAVE format of the MATRIXx software package. If the first record
begins with the characters MATSAVE, then the file is assumed to be in the MATSAVE format of the
MATRIXx software package.
data_element modify matrix full
Note that the three specifications for the format of the data file are case sensitive. Capital letters and
a lower case x must be used to make a selection.
No other kinds of files are currently supported. However, the ADAMSMAT option is fairly general
since the format for reading in the data is specified within the file. See the section in the Adams
Reference Manual on the MATRIX statement for a description of the file format.
4. All three kinds of files, ADAMSMAT, MATRIXx, and MATSAVE, can contain data for more than
one matrix. The NAME_OF_MATRIX_IN_FILE parameter is used to select a particular matrix
from a file even if the file contains only one MATRIX. You must create additional MATRIX
elements in your Adams View model if multiple matrices are to be read from the same file.

Allows you to modify an existing FULL MATRIX.
The MATRIX to be defined is FULL therefore, the VALUES parameter specifies all of the M times N entries
in the matrix. The sequence of the values depends on the value of the INPUT_ORDER parameter. If
BY_ROW is specified, you enter the values row-by-row. If BY_COLUMN is specified, you enter the values
column-by-column.
Format:
matrix_name = existing matrix
new_matrix_name = new name for the matrix
adams_id = integer
comments = string
row_count = integer
column_count = integer
values = real
result_set_component_names = existing component
input_order = matrix_input_order
units = string
Example:
If you want to modify the following matrix of values in full format such that the second row second column
will have value 1.200 instead of 0.000 then you can use the following commands:
data_element 69
data_element modify matrix full &

matrix_name = matrix_1 &
comments = "matrix example in full format" &
row_count = 4 &
column_count = 2 &
values = 1.364,0.000,0.000,1.200,-3.546,4.008,0.000,0.7999 &
input_order = by_column
Description:

matrix_name Matrix name Specifies the name of the existing matrix.
New_matrix_name New name for the Specifies the name of the new matrix. You
matrix may use this name later to refer to this
matrix.
adams_id Integer Specifies an integer used to identify this
element in the Adams data file.
comments String Specifies comments for the object being
created or modified.
row_count Integer Specifies the number of rows (M) in the
column_count Integer Specifies the number of columns (N) in the
value Real Specifies the real number values that you
enter to populate a FULL MATRIX.

result_set_component_names Existing component You can only use a result set component as
matrix values using full format and entering
all the values stored in the result set
component.
input_order By_column,by_row Specifies the order the values that you input
will appear in for a FULL MATRIX format
(all of the M by N entries will be specific
numeric values
units String Allows you to specify the type of units to be
used for this object.
1. A data element matrix is a general M x N array that can be a rectangular or square two-dimensional
matrix or a row or column matrix. You can enter the data in:
• Full format - You list all the M x N values or specify the results of a simulation (result set
components).
• Sparse format - You list the row position, column position, and value for only nonzero entry
values.
• External file - Enter a file containing a matrix.
If one-third or more of the entries in a matrix are nonzero, we recommend that you use full format
since it takes less time to create. If the matrix is mostly empty and entering each nonzero entry's row
position, column position, and value takes less time than entering all of the values, you should use the
sparse format.
unique name.
data_element 71
data_element modify matrix sparse
be assigned to it.
3. The MATRIX to be defined is FULL therefore, the VALUES parameter specifies all of the M times
N entries in the matrix. The sequence of the values depends on the value of the INPUT_ORDER
parameter. If BY_ROW is specified, you enter the values row-by-row.
If BY_COLUMN is specified, you enter the values column-by-column.
4. A result set is a basic set of state variable data that Adams Solver calculates during a simulation. Adams
Solver outputs the data at each simulation output step. A component of a result set is a time series of
a particular quantity (for example, the x displacement of a part or the y torque in a joint).
5. The input_order parameter can take two values:
a. BY_ROW indicates the values are listed by row in the VALUES parameter (that is, starting with
the first row and proceeding to the second, and so on until the entire matrix is completely
defined).
b. BY_COLUMN indicates the values are listed by column (that is, starting with the first column
and proceeding to the second, and so on).
Default value is BY_COLUMN
6. Since this object can be used in a variety of contexts, Adams View can not determine what type of

Allows you to modify a SPARSE MATRIX.
The MATRIX to be defined is SPARSE therefore, the VALUES parameter specifies only the entries that may
be non zero. That is, all entries in the M by N array not assigned values by the ROW_INDEX,
COLUMN_INDEX, and VALUES parameters are assumed to be equal to zero in Adams. Therefore, the
kth entry in the VALUES parameter is assigned to the row identified by the kth entry in ROW_INDEX and
to the column identified by the kth entry in COLUMN_INDEX for k=1,2,...,n.
Format:
matrix_name = existing sparse matrix
adams_id = integer
comments = string
row_index = integer
column_index = integer

values = real
units = string
Example:
data_element modify matrix sparse &
matrix_name = matrix__1 &
new_matrix_name = sparse_matrix_ex &
row_index = 2,3 &
column_index = 1,1 &
values = 3.456,4.567
Description:

matrix_name, Matrix_name Specifies the name of the matrix to modify.
New_matrix_name New matrix_name Specifies the new name of the matrix.
adams_id, Integer Specifies an integer used to identify this element in the Adams
data file.
row_index, Integer Specifies the row position of each of the N entries in the
VALUES parameter for a SPARSE MATRIX.
column_index Integer Specifies the column position of each of the M entries in the
VALUES parameter for a SPARSE MATRIX.
Values Real Specifies the real number values that you enter to populate a
SPARSE MATRIX.
units String Allows you to specify the type of units to be used for this
object.
unique name.
data_element 73
data_element modify plant input
be assigned to it.
position in the matrix of the corresponding entry in the VALUES parameter. For example, the third
value entered for the ROW_INDEX parameter defines what matrix row the third value entered for
the VALUES parameter is located on.
position in the matrix of the corresponding entry in the VALUES parameter. For example, the forth
value entered for the COLUMN_INDEX parameter defines what matrix column the forth value
entered for the VALUES parameter is located on.
5. The MATRIX to be defined is SPARSE therefore, the VALUES parameter specifies only the entries
that may be non zero. That is, all entries in the M by N array not assigned values by the
ROW_INDEX, COLUMN_INDEX, and VALUES parameters are assumed to be equal to zero in
Adams. Therefore, the kth entry in the VALUES parameter is assigned to the row identified by the
kth entry in ROW_INDEX and to the column identified by the kth entry in COLUMN_INDEX
for k=1,2,...,n.

Allows you to modify an existing PLANT INPUT element.
Format:
plant_input_name = an existing pinput
new_plant_input_name = a new pinput
adams_id = adams_id

comments = string
Example:
data_element modify plant input &
new_plant_input_name = pinput__2 &
adams_id = 1 &
comments = " a modified plant input" &
Description:

plant_input_name An Existing Pinput Specifies the name of an existing plant_input.
new_plant_input_name A New Pinput Specifies the name of the new plant_input. You may
use this name later to refer to this plant_input.
Adams data file.
modified.
1. A PLANT INPUT element, along with a PLANT OUTPUT element, is required by the Adams
ADAMS_COMMAND_FILE parameter with the analysis SUBMIT command. Use
the "ACF" button on the text editor and select the GENERATE_STATE_MATRIX
option. You will finally use a panel to select the PLANT INPUTs, PLANT OUTPUTs,
and the format that the state matrices should be generated in
A PLANT INPUT defines a set of inputs to the mechanical system and PLANT OUTPUT defines
the set of measured outputs from the system. The LINEAR/STATEMAT analysis linearizes the
data_element 75
{x}= [A] {x} + [B] {u}

{y}= [C] {x} + [D] {u}
where x is the linearized system state, u is the system inputs defined by the PLANT INPUT element,
and y is the system outputs defined by the PLANT OUTPUT element. This form is commonly
referred to as the state space form of the system equations in control theory. Adams outputs the A,
B, C, and D matrices for use in a control-system design or any other linear system analysis software.
When you run an analysis type other than LINEAR/STATEMAT , the PLANT INPUT element acts
only as a pointer to the list of the specified VARIABLEs.
2. Both FUNCTION expressions and user-written subroutines can access the PLANT INPUT
information. FUNCTION expressions access the values by using the internal Adams function
PINVAL(i1 ,i2) where i1 specifies the PLANT INPUT name , and i2 specifies the i2-th VARIABLE
in the PLANT INPUT statement list. Note that i2 is not the name of the VARIABLE.
User-written subroutines call the subroutine SYSFNC to access single elements of the PLANT
INPUT list and call the subroutine SYSARY to access all values for a PLANT INPUT.
be assigned to it.
yourself.
data_element modify plant output
Cautions:
 Adams View will not allow you to have two plant_inputs with the same full name, so you must
Tips:
associated with it.

Allows you to modify an existing PLANT OUTPUT element.
data_element 77
Format:
plant_output_name = an existing poutput
new_plant_output_name = a new poutput
adams_id = adams_id
comments = string
Example:
data_element modify plant output &
plant_output_name = poutput__1 &
new_plant_output_name = poutput__2 &
adams_id = 1 &
comments = "a modified plant output element " &
Description:

plant_output_name An Existing Specifies the name of an existing plant_output.
Poutput
new_plant_output_name A New Poutput Specifies the name of the new plant_output. You may use
this name later to refer to this plant_output.
Adams data file.
modified.
Variable
1. A PLANT OUTPUT element, along with a PLANT INPUT element, is required by the Adams
ADAMS_COMMAND_FILE parameter with the analysis SUBMIT command. Use
the "ACF" button on the text editor and select the GENERATE_STATE_MATRIX
option. You will finally use a panel to select the PLANT INPUTs, PLANT OUTPUTs,
and the format that the state matrices should be generated in
PLANT OUTPUT defines the set of measured outputs from the mechanical system and PLANT
INPUT defines a set of inputs to the mechanical system. The LINEAR command linearizes the
{x}= [A] {x} + [B] {u}
{y}= [C] {x} + [D] {u}
where x is the linearized system state (X_STATE_ARRAY), u is the system inputs defined by the
PLANT INPUT element (U_INPUT_ARRAY), and y is the system outputs defined by the PLANT
OUTPUT element (Y_OUTPUT_ARRAY). This form is commonly referred to as the state space
form of the system equations in control theory. Adams outputs the A, B, C, and D matrices (i.e.
A_STATE_MATRIX, B_INPUT_MATRIX, C_OUTPUT_MATRIX, and
D_FEEDFORWARD_MATRIX) for use in a control-system design or any other linear system
analysis software.
When the user runs an analysis type other than LINEAR , the PLANT OUTPUT element acts only
as a pointer to the list of VARIABLE specified.
2. Both FUNCTION expressions and user-written subroutines can access the PLANT OUTPUT
element. FUNCTION expressions access the values by using the internal Adams function
POUVAL(i1 ,i2) where i1 specifies the PLANT OUTPUT name , and i2 specifies the i2-th
VARIABLE entry in the PLANT INPUT parameter list. Note that i2 is not the name of the
VARIABLE.
User-written subroutines access single elements of the PLANT OUTPUT list and call the subroutine
SYSFNC to access all values for a PLANT OUTPUT by calling the subroutine SYSARY.
assumed.
data_element 79
be assigned to it.
you must enter its full name.To identify a variable under a different model, for instance, you may
need to enter the model name as well. For example, you may specify variable 'fluid_volume' from
model 'hydro' by entering ".hydro.fluid_volume'". If you type a "?", Adams View will list the variable
Cautions:
1. Adams View will not allow you to have two plant_outputs with the same full name, so you must
data_element modify plant state
Tips:
associated with it.

Allows you to modify an existing PLANT STATE element.
Format:
adams_id = adams_id
comments = string
plant_state_name = a new plant state
Example:
data_element modify plant state &
plant_state_name = pstate__1 &
adams_id = 1 &
comments = "a modified plant state element " &
Description:

plant_state_name An Existing Plant Specifies the name of an existing plant_state.
State
new_plant_state_name A New Plant State Specifies the name of the new plant_state. You may use
this name later to refer to this plant_state.
Adams data file.
modified.
Variable
data_element 81
be assigned to it.
yourself.
data_element modify spline
Cautions:
 Adams View will not allow you to have two plant_states with the same full name, so you must
Tips:
1. if the variable is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.

Allows for modification of an existing spline object.
Format:
spline_name = an existing spline
new_spline_name = a new spline
adams_id = adams_id
comments = string
x = real
y = real
z_result_set_component_name = an existing component
z= real
linear_extrapolate = boolean
x_units = string
y_units = string
data_element 83

z_units = string
file_name = string
Example:
data_element modify spline &
new_spline_name = spline__2 &
adams_id = 2 &
comments = "a modified spline" &
linear_extrapolate = yes &
x_units = mm &
y_units = mm &
z_units = degree &
file_name = "c:\spline.txt"
Description:

spline_name An Existing Spline Specifies the name of the an existing spline
new_spline_name A New Spline Specifies the name of the new spline. You may use this
name later to refer to this spline.
Adams data file.
modified.
x_result_set_componen An Existing Specifies the result set component containing values for
t_name Component the spline X (independent) variable.
x Real
y_result_set_componen An Existing Specifies the result set component containing values for
t_name Component the spline Y (dependent) variable.
y Real
z_result_set_component An Existing Specifies the result set component containing values for
_name Component the spline Z (independent) variable.
z Real
linear_extrapolate Boolean

units String Allows you to specify the type of units to be used for this
object.
x_units String Allows you to specify the type of X units to be used for this
object.
y_units String Allows you to specify the type of Y units to be used for this
object.
z_units String Allows you to specify the type of Z units to be used for this
object.
file_name String
1. A spline interpolates between discrete data for a user-provided function or a utility subroutine called
by a user-written subroutine.
You use the spline to provide one or two independent variables and one dependent variable for each
data point you want to enter. Adams uses curve fitting techniques to interpolate between data points
to create a continuous function. If the spline data has one independent variable, Adams uses a cubic
polynomial to interpolate between points.
If the spline data has two independent variables, Adams first uses a cubic interpolation method to
interpolate between points of the first independent variable and then uses a linear method to
interpolate between curves of the second independent variable.
2. To use the discrete data input with a spline, you must write either a function expression that includes
one of the two Adams spline functions (AKISPL function and CUBSPL function) or a user-written
subroutine that calls one of the two spline utility subroutines (AKISPL subroutine and CUBSPL
subroutine).
3. These spline functions and utility subroutines use two different interpolation methods. The AKISPL
function and the AKISPL subroutine use the Akima method of interpolation. The Akima method is
a local cubic curve fitting technique. The CUBSPL function and the CUBSPL subroutine use the
traditional cubic method of interpolation. The traditional cubic method is a global cubic curve fitting
technique.
Both the Akima method and the traditional cubic method use cubic polynomials to interpolate values
that fall between two adjacent points on a curve. Both provide closer approximations than other curve
fitting techniques (for example, Lagrange polynomials, difference tables, and Fourier series). For data
with two independent variables, Adams uses a linear interpolation technique to interpolate values that
fall between curves.
4. If you have created a spline in Adams View, you may wish to plot the data points or the interpolated
curve to verify that you entered the data correctly and that the spline interpolates smoothly. To do
this, first use the 'NUMERIC_RESULTS CREATE SPLINE' command to create a result set from
the spline. This result set will contain components composed of the spline data points. You can then
data_element 85
plot the result set (i.e. the spline data points) with the XY_PLOTS command. You may also use the
'NUMERIC_RESULTS CREATE INTERPOLATION' command to interpolate more points from
the data-point result set, and then plot those. The Adams View CUBIC and AKIMA interpolation
options use the same methods as the Adams CUBSPL and AKISPL functions, respectively.
assumed.
be assigned to it.
6. . When you use the FILE ADAMS_DATA_SET WRITE command, Adams View writes an Adams
yourself.
8. You must supply a Y value corresponding to each combination of X and Z values. First list the
component with values for each X value at the first Z value, then the component with values for each
X value at the second Z value, and so on.
data_element modify string
9. Since this object can be used in a variety ov contexts, Adams View can not determine what type of
preform the proper conversions on the values you specify.
10. In the Adams View database and command language, units specification for splines can be done in
either of two ways: via parameters "x_units", "y_units" and "z_units"; or by a single "units"
parameter. If the Spline has this "units" parameter defined, it will be mapped to the Y Units field in
this dialog.
Cautions:
1. Adams View will not allow you to have two splines with the same full name, so you must provide a
unique name.

Allows you to modify an existing character string.
Format:
string_name = an existing astring
new_string_name = a new astring
adams_id = adams_id
comments = string
string = string
Example:
data_element modify string &
adams_id = 1 &
comments = " a modified string" &
string = "sample string modified"
data_element 87
Description:

string_name An Existing Astring Specifies the name of an existing string.
new_string_name A New Astring Specifies the name of the new string. You may use this name
later to refer to this string.
Adams data file.
comments Strings Specifies comments for the object being created or modified.
string Strings A STRING element defines a character string that may be
referred to later in the execution of Adams.
1. A STRING element defines a character string that may be referred to later in the execution of Adams.
The character string cannot be broken and continued on the following line; however, the STRING
element can be longer than a single line. A GTSTRG subroutine can be used to retrieve this character
assumed.
be assigned to it.
yourself.
data_element modify variable
5. The character string cannot be broken and continued on the following line; however, the STRING
element can be longer than a single line. An Adams interactive STRING command can be used to
alter or review this character string. A GTSTRG subroutine can be used to retrieve this character
Cautions:
1. Adams View will not allow you to have two strings with the same full name, so you must provide a
unique name.

Allows you to modify an existing variable.
Format:
variable_name = an existing solvar
new_variable_name = a new solvar
adams_id = adams_id
comments = string
function = function
routine = string
Example:
data_element modify variable &
variable_name = variable__10 &
adams_id = 5 &
data_element 89
data_element modify variable &

initial_condition = 0.121 &
function = cos( 10 )
Description:

variable_name An Existing Solvar Specifies the name of an existing variable
new_variable_name A New Solvar Specifies the name of the new variable. You may use this
name later to refer to this variable.
Adams data file.
initial_condition Real Specifies the initial value of the user_defined differential
variable and, optionally, an approximate value of the initial
time derivative.
function Function Specifies the function expression definition that is used to
compute the value of this variable.
subroutine.
routine String
1. You create VARIABLEs to define scalar algebraic equations for independent use, or as part of the
PLANT INPUT, PLANT OUTPUT, or ARRAY elements. The computed value of the VARIABLE
may depend on almost any Adams system variable. Note that you cannot access reaction forces from
user defined, POINT_CURVE, and CURVE_CURVE constraints (Adams UCONs, PTCV, CVCV
statements). You can define the computed value of a VARIABLE by either writing a FUNCTION
expression in the model or by calling a VARSUB user-written subroutine. The Adams Reference
Manual chapter on "Function Expressions," discusses the attributes of FUNCTION expressions, and
the chapter on "Subroutines," discusses user-written subroutines and accessible utility subroutines.
2. FUNCTION expressions and user-written subroutines can access the computed value of the
VARIABLE with the Adams View function VARVAL(variable_name) to represent the value, where
variable_name specifies the name you gave the VARIABLE when it was created.
User-written subroutines access single VARIABLE statement values by calling the subroutine
SYSFNC.
Caution should be used when defining VARIABLEs that are dependent on other VARIABLEs or on
Adams View elements that contains functions. If a defined system of equations does not have a stable
solution, convergence may fail for the entire Adams model. The following example refers to this type
of VARIABLE statement:
VARIABLE/1, FUNCTION= VARVAL(1)+1
When looked at as an algebraic equation, it looks like the following:
V=V+1.
However, when Adams tries to solve this equation using the Newton-Raphson iteration, the solution
diverges and a message appears on the screen indicating that the solution has failed to converge.
3. Adams View will not allow you to have two variables with the same full name, so you must provide
a unique name.
be assigned to it.
yourself.
data_element 91
6. The first value is the value of the user- defined variable at the start of the simulation. If you have
entered an implicit equation, the second value may also need to be specified, which is an approximate
value of the time derivative of the user-defined variable at the start of the simulation. Adams may
adjust the value of the time derivative when it performs an initial conditions analysis. Entering an
initial value for the time derivative may help Adams converge to an initial conditions solution. If you
enter an explicit equation, you do not need to supply the second value since Adams can compute the
initial time derivative directly from the equation.
cursor is put near the problem.Proper unit consistency is not checked during function expression
verification.
Tips:
 See the Adams User's Manual for information on writing user-written subroutines.
defaults 1
defaults adams_output
defaults
The ADAMS_OUTPUT command is used to set parameters that control the organization and statement
format of Adams datasets written by VIEW.
Format:
statement_order = statement_order
arguments_per_line = argument_count
text_case = text_case
indent_spaces = integer
write_default_values = on/off
scientific_notation = integer
trailing_zeros = on/off
zero_threshold = real
round_off = on/off
significant_figures = integer
Example:
Defaults adams_output &
statement_order = markers_with_parts &
arguments_per_line = single
This statement specifies that in the dataset markers are written as a group after the part to which they belong.
Graphics that belong to a single part are written after the markers for that part, and graphics that connect one
or more parts are written after all the parts are written. Also only one argument will be written in one line as
shown below.
PART/1 , QG = 0.5, 0, 0 , REULER = 0D, 90D, 0D , MASS = 1.2
MARKER/101 , PART = 1 , QP = -0.5, 0, 0

Description:

statement_order Markers_with_parts, This controls the organization of the statements
Markers_where_used, within the dataset.
Submodels_and_AdamsId,
Submodels_and_ObjName,
As_found_in_file
arguments_per_line Single/multiple This controls how many arguments are written on
each line of an Adams dataset statement. The
default is a single argument per line.
text_case Upper/lower/mixed This controls the case of the text written for the
statement's keywords and parameters.
indent_spaces Integer This controls the number of spaces after the
comma in column one used to indent a
continuation line of a statement.
write_default_values On/off This controls whether or not arguments that have
default values are written explicitly into the
dataset. The default is that the arguments with
default values are not written into the datset.
scientific_notation Integer This controls the lower and upper powers of ten
where the format for real numbers switches from a
fixed point format to scientific notation.
trailing_zeros On/off This controls whether or not trailing zeros are
printed for real numbers.
decimal_places Integer This controls how many places are written after the
decimal point for real numbers. The default value
is ten decimal places.
zero_threshold Real This specifies the threshold value for numbers
being written to an Adams data set.
round_off On/off This turns the round off feature for real numbers
on or off. The actual numbers of places retained
during rounding off is controlled by the
SIGNIFICANT_FIGURES argument.
significant_figures Integer This controls how many significant figures of a real
number are retained during round off when it is
enabled by setting the value of the ROUND_OFF
argument to ON.
active_only On/off
defaults 3
1. The default for statement order is AS_FOUND_IN_FILE, unless the model was originally created
in view, in which case the default is MARKERS_WITH_PARTS. Note that the order of the
arguments within a statement are written in a fixed order.
AS_FOUND_IN_FILE
The order of the statements in the original dataset is maintained when the model is written back to a
dataset. Any new statements added to the original model are written after all the original statements,
and both sections are labelled to indicate which statements came from the original dataset and which
statements are new.
MARKERS_WITH_PARTS
Markers are written as a group after the part to which they belong. Graphics that belong to a single
part are written after the markers for that part, and graphics that connect one or more parts are written
after all the parts are written.
Statements of the same type, such as JOINTs, JPRIMs, BUSHINGs, etc., are written as a group, in
order of ascending Adams id number.
In general, statements are written before other statements that depend on them. For example, markers
are written before the joints that use them, joints are written before any couplers that connect them,
etc.
MARKERS_WHERE_USED
Markers are written immediately after certain types of statements that depend on the existance of
those markers. The types of statements for which this is done is as follows:
BEAM BUSHING FIELD SFORCE SPRINGDAMPER VFORCE VTORQUE GFORCE
NFORCE JOINT JPRIM REQUEST MREQUEST CVCV PTCV
If a marker is not used by any of these statements, it is written after the part to which it belongs.
Graphics that belong to a single part are written after the markers for that part, and graphics that
connect one or more parts are written after all the parts are written.
Statements of the same type, such as JOINTs, JPRIMs, BUSHINGs, etc., are written as a group, in
order of ascending Adams id number.
In general, the order in which the different types of statements are written into the dataset is similar
to the order used in View 1.0 and 6.0.
2. For the arguments_per_line parameter,there are 2 choices:
SINGLE
Write only one argument and its values for each line of the statement. An example of how this would
look is as follows:
PART/1 , QG = 0.5, 0, 0 , REULER = 0D, 90D, 0D , MASS = 1.2
MARKER/101 , PART = 1 , QP = -0.5, 0, 0
MULTIPLE
Write as many arguments and their values that will fit within 80 columns for each line of the
statement. An example of how this would look is as follows:
PART/1, QG = 0.5, 0, 0, REULER = 0D, 90D, 0D, MASS = 1.2

MARKER/101, PART = 1, QP = -0.5, 0, 0
3. The text_case parameter does not affect comments, function expressions, titles, or filenames that are
used as values of arguments. The default is UPPER.
• UPPER Text for keywords and parameters in the dataset are written in upper case.
• LOWER Text for keywords and parameters in the dataset are written in lower case.
• MIXED Text for keywords and parameters in the dataset are written in mixed case. The first
character of each word is in upper case, and the remaining characters are in lower case.
The text case control will not affect certain types of string valued arguments. They following
arguments will be written into the dataset the way they are stored in the database.
TIRE: TPF and RDF RESULTS: COMMENT MATRIX:

FILE and NAME MADATA: COMMENT STRING: STRING REQUEST:
TITLE, COMMENT, FUNCTION, and F1 to F8 MREQUEST: COMMENT UCON:
FUNCTION MOTION: FUNCTION FIELD: FUNCTION SFORCE:
FUNCTION GFORCE: FUNCTION VFORCE: FUNCTION VTORQUE:
FUNCTION VARIABLE: FUNCTION CURVE: FUNCTION DIFF:
FUNCTION GSE: FUNCTION SENSOR: FUNCTION
4. The allowed values for indent_spaces are between zero and four spaces. Five or more spaces would
make the subsequent text on the line a comment. The default is one space.
The text for function expressions is not indented for continuation lines. It is assumed that the user
will add any leading spaces that they wish for indentation. Any indentation added by the dataset
writer would interfer with the the user's, often used to show nesting of IF functions. The argument
list for a user function will be indented if it requires more than one line.
The values of an argument that has multiple string values separated by colons will be preceded by a
comma and indented if it has to be placed on a continuation line. This applies to the PART/EXACT
and COUPLER/TYPE arguments. The exception is the REQUEST/TITLE argument that doesn't
allow imbedded blanks. This will be preceded by a comma, but not indented.
5. The default values are -4 and 5, meaning that any number less than or equal to 1.0E-04 or greater
than or equal to 1.0E+05 will be written in scientific notation.
6. When enabled, all the digits after the decimal point will be printed, whether they are zero or not.
When disabled, any zeros at the end of the fractional part of the number will be dropped, leaving the
last digit as a non-zero digit.
7. If a number has an absolute value smaller than the zero threshold value, the it will be written out as
zero. This value is independent of units.
8. The default for significant_figures parameter is to use ten significant figures.
This number is distinct from the number of places actually printed for a real number, controlled by
the DECIMAL_PLACES argument.
9. The values assigned to the parameters will remain in effect until reassigned or the end of program
execution.
defaults 5
defaults analysis
defaults analysis
The DEFAULTS ANALYSIS command assigns a value to ANALYSIS_NAME which will be used as the
default for subsequent commands.
This default value is reset when a new file is read. Each time the file is read in (.GRA, .REQ, or .RES) the
ANALYSIS_NAME is set to the file name minus the extension (any preceding path is also stripped off ).
Format:
defaults analysis
defaults analysis analysis_name = existing_analysis
Example:
defaults analysis &
defaults analysis analysis_name = my_analysis
Description:

Analysis_name Existing analysis This parameter specifies the name of an analysis name.
1. When Adams View reads a graphics file (.GRA), a request file (.REQ), or a results file (.RES) an
analysis name is created. By default, the name of the analysis is the file name excluding the extension.
Adams View requires that Adams simulations have unique names and the default name of an analysis
may be overridden when reading the file(s) using the file_name parameter. When referring to an
analysis name that already exists quotes are not necessary. When processing any command that
requires an analysis name the system will default to the default analysis name. The default analysis
name is set to the last analysis file read in (.GRA, .REQ, .RES, or all three). To change the default
analysis name without reading in an analysis file use the "defaults analysis" command.
Cautions:
1. Default name of an analysis may be overridden when reading the file(s) using the file_name
parameter.
defaults attributes
This command allows you to specify the GRAPHIC ATTRIBUTES INHERITANCE algorithm used by
Adams View.
defaults attributes
Format:
defaults attributes
inheritance = up_down
icon_visibility = on/off
size_of_icons = real number
grid_visibility = on/off
endcap_visibility = on/ off
spacing_for_grid = real number
screen_font = font name
postscript_font = font name
dimming_factor = real number
Example:
defaults attributes &
inheritance = bottom_up &
icon_visibility = on &
size_of_icons = 0.2 &
grid_visibility = on &
endcap_visibility = off &
spacing_for_grid = 0.2 &
screen_font = "--Arial-Normal " &
postscript_font = times_roman &
dimming_factor = 0.2
Description:

inheritance Up_down Specifies the graphics attributes INHERITANCE
algorithm to be used by Adams View.
icon_visibility On_off Specifies whether or not to display icons.
size_of_icons Length Allows you to specify the size the Adams View icons will
appear.
grid_visibility On_off_with_toggle2 The GRID_VISIBILITY parameter provides control over
the visibility of the grid in all views.
endcap_visibility On_off_with_toggle2
defaults 7
defaults attributes

spacing_for_grid Length The SPACING_FOR_GRID parameter provides control
over the spacing between the individual grid points for all
views.
screen_font String This parameter controls the device dependent font to be
used when drawing any bitmapped text on the screen.
postscript_font Postscript_fonts This parameter controls the font to be used when drawing
any bitmapped text for a hardcopy output.
dimming_factor Real Sets the level of dimming desired for objects which have
been deactivated via the ACTIVE attribute.
1. GRAPHIC ATTRIBUTES may be applied to almost any entity that may be created in Adams VIEW.
ATTRIBUTE may be inherited from another entity.
2. The rules of INHERITANCE are either TOP_DOWN or BOTTOM_UP. This means that the
attributes are assumed from the children up to the parents (i.e. BOTTOM_UP), or, from the parents
down to the children (i.e. TOP_DOWN). For example, in INHERITANCE=BOTTOM_UP, if the
visibility of a marker is set on, it will override the visibility of the markers parent part when the part
visibility is set to off. Also, in INHERITANCE=TOP_DOWN, if the color of a part is set to red, it
will override the color set for a green marker and the marker will appear red.
3. GRAPHICS ATTRIBUTES include color, visibility, name visibility, render mode, and icon size.
4. Turning the default icon visibility off will result in no icons being displayed, even if they are set to
ON individually. If the default icon visibility is OFF, the visibility of each icon will be determined by
the visibility on that ICON.
5. If you set ICON_SIZE at the model level or at the lower modeling levels of part, marker, constraint,
and force, that values will take precedence.
6. If the visibility of the grid is set for a particular view with the VIEW MANAGE MODIFY
GRID_VISIBILITY command, that setting will be used instead of the default setting. To specify that
the default grid visibility is to be used, enter the command VIEW MANAGE MODIFY
GRID_VISIBILITY=NO_OPINION
7. If the spacing of the grid is set for a particular view with the VIEW MANAGE MODIFY
SPACING_FOR_GRID command, that setting will be used instead of the default setting. To specify
that the default grid visibility is to be used, enter the command VIEW MANAGE MODIFY
SPACING_FOR_GRID=0
8. Using question mark help (typing a '?' or selecting the ? button) for this parameter will display a list
of the available fonts. This parameter does not control the type of font that will be used for hardcopy
output. See the POSTSCRIPT_FONT parameter for information on controlling fonts for hardcopy
output.
defaults command_file
9. A zero value for the dimming factor will make the objects black, while a dimming factor of 1.0 will
cause deactivated objects to appear the same color as active objects.
The DEFAULTS COMMAND_FILE command is used to specify what happens when an error is
encountered while reading a command file.
Format:
on_error = error_action
echo_commands = on.off
update_screen = on/off
Example:
defaults command_file &
on_error = continue_command &
echo_commands = on &
update_screen = on
Description:

echo_commands On_off Specifies whether or not Adams View will echo commands while
executing command files.
update_screen On_off Specifies whether Adams View will update the screen while executing
command files.
1. The three legal values for the on_error parameter are CONTINUE_COMMAND,
IGNORE_COMMAND, and ABORT_FILE. CONTINUE_COMMAND continues processing
the line as if it were typed interactively. This can be dangerous if there is no correction later on the
line, since the parser will keep issuing errors until a correction is made. The errors may continue
beyond the end of the line, even to the end of the file, if carriage-returns are invalid.
CONTINUE_COMMAND should only be used if the command file is a literal recording of your
key strokes, complete with backspaces, or other corrections, after mistakes. IGNORE_COMMAND
ignores the line the error was found on, and starts processing the next line as a new command. The
parser can usually recover and execute subsequent commands in the file. If subsequent commands
defaults 9
defaults coordinate_system
depend on the results of the invalid command, however, they may fail or give unexpected results.
ABORT_FILE immediately closes all the command files and returns to interactive input. This is the
most conservative setting, since it guarantees subsequent commands will cause no further errors or
unexpected results.
IGNORE_COMMAND is the default action.
2. If you select ON, for the echo_commands, the default, the commands will scroll through the Dialog
area and will be recorded as comments in the log file. If you select OFF, the commands will not be
displayed or logged. As a result, the command file will execute more quickly, and the log file will be
smaller.
3. For the update_screen parameter, if you select ON, the default, Adams View will update the display
after each command. If ECHO_COMMANDS is ON, you will see commands scrolling through the
Dialog area. If the command file changes the displayed geometry or plots, you will see the display
change as the commands are executed. If you select OFF, the display will not be updated until the
command file is finished executing. You will only see the final result. If the command file normally
generates many screen updates, especially of solid or shaded views, selecting OFF will make it execute
more quickly.
Tips:
1. The ON_ERROR parameter is useful to set modes for debugging command files.
Allows you to select the coordinate system that location coordinates and orientation angles are with respect
to by default.
Format:
default_coordinate_system = an existing model, part or marker
Example:
defaults coordinate_system &
default_coordinate_system = ground
Description:

default_coordinate_system An Existing Model, Specifies the coordinate system that location
Part Or Marker coordinates and orientation angles are with respect
to by default.
defaults expert_fields
1. You may also change this default by using the RELATIVE_TO parameter on commands that take
location and orientation parameters. If you do not use the RELATIVE_TO parameter, Adams View
assumes the coordinates and angles you enter are in the default coordinate system.
2. Initially, the default is the model, which is the global coordinate system. This is true for orienting
markers as well as parts. Note that this is different than Adams, where markers are specified relative
to the part, not the global system.
3. You use this command to change the default to any model, part, or marker.
Choosing any model as the default is the same as using global coordinates. By choosing a part or
marker, you may enter locations and orientations relative to that part or marker.
4. If you select a part as the default coordinate system, you then enter marker coordinates relative to that
part, just as in Adams. You can locate other parts relative to that part, as well, or choose a marker to
locate from.
Tips:
1. You may also change the default_coordinate_system by using the RELATIVE_TO parameter on
commands that take location and orientation parameters.
Control the displaying of expert fields on panels.
Format:
expert_mode = on/off
Example:
defaults expert_fields &
expert_mode = off
Description:

expert_mode ON_OFF This parameter controls the global default for displaying expert fields
on panels.
defaults 11
defaults force_graphics
1. The DEFAULTS command is used set various parameters of the system. The values assigned to these
parameters will be the default for commands that use them throughout the system.Some of these
parameters are not allowed to default in every case where they are used. If this is true the user is
informed.
2. When expert_mode is on, all panel fields are displayed. When expert_mode is off, any panel fields
that are designated as expert fields will not be initially displayed. They may be displayed by selecting
the MORE button that is in the lower right corner of the panel.
This command sets the defaults for the display of force graphics during an animation.
Format:
force_scale = real
torque_scale = real
display_text = boolean
display_wireframe = boolean
always_in_front = boolean
Example:
defaults force_graphics &
force_scale = 1.5 &
torque_scale = 2.5 &
decimal_places = 3 &
always_in_front = no &
display_text = yes
defaults geometry
Description:

force_scale Real Specify the default size of the force scale to be used for the force
graphics.
torque_scale Real Specify the default size of the torque scale to be used for the force
graphics
display_text Yes/No Specify whether text has to be displayed by default in the force
graphics
decimal_places Integer Specify how many places are written after the decimal point for force
graphics text. The default value is 4.
display_wireframe Yes/No Specify whether wireframe has to be displayed by default in the force
graphics
always_in_front Yes/No Specify if you want Adams View to show force graphics in the
foreground of the model so model geometry does not obscure them.
1. The scale value will have a multiplicative effect on the current size of the force graphics. For example,
a scale value of 0.25 will make the force graphics appear one-fourth as large. A scale value of 2.0 will
make the force graphics appear twice as large.
defaults geometry
The DEFAULTS GEOMETRY command assigns a value to following DEFAULTS
GEOMETRY_PARAMETERS.
Format:
defaults geometry
defaults_geometry_parameter = real number
Example:
defaults geometry &
CurveChordToleranceScale = 0.3
Description:
defaults 13
defaults geometry
defaults geometry

CurveChordToleranceScale Real value Curve chord tolerance scale is the multiplying factor for the curve chord
tolerance. Curve chord tolerance is the maximum chordal distance
between a facet edge and its original edge entity.
The default value is 0.3
If the curve chord tolerance scale is less than 0.3, the tessellation will be
finer. A value greater than 0.3 will result in a coarser tessellation.
defaults 15
defaults geometry

CurveChordAngle Real value Curve chord angle is the maximum angle (always in radians, irrespective
of model units) which is permitted between a facet chord and its original
edge entity.
The default is 0.26 (that is 15 deg) which means a value will be

automatically set by Adams if it is not explicitly set by the user.
Lesser curve chord angle will result in a finer tessellation. Greater angle
will result in a coarser tessellation.
defaults geometry

SurfacePlaneToleranceScale Real value Surface plane tolerance scale is the multiplying factor for the surface
plane tolerance. Surface plane tolerance is the maximum distance
between the mid-plane of a facet and its original face entity.
The default value is 0.3.
If the surface plane tolerance scale is less than 0.3, the tessellation will be
finer. A value greater than 0.3 will result in a coarser tessellation.
defaults 17
defaults hardcopy

SurfacePlaneAngle Real value Surface plane angle is the maximum angle (always in radians,
irrespective of model units) which is permitted between the surface
normal at any two positions on the surface which lie within the facet
boundary.
The default is 0.26 (that is 15 deg) which means a value will be

automatically set by Adams if it is not explicitly set by the user.
Lesser surface plane angle will result in a finer tessellation. Greater angle
will result in a coarser tessellation.
Editing these values through this command will reset the system defaults for this session and all existing
geometry or newly imported geometry in the session will be influenced by them. Once any of these values is
set, it will not be changed throughout session unless it is reset via this command or the File-Import dialog.
When using the File-Import dialog the values will only apply for the specific geometry imported with those
values.
Cautions:
CurveChordToleranceScale, CurveChordAngle, SurfacePlaneToleranceScale and SurfacePlaneAngle are
always positive real values.
defaults hardcopy
Allows the user to send screen output to hard copy file.
defaults hardcopy
Format:
defaults hardcopy
paper_type = hardcopy paper
orientation = hardcopy_orientation
send_to_printer = boolean
file_name = string
print_command = string
black_and_white_graphics = boolean
black_and_white_plot = boolean
language = hardcopy_language
image_height = real
image_width = real
Example:
defaults hardcopy &
paper_type = a1 &
orientation= portrait &
file_name = printtofile
Description:

paper_type Default/ Eight_by_eleven/ A0/ Specify the kind of default paper type to be
A1/ A2/ A3/ A4/ B5/ used.
B/ C/ D/ E/ F
orientation Landscape/ Portrait Specify the default orientation to be used.
send_to_printer Yes/no
file_name String Specifies the name of the file that is to be
read, written, or executed.
print_command String
black_and_white_graphi Yes/no Specifies if black and white graphics is
cs required.
black_and_white_plot Yes/no Specifies if black and white plot is required.
Language Bmp/ Xpm/ Jpg/ Tiff/ Png The LANGUAGE parameter is used to
specify plotting language is to be used for the
image sent to a hardcopy file.
defaults 19
defaults hardcopy

image_height Real Specify the default image height
image_width Real Specify the default image width
Include_toolbars Yes/no
1. You do not need to enclose the file name in quotes if it only contains alpha-numeric characters and
2. The legal values for the language parameter are: BMP, XPM, JPG, TIFF and PNG. The resulting file
should be printable on any device supporting those languages.
The LANGUAGE parameter is optional and if not entered, will be set to BMP.
3. The proper extensionof a file_name is the default but can be overridden by simply supplying a
Cautions:
1. Care should be taken when performing a hardcopy. The choice of draw modes in the view (wireframe,
solid, shaded, set in the view manage modify command or from the control panel) will have impact
on the image sent to the hard copy file. If solid or shaded mode is "on" in the desired view, some
graphics may "seem" to disappear. This happens if the image of an entity is such that the edges of the
shaded entity obscured the shaded or filled area. To avoid this use wireframe draw mode or assure
"facet" interiors are visible before the hardcopy is attempted. The choice of background colors can
have a similar effect.
Tips:
1. The user may specify the view_name to be sent to the desired hardcopy file name. The FILE_NAME
parameter provides a means to specify the name of the hardcopy file the screen image(s) selected by
the user will be written to. The FILE_NAME is an optional parameter and if not entered, a default
name will be constructed. If entered file name must be enclosed in quotes.
2. The ORIENTATION parameter is used to specify how to orient the image sent to a hardcopy file.
There are two legal values for this parameter: LANDSCAPE and PORTRAIT.
3. The LANGUAGE parameter is used to specify plotting language is to be used for the image sent to a
hardcopy file. The legal values for the language parameter are: BMP, XPM, JPG, TIFF and PNG.
defaults icon_naming command
defaults icon_naming command

Defaults icon_naming allows you to set names (full, short, id) to the graphics window items.
Format:
defaults icon_naming show_as = full_name, partial_name, adams_id
Example:
defaults icon_naming show_as = full_name
defaults icon_naming show_as = partial_name
defaults icon_naming show_as = adams_id
Parameter Description
full_name Displays full hierarchy minus model name (for example, PART.MARKER).
partial_name Displays focal object name only (for example, MARKER).
adams_id Displays Adams Solver ID number only.
default lights
This command sets the default settings for the lighting.
You can enhance the quality and realism of your animations by using focused lighting that comes from
different directions, and define the angle of that lighting (how far it is from the centerline). You can think of
this as if you were swinging a light boom across your model.
Format:
Default lights
Light = top_left, top, top_right, left, center, right, bottom_left, bottom, bottom_right
Enable_light = boolean
Example:
Default lights &
Light = top_right &
Enable_light = yes
defaults 21
default lights
Description:

Light top_left, top, top_right, left, center, right, Defines the angle of the lighting.
bottom_left, bottom, bottom_right
Enable_light Yes/No Turns the light on or off
1. Following are the various angles that can be used to define the lighting:
Figure 1 A. “Top_left” sets the light from upper left corner top as illustrated in the example below.
Figure 2 B. Top sets the light from the top as illustrated in the example below.
Figure 3 C. “Top_right” sets the light from the top right as illustrated in the example below
default lights
Figure 4 D. “left” sets the light from the left as illustrated in the example below.
Figure 5 E. “Right” sets the light from the right as illustrated in the example below.
defaults 23
default lights
Figure 6 F. “BOTTOM_LEFT” sets the light from the bottom left as illustrated in the example below.
Figure 7 F. “BOTTOM” sets the light from the bottom as illustrated in the example below.
defaults model
Figure 8 G. “BOTTOM_RIGHT” sets the light from the bottom right as illustrated in the example below.
defaults model
The defaults model command is used to set the location the parser uses when it is validating some object
name (that is marker, joint, and so on) when the user does not start at the root node.
Format:
defaults model
model_name = existing model
part_name = existing part
flexible_body_name = existing flex body
point_mass_name = existing point mass
defaults 25
defaults model
defaults model
marker_name = existing marker
joint_name = existing joint,
geometry_name = existing geometry
Example:
defaults model &
model_name = model_1 &
part_name = cam_part &
marker_name = marker_1
Description:

model_name Existing model Specifies an existing model
part_name Existing part Specifies an existing part
flexible_body_name Existing flex body Specifies the name of a flexible body
point_mass_name Existing point mass Specifies an existing point_mass
marker_name Existing marker Specifies an existing marker
joint_name Existing joint Specifies an existing joint
geometry_name Existing geometry Specifies an existing geometry
1. You may identify a model by typing its name or by picking it from the screen.
2. If the model is not visible on the screen, you must type the name.
3. You may also find it convenient to type the name even if the model is displayed.
• You must separate multiple model names by commas.
• If the model is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
• You need not separate multiple model picks by commas. This also applies to identification of
parts, flexible bodies, point masses, markers, joints and geometries.
defaults name_generation constraint
Caution: 1. If an entity of the specific type is created it becomes the default setting.
2. A flexible body may not have the same name as another flexible body in the same
model.
3. If you set some model default values in a model, for example, Model_1, then create and
navigate to another model, for example, Model_2, the default settings of Model_1 will
be replaced by those of Model_2. On navigating back to Model_1, the first part, flexible
body, and so on within Model_1 will be set as the default values and the original default
values set will be lost.

Allows you to set the name-generation prefixes for constraints.
Format:
coupler_prefix = string
gear_prefix = string
joint_prefix = string
jprim_prefix = string
motion_prefix = string
user_constraint_prefix = string
point_curve_prefix = string
curve_curve_prefix = string
Example:
defaults name_generation constraint &
coupler_prefix = my_coupler
After this command is executed all couplers created will have names My_COUPLER_2, MY_COUPLER_3
and so on.
defaults 27
defaults name_generation data_element
Description:

coupler_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a coupler.
gear_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a gear.
joint_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a joint.
jprim_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a jprim.
motion_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a motion.
user_constraint_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a user_constraint
point_curve_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a point_constraint.
curve_curve_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a curve_curve.
1. Normally, text strings are composed of alphabetic, numeric, or '_' (underscore) characters, and start
By enclosing the text string in double quotes, you may use other printable characters, or start the
name with a numeral. If a text string contains other printable characters, or starts with a numeral, you
must always quote the text string when entering it.

Allows you to set the name-generation prefixes for data_element entities.
Format:
curve_prefix = string
spline_prefix = string
variable_prefix = string
array_prefix = string
matrix_prefix = string

plant_input_prefix = string
plant_output_prefix = string
string_prefix = string
Example:
Defaults name_generation data_element &
curve_prefix = my_curve
Description:

curve_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a curve data element.
spline_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a spline data element.
variable_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a variable data
element.
array_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for an array data
element.
matrix_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a matrix data
element.
plant_input_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a plant_input data
element.
plant_output_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a plant_output data
element.
string_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a string data element.
defaults 29
defaults name_generation force

Allows you to set the name-generation prefixes for forces.
Format:
beam_prefix = string
bushing_prefix = string
field_prefix = string
single_component_force_prefix = string
spring_damper_prefix = string
multi_point_force_prefix = string
force_vector_prefix = string
torque_vector_prefix = string
general_force_prefix = string
Example:
defaults name_generation force &
beam_prefix = my_beam &
bushing_prefix = bush
Beams created will have names my_beam_2, my_beam_3, etc. and tires created will have names bush_2,
bush_3, etc.
Description:

beam_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a beam.
bushing_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a bushing.
field_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a field.
defaults name_generation geometry

single_component_force_ String Specifies the text string to be used as a prefix when Adams
prefix View generates names for a single_component_force.
spring_damper_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a spring_damper.
multi_point_force_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a multi_point_force.
force_vector_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a force_vector.
torque_vector_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a torque_vector.
general_force_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a general_force.

Allows you to set the name-generation prefixes for geometric entities.
Format:
arc_prefix = string
block_prefix = string
circle_prefix = string
cylinder_prefix = string
ellipsoid_prefix = string
frustum_prefix = string
force_prefix = string
spring_damper_prefix = string
torus_prefix = string
revolution_prefix = string
defaults 31

extrusion_prefix = string
note_prefix = string
polyline_prefix = string
bspline_prefix = string
outline_prefix = string
Example:
defaults name_generation geometry &
arc_prefix = my_arc &
block_prefix = my_block &
torus_prefix = my_torus
After the above command is executed, all arcs created will have names MY_ARC_2, MY_ARC_3 and so on,
all blocks will have names MY_BLOCK_2, MY_BLOCK_3 and so on, and all toruses created will have
names MY_TORUS_2, MY_TORUS_3 and so on.
Description:

circle_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a circle.
arc_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for an arc.
block_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a block.
cylinder_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a cylinder.
ellipsoid_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for an ellipsoid.
frustum_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a frustrum.
force_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a force.
spring_damper_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a spring damper.
torus_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a torus.
defaults name_generation layout

revolution_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a revolution.
extrusion_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for an extrusion.
note_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a note.
polyline_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a polyline.
bspline_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a bspline.
outline_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for an outline.

Defaults Name_generation layout allows you to control the layout of default names.
Format:
prefix_active = yes/no
prefix_text = string
entity_prefix = yes/no
integer_id = yes/no
suffix_active = yes/no
suffix_text = string
Example:
defaults name_generation layout &
prefix_active = yes &
prefix_text = abc &
defaults 33
defaults name_generation layout &

entity_prefix = yes &
integer_id = yes &
suffix_active = yes &
suffix_text = def
Description:

prefix_active Boolean Specifies whether or not to add the PREFIX_TEXT string to
the beginning of a modeling entity's name.
prefix_text String Specifies a text string to start all modeling entity names with.
entity_prefix Boolean Specifies the text string to be used as a prefix when Adams
View generates names for a database entity.
integer_id Boolean Specifies whether or not Adams View should append an
integer ID to the end of database names, when generating
them.
suffix_text String Specifies whether or not to append the SUFFIX_TEXT string
to the end of a modeling entity's name
suffix_active Boolean Specifies whether or not to append the SUFFIX_TEXT string
to the end of a modeling entity's name.
1. Adams View combines four components when automatically generating a name:
 a general prefix
 an entity-specific prefix
 an integer entity identifier
 a general suffix
You use this command to specify the general prefix and suffix, and to control which components are
included in the name. By default, Adams View uses only the entity-specific prefix and integer entity
identifier.
2. PREFIX_TEXT is a string that Adams View will add to the start of a database name.
Example
PREFIX_TEXT = "sla_"
PART_NAME = "wheel"
The resultant name would be "sla_wheel"
defaults name_generation marker
3. By enclosing the string for prefix_text in double quotes, you may use other printable characters, or
start the name with a numeral. If a name contains special characters, or starts with a numeral, you
must always quote the string when entering it.
with an alphabetic or '_' character. They may be of any length. By enclosing the text string in double
quotes, you may use other printable characters, or start the name with a numeral. If a text string
contains other printable characters, or starts with a numeral, you must always quote the text string
when entering it.
5. In the case of Adams modeling entities, this integer ID will be the ADAMS_ID. In the case of post-
processing entities, like plots, the integer ID is just an integer to make the name more unique.
Entering YES, will instruct Adams View to append integer IDs to all database names. Entering NO,
will instruct Adams View NOT to append integer IDs to all database names.
6. SUFFIX_TEXT is a string that Adams View will append at the end of a database name.
Example
SUFFIX_TEXT = "_sla"
PART_NAME = "wheel"
The resultant name would be "wheel_sla"
7. SUFFIX_TEXT is a string that Adams View will append at the end of a database name.
Example:
SUFFIX_TEXT = "_sla"
PART_NAME = "wheel"
The resultant name would be "wheel_sla"

Allows you to set the name-generation prefix for markers.
Format:
marker_prefix = string
floating_marker_prefix = string
Example:
defaults name_generation marker &
marker_prefix = my_mar &
floating_marker_prefix = my_float_mar
defaults 35
defaults name_generation model
After this command is executed, all new markers created will be named My_MAR_2, MY_MAR_3, and so
on, and all new floating markers will be named MY_FLOAT_MAR_2, MY_FLOAT_MAR_3, and so on.
Description:

Marker_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a marker.
Floating_marker_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a floating_marker.

Allows you to set the name-generation prefixes for model entities.
Format:
model_prefix = string
gravity_field_prefix = string
sensor_prefix = string
Example:
defaults name_generation model &
model_prefix = my_car_model
Once this command is executed, if we create a new model, the model will get the name,
MY_CAR_MODEL2. New models created after that get the names My_CAR_MODEL_3 and so on. If the
generated name is not unique, Adams View appends a '_2' to the name. If the name is still not unique,
Adams View increments the '2' to a '3'. Adams View will continue incrementing until it finds a unique
name.
defaults name_generation part
Description:

Model_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a model.
Gravity_field_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a gravity_field.
Sensor_prefix String Specifies the text string to be used as a prefix when Adams
View generates names for a sensor.

Allows you to set the name-generation prefixes for part entities.
Format:
part_prefix = string
diff_prefix = string
transfer_function_prefix = string
linear_state_equation_prefix = string
general_state_equation_prefix = string
Example:
defaults name_generation part &
part_prefix = my_part
After this command is executed, all the parts will have part names with prefix “MY_PART”. For example,
MY_PART_2, MY_PART_3, and so on.
defaults 37
defaults name_generation postprocessing
Description:

Part_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a part.
Diff_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a differential
equation.
transfer_function_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a transfer function.
linear_state_equation_pref String Specifies the text string to be used as a prefix when
ix Adams View generates names for a linear state
equation.
general_state_equation_pr String Specifies the text string to be used as a prefix when
efix Adams View generates names for a general state
equation.

Allows you to set the name-generation prefixes for postprocessing entities.
Format:
plot_prefix = string
curve_prefix = string
complex_scatter_prefix = string
eigen_solution_prefix = string
request_prefix = string
femdata_prefix = string
mrequest_prefix = string
defaults orient_axis_and_plane
Example:
defaults name_generation postprocessing &
plot_prefix = plot &
mrequest_prefix = mreq
Description:

plot_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a plot.
curve_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a curve.
complex_scatter_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a complex_scatter.
eigen_solution_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for an eigen solution.
request_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for a request.
femdata_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for femdata.
mrequest_prefix String Specifies the text string to be used as a prefix when
Adams View generates names for an mrequest.
Allows you to select the axis and plane controlled by the ALONG_AXIS_ORIENTATION and
IN_PLANE_ORIENTATION parameters.
Format:
axis_and_plane_setting = axis_setting
defaults 39
defaults page
Example:
defaults orient_axis_and_plane &
axis_and_plane_setting = z_axis_zx_plane
Description:

axis_and_plane_setting Axis_settings Specifies the axis and plane controlled by the
ALONG_AXIS_ORIENTATION and
IN_PLANE_ORIENTATION parameters.
1. You use ALONG_AXIS_ORIENTATION to specify a part or marker coordinate axis,and use
IN_PLANE_ORIENTATION to specify an axis and coordinate plane.
2. You use this command to set which axis and plane you wish to control. The default is the Z axis and
XZ plane, meaning that ALONG_AXIS_ORIENTATION and IN_PLANE_ORIENTATION
work, as does the Adams x-point-z-point method. You direct the Z axis and, with
IN_PLANE_ORIENTATION, locate the XZ plane.
3. You may find it convenient to specify other combinations of axes and planes. However, it is the X axis
of a beam J marker, for example, that defines the centroidal axis of the beam. In this case, you may
wish to direct the X axis when creating the J marker.
You may choose to orient any axis, and either planes adjacent to that axis. For example, selecting
X_AXIS_XY_PLANE means you will subsequently be directing the X axis and locating the XY plane.
defaults page
Specifies the default page name that will be used when a page name is not specified.
Format:
defaults page
page_name = existing page
Example:
defaults page &
page_name = page_1
Now in subsequent commands even if page name is not specified, PAGE_1 will be used by default.
defaults plot
Description:

Page_name Existing page Specify an existing page name.
defaults plot
The DEFAULTS PLOT command is used to set the default plot or curve for subsequent xy plot template,
or curve commands.
Format:
defaults plot
plot_name = existing plot
curve_name = existing curve
Example:
defaults plot &
defaults plot plot_name = test &
xy_plots template modify hlim = 1,50
Note, in the template modify command, no plot name was given to override the default set in the previous
command.
Description:

Plot_name Existing plot name A plot name is a string of characters that identifies a plot.
Curve_name Existing curve name A curve name is a string of characters that identifies a curve.
1. Plot names are assigned when plots are created. After a plot has been created, it may be referenced by
its name until it is deleted. A plot may NOT have the same name as another plot.
A plot_name may be arbitrarily long and a combination of letters of the alphabet and numbers may
be used. The leading character must be a letter.
2. Curve names are assigned by the user when curves are created. After a curve has been created, it may
be referenced by its name until it is deleted. A curve may not have the same name as another curve
on the same plot. A curve is associated to a plot and may be referenced at any time with respect to the
plot. For example, a curve named "c1" on plot "p1" may be referenced by the full specification of
defaults 41
defaults plt_attributes
".p1.c1". This type of full name specification avoids the need to force a given plot to be the "current"
or "default" to the reference data (that is, a curve) associated with it. This is very useful when copying
a curve from one plot to another and so on. A curve_name may be arbitrarily long and a combination
of letters of the alphabet and numbers may be used. The leading character must be a letter.
This command allows the user to control various global attributes for XY plots.
Format:
grid_visibility = on_off
secondary_grid_visibility = on_off
tic_visibility = on_off
legend_visibility = on_off
simulation_legend_visibility = on_off
legend_border_visibility = on_off
simulation_legend_border_visibility = on_off
axis_label_visibility = on_off
symbol_visibility = on_off
border_line_type = line_style
border_thickness = real
title_color = an existing color
subtitle_color = an existing color
haxis_label_color = an existing color
vaxis_label_color = an existing color
axis_numbers_color = an existing color
grid_color = an existing color
secondary_grid_color = an existing color
tic_color = an existing color
border_color = an existing color
legend_border_color = an existing color
simulation_legend_border_color = an existing color
axis_color = an existing color
scientific_notation = integer
trailing_zeros = on_off
legend_placement = plot_legend_place
simulation_legend_placement = plot_legend_place
legend_fill = on_off
simulation_legend_fill = on_off
legend_border_color =
simulation_legend_border_color =
legend_border_line_type = line_style
simulation_legend_border_line_type = line_style
graph_area = real
title_font_size = real
subtitle_font_size = real
legend_font_size = real
strip_chart_font_size = real
zero_line = on_off
Example:
defaults plt_attributes &
grid_visibility = on &
secondary_grid_visibility = off &
tic_visibility = on &
legend_visibility = on &
simulation_legend_visibility = on &
legend_border_visibility = on &
simulation_legend_border_visibility = off &
axis_label_visibility = on &
symbol_visibility = on &
border_line_type = solid &
border_thickness = 0.2 &
title_color = RED &
subtitle_color = GREEN &
haxis_label_color = BLACK &
vaxis_label_color = BLACK &
axis_numbers_color = BLUE &
defaults 43
defaults plt_attributes &

grid_color = YELLOW &
secondary_grid_color = NO_COLOR &
tic_color = NO_COLOR &
border_color = BLACK &
legend_border_color = NO_COLOR &
simulation_legend_border_color = NO_COLOR &
axis_color = BLACK &
scientific_notation = -5 , 5 &
decimal_places = 4 &
legend_placement = top_right &
simulation_legend_placement = top_left &
legend_fill = on &
simulation_legend_fill = off &
use_matlab = no &
legend_border_line_type = solid
Description:

grid_visibility On_off The GRID_VISIBILITY parameter provides
control over the visibility of the grid of a given
view.
secondary_grid_visibility On_off
tic_visibility On_off This parameter controls the default visibility of
axis tic marks for all subsequently created XY
plots.Tic marks are the small lines intersecting
the axis.
legend_visibility On_off This parameter controls the default visibility of
legends for all subsequently created XY plots.
simulation_legend_visibility On_off
legend_border_visibility On_off
simulation_legend_border_visi On_off
bility
axis_label_visibility On_off This parameter controls the default visibility of
axis labels for all subsequently created XY plots.

symbol_visibility On_off This parameter controls the default visibility of
xy_plot curve symbols for all subsequently
created XY plots.
border_line_type Line_style
border_thickness Real
title_color An Existing Color This parameter controls the default color of the
title for all subsequently created XY plots.
subtitle_color An Existing Color This parameter controls the default color of the
subtitle for all subsequently created XY plots.
haxis_label_color An Existing Color This parameter controls the default color of the
horizontal axis label for all subsequently created
XY plots.
vaxis_label_color An Existing Color This parameter controls the default color of the
vertical axis label for all subsequently created XY
plots.
axis_numbers_color An Existing Color This parameter controls the default color of the
axis numbers for all subsequently created XY
plots.
grid_color An Existing Color This parameter controls the default color of the
plot grid for all subsequently created XY plots.
secondary_grid_color An Existing Color
tic_color An Existing Color
border_color An Existing Color
legend_border_color An Existing Color
simulation_legend_border_col An Existing Color
or
axis_color An Existing Color This parameter controls the default color of the
axis line for all subsequently created plot axes.
scientific_notation Integer This controls the lower and upper powers of ten
where the format for real numbers switches from
a fixed point format to scientific notation.
trailing_zeros On_off This controls whether or not trailing zeros are
printed for real numbers.
decimal_places Integer This controls how many places are written after
the decimal point for real numbers. The default
value is ten decimal places.
defaults 45

legend_placement Plot_legend_place This parameter controls the default placement of
legends for all subsequently created XY plots.
Legends may be placed at the top,bottom, or
right side of a plot.
simulation_legend_placement Plot_legend_place
legend_fill On_off
simulation_legend_fill On_off
legend_border_color An Existing Color
simulation_legend_border_col An Existing Color
or
legend_border_line_type Line_style
simulation_legend_border_lin Line_style
e_type
graph_area Real Specifies the size and shape of the graph for all
subsequently created plots. The four graph area
values are the x, y coordinates of the lower left
and upper right corners of the graph.
title_font_size Real
subtitle_font_size Real
legend_font_size Real
strip_chart_font_size Real
zero_line On_off
1. The attributes set using this command will be used for any subsequently created plots. The attributes
that may be controlled are:
 VISIBILITY for grid lines, tic marks, legends, axis labels, and plot curve symbols.
 COLOR for the plot title, plot subtitle, horizontal and vertical axis labels, axis numbers, plot grid,
tic marks, and plot border.
 NUMERICAL_FORMAT for controlling the limits for displaying numerical values in scientific
notation, whether trailing zeroes are displayed, and how many decimal places to display.
 CONFIGURATION for the placement of legends and whether or not to display the zero line.
2. You may modify these attributes on an existing plot with the XY_PLOTSATTRIBUTES command.
3. Symbols are the graphic markers on a curve identifying the data points.
4. The default values for the scientific_notation parameter are -4 and 5, meaning that any number less
than or equal to 1.0E-04 or greater than or equal to 1.0E+05will be written in scientific notation.
defaults prompting_level
5. When the trailing_zeros parameter is enabled, all the digits after the decimal point will be printed,
whether they are zero or not. When disabled, any zeros at the end of the fractional part of the number
will be dropped, leaving the last digit as a non-zero digit.
The DEFAULTS PROMPTING_LEVEL command is used to set the amount of prompting the parser does,
and whether it echoes defaults.
Format:
level = prompting_level
echo_defaults = on/off
wildcard_messages = wldchar_msgs
Example:
defaults prompting_level &
level = required_only &
echo_defaults = on &
wildcard_messages = all
Description:

level Prompting_level Specifies which command parameters Adams View will
prompt for when you give only the keywords for a command.
echo_default On_off The ECHO_DEFAULTS parameter controls whether Adams
View echoes the default parameter values it assumes for a
command.
wildcard_messages Wldcrd_msgs The WILDCARD_MESSGES parameter controls the severity
of messages output when using wildcards on FOR commands.
1. The LEVEL parameter is used to specify which of the command parameters the parser will prompt
for when only the keywords for a command is given. If one or more parameter is specified when the
command is entered, the parser will prompt for required parameters only, regardless of what the
prompting level is set at.
defaults 47
defaults report
2. The default for LEVEL is REQUIRED, which means that if only keywords are entered (no
parameters), then only the required parameters are prompted for. If FULL is specified, then all
parameters will be prompted for when only keywords are entered before the carriage return. If
DEFAULT_ONLY is specified then the required parameters and parameters which have default
values will be prompted for when only keywords are entered before the carriage return.
3. The ECHO_DEFAULTS parameter controls whether Adams View echoes the default parameter
values it assumes for a command. The default is OFF. If you set it ON, Adams View will list any
assumed defaults after you enter each command.
4. If you enter one or more parameter with the command, Adams View will prompt for required
parameters only. The default is REQUIRED, which means that if you enter only keywords (no
parameters), then Adams View prompts you for the required parameters only. If you specify FULL,
Adams View will prompt for all parameters. If you specify DEFAULT_ONLY, Adams View will
prompt for the required parameters and parameters which have default values.
5. For the echo_default parameter, the default is OFF. If you set it toON, Adams View will list any
assumed defaults after you enter each command.
6. The default for wildcard_messages is ALL, which causes all messages generated by the use of wildcards
to be output. If you set it to ERRORS_ONLY, only error messages will be output. NONE will
suppress all messages generated by wildcards on FOR commands.
defaults report
This command can be used to specify the default base font size to be used in reports.
Format:
defaults report
base_font_size = integer
Example:
defaults report &
base_font_size = 10
Description:

Base_font_size Integer Specify the default size of the font size to be used in
reports.
defaults solver
Default solver compatibility_checking checks compatibility of object with selected solver (C++/Fortran)
defaults sprintf_precision
Format:
defaults solver
compatibility_checking = existing page.
Example:
defaults solver &
compatibility_check = On
It will be True by default.
Description:

compatibility_check On/Off Checks compatibility of object with selected solver
(C++/Fortran)
Allows you to change the precision level of real number.
Default precision level is 10.
Format:
defaults sprintf_precision precision = integer_precision
Example:
defaults analysis &
defaults sprintf_precision precision = 15
Description:

sprintf_precision Integer Number This parameter specifies up to which precision
exponential real numbers can be formatted.
defaults 49
defaults units
Default precision level is 10, so up to 1e-11 value can be processed without formatting. Input value less than
1e-11 will be formatted to zero. We can change this default precision level via this sprintf_precision
command.
CMD and TO files as well as Adams View GUI reflects the formatted number as per the set precision level.
Cautions:
1. Default precision level is 10
defaults units
Allows you to set the default length, angle, force, mass, time units, as well as the conventions for coordinates
and orientation angles.
Format:
defaults units
force = force_units
mass= mass_units
length = linear_units
time = time_units
angle = angular_units
frequency = frequency_units
coordinate_system_type = coordinate_system_type
orientation_type = orientation_type
Example:
defaults units &
force = newton &
mass = kg &
length = meter &
time = second &
angle = degrees &
frequency = hz &
coordinate_system_type = cartesian &
orientation_type = space313
defaults units
Description:

force Force_units Specifies the default force units
mass Mass_units Specifies the default mass units
length Linear_units Specifies the default length units
Time Time_units Specifies the default time units
units_consistency_fact Real Specifies a conversion factor to make your force,
or mass, length, and time units consistent
angle Angular_units Specifies the default angle units
frequency Frequency_units Specifies the default frequency units
coordinate_system_typ Coordinate_system_type Specifies a Cartesian, cylindrical, or spherical
e coordinate system as the default
orientation_type Rotation_sequence Specifies the axes and axis rotation order that Adams
View should use when interpreting orientation
angles
1. Adams View will use these units for any values you enter and any values it displays. Adams View also
assumes these units for values read from or written to a file, unless you override them with parameters
on the file read or write command. Adams View uses the coordinate and orientation conventions to
interpret values you enter for location and orientation parameters, such as LOCATION and
ORIENTATION on the 'MARKER CREATE' command.
2. You may select any force, mass, length, or time units you wish. For Adams results to be meaningful,
however, you or Adams View must compute a factor such that the equation
Force = (Mass / UNITS_CONSISTENCY_FACTOR) * Acceleration is
satisfied.
For example, if you use Newtons, kilograms, millimeters, and seconds,
UNITS_CONSISTENCY_FACTOR is 1000. Adams documentation and Data Set Language refer
to this factor as GC, on the ACCGRAV card.
3. By default, Adams View will compute the proper factor when you write an Adams data set. You may,
if you wish, specify it yourself using the 'FORCE CREATE BODY GRAVITATIONAL' command.
4. Adams View will use these units for any values you enter and any values it displays. Adams View also
assumes these units for values read from or written to a file, unless you override them with parameters
on the file read or write command.
5. If you do not specify UNITS_CONSISTENCY_FACTOR, or specify it as zero, Adams View will
calculate it for you when it writes the Adams data set. You may select any force, mass, length, or time
units you wish. For Adams results to be meaningful, however, you or Adams View must compute a
factor such that the Equation
defaults 51
defaults units
Force = (Mass / UNITS_CONSISTENCY_FACTOR) * Acceleration is

satisfied.
For example, if you use Newtons, kilograms, millimeters, and seconds,
UNITS_CONSISTENCY_FACTOR is 1000. Adams documentation and Data Set Language refer
to this factor as GC, on the ACCGRAV card. The only case in which you should set
UNITS_CONSISTENCY_FACTOR yourself is when you are using a set of units Adams View does
not support. Otherwise, you should probably let Adams View compute it for you.
6. If you do use this command to set UNITS_CONSISTENCY_FACTOR to a non-zero value, Adams
View will write your value to an Adams data set. Adams View will not change your value, even if you
later change your force, mass, length, or time units. If you explicitly set
UNITS_CONSISTENCY_FACTOR, then later change your units, remember to update
UNITS_CONSISTENCY_FACTOR.
7. When specifying a location, in order to specify the coordinate system, you provide three coordinates
with respect to the X, Y, and Z axes of a model, part, or marker. In a Cartesian coordinate system,
you specify x, y, and z. These are distances from the coordinate system origin to the point along the
X, Y, and Z axes. In a cylindrical coordinate system, you specify r, theta, and z. R is the distance in
the XY plane to the point. R is measured from the origin to the point projected onto the XY plane.
Theta is the angle in the XY plane to the point. Theta is measured from the X axis to the line
connecting the origin and the point projected into the XY plane. Theta is positive towards the Y axis
(that is, the right-hand rule about the Z axis). Z is the distance to the point along the Z axis.
In a spherical coordinate system, you specify rho, phi, theta. Rho is the distance from the origin to
the point. Phi is the angle between the Z axis and the line connecting the origin and the point. Theta
is the angle in the XY plane to the point, as in cylindrical coordinates. Distances are in the length units
you have chosen. Angles are in the angle units you have chosen.
8. Adams View uses the three orientation angles to do three rotations about the axes of the coordinate
system involved. These rotations may be space-fixed or body-fixed, and in any sequence. You specify
the rotation sequence as three digits which determine which axes are rotated about, and in what
order.The numbers 1,2,3 correspond to X, Y, Z axes. A rotation order of '312', for example, produces
rotations about the Z, then X, then Y axes. If you select body-fixed rotations, Adams View applies the
rotations about axes that move with the body as it rotates. The first rotation produces a new set of
axes. The second rotation is applied about one of the new axes, producing another set of axes. The
third rotation is applied about one of the 'new-new' axes, and produces the final orientation. If you
select space-fixed rotations, Adams View applies the rotations about axes that remain in their original
orientation.
Example: body313
• 'body' indicates a progressive set of rotations.
• '313' indicates the axis rotation order is ZXZ.
• The first rotation will be about the existing Z-axis.
This produces new X and Y axes.
• The second rotation will be about the new X-axis.
This produces new Z and Y axes.
defaults vector_plots
• The third rotation will be about the new Z-axis.

Example: space313
• 'space' indicates a fixed set of rotations.
• '313' indicates the axis rotation order is ZXZ.
• The first rotation will be about the original Z-axis.
• The second rotation will be about the original X-axis.
• The third rotation will be about the original Z-axis.
Format:
scale = real
display_torque = boolean
Example:
defaults vector_plots &
scale = 1.5 &
display_torque = yes
Description:

display_torque Yes/No Specifies whether the torque has to be displayed by
default in the vector plots
Scale Real Specifies the default scale to be used in the vector plots
defaults view
The DEFAULTS command is used to set various parameters of the system. The values assigned to these
parameters will be the default for commands that use them throughout the system. Some of these parameters
are not allowed to default in every case where they are used. If this is true, the user is informed.
Format:
defaults view
view_name = name of an existing view
defaults 53
defaults view
Example:
defaults view &
view_name = .gui.def_view.view_1
Description:

view_name An Existing View Name of an existing view
"all displayed views".
2. 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.
3. 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.
defaults view
display_attributes 1
display_attributes color constraint
display_attributes
The CONSTRAINT keyword indicates that you can specify a default color for all graphics associated with a
constraint.
Color set on a modeling entity will be enforced down the model hierarchy to any lower entities in the
hierarchy.
If an entity at a lower level has a color applied to it, and an entity above it in the model hierarchy has the same
attribute, the highest level entity's color will take precedence.
For example:
.model --------------- color = red
.part ------------ color = no_color
.marker ------- color = blue
The model's color attribute will be enforced on the entities below it, cancelling out the color attribute set on
the marker. Both, the part which has no color attribute and the marker's color, will be red.
Note: Adams View will issue a warning message, reminding you that the attribute has been stored,
but the attribute from an entity at a higher level will take precedence.
In the example, if the attribute is removed from the model, the attribute stored with the marker will be
enforced.
You remove a color attribute from a database entity by setting its color to NO_COLOR.
.model --------------- color = no_color
The marker color will now be blue.
Format:
Example:
display_attributes color constraint &
color = violetred &
Description:

Constraint_name Existing constraint Specifies the constraint to be modified.
1. You may identify constraint by typing its name or by picking it from the screen.
If the constraint is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the constraint is displayed.
If constraint is available by default, you may identify it by entering only its name. If it is not, you
must enter its full name. To identify constraint under another model, for instance, you may need to
enter the model and part names as well. For example, you may specify arc 'end' on part 'arm' in model
'susp' by entering ".susp.arm.end".
If you type a "?", Adams View will list the constraints available by default.
You must separate multiple constraint names by commas.
If the constraint is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple constraint picks by commas.
2. Adams View allows you to specify the following colors amongst others for modeling entities:
BLACK, WHITE, RED, GREEN, BLUE, CYAN, MAGENTA, YELLOW, and NO_COLOR
Example 1: .
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
display_attributes color force

The FORCE keyword indicates that you can specify a default color for all graphics associated with a
constraint.
Color set on a modeling entity will by enforced down the model hierarchy, to any lower entities in the
hierarchy.
attribute, the highest level entity's color will take precedence.
An example:
.model --------------- color = red
the marker. Both the part, which has no color attribute, and the marker's color will be red.
enforced.
Format:
Example:
display_attributes color force &
constraint_name = force_2 &
color = violetred &
Description:

Constraint_name Existing constraint Specifies the force to be modified.
1. You may identify the force by typing its name or by picking it from the screen.
If the force is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the constraint is displayed.
If force is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify force under another model, for instance, you may need to enter the
model and part names as well. For example, you may specify arc 'end' on part 'arm' in model 'susp'
by entering ".susp.arm.end". If you type a "?", Adams View will list the constraints available by
default.
You must separate multiple force names by commas.
If the force is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple force picks by commas.
2. Adams View allows you to specify the following colors amongst others for modeling entities:
BLACK, WHITE, RED, GREEN, BLUE, CYAN, MAGENTA, YELLOW, and NO_COLOR
Example 1:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
display_attributes color geometry

The GEOMETRY keyword indicates that you can specify a default color for a geometry entity.
You can specify a "scope" for the color you select using the ENTITY_SCOPE parameter. This scope will
limit the color's application to: FILL_COLOR, EDGE_COLOR, OUTLINE_COLOR, or ALL_COLOR.
Color set on a modeling entity will by enforced down the model hierarchy to any lower entities in the
hierarchy.
attribute, the highest level entity's color will take precedence. For example:
.model --------------- color = red
the marker. Both, the part which has no color attribute and the marker's color, will be red.
enforced.
Format:
geometry_name = existing geometric entity
entity_scope = color_scope
Example:
display_attributes color geometry &
geometry_name = link_2 &
color = violetred &
entity_scope = fill_color
Color of link_2 will be VioletRed when it is shaded or viewed in the rendered mode.
Description:

geometry_name, Existing Geometry Specifies the geometry to be modified. You use this
parameter to identify the existing geometry to be
affected with this command.
color, Existing Color Specifies the color the modeling entity should be
drawn in.
entity_scope Fill_color, Edge_color, The ENTITY_SCOPE parameter is used to control
Outline_color, Text_color, how a color modification is to affect a particular
All_color graphic entity.
1. You may identify geometry by typing its name or by picking it from the screen.
If the geometry is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the geometry is displayed.
If geometry is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify geometry under another model, for instance, you may need to enter
the model and part names as well. For example, you may specify arc 'end' on part 'arm' in model
'susp' by entering ".susp.arm.end". If you type a "?", Adams View will list the geometrys available by
default.
You must separate multiple geometry names by commas.
If the geometry is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple geometry picks by commas.
2. Adams View allows you to specify the following colors, among others, for modeling entities: BLACK,
WHITE, RED, GREEN, BLUE, CYAN, MAGENTA, YELLOW, and NO_COLOR
Example 1:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part ---------------------- RED
display_attributes color marker
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
3. The legal values for this parameter are FILL_COLOR, EDGE_COLOR, OUTLINE_COLOR, and
ALL.
FILL_COLOR is the color of those areas of a graphic that can be shaded (they include sides of a
cylinders, frustums, boxes, etc.). The EDGE_COLOR is the color of the lines making up the edges
of the facets (or areas filled by the FILL_COLOR) of a graphic that can be shaded.
The OUTLINE_COLOR represents the color of the lines that make up those graphics that cannot
be shaded or filled, like an outline graphic statement consisting of two points or the coil of a
springdamper.
Finally, the ALL value indicates that all three entity types, FILL_COLOR, EDGE_COLOR, and
OUTLINE_COLOR will be affected by the color change.
The ENTITY_SCOPE parameter is optional and if not entered, will be set to FILL_COLOR.

Allows you to control the color of graphic entities associated with a marker.
Format:
marker_name = an existing par
Example:
display_attributes color marker &
marker_name = part__1 &
color = BLUE
Description:

marker_name An Existing marker Specifies the marker to be modified. You use this parameter to
identify the existing marker to be affected with this command.
COLOR An Existing Color Specifies the color the modeling entity should be drawn in.
1. The MARKER keyword indicates that you can specify a default color for all graphics associated with
a marker.
You can specify a "scope" for the color you select using the ENTITY_SCOPE parameter. This scope
will limit the color's application to: FILL_COLOR, EDGE_COLOR, OUTLINE_COLOR, or
ALL_COLOR.
Color set on a modeling entity will be enforced down the model hierarchy, to any lower entities in
the hierarchy.
If an entity at a lower level has a color applied to it, and an entity above it in the model hierarchy has
the same attribute, the highest level entity's color will take precedence.
An example:
.model --------------- color = red
The model's color attribute will be enforced on the entities below it, cancelling out the color attribute
set on the marker. Both the part, which has no color attribute, and the marker's color will be red.
Note: Adams View will issue a warning message, reminding you that the attribute has been
stored, but the attribute from an entity at a higher level will take precedence
In the example, if the attribute is removed from the model, the attribute stored with the marker will
be enforced.
2. You may identify a marker by typing its name or by picking it from the screen.
MAR followed by the Adams data set marker ID number. For example, the name of Adams
MARKER/101 is MAR101. If you created the marker during preprocessing, you will have given it a
name at that time.
If a marker is available by default, you may identify it by entering only its name. If it is not, you must
3. Adams View allows you to specify the following colors for modeling.
entities: BLACK, WHITE, RED, GREEN, BLUE, CYAN, MAGENTA, YELLOW, and
NO_COLOR
Example 1:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
4. The legal values for the entity_scope parameter are FILL_COLOR, EDGE_COLOR,
OUTLINE_COLOR, and ALL.
cylinders, frustums, boxes, etc.) The EDGE_COLOR is the color of the lines making up the edges
springdamper.
Tips:
1. 1. If the part is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple part picks by commas.
display_attributes color model

Allows you to control the color of graphic entities associated with a model.
Format:
model_name = an existing model
Example:
display_attributes color model &
model_name = crankshaft &
color = blue &
entity_scope = edge_color
Description:

model_name An Existing Model Specifies the model to be modified. You use this parameter to
identify the existing model to be affected with this command.
entity_scope Color_Scope The ENTITY_SCOPE parameter is used to control how a color
modification is to affect a particular graphic entity.
1. The MODEL keyword indicates that you can specify a default color for all graphics associated with
the model.
You can specify a "scope" for the color you select using the ENTITY_SCOPE parameter. This scope
will limit the color's application to: FILL_COLOR, EDGE_COLOR, OUTLINE_COLOR, or
ALL_COLOR.
Color set on a modeling entity will be enforced down the model hierarchy, to any lower entities in
the hierarchy.
If an entity at a lower level has a color applied to it, and an entity above it in the model hierarchy has
the same attribute, the highest level entity's color will take precedence.
For example:
.model --------------- color = red
The model's color attribute will be enforced on the entities below it, cancelling out the color attribute
set on the marker. Both the part, which has no color attribute, and the marker's color will be red.
Note: Adams View will issue a warning message, reminding you that the attribute has been
stored, but the attribute from an entity at a higher level will take precedence.
In the example, if the attribute is removed from the model, the attribute stored with the marker will
be enforced.
The marker color will now be blue
If the model is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the model is displayed.
You must separate multiple model names by commas.
If the model is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple model picks by commas.
Example 1:
.model -------------------------NO_COLOR
.part---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
display_attributes color part
OUTLINE_COLOR, and ALL.
The OUTLINE_COLOR represents the color of the lines that make up those graphics that can not
springdamper.

Allows you to control the color of graphic entities associated with a part.
Format:
part_name = an existing part
equation_name = an existing equ
Example:
display_attributes color part &
part_name = part__1 &
color = blue &
entity_scope = edge_color
Description:

model_name An Existing Part Specifies the part to be modified. You use this parameter to
identify the existing part to be affected with this command.

equation_name An Existing Equ Specifies the equation to be modified. You use this parameter to
identify the existing equation to be affected with this command.
entity_scope Color_Scope The ENTITY_SCOPE parameter is used to control how a color
modification is to affect a particular graphic entity.
1. The PART keyword indicates that the color of the graphic components associated to a particular part
are to be affected by the current command. The color of the graphics associated to a part can be
affected all at once or individually (The smallest graphic entity that can be affected is that defined by
the Adams GRAPHICS statement). The scope of the color change to a particular graphic entity can
be controlled as well. The ENTITY_SCOPE can be set to the FILL_COLOR, the EDGE_COLOR,
the LINE_COLOR, or ALL.
The part or graphic entity is identified by the ID label associated to the Adams PART or GRAPHICS
statement respectively. The desired part or graphic is communicated to the application either by
entering the label from the keyboard or picking the particular graphic from the terminal screen using
the cursor (mouse).
2. You may identify a part by typing its name or by picking it from the screen.
followed by the Adams data set part ID number. For example, the name of Adams PART/101 is
PAR101. If you created the part during preprocessing, you will have given it a name at that time.
If a part is available by default, you may identify it by entering only its name. If it is not, you must
3. You may identify an equation by typing its name or by picking it from the screen.
Since equations do not have a geometric position, Adams View displays equation icons at the model
origin. If the equation icon is not visible on the screen, you must type the name. You may also find
it convenient to type the name even if the equation icon is displayed.
If you created the equation by reading an Adams data set or graphics file, the equation name is the
letters DIF followed by the Adams data set equation ID number. For example, the name of Adams
DIFF/101 is DIF101. If you created the equation during preprocessing, you will have given it a
name at that time.
If a equation is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a equation under a different model, for instance, you may need
to enter the model name as well. For example, you may specify equation 'fluid_volume' from model
'hydro' by entering ".hydro.fluid_volume'". If you type a "?", Adams View will list the equations
You must separate multiple equation names by commas.
Example 1:
.model -------------------------NO_COLOR
.part---------------------- RED
Example 2: .
model -------------------------NO_COLOR
.part---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
OUTLINE_COLOR, and ALL. FILL_COLOR is the color of those areas of a graphic that can be
shaded (they include sides of a cylinders, frustums, boxes, etc.). The EDGE_COLOR is the color of
the lines making up the edges of the facets (or areas filled by the FILL_COLOR) of a graphic that can
be shaded.
The OUTLINE_COLOR represents the color of the lines that make up those graphics that can not
springdamper.
Tips:
1. If the part is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
display_attributes icon_size constraint

Allows you to specify the size the Adams View constraint icons will appear.
Format:
constraint_name = an existing constraint
Example:
display_attributes icon_size constraint &
constraint_name = .crankshaft.drivermotion.motion_r2 &
size_of_icons = 0.9
Description:

constraint_name An Existing Constraint Specifies the constraint to be modified. You use this
parameter to identify the existing constraint to be affected
with this command.
scale_of_icons Real Specifies a unit-less scale factor to be applied to the current
icon size.
will appear in.
1. You may set a specific size for icons in modeling units, or scale their present size with a unit-less scale
factor.
If no initial size is specified for Adams View icons, the default size will be one modeling LENGTH
unit. For example, if the modeling units are K/M/S, a revolute joint icon will be one meter in
diameter.
When you specify an ICON_SCALE, a new size is calculated by multiplying the current size, by the
scale, and storing the product as the new ICON_SIZE.
If a model has an ICON_SIZE set, and a constraint under that model has a different ICON_SIZE,
the model's ICON_SIZE will take precedence.
For Example:
.model ---------------------- ICON_SIZE = .25 meters
.constraint-------------- ICON_SIZE = .125 meters
If the model has an ICON_SIZE of 0.0 set, and a constraint under the model has an ICON_SIZE
of .125, the constraint's ICON_SIZE will be used.
For Example:
.model ---------------------- ICON_SIZE = 0.0 meters
.constraint-------------- ICON_SIZE = .125 meters
If the constraint is not visible on the screen, you must type the name. You may also find it convenient
to type the name even if the constraint is displayed.
If you created the constraint by reading an Adams data set, the constraint name is the first three letters
of the Adams statement type followed by the Adams data set constraint ID number. For example,
the name of Adams JOINT/101 is JOI101. If you created the constraint during preprocessing, you
will have given it a name at that time.
If a constraint is available by default, you may identify it by entering only its name. If it is not, you
must enter its full name.
To identify a constraint under a different model, for instance, you may need to enter the model name
as well. For example, you may specify constraint 'servo_motor' from model 'test' by entering
".test.servo_motor". If you type a "?", Adams View will list the constraints available by default.
in length.
in length.
For Example:
.part-------------------- SIZE_OF_ICONS = .125 meters
The part's icon will be 1.5 meters is size.
display_attributes icon_size force
If the model has SIZE_OF_ICONS of set to 0.0 , and a part under that model has a
SIZE_OF_ICONS set to .125, the part's icon size will be used.
An Example:
The part's icon will be .125 meters is size.
Tips:
1. If the constraint is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple constraint picks by commas.

Allows you to specify the size the Adams View force icons will appear.
Format:
force_name = an existing constraint
Example:
display_attributes icon_size force &
force_name = .crankshaft.DriverMotion.motion_r2 &
size_of_icons = 0.9
Description:

force_name An Existing Force Specifies the force to be modified. You use this parameter to
identify the existing force to be affected with this command.
scale_of_icons Real Specifies a unit-less scale factor to apply to the current icon size.
size_of_icons Length Specifies the size, in modeling units, the Adams View icons will
appear.
factor. If no initial size is specified for Adams View icons, the default size will be one modeling
LENGTH unit. For example, if the modeling units are K/M/S, a translational force icon will be one
meter in length.
When you specify an ICON_SCALE, a new size is calculated by multipling the current size, by the
If a model has an ICON_SIZE set, and a force under that model has a different ICON_SIZE, the
model's ICON_SIZE will take precedence.
For Example:
.force------------------- ICON_SIZE = .125 meters
The force's icon will be .25 meters is size.
If the model has an ICON_SIZE of 0.0 set, and a force under the model has a ICON_SIZE of .125,
the force's ICON_SIZE will be used.
For Example:
.force------------------- ICON_SIZE = .125 meters
The force's icon will be .125 meters is size.
2. You may identify a force by typing its name or by picking it from the screen.
You may also find it convenient to type the name even if the force is displayed.
If you created the force by reading an Adams data set or graphics file, the force name is the first three
letters of the Adams statement followed by the Adams data set force ID number. For example, the
name of Adams SFORCE/101 is SFO101. If you created the force during preprocessing, you will
have given it a name at that time.
If a force is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a force under a preprocessing model, for instance, you may need to
enter the model name as well. For example, you may specify the force named 'bumper' from the
model named 'test' by entering ".test.bumper". If you type a "?", Adams View will list the forces
in length.
in length.
display_attributes icon_size marker
5. When you set SIZE_OF_ICONS at the model level, all Adams View icons used in creating a model
If the model has a SIZE_OF_ICONS set, and a part under that model has a different
For Example:
For Example:
Tips:
1. If the force is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple force picks by commas.

Allows you to specify the size the Adams View marker icon will appear in.
Format:
marker_name = an existing constraint
Example:
display_attributes icon_size marker &
marker_name = marker__1 &
size_of_icons = 0.9
Description:

marker_name An Existing Marker Specifies the marker to be modified. You use this parameter to
scale_of_icons Real Specifies a unit-less scale factor to be applied to the current
icon size.
will appear in.
factor.
unit. For example, if the modeling units are K/M/S, a marker axes icon will have triad legs of one
meter in length.
If a part has an ICON_SIZE set, and a marker under that part has a different ICON_SIZE, the part's
ICON_SIZE will take precedence.
An Example:
.part -------------------- ICON_SIZE = .125 meters
.marker ---------------- ICON_SIZE = .2 meters
The marker's icon will be .125 meters is size.
If the model, and part have an ICON_SIZE of 0.0 set, and a marker under the part has a
ICON_SIZE of .125, the marker's ICON_SIZE will be used.
For Example:
.part -------------------- ICON_SIZE = 0.0 meters
.marker ---------------- ICON_SIZE = .2meters
The marker's icon will be .2 meters is size.
MARKER/101 is MAR101. If you created the marker during preprocessing, you will have given it
a name at that time.
display_attributes icon_size model
in length.
in length.
For Example:
model ---------------------- SIZE_OF_ICONS = .15 meters
part -------------------- SIZE_OF_ICONS = .125 meters
An Example:
.part -------------------- SIZE_OF_ICONS = .125 meters
Tips:
1. If the marker is visible in one of your views, you may identify it by picking on it.
2. You need not separate multiple marker picks by commas.

Allows you to specify the size all Adams View icons in a model will appear in.
Format:
Example:
display_attributes icon_size model &
model_name = piston &
size_of_icons = 0.9
Description:

model_name An Existing Model Specifies the model to be modified. You use this parameter to
scale_of_icons Real Specifies a unit-less scale factor to be applied to the current icon
size.
appear in.
factor.
in length.
When you set ICON_SIZE at the model level, all Adams View icons used in creating a model will
use the size specified.
If the model has an ICON_SIZE set, and a part under that model has a different ICON_SIZE, the
model's ICONS_SIZE will take precedence.
For Example:
.part-------------------- ICON_SIZE = .125 meters
If the model has an ICON_SIZE of 0.0 set, and a part under that model has a ICON_SIZE of .125,
the part's ICON_SIZE will be used.
For Example:
associated with it.
in length.
in length.
For Example:
For Example:
Tips:
1. If the model is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
display_attributes icon_size part
2. You need not separate multiple model picks by commas.

Allows you to specify the size the Adams View part icon will appear in.
Format:
Example:
display_attributes icon_size part &
part_name = piston &
size_of_icons = 0.9
Description:

part_name An Exisisting Part Specifies the part to be modified. You use this parameter to
scale_of_icons Real Specifies a unit-less scale factor to be applied to the current icon
size.
appear in.
factor.
in length.
If a model has an ICON_SIZE set, and a part under that model has a different ICON_SIZE, the
model's ICON_SIZE will take precedence.
For Example:

If the model has an ICON_SIZE of 0.0 set, and a part under the model has an ICON_SIZE of .125,
the part's ICON_SIZE will be used.
For Example:
in length.
in length.
For Example:
display_attributes rendering_mode
For Example:
Tips:
associated with it.
This command specifies the rendering mode of individual or groups of graphic objects.
Format:
geometry_name = an existing geometric entity
type_of_geometry = geometry_type
render_mode = render_mode
Example:
display_attributes rendering_mode &
geometry_name = solid3 &
type_of_geometry = block &
render_mode = wireframe
Description:

geometry_name An Existing Geometric Entity Specifies the geometry to be modified. You use this
type_of_geometry Geometry_Types Specifies the type of geometry that is to have its
rendering mode modified.
render_mode Render_Modes The render mode is an attribute that is attached to
each of the specific graphic entities and works in
tandem with a view's RENDER attribute (see
below).
1. This render mode is an attribute that is attached to each of the specific graphic entities and works in
tandem with a view's RENDER attribute.
There are two possible values for the RENDERING_MODE parameter:
WIREFRAME - Graphic objects that have a WIREFRAME rendering mode will ALWAYS be drawn
as wireframe geometry, regardless of how views are rendered (wireframe, solid, or shaded).
FILLED - Graphic objects that have a FILLED rendering mode will be drawn based upon the view's
RENDER parameter that the graphic is drawn in (wireframe, solids, shaded).
If you type a "?", Adams View will list the geometrys available by default.
3. This parameter acts as a filter to decide which of the selected geometry objects will have their
rendering mode modified.
The possible values are: ARC, BOX, FRUSTUM, SPRINGDAMPER, OUTLINE, or ALL. The
ARC setting includes both arc and circle geometry. The FRUSTUM setting includes both, frustum
and cylinder geometry.
4. Graphic objects that can have their rendering mode altered include: arcs, outlines, boxes, circles,
cylinders, frustums, and spring damper graphics.
The selection of graphic objects can be based on association to a particular analysis, part, or by
individual graphic name. When the rendering mode of a part is specified, all graphic objects fixed to
that part are drawn with the rendering mode of the part. Graphics that span parts can only be selected
by graphic name.
Adams View supports WIREFRAME and FILLED rendering modes.
This command should not be confused with the VIEW MANAGEMENT... RENDER parameter.
The RENDER parameter in view control sets an attribute associated with a particular view. So, if the
view render mode is wireframe, all the graphics will be drawn in wireframe mode regardless of the
value of a specific graphic object's render mode attribute. However, if the view render mode is set to
SOLIDS or SHADED, then a specific graphic entity will be drawn in the mode specified by the
DISPLAY_ATTRIBUTES RENDER_MODE command. In other words, the view RENDER
parameter is an attribute of the view and the display_attribute render mode is an attribute of the
specific graphic element. Or, WIREFRAME is the dominant mode and regardless of how it is set
(either RENDER by view or RENDERING_MODE by graphic object).
display_attributes scale force_graphics
Tips:
1. If the geometry is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple geometry picks by commas.

The FORCE_GRAPHICS command indicates that all translational force graphics associated with a specified
analysis are to be scaled. The scale value will have a multiplicative effect on the current size of the force
graphics. For example, a scale value of 0.25 will make the force graphics appear one-fourth as large. A scale
value of 2.0 will make the force graphics appear twice as large.
Format:
scale = real
Example:
display_attributes scale force_graphics &
analaysis_name = analysis_1 &
scale = 2.0
Force graphics in the analysis ANALYSIS_1 will appear twice as large as they used to, once the above
command is executed.
Description:

analysis_name Existing Analysis This parameter specifies an analysis name.
scale Real The scale parameter is used to control the size of the marker, force,
or torque graphic symbols.
1. When Adams View reads a graphics file (.GRA), a request file (.REQ), or a results file (.RES), an
display_attributes scale torque_graphics
analysis name that already exists, quotes are not necessary. When processing any command that
requires an analysis name, the system will default to the default analysis name. The default analysis
2. The scale value will have a multiplicative effect on the current size of the graphic symbols. For
example, a scale value of 0.25 will make the graphic symbol appear one-fourth as large. A scale value
of 2.0 will make the graphic symbol appear twice as large. The scale value is a real number and must
be greater than zero. This parameter is optional and if not entered will default to 1.0.

The TORQUE_GRAPHICS command indicates that all rotational force graphics associated with a specified
analysis are to be scaled. The scale value will have a multiplicative effect on the current size of the rotational
force graphic symbol. For example, a scale value of 0.25 will make the rotational force graphic symbols appear
one-fourth as large. A scale value of 2.0 will make the rotational force graphic symbols appear twice as large.
Format:
scale = real
Example:
display_attributes scale torque_graphics &
analaysis_name = analysis_1 &
scale = 2.0
Torque graphic symbol in the analysis ANALYSIS_1 will appear twice as large as they used to, once the above
command is executed.
Description:

Analysis_name Existing Analysis This parameter specifies an analysis name.
Scale Real The scale parameter is used to control the size of marker, force, or
torque graphic symbols.
display_attributes visibility constraint
analysis name without reading in an analysis file, use the "defaults analysis" command.
2. The scale value will have a multiplicative effect on the current size of the graphic symbols. For
example, a scale value of 0.25 will make the graphic symbol appear one-fourth as large. A scale value
of 2.0 will make the graphic symbol appear twice as large. The scale value is a real number and must
be greater than zero. This parameter is optional and if not entered, will default to 1.0.

Allows you to set the visibility of an existing constraint in Adams View.
Format:
constraint _name = an existing constraint
name_visibility = on_off_with_toggle
Description:

constraint _name An Existing Constraint Specifies the constraint to be modified. You use this
parameter toidentify the existing constraint to be affected
with this command.
name_visibility On_off_with_toggle The NAME_VISIBILITY parameter provides control over
the visibility of the view name displayed at the top center
1. When you set an attribute on a modeling entity, that attribute gets stored with the entity in the
database. There are rules for the application of these attributes.
Visibility applied to any modeling entity will be enforced down the modeling hierarchy in the
following fashion.
A visibility attribute setting of ON, allows that entity to be drawn.

This means if you set visibility=on for a marker, but its parent part has a visibility setting of off, the
marker will not be visible.
A visibility setting of OFF, turns that entity's visibility off and, has the effect of turning visibility off
for all modeling entities below it.
For Example:
.model ---------------- visibility = on
.part ------------- visibility = off
.marker -------- visibility = on
The marker will not be visible because the part is not visible.
By default, all entities have a visibility attribute of ON, when created.
of the Adams statement type followed by the Adams data set constraint ID number. For example,
the name of Adams JOINT/101 is JOI101. If you created the constraint during preprocessing, you
To identify a constraint under a different model, for instance, you may need to enter the model name
as well. For example, you may specify constraint 'servo_motor' from model 'test' by entering
".test.servo_motor". If you type a "?", Adams View will list the constraints available by default.
are to be drawn in an Adams View viewport.
The legal values for this parameter are: ON, OFF, and TOGGLE. ON will make the desired entity
visible. OFF will make the desired entity invisible. TOGGLE will take the current state of an entities
visibility and reverse it.
4. The legal values of the name_visibility parameter are ON and OFF. This is an optional parameter
and if not entered, the name will be visible (i.e. will be ON).
Note that if the visibility of the view name is turned off, the only indication that a view is "active" will
be the color of the viewport border. This would be a problem on a black and white monitor.
Tips:
1. If the constraint is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple constraint picks by commas.
display_attributes visibility force

Allows you to set the visibility of an existing force in Adams View.
Format:
force_name = an existing force
Example:
display_attributes visibility force &
force_name = force__1 &
visibility = on &
name_visibility = on
Description:

force_name An Existing Force Specifies the force to be modified. You use this parameter to
identify the existing force to be affected with this command.
name_visibility On_off_with_toggle The NAME_VISIBILITY parameter provides control over the
visibility of the view name displayed at the top center position of
a given view.
Visibility applied to any modeling entity will be enforced down the modeling hierarchy, in the
following fashion.
This means if you set visibility on for a marker, but its parent part has a visibility setting of off, the
A visibility setting of OFF, turns that entity's visibility off and, has the effect of turning visibility off
For Example:
display_attributes visibility geometry

You may also find it convenient to type the name even if the force is displayed.
and if not entered, the name will be visible (that is, will be ON).
Tips:
1. If the force is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple force picks by commas.

Allows you to set the visibility of an existing geometric entity in Adams View.
Format:
Example:
display_attributes visibility geometry &
geometry_name = solid3 &
visibility = on
Description:

1. The GEOMETRY keyword indicates that you can specify the visibility for a geometry entity.
When you set an attribute on a modeling entity, that attribute gets stored with the entity in the
Visibility applied to any modeling entity will be enforced down the modeling hierarchy, in the
following fashion.
A visibility setting of OFF, turns that entity's visibility off and has the effect of turning visibility off
For Example:
display_attributes visibility marker
If you type a "?", Adams View will list the geometrys available by default.
visible. OFF will make the desired entity invisible. TOGGLE will take the current state of an entity’s
Tips:
1. If the geometry is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.

Allows you to set the visibility of an existing marker in Adams View.
Format:
marker_name = an existing marker
Example:
display_attributes visibility marker &
marker_name = marker_1 &
visibility = on &
Description:

marker_name An Existing Marker Specifies the marker to be modified. You use this parameter to
visibility of the view name displayed at the top center position
of a given view.
1. The MARKER keyword is used to control whether a particular (or group of) markers(s) are to be
drawn in an Adams View viewport. The visibility of markers can be set using this command. The
scope of a particular marker visibility change can be controlled. This means that a single visibility
change can affect all markers in a particular analysis, on a particular part, or marker visibility can be
controlled individually.
name at that time.
and if not entered, the name will be visible (that is, will be ON).
display_attributes visibility model
Tips:
1. If the marker is visible in one of your views, you may identify it by picking on it.

Allows you to set the visibility of an existing model in Adams View.
Format:
Example:
display_attributes visibility model &
visibility = on &
Description:

model_name An Existing Model Specifies the model to be modified. You use
this parameter to identify the existing model
to be affected with this command.
visibility On_Off_With_Toggle Specifies the visibility of graphic entities.
name_visibility On_Off_With_Toggle The NAME_VISIBILITY parameter
provides control over the visibility of the view
name displayed at the top center position of a
given view.
Visibility applied to any modeling entity will be enforced down the modeling hierarchy in the
following fashion.
display_attributes visibility part
A visibility setting of OFF, turns that entity's visibility off and has the effect of turning visibility off
An Example:
If the model is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the model is displayed.
associated with it.

Allows you to set the visibility of an existing part in Adams View.
Format:
Example:
display_attributes visibility part &
visibility = on &
Description:

part_name An Existing Part Specifies the part to be modified. You use this parameter to
equation_name An Existing Equ Specifies the equation to be modified.You use this parameter
to identify the existing equation to be affected with this
command.
visibility of the view name displayed at the top center position
of a given view.
1. The PART keyword indicates that the visibility of the graphic components associated to a particular
part are to be affected by the current command. The visibility of the graphics associated to a part can
only be affected all at once (not individually).
The part is identified by the ID label associated to the Adams PART statement. The desired part is
communicated to the application either by entering the label from the keyboard or picking the
particular graphic from the terminal screen using the cursor (mouse).
display_attributes visibility plot
it convenient to type the name even if the equation icon is displayed.
If you created the equation by reading an Adams data set or graphics file, the equation name is the
letters DIF followed by the Adams data set equation ID number. For example, the name of Adams
DIFF/101 is DIF101. If you created the equation during preprocessing, you will have given it a name
at that time.
If a equation is available by default, you may identify it by entering only its name. If it is not, you
must enter its full name. To identify a equation under a different model, for instance, you may need
to enter the model name as well. For example, you may specify equation 'fluid_volume' from model
'hydro' by entering ".hydro.fluid_volume'". If you type a "?", Adams View will list the equations
You must separate multiple equation names by commas.
If the equation is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple equation picks by commas.
Tips:
associated with it.

This command allows the user to control the visibility of objects on an XY plot. These objects include notes,
grid_lines, tic_marks, legend, axis_labels, and symbols. By changing the visibility of these objects, you can
alter the appearance of the plot without deleting them.
Format:
plot_name = an existing plot
grid_lines = on /off

tic_marks = on/ off
legend = on / off
axis_labels = on /off
symbol = on / off
Example:
display_attributes visibility plot &
plot_name = plot_1 &
grid_lines = on &
tic_marks = on &
legend = off &
axis_labels = on &
symbol = off
Description:

plot_name An Existing Plot A plot name is a string of characters that identifies a plot
grid_lines On_off This parameter controls the visibility of the plot grid lines
tic_marks On_off This parameter controls the visibility of axis tic marks
legend On_off This parameter controls the visibility of the XY plot legend
axis_labels On_off This parameter allows the visibility of the axis labels to be turned ON or
OFF
symbol On_off This parameter controls the visibility of xy_plot curve symbols
1. Plot names are assigned when plots are created. After a plot has been created, it may be referenced by
its name until it is deleted. A plot may NOT have the same name as another plot.
A plot_name may be arbitrarily long and a combination of letters of the alphabet and numbers may
2. Grid lines are a set of vertical and horizontal lines that are extensions of the tic marks on the vertical
and horizontal axes. Grid lines provide for more accurate interpretation of the data on an XY plot.
ON indicates that the grid lines will be visible, OFF indicates that the grid lines will be invisible. This
parameter is optional and if not entered, grid lines will be displayed on the xy_plot.
3. Tic marks are the small lines intersecting the axis. ON, the default, indicates that the tic marks will
be visible; OFF indicates that the tic marks will be invisible.
4. The XY plot legend displays a label beside a key describing that curve. The label will be the Adams
request statement comment, if one is found. If no request comment is found, a label is created by
concatenating the data specified in the haxis_data and vaxis_data parameters that comprise that curve.
The key will look like the curve with respect to color, line type, and line thickness. The plot legend
is displayed at the top of the XY plot template. This parameter is optional and ON (the default)
indicates that the legend will be visible, OFF indicates that the legend will be invisible.
5. For the axis_labels parameter, ON indicates that the labels are to be visible; OFF indicates that the
labels are to be invisible. The vertical and horizontal axis labels are controlled by this parameter. This
parameter is optional and if not entered, axis_labels will be displayed on the xy_plot.
6. Symbols are the graphic markers on a curve, identifying the data points. ON, the default, indicates
that the symbols on a particular curve will be visible, OFF indicates that the symbols will be invisible.
else 1
else
Allows you to use the IF, ELSE, ELSEIF, and END commands to execute a group of commands conditionally.
The execution of commands bracketed by IF and END depends on the value of an expression.
You can use the IF command with or without the ELSE command.
Format:
else
if condition = (expression)...end
if condition = (expression)...else...end
Example:
if condition=(DB_EXISTS ("MAR1"))
marker modify marker=mar1 location=2,0,0
else
marker create marker=mar1 location=2,0,0
end
In the above example, if the marker MAR1 exists, Adams View modifies its location. If the marker does not
exist, Adams View creates it and sets its location.
1. The question-mark/colon (?:) operator, used in a conditional expression, replaces an IF/ELSE
command that distinguishes one of two values. The expression consists of three parts: a condition
whose truth determines which value is selected, and two expressions for the values.
condition expression ? expression a : expression b
When evaluated, the conditional operator takes on one of the two values. The expression that comes
before the question-mark is interpreted as boolean-valued. If it is true (non-zero), then expression a
is used as the value of the conditional operator, otherwise expression b is used as the value.
For example, consider the commands below:
if condition = (variable_a < variable_b)
variable set variable = variable_min real = (EVAL(variable_a))
else
variable set variable = variable_min real = (EVAL(variable_b))
end
This can be expressed more concisely by using a ?: conditional operator:
variable set variable = variable_min &
real = (EVAL((variable_a < variable_b)? variable_a : variable_b))
elseif 1
elseif
You can nest any combination of looping (FOR/END, WHILE/END) and conditional constructs
(IF/ELSEIF/ELSE/END).
Note: As with all Adams View commands, you can use the IF, ELSE, ELSEIF, and END commands
on the command line, in macros, and in command files.
Format:
elseif
if condition = (expression)
elseif condition = (expression)
else (optional)
end
Example:
! Bodies
variable create variable=object_type string=(eval(DB_TYPE(.MDI.obj)))
if condition=(object_type == "marker")
interface command_builder command="marker modify marker" initial=(.MDI.obj)
elseif condition=(object_type == "point")
interface dialog display dialog=.gui.main_objecttable parameter="Points"
elseif condition=(object_type == "flexible_body")
interface dialog display dialog=.gui.flx_dia_panel parameter=(.MDI.obj)
! Constraints - complex joints
elseif condition=(object_type == "coupler" )
interface dialog display dialog=.gui.coupler_cremod parameter=(.MDI.obj)
elseif condition=(object_type == "gear" )
interface command_builder command="constraint modify complex_joint gear"
initial=(.MDI.obj)
! Constraints - Higher Pair contact

elseif condition=(object_type == "curve_curve" )
interface command_builder command="constraint modify higher_pair_contact
curve_curve" init=(.MDI.obj)
elseif condition=(object_type == "point_curve" )
point_curve" init=(.MDI.obj)
end
The above example illustrates how to use ELSEIF to determine the type of object and then perform an
operation on the object, based on the object's type. The example assumes that an Adams View variable named
.mdi.org exists and its type is database object.
Description:

Condition Expression If the expression evaluates to a non-zero value, Adams View
executes the commands following the IF or ELSEIF
command up to the ELSE, when present, or the END, if
you do not use the ELSE. If the expression evaluates to zero
and you used ELSE, Adams View executes the commands
between the ELSE and the END commands.
Tips:
1. You can have any number of ELSEIF CONDITION commands.
else
end
real = (EVAL((variable_a < variable_b)? variable_a :
variable_b))
end 1
end
Note: As with all Adams View commands, you can use the IF, ELSE, ELSEIF, and END commands
on the command line, in macros, and in command files.
Format:
end
elseif condition = (expression)
else (optional)
end
Example:
! Bodies
variable create variable=object_type string=(eval(DB_TYPE(.MDI.obj)))
if condition=(object_type == "marker")
interface command_builder command="marker modify marker" initial=(.MDI.obj)
elseif condition=(object_type == "point")
interface dialog display dialog=.gui.main_objecttable parameter="Points"
elseif condition=(object_type == "flexible_body")
interface dialog display dialog=.gui.flx_dia_panel parameter=(.MDI.obj)
! Constraints - complex joints
elseif condition=(object_type == "coupler" )
interface dialog display dialog=.gui.coupler_cremod parameter=(.MDI.obj)
elseif condition=(object_type == "gear" )
interface command_builder command="constraint modify complex_joint gear"
initial=(.MDI.obj)
! Constraints - Higher Pair contact
elseif condition=(object_type == "curve_curve" )
curve_curve" init=(.MDI.obj)
elseif condition=(object_type == "point_curve" )
point_curve" init=(.MDI.obj)
end
The above example illustrates how to use ELSEIF to determine the type of object and then perform an
operation on the object based on the object's type. The example assumes that an Adams View variable named
.mdi.org exists and its type is database object.
entity 1
entity attributes
entity
entity attributes
Allows you to modify the attributes of an entity in the model database.
The display attributes of the entities in the model database like icon size, visibility, name_visibility,
transparency, color, line properties, and dependent properties are edited using this command.
Format:
entity attributes
entity_name = an existing entity
type_filter = ent
expr_visibility = integer
transparency = integer
lod = integer
color = an_exisitng_color
line_thickness = real
line_type = line_style
Example:
entity attributes &
entity_name = .copy_of_model.pendulum &
type_filter = part &
size_of_icons = 20&
visibility = on &
name_visibility = on &
transparency = 50 &
lod = 100 &
entity attributes
entity attributes &

color = .colors.CYAN &
entity_scope = all_color &
line_thickness = .1 &
line_type = dotdash &
active = on &
Description:

entity_name An Existing Entity Specifies the name of an existing entity
type_filter Ent Specifies the types of objects allowed
size_of_icons Length Specifies the size of icon in modeling
units
scale_of_icons Real Specifies unit-less scale factor for
existing size of icons
expr_visibility Integer
visibility On_off_with_toggle Specifies the visibility of graphic icons
name_visibility On_off_with_toggle Specifies the visibility of the entity
names
transparency Integer Specifies the transparency level for
graphic entities
lod Integer Specifies the level of details for shells
color An_exisitng_color Specifies the color of the modeling
entities
entity_scope Color_scope Specifies the control of color
modification for graphic entity
line_thickness Real Specifies the line thickness for entity
outline
line_type Line_style Specifies the line type for a curve
active On_off_no_opinion Specifies whether or not the element is
active
dependents_active On_off_no_opinion Specifies the dependent element’s active
status
entity 3
entity attributes
1. The ‘entity_name’ specifies any existing database entity. You may identify a database entity by typing
its name or by picking it from the screen. If the database 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 database entity is
displayed. If you created the database entity by reading an Adams data set or graphics file, the database
entity name is the first three letters of the Adams object, followed by the Adams data set database
entity ID number. For example, the name of ADAMS PART/101 is PAR101. If you created the
database entity during preprocessing, you will have given it a name at that time. If the database entity
is available by default, you may identify it by entering only its name. If it is not, you must enter its
full name. For example, to identify a part under an analysis, you may need to enter the analysis name
as well. You may specify the part named par101 from the analysis named test by entering
"/test/par101". If you type a "?", Adams Adams View will list the database entities available by default.
You must separate multiple database entity names by commas. If the database entity is visible in one
separate multiple database entity picks by commas.
2. The ‘type_filter’ specifies the type of objects allowed. When specifying the objects for this operation
a wild cards can be used, which may result in too many objects being found. For example, if all the
parts for model MOD1 are desired, specifying .MOD1.* will get not only the parts, but all children
of the model, like joints, forces, etc. Using the parameter TYPE_FILTER=part will result in only
the parts being processed by this command.
3. Size of icons specifies the size, in modeling units, the Adams View icons will appear in. If no initial
size is specified for Adams View icons, the default size will be one modeling LENGTH unit. For
example, if the modeling units are K/M/S, a part axes icon will have triad legs of one meter in length.
will use the size specified. If the model has an SIZE_OF_ICONS set, and a part under that model
has a different SIZE_OF_ICONS, the model's ICONS_SIZE will take precedence. For Example:
For Example:
4. Scale of icons specifies a unit-less scale factor to apply to the current icon size.If no initial size is
specified for Adams View icons, the default size will be one modeling LENGTH unit. For example,
if the modeling unitsare K/M/S, a part axes icon will have triad legs of one meter in length. When
you specify SCALE_OF_ICONS, a new size is calculated by multipling the current size, by the scale,
and storing the product as the new ICON_SIZE.
entity attributes
5. Visibility specifies the visibility of graphic entities. The visibility parameter is used to control whether
graphic entities, such as markers, joints, and parts, are to be drawn in an Adams View viewport. The
legal values for this parameter are: ON, OFF, and TOGGLE. ON will make the desired entity
6. The NAME_VISIBILITY parameter provides control over the visibility of the view name displayed
at the top center position of a given view. The legal values of this parameter are ON and OFF. This
is an optional parameter and if not entered, the name will be visible (i.e. will be ON). Note that if the
visibility of the view name is turned off, the only indication that a view is "active" will be the color of
the viewport border. This could be a problem on a black and white monitor.
7. The ‘transparency’ sets the level of transparency of a graphic entity. The legal values range from 0 to
100, where a value of 100 will make the graphic entity fully transparent. The ‘lod’ gives the level of
details for a shell object. The range of values is from 0 to 100.
8. The color specifies the color the modeling entity should be drawn in. Adams View allows you to
specify the following colors for modeling entities: BLACK, WHITE, RED, GREEN, BLUE, CYAN,
MAGENTA, YELLOW, and NO_COLOR Specifying 'NO_COLOR' for a modeling entity,
instructs Adams View to use the default color for this entity, if there is no color present in its parent
modeling entity.
Example 1:
.model -------------------------NO_COLOR
.part---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part---------------------- NO_COLOR
9. The ENTITY_SCOPE parameter is used to control how a color modification is to affect a particular
graphic entity. The legal values for this parameter are FILL_COLOR, EDGE_COLOR,
shaded (they include sides of a cylinders, frustums, boxes, etc.). The EDGE_COLOR is the color of
be shaded. The OUTLINE_COLOR represents the color of the lines that make up those graphics
entity 5
entity attributes
that cannot be shaded or filled, like an outline graphic statement consisting of two points or the coil
of a springdamper. Finally, the ALL value indicates that all three entity types, FILL_COLOR,
EDGE_COLOR, and OUTLINE_COLOR will be affected by the color change. The
ENTITY_SCOPE parameter is optional and if not entered, will be set to FILL_COLOR.
10. The line thickness specifies the thickness of the line, whereas, the ‘line type’ parameter allows the
selection of the line type for a curve. The line type describes how the line will look when displayed
on a plot. Adams View supports solid, dash, dotdash, and dot.
Line Type Appearance
solid _______________
dash _ _ _ _ _ _ _ _
dotdash . _ . _ . _ . _
dot . . . . . . . .
11. When you set ACTIVE=NO, that element is written to the data set as a comment. When you set
the ACTIVE attribute on an object, you are also setting it on the children of the object. If you set
ACTIVE=YES on the marker, after setting activation on the part. The DEPENDENTS_ACTIVE
parameter acts in the same fashion, but sets the ACTIVE attribute for the dependents all the way
down the dependency chain. For example, if you execute the following command:
then JOI1 will be deactivated. Also, if the joint JOI1 is referenced in a request function, or if the I
marker is referenced by a request, then the request will be deactivated. Propagation of activation status
through groups is as if each element were to have its activation status changed indvidually.
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
12. EXPR_ACTIVE allows you to set the activity of the group using an integer value, which allows
parameterization. Adams View at this time does not allow expressions when specifying option lists.
To allow the activity of a group to be set parametrically, the parameter EXPR_ACTIVE was added
to the GROUP CREATE and GROUP MODIFY commands. This parameter takes an integer value.
If the value is not set, either because the parameter was never used, or it was unset with the (none)
entity copy
expression, then the standard activity rules apply. If the EXPR_ACTIVE is set to an expression that
evaluates to zero (FALSE), the objects in the group will be in active (and will not be included by
Adams Solver in any simulation). If the value is the default or non-zero (TRUE), then the objects
will be active (and will be included in simulations).
entity copy
Allows you to copy the entities from a model database.
The entities in the model database like system_defaults, gui, sim_preferences, colors, icons, MDI,
SELECT_LIST, materials, VISIBILITY_LIST, model and plots can be copied as a new entity.
Format:
entity copy
new_entity_name = a new entity
Example:
entity copy &
entity_name = model_1 &
new_entity_name = copy_of_model
Description:

new_entity_name A New Entity Specifies a new name for an existing entity
entity ID number. For example, the name of Adams PART/101 is PAR101. If you created the
entity 7
entity delete
"/test/par101". If you type a "?", Adams View will list the database entities available by default. You
must separate multiple database entity names by commas. If the database entity is visible in one of
your views, you may identify it by picking on any of the graphics associated with it. You need not
2. The ‘new_entity_name’ is the name of a new entity to which the existing entity is copied.
entity delete
Allows you to delete the entity in the model database.
The entities in the model database like parts, joints, forces, markers, etc. can be deleted by using this
command applying a type filter as needsed
Format:
entity delete
type_filter = ent
Example:
entity delete &
entity_name = pendulum &
type_filter = part
Description:

entity name is the first three letters of the Adams object, followed by the ADAMS data set database
entity ID number. For example, the name of Adams PART/101 is PAR101. If you created the
entity modify
2. The ‘type_filter’ specify the type of objects allowed. When specifying the objects for this operation a
wild cards can be used, which may result in too many objects being found. For example, if all the parts
for model MOD1 are desired, specifying .MOD1.* will get not only the parts, but all children of the
model, like joints, forces and so on. Using the parameter TYPE_FILTER=part will result in only the
parts being processed by this command.
entity modify
Allows you to modify the entity in the model database.
The entities in the model database like parts, joints, simulation, measures, etc. can be modified or renamed
by using this command.
Format:
entity modify
new_entity_name = a new entity
adams_id = adams_id
comments = string
Example:
entity modify &
entity_name = .model_1.PART_3 &
new_entity_name = pendulum &
adams_id = 3 &
comments = simple_pendulum
Description:

new_entity_name A New Entity Specifies a new name for an existing entity
adams_id Adams_id Specifies an integer used to identify this element in Adams
database
comments String Specifies comments on the element, if any
entity 9
entity modify
1. The ‘entity_name’ specifies any existing database entities. You may identify a database entity by
typing its name or by picking it from the screen. If the database 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 database entity is
entity ID number. For example, the name of Adams Part/101 is PAR101. If you created the database
entity during preprocessing, you will have given it a name at that time. If the database entity is
available by default, you may identify it by entering only its name. If it is not, you must enter its full
name. For example, to identify a part under an analysis, you may need to enter the analysis name as
well. You may specify the part named par101 from the analysis named test by entering
2. The ‘new_entity_name’ will rename the existing entity.
3. The ‘adams_id’ specifies an integer used to identify this element in the Adams data file. When you
use the FILE ADAMS_DATA_SET WRITE command, Adams View writes an Adams data file for
4. The parameter ‘comments’ specifies comments for the object being created or modified. When an
Adams Solver data file (.adm) is read into Adams View, all comments associated with a statement
(from the end of the previous statement through the end of the current statement) are stored with
the object. Comments in the data file can be associated with model. These comments must follow the
title statement and be followed by the comment 'END OF MODEL COMMENTS'. This string
must be uppercase. When an Adams Solver data file is written, the comments for an object are written
before the statement corresponding to the object.
entity modify
executive_control 1
executive_control attributes sensor
executive_control
Allows you to change the color and visibility of a sensor icon.
Format:
Sensor_name = existing sensor
Visbility = on/off/no_opinion/toggle
Color = an existing color
Active = on/off/no_opinion/toggle
Dependents_active = on/off/no_opinion/toggle
Example:
Executive_control attributes sensor &
Sensor_name = SENSOR_1 &
Visbility = on &
Color = RED &
Active = on &
Dependents_active = off
Description:

Sensor_name Existing sensor name Specifies an existing sensor.
Visibility On/off/no_opinion/toggle Specifies the visibility of graphic entities.
Color Existing color Specifies the color the modeling entity should
be drawn in.
Active On/off/no_opinion/toggle When you set ACTIVE=NO, that element is
written to the data set as a comment.
Dependents_active On/off/no_opinion/toggle Sets the active attributes for the dependents, all
the way down the dependency chain.
1. You may identify a sensor by typing its name or by picking it from the screen.
Since sensors do not have a geometric position, Adams View displays sensor icons at or near the model
origin. If the sensor icon is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the sensor icon is displayed.
If you created the sensor by reading an Adams data set, the sensor name is the letters SEN followed
by the Adams data set sensor ID number. The name of Adams SENSOR/101 is SEN101, for
example. If you created the sensor during preprocessing, you gave it a name at that time.
If a sensor is owned by the default model, you may identify it by entering its name only. If it is not,
you must enter its full name. To identify a sensor under a different model, for instance, you may need
to enter the model name as well. For example, you may specify sensor 'fluid_volume_limit' from
model 'hydro' by entering ".hydro.fluid_volume_limit'". If you type a "?", Adams View will list the
sensor available by default.
You must separate multiple sensor names by commas.
If the sensor is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple sensor picks by commas.
Example 1: .model -------------------------NO_COLOR .part
---------------------- RED .geometry(circle) ------- NO_COLOR
---------------------- RED .geometry(circle) ------- BLUE
---------------------- NO_COLOR .geometry(circle) ------- BLUE
4. When you set the ACTIVE attribute on an object, you are also setting it on the children of the object.
If you set ACTIVE=NO on a part, but wish for a marker on that part to be on, then you must
for the dependents, all the way down the dependency chain. For example, if you execute the
following command:
executive_control 3
executive_control copy sensor
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control

Allows you to copy a sensor.
Format:
sensor_name = Name of existing sensor
sew_sensor_name = Name of new sensor
Example:
executive_control copy sensor &
sensor_name = SENSOR_1 &
sew_sensor_name = My_Copied_Sensor
Description:

Sensor_name Existing sensor name Specifies the sensor to be copied
New_sensor_name Name of new sensor Specifies the name of the new sensor. You may use
this name later to refer to this sensor.
executive_control create sensor
by the Adams data set sensor ID number. For example, the name of Adams SENSOR/101 is
SEN101. If you created the sensor during preprocessing, you will have given it a name at that time.
If a sensor is owned by the default model, you may identify it by entering only its name. If it is not,
associated with it.

Allows you to create a sensor. You may reverse this creation at a later time with an UNDO command.
Sensors are contained in a model. Before creating sensors, you must use the 'MODEL CREATE' command
to create a model.
A SENSOR monitors the Adams simulation for a user-defined event and effects a set of simulation controls
when the event occurs. The simulation controls and modifies the integration and the output step sizes, to
output additional diagnostic information, and to alter the simulation end time.
You define the event by creating a function and comparing it against a given value. The function the
SENSOR uses may depend on distance, velocity, acceleration, and force between markers, on user-defined
variables, and on simulation time. Adams evaluates the function after every successful integration step when
doing dynamic analysis and after every successful solution step when doing other types of analysis. To define
the function, use a FUNCTION expression or a user-written subroutine.
Format:
sensor_name= String
adams_id = geom._id
comments = string
compare = GE/EQ/LE
codgen = on/off
executive_control 5

dt= real
halt = on/off
bisection= real
time_error= real
value= real
error = real
angular_value= real
angular_error= real
print= on/off
restart= on/off
return= on/off
stepsize= real
yydump= on/off
function= Function
user_function= real
routine= string
evaluate= Run time function
user_evaluate= real
evaluate_routine= string
Example:
executive_control create sensor &
sensor_name = MY_SENSOR &
function = "1E2+3.4+6" &
comments = "Example Sensor" &
compare = ge &
codgen = on &
halt = on &
value = 50.9
Description:

sensor_name String Specifies the name of the new sensor. You may use this name
later to refer to this sensor.
data file.
compare GE, EQ, LE Specifies what kind of comparison is to be made to initiate the
action by the SENSOR.
codgen ON/OFF Specifies that Adams is to generate a new pivot sequence for
matrix factorization when the event Adams is sensing has the
specified relationship to VALUE.
Dt Real Specifies that the time between consecutive output steps
should be redefined. This is done when Adams first senses that
the FUNCTION specified has the same relationship as
specified to VALUE. Adams uses this value until it is changed.
halt On/OFF Specifies that execution should be terminated when the
FUNCTION that Adams is sensing, has the specified
relationship to VALUE.
value Real Specifies the non-angular VALUE you want to relate to the
FUNCTION that Adams is sensing.
error Real Specifies the absolute non-angular value of allowable error
between VALUE and the value of the FUNCTION that
Adams is sensing.
angular_value Real Specifies the angular VALUE you want to relate to the
angular_error Real Specifies the absolute angular value of allowable error between
VALUE and the value of the FUNCTION that Adams is
sensing.
Print On/OFF Specifies that Adams should write data to the request, graphics,
and output files when the FUNCTION that Adams is sensing,
has the specified relationship to VALUE.
restart On/OFF Specifies that Adams should restart the integration when the
FUNCTION that Adams is sensing has the specified
relationship to VALUE. Adams reinitializes the integration
step size to HINIT and reduces the integration order to one.
return On/OFF Specifies that Adams should stop the simulation and return to
the command level, when the FUNCTION that Adams is
sensing has the specified relationship to VALUE.
executive_control 7

stepsize Real Specifies that Adams should redefine the trial integration step
size when the FUNCTION that Adams is sensing has the
specified relationship to VALUE. This change is temporary
and lasts only for the next step. If this step size is unsatisfactory
for convergence or if it generates too much error, Adams tries
one or more different step sizes.
Yydump On/OFF Specifies that Adams should dump the state variable vector
when the FUNCTION that Adams is sensing has the specified
function Function Specifies a FUNCTION expression to define the sensor.
user_function Real Specifies a list of constants that are to be passed to a user-
written subroutine to define the sensor.
1. Adams View will not allow you to have two sensors with the same name, so you must provide a unique
name.
You may, ofcourse, delete this name and use your own. The form of a full name is:
be assigned to it.
3. The COMPARE type can take on the values EQ, GE, or LE:
EQ initiates action when the FUNCTION that Adams is sensing is from (VALUE - ERROR) to
(VALUE + ERROR).
GE initiates action when the FUNCTION that Adams is sensing is greater than VALUE - ERROR.
LE initiates action when the FUNCTION that Adams is sensing is less than VALUE + ERROR.
4. The Codgen parameter may help the integrator to produce more accurate data or to proceed more
smoothly at troublesome points in time. Adams generates a pivot sequence for matrix factorization
before starting the simulation. Then Adams does not generate a new pivot sequence unless the
CODGEN argument is used or it is necessary to reach convergence.
5. The easiest way to enter a function expression in Adams View is to use the text editor in combination
button at the upper right side of the text editor. If there is a syntax error, a message is printed and the
verification.
The remainder of this explanation will cover the components of FUNCTION expressions as
summarized in the following table.
Components Examples
Numbers FUNCTION = 1E2 + 3.4 + 6
Operators FUNCTION = 3*6/2 + 3 - 2**2
System Constants FUNCTION = PI + 20
System Variabless FUNCTION = AX(1040, 2010)
Arithmetic Ifs FUNCTION = IF(DX(3, 5): -1, 0, 1)
Fortran-77 Functions FUNCTION = ABS(NUM) - 6
Blanks FUNCTION = 1 + 2
Continuation Commas FUNCTION = 1 + 1 + 1 + 1 + 1 + 1 , + 1 + 1 + 1 + 1 + 1 + 1 + 1
Adams Functions FUNCTION = POLY(0, 0, 6.28)
NUMBERS
FUNCTION expressions can include integers, real numbers, and exponents. In other words, any
numbers that are legal in Adams are legal in a FUNCTION expression.
OPERATORS
executive_control 9
In a FUNCTION expression, Adams allows any of the operators **, *, /, +, and -. Adams executes
these operators according to the following precedence rules:
• From greatest to least, the operators have the following priorities. ** then * / then + -. In other
words, Adams executes exponentiation (**) before all other operators and executes
multiplication (*) and division (/) before addition (+) and subtraction (-).
• When a statement has operators of the same priority, Adams executes them from left to right.
• You can use parentheses to alter the precedence of operators. For example, in the equation
FUNCTION = (1-TIME)*30/PI
Adams subtracts TIME from one before it performs multiplication and division.
SYSTEM CONSTANTS
You can include the following system constants in a FUNCTION expression:
• PI Value of pi (to eighteen significant digits)
• DTOR Value of pi/180 for converting degrees to radians
• RTOD Value of 180/pi for converting radians to degrees
The following example of a FUNCTION with a system constant, multiplies the system constant PI
by the displacement of marker 10 with respect to marker 14:
FUNCTION = PI*DM(10,14)
BLANKS
A FUNCTION expression can contain any number of blank spaces. Five consecutive blank spaces in
an expression do not terminate input of the expression (by indicating that what follows is a comment)
as they do in an Adams statement. However, you should remember these two restrictions.
• You cannot put a blank space in the middle of a number.
• Adams does not accept a blank space between a function and its left bracket. (This is true for
both, FORTRAN-77 functions and Adams functions.)
CONTINUATION COMMAS
You can use a comma to continue FUNCTION expressions. You can break the expression anywhere
except in the middle of a number, in the middle of a name, or between a function and its left bracket.
Put a continuation comma in column one of the following line before the rest of the expression. If
you break the expression at a comma that is part of the expression, you must use both, the expression
comma and the continuation comma. You may use more than one continuation comma to extend
an expression over several lines.
FUNCTION BUILDER
The FUNCTIONS button at the right side of the Adams View text editor provides a means for
constructing an Adams function string. These functions are briefly described below. Upon picking
the FUNCTIONS button, you will be presented with the list of available functions in the "selection
window". After you select the desired function, a panel will appear with fields representing the various
parameters for the function. You will have full access to on-line help with this panel just like you have
with regular panels. After you have completed the panel and selected the DONE button on the panel,
the function string will be constructed and inserted at the current text cursor location in the text edit
window.
SYSTEM VARIABLES
A FUNCTION expression may access the current value of a system variable and use the value in
computations. These values are accessed through a collection of functions. The accessible system
variables include the following: Time, Mode, Displacements (Translational and Rotational),
Velocities (Translational and Rotational), Accelerations (Translational and Rotational), Forces
(Translational and Rotational), and User-defined variables. Invoke the text edit window and pick the
FUNCTIONS button to get a list of functions that can be accessed.
In general, you use a function character string (such as DM, VX, or FZ) and a list of values (e.g. i1,
i2, and i3) to access a system variable in an expression. For example, the value i1 may be the name of
the marker for which you want to measure a quantity (such as displacement, velocity, acceleration, or
force), i2 is the name of the marker with respect to which you want to measure the quantity, and i3
is the name of the marker you want to use to resolve the components of the quantity. If you do not
specify marker i3, Adams computes the result in the ground reference frame.
ARITHMETIC IFS
Arithmetic IFs allow you to conditionally define FUNCTION. The format for arithmetic IFs is as
follows:
IF (expression 1: expression 2, expression 3, expression 4)
Adams evaluates expression 1. If expression 1 is less than zero, the arithmetic IF equals expression 2;
if expression 1 equals zero, the arithmetic IF equals expression 3; and if expression 1 is greater than
zero, the arithmetic IF equals expression 4.
A FUNCTION expression with an arithmetic IF and its four expressions, is given below:
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
If the radial velocity between markers 10 and 31 is less than or equal to zero, the value of the
FUNCTION expression is zero; but if the radial velocity between markers 10 and 31 is greater than
zero, the value of the FUNCTION expression is six hundred.
In some ways, you may treat IF as a variable. For example, you can place it anywhere in the
expression. In addition, you can nest arithmetic IFs nine levels deep.
FORTRAN-77 FUNCTIONS
You can use the FORTRAN functions ABS, ATAN, ATAN2, COS, EXP, LOG, LOG10, MIN,
MAX, SIN, SQRT, and TAN in your expression. For more information about these functions, see
a FORTRAN reference manual. Invoke the text edit window and pick the FUNCTIONS button to
get a list of functions that can be accessed.
ADAMS FUNCTIONS
In general, an Adams function evaluates a mathematical equation and returns a value to your
FUNCTION expression. The following table lists all the Adams functions and their purposes.
Invoke the text edit window and pick the FUNCTIONS button to make a list of functions that can
be accessed.
executive_control 11
executive_control delete sensor
Names Purposes
AKISPL Accesses the data in a SPLINE statement and uses the Akima cubic method
to fit a cubic curve(a spline) to the data.
BISTOP Evaluates a force restricting displacement of a part in two opposite
directions
CHEBY Evaluates a Chebyshev polynomial
CUBSPL Accesses the data in a SPLINE statement and uses the traditional cubic
method to fit a cubic curve (a spline) to the data.
FORCOS Evaluates a Fourier cosine series
FORSIN Evaluates a Fourier sine series
HAVSIN Evaluates a haversine function
IMPACT Evaluates a force restricting displacement of a part in one direction
POLY Evaluates a polynomial
SHF Evaluates a simple harmonic function
STEP Approximates a step function with a cubic polynomial
6. To define the sensor with a user-written subroutine, enter the values (r1[,...,r30]) that you want
Adams to pass to the user-written subroutine SENSUB. The Adams Users Manual discusses more
details about the use of the "SENSUB" subroutine.
Cautions:
1. The SENSOR function must be continuous because Adams tries to adjust the step size to find the
exact time the sensor becomes active. This process is inaccurate and time consuming when the
function is discontinuous. For that reason, functions of time or displacements work best for sensors;
functions of velocities, accelerations, and forces are less desirable.
Any sensor will set the simulation control each time Adams tests the sensor and finds it to be active.
Adams tests the sensor after every successful time step. If the sensor becomes active, Adams sets the
simulation control and does not test the sensor again until it has taken three successful time steps.
Then Adams again tests the sensor after every successful time step.
If you want Adams to take an action, you should be sure to include one of the action arguments
(CODGEN, DT, HALT, PRINT, RESTART, RETURN, STEPSIZE, and YYDUMP) in the
SENSOR definition. The sensor can become active even if one of the action arguments is not
included. However, Adams does not, of course, take any action unless one is specified.

Allows you to delete a sensor. You must enter the name of the sensor you wish to delete by either picking it
from the screen or specifying the full name.
executive_control modify sensor
Format:
Sensor_name= Name of existing sensor
Example:
executive_control delete sensor &
Sensor_name = SENSOR_1
Description:

Sensor_name Existing sensor name Specifies the sensor to delete
by the Adams data set sensor ID number. For example, the name of Adams SENSOR/101 is
SEN101. If you created the sensor during preprocessing, you will have given it a name at that time.
If a sensor is owned by the default model, you may identify it by entering only its name. If it is not,
associated with it.

Allows you to modify a sensor. You may reverse this creation at a later time with an UNDO command.
Sensors are contained in a model. Before creating sensors, you must use the 'MODEL CREATE' command
to create a model.
A SENSOR monitors the Adams simulation for a user-defined event and effects a set of simulation controls
when the event occurs. The simulation controls and modifies the integration and the output step sizes, to
output additional diagnostic information, and to alter the simulation end time.
You define the event by creating a function and comparing it against a given value. The function the
SENSOR uses may depend on distance, velocity, acceleration, and force between markers, on user-defined
variables, and on simulation time. Adams evaluates the function after every successful integration step when
doing dynamic analysis, and after every successful solution step when doing other types of analysis. To define
the function, use a FUNCTION expression or a user-written subroutine.
Format:
sensor_name= String
new_sensor_name = string
adams_id = geom._id
comments = string
compare = GE/EQ/LE
codgen = on/off
dt = real
halt = on/off
bisection= real
time_error= real
value= real
error = real
angular_value= real
angular_error= real
print= on/off
restart= on/off
return= on/off
stepsize= real
yydump= on/off
function= Function
user_function= real
routine= string
evaluate= Run time function
user_evaluate= real
evaluate_routine= string
Example:
executive_control modify sensor &
sensor_name = MY_SENSOR &
new_sensor_name = HALT_WHEN_F1_REACHED&
function = "1E2+3.4+6" &
comments = "Example Sensor" &
compare = ge&
codgen = on &
halt = on &
value = 50.9
Description:

sensor_name String Specifies the name of the sensor you wish to modify
New_sensor_name String Specifies the name of the new sensor. You may use this name
later to refer to this sensor.
data file.
comments String Specifies comments for the object being created or modified
compare GE, EQ, LE Specifies what kind of comparison is to be made to initiate the
action by the SENSOR.
codgen ON/OFF Specifies that Adams is to generate a new pivot sequence for
matrix factorization when the event that Adams is sensing has
the specified relationship to VALUE.
Dt Real Specifies that the time between consecutive output steps should
be redefined. This is done when Adams first senses that the
FUNCTION specified has the same relationship as specified to
VALUE. Adams uses this value until it is changed.
halt On/OFF Specifies that execution should be terminated when the
value Real Specifies the non-angular VALUE you want to relate to the
error Real Specifies the absolute non-angular value of allowable error
between VALUE and the value of the FUNCTION that Adams
is sensing.

angular_value Real Specifies the angular VALUE you want to relate to the
angular_error Real Specifies the absolute angular value of allowable error between
VALUE and the value of the FUNCTION that Adams is
sensing.
Print On/OFF Specifies that Adams should write data to the request, graphics,
and output files when the FUNCTION that Adams is sensing
has the specified relationship to VALUE.
restart On/OFF Specifies that Adams should restart the integration when the
relationship to VALUE. Adams reinitializes the integration step
size to HINIT and reduces the integration order to one.
return On/OFF Specifies that Adams should stop the simulation and return to
the command level when the FUNCTION that Adams is
sensing has the specified relationship to VALUE.
stepsize Real Specifies that Adams should redefine the trial integration step
size when the FUNCTION that Adams is sensing has the
specified relationship to VALUE. This change is temporary and
lasts only for the next step. If this step size is unsatisfactory for
convergence or if it generates too much error, Adams tries one or
more different step sizes.
Yydump On/OFF Specifies that Adams should dump the state variable vector when
the FUNCTION that Adams is sensing has the specified
function Function Specifies a FUNCTION expression to define the sensor.
user_function Real Specifies a list of constants that are to be passed to a user-written
subroutine to define the sensor.
1. Adams View will not allow you to have two sensors with the same name, so you must provide a unique
name.
of course, delete this name and use your own. The form of a full name is:
be assigned to it.
3. The COMPARE type can take on the values EQ, GE, or LE:
EQ initiates action when the FUNCTION that Adams is sensing is from (VALUE - ERROR) to
(VALUE + ERROR).
GE initiates action when the FUNCTION that Adams is sensing is greater than VALUE - ERROR.
LE initiates action when the FUNCTION that Adams is sensing is less than VALUE + ERROR.
4. The Codgen parameter may help the integrator to produce more accurate data or to proceed more
smoothly at troublesome points in time. Adams generates a pivot sequence for matrix factorization
before starting the simulation. Then Adams does not generate a new pivot sequence unless the
CODGEN argument is used or it is necessary to reach convergence.
verification.
summarized in the following table:
Components Examples
System Variables FUNCTION = AX(1040, 2010)
NUMBERS
OPERATORS
• From greatest to the least, the operators have the following priorities. ** then * / then + -. In other
• You can use parentheses to alter the precedence of operators. For example, in the equation,
SYSTEM CONSTANTS
The following example of a FUNCTION with a system constant multiplies the system constant PI
BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
window". After you select the desired function, a panel will appear with fields representing the
various parameters for the function. You will have full access to on-line help with this panel just like
you have with regular panels. After you have completed the panel and selected the DONE button on
the panel, the function string will be constructed and inserted at the current text cursor location in
the text edit window.
SYSTEM VARIABLES
ARITHMETIC IFS
Arithmetic IFs allow you to conditionally define FUNCTION. The format for arithmetic IFs
follows.
A FUNCTION expression with an arithmetic IF and its four expressions is as given below:
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
ADAMS FUNCTIONS
be accessed.
Names Purposes
AKISPL Accesses the data in a SPLINE statement and uses the Akima cubic method to fit
a cubic curve(a spline) to the data.
BISTOP Evaluates a force restricting displacement of a part in two opposite directions
CUBSPL Accesses the data in a SPLINE statement and uses the traditional cubic method to
fit a cubic curve (a spline) to the data.
IMPACT Evaluates a force restricting displacement of a part in one direction.
executive_control set dynamics_parameters coord_partitioning_parameters
6. To define the sensor with a user-written subroutine, enter the values (r1[,...,r30]) that you want
Adams to pass to the user-written subroutine SENSUB. The Adams Users Manual discusses more
details about the use of the "SENSUB" subroutine.
Cautions:
1. The SENSOR function must be continuous because Adams tries to adjust the step size to find the
exact time the sensor becomes active. This process is inaccurate and time consuming when the
function is discontinuous. For that reason, functions of time or displacements work best for sensors;
functions of velocities, accelerations, and forces are less desirable.
Any sensor will set the simulation control each time Adams tests the sensor and finds it to be active.
Adams tests the sensor after every successful time step. If the sensor becomes active, Adams sets the
simulation control and does not test the sensor again until it has taken three successful time steps.
Then Adams again tests the sensor after every successful time step.
If you want Adams to take an action, you should be sure to include one of the action arguments
(CODGEN, DT, HALT, PRINT, RESTART, RETURN, STEPSIZE, and YYDUMP) in the
SENSOR definition. The sensor can become active even if one of the action arguments is not
included. However, Adams does not, of course, take any action unless one is specified.
executive_control set dynamics_parameters

coord_partitioning_parameters
The COORD_PARTITIONING_PARAMETERS command allows you to control the coordinate
partitioning algorithm for the Adams-Bashforth-Moulton integrator. This command affects the coordinate
partitioning as well as the iterative solutions for the dependent displacements and the accelerations and
Lagrange multipliers.
Description:

model_name An existing model Specifies the model to be modified. You use this parameter
to identify the existing model to be affected with this
command.
dd_relative_error Real Specifies the relative error tolerance for the iterative
solution of the displacements of the dependent coordinates.
The relative error for the displacements will be bounded by
a minimum of DD_RELATIVE_ERROR and the
integration error tolerance.
dd_absolute_error Real Specifies the absolute error tolerance for the iterative
solution of the displacements of the dependent coordinates.
The absolute error for the displacements will be bounded
by a minimum of dd_absolute_error and 1/100-th of the

dd_maximum_iterati Integer Specifies the maximum number of iterations allowed for
ons the modified Newton-Raphson algorithm to converge to
the displacements for the dependent coordinates.
dd_pattern_for_jacob Yes/No Indicates the pattern of yes’s and no’s for reevaluating the
ian Jacobian matrix during the modified Newton-Raphson
iterative solution for the displacements of the dependent
coordinates.
repartition_threshold Real Allows some control over the re-partitioning of coordinates
into independent and dependent coordinates.
al_relative_error Real Specifies the relative error tolerance for the iterative
solution of the accelerations and the Lagrange multipliers
(i.e. constraint forces).
al_absolute_error Real Specifies the absolute error tolerance for the iterative
solution of the accelerations and the Lagrange multipliers
(i.e. constraint forces).
al_maximum_iteratio Integer Specifies the maximum number of iterations allowed for
ns the modified Newton-Raphson algorithm to converge to
the accelerations and the Lagrange multipliers.
al_pattern_for_jacobi Yes/No Indicates the pattern of yes's and no's for reevaluating the
an Jacobian matrix during the modified Newton-Raphson
iterative solution for the accelerations and the Lagrange
multipliers.

scaling Yes/No No action will be taken if this parameter is not specified.
scale_factor Real Allows you to specify the amount to scale the geometry that
is read in from a Wavefront .obj file. The geometry will be
scaled uniformly in the x, y, and z directions.
watch_partitioning_p ERROR_IN_ITER Provides the user with a means for observing the progress of
erf ATION, the simulation by causing Adams to write information
NO_ERROR_IN_ about the performance of coordinate partitioning
ITERATION, calculations onto the screen.
FAILURE_IN_ITE
RATION,
NO_FAILURE_IN
_ITERATION,
CONDITION,
NO_CONDITIO
N,
REPARTITION,
NO_REPARTITI
ON, DOF,
NO_DOF, ALL,
NONE
associated with it.
2. In general, for efficiency reasons, the coordinates are re-partitioned whenever:
 A matrix inverse condition number gets too small
 The displacment iterations do not converge
 A part rotation occurs
 A matrix becomes numerically singular, or
 The unit energy ratio is less than its original value times the value of
REPARTITION_THRESHOLD.
executive_control set dynamics_parameters dynamic_solver
3. The relative error will be bounded by a minimum of AL_RELATIVE_ERROR and one tenth of the
4. The absolute error will be bounded by a minimum of AL_ABSOLUTE_ERROR and one tenth of
the integration error tolerance.
5. The WATCH_PARTITIONING_PERF only affects diagnostics, not results.
ERROR_IN_ITERATION: The value of the error and the component of the state vector,
contributing the most to the size of the error after every iteration of the algorithm of the dependent
displacements and for the accelerations and the constraint forces.
FAILURE_IN_ITERATION: The value of the error and the component of the state vector,
contributing the most to the size of the error when the algorithm for the dependent displacements
and for the accelerations and the constraint forces fails to converge.
CONDITION: An estimate of the condition number of the Jacobian matrix for the corrector
algorithm each time it is reevaluated.
REPARTITION: An indication that the current choice for the independent coordinates is no longer
acceptable and the coordinates will be re-partitioned.
DOF: A list of the degrees-of-freedom (i.e. the independent coordinates) each time the partitioning
is done.
ALL: All options are on.
NONE: All options are off.

dynamic_solver
The EXECUTIVE_CONTROL SET DYNAMICS_PARAMETERS DYNAMIC_SOLVER command
defines the two fundamental components of the mathematical methods for a dynamic solution: the form of
the equations and the integration algorithm.
executive_control set dynamics_parameters dynamic_solver
Description:

model_name An existing model Specifies the model to be modified. You use
this parameter to identify the existing model to
be affected with this command.
ordinary_differential_ Ode-type Causes Adams to reduce the equations
equations governing the dynamics of the problem to a
system of ordinary differential equations. The
value assigned to the argument specifies the
algorithm for doing the reduction. For the 7.0
release, COORDINATE_PARTITIONING is
the only option available.
ode_integrator ODE_INTEGRATOR Specifies the numerical method for integrating
the ODEs. For the 7.0 release, the value,
Adams, is the only option available.
differential_and_alge STANDARD_INDEX_THRE Causes Adams to integrate the full set of Euler-
braic_equations E/LAGRANGIAN_CONSTR Lagrange differential and algebraic equations.
AINED/ The value assigned to this argument indicates
STABILIZED_INDEX_TWO/ the form of the equations.
PENALTY
dae_integrator BDF/BDF_FIXED Specifies the numerical method for integrating
the DAEs. For the 7.0 release, the value, BDF,
is the only option available.
associated with it.
2. For the 7.0 release, STANDARD_INDEX_THREE is the only option. The full system of 2n + m +
p differential equations consists of the following:
n Euler-Lagrange differential equations (one for each generalized coordinate);
m constraint equations;
n equations of the form x - u = 0 (one for each generalized coordinate) to reduce the differential
equations to first order; and
executive_control set dynamics_parameters integrator_parameters
p state equations, first-order differential equations, or other algebraic equations that may have been
added to the problem.

integrator_parameters
The EXECUTIVE_CONTROL SET DYNAMICS_PARAMETERS INTEGRATOR_PARAMETERS
command controls parameters common to multiple integrators.
Description:

model_name AN EXISTING Specifies the model to be modified. You use this parameter
MODEL to identify the existing model to be affected with this
command.
relative_error Real Specifies a relative error tolerance for the integrator
absolute_error Real Specifies the absolute error tolerance for the integrator.
The absolute error tolerance will by bounded by the value
of ABSOLUTE_ERROR.
error_scaling Real number Real number should be > 0. Can take 1-16 values.
continue_on_failure Yes/no When the CONTINUE_ON_FAILURE argument is set
to YES, it allows the code to continue the simulation with
a set of relaxed error tolerances when the specified
conditions cannot be met. Otherwise, when set to NO, the
control of the Adams simulation will be returned to the
command level.
step_maximum Integer The maximum number of integration steps that the code
will take between output steps.
init_time_step Real number Real number should be > 0
max_time_step Real number Real number should be > 0
min_time_step Real number Real number should be > 0
max_integrator_order Integer Integer should be greater than 0 and less than or equal to
12
executive_control set dynamics_parameters integrator_parameters

interpolate Yes/No Indicates whether interpolation is allowed. That is,
indicates whether the integrator can choose integration
steps independent of output steps and the interpolate
results for the output step times.
watch_integrator_per MONITOR, Provides the user with a means for observing the progress
f NO_MONITOR, of the simulation by causing Adams to write information
ERROR_IN_INTE about the status and performance of the integration to the
GRATOR, screen.
NO_ERROR_IN_I
NTEGRATOR,
FAILURE_IN_INT
EGRATOR,
NO_FAILURE_IN
_INTEGRATOR,
STEPSIZE,
NO_STEPSIZE,
NEWSTEP,
NO_NEWSTEP,
OUTPUT,
NO_OUTPUT,
ALL, NONE
reconcile ALL, Corrects interpolated results before Adams writes them to
DISPLACEMENTS the output files to satisfy the constraint equations.
, NONE
associated with it.
2. The relative error tolerance will be bounded by a minimum of:
 RELATIVE_ERROR, if a value is specified for it.
 (5.0 * 0.1**r), where r is the value specified by the command
>> EXECUTIVE_CONTROL SET EASY_DYNAMICS &
>& MODEL_NAME = <model_name> &
executive_control set equilibrium_parameters
>& DIGITS_OF_PRECISION = r
if no value is specified for RELATIVE_ERROR.
3. After STEP_MAXIMUM integration steps, the simulation will stop and return to the command
level. This feature is provided as a precaution against a simulation that is taking too much CPU time.
4. The WATCH_INTEGRATOR_PERF argument only affects diagnostics, not results.
The values can be:
MONITOR: The time, step size, and function-evaluation count at ten equally spaced output times
during the simulation.
ERROR_IN_INTEGRATOR: The integration error after every time step.
FAILURE_IN_INTEGRATOR: The integration error when the code has to repeat the step because
the calculated solution failed to meet the error criteria.
STEPSIZE: The step size and order after every integration step.
NEWSTEP: The step size and order only when the values are changed.
OUTPUT: An indication that another output record is being written to the output files.
ALL: All options are on.
NONE: All options are off.
5. The values for RECONCILE can be:
DISPLACEMENTS: Only the displacements are corrected to satisfy the constraints.
ALL: The displacements are corrected to satisfy the constraints and the velocities and accelerations are
corrected to satisfy the constraint derivatives.
NONE: The integration step size is adjusted to force the integrator to compute the solution at every
output step. In this situation, INTERPOLATE must be set to NO.
Cautions:
1. Note that interpolation is not yet available when the EXECUTIVE_CONTROL SET
DYNAMICS_PARAMETERS BDF_PARAMETER command specifies FIXED or VARIABLE
coefficients for the PREDICTOR_COEFFICIENTS argument.

Controls the error tolerance and other parameters for execution of static equilibrium and quasi-static
equilibrium analyses.
You would set these parameters only when you are requesting a static equilibrium or a quasi- static
equilibrium analysis and you want to change one or more of the tolerances and other parameters from the
default values.
Format:
dynamic = yes/no
alimit = real
error = real
imbalance = real
maxit = integer
pattern_for_jacobian = string
stability = real
tlimit = real
global_damping = real
settling_time = real
acceleration_error = real
kinetic_energy_error = real
static_method = original/advanced/aggressive/all
atol = real
rtol = real
maxitl = integer
etamax = real
eta = real
Example:
executive_control set equilibrium_parameters &
model_name = .model_1 &
dynamic = no &
static_method = all &
atol = 1.0e-005 &
rtol = 1.0e-007 &
maxitl = 30 &
etamax = 0.8 &
eta = 1.0e-003
Description:

model_name An existing model Specify an existing model.
dynamic yes/no Specifies if dynamic simulation needs to be performed or not
to find the static equilibrium.
alimit real Specifies the maximum angular increment allowed per
iteration.
error real Specifies the relative correction convergence threshold.
imbalance real Specifies the equation imbalance convergence threshold.
maxit integer Specifies the maximum number of iterations allowed for
finding static equilibrium.
pattern_for_jacobian string Specifies the pattern for evaluating Jacobian matrix.
stability real Specifies the fraction of mass and damping matrices to be
added to stiffness matrix to stabilize the iteration process.
tlimit real Specifies the maximum translational increment allowed per
iteration during static simulations.
global_damping real Specifies the coefficient for global damping applied to all
bodies during static simulations performed using dynamic
analyses.
settling_time real Specifies the maximum time allowed to reach equilibrium
during static simulations performed using dynamic analyses.
acceleration_error real Specifies the maximum acceleration error allowed during
static simulations performed using dynamic analyses.
kinetic_energy_error real Specifies the maximum kinetic energy error allowed in static
simulations performed using dynamic analyses.
static_method original/advanced/ Specifies the type of static method to be selected to perform
aggressive/all static equilibrium analyses.
atol real Specifies the absolute tolerance value.
rtol real Specifies the relative tolerance value.
maxitl integer Specifies the maximum number of allowed inner non-linear
iterations.
etamax real Specifies the maximum error tolerance for residual in the
inner iteration.
eta real Specifies the inner iteration error control parameter.
1. You use model_name parameter to identify the existing model to be affected with this command. You
may identify a model by typing its name or by picking it from the screen. If the model is not visible
model is displayed. You must separate multiple model names by commas. If the model is visible in
one of your views, you may identify it by picking on any of the graphics associated with it.
2. The default for alimit parameter is 100 and the range is alimit > 0. You should specify the value in
current modeling units (degrees by default).
3. The iterative process carried out during the equilibrium analysis can not converge prior to all relevant
relative corrections being smaller than the value specified by error parameter. The default for this
parameter is 1.0E-04 and the range is error > 0.
4. The iterative process carried out during the equilibrium analysis can not converge prior to each
equation imbalance being smaller than the value specified by imbalance parameter. The default for
this parameter is 1.0E-04 and the range is imbalance > 0.
5. The default for maxit parameter is 25 and the range is maxit > 0.
6. Often the stiffness matrix is singular for a system because the system is neutrally stable (for example,
the system moves in certain directions without affecting the potential energy). Adding a fraction of
the mass and damping matrices to the stiffness matrix removes this singularity and makes it possible
to solve for equilibrium positions. The value of parameter stability does not affect the accuracy of the
solution, but it does affect the rate of convergence of the iteration process. The default is 1.0E-05 and
the range is stability ≥ 0 .
7. The default for tlimit parameter is 20 and the range is tlimit > 0.
8. The default for global_damping parameter is 0 and the range is global_damping ≥ 0 .
9. The default for settling_time is 100 and the range is > 0.
10. The default for acceleration_error is 1.0e-2 and the range is > 0.
11. The default for kinetic_energy_error is 1.0e-2 and the range is > 0.
12. The static_method parameter chooses the method to perform static equilibrium analysis as follows:
• ORIGINAL, for running only the ORIGINAL Solver
• ADVANCED, runs, in order, the following methods until one shows progress:
ORIGINAL
ORIGINAL+Krylov
ORIGINAL+UMF
Newton+Krylov
Tensor-Krylov block-3
Tensor-Krylov block-2+
• AGGRESSIVE, runs, in order, the following methods until one shows progress:
ORIGINAL
ORIGINAL+Krylov
ORIGINAL+UMF
Newton+Krylov
Broyden-Armijo
Trust-Region
• ALL, runs, in order, all the available methods, until one shows progress:
ORIGINAL
ORIGINAL+Krylov
ORIGINAL+UMF
Newton+Krylov
Broyden-Armijo
Trust-Region
Hooke-Jeeves
Default: ORIGINAL
13. The default for atol is 1.0e-6 and the range is 0.0 ≤ atol < 1.0 .
14. The default for rtol is 0.0 and the range is 0.0 ≤ rtol < 1.0 .
15. For all solvers, except ORIGINAL and ORIGINAL+Krylov, the tolerance is defined as :
TOL=ATOL+||xIC||*RTOL.
For ORIGINAL and ORIGINAL+Krylov solvers the tolerance is equal to error.
16. ORIGINAL, ORIGINAL+Krylov and ORIGINAL+UMF solver methods ignore maxitl parameter.
For Hooke-Jeeves method, allowed budget of function evaluations is set to maxitl*N, where N is the
size of the problem (number of unknowns).
17. The default for maxitl is 40 and the range is maxitl ≥ 1 .
executive_control set easy_dynamics
18. The parameter etamax specifies the maximum threshold for the error tolerance of the linear Krylov
solver (for Newton+Krylov and Tensor-Krylov methods) that solves the linear systems required by
Krylov algorithm. Maximum error tolerance for residual in inner iteration. The inner iteration
terminates when the relative linear residual is smaller than eta*| F(x_c) |. eta is determined by the
modified Eisenstat-Walker formula if etamax > 0. If etamax < 0, then eta = |etamax| for the entire
iteration.
19. The default for etamax is 0.9 and the range is 0.0 ≤ etamax < 1.0 .
20. The parameter eta specifies the initial residual tolerance for the linear Krylov Solver for
Tensor_Krylov method. The Tensor-Krylov eta parameter is maintained adaptively by the Krylov
algorithm but eta is the indicated starting value, while etamax is the maximum threshold for eta. The
default for eta is 1.0e-4 and the range is 0.0 ≤ eta < 1.0 .
21. The parameter eta specifies the dimensionless radius of the trust-region for Trust-region method.
The smaller the value, the more the refinement of Trust-region solution (hence more work). The
range is 0.0 ≤ eta ≤ 0.25 .

The EXECUTIVE_CONTROL SET EASY_DYNAMICS command provides an automatic way to select
integration attributes with a single command. In addition, this command provides an easy-to-understand
method for controlling the error.
Format:
Model_name = string
Significant_digits = real
Dynamic_attribute = stiff/high_frequencies/smooth
executive_control set integrator_parameters dstiff
Description:

Model_name An existing model Specifies the model to be modified. You use this
parameter to identify the existing model to be
SIGNIFICANT_DIGITS real Defines the tolerance of the integration error in
decimal digits of accuracy. The relative, local
truncation errors for the integrator will be
bounded by 5 * (0.1 ** r), where r is the specified
value for the SIGNIFICANT_DIGITS
argument.
dynamic_attribute STIFF/HIGH_FREQUE Indicates the characteristics of the mechanism to
NCIES/ SMOOTH be simulated.
If the model is not visible on the screen, you must type the name. You may also find it convenient
to type the name even if the model is displayed.
associated with it.
2. The value of DYNAMIC_ATTRIBUTE can be:
STIFF: Causes Adams to begin integration with the BDF integrator with VARIABLE coefficients.
HIGH_FREQUENCIES: Causes Adams to begin integration with coordinate partitioned equations
and the Adams-Bashforth-Moulton integrator. If you specify PERSISTENCE on the
SOLUTION_PRIORITY argument, Adams switches integrators after a convergence failure,
regardless of the value of DYNAMIC_ATTRIBUTE.

The DSTIFF command specifies the integration error tolerance and other parameters for a dynamic analysis
using the DASSL computer code.
The principal distinctions among the various ways that the backward differentiation formulas can be
implemented in an integration code involve the method of incorporating the variable step size in prediction
scheme. The DASSL integrator uses a fixed leading coefficient formulation for the finite difference
approximations to the derivatives.
While not as computationally efficient, the approach used by DASSL should be more stable numerically than
the fixed-coefficient method in GSTIFF. The trade-off works in reverse order in comparison to the variable
coefficients computed for the WSTIFF integrator in Adams. In general, for problems with behavior that do
not exhibit severe gradients in the solution, the savings in CPU time need not be sacrificed for the more stable
methods.
A second distinguishing feature of DSTIFF is that it is able to interpolate output data between integration
steps. By default, DSTIFF also corrects the interpolated output data to be consistent with the system
constraints (see the RECONCILE_VEL_AND_ACC parameter). While GSTIFF and WSTIFF must
integrate exactly to an output step in order to generate output data, DSTIFF may take an integration step
past an output time and interpolate the output data. This allows DSTIFF to adjust the integration step based
solely on the error criteria, and take larger integration step than output step when possible. As a result,
DSTIFF may be able to complete a simulation with fewer integration steps than would GSTIFF or WSTIFF.
This may result in speed improvement (although the interpolation and correction require some computation
as well).
As described in the various sections covering the ERROR_TOLERANCE parameter for the GSTIFF,
DSTIFF, and WSTIFF commands, the only other significant differences between the integrators in Adams
involve the error control algorithms.
For an analysis with the EQUILIBRIUM, IC, or KINEMATICS commands, the ALIMIT parameter
controls the maximum angular increment per iteration and the TLIMIT parameter controls the maximum
translational increment per iteration. The DSTIFF, GSTIFF, and WSTIFF commands do not allow you to
control either the maximum angular increment per iteration or the maximum translational increment per
iteration. Because large rotational displacements often cause problems for dynamic simulations, Adams
limits the maximum angular increment per iteration to 0.5 rads (~ 29 deg.). However, because large
translational displacements do not generally cause problems during dynamic simulations, Adams imposes no
limit on the maximum translational increment per iteration. Format:
Description:

model_name An existing model Specifies the model to be modified. You use this parameter
command.
error_tolerance Real Specifies the integration error tolerance. The
ERROR_TOLERANCE parameter is also used to
determine the convergence criterion for the corrector. The
convergence tolerance is the value of
ERROR_TOLERANCE parameter divided by 1000.
hinit_time_step Real number Specifies the initial time step to be attempted in the
integrator.
hmax_time_step Real number Specifies the maximum integration step size Adams is to
allow.
kmax_integrator_order Integer Specifies the maximum order of the integrator. Reducing
KMAX may speed integration when damping is light and
the equations are numerically stiff.

maxit_corrector_iterati Integer Specifies the maximum number of iterations that the
ons corrector will take before the integrator backs off on the
current value of the time step and tries a smaller value to
achieve further progress.
pattern_for_jacobian Yes/No Specifies as many as ten character strings that together
establish the pattern for evaluating the Jacobian matrix
during Newton-Raphson iteration.
watch_integrator_perf MONITOR, Specifies as many as nine character strings that together
NO_MONITOR establish the aspects of integrator performance you want to
, INTERR, watch.
NO_INTERR,
CORERR,
NO_CORERR,
INTFAIL,
NO_INTFAIL,
CORFAIL,
NO_CORFAIL,
MATRIX,
NO_MATRIX,
STEPSIZE,
NO_STEPSIZE,
NEWSTEP,
NO_NEWSTEP,
OUTPUT,
NO_OUTPUT,
ALL, NONE
reconcile_vel_and_acc YES/NO Reconciles the values of the displacements with the
constraint equations in the problem.
associated with it.
2. A predictor-corrector scheme is implemented in DASSL to integrate the system of differential and

algebraic equations. The predictor algorithm uses a polynomial fit to the previous values of each
component of state vector to estimate its value at the next time step. The corrector algorithm begins
with the set of predicted values and uses a modified Newton-Raphson iteration scheme to find a
solution that satisfies the equations to within the convergence tolerance.
The convergence criterion imposed on the DASSL integrator in Adams uses the maximum norm over
the relative errors in all of the components of the state vector. The result must be bounded by .001r,
i.e. by thousandth of the specified integration error tolerance r.
3. HINIT_TIME_STEP is not specified or if it is set equal to 0, then the integrator will attempt to get
started with the default value. The initial step actually used by the integrator is determined by the
error tolerance.
4. For the pattern_for_jacobian for each iteration, T or TRUE indicates that Adams is to evaluate the
Jacobian, or F or FALSE indicates that Adams is not to evaluate the Jacobian. Thus cj determines
whether or not Adams is to evaluate the Jacobian at the jth iteration. If necessary, Adams repeats the
pattern of evaluation until it reaches the maximum number of iterations (MAXIT). The number of
Y's or Yes’s and N's or No's, together, must be at least one and no more than ten. PATTERN defaults
to Y:N:N:N:Y:N:N:N:Y:N, i.e. to evaluating the Jacobian at every fourth iteration.
5. For the watch_integrator_perf parameter, the items you can watch and the defaults are as follows:
(NO) CORERR - (Do Not) Print the maximum corrector error and the equation in which it occurs,
and the largest variable change and the equation in which it occurs. The default is no CORERR.
(NO) CORFAIL - (Do Not) Print every time the corrector does not converge within the number
of iterations set by MAXIT. The default is no CORFAIL
(NO) INTERR - (Do Not) Print the maximum integration error at each integration step and the
variable in which it occurs. The default is no INTERR.
(NO) INTFAIL - (Do Not) Print every time Adams tries a step that exceeds the integration error
tolerance. The default is no INTFAIL.
(NO) MATRIX - (Do Not) Print the inverse condition number of the Jacobian matrix for teach
factorization. The default is no MATRIX.
(NO) MONITOR - (Do Not) Print the general statistics ten times during the simulation period.
The default is no MONITOR.
(NO) OUTPUT - (Do Not) Print each time Adams sends results to the output files. The default
is no OUTPUT.
(NO) NEWSTEP - (Do Not) Print the new step size and order at the beginning of each trial step.
The default is no NEWSTEP.
(NO) STEPSIZE - (Do Not) Print the statistics when changing the integration step size. The default
is no STEPSIZE.
In addition, the following items affect all aspects:
ALL - Print all of the aspects of the integration process.
NONE - Print none of the aspects of the integration process.
executive_control set kinematics_parameters
Watch defaults to : NO_CORERR, NO_CORFAIL, NO_INTERR, NO_INTFAIL,

NO_MATRIX, MONITOR, NO_OUTPUT, NO_NEWSTEP, NO_STEPSIZE.
6. The interpolated values of the velocities and accelerations are also corrected to satisfy the derivatives
of the constraint equations only when RECONCILE_VEL_AND_ACC is turned on. Otherwise,
the output values for the velocities and accelerations are the interpolated results. Since the integration
step is determined solely by the error tolerance, the DASSL integrator generally does not compute the
solution at the output points. Therefore, the output values of the solution are interpolated from the
computed values at the integration steps. Thus, Adams must correct the displacements for the output
values to satisfy the constraints.

KINEMATICS_PARAMETERS allow control over the kinematic simulation in Adams. Kinematics
parameters include error tolerances and other parameters for kinematic analyses. You would set these
parameters only when you are requesting a kinematic analysis and you want to change one or more of the
tolerances and parameters from the default values.
Format:
model_name= model_name
alimit = real_number
error = real_number
maxit = integer_number
aerror = real_number
amaxit = integer_number
tlimit = real_number
hmax = real_number
pattern_for_jacobian = yes/no
apattern_for_jacobian = yes/no
Example:
executive_control set kinematics_parameters &
model_name= model_1 &
pattern_for_jacobian = yes &
apattern_for_jacobian = yes
Description:

model_name String Specifies the model to be modified. You use this parameter to
alimit Real number Specifies the maximum angular increment Adams is to allow
per iteration. Can take a real value greater than zero.
error Real number Specifies the maximum relative displacement error Adams is
to allow. Can take a real value greater than zero.
maxit Integer number Specifies the maximum number of iterations Adams is to
allow for finding static equilibrium in a static equilibrium
analysis. Can take an integer value greater than zero.
aerror Real number Specifies the maximum acceleration error Adams is to allow
for each time step during a kinematic solution.
amaxit Integer number Specifies the maximum number of iterations Adams is to
allow for finding accelerations at a point in time during a
kinematics solution.
tlimit Real number Specifies the maximum translational increment Adams is to
allow per iteration.
hmax Real number
pattern_for_jacobian Yes/No Specifies as many as ten character strings that together
establish the pattern for evaluating the Jacobian matrix during
Newton-Raphson iteration.
apattern_for_jacobian Yes/No Specifies as many as ten character strings that together
establish the pattern for Jacobian evaluations during
acceleration solution.
1. Kinematics parameters include error tolerances and other parameters for kinematic analyses. You
would set these parameters only when you are requesting a kinematic analysis and you want to change
one or more of the tolerances andparameters from the default values.
2. A kinematic analysis is only appropriate when a system has zero degrees-of-freedom. A kinematic
analysis solves for the displacements, velocities, accelerations, and forces (if any) at a series of points
in time. To find the displacements, Adams uses Newton-Raphson iteration to solve a nonlinear set of
algebraic equations. After finding the displacements, Adams solves linear equations without iteration
to find the velocities, accelerations, and forces. Adams repeats this procedure at successively later times
until it obtains results over the period of time specified in the Adams SIMULATE command.
executive_control set numerical_integration_parameters
3. You may identify a model by typing its name or by picking it from the screen. If the model is not
visible on the screen, you must type the name. You may also find it convenient to type the name even
if the model is displayed. You must separate multiple model names by commas. If the model is visible
in one of your views, you may identify it by picking on any of the graphics associated with it.
4. The parameter PATTERN_FOR_JACOBIAN specifies as many as ten character strings that together
establish the pattern for evaluating the Jacobian matrix during Newton-Raphson iteration. For each
iteration, T or TRUE indicates that Adams is to evaluate the Jacobian, or F or FALSE indicates that
Adams is not to evaluate the Jacobian. Thus cj determines whether or not Adams is to evaluate the
Jacobian at the jth iteration. If necessary, Adams repeats the pattern of evaluation until it reaches the
maximum number of iterations (MAXIT). The number of Y's or Yes’s and N's or No's, together,
must be at least one and no more than ten. PATTERN defaults to Y:Y:Y:Y:Y:Y:Y:Y:Y:Y, i.e. to
evaluating the Jacobian at every iteration.
5. The parameter APATTERN_FOR_JACOBIAN specifies as many as ten character strings that
together establish the pattern for Jacobian evaluations during acceleration solution. For each iteration,
T or TRUE indicates that Adams is to evaluate the Jacobian, or F or FALSE indicates that Adams is
not to evaluate the Jacobian. Thus cj determines whether or not Adams is to evaluate the Jacobian at
the jth iteration. If necessary, Adams repeats the pattern of evaluation until it reaches the maximum
number of iterations (AMAXIT). The number of Y's or Yes’s and N's or No's, together, must be at
least one and no more than ten. PATTERN defaults to Y:Y:Y:Y:Y:Y:Y:Y:Y:Y, i.e. to evaluating the
Jacobian at every iteration.
Cautions:
1. AERROR must be greater than zero, and defaults to 1.0E-04.

Description:

model_name Existing model Specifies the model to be modified. You use this
parameter to identify the existing model to be
integrator_type GSTIFF, WSTIFF, Specifies the integrator type to be used
DSTIFF, ABAM,
CPBDF, HASTIFF,
SI2_GSTIFF
solver_type CALAHAN, Specifies the Solver type
HARWELL
error_tolerance Real Specifies the error tolerance. Should be greater than
0.

pattern_for_jacobian Yes/No Specifies the pattern for jacobian. Can take up to 10
boolean values.
maxit_corrector_iterati Integer Should be an integer greater than 0
ons
hinit_time_step Real Should be a real number greater than 0
hmin_time_step Real Should be a real number greater than 0
hmax_time_step Real Should be a real number greater than 0
adaptivity Real Specify the adaptivity
scale Real Specify the scale
kmax_integrator_order Integer Specify the integrator order. Integer specified should
be greater than 0 and less than or equal to 12.
interpolate Yes/No Indicates whether interpolation is allowed. That is,
indicates whether the integrator can choose
integration steps independent of output steps and
the interpolate results for the output step times.
reconcile ALL, Corrects interpolated results before Adams writes
DISPLACEMENTS, them to the output files to satisfy the constraint
NONE equations.
repartition_threshold Real number Allows some control of the re-partitioning of
coordinates into independent and dependent
coordinates.
corrector_resolution_fa Real Specifies the corrector resolution factor
ctor
fixed_iterations Integer Specify the number of iterations per integration step
for the GSTIFF and HHT method. Should be an
integer greater than 0.
hratio Integer Specify the number of times the step size goes into
the output sampling rate (that is, hratio=dtout/h)
for the GSTIFF and HHT method. Should be an
integer greater than 0 and it is relevant if
fixed_iterations is specified.
max_error Real Specifies the amount of error above which the user
would like Adams Solver to stop trying to solve the
problem for the GSTIFF and HHT method. Value
should be positive real and it is relevant if
fixed_iterations is specified.
executive_control set preferences
associated with it.
2. The values for RECONCILE can be:
DISPLACEMENTS: Only the displacements are corrected to satisfy the constraints.
ALL: The displacements are corrected to satisfy the constraints and the velocities and accelerations are
corrected to satisfy the constraint derivatives.
NONE: The integration step size is adjusted to force the integrator to compute the solution at every
output step. In this situation,
INTERPOLATE must be set to NO.
3. In general, for efficiency reasons, the coordinates are re-partitioned whenever:
• A matrix inverse condition number gets too small
• The displacement iterations do not converge
• A part rotation occurs
• A matrix becomes numerically singular, or
• The unit energy ratio is less than its original value times the value of
REPARTITION_THRESHOLD.
Cautions:
1. Note that interpolation is not yet available when the EXECUTIVE_CONTROL SET
DYNAMICS_PARAMETERS BDF_PARAMETER command specifies FIXED or VARIABLE
coefficients for the PREDICTOR_COEFFICIENTS argument.

This command allows you to set preferences for Adams Solver.
Format:
model_name = Name of existing model
status_message = on/off
contact_geometry_library = default library/parasolids
contact_faceting_tolerance = real_number
thread_count = integer_number
library_path = string
flex_limit_check = none/skin/selnod
flex_limit_check_action = halt/return/message_only
Example:
executive_control set preferences &
status_message = on &
contact_geometry_library = default_library &
flex_limit_check = none &
flex_limit_check_action = halt
Description:

model_name Existing Model Name Specifies an existing model.
status_message on/off Specifies the status message to be on or off.
contact_geometry_library default_library/ Specifies the geometry library to be used for
parasolid contact operations.
contact_faceting_tolerance Real Specifies the resolution of the mesh that is to be
created from the solid geometries in the model.
thread-count Integer Specifies the number of parallel threads that
Adams Solver (C++) will use when performing the
simulation.
library_path String Specifies a colon-separated list of directories which
are to be searched for user subroutine plug-in
libraries before searching in the default locations.
flex_limit_check none/skin/selnod Specifies flexible body linear limit checking on all
the flexible bodies.
flex_limit_check_action halt/return/ Specifies what action Adams Solver (C++) should
message_only take if a flexible body exceeds its linear limit.
1. Status_message controls the presence of two status messages in the .msg file produced by Adams
Solver (C++). These status messages mimic status messages produced by Adams Solver (FORTRAN).
This preference has no effect on Adams Solver (FORTRAN).
If it is set to ON, the first status message is sent after every simulation and has the form “Simulate
status =i”. The second message is sent when Adams Solver (C++) terminates and has the form
“Termination status = i”. In both cases, “i” is an integer number reporting the status.
2. For many models, the Default Library can substantially reduce simulation time for contact
operations. Because it is polygon-based, however, it is not always as accurate as the Parasolid geometry
engine. Parasolid is an exact boundary-representation geometric modeler, which makes it highly
accurate, but not as fast as a polygon-based engine. For these reasons, you can switch from one to the
other depending on your needs.
3. The faceting tolerance is defined as the maximum error between the true surface and the surface of
the faceted representation of the geometry. The maximum error is guaranteed not to exceed (1/value)
* the minimum dimension of each geometry's bounding box.
The default value of this parameter is 300.
4. The number of threads, must be an integer in the range of 1 to 8. The default value is 1.
By executing multiple threads in parallel across multiple processors, Adams Solver (C++) can reduce
the wall time required for a simulation. Typically, the optimal number of threads is between N and
2N, where N is the number of processors (including virtual processors, such as Pentium processors
supporting HyperThreading). Note that this option has no effect on IRIX architectures.
Note: The Intel® Pentium® 4 processor introduced a feature called Hyper Threading, where
a single physical processor can support more than one logical instruction stream,
simulating multiple logical processors on a single physical processor. For many
applications and environments, this capability may offer performance improvements
over non-Hyper Threading processors. If multiple analysis jobs are running
concurrently, however, there may be performance degradations. If an installation
determines this to be the case, hyper threading should be disabled. This can be done
on a permanent basis through BIOS operations or, for Windows platforms, hyper
threading may be disabled on a process by process basis using the “hyperthreads”
keyword.
5. By setting flex_limit_check parameter to:

skin - Adams Solver (C++) will check the deformation of all the nodes on the skin to see whether they
exceed the linear limit. To use this option, MNF_FILE or DB_FILE need to be specified in
FLEX_BODY statement.
SELNOD - Adams Solver (C++) will only check the nodes specified in SELNOD section in MTX
file.
The linear limit is defined as 10% of the characteristic length of the flexible body. User can use
CHAR_LEN in FLEX_BODY statement to specify the characteristic length. If CHAR_LEN is not
specified, Adams Solver (C++) will try to calculate the characteristic length use MNF or MD DB if
MNF_FILE or DB_FILE is specified. Otherwise, Adams Solver (C++) will issue a warning.
6. Setting the flex_limit_check_action to:
executive_control set solver_parameters
HALT - Terminates execution of Adams Solver (C++).

RETURN - Stops the simulation and returns to the command level.
MESSAGE_ONLY - Issue a warning message only (Default).
For more information see PREFERENCES statement in Adams Solver online help.

This command provides a means to select between the harwel, calahan, umf and auto integration solvers in
Adams. This selection is made on a model by model basis.
Therefore, each time you submit the model, the chosen solver will be used until this command is used to
select the alternative. For a complete description of these solvers, see the Adams documentation.
Format:
model_name= model_name
solver_type = solver_identifer_string
Example:
executive_control set solver_parameters &
solver_type = calahan
Description:

model_name String Specifies the model to be modified. You use this parameter to identify the
existing model to be affected with this command.
solver_type String Specifies that the HARWELL, CALAHAN, UMF or AUTO integration
solvers is to be used in Adams for simulation of the model specified in the
MODEL_NAME parameter. Each time you submit the model to be
analyzed, the chosen solver will be used until this command is used to select
the alternative.
1. Specifies the model that is to be modified. You use this parameter to identify the existing model to be
affected with this command. You may identify a model by typing its name or by picking it from the
screen. If the model is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the model is displayed. You must separate multiple model names
by commas. If the model is visible in one of your views, you may identify it by picking on any of the
2. Solver types
a. CALAHAN
Specifies that Adams Solver (FORTRAN) is to use the CALAHAN solver exclusively. The
Calahan solver is usually faster than the Harwell solver, but it cannot analyze systems with
redundant constraints.
b. HARWELL
Specifies that Adams Solver (FORTRAN) is to use the HARWELL solver exclusively. The
Harwell solver can analyze systems with redundant constraints, but is usually slower than the
Calahan solver. The CALAHAN and HARWELL solvers use somewhat different strategies for
picking pivots during the linear solution.
If one solver is experiencing difficulties solving an ill-conditioned model, you may try the other
solver. One may work better on a particular model than the other. Even though you deactivate all
your redundant constraints, Adams Solver (FORTRAN) does not allow you to use the Calahan
solver. If (under these circumstances) you issue the LSOLVER/CALAHAN command, Adams
Solver (FORTRAN) returns the message: “Changing to the CALAHAN solver is not allowed for this
model due to the presence of redundant constraints.” To avoid this problem, deactivate all your
redundant constraints, run a short simulation, and then issue the LSOLVER/CALAHAN
command.
c. UMF
Specifies that Adams Solver (C++) is to use the UMF solver exclusively. The UMF solver is
typically faster for models with very large number of equations (>4000).
d. AUTO
Specifies that Adams Solver(C++) is permitted to decide which solver to use based on the number
of equations in the model and the amount of Jacobian fill.
file 1
file adams_data_set merge
file
Allows you to merge one Adams data set file or model with another Adams data set file.
Format:
file_name = string
force = force_units
mass = mass_units
time = time_units
Example:
file adams_data_set merge &
file_name = "c:\mydir\desktop\merge1" &
model_name = model_2
Description:

file_name String Specifies the name of the file that is to be read, written, or executed
model_name An Existing Model Specifies an existing model in Adams View with which to merge the
Adams dataset file
length Linear_units Specifies the length units in the file, if different than the current
default
force Force_units Specifies the force units in the file, if different than the current
default
mass Mass_units Specifies the mass units in the file, if different than the current
default
time Time_units Specifies the time units in the file, if different than the current
default
1. Adams Solver IDs, referenced but not defined in the Adams Solver dataset file being merged, are
assumed to be already existing in that file. For example, the following marker definition references to
a part, Adams Solver ID 99. If there is a part 99 in the Adams Solver dataset file, it is assumed that
the reference is to that part. If, however, there is no such part in the Adams Solver dataset file, Adams
View will use the part, Adams Solver ID 99, in the model as the parent of this marker. References to
Adams Solver IDs in the model may also be used for the definition of constraints and forces.
****** adams_view_name='rocker_1' ******
MARKER/9901 , PART = 99 , QP = 100, 75, 0 , REU = 3.14159, 0, 0
Adams View names, that are specified in the Adams Solver dataset file and are not unique with respect
to the model, will be ignored. Adams View will provide a name for the entity using the default name
generation. See the DEFAULT NAME_GENERATION command for more information. For
example, if you read an Adams Solver dataset file with the following marker defined:
****** adams_view_name='rocker_1' ******
MARKER/9901 , PART = 99 , QP = 100, 75, 0 , REU = 3.14159, 0, 0
and the model already existing in Adams View contained an entity named rocker_1 on the PART
with Adams Solver ID 99, the marker would be named using the default name generation. Instead of
being named .MOD1.PAR99.rocker_1, it would be named .MOD1.PAR99.MAR9901. If the
Adams Solver ID specified for the marker 9901 was not unique, a default Adams Solver ID would be
assigned. The default Adams Solver ID is one more (greater by 1) than the highest Adams Solver ID
already in the model.
You cannot merge two existing models in Adams View. To merge two models in Adams View, you
must first write one to an Adams Solver dataset file using the FILE ADAMS_DATA_SET WRITE
command, then read the file back in, using the FILE ADAMS_DATA_SET MERGE command.
2. The proper extension is the default, but can be overridden simply by supplying a different extension.
You do not need to enclose the file name in quotes if it contains only alpha-numeric characters and
3. The model specified is considered the parent model and all Adams IDs and Adams View names in
this model will take precedence over the Adams IDs and the Adams View names specified in the
Adams dataset file.
You may identify a model by typing its name or by picking it from the screen. If the model is not
if the model is displayed. You must separate multiple model names by commas.
associated with it.
4. If you do not use the length parameter, Adams View will read or write the file using your default
modeling units. You only need to enter this parameter when you wish to read or write a file with
different units than those you are currently using.
file 3
file adams_data_set write
Specifying this parameter does not change your default modeling units, it only overrides them during
the file read or write operation. Use the DEFAULT UNITS command if you wish to change your
default modeling units.
5. If you do not use the force parameter, Adams View will read or write the file using your default
modeling units. You only need to enter this parameter when you wish to read or write a file with units
different than those you are currently using.
6. If you do not use the mass parameter, Adams View will read or write the file using your default
7. If you do not use the time parameter, Adams View will read or write the file using your default

Allows you to write an Adams data set from an existing Adams View model.
Format:
file_name = string
write_to_terminal = the constant default value will be used if this
parameter is omitted =
angle = angular_units
force = force_units
mass = mass_units
time =
Example:
file adams_data_set write &
file_name = "c:\model.adm" &
length = mm
Description:

model_name An Existing Model Specifies an existing model
file_name String Specifies the name of the file that is to be read,
written, or executed.
write_to_terminal The Constant Default Value Specifies whether or not the information requested
will be used if this parameter is to be sent to the informational window
is omitted.
anglle Angular_units Specifies the angle units in the file, if different
from the current default.
length Linear_units Specifies the length units in the file if different
from the current default.
force Force_units Specifies the force units in the file, if different from
the current default.
mass Mass_units Specifies the mass units in the file, if different from
Time Time_units Specifies the time units in the file, if different from
1. Adams View will preserve the database names you have chosen, by writing them as comments in the
Adams data set. This will allow you to read the data set at a later date, and still have the original
database names.
The AdamsAdams View model does not have to be complete to be written out in the form of an
Adams data set. If you want to check your model for completeness and consistency, use the 'MODEL
VERIFY' command before writing the data set.
Writing an Adams data set is a convenient method to transfer a Adams View model from one
computing platform to another computing platform from a different hardware vendor.
file 5

associated with it.
3. The proper extension is the default but can be overridden by simply supplying a different extension.
4. Specify whether the information requested is to be sent to the informational window or not.
This parameter is most likely be used in conjunction with the FILE_NAME parameter to get the
information put into a file.
5. If you do not use the angle parameter, Adams View will read or write the file using your default
different from those you are currently using.
6. If you do not use the length parameter, Adams View will read or write the file using your default
7. If you do not use the force parameter, Adams View will read or write the file using your default
8. If you do not us the mass parameter, Adams View will read or write the file using your default
9. If you do not use the time parameter, Adams View will read or write the file using your default
file analysis read
file analysis read

Allows you to read a set of analysis files, which is a set of output files that Adams Solver generates during a
simulation. The files include:
 Graphics
 Request
 Results
You can import multiple files if you associate and store the files with a model. Adams View reads and creates
all analyses under the specified model. If you do not provide a model name, Adams View reads each analysis
into its own model. For request files, when you specify multiple files, the Request IDs button only displays
the requests from the first file listed. The list of IDs will, however, be applied to all files.
If you select to associate the files with a particular simulation, you can only import one set of output files
generated from the same Adams Solver simulation. Adams View uses the time-date stamp placed at the
beginning of each output file to determine if the files were generated by the same simulation run
.
Note: If you choose to edit the time-date stamps, make sure that the output files came from similar
simulations. Otherwise, result processing may lead to erroneous information.
Format:
file analysis read
file_name = string
model_name = new or existing analysis
analysis_name = new or existing analysis
force = force_units
mass = mass_units
time = time_units
Example:
file analysis read&
file_name = “c:\analysis_files\my_analysis_1.gra” &
model_name = my_model &
length = mm &
file 7
file analysis read
file analysis read&

time = second &
force = newton &
mass = kg
Description:

file_name String Specifies the name of the file or files to be read.
model_name New Model Enter the model name under which you want to
store the analysis files in the modeling database.
analysis_name New or Existing Analysis Specifies the name of the analysis in which to
store output files.
length(optional) mm, cm, meter, km, inch, Specifies the length units in the file, if different
foot, mile. from the current default.
force(optional) newton, knewton, dyne, Specifies the force units in the file, if different
pound_force, kpound_force, from the current default.
kg_force, ounce_force,
millinewton, centinewton,
poundal.
mass(optional) kg, gram, pound_mass, Specifies the mass units in the file, if different
kpound_mass, slug, from the current default.
ounce_mass, and tonne.
time(optional) millisecond, second, minute, Specifies the time units in the file, if different
and hour. from the current default.
1. The proper extension is the default, but you can override it by supplying a different extension. You
can only read in multiple files if you associate them with a model.
It is not necessary to enclose the file name in quotes if it only contains alphanumeric characters and
for directory paths, you must enclose the file name in quotes.
2. You can enter multiple files in the file_name parameter if you select to store them under a model.
Adams View requires that simulations have unique names. Therefore, if an analysis already exists with
the same name as your files, use this parameter to assign a unique name at the time of reading the
file(s).
file analysis write
4. If you do not specify the length parameter, Adams View reads or writes the file using your default
modeling units.
If you want to read or write a file with units other than those you are currently using, you must specify
this parameter. Specifying this parameter, however, does not change your default modeling units; it
only overrides them during the file read or write operation.
If you want to change your default modeling units, use the defaults units command.
file analysis write

Allows you to write a set of output files generated from the same analysis.
Format:
file analysis write
file_name = string
entity_name = existing entity
Example:
file analysis write &
file_name = “c:\analysis\analysis_1”
Description:

analysis_name Existing analysis Specifies the name of the analysis in which to store output files.
file_name(optional) String Specifies the name of the file that is to be read, written, or
executed.
Entity_name Existing entity Specifies the objects to be written to a partial binary file.
(Rarely used except internally by vertical applications, such as
Adams Car)
file name, excluding the extension. Adams View requires that simulations have unique names.
Therefore, if an analysis already exists with the same name as your files, use this parameter to assign
a unique name at the time of reading the file(s).
file 9
file binary read
2. The proper extension for the file_name parameter is the default, but you can override it by supplying
a different extension.
file binary read

Allows you to read an Adams View binary file.
When you read an AdamsAdams View binary file, the contents of that file replace the current Adams View
database. Any model that exists at the time of the read, will be over-written by the database in the file.
Format:
file binary read
file_name = string
alert = boolean
Example:
file binary read &
file_name = "c:\mydir\desktop\model_1.bin" &
alert = yes
Description:

file_name String Specifies the name of the file that is to be read, written, or executed
alert Boolean Alerts the user if data has been modified
2. Specifies whether or not to alert the user before reading the binary file if there is data that has been
modified since the last save operation. The alert box provides the user with the options to continue
with the read or to cancel the read.
file binary write
file binary write

Allows you to writes an Adams View binary database file.
All information stored in the database is written to a binary file. That is, all preprocessing modeling entities,
customized menus and panels, view orientations, and postprocessing analyses are written to a binary file.
Binary files do not include current counters for hardcopy file names, nor do they store the current size of the
menus.
Note: There is no restriction on the size of the binary file. While there is no theoretical limit to .bin
file size, practically speaking, the size of a .bin file will be limited to the amount of RAM
available to the Adams session.
Format:
file binary write
file_name = string
demo_version = real
alert_if_exists = boolean
Example:
file binary write &
file_name = "c:\mydir\desktop\model_1.bin" &
alert_if_exists = yes
Description:

file_name String Specifies the name of the file that is to be read, written, or executed.
demo_version Real Specifies that the binary file to be written should be for use with the
Mechanical Dynamics, Inc. "Adams Demonstration System".
alert_if_exists Boolean Specifies whether or not to issue an alert before writing the file, if a file
with the same name already exists
1. IT IS IMPORTANT TO NOTE that the binary file is not transferable to different machines from
different hardware vendors. For example, you cannot read in an Adams View binary file written on a
Silicon Graphics workstation, into Adams View on a Digital Equipment Corp. VaxStation. Also some
machines from the same hardware vendor write incompatible binary files. An example of this is a
file 11
file command read
binary file written on a SUN 4/x and a binary file written on SUN 3/x. To transfer preprocessing
models from Adams View on one hardware vendor’s machine to a different hardware vendor’s
machine, you should use the FILE COMMAND WRITE command. The default extension for the
binary file is ".bin", but this is not necessary.
2. The proper extension is the default, but you can override it by supplying a different extension.
3. Specifies whether or not to issue an alert before writing the file, if a file with the same name already
exists. The alert box provides you with the options to cancel the write, overwrite the existing file, or
to back up the existing file, and then perform the write.
file command read

Reads a command file and executes the commands contained within. The commands will be executed as if
they were typed at the command line. Control will be returned after all the commands have been executed.
If an error is detected in one of the commands and Adams View is unable to process the command, the system
can react in one of several ways. This can be specified using the defaults command_file command, the default
being to abort the file.
Format:
file command read
file_name = string
Example
file command read &
file_name = “C:\mydir\mymodel_1.cmd”
Description:

file_name String Specifies the name of the file that is to be read and executed.
1. The proper extension for the file_name parameter is the default (.cmd), but you can override it by
supplying a different extension.
2. It is not necessary 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 '[ ]'
file command write
file command write

Allows you to write a command file from an existing Adams View model.
Adams View will create a file that contains all the commands necessary to create the model you specify with
the parameter entity_name. This will allow you to move the model from the computing platform you are
currently on, to another computer from a different hardware vendor.
Format:
file command write
entity_name = an existing model
file_name = string
use_parasolid = as_is/full
Example
file command write &
entity_name = .model_1 &
file_name = mymodel_1.cmd &
use_parasolid = as_is
Description:

entity_name an existing model Specifies an existing model to be written as Adams View command
file.
file_name string Specifies the name of the file that is to be written.
use_parasolid as_is/full Allows you to write the geometric definition of an Adams model in
Parasolids file format or in Adams View command language
format.
1. The proper extension in the file_name parameter is the default (.cmd), but you can override it by
It is not necessary to enclose the file name in quotes if it only contains alpha-numeric characters and
if the model is displayed.
file 13
file dac read
You must separate multiple model names by commas. If the model is visible in one of your views, you
may identify it by picking on any of the graphics associated with it. You need not separate multiple
model picks by commas.
3. For the use_parasolid value select either:
a. As is - Adams View exports any geometry that was imported from a Parasolid file out to a
Parasolid file when it writes the command file. The command file references the newly created
Parasolid file. All other geometry (for example, cylinder, shell, and spring-dampers) are defined
using Adams View command language and included in the command file.
b. Full - Adams View exports all static geometry to Parasolid files instead of using Adams View
command language. This includes cylinders, shells, Parasolid, solids, and so on. It does not
include dynamic outlines, spring-damper graphics, and graphic force vectors. These graphics
continue to be defined in the Adams View command language.
4. The commands written to the file may or may not be in the order you originally entered them. Adams
View writes out the commands in the following order.
a. Units for the model.
b. The model create command.
c. The Parts
The attributes of the part.
The markers belonging to the part.
The attributes of the marker.
The geometry belonging to the part.
The attributes of the geometry.
d. The constraints.
The attributes of the constraint.
e. The Forces.
The attributes of the force.
f. The Dynamic geometry. Geometry that spans two different parts.
The attributes of the geometry.
g. Acceleration due to gravity.
h. Adams Analysis Settings.
file dac read

Allows you to import DAC files.
nCode International created the DAC file format. This DAC format supports single-parameter (time series),
two-parameter (x-y), and three-parameter (histogram) files. Adams Durability supports the time series
format. With this DAC format, you can input data from durability test machines and output data to nSoft
file dac write
and other DAC-compatible programs. This topic contains an overview of the DAC format. For a detailed
description of the DAC format, see the nSoft data File Formats document from nCode International.
DAC files are binary, sequential, and fixed-length with 512-byte records. The data represents a fixed sample
rate or time step. Real numbers are single-precision (4-byte) values. Each file has header, data, and footer
regions. Adams Durability supports both old (pre version 5.0) and new (version 5.0+) DAC formats with a
single channel of time series data.
In general, DAC files are not portable from platform to platform. For example, files created by Adams
Durability on a Windows platform are not readable by Adams Durability or other programs on Linux
platforms. nCode provides an nSoft utility to convert DAC files from one platform to another. However, this
utility does not have a specification for the Linux platform. When using Adams Durability or Adams View
on a Linux platform, use DAC files that have been converted to Windows or INTEL (Windows DAC files
are compatible with Linux). Note that Linux-generated DAC files can be processed on Windows and vice
versa.
Format:
file dac read
file_name = file_name
dac_object_name = dac_file_object_name
Description:

File_name String Specifies the name of the file that is to be read, written, or
executed.
dac_object_name Dac_file_object_name Specifies the name of the dac_file object that will contain the
data from the file. Default is the file name.
The proper extension in the file_name parameter is the default, but you can override it by supplying a
It is not necessary to enclose the file name in quotes if it only contains alphanumeric 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 file name in quotes.
file dac write

Allows you to export DAC-format request files from Adams View after a simulation completes. This
technique does not require you to set up requests before running the simulation.
nCode International created the DAC file format. This DAC format supports single-parameter (time series),
two-parameter (x-y), and three-parameter (histogram) files. Adams Durability supports the time series
file 15
file dac write
format. With this DAC format, you can input data from durability test machines and output data to nSoft
and other DAC-compatible programs. This topic contains an overview of the DAC format. For a detailed
description of the DAC format, see the nSoft data File Formats document from nCode International.
DAC files are binary, sequential, and fixed-length with 512-byte records. The data represent a fixed sample
rate or time step. Real numbers are single-precision (4-byte) values. Each file has header, data, and footer
regions. Adams Durability supports both old (pre version 5.0) and new (version 5.0+) DAC formats with a
single channel of time series data.
In general, DAC files are not portable from platform to platform. For example, files created by Adams
Durability on a Windows platform are not readable by Adams Durability or other programs on Linux
platforms. nCode provides an nSoft utility to convert DAC files from one platform to another. However, this
utility does not have a specification for the Linux platform. When using Adams Durability or Adams View
on a Linux platform, use DAC files that have been converted to Windows or INTEL (Windows DAC files
are compatible with Linux). Note that Linux-generated DAC files can be processed on Windows and vice
versa.
Format:
file dac write
result_set_component = existing result_set
Example:
file dac write &
file_name = c:\data\dac_format &
result_set_component = my_result_set
Description:

executed.
Result_set_component Existing Result Set Identifies the components of an existing result set. The
components must be in an existing result set and reference
to the component must include the result set name.
1. The proper extension in the file_name parameter is the default, but you can override it by supplying
file dac write
2. For example, assume you read a request file named shift.req, and this request file contains the result
set REQ1. If you want to refer to the X component in the result set REQ1, enter .SHIFT.REQ1.X
(you can omit .SHIFT. if SHIFT is the current analysis_name). SHIFT refers to the analysis name
from which the result set came (or is stored under).
Result sets are associated with an analysis and can be identified as such. A result set associated with
request 101 from an analysis named test can be referred to as .test.req101.
The table illustrates the default names assigned to result sets and result set components read from
request (.req) and results (.res) files.
Result set naming
Result set type: Result set name: Component names: File that result is from:
part PARxxx... x y z e1 e2 e3 e4 mag results file
vx vy vz wx wy wz
accx accy accz wdx wdy

wdz
diff DIFxxx... q dq results file
joint JOIxxx... fx fy fz tx ty tz fmag tmag results file
jprim JPRxxx... fx fy fz tx ty tz fmag tmag results file
motion MOTxxx... fx fy fz tx ty tz fmag tmag results file
gear GEAxxx... fx fy fz results file
coupler COUxxx... fx1 fy1 fz1 tx1 ty1 tz1 results file
fmag1 tmag1
fx2 fy2 fz2 tx2 ty2 tz2

fmag2 tmag2

fmag3 tmag3
sforce SFOxxx... fx fy fz tx ty tz fmag tmag results file
spring damp SPRxxx... fx fy fz tx ty tz fmag tmag results file
bushing BUSxxx... fx fy fz tx ty tz fmag tmag results file
beam BEAxxx... fx fy fz tx ty tz fmag tmag results file
field FIExxx... fx fy fz tx ty tz fmag tmag results file
user request UREQxxx... u1 u2 u3 u4 u5 u6 u7 u8 results file
request REQxxx... x y z r1 r2 r3 mag amag request file
ucon (not implemented)
file 17
file enhanced_data_set read (.eds)
file enhanced_data_set read (.eds)

Allows you to read an Adams enhanced_data_set file.
Format:
file enhanced_data_set read

file_name = string
mode = Modify, replace, rename, error
Suppress_cpp = Boolean
Defines = string
Example:
File enhanced_data_set read &

file_name = "c:\mydir\desktop\example.eds"
Description:

file_name String Specifies the name of the (.eds) file to be read
mode Modify/replace/ rename/error Specifies the mode to read enhanced dataset file
suppress_cpp Boolean The suppress_cpp option is no longer supported.
Commands with or without this argument
specified now always behave as though
suppress_cpp=yes.
defines String
The suppress_cpp option is no longer supported since Adams no longer includes a third party copy of the C
preprocessor, cpp. Commands with or without this argument specified now always behave as though
suppress_cpp=yes.
file enhanced_data_set write (.eds)

Allows you to write an enhanced_data_set from Adams
file enhanced_data_set write (.eds)
Format:
file enhanced_data_set write

entity_names = an existing adams entities
file_name = string
format = encoded, plain_text, pretty_text
suppress_defaults = Boolean
inverse_define_objects = Adams entity/object
full_name_strings = string
partial_name_strings = string
header_comments = string
ignore_fields = string
Example:
file adams_data_set write &

file_name = "c:\model.adm" &
length = mm
Description:

entity_names An Existing Adams entities Specifies an existing Adams entity name
file_name String Specifies the name of the file that is to be written
format encoded, plain_text, Specifies the format to write EDS file
pretty_text
suppress_defaults Boolean Specifies the suppress default yes or no
inverse_define_objects An existing Adams object Specifies as existing Adams object
full_name_strings String Specifies the full name string
partial_name_strings String Specifies the partial name string
header_comments String Specifies the header comment for EDS file
ignore_fields String Specifies the fields to be ignore
file 19
file fea_loads write
Note: EDS file format is not portable between versions of Adams View.

Allows you to export FEA load information in your model from Adams View after a simulation completes.
This technique does not require you to set up requests before the simulation.
Learn about:
 About Exporting FEA Loads
 Process for Exporting FEA Loads
 Limitations for Exporting FEA Loads
Format:
flexible_body_name = an existing flexible body
file_name = string
header = string
no_inertia = yes/no
node_id = integers
locations = locations
start_time = real
end_time = real
time = reals
tolerance = real
format = Ansys/nastran/abaqus/adams_fem/dac/rpc/marc
Example:
file fea_loads write &
file_name = "c:/mydir/desktop/fea_loads.dat" &
flexible_body_name = FLEX_BODY_1 &
format = nastran
Parameter Type Description

marker_name Existing marker Only for rigid body. This parameter is mutually
(required) exclusive to the flexible body name. It specifies name
of existing marker on rigid body which all load
information will be relative.
flexible_body_name Existing flexible body This parameter is mutually exclusive to the marker
(required) name. It specifies name of existing flexible body and all
load information will be relative to the origin of the
flexible body.
analysis_name Existing analysis Specifies the name of the analysis.
(required)
file_name String (required) Specifies the name of the file that is to be written.
header String (Optional) Only for adams_fem file format. It specifies the strings
of the header written in the exported file.
no_inertia yes/no Select to write inertia loads in addition to external
loads or not. Inertia loads include linear acceleration,
angular acceleration, and angular velocity of the
flexible body. Reaction loads include applied and
reaction forces acting on the body. The default is yes
(Inertia loads are not included).
node_id Integers (Optional) Specifies node IDs to assign to the load points and it’s
useful for rigid body because no node ID is defined at
each markers. For flexible body, Adams View
automatically assigns node IDs to the load points
based on the actual node IDs of the flexible body at
these load locations.
locations Locations (Optional) Specified the locations corresponding to node IDs
above to find out the marker which has the same
location. The number of locations and node IDs have
to be identical.
start_time Real (Optional) Only for DAC/RPC file format. It specifies the start
time to be written. The default is 0.0.
end_time Real (Optional) Only for DAC/RPC file format. It specifies the end time
to be written. The default is the end time of the
analysis.
file 21
file geometry read

time Reals (Optional) For other than DAC/RPC file format. It specifies the
times separated by commas (,) to be written. All time
steps are written if leave this blank.
tolerance Real (Optional) For other than DAC/RPC file format. It specifies the
time range to write loads at each times above. For
example, if you requested output at time steps 2 and 5
with a tolerance of 0.1, Adams View write for all
output steps between 1.9 and 2.1 and 4.9 and 5.1. The
default value is 0.0 and the loads at times are only
written.
format ansys/nastran/abaqus/a Select the file format for the loads file that you want
dams_fem/dac/rpc/ma Adams View to write. The default is adams_fem.
rc
The proper extension is the default, but you can override it by supplying a different extension. It is not
necessary to enclose the file name in quotes if it only contains alphanumeric 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 file name in quotes.
file geometry read

Allows you to import CAD geometry (CatiaV4, CatiaV5, Inventor, Acis, PROE, Solidworks, Unigraphics,
VDA, IGES, STEP or Parasolid). See Manage Geometry Options for more information.
Format:
file geometry read
type_of_geometry = geometry_file_type
file_name = string
option_file_name = string
geometry_type = iges_geometry_type
blanked_entities = boolean
level = integer
create_geometry = geom_create_type
scale = real
file geometry read
file geometry read

mesh_density = integer
tolerance = real
single_shell = shell_opt
location = location
display_summary = boolean
Example:
file geometry read &
type_of_geometry = igs &
file_name = "c:\data.igs" &
part_name = part_2 &
mesh_density = 10 &
blanked_entities = yes &
tolerance = 0.001
Description:

type_of_geometry Geometry_file_type Specifies the type of geometry that is to have its rendering
mode modified.
file_name String Specifies the name of the file that is to be read, written, or
executed.
option_file_name String Specifies the name of the file that contains translation
options specific to the geometry format under
consideration. Note the options file is specific to either the
import or the export operation and to the designated
geometry format.
part_name An Existing Part Specifies the name of the part with which you want to
associate the imported geometry.
file 23
file geometry read

model_name An existing model This parameter is mutually exclusive to the 'part_name'
parameter and is valid only for Interop based translations.
When this parameter is specified, all individual parts in
the native assembly being imported are translated as
separate Adams View parts under the model.
geometry_type Iges_geometry_type Specifies the type of geometric entities to be translated
from the IGES file to View.
blanked_entities Boolean Specifies if invisible geometry is to be converted.
level Integer Note: This argument has been deprecated and no longer
has any influence.
create_geometry Geom_create_type Note: This argument has been deprecated and no longer
has any influence.
scale Real Enter the factor by which you want to scale the size of the
geometry created.
mesh_density Integer Note: This argument has been deprecated and no longer
has any influence.
tolerance Real Note: This argument has been deprecated and no longer
has any influence.
single_shell Shell_opt Values are: yes, no, and wireframe_only.
Note: This parameter is valid only when importing the
geometry under a part. If the geometry is being
imported under a model, then this parameter
will be ignored.
location Location Specifies the translational position where the geometry in
the CAD file is to be located, relative to the MSC. part
coordinate system.
orientation Orientation Specifies the angular position where the geometry in the
CAD file is to be oriented, relative to the MSC. part
coordinate system.
file geometry read

relative_to An Existing Model, Specifies the coordinate system relative to which the
Part Or Marker location coordinates and orientation angles exist.
display_summary Boolean Values: Yes or no
Specifies a yes, will turn logging ON, otherwise no log file
of the translation operation will be generated.
ref_markers global/local Upon import Adams creates reference markers to
correspond with each piece of geometry created in the
Adams model. These markers are typically automatically
named with the prefix PSMAR. These reference markers
are usually located and oriented at the origin of the Adams
model. However, sometimes the geometry in the CAD file
was created in such a way in the CAD system that it has a
location/orientation transformation value relative to the
CAD assembly/part origin.
For example, the geometry was created via a

copy/paste/move action performed on an original piece of
geometry, or an assembly is composed of a number of
parts/sub-assemblies re-located relative to the origins
about which they were originally modelled.
In these scenarios, setting the option Reference Markers to

“Local” will locate/orient the Adams-created reference
markers by applying the same location/orientation
transformation value used in construction in the CAD
system to the marker relative to the Adams model origin.
Setting the option Reference Markers to “Global” will
locate/orient all reference markers at the origin of the
Adams model.
Note: This ref_markers argument is ignored if the

“type_of_geometry” argument is set to “igs” or
“stp” and a warning to this effect will be issued.
The default is "Global".
1. The type_of_geometry parameter acts as a filter to decide which of the selected geometry objects will
have their rendering mode modified. The possible values are: arc, box, frustum, springdamper,
outline, or all. The arc setting includes both arc and circle geometry. The frustum setting includes
both frustum and cylinder geometry.
Values are: igs, stp.
file 25
file geometry read
2. The proper extension of the file is the default, but you can override it by supplying a different
extension.
3. The options file contains all translation options for that specific geometry format and the specific
operation (either import or export but not both). The options file is an easier way of specifying a
complete set of translation options at once during an operation. The file can be generated beforehand,
using the 'Manage Geometry Translation Options' dialog box, accessible from the main menu
(Settings → Geometry Translation).
4. You can specify any combination of these values for the geometry_type parameter:
• Point - Only include vertices of geometric entities
• Wireframe - Include lines, arcs, curves, and splines
• Surface - Include surfaces. The IGES translator supports all the standard surfaces. In the case of
trimmed and bounded surfaces, the untrimmed surfaces and the associated model space trimming
curves are processed, but no trimming is performed.
• Text - Include annotation entities including leader lines, arrows, dimensions, and alphanumeric
characters. The entire annotation data is stroked, so the relative size of most fonts is represented
accurately. Stroked text is translated to View as polylines, allowing for a more accurate
representation of the size of the text in the IGES file, but requires more memory than translating
all text to one font. Large amounts of text may adversely affect performance of the IGES translator
and View.
• All - Include all entities.
Example: The following command translates surfaces and text from the IGES file to View:
file iges read file

"cylinder.igs" & = geometry_type = surface,text .mod1.ground
part_name
5. Any IGES entity encountered in the IGES file can be blanked by the program that created the IGES
file. This is similar to View visibility.
If you specify No for the blanked_entities parameter, the blanked entities are not translated to View.
If you specify Yes, the blanked entities are translated to View and are made invisible.
The IGES entities that are blanked are typically construction entities that are used in the definition
of another geometric entity. For example, a line may be used as the center of rotation of another line
in the definition of a cylinder. The center line, and the sweep line rotated about the center line, would
both be blanked because they are temporary entities used in the construction of the cylinder.
Once you translated blanked entities to View, there is no distinction between construction entities
and other geometry. You can use the display_attributes command to turn on the visibility of the
blanked entities.
file geometry read
Values are: yes and no.

6. Levels let you associate geometry into a group. These groups can be manipulated as a single entity for
purposes of visibility and color. The CAD program that generated the CAD file defines the levels and
are labeled with integers greater than or equal to 0. Levels are typically used to organize data for
viewing and are similar to layers. If you do not specify the levels you want translated, Exchange reads
all levels.
You can specify a single level or a range of levels. Separate the range with a comma (,). For example,
enter 10, 15 to translate levels 10, 11, 12, 13, 14, and 15.
7. You can convert a subset of the geometric entities read by the IGES translator to outlines and markers
in View.
If you specify the create_geometry parameter with the value outline, the entities listed below will be
translated into View outlines with a marker created at each vertex. These markers will have an
orientation parallel to the lprf of the part selected in the part_name parameter.
If you specify this parameter with the value polyline, the above-mentioned entities will be translated
into View polylines. No markers are created when polylines are generated.
Generating outlines has the advantage of having markers created at each vertex. These markers are
standard View markers that may be used for the definition of constraints, forces, mass properties, and
other View geometry. The outlines and markers may also be written to an /Solver dataset file. The
disadvantage of using outlines is the increased memory requirements. Geometry translated to
polylines will not have markers and requires about one third of the memory to store the equivalent
outline. Polylines are not written to an /Solver dataset file.
Values are: solid and polyline.
8. The default scale factor is 1.0, meaning that the geometry in Exchange will be the same size as the
geometry in the CAD file. A scale factor less than 1.0 reduces the size of geometry and a scale factor
greater than 1.0 increases the size of the geometry.
For example, if you specify a scale factor of 0.5, Exchange translates a cylinder of length 2 meters and
diameter of .5 meters to a length of 1 meter and diameter of .25 meters. Exchange also scales the
distance from the geometry to the coordinate system specified in the Relative To text box according
to the scale value. If the cylinder was located at 3, 2, 0 in the file, it would be located at 1.5, 1, 0 after
it is translated to MSC.. The orientation of the geometry is not effected by scale value.
9. The minimum mesh is a 2 X 2 that will display only the boundaries of the surface.
If you do not specify the mesh_density parameter, the iges translator calculates the mesh values based
on the tolerance specified with the tolerance parameter, and polygonizes the surface.
For polygonalization, the surface is sampled at several U/V rulings based on the surface type. The
ruling that generates the most points at the specified tolerance in the U and V direction determines
the polygon density for the surface.
For certain surface types (for example, NURBS) a maximum sample is used to reduce the
approximation time for polygonalizing high-order surfaces. This maximum is currently being set to
4 in each U/V direction.
file 27
file geometry write
Note that specifying a mesh requires less computation than letting the translator default to a
polygonalization (i.e. not setting the mesh_density parameter), but the polylines generated for a mesh
may not be shaded in View. The polylines generated for a polygonalization are closed (polygons) and
therefore may be shaded in View.
10. The tolerance value is the measure of the midpoint chordal distance from the approximated
curve/surface to the true curve/surface.
11. The coordinates specified by the location parameter can be relative to any other coordinate system
defined in the model.
By default, you enter Cartesian (x,y,z) coordinates. You can change the convention for entering
translational positions.
12. The orientation coordinates can be relative to any other coordinate system defined in the model.
View orients the coordinate system starting from the initial coordinate system and applying three
successive rotations. By default, you supply body-fixed 313 angles. You can change the convention
for entering orientation angles.
13. If you do not specify the ‘relative_to’ parameter, View uses the default coordinate system. The default
coordinate system is initially your model, that is. the global coordinate system. You can change the
default coordinate system using the default coordinate_system command.
Cautions:
 Be careful when specifying the tolerance. You should have advanced knowledge of the units and size
of the geometry in the CAD file before setting the tolerance. If you do not know the size of the
geometry in the file, Exchange may translate the geometry so it is too coarse, or too fine. A tolerance
that is too fine can potentially cause Exchange to use excessive computing power and memory.
file geometry write

Allows you to export CAD data (IGES, STEP, or Parasolid). See Manage Geometry Options for more
information.
Format:
file geometry write
type_of_geometry = geometry_file_type
file_name = string
option_file_name = string
explode = boolean
file geometry write
file geometry write

part_name = an existing body
display_summary = boolean
Example:
file geometry write &
type_of_geometry = stp &
file_name = "c:\data.stp" &
explode = yes &
frame_number = 10
Description:

type_of_geometry Geometry_file_type Specifies the type of geometry that is to have its
(required) rendering mode modified.
file_name(required) String Specifies the name of the file that is to be read,
option_file_name String Specifies the name of the file that contains
translation options specific to the geometry
format under consideration. Note the options
file is specific to either the import or the export
operation and to the designated geometry
format.
explode(optional) Boolean Values are: yes and no.
model_name(required) An Existing Model Specifies the Adams View model to be written
to the CAD file. Adams View places each rigid
body in the model on a separate level.
analysis_name(required) An Existing Analysis Specifies a model at a particular simulation
frame (time) of a particular analysis.
file 29
file geometry write

frame_number(required Integer Specifies the frame number (simulation output
) time step) at which to configure a model during
the file geometry write command
part_name(required) An Existing Body Specifies the name of the Adams part from
which the geometry is written to the iges file.
display_summary Boolean Values: Yes or no
Specifies a yes, will turn logging ON, otherwise

no log file of the translation operation will be
generated.
1. The ‘type_of_geometry’ parameter acts as a filter to decide which of the selected geometry objects will
have their rendering mode modified. The possible values are: arc, box, frustum, springdamper,
outline, or all. The arc setting includes both arc and circle geometry. The frustum setting includes
both frustum and cylinder geometry.
Values are: igs, stp.
2. The proper extension for the file specified by the ‘file_name’ parameter is the default, but you can
override it by supplying a different extension.
3. All geometry written to the IGES file is defined with respect to the global coordinate system of the
Adams View model.
4. The options file contains all translation options for that specific geometry format and the specific
operation (either import or export but not both). The options file is an easier way of specifying a
complete set of translation options at once during an operation. The file can be generated beforehand,
using the 'Manage Geometry Translation Options' dialog box, accessible from the main menu
(Settings → Geometry Translation).
5. This analysis_name parameter is helpful for transferring position data of an Adams View model to a
drafting program to prepare drawings of the mechanism at various states of operation. Adams View
writes all parts and geometry to the CAD file in the same relative position as they appear in a single
frame
6. If you specify the ‘frame_number’ parameter, it must be a positive integer corresponding to the
desired frame (output time step), and the default value is initially 1. If you enter a new value, it will
be remembered and will be the default next time the command is used. If you enter a value greater
than the last frame number, Adams displays the last frame.
7. The geometry will be defined with respect to the global reference frame within the geometry file.
You can identify a part by typing its name or by picking it from the screen:
file geometry write
If the part is not visible on the screen, you must type the name (you may find it convenient to type
the name even if the part is visible). If you created the part by reading a dataset or graphics file, the
part name is the letters par followed by the dataset part ID number. For example, the name of Adams
PART/101 is PAR101. If you created the part during preprocessing, you will have given it a name at
that time. If a part is available by default, you can identify it by entering only its name. If it is not,
To identify a part under another model, for example, you may need to enter the model name, as well.
For example, you may specify part arm from model robot by entering .robot.arm. If you type a ?,
Adams View will list the parts available by default.
You must separate multiple part names with commas.
If the part is visible in one of your views, you can identify it by picking on any of the graphics
associated with it. It is not necessary to separate multiple part picks with commas.
8. The FRAME_NUMBER parameter is used to specify the frame number (Adams simulation output
time step) at which to configure a model during the single_frame_display command. 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.
views that contain the model indicated by analysis_name will be affected.
9. Specifies the name of the Adams PART from which the geometry is written to the IGES file. The
geometry will be defined with respect to the global reference frame within the IGES file.
type the name even if the part is displayed. If you created the part by reading an Adams data set or
graphics file, the part name is the letters PAR followed by the Adams data set part ID number. For
example, the name of Adams PART/101 is PAR101. If you created the part during preprocessing,
you will have given it a name at that time.
".robot.arm".
associated with it.
file 31
file graphics read
Tips:
 If you type a "?", Adams View will list the parts available by default.
file graphics read

Allows you to read a graphics file into Adams View, so the information contained may be animated,
manipulated or viewed. When specifying the name of the graphics file to be read, the extension .GRA will be
appended by default. This may be overridden by specifying a different extension.
Format:
file graphics read
file_name = string
mass = mass_units
time = time_units
force = force_units
Example:
file graphics read &
file_name = "c:\model_1.gra" &
disk_based_results = yes
Description:

analysis_name An Existing Analysis Specifies the name of the analysis to store the Adams output in.
executed.
length Linear_units Specifies the length units in the file, if different from the current
default.
file graphics write

mass Mass_units Specifies the mass units in the file, if different from the current
default.
time Time_units Specifies the time units in the file, if different from the current
default.
force Force_units Specifies the force units in the file, if different from the current
default.
associated with it.
2. When Adams View reads a graphics file (.GRA), a request file (.REQ), a results file (.RES), or all three
with the FILE ANALYSIS READ, it stores them in an analysis. By default, the name of the analysis
is the file name excluding the extension.
Adams View requires that Adams simulations have unique names, therefore, if an analysis already
exists with the same name as your files, use this parameter to assign a unique name at the time of
reading the file(s).
3. The proper extension for the file is the default but can be overridden by simply supplying a different
extension.
4. If you do not use the length/mass/time parameter, Adams View will read or write the file using your
default modeling units. You only need to enter this parameter when you wish to read or write a file
with different units than those you are currently using.
file graphics write

Allows you to write a graphics (.gra) file, so you can use the graphics data in Adams PostProcessor or other
postprocessor.
file 33
file html write
Format:
file graphics write
file_name = string
Example:
file graphics write &
file_name = "c:\model_1.gra"
Description:

analysis_name(required) An Existing Analysis Specifies the name of the analysis from which data
should be extracted to write the graphics file.
file_name(required) String Specifies the name of the file that is to be written.
1. The analysis_name parameter specifies the name of the analysis to store the Adams output in. When
Adams View reads a graphics file (.GRA), a request file (.REQ), a results file (.RES), or all three with
the FILE ANALYSIS READ, it stores them in an analysis. By default, the name of the analysis is the
file name excluding the extension.
Adams View requires that Adams simulations have unique names, therefore if an analysis already
2. The file has a .gra extension by default, but you can override it by supplying a different extension.It's
not necessary to enclose the file name in quotes if it only contains alphanumeric 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 file name in quotes.
file html write

Allows you to export the Adams PostProcessor data in the current session of Adams PostProcessor as an
HTML report for viewing by others in your organization.
file html write
Format:
file html write
file_name = file
output_directory = string
title = string
author = string
date = date
comment = string
title_image_file_name = file
image_width = integer
image_height = integer
image_format = png/jpg
movie_format = png/ jpg/ avi/mpg
export_animations = boolean
avi_frames_per_second = integer
avi_quality = integer
avi_keyframe_every = integer
mpeg_ngop = integer
mpeg_round_size = boolean
include_points = boolean
include_markers = boolean
Example:
File Html Write &
File=(.gui.ppt_file_export.c_html.c_tabs.c_file.file_var.string_value) &
Output_directory =(.gui.ppt_file_export.c_html.c_tabs.c_file.dir_var) &
Page_name =Page_1 &
Title=(.gui.ppt_file_export.c_html.c_tabs.c_title.title_var) &
Model_name=.model_1 &
Comment="This Report Is For Analysis_1 In Model Model_1" &
Date=(.gui.ppt_file_export.c_html.c_tabs.c_title.date_var) &
Author=(.gui.ppt_file_export.c_html.c_tabs.c_title.author_var) &
Title_image_file_name=(.gui.ppt_file_export.c_html.c_tabs.c_title.image_var)
&
Image_format =Png &
Image_height =423 &
Image_width =834 &
Export_animations =Yes &
Movie_format =Avi &
file 35
file html write
Avi_compression=(Eval(.gui.ppt_file_export.c_html.c_tabs.c_pages.o_movie_for
mat.current_choice) == "Compressed Avi" ? "Yes" : "No") &
Avi_keyframe_every = 500 &
Avi_frames_per_sec = 10 &
Avi_quality = 75
Include_markers = Yes
Description:

file_name File name Specifies the name of the top-level file that is to be written.
output_directory String Specifies where you want the resulting HTML files and
folders to be stored. This directory may not exist yet.
title String Specifies a title for the published data. It will be used as the
title in the top HTML file, and appear on the title page.
author String Specifies the author of the data. It will appear on the title
page.
date Date Specifies the date the data was published. It will appear on
the title page.
comment String Specifies any comments about the data. It will appear on
the title page.
model_names Existing model Specifies the models for which you want to export
information.
page_name Existing page Specifies the pages of plots and animations you want
exported.
title_image_file_name File Specifies the path and file of an image to appear in the
upper right corner.
image_width Integer Enter the pixel size width of the exported pages.
image_height Integer Enter the pixel size height of the exported pages.
image_format Png/jpg For the pages of plots, enter the image format in which to
store the pages of plots.
movie_format Png/ jpg/ avi/mpg. Specifies the type of movie to export the animation as.
(AVI format is only available on Windows.)
export_animations Yes/No Values are:
yes - Export any page with animations as movies.
no - For all pages, export each as a single image file.

avi_frames_per_second Integer If you select compressed AVI format, set the frame rate.
The default is a frame rate of 10 seconds per frame.
file html write

avi_compression Yes/no Specifies whether or not to compress an AVI file. Values
are: yes and no. The default is yes.
avi_quality Integer Specifies quality as a percent_integer from 1 to 100. Larger
the number, better the quality and larger the AVI file. The
default is 75% compression.
avi_keyframe_every Integer Indicates how often a complete frame (keyframe) is
written to the AVI file; the smaller the number, the larger
the file. The default is each key frame 500 frames apart.
mpeg_ngop Integer Indicates how often a complete frame (keyframe) is
written to the MPEG file
mpeg_round_size Yes/no Some playback programs require the pixel height and
width to be multiplies of 16. Set this option to yes to
ensure that your movie plays in many playback programs.
Include_points Yes/No Specifies whether Points information needs to be included
in the HTML report
Include_markers Yes/No Specifies whether Marker information needs to be
included in the HTML report
1. For the file_name parameter,the proper extension is the default .htm, but you can override it by
supplying a different extension. There will be several other files and subdirectoreis exported in the
report.
2. When you export model information, you output information about the model objects: parts,
constraints, forces, measures, requests, and assembly objects. Adams View creates a folder for each
model and objects in the model, grouped by type.
3. By default, Adams PostProcessor maintains the aspect ratio of the images so if you enter a value for
image_width, Adams PostProcessor automatically calculates the height based on the current aspect
ratio, and the reverse.
If you leave image_width and image_height blank, Adams View uses their default size in Adams
PostProcessor.
4. For the movie_format parameter,
• If you select jpg or png, Adams Processor, exports each frame as an png or jpg file, and then plays
them as a movie.
• If you select compressed AVI format, set avi_frames_per_second.
• If you select .mpg, you can also set mpeg_ngop or mpeg_round_size.
file 37
file iges read
5. For the “mpeg_ngop” parameter, the smaller the number, the larger the file. Some movie players
cannot handle compression; in that case, set to 1.
file iges read

Allows you to read an IGES geometry file.
Format:
file iges read
file_name = string
geometry_type = iges_geometry_type
blanked_entities = boolean
level = integer
create_geometry = iges_create_type
scale = real
mesh_density = integer
tolerance = real
single_shell = shell_opt
location = location
Example:
file iges read &
file_name = "c:\data.igs" &
geometry_type = all &
location = 10 , 10 , 10 &
orientation = 0 , 0 , 0&
relative_to = ground
file iges read
Description:

file_name String Specifies the name of the IGES file containing the
geometry, to be imported into Adams View for the
FILE IGES READ command, or the name of the IGES
file to be generated for the FILE IGES WRITE
command.
option_file_name String Specifies the name of the file that contains translation
options specific to the geometry format under
consideration. Note the options file is specific to either
the import or the export operation and to the designated
geometry format.
part_name An Existing Part Specifies the name of an existing Adams View PART
onto which the translated geometry will be placed.
geometry_type Iges_geometry_type Specifies the type of geometric entities to be translated
from the IGES file to Adams View.
blanked_entities Boolean Specifies if invisible geometry is to be converted.
level Integer Note: This argument has been deprecated and no
longer has any influence.
Specifies the IGES levels that are to be converted
during the file read.
create_geometry Iges_create_type Note: This argument has been deprecated and no
Specifies the type of Adams View geometry created
when geometry is translated from the IGES file to
Adams View.
scale Real Specifies the scale factor to be applied to the size of the
geometry created in Adams View
mesh_density Integer Note: This argument has been deprecated and no
The mesh density specifies the number of rulings on a
surface in each parametric (U/V) direction.
tolerance Real Note: This argument has been deprecated and no
Specifies the tolerance value used in the approximation
of curves and surfaces when they are translated into
Adams View.
single_shell Shell_opt
file 39
file iges read

location Location Specifies the translational position where the geometry
in the IGES file is to be located relative to the Adams
View part lprf.
orientation Orientation Specifies the angular position where the geometry in
the IGES file is to be oriented relative to the Adams
View part lprf.
relative_to An Existing Model, Part Or Specifies the coordinate system that location
Marker coordinates and orientation angles correspond to.
1. The Adams IGES translator is an optional module for Adams View. Adams IGES imports standard
IGES geometry files from any CAD software package and operates on this data to convert it into a
set of Adams View geometry elements. These elements can correspond either to standard Adams
GRAPHICS statements or polylines. You associate the IGES geometry with any rigid body part of
the Adams View model prior to, or subsequent to an Adams simulation.
2. Include the complete path name unless the file currently resides in the directory from which you are
running Adams View.
If the files that you want to read into Adams View are not in the directory in which you are running
AdamsAdams View, use the complete path name of the files. Enclose the full path name in double
quotation marks ("") because the full path name includes special characters; characters other than
alphabetic, numeric, or underscore characters.
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.
Adams View assumes that the file extension is ".igs." Therefore, you do not have to include the file
extension if it is ".igs."
3. The geometry may be placed upon a part and used for preprocessing and postprocessing. Markers
created by the IGES translator will be located on the part specified in this parameter.
model name, as well. For example, you may specify part 'arm' from model 'robot' by entering
".robot.arm".
file iges read
associated with it.
4. Admissible values for the geometry_type parameter are:
Wireframe - This general type of geometry includes lines, arcs, curves, and splines.
Surface--The IGES translator supports all the standard surfaces. In the case of trimmed and bounded
surfaces, the untrimmed surfaces and the associated model space trimming curves are processed, but
no trimming is performed.
Text-Text implies annotation entities including leader lines, arrows, dimensions as well as alpha-
numeric characters. All annotation data is stroked, so the relative size of most fonts is represented
accurately. Stroked text is translated to Adams View as polylines. This allows for a more accurate
representation of the size of the text in the IGES file but requires more memory than translating all
text to one font.
Large amounts of text may adversely affect the performance of the IGES translator and Adams View.
All-All supported entities are translated to Adams View.
Any combination of these values may be specified. For example, the following command will translate
surfaces and text from the IGES file to Adams View.
FILE IGES READ FILE="cylinder.igs"&
GEOMETRY_TYPE=Surface,Text PART_NAME=.mod1.ground
5. Any IGES entity encountered in the IGES file may be blanked by the program that created the IGES
file. This is similar to Adams View visibility. If you specify No for the BLANKED_ENTITIES
parameter, then the blanked entities are not translated to Adams View. If you specify Yes for the
BLANKED_ENTITIES parameter, then the blanked entities are translated to Adams View and they
are made to be invisible.
IGES entities that are blanked are typically construction entities that are used in the definition of
another geometric entity. For example, a line may be used as the center of rotation of another line in
the definition of a cylinder. The center line, and the sweep line rotated about the center line, would
both be blanked because they are temporary entities used in the construction of the cylinder.
Once blanked entities have been translated to Adams View, there is no distinction between
construction entities and other geometry. The DISPLAY_ATTRIBUTES commands may be used to
turn the visibility of the blanked entities on.
6. An IGES level is a means of associating geometry into a group. These groups may be manipulated as
a single entity for purposes of visibility and color. IGES levels are defined by the program that
generates the IGES file and are labeled with integers greater than or equal to zero. Levels are typically
used to organize data for viewing and are similar to layers in the CAD sense. Adams View will read
all levels by default if the LEVEL parameter is not specified.
Adams View allows specification of one level or a range of levels to be translated from the IGES file.
The following command translates levels 10,11,12,13,14, and 15 from the IGES file to Adams View.
FILE IGES READ FILE="engine.igs"LEVEL=10,15&
PART_NAME=.coupe.block
file 41
file iges read
7. A subset of the geometric entities read by the IGES translator may be converted to outlines and
markers in Adams View. Refer to the table below for a complete list of entities that may be translated
into outlines and markers or polylines.
If CREATE_GEOMETRY is specified with the value 'outline', the entities listed below will be
translated into Adams outlines with a marker created at each vertex. These markers will have an
orientation parallel to the lprf of the PART selected in the PART_NAME parameter.
If CREATE_GEOMETRY is specified with the value of 'polyline', the above mentioned entities will
be translated into Adams View polylines. No markers are created when polylines are generated.
Generating outlines has the advantage of having markers created at each vertex. These markers are
standard Adams View markers that may be used for the definition of constraints, forces, mass
properties, and other Adams View geometry. The outlines and markers may also be written to an
Adams data set file. The disadvantage of using outlines is the increased memory requirements.
Geometry translated to polylines will not have markers and requires about one third of the memory
to store the equivalent outline. Polylines are not written to an Adams data set file.
In addition to the entities listed below, outlines may be created for any geometry or annotation entity
that results in a linear approximation of two points. In this case, a line is created.
Outlines may also be created for surfaces that are polygonalized.
IGES ENTITY TYPE NO. CONVERTED TO Adams View Object

Circular Arc 100 Arc, Circle
Composite Curve 102 Polyline
Conic Arc 104 Polyline
Copious Data 106 Outline or Polyline
Centerline 106 (20-21) Polyline
Section 106 (31-38) Polyline
Witness Line 106 (40) Polyline
Plane 108 Outline or Polyline
Line 110 Outline or Polyline
Parametric Spline Curve 112 Polyline
Parametric Spline Surface 114 Polyline
Point 116 Marker
Ruled Surface 118 Outline or Polyline
Surface of Revolution 120 Cylinder, Outline, or Polyline
Tabulated Cylinder 122 Cylinder, Frustum, Outline, or Polyline
Rational B-Spline Curve 126 Polyline
file iges read

Rational B-Spline Surface 128 Outline or Polyline
Offset Curve 130 Polyline
Offset Surface 140 Outline or Polyline

Boundary 141 Polyline
Curve on a Parametric 142 Polyline
Surface
Bounded Surface 143 Outline or Polyline
Trimmed (Parametric) 144 Outline or Polyline
Surface
Angular Dimension 202 Polyline
Curve Dimension 204 Polyline
Diameter Dimension 206 Polyline
Flag Note 208 Polyline
General Label 210 Polyline
General Note 212 Polyline
New General Note 213 Polyline
Leader (Arrow) 214 Polyline
Linear Dimension 216 Polyline
Ordinate Dimension 218 Polyline
Point Dimension 220 Polyline
Radius Dimension 222 Polyline
General Symbol 228 Polyline
Sectioned Area 230 Polyline
8. The default scale factor is 1.0. If the scale factor of 1.0 is used, the geometry created in the Adams
VIEW will be the same size as the geometry in the IGES file. A scale factor less than 1.0 will reduce
the size of geometry and a scale factor greater than 1.0 will increase the size of the geometry. For
example, assume the scale factor specified is 0.5, a cylinder of length 2 meters and diameter .5 meters
would be translated to Adams View with the length of 1 meter and diameter of .25 meters. The
distance from geometry to the RELATIVE_TO coordinate system will be scaled accordingly. If the
previously mentioned cylinder was located at 3,2,0 in the IGES file, it would be located at 1.5,1,0
after it is translated to Adams View.
The orientation of the geometry is not affected by the SCALE parameter.
file 43
file iges read
9. The following is an example of a 5 X 3 mesh.

_____________________
: : : : :
: : : : :
: : : : :
:_______:_____:____:____:
: : : : :
: : : : :
:______:____:____:___:
The minimum mesh is a 2 X 2 which will display only the boundaries of the surface. If the
MESH_DENSITY parameter is not specified, the mesh values will be calculated by the IGES
translator based upon the tolerance specified with the TOLERANCE parameter and the surface will
be polygonalized. For polygonalization, the surface is sampled at several U/V rulings based on the
surface type. The ruling that generates the most points at the specified tolerance in the U and V
direction determines the polygon density for the surface. For certain surface types (e.g. NURBS) a
maximum sample is used to reduce the approximation time for polygonalizing high order surfaces.
This maximum is currently being set to 4 in each U/V direction.
It should be noted that specifying a mesh requires less computation than letting the translator default
to a polygonalization (i.e. not setting the MESH_DENSITY parameter), but the polylines generated
for a mesh may not be shaded in Adams View. The polylines generated for a polygonalization are
closed (polygons) and therefore, may be shaded in Adams View.
10. This tolerance is the measure of the midpoint chordal distance from the approximated curve/surface
to the true curve/surface.
+++
+ | +
+ |tolerance +
+ ___________|_____________+
+ /
+ /
+ /
+ / + = true curve
/
+ / __ = approximate curve
/ /
+ /
file iges read
/
+/
Caution should be used when specifying the TOLERANCE parameter. Since you specify the
tolerance value, advance knowledge of the units and size of the geometry in the IGES file is necessary.
If the size of the geometry in the IGES file is not known the geometry translated to Adams View may
be created too coarse, or worse, too fine. A tolerance that is too fine can potentially cause the IGES
translator to use excessive CPU and memory.
The TOLERANCE parameter becomes more significant if the MESH_DENSITY parameter is not
specified. If the MESH_DENSITY parameter is not specified, the IGES translator will polygonalize
any surfaces encountered in the IGES file. If the IGES file contains a large number of surfaces, the
IGES translator might generate a large amount of data, degrading the performance of Adams View.
If the translation appears to be taking too much time, try increasing the value specified for the
TOLERANCE. Try reading the IGES file with the TOLERANCE increased by a factor of 10. If the
speed degradation is caused by a tolerance that is too fine, you will see a dramatic improvement with
a larger value specified for the TOLERANCE parameter.
The tolerance reported in the log file and in the LIST_INFO is the tolerance of the data defined in
the IGES file. This is the maximum tolerance available in the IGES file and is usually too fine for
efficient translation to Adams View. It is recommended to try a tolerance several orders of magnitude
greater than the tolerance specified in the IGES file.
11. The coordinates specified by the LOCATION parameter can be relative to any other coordinate
system defined in the Adams View model (See the RELATIVE_TO parameter for this command).
12. The orientation coordinates can be relative to any other coordinate system defined in the Adams
View model (See the RELATIVE_TO parameter for this command).
By default, you supply Euler (known as body313, or body-fixed z, x, z) angles. You may change this
convention with the 'DEFAULTS UNITS ORIENTATION_TYPE=' command. For example,
selecting SPACE123 means you will subsequently be supplying space-fixed x, y, and z, angles.
AdamsAdams View applies your orientation angles starting from the coordinate system you identify
with the RELATIVE_TO parameter. The default for the RELATIVE_TO parameter is the default
coordinate system.
Refer to the Appendix on "Specifying Locations and Orientations in Adams View" in the Adams
View Users Manual for more information on the ORIENTATION parameter.
Tip: If you type a "?", Adams View will list the parts available by default.
file 45
file log_file
file log_file
The log_file is an ASCII file Adams View creates, that becomes a record of Adams View session.
Format:
file log_file
file_name = string
write_switch = on_off
messages_include = on_off
commands_include = on_off
expand_commands = on_off
Example:
file log_file &
write_switch = on &
messages_include = on &
commands_include = on
Description:

write_switch On_Off This parameter controls whether or not Adams View generates a log
file.
messages_include On_Off Allows you to specify the inclusion or exclusion of diagnostic
messages, produced by Adams View, into the log file
commands_include On_Off COMMANDS_INCLUDE is a parameter to the "file log_file"
command
expand_commands On_Off EXPAND_COMMANDS is a parameter on the "file log_file"
command
1. All commands, messages, and prompts are sent to the log file. The name of this file is defaulted to
aview.log.
The default name may be overridden using the file_name parameter of the LOG_FILE command.
The log_file command allows modification of the behavior of the log file that is generated when
Adams View is running. These modifications include:
• Specification of the name of the log file
file log_file
• A switch to turn off the log file write (slight system performance improvement)
• A switch for inclusion or exclusion of system messages
• A switch to include or exclude commands entered
• A switch for the expansion of abbreviated commands
The log file is also useful for reproducing a session (e.g. recreating a session after a system crash or
other such catastrophic failure) and for creation of command macros (see help for the
expand_commands parameter). Log files are command files generated by the Adams View containing
all commands executed as well as diagnostics generated (All diagnostics and messages are written to
the log file as comments.
This allows the log file to be executed directly as a command file).
Log files may be read in and executed in the same fashion as other command files. Each time Adams
View is run, a new log file is generated. If you wish to save the log file after finishing a session, make
sure the log file is renamed, otherwise it may be replaced the next time the application is started.
3. Turning off the log file will result in a slight performance improvement. The name of the log file is
defaulted to aview.log. The default name may be overridden using the file_name parameter. By
default, Adams View generates a log file that may be played back at a later time. Each time Adams
View is run a new log file is generated.
If this parameter is turned Off, Adams View will not generate a log file. It is recommended that the
log file remain activated because it represents a record of the session. A log file may be executed as a
command file in order to reproduce a session. This is useful in recreating a session after a system crash
or other such catastrophic failure.
4. By default, all messages from Adams View are sent to the log file. This allows a more complete
representation of the session in the log file and provides more information to someone who is reading
the log file.
Messages are stored as comments in the log file, and are therefore ignored by the command processor
if the log file is read in as a command file.
5. commands_include parameter allows you to specify whether the command entered during an Adams
View session should be echoed to the log file. If the value of the COMMANDS_INCLUDE
parameter is Off, no commands entered by the user or a command file will be printed to the log file.
ON, the default, indicates all commands will be echoed to the log file.
If the user wishes to use the log file as a command file, this parameter should be set to ON. Also, the
EXPAND_COMMANDS parameter should be set as well.
file 47
file mnfxform mirror
Note: If a command file is executed, these commands will be sent to the log file as comments.
This is because if the command that executes the command file, as well as the commands
in the command file are both left as executable in the log file, then the commands will
be executed twice! Once, by calling the same command file, and next, as logged when
the file was read the first time.
6. expand_commands allows you to specify whether the commands entered should be written to the log
file as they are entered (possibly abbreviated) or expanded to full length. If EXPAND_COMMANDS
is turned ON, entire command keywords and parameter names are written to the log file even if only
abbreviations are entered. The default setting is OFF. This provides a very efficient way to create
command procedures. For example, the user can interactively enter the abbreviated commands to
quickly create an xy plot. (Entering the abbreviated commands is much faster but can create a log file
that is not very readable.) With the EXPAND_COMMANDS parameter set to "on", the fully
expanded commands are written to the log file. This log file can be renamed and executed as a
command file to repeat a given action, such as recreating the xy plot for subsequent analysis runs.
Also, once created, the converted log file can be edited to perform similar yet different functions. You
may expand commands in an existing command file by first placing the command "file log_file
expand_commands=on commands_include=on" at the beginning of the file. If you then execute the
command file, the resulting log file will contain an expanded copy of the commands.

Allows you to mirror a flexible body. You need to specify an existing Flexible Body / Modal Neutral File
(MNF) / MD DB file, a plane for mirroring. The flexible body will be mirrored with respect to the specified
plane. You can also specify offset/ new interface node ids which will increment/replace the current interface
node ids of the flexible body respectively. You can also optimize the MNF by using the option MNF Write
Option, which corresponds to the parameters in the MDI_MNFWRITE_OPTIONS environment variable. For
more information on the MDI_MNFWRITE_OPTIONS, see Setting Up Translation Options through the MNF
Toolkit.

flexible_body_name = existing flexible body
modal_neutral_file_name = string
md_db_file_name = string
index_in_database = integer
output_file_type = mnf/md db
output_file_name = string
orientation = Global X/Global Y/Global Z/
X Axis/Y Axis/Z Axis/User
Defined

marker = existing model marker
user_input = orientation
location = location
pl_point_1 = location
point_1 = location
point_2 = location
node_number_offset = integer
id_list = integer array
mnfwrite_options = string
Example:
file mnfxform mirror &
modal_neutral_file_name = "D:\MSC.Software\Adams\flex\examples\mnf\lin
k.mnf" &
output_file_type = mnf &
output_file_name = "D:\mirroring.mnf" &
orientation = Global Z &
location = 0,0,100 &
mnfwrite_options = single

flexible_body_name Existing flexible This parameter is mutually exclusive to the MNF file
body and MD DB File.Specifies the flexible body that needs
to be mirrored.
modal_neutral_file_name String This parameter is mutually exclusive to the flexible
body name and MD DB File. It specifies the name of
the MNF file name to be mirrored.
md_db_file_name String This parameter is mutually exclusive to the MNF file
and flexible body name. It specifies the name of the MD
DB file to mirror.
file 49

index_in_database Integer This parameter applies only, when the user has selected
md_ db_ file_name for mirroring a flexible body. This
parameter specifies the index of the flexible body in the
specified MD DB. It is optional. If not specified, it is
assumed to have the value 1.
output_file_type mnf, md db Specifies what kind of output file will be created either
MNF/ MD DB.
output_file_name String Specifies the name of MNF/MD DB file to be created
after mirroring.
orientation Global X, Global Y, Specifies the orientation for mirroring. If orientation is
Global Z, X Axis,Y X Axis, Y Axis or Z Axis then marker needs to be
Axis, Z Axis, User specified as these axis are marker's axis. If orientation is
Defined user defined then you need to enter user_input.
marker Existing Model, Specifies an existing marker on the model. This option
Marker is only available when orientation is X Axis, Y Axis, Z
Axis.
user_input Orientation Specifies any arbitrary orientation about which you
want to mirror the flexible body.
location location Specifies the location for mirroring.
pl_point_1 location This parameter and the next parameters (pl_point_2 &
pl_point_3) are mutually exclusive to the parameters
(orientation, marker and location). It specifies x, y, and
z coordinates of first point that lies on a plane.
pl_point_2 location Specifies x, y, and z coordinates of second point that lies
on a plane.
pl_point_3 location Specifies x, y, and z coordinates of third point that lies
on a plane.
point_1 location This parameter and the next parameters (point_2) are
mutually exclusive to the parameters (orientation,
marker, location, pl_point_1, pl_point_2 and
pl_point_3). It specifies x, y, and z coordinates of one of
the end points.
point_2 location Specifies x, y, and z coordinates of one of the end points.
file mnfxform rotate

node_number_offset integer This parameter is mutually exclusive to the id_list.
Specifies offset value by which the current interface
node ids will be incremented. It is optional parameter.
id_list integer array This parameter is mutually exclusive to the
node_number_offset. It specifies a list of new interface
node ids that will replace the current interface node ids.
It is optional parameter.
mnfwrite_options parameters in Specifies a list of parameters in
MDI_MNFWRITE_O MDI_MNFWRITE_OPTIONS environment variable.
PTIONS
environmental It optimizes the MNF through Adams Flex Toolkit. It is
variable optional parameter.

Allows you to rotate a flexible body. You need to specify an existing Flexible Body / Modal Neutral File
(MNF) / MD DB file, an axis for rotation and angle. The flexible body will be rotated about the specified
axis by specified angle. You can also specify offset/ new interface node ids which will increment/replace the
current interface node ids of the flexible body respectively. You can also optimize the MNF by using the
option MNF Write Option, which corresponds to the parameters in the MDI_MNFWRITE_OPTIONS
environment variable. For more information on the MDI_MNFWRITE_OPTIONS, see Setting Up Translation
Options through the MNF Toolkit.

Defined
location = location
file 51

point_1 = location
point_2 = location
angle = real
Example:
file mnfxform rotate &
modal_neutral_file_name = "D:\MSC.Software\Adams\flex\examples\MSCNASTR
AN\demo\plate.MASTER" &
output_file_type = md db &
output_file_name = "D:\rotation.MASTER" &
orientation = Global Z &
location = 0,0,100 &
angle = 60 &
id_list = 10,50,70

body and MD DB File. Specifies the flexible body that needs
to be rotated.
the MNF file name to be rotated.
DB file to rotate.
md_ db_ file_name for rotating a flexible body. This

MNF/ MD DB.
after rotation.
orientation Global X, Global Y, Specifies orientation for rotation. If orientation is X
Global Z, X Axis,Y Axis, Y Axis or Z Axis then marker needs to be specified
Axis, Z Axis, User as these axis are marker's axis. If orientation is user
Defined defined then you need to enter user_input.
Axis.
user_input Orientation Specifies any arbitrary orientation about which you
want to rotate the flexible body.
location location Specifies the location for rotation.
pl_point_1 location This parameter and the next parameters (pl_point_2
and pl_point_3) are mutually exclusive to the
parameters (orientation, marker and location). It
specifies x, y, and z coordinates of first point that lies on
a plane.
on a plane.
on a plane.
marker, location, pl_point_1, pl_point_2 and
the end points.
angle real Specifies the angle for rotation.
file 53
file mnfxform translate

PTIONS

Allows you to translate a flexible body. You need to specify an existing Flexible Body / Modal Neutral File
(MNF) / MD DB file, direction for translation and distance. The flexible body will be translated in the
specified direction by specified distance. You can also specify offset/ new interface node ids which will
increment/replace the current interface node ids of the flexible body respectively. You can also optimize the
MNF by using the option MNF Write Option, which corresponds to the parameters in the
MDI_MNFWRITE_OPTIONS environment variable. For more information on the
MDI_MNFWRITE_OPTIONS, see Setting Up Translation Options through the MNF Toolkit.

Defined
v_distance = real

pl_distance = real
point_1 = location
point_2 = location
ep_distance = real
Example:
file mnfxform translate &
modal_neutral_file_name = "D:\MSC.Software\Adams\flex\examples\mnf\link
.mnf" &
output_file_type = mnf &
output_file_name = "D:\translation.mnf" &
orientation = Global Y &
v_distance = 100 &
node_number_offset = 1000 &
mnfwrite_options = fast_invar, MKS, strip_face

body and MD DB File. Specifies the flexible body that needs
to be translated.
the MNF file name to be translated.
DB file to translate.
md_ db_ file_name for translating a flexible body. This
file 55

MNF/ MD DB.
after translation.
orientation Global X, Global Y, Specifies the orientation for translation. If orientation is
Global Z, X Axis, X Axis, Y Axis or Z Axis then marker needs to be
Y Axis, Z Axis, User specified as these axis are marker's axis. If orientation is
Defined user defined then you need to enter user_input.
Axis.
user_input Orientation Specifies any arbitrary direction in which you want to
translate the flexible body.
v_distance real Specifies the distance for translation.
pl_point_1 location This parameter and the next parameters (pl_point_2 &
pl_point_3) are mutually exclusive to the parameters
(orientation, marker and location). It specifies x, y, and
z coordinates of first point that lies on a plane.
on a plane.
on a plane.
pl_distance real Specifies the distance for translation.
marker location, pl_point_1, pl_point_2 and
the end points.
ep_distance real Specifies the distance for translation. It is optional. In
case distance is not specified then distance is length of
segment (point_1point_2).
file parasolid write

PTIONS

Allows you to write the geometric definition of an Adams model or part from to the Parasolids file format.
You can then read the Parasolid file into a CAD program.
You can export an entire model, an individual part of a model, or a model as it exists at a particular simulation
time. Exporting the model at a particular simulation time is helpful for transferring position data of an Adams
model to a CAD program to prepare drawings of the mechanism at various states of operation.
Format:
file_name = string
type = ascii/binary/neutral
file 57
Description:

File_name String Specifies the name of the file that is to be read. The proper
extension is the default, but you can override it by supplying a
Type Ascii/binary/neutral Specifies the type of file
Model_name Existing model Specifies the Adams View model to be written to the CAD file.
Adams View places each rigid body in the model on a separate
level.
Analysis_name Existing analysis Specifies the model at a particular simulation frame (time) of a
particular analysis to export.
frame_number Integer Specifies the frame number (simulation output time step) at
which to configure a model during the single_frame_display
command.
part_name Existing Part Specifies the name of the Adams part from which the geometry is
written to the iges file.
1. It is not necessary to enclose the file name in quotes if it only contains alphanumeric characters and
2. The analysis_name parameter is helpful for transferring position data of an Adams View model to a
drafting program to prepare drawings of the mechanism at various states of operation. Adams View
writes all parts and geometry to the CAD file in the same relative position as they appear in a single
frame display.
3. If you specify the frame_number parameter, it must be a positive integer corresponding to the desired
frame (output time step), and the default value is initially 1. If you enter a new value, it will be
remembered and be the default next time the command is used. If you enter a value greater than the
last frame number, the system will display the last frame.
parameters. If none of the three are entered, the first frame will be displayed
Note: Even if you only provide one view_name, the frame number will be applied to the
the analysis_name parameter). If you only provide analysis_name (view_name
parameter is omitted), any views that contain the model indicated by analysis_name will
be affected.
file parasolid read
4. The geometry specified in the part_name parameter will be defined with respect to the global
reference frame within the iges file.
You can identify a part by typing its name or by picking it from the screen.
If the part is not visible on the screen, you must type the name (you may find it convenient to type
the name even if the part is visible). If you created the part by reading a dataset or graphics file, the
part name is the letters par followed by the dataset part ID number.
For example, the name of Adams PART/101 is PAR101. If you created the part during preprocessing,
you will have given it a name at that time. If a part is available by default, you can identify it by
entering only its name. If it is not, you must enter its full name.
To identify a part under another model, for example, you may need to enter the model name as well.
For example, you may specify part arm from model robot by entering .robot.arm. If you type a ?,
Adams View will list the parts available by default.
file parasolid read

Imports Parasolids geometry. See Manage Geometry Options for more information.
When you import Parasolids geometry, Adams View reads the file and converts the geometry into a set of
Adams geometric elements. By importing geometry from standard CAD packages you can reduce the need
to recreate geometry primitives within Adams, and you can enhance your ability to realistically view the
behavior of complicated mechanical systems.
You can associate the geometry that you import with an existing part or create a new part with which to
associate it.
Format:
file parasolid read
file_name = string
type = parasolid_file_type
model_name = new or existing model
part_name = new or existing body
location = location
relative_to = existing model,part or marker
file 59
file parasolid read
Example:
file parasolid read &
file_name = "d:/examples/engine/crankshaft.xmt_txt" &
type = ascii &
explode_assemblies = boolean
Description:

file_name(required) String Specifies the name of the file that is to be read.
type(optional) Ascii/binary/neutral Specifies the internal format. The options are:
ASCII, binary, and neutral.
model_name(required) New Or Existing Model Enter the model name under which you want to
store the geometry.
part_name(required) New Or Existing Body Enter the part name under which you want to
store the geometry.
location(optional) Location Specifies the translational position where the
geometry in the imported file is to be located
relative to the Adams View part lprf.
orientation(optional) Orientation Specifies the angular position where the geometry
in the imported file is to be oriented relative to
the Adams View part lprf.
file parasolid read

relative_to(optional) Existing Body,part Or Specifies the coordinate system relative to which
Marker the location coordinates and orientation angles
exist.
explode_assemblies(optio Yes/no Specifies whether or not each geometric entity in
nal) an assembly is created as an separate marker
(yes) or consolidated into one (no). no is the
default.
ref_markers global/local Upon import Adams creates reference markers to
correspond with each piece of geometry created
in the Adams model. These markers are typically
automatically named with the prefix PSMAR.
These reference markers are usually located and
oriented at the origin of the Adams model.
However, sometimes the geometry in the CAD
file was created in such a way in the CAD system
that it has a location/orientation transformation
value relative to the CAD assembly/part origin.
For example, the geometry was created via a

copy/paste/move action performed on an original
piece of geometry, or an assembly is composed of
a number of parts/sub-assemblies re-located
relative to the origins about which they were
originally modelled.
In these scenarios, setting the option Reference

Markers to “Local” will locate/orient the Adams-
created reference markers by applying the same
location/orientation transformation value used in
construction in the CAD system to the marker
relative to the Adams model origin. Setting the
option Reference Markers to “Global” will
locate/orient all reference markers at the origin of
the Adams model.
The default is "Global".
file 61
file postprocessing
It's not necessary to enclose the file name in quotes if it only contains alphanumeric characters and
2. The coordinates specified in the location parameter can be relative to any other coordinate system
defined in the Adams View model.
By default, you supply Cartesian (x, y, z) coordinates. You can use the defaults units
coordinate_system_type = command to change this convention. For example, selecting cylindrical
means that you will subsequently be supplying r, theta, and z coordinates.
3. Adams View orients the coordinate system by starting from the initial coordinate system and applying
three successive rotations. Depending on the convention you have selected, the rotations may occur
about space-fixed or body-fixed axes in any meaningful combination of the x-, y-, and z-axes.
By default, you supply Euler (known as body313, or body-fixed z, x, z) angles. You can change this
convention with the defaults units orientation_type = command. For example, selecting space123
means you will subsequently be supplying space-fixed x, y, and z, angles.
relative_to parameter. The default for the relative_to parameter is the default coordinate system.
4. If you don't specify the “relative_to” parameter, Adams View uses the default coordinate system. The
default coordinate system is initially your model, that is, the global coordinate system. You can change
the default coordinate system using the defaults coordinate_system command.
file postprocessing
Allows you to export data from Adams View for use with a stand-alone version of Adams PostProcessor. When
you export Adams PostProcessor files, Adams View generates a command file (.cmd) and all required
supporting files, including:
 Dataset (.adm) file
 Shell (.shl) files needed for geometry representation
 Matrix (.mtx) files for use with the .adm file, if needed
The command file also contains commands to read in the other files when you import the command file into
Adams PostProcessor.
Adams View names the command file ModelName_to_ppt.cmd, where ModelName is the name of the
model.
Format:
file postprocessing
model_names = existing models
file render read
Example:
file postprocessing &
model_names = suspension14
This will create a file called suspension14_to_ppt.cmd which can be used with Adams postprocessor.
Description:

Model_names Existing model Specifies the models for which you want to export
information.
Cautions:
The simulation results are not referenced in the command file. You must import the analysis files (graphics,
request, and results files) separately into Adams PostProcessor.
file render read

Format:
file render read
file_name = string
scale = real
location = location
Example:
file render read &
file_name = “c:\users\ashish\render” &
part_name = ground &
scale = 2
file 63
file render read
Description:

file_name String Specifies the name of the file that is to be read
part_name An Existing Part Specifies the name of an existing Adams View part onto which the
translated geometry will be placed
scale Real Specifies the scale factor to be applied to the size of the geometry
created in Adams View
location Location Specifies the translational position where the geometry in the
imported file is to be located, relative to the Adams View part lprf
orientation Orientation Specifies the angular position where the geometry in the imported file
is to be oriented, relative to the Adams View part lprf
relative_to An Existing Model, Specifies the coordinate system, relative to which the location
Part Or Marker coordinates and orientation angles exist.
1. It is not necessary to enclose the file name in quotes if it only contains alphanumeric characters and
2. You can place the geometry upon a part and use it for preprocessing and postprocessing. Markers
created by the iges translator will be located on the part you specify in this parameter.
You can identify a part by typing its name or by picking it from the screen. If the part is not visible
on the screen, you must type the name (you may find it convenient to type the name even if the part
is visible).
If you created the part by reading a dataset or graphics file, the part name is the letters par followed
by the dataset part ID number. For example, the name of Adams PART/101 is PAR101. If you
created the part during preprocessing, you will have given it a name at that time.
If a part is available by default, you can identify it by entering only its name. If it is not, you must
enter its full name. To identify a part under another model, for example, you may need to enter the
model name as well. For example, you may specify part arm from model robot by entering .robot.arm.
If you type a ?, Adams View will list the parts available by default.
3. The default scale factor is 1.0.
Scale factor influences geometry created in Adams View with respect to the geometry in the imported
file, as follows:
• A scale factor of 1.0 - Geometry will be the same size.
• A scale factor of less than 1.0 - Reduces the size of geometry.
file request read
• A scale factor greater than 1.0 - Increases the size of geometry.

For example, assume that the scale factor is 0.5. Then, a cylinder of length 2 m and diameter .5 m
would be translated to Adams View with the length of 1 m and diameter of .25 m. The distance from
geometry to the realtive_to coordinate system will be scaled accordingly. If the previously mentioned
cylinder was located at 3,2,0 in the iges file, it would be located at 1.5,1,0 after it is translated to
Adams View.
This parameter does not affect the orientation of geometry.
4. These coordinates can be relative to any other coordinate system defined in the Adams View model.
By default, you supply Cartesian (x, y, z) coordinates. You can use the defaults units
coordinate_system_type = command to change this convention. For example, selecting cylindrical
means that you will subsequently be supplying r, theta, and z coordinates.
5. These orientation coordinates can be relative to any other coordinate system defined in the Adams
View model.
Adams View orients the coordinate system by starting from the initial coordinate system and applying
three successive rotations. Depending on the convention you have selected, the rotations may occur
about space-fixed or body-fixed axes in any meaningful combination of the x-, y-, and z-axes.
By default, you supply Euler (known as body313, or body-fixed z, x, z) angles. You can change this
convention with the defaults units orientation_type = command. For example, selecting space123
means you will subsequently be supplying space-fixed x, y, and z, angles.
relative_to parameter. The default for the relative_to parameter is the default coordinate system.
6. If you do not specify the relative_to parameter, Adams View uses the default coordinate system. The
default coordinate system is initially your model, that is, the global coordinate system. You can change
the default coordinate system using the defaults coordinate_system command.
file request read

Allows you to read a request file into Adams View so the information contained may be plotted, manipulated
or viewed. When specifying the name of the request file to be read, the extension .REQ will be appended by
default. This may be overridden by specifying a different extension.
You can import multiple files if you associate and store the files with a model. Adams View reads and creates
all analysis files under the specified model. If you do not provide a model name, Adams View reads each
analysis file into its own model.
If you select to associate the files with a particular simulation, you can only import one set of output files
generated from the same Adams Solver simulation. Adams View uses the time-date stamp placed at the
beginning of each output file to determine if the files were generated by the same simulation run.
When Adams View reads a request file, it creates a new analysis. Each block of data in the request file that
corresponds to a request statement in the Adams View input data is stored as result set in the analysis. The
default name of the analysis will be the name of the request file, excluding the extension.
file 65
file request read
You can overwrite the default analysis name using the file_name parameter. The name of each result set will
be req with the request statement ID appended to it. For example, request/1508 would produce a result set
name of req1508.
Format:
file request read
file_name = string
analysis_name = new or existing analysis
force = force_units
mass = mass_units
time = time_units
request_ids = integer
disk_based_results = boolean
Example:
file request read &
file_name = "c:\\my documents\last_run.req" &
disk_based_results = yes &
request_ids = 5 &
time_step_skip = 1 &
length = meter &
mass = kg &
time = millisecond &
force = newton
Description:

file_name(required) String Specifies the name of the file that is to
be read.
model_name(optional) New or Existing Model Specifies a new or an existing model.
analysis_name(optional) New or Existing Analysis Specifies the name of the analysis in
which to store output files.
file request read

length(optional) Mm, Cm, Meter, Km, Inch, Specifies the length units in the file, if
Foot,mile. different than the current default.
force(optional) Newton, Knewton, Dyne, Specifies the force units in the file, if
Pound_force, Kpound_force, different from the current default.
Kg_force, Ounce_force,
Millinewton, Centinewton,
Poundal.
mass(optional) Kg, Gram, Pound_mass, Specifies the mass units in the file, if
Kpound_mass, Slug, different from the current default.
Ounce_mass, And Tonne.
time(optional) Millisecond, Second, Minute, and Specifies the time units in the file, if
Hour. different from the current default.
disk_based_results Yes/No Specifies whether or not to store data on
(optional) disk. Enter either yes or no.
request_ids(optional) Integer Specifies a list of integers corresponding
to the Adams IDs of the requests you
want read from the file. If blank, then
Adams reads all requests from the file.
time_step_skip (optional) Integer Specifies whether or not to skip time
steps by specifying a pattern of time
steps to skip.
1. For the filename parameter, The .req extension is the default, but you can override it by supplying a
2. You can identify a model by typing its name or by picking it from the screen:
If the model is not visible on the screen, you must type the name (you may find it convenient to type
the name even if the model is visible). You must separate multiple model names with commas.
If the model is visible in one of your views, you can identify it by picking on any of the graphics
associated with it. It is not necessary to separate multiple model picks with commas.
3. When Adams View reads a request, graphics, and results file (.req, .gra, and .res, respectively) with
Adams View requires that simulations have unique names. Therefore, if an analysis already exists with
the same name as your files, use this parameter to assign a unique name at the time of reading the
file(s).
file 67
file request write
4. If you do not specify the “length”,”mass”,“time” or “force” parameter, Adams View reads or writes
the file using your default modeling units.
If you want to read or write a file with units other than those you are currently using, you must specify
this parameter. Specifying this parameter, however, does not change your default modeling units; it
only overrides them during the file read or write operation.
If you want to change your default modeling units, use the defaults units command.
5. If you specify yes for the “disk_based_results” parameter, only the header information from the file is
made memory resident, the bulk of the data remains on disk. This can significantly slow down
operations for small files where leaving on disk merely adds overhead, but for very large files, it can
have the opposite effect and improve performance due to the reduced memory footprint.
6. If you have a large request file with unnecessary fine time resolution, specifying a time_step_skip can
significantly reduce the amount of memory used to store the data.
For example, if you specify time_step_skip = 1, the pattern starts at 1, skips one, takes step 3, and so
on: 1,3,5,7,... A value of 2 would result in 1,4,7,10,13,...
file request write

Allows you to export a request file from Adams View. A Request file contains requests for standard
displacement, velocity, acceleration, or force information. You can also define other quantities (such as
pressure, work, energy, momentum, and more) that you want as output during a simulation.
Format:
file request write
file_name = string
Example:
file request write &
file_name = “c:\analysis\analysis_1”
Description:

analysis_name Existing Analysis Specifies the name of the analysis from which data should be
extracted to write the request file.
file_name String Specifies the name of the file that is to be written.
file results read
file results read

Allows you to read a results file into Adams View so the information contained may be plotted, manipulated
or viewed. When specifying the name of the results file to be read the extension RES will be appended by
default. This may be overridden by specifying a different extension.
Format:
file results read
file_name = string
mass = mass_units
time = time_units
force = force_units
Skip_time_interval = integer
Skip_contact_interval = integer
Example:
file results read &
file_name = "c:\model_1.res" &
disk_based_results = yes
file 69
file results read
Description:

analysis_name An Existing Specifies the name of the analysis to store the Adams output
Analysis in.
executed.
length Linear_units Specifies the length units in the file, if different from the
current default.
mass Mass_units Specifies the mass units in the file, if different from the
current default.
time Time_units Specifies the time units in the file, if different from the
current default.
force Force_units Specifies the force units in the file, if different from the
current default.
Skip_time_interval Integer Specifies whether or not to skip time steps by specifying a
pattern of time steps to skip in the result file. This should be
greater than or equal to 0.
Skip_contact_interval Integer Specifies whether or not to skip contact steps by specifying
a pattern of time steps to skip in the result file. This should
be greater than or equal to 0.
associated with it.
2. When Adams View reads a graphics file (.GRA), a request file (.REQ), a results file (.RES), or all three
with the FILE ANALYSIS READ, it stores them in an analysis. By default, the name of the analysis
is the file name excluding the extension.
3. The proper extension for the file is the default but can be overridden by simply supplying a different
extension.
file results write
4. If you do not use the length/mass/time parameter, Adams View will read or write the file using your
default modeling units. You only need to enter this parameter when you wish to read or write a file
with different units than those you are currently using.
5. If you have a large result file with unnecessary fine time resolution, specifying a skip_time_interval
and skip_contact_interval can significantly reduce the amount of memory used to store the data as
well as reduce the reading time.
If the skip_time_interval and skip_contact_interval are not provided or if their values are both 1 then
the entire result file is read as usual. If the skip_time_interval is for example 3, and the
skip_contact_interval is 4 for a result file with the name test.res, then every 3rd step (not including
initialCondition, input and contact step) and every fourth contact step is included in the new results
file with the name test_3_4.res. This file after shrinking is read into Adams View instead of the original
file. This file is stored in the same location as the original result file.
file results write

Allows you to write results to a results (.res) file.
Format:
file results write
file_name = string
Example:
file results write &
file_name = "c:\model_1.res"
Description:

analysis_name(required) An Existing Analysis Specifies the name of the analysis from which data
should be extracted to write the graphics file.
file_name(required) String Specifies the name of the file that is to be written.
file 71
file rpc read
1. The analysis_name parameter specifies the name of the analysis to store the Adams output in. When
Adams View reads a graphics file (.GRA), a request file (.REQ), a results file (.RES), or all three with
the FILE ANALYSIS READ, it stores them in an analysis. By default, the name of the analysis is the
2. The results file has a .res extension by default, but you can override it by supplying a different
extension.
file rpc read

Allows you to read RPC III files into Adams View.
MTS Systems Corporation created the Remote Parameter Control (RPC) III file format. This format has
become a standard for writing time history information of loads, forces, and accelerations. With RPC III, you
can input data from durability test machines and output data to any RPC III-compatible programs. This
topic contains an overview of the RPC III format. For a detailed description of the RPC III format, see
www.mts.com.
RPC III files are sequential and fixed-length with 512-byte records. The files begin with a standard header
that describes the file contents. The header includes a FORMAT flag that specifies one of four data formats:
 BINARY_IEEE_LITTLE_END - used on Windows systems
 BINARY_IEEE_BIG_END - used on Linux systems
 BINARY - used on VAX systems
 ASCII
Adams View and Adams Durability can read any of the binary formats, so from the point of view of an Adams
user, these files are portable between platforms. These products can also write RPC III files in the
BINARY_IEEE_LITTLE_END format because MTS only provides RPC III software for the Windows
platform.
The RPC III file format supports multi-channel time history data with a fixed sample rate or time step.
Adams View and Adams Durability support an unlimited number of channels. These binary files map real
data into a short (2-byte) signed integer with the header providing a scaling factor for each channel. Because
the scaling factor essentially determines where the decimal point appears in these signed numbers, the
maximum resolution of data in an RPC III file is 0.0000305 () when the scaling factor is 1.
A key point to remember is that data that varies less than the magnitude of the channel resolution will not be
reflected in an RPC III file. For example, with a scaling factor of 1, changes less than ±0.0000305 will not
register in the RPC III data file.
file rpc write
Format:
file rpc read
rpc_object_name = dac_file_object_name
Description:

File_name String Specifies the name of the file that is to be read,
Rpc_object_name RPC_file_object_name Specifies the name of the RPC object that is to hold
the RPC data. If unspecified, uses the file name.
The proper extension in the file_name parameter is the default, but you can override it by supplying a
file rpc write

Allows you to write out RPC III files from Adams View. This technique does not require you to set up
requests before running the simulation.
By definition, results output to an RPC III must have constant time steps. If the results data being output
includes non-constant time steps, Adams View issues a warning and the time axis of the data will be warped
so that the time interval is constant.
MTS Systems Corporation created the Remote Parameter Control (RPC) III file format. This format has
become a standard for writing time history information of loads, forces, and accelerations. With RPC III, you
can input data from durability test machines and output data to any RPC III-compatible programs. This
topic contains an overview of the RPC III format. For a detailed description of the RPC III format, see
www.mts.com.
RPC III files are sequential and fixed-length with 512-byte records. The files begin with a standard header
that describes the file contents. The header includes a FORMAT flag that specifies one of four data formats:
 BINARY_IEEE_LITTLE_END - used on Windows systems
 BINARY_IEEE_BIG_END - used on Linux systems
 BINARY - used on VAX systems
 ASCII
file 73
file rpc write
Adams View and Adams Durability can read any of the binary formats, so from the point of view of an Adams
user, these files are portable between platforms. These products can also write RPC III files in the
BINARY_IEEE_LITTLE_END format because MTS only provides RPC III software for the Windows
platform.
The RPC III file format supports multi-channel time history data with a fixed sample rate or time step.
Adams View and Adams Durability support an unlimited number of channels. These binary files map real
data into a short (2-byte) signed integer with the header providing a scaling factor for each channel. Because
the scaling factor essentially determines where the decimal point appears in these signed numbers, the
maximum resolution of data in an RPC III file is 0.0000305 () when the scaling factor is 1.
A key point to remember is that data that varies less than the magnitude of the channel resolution will not be
reflected in an RPC III file. For example, with a scaling factor of 1, changes less than ±0.0000305 will not
register in the RPC III data file.
Format:
file rpc write
result_set_component = existing result_set
Example:
file rpc write &
file_name = c:\data\rpc_format &
result_set_component = my_result_set
Description:

executed.
Result_set_component Existing result set Identifies the components of an existing result set. The
components must be in an existing result set and reference
to the component must include the result set name.
1. The proper extension in the file_name parameter is the default, but you can override it by supplying
file rpc write
2. For example, assume you read a request file named shift.req, and this request file contains the result
set REQ1. If you want to refer to the X component in the result set REQ1, enter .SHIFT.REQ1.X
(you can omit .SHIFT. if SHIFT is the current analysis_name). SHIFT refers to the analysis name
from which the result set came (or is stored under).
request 101 from an analysis named test can be referred to as .test.req101.
The table illustrates the default names assigned to result sets and result set components read from
Result set naming
vx vy vz wx wy wz
accx accy accz wdx wdy

wdz
fmag1 tmag1

fmag2 tmag2

fmag3 tmag3
file 75
file shell write
file shell write

Allows you to export shell geometry from existing geometry in your model.
Format:
file shell write
file_name = string
shell_name = existing shell
Example:
file shell write &
file_name = "c:\mydir\desktop\shell"
Description:

file_name String Specifies the name of the file that is to be written
shell_name Existing Shell Name of the shell object in your model that you want to write to a file.
The proper extension is the default, but you can override it by supplying a different extension.
file spread_sheet write

Allows you to write out a tab delimited file from an existing Adams View result set.
Format:
file_name = string
result_set_name = an existing result set
Example:
file spread_sheet write &
file_name = "c:\mydir\desktop\shell"
Description:

executed.
result_set_name An Existing Result Set This parameter allows you to identify a result set name.
1. Any result set in Adams View that was created by reading in a REQUEST, or RESULTS file can be
output into tab delimited spread sheet format.
You will be required to specify a file name and the result set name you wish to be written out.
Example:
FILE SPREAD_SHEET WRITE FILE_NAME=REQ5.sps RESULT_SET_NAME=REQ5
2. The proper extension is 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.
3. A result set is a storage place for any kind of numeric tabular data. A result set can contain "n"
components. A component is most usually set up to contain vector components of values like
displacement, velocity, acceleration, force, etc. However, in this case, a result set is completely general
and can store any numeric value in a component with only a few exceptions. These exceptions are
those cases when the user asks the system to mix incompatible value types like complex in the same
component as real values.
This is a required parameter and the result set name given must be within a particular analysis. A result
set name may be arbitrarily long and a combination of letters of the alphabet and numbers may be
used. The leading character must be a letter.
Result Sets are associated with an analysis run and can be identified as such. A result set associated
with request 101 from an analysis named "test" is referred to as .test.req101.
Several predefined result set types are created when Adams request and result files are read into Adams
View. For example, assume you have read a request file called "SHIFT.REQ", and this request file
contains the result information for the Adams statement REQUEST/1. The result set will be named
REQ1, and may also be referred to relative to the analysis name .shift.req1. If you wish to refer to a
component in the same result set the full name for the X component would be .SHIFT.REQ1.X.
The following table illustrates the default names assigned to result sets and result set components read from
request (.REQ) and results (.RES) files.
file 77
vx vy vz wx wy wz
accx accy accz wdx

wdy wdz
joint JOIxxx... fx fy fz tx ty tz fmag results file
tmag
jprim JPRxxx... fx fy fz tx ty tz fmag results file
tmag
motion MOTxxx... fx fy fz tx ty tz fmag results file
tmag
coupler COUxxx... fx1 fy1 fz1 tx1 ty1 results file
tz1 fmag1 tmag1
fx2 fy2 fz2 tx2 ty2

tz2 fmag2 tmag2
fx3 fy3 fz3 tx3 ty3

tz3 fmag3 tmag3
sforce SFOxxx... fx fy fz tx ty tz fmag results file
tmag
spring damp SPRxxx... fx fy fz tx ty tz fmag results file
tmag
bushing BUSxxx... fx fy fz tx ty tz fmag results file
tmag
beam BEAxxx... fx fy fz tx ty tz fmag results file
tmag
field FIExxx... fx fy fz tx ty tz fmag results file
tmag
user request UREQxxx... u1 u2 u3 u4 u5 u6
u7 u8
request REQxxx... x y z r1 r2 r3 mag
amag
file stereo_lithography read

Allows you to import stereo lithography (SLA) geometry into Adams. As you import the SLA geometry, you
associate the geometry with an existing part or you create a new part with which to associate it.
Format:
file_name = string
scale = real
location = location
Example:
file stereo_lithography read &
file_name = "c:\mydir\desktop\steriolitho" &
scale = 2 &
location = 2,90,50
Description:

executed
part_name An Existing Partf Specifies the name of an existing Adams View PART onto
which the translated geometry will be placed
scale Real Specifies the scale factor to be applied to the size of the
geometry created in Adams View
location Location Specifies the translational position where the geometry in the
IGES file is to be located relative to the Adams View part lprf
orientation Orientation Specifies the angular position where the geometry in the
IGES file is to be oriented relative to the Adams View part
lprf
relative_to An Existing Model, Specifies the coordinate system that location coordinates and
Part Or Marker orientation angles correspond to
file 79
2. The geometry may be placed upon a part and used for preprocessing and postprocessing. Markers
created by the IGES translator will be located on the part specified in this parameter.
associated with it.
3. The default scale factor is 1.0. If the scale factor of 1.0 is used the geometry created in the Adams
VIEW will be the same size as the geometry in the IGES file. A scale factor less than 1.0 will reduce
the size of geometry and a scale factor greater than 1.0 will increase the size of the geometry. For
example, assume the scale factor specified is 0.5, a cylinder of length 2 meters and diameter .5 meters
would be translated to Adams View with the length of 1 meter and diameter of .25 meters. The
distance from geometry to the RELATIVE_TO coordinate system will be scaled accordingly. If the
previously mentioned cylinder was located at 3,2,0 in the IGES file, it would be located at 1.5,1,0
after it is translated to Adams View.
The orientation of the geometry is not affected by the SCALE parameter.
4. These coordinates can be relative to any other coordinate system defined in the Adams View model
(See the RELATIVE_TO parameter for this command).
5. These orientation coordinates can be relative to any other coordinate system defined in the Adams
View model (See the RELATIVE_TO parameter for this command).
file table write
By default, you supply Euler (known as body313, or body-fixed z, x, z) angles. You may change this
convention with the 'DEFAULTS UNITS ORIENTATION_TYPE=' command. For example,
selecting SPACE123 means you will subsequently be supplying space-fixed x, y, and z, angles.
system.
6. Refer to the Appendix on "Specifying Locations and Orientations in Adams View" in the Adams
View Users Manual for more information on the ORIENTATION parameter.
7. If relative_to parameter is not specified, the default coordinate system is used. The default coordinate
system is initially your model, that is, the global coordinate system. You may change the default
coordinate system using the 'defaults coordinate_system' command
.
Caution: File name required for file stereo_lithography read part_name
file table write

Allows you to write a plot out as a table.
Format:
file table write
file_name = string
format = string
Example:
file table write &
write plot_name = plot_1 &
file_name = "c:\mydir\desktop\table" &
format = html
Description:

plot_name Existing Plot Specifies the name of the plot from which the curves are to be extracted as
the source for the table's data.
file_name String Specifies the name of the file in which to store the table. If blank, uses the
name of the plot.
format String Specifies the format of the table (HTML or spreadsheet)
file 81
file table write
1. HTML is the default. If you specify spreadsheet, then the command is the same as the file spreadsheet
write command except that it takes its data from a plot curve.
file temporary_settings apply

Allows you to apply the settings within one or more Temporary Settings Files (TSF) to a model.
A Temporary Settings File (TSF) contains sets of model parameter data that can be applied "temporarily" for
a given simulation. When you apply an Adams Temporary Settings file with this command, the contents of
that file actually replace those in the current Adams View database.
Format:
file_name = String
model = String
Example:
file temporary_settings apply &
file_name = "c:\mydir\desktop\easy_model.tsf" &
model = Model_1
Description:

file_name String Specifies the name of one or more TSF files to be applied
model String Specify the model name
1. The default file extension is .tsf but it can be overridden by simply supplying a different extension.
3. To apply multiple temporary settings files at once with this command separate the file names in the
File_name argument commas like so: "c:\mydir\desktop\easy_model.tsf",
"c:\myotherdir\files\moderate_model.tsf", "c:\mydir\other_files\aggressive.tsf"
4. The same object property or solver setting can be specified more than once in single apply command
because it appears more than once within a single .tsf file and/or within the set of .tsf files specified in
a single apply command. However, Adams View will apply only the value specified nearest the
bottom of the last .tsf file in the list of files supplied through this apply command in which the
redundant property/setting has been specified.
5. If an invalid value is specified for a given object property or solver setting, then Adams View will
ignore this and move on to the next setting within the .tsf
file 83
file temporary_settings write
6. The properties set via a "file temporary_settings apply" command can be returned to their original
values using the "file temporary_settings revert" command
7. The revert command only reverts the settings from the most recently issued "file temporary_settings
apply" command. So, be aware that issuing two (or more) apply commands without revert commands
in between makes the changes from all but the last apply command unresponsive to the revert
command.

Allows you to write Temporary Settings File (TSF).
Specified object property values and solver settings values are written to a TSF file.
Format:
file_name = String
object_properties = Strings
Values = Strings
solver_properties = Strings
Settings= Strings
Example:
file temporary_settings write &
file_name = "c:\mydir\desktop\model_x.tsf" &
object_properties = "DV_1.value", "JOINT_1.j_marker_name", "motion_1.function" &
Values = "11.0", ".MODEL_1.ground.MARKER_4", "PI*30" &
Solver_properties = "debug.dump", "equilibrium.alimit", "integrator.formulation",
"linear_solver.solver" &
Settings = "True", "9.0", "i3", "auto"
file temporary_settings revert
Description:

file_name String Specifies the name of the TSF file that is to be written.
object_properties Strings An array of object property strings that specifies the Adams object
properties to be set. Uses the form of Adams python syntax; that is,
object_name.property.
values Strings Specifies the values of the object properties. It is string array of
values for object properties. The number of strings in object
properties should be equal to the number of strings in values.
solver_properties Strings Specifies Adams solver properties in the form of Adams python
syntax; that is, SolverSettings.property. You can specify one or more
properties.
settings Strings A string array that specifies the settings for the corresponding solver
properties declared in the solver_properties array. The number of
strings in solver_properties should be equal to the number of
strings in settings

Allows you to revert the object and solver properties which had been applied with a Temporary Settings File
(TSF) apply command.
After using this revert command, any properties set by the most recently issued "file temporary_settings apply"
command with be reset to the values they had just prior to that "file temporary_settings apply" command
being issued.
Because the revert command only reverts the settings from the most recently issued "file temporary_settings
apply" command, be aware that issuing two (or more) apply commands without revert commands in between
makes the changes from all but the last apply command unresponsive to the revert command.
Format:
model = String
Example:
file temporary_settings revert &
model = Model_1
file 85
file testdata read measures
Description:

model String Specify the model name in which to revert from TSF-applied property
values to the values stored in the database prior the TSF application.

Allows you to import test data as measures
Format:
model_name = a new or existing model
analysis_name = a new or existing analysis
use_file_column_labels = boolean
units = string
independent_column_index = integer
file_name = string
Example:
file testdata read measures &
use_file_column_labels = yes
Description:

model_name A New or Existing Model Specifies an existing model
analysis_name A New or Existing Analysis Specifies an existing analysis
use_file_column_labels Boolean Specifies how to define the names of the
measures
units String Allows you to specify the type of units to be
used for this object.
independent_column_index Integer Specifies which column in the data file
contains the x-axis data.
file_name String Specifies the name of the file that is to be
read, written, or executed
associated with it.
2. You may identify an analysis by typing its name or by picking it from the screen.
An analysis may be picked from the screen if you have read an Adams Graphics file, and use the
GRAPHIC_RESULTS command to display it. If the analysis is not visible on the screen, you must
type the name. You may also find it convenient to type the name even if the analysis is displayed.
You may have explicitly named the analysis when you created it by reading one or more Adams output
files. By default, the name of the analysis is the root name of the Adams output files. If you created
the analysis by reading an Adams Graphics file, for instance, the analysis name is the name of the
graphics file without the .gra extension.
You may get a list of analysis by typing a "?" in response to a parameter that requires an analysis name
be entered.
You must separate multiple analysis names by commas.
If the analysis is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple analysis picks by commas.
See Also getting_started - for naming syntax and wildcards.
3. If there are textual column headers in the file, select yes. Adams uses the column header text as the
names of each measure. Values are: yes and no.
4. Since this object can be used in a variety ov contexts, Adams View cannot determine what type of
5. Enter the column number. Adams uses all other columns as the y-axis data. It is used as the
independent data for the measure.
file 87
file testdata read splines

Format:
model_name = a new or existing model
use_file_column_labels = boolean
units = string
independent_column_index = integer
file_name = string
Example:
file testdata read splines &
use_file_column_labels = yes &
independent_column_index = 3
Description:

model_name A New Or Existing Specifies an existing model
Model
use_file_column_labels Boolean Specifies how to define the names of the splines
units String Allows you to specify the type of units to be used
for this object.
independent_column_index Integer Specifies the column number to indicate which
column in the file to use for the independent data
(X parameter) in the Adams spline.
file_name String Specifies the name of the file that is to be read,
written, or executed
associated with it.
file text close

2. If there are textual column headers in the file, select yes. Adams uses the column header text as the
names of each spline.Values are: yes and no. The default is no.
3. Since this object can be used in a variety of contexts, Adams View cannot determine what type of units
it should have. By telling Adams View what the unit type for this object is, Adams View can preform
the proper conversions on the values you specify.
4. The columns are numbered sequentially from left to right starting with 1, 2, 3, and so on.
If you specify an independent data index for splines, Adams does not create a spline for the column
of the file with that index. Instead, that column of data is used as the x data for all splines. If you do
not include an independent column index, then the series of numbers 1, 2, 3, and so on is used for
the x data of all splines.
file text close

Indicates that the text file is to be closed.
Format:
file text close
file_name = string
Example:
file text close &
file_name = “C:\Model_Data.txt”
Description:

file_name String Specifies the name of the input or output text file to be closed.
1. If you do not specify a file_name parameter, then the last opened, or written file is assumed. After a
file has been closed, any attempts to write to it will cause an error.
2. The proper extension for file_name parameter is the default (.txt) but can be overridden by simply
file 89
file text open
file text open

Allows you to open a text file for writing.
Format:
file text open
file_name = string
open_mode = open_mode
Example:
file text open &
file_name = "c:\data.txt" &
open_mode = append
Description:

file_name String Specifies the name of the input or output text file.
open_mode Open_mode Specifies the mode in which the file is to be opened, thereby determining
which operations are valid for this file. Available values are: APPEND and
OVERWRITE.
1. Depending upon the open_mode the file can either be overwritten completely or appended.
2. You may use the file_name later in file text write or file text close commands to indicate
which file you wish to operate upon.
The proper extension for file_name parameter is the default (.txt) but can be overridden simply by
3. If the file is opened with open_mode=OVERWRITE, any existing file with the name given in the
file_name parameter is deleted at the time of the OPEN. If the file is opened with
open_mode=APPEND, then any existing file is appended by subsequent WRITEs (the file need not
exist for the APPEND mode to work).
file text write
file text write

Indicates that output composed of the values_for_output is to be sent to the specified destination, using the
given format.
Format:
file text write
file_name = string
variable_name = an existing vvar
format_for_output = string
values_for_output = string
newline = boolean
Example:
file text write &
format_for_output = "the varmint is a %s, kill it %s." &
values_for_output = "snake", "now"
Description:

file_name String Specifies the name of the output text file.
variable_name An Existing Vvar Specifies a variable to which Adams View stores a
formatted string.
format_for_output String Specifies the format for the output text.
values_for_output String Specifies the values that are to be placed in the output
string.
newline Boolean Controls whether or not the command causes the output
to terminate the line with this write command.
1. The destination depends on what you specify, a file_name or a variable_name. You may specify
neither, one, or both destinations. If writing to a file, you must open it first.
If you specify neither, Adams View assumes the last opened or written file as the intended destination.
If you specify just the file_name, Adams View writes the output to that file. If you specify just the
variable_name, Adams View assigns the text string to that variable. If you specify both, Adams View
performs both actions.
file 91
file text write
2. The proper extension for file_name parameter is the default (.txt) but can be overridden by simply
3. Output formats are a mixture of text and conversion specifications. Each conversion specification
usually has a matching argument in the values_for_output parameter. A conversion specification
begins with a percent sign, '%', and is terminated by a letter or another percent sign.
FILE TEXT WRITE &
FORMAT_FOR_OUTPUT="The varmint is a %s, kill it %s." &
VALUES_FOR_OUTPUT="snake", "now"
Generates the string "The varmint is a snake, kill it now." to be written to the
appropriate file or variable. Note that there are two conversion specifications (both '%s') and two
values for output.
The conversion specifications provided by Adams View are a subset of those used in the ANSI-C
programming language.
Valid conversion specifiers are:
• % literal percent sign ("%%" is output as "%")
• d integer in base 10, 1 or 123
• e exponential floating point, 1.23e-04
• E exponential floating point, 1.23E-04
• f fixed point real, 345.67
• g general fixed or floating point (depending upon magnitude)
• G general fixed or floating point (depending upon magnitude)
• i same as d, above
• o unsigned integer in base 8 (o is for octal)
• s character string
• u unsigned integer in base 10
• x unsigned integer in base 16 (decimal 10 is 'a', 11 is 'b', etc.)
• X unsigned integer in base 16 (decimal 10 is 'A', 11 is 'B', etc.)
Most conversion specifications may contain flags between the leading percent sign and the
terminating conversion specifier. These flags allow you to tune the format of your output further.
Some of the valid flags are:
- Indicates that the output is to be left justified in the field, with the default being right justification.
This is only useful when the field width is specified, see below.
+ Force a sign to be output for all numeric values.
... FORMAT="%+d %+d" VALUES=(-1), (1)produces -1 +1
0 Forces output of leading zeros when a field width is specified.
file wavefront read
Field width is specified by prefixing the conversion specifier with a number. It determines how much
space is to be reserved for the output text. The following format and values
... FORMAT="%03d%6d" VALUES=(5),(6) generates"005.....6"as
output, where '.' denotes blank space (in this example only).
You specify precision with a number and decimal point following the field width prefix. For instance,
... FORMAT="%5.2f %010.3e" VALUES=(2.3),(5.4)produces the
output:
" 2.30 05.400e+00"
Adams View converts the values for output to the appropriate type for the conversion specifier. Use
of expressions is extremely useful here.
4. If newline is NO, then subsequent WRITEs will produce output along the same line. If newline is
YES , then any succeeding WRITE command will write on a new line. This parameter is optional and
has a default value of YES.
file wavefront read

Allows you to read a Wavefront .obj file into Adams View. Adams View only interprets vertex, face, and group
information. Smoothing groups, textures, and material properties are ignored.
If you want the .obj file to be read such that its contents belong to a single Adams View part, use the
PART_NAME parameter. Adams View will then create a separate shell graphic object for each occurrence of
a group in the .obj file.
If you want the .obj file to be read such that its contents belong to an Adams View mechanism, use the
MODEL_NAME parameter.
Adams View will create a new part for each unique group name in the .obj file. If the same group name
appears more than once, a separate shell object will be added to the part with the same name as the group.
Format:
file wavefront read
file_name = string
part_name = new or existing body
geometry_placed = wave_geom_place
scale_factor = real
set_read_only = boolean
file 93
file wavefront read
Description:

executed.
Model_name New or Existing Model Specifies the name of a new or existing Adams View
MODEL onto which the geometry created from reading
a Wavefront .obj will be placed.
part_name New or Existing Body Specifies the name of a new or existing Adams View PART
onto which the geometry created from reading a
Wavefront .obj will be placed.
geometry_placed, Relative_to_part, Allows you specify whether the coordinates in the
Relative_to_ground wavefront file are to be interpreted as relative to the part
or relative to ground. Adams View writes wavefront files
with the coordinates relative to the parts.
scale_factor, Real Allows you to specify the amount to scale the geometry
that is read in from a Wavefront .obj file. The geometry
will be scaled uniformly in the x, y, and z directions.
set_read_only Yes/No Allows you to specify that all shells created as a result of
reading in a wavefront file are to be tagged as read-only.
This means that any file writing commands (such as file
wavefront write or file iges write) will not output the
read-only shells. There is no way to remove the read-only
setting once the shells have been created.
2. Adams View will create a new part for each unique group name in the .obj file. If the same group name
appears more than once, a separate shell object will be added to the part with the same name as the
group.
file wavefront write
associated with it.
3. Adams View will create a separate shell graphic object on the part for each occurrence of a group in
the .obj file.
associated with it.

Generates a set of input files that are read by the Advanced Visualizer developed by Wavefront Technologies.
The Advanced Visualizer provides high quality rendering and animation for improved visualization of
analysis results.
Adams View generates four types of files with the following extensions:
obj
Each file contains a list of points and polygons that collectively define the geometry on a part. The file name
will be the name of the part with a .obj extension. For example, a part named 'crank' would have an object
file crank.obj. Icons such as markers and center of mass are not written to this file. There will be one object
file created for each part in your analysis.
.chnl
This file contains channel data. Channel data is the translation and orientation of the part for the duration
of the simulation.
file 95
The values in the channel file are x, y, and z translation and body 123 rotation. Note that the orientation of
the parts are not defined in body 323 (Euler angles). The file name will be the name of the part with the .chnl
extension. For example, the part named 'crank' would have a channel file crank.chnl. There will be one
channel file created for each part in your analysis.
.set
The set file contains information to initialize the Advanced Visualizer including camera and lights. The file
name will be the name of the model with a .set extension. For example, a model named 'piston' would have
a set file piston.set. There will only be one set file created.
.cmd
This file is the Advanced Visualizer command file that will load the object files and channel files into the
Advanced Visualizer when executed. Note that this command file is not compatible with Adams View. The
file name will be the name of the model with the .cmd extension. For example, a model named 'piston' would
have a command file 'piston.cmd'. There will only be one command file created.
The graphic Spring Damper, Graphic Force and Outlines that connect markers on more than one part are
not supported.
Graphic attributes associated with geometry, parts, and models are not supported.
Format:
model_name = existing_model
reference = local or global
Example:
file wavefront write &
model_name = model_1
Description:

model_name Existing model Specifies an existing model
Analysis_name Existing analysis Specifies an existing analysis
Part_name Existing part Specifies an existing part
Reference Local or Global The wavefront data will be exported with the local or
global coordinate system
1. You can identify a model by typing its name or by picking it from the screen:
• If the model is not visible on the screen, you must type the name (you may find it convenient to
type the name even if the model is visible). You must separate multiple model names with
commas.
If the model is visible in one of your views, you can identify it by picking on any of the graphics
associated with it. It is not necessary to separate multiple model picks with commas.
2. You can identify an analysis by typing its name or by picking it from the screen:
• You can pick an analysis from the screen if you have read a graphics file, and use the
graphic_results command to display it. If the analysis is not visible on the screen, you must type
the name (you may find it convenient to type the name even if the analysis is displayed).
• You may have explicitly named the analysis when you created it by reading one or more output
files. By default, the name of the analysis is the root name of the output files. If you created the
analysis by reading a graphics file, for example, the analysis name is the name of the graphics file
without the .gra extension.
• You can get a list of analyses by typing a ? in response to a parameter that requires an analysis
name.You must separate multiple analysis names with commas.
• If the analysis is visible in one of your views, you may identify it by picking on any of the graphics
associated with it. It is not necessary to separate multiple analysis picks with commas.
floating_marker 1
floating_marker copy
floating_marker
Allows copying an existing floating marker.
Floating marker specifies a site for applying forces or constraints to parts. The force or constraint dictates the
location and orientation of the floating marker. Therefore, you do not specify a position for a floating marker.
This allows the floating marker’s location and orientation to change with respect to its body coordinate system
during the simulation, as dictated by the force or constraint.
The marker can be copied by using this command.
Format:
floating_marker_name = an existing fmarker
new_floating_marker_name = a new fmarker
Example:
floating_marker copy &
floating_marker_name = FMARKER_12 &
new_floating_marker_name = fmarker_121
Description:

floating_marker_name An Existing Fmarker Specifies the name of an existing floating marker
new_floating_marker_name A New Fmarker Specifies a new name for the copied floating
marker
1. The floating marker has no position or orientation specified. The position and orientation of the
floating marker changes while simulation according to the mode of application of force or constraint
or location of the force on the moving body. For example, the orientation of the force may be set as
moving with the body, fixed in space or between two bodies, which decides the position and
orientation of the force while simulation.
2. The floating marker can be copied to a new floating marker, where a new name can be specified for
the same.
floating_marker create
Allows creation of a floating marker.
Format:
floating_marker_name = a new fmarker
adams_id = adams_id
node_ID = integer
comments = string
Example:
floating_marker create &
floating_marker_name = .model_1.PART_3.FMARKER_12 &
adams_id = 12 &
node_id = 10 &
comments = floating_marker_for_part_3
Description:

floating_marker_name A New Fmarker Specifies the name of a new floating marker
adams_id Adams_id Specifies an integer used to identify this
element in Adams database
node_id Integer Specifies an integer used to identify a node for
a flexible body
comments String Specifies the comments if any for the new
floating marker
1. 1. The floating marker has no position specified. The position and orientation of the floating marker
changes while simulation according to the mode of application of force or constraint or location of
the force on the moving body. For example, the orientation of the force may be set as moving with
the body, fixed in space or between two bodies, which decides the position and orientation of the
force while simuation.
floating_marker 3
floating_marker delete
The ‘adams_id’ specifies an integer used to identify this element in the Adams data file. When you
2. The ‘comment’ specifies comments for the object being created or modified. When an Adams Solver
data file (.adm) is read into Adams View, all comments associated with a statement (from the end of
the previous statement through the end of the current statement) are stored with the object.
Comments in the data file can be associated with model. These comments must follow the title
statement and be followed by the comment 'END OF MODEL COMMENTS'. This string must
be uppercase. When an Adams Solver data file is written, the comments for an object are written
before the statement corresponding to the object. The ‘node_id’ refers to the attachment point of
node on a flexible body.
3. When applied to flexible bodies, a floating marker can be either associated with a node or not (via the
“node_id” argument). Because a floating marker is often moving across the body to which it belongs,
it typically does not make sense to associate a flexible body’s floating marker with any particular node.
Be advised, that this means the reaction loads from the force object which the floating marker
supports will be applied to the rigid body motion of the flexible body and not on a modal basis
deforming the part locally at the nodes near the force application point.
Allows deleting a floating marker.
Format:
Example:
floating_marker delete &
floating_marker_name = FMARKER_11
floating_marker modify
Description:

1. The floating marker has no position or orientation specified. The position and orientation of the
floating marker changes while simulation according to the mode of application of force or constraint
or location of the force on the moving body. For example, the orientation of the force may be set as
moving with the body, fixed in space or between two bodies, which decides the position and
orientation of the force while simulation.
2. The floating marker can be deleted by providing the appropriate floating marker name while the
‘delete’ command
Allows modifying of a floating marker.
Format:
new_floating_marker_name = a new floating marker
adams_id = adams_id
node_ID = integer
comments = string
Example:
floating_marker modify &
floating_marker_name = .model_1.PART_3.FMARKER_12 &
new_floating_marker_name = .model_1.PART_3.FMARKER_13 &
adams_id = 12 &
node_id = 10 &
comments = floating_marker_for_part_3
floating_marker 5
Description:

new_floating_marker_name A New Fmarker Specifies a new name for an existing floating
marker
Adams database
node_id Integer Specifies an integer used to identify a node for a
flexible body
comments String Specifies the comments if any for the new floating
marker
1. The floating marker has no position specified. The position and orientation of the floating marker
changes while simulation according to the mode of application of force or constraint or location of
the force on the moving body. For example, the orientation of the force may be set as moving with
the body, fixed in space or between two bodies, which decides the position and orientation of the
force while simulation.
The ‘adams_id’ specifies an integer used to identify this element in the Adams data file. When you
before the statement corresponding to the object. The ‘node_id’ refers to the attachement point of
node on a flexible body.
3. When applied to flexible bodies, a floating marker can be either associated with a node or not (via the
“node_id” argument). Because a floating marker is often moving across the body to which it belongs,
it typically does not make sense to associate a flexible body’s floating marker with any particular node.
Be advised, that this means the reaction loads from the force object which the floating marker
supports will be applied to the rigid body motion of the flexible body and not on a modal basis
deforming the part locally at the nodes near the force application point.
for 1
for
The FOR and END commands allow you to execute a group of commands a fixed set of times. You can use
FOR either to perform numeric iteration or to operate on a set of Adams View objects, such as markers or
parts. Adams View executes the commands bracketed by FOR and END for each value of a variable in the
specified range or upon the specified set of objects.
Format:
for
variable_name = variable
object_name = existing object
start_value = real
end_value = real
type_filter = object_type
group_name = existing group
echo_all_loops = yes/no
end
Example:
for variable_name=tempreal start_value=1 end_value=10

marker create marker_name=(eval("MAR" // RTOI(tempreal))) &
location=(eval(tempreal-1)), 0, 0
end
In this example, Adams View creates 10 markers, MAR1 through MAR10, on the default part, and locates
them one unit apart on the x-axis of the part's coordinate system.
Description:

variable_name New Variable Specifies the name of the temporary variable to be
created within the loop
object_names Existing Object Specifies an existing object. This is used when FOR
is to be operated on a set of objects.
type_filter Object Type The TYPE parameter applies a filter to the set of
objects.

start_value Real Expression Specifies the starting value of the variable in the
loop.
end_value Real Expression Specifies the last value of the variable in the loop.
Once the loop is executed for this value, it
terminates.
increment_value Real Expression Specifies the increment for the value of the variable
for each iteration in the loop. This can be either
positive or negative.
group_name Existing Group Specifies a group name
echo_all_loops Yes/No Specifies a Boolean value
1. When the FOR statement is operated on objects, the object_name parameter is used.
FOR VARIABLE_NAME=var OBJECT_NAMES=objects &
TYPE=database_object_type
...
END
For this type of FOR loop, Adams View creates a temporary Adams View variable named var of type
OBJECT and successively assigns the value of each object in the set to the variable. The commands
inside the FOR/END pair can use var as they would any other Adams View variable of type OBJECT.
Adams View deletes the variable when the loop terminates.
2. Consider the following example in which Adams View renumbers the Adams IDs of markers
belonging to the part follower, starting at 5000, and incrementing by one for each marker in the set.
for variable_name=the_marker object_names=.fourbar.follower.*
type=marker
marker modify marker_name=(eval(the_marker)) adams_id=(eval(ip))
variable modify variable_name=ip integer_value=(eval(ip+1))
end
You can use the EVAL function to get the instantaneous value of an expression rather than assigning
the expression itself. An expression's value changes whenever the value of any variable in it changes.
Sometimes you want this behavior; other times you do not. Using EVAL avoids this behavior.
As shown, you can use wildcards to specify the objects for the OBJECT_NAME parameter. The
TYPE parameter applies a filter to the set of objects, in this case, matching only children of the part
that are markers.
If you use a more general wildcard, Adams View may execute the command more slowly than if you
use a more specific wildcard. For example, if you want all the markers in the model MOD1, use
OBJECT_NAME=.MOD1.* type=MARKER instead of OBJECT_NAME=* type=MARKER.
force 1
force attributes
force
force attributes
Allows you to specify the attributes to be set on an individual force or a group of forces.
You can set the following attributes on a force:
 SIZE_OF_ICONS / SCALE_OF_ICONS: These two parameters are mutually exclusive. You may
set the size of an icon used for the force representation in modeling units, or you may scale the size of
the icon by a non-unit scale factor.
 VISIBILITY: You may set the visibility of a force ON, OFF or TOGGLE the current setting.
When you set the visibility OFF, the force will not be drawn. When you set the visibility ON, you
allow that force to be drawn.
 NAME_VISIBILITY: You may set the name label visibility of a force ON, OFF or TOGGLE the
 COLOR: You may set the color of a force with this parameter.
If an entity does not have a GRAPHICS ATTRIBUTE setting, the value for that GRAPHIC ATTRIBUTE
may be inherited from another entity. INHERITANCE may either be TOP_DOWN or BOTTOM_UP.
BOTTOM_UP and TOP_DOWN refer to the natural hierarchy of the Adams model. The hierarchy is a tree
structure with the model at the apex. Parts exist beneath the model, and markers exist beneath the parts. If
the icon size of the model is set to 0.1, and the default INHERITANCE is set to TOP_DOWN, then all
icons displayed within the model will be displayed at this size. However, if the icon size of a model is set to
0.1, and then the default INHERITANCE is set to BOTTOM_UP, then any icons set to a size other than
the model's icon size will be displayed at their own size.
Format:
force attributes
force_name = existing force
scale_of_icons = real number
size_of_icons = real number
visibility = on/off/no_opinion/toggle
name_visibility = on/off/no_opinion/toggle
active = on/off/no_opinion
dependents_active = on/off/no_opinion
force attributes
Example:
force attributes &
Force_name = FORCE_1 &
Color = RED &
Name_visibility = OFF &
Active = On &
Dependents_active = OFF
Description:

force_name Existing force Specifies the force to be modified. You use this
parameter to identify the existing force to be
scale_of_icons Real Specifies a unit-less scale factor to apply to the
current icon size.
size_of_icons Real Specifies the size, in modeling units, the Adams
View icons will appear in.
Visibility ON/ OFF/ Specifies the visibility of graphic entities.
NO_OPINION/
TOGGLE
name_visibility ON/ OFF/ The NAME_VISIBILITY parameter provides
NO_OPINION/ control over the visibility of the view name
TOGGLE displayed at the top center position of a given
view.
color Existing color Specifies the color the modeling entity should be
drawn in.
Active On/OFF/NO_OPINION When you set ACTIVE=NO, that element is
dependents_active On/OFF/NO_OPINION When you set ACTIVE=NO, that element is
If the force is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the force is displayed.
force 3
force attributes
associated with it.
in length.
in length.
SIZE_OF_ICONS, the ICONS_SIZE of the model will take precedence.
An Example:
model ---------------------- SIZE_OF_ICONS = .15 meters .part
-------------------- SIZE_OF_ICONS = .125 meters
The icon of the part will be 1.5 meters is size.
If the model has SIZE_OF_ICONS set to 0.0, and a part under that model has a SIZE_OF_ICONS
set to .125, the icon size of the part will be used.
An Example:
model ---------------------- SIZE_OF_ICONS = 0.0 meters .part
-------------------- SIZE_OF_ICONS = .125 meters
The icon of the part will be .125 meters is size.
TOGGLE will take the current state of visibility of an entity and reverse it.
force attributes
Example 1:
.model -------------------------NO_COLOR
.part---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part---------------------- NO_COLOR

command:
force 5
force copy
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
force copy
Allows you to create a replica force within the same model.
This replica force will be identical to the original with the exception of the force name. Forces must have
unique names relative to other forces in a given model. The replica will be completely independent of the
original, and may be modified without affecting the original.
The replica force will use the same markers to define it. The first step after the copy operation may be to
modify the replica to use different markers.
Forces may not be copied from model to model.
Format:
force copy
force_name = Existing force
new_force_name = new force name
Example:
force copy &
force_name = FORCE_1 &
New_force_name = FORCE_1_COPY
Description:

Force_name Existing Force Specifies the force to be copied
New_force_name New force name Specifies the name of the new force
force copy
associated with it.
2. You may use this new_force_name later to refer to this force. Adams View will not allow you to have
two forces with the same name, so you must provide a unique name.
be assigned to it.
Tips:
 Any Adams View object you delete, may be "undeleted" by using the UNDO commands. If you
have deleted something you would like back, enter the command "undo backward", or pick on the
fixed menu entry 'UNDO'.
force 7
force create body gravitational

Allows you to create a gravitational body object.
Format:
gravity_field_name = new_grav_field_na,e
comments = string
units_consistency_factor = real_number
x_component_gravity = real_number
y_component_gravity = real_number
z_component_gravity = real_number
Example:
force create body gravitational &
gravity_field_name = ACCGRAV__1 &
comments = “” &
units_consistency_factor = 0 &
x_component_gravity = 0.8 &
y_component_gravity = 0.8 &
z_component_gravity = 0.7
Description:

gravity_field_name String Specifies the name of the new gravity field.
modified.
units_consistency_factor Real Specifies a conversion factor to make your force, mass,
length, and time units consistent
x_component_gravity Real Specifies the x component of gravitational acceleration
with respect to the ground reference frame.
y_component_gravity Real Specifies the y component of gravitational acceleration
z_component_gravity Real Specifies the z component of gravitational acceleration
1. In conjunction with the part masses, the gravitational field defines a body force at the center of gravity
of each part. The force direction is defined by the X_COMPONENT_GRAVITY,
Y_COMPONENT_GRAVITY, and Z_COMPONENT_GRAVITY parameters. The force
magnitude is the part mass multiplied by the magnitude of the gravity vector. Each gravity field is
written as an Adams ACCGRAV statement. Although Adams View allows you to create more than
one gravity field, you should only use one, since Adams only allows one ACCGRAV statement. You
may also specify UNITS_CONSISTENCY_FACTOR in a gravity field. Adams View writes this as
the GC parameter in the ACCGRAV statement. Although UNITS_CONSISTENCY_FACTOR
affects the reporting of all forces, not just gravitational, it is included here because it also appears in
the ACCGRAV statement.
2. You may use the gracity_field_name name later to refer to this gravity field. Adams View will not
allow you to have two gravity fields with the same name, so you must provide a unique name.
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. Note that you
can specify the parentage of an entity (for example, what part “owns" a marker or a geometry
be assigned to it.
3. You may select any force, mass, length, or time units you wish. In order for Adams results to be
meaningful, however, you or Adams View must compute a factor such that the equation Force =
(Mass / UNITS_CONSISTENCY_FACTOR) * Acceleration is satisfied. For example, if you use
Newtons, kilograms, millimeters, and seconds, UNITS_CONSISTENCY_FACTOR is 1000.
Adams documentation and Data Set Language refer to this factor as GC, on the ACCGRAV card.
The only case in which you should set UNITS_CONSISTENCY_FACTOR yourself is when you
are using a set of units Adams View does not support. Otherwise, you should probably let Adams
View compute it for you. If you do use this command to set UNITS_CONSISTENCY_FACTOR
to a non-zero value, Adams View will write your value to an Adams data set. Adams View will not
change your value, even if you later change your force, mass, length, or time units. If you explicitly
set UNITS_CONSISTENCY_FACTOR, and then later change your units, remember to
updateUNITS_CONSISTENCY_FACTOR.
Tips:
 If you do not specify UNITS_CONSISTENCY_FACTOR, or specify it as zero, Adams View will
calculate it for you when it writes the Adams data set.
force 9
force create direct force_vector

Allows you to create a vector force.
The FORCE_VECTOR is a translational vector force that is specified using three orthogonal components.
The resultant vector determines the direction of the force action. This resultant vector is formed by the three
component forces that the user defines along the "reference marker" axes. The reaction is equal and opposite
to the action. The user may define the FORCE_VECTOR components in Adams View through user-
specified function expressions or by specifying up to 30 user-defined parameters that are passed to a user-
written subroutine (a "VFOSUB") linked to Adams.
The FORCE_VECTOR corresponds to the Adams VFORCE statement.
The FORCE_VECTOR creates an Adams translational vector force element that applies the forces between
two parts of the system. The element applies an action force to the part that contains the I marker and a
corresponding reaction force to the part to which the "floating" J marker belongs. This "floating marker" is
automatically created by Adams View and is positioned to be coincident with the I marker. Subsequently,
the FORCE_VECTOR establishes the position of the "floating" J marker. As the system moves, Adams
moves the "floating" J marker on its part to keep the "floating" J and I markers superimposed. Thus, Adams
applies the reaction force to the "floating" J markers part at the instantaneous position of the I marker.
The total vector force that Adams supplies is the vector sum of the individual force components that the user
specifies. The magnitude of the total vector force is the square root of the sum of the components squared.
Its value will be the resultant (i.e. the square root of the sum of the squares) of the three mutually-orthogonal
force components.
Format:
force_vector_name = new V force name
Adams_id = geom._id
comments= String
i_marker_name = Existing Marker name
j_floating_marker_name = Existing J floating marker name
j_part_name = Existing body
j_marker_id = integer
error = real number
x_force_function = Function
y_force_function = Function
z_force_function = Function
xyz_force_function = Function

user_function = Real
routin e= String
Description:

force_vector_name New V Force Specifies the name of the new force_vector. You may
use this name later to refer to this force_vector.
Adams_id Geom_id Specifies an integer used to identify this element in
modified.
i_marker_name Existing marker Specifies the marker at which Adams applies the
forces and/or torques.
j_floating_marker_name Existing marker Specify the J floating marker name.
j_part_name Existing body Specifies the part on which Adams View creates a
floating marker.
j_marker_id Integer Specifies the Adams ID for the floating marker which
is automatically created on the J part by Adams View.
request or function by the ID you specify, instead of
ref_marker_name Existing marker Specifies a marker that acts as a coordinate reference
for the definition of three orthogonal force and/or
torque components. These components make up the
force and/or torque being defined. The user must
ensure that the reference_marker is fixed on a part
(i.e. not a "floating" marker). The reference_marker
may be the same as the I marker and may be on any
part of the model.
Error Real
x_force_function Function Specifies the x component of the translational force
for this element. Adams applies this force parallel to
the x axis of the reference marker specified in the
REF_MARKER_NAME parameter.
y_force_function Function Specifies the y component of the translational force
the y axis of the reference marker specified in the
force 11

z_force_function Function Specifies the z component of the translational force
the z axis of the reference marker specified in the
xyz_force_function Function
written subroutine. See the Adams User's Manual for
information on writing user-written subroutines.
routine String
1. Adams View will not allow you to have two force_vectors with the same name, so you must provide
a unique name.
with an alphabetic or '_' character. They may of be any length.
be assigned to it.
4. The user must ensure that the I marker is a fixed marker and on a different part than the part specified
in the J_PART_NAME parameter. Because the I marker is a fixed marker, and the "floating" marker
will move around on the j_part to remain coincident with the I marker, Adams always applies the
force action at a fixed point on the part containing the I marker. The reaction force is applied to the
j_part at a point coincident with the I marker.
The "floating" marker is automatically created by Adams View on the part specified in the
J_PART_NAME parameter.
5. Adams subsequently applies the reaction forces and/or torques to this "floating" J marker. The user
must ensure that the j_part is a different part than the part containing the I marker. Adams will move
the "floating" J marker around on the j_part to keep it superimposed on the I marker, meaning the
point of application of the reaction force may move around on the j_part. Reaction forces are not
calculated when the "floating" J marker is on the ground part.
name at that time.
force 13
verification.
Components Examples
NUMBERS
OPERATORS
 From greatest to the least, the operators have the following priorities. ** then * / then + -. In other
words, Adams executes exponentiation (**) before all other operators and executes multiplication (*)
and division (/) before addition (+) and subtraction (-).
 When a statement has operators of the same priority, Adams executes them from left to right.
 You can use parentheses to alter the precedence of operators. For example, in the equation,
SYSTEM CONSTANTS
BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
SYSTEM VARIABLES
ARITHMETIC IFS
force 15
follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
be accessed.
Names Purposes
a cubic curve (a spline) to the data.
force create direct general_force

Allows you to create a general force. A GENERAL_FORCE defines a complete force element, consisting of
three mutually orthogonal translational force components and three orthogonal torque components.
Format:
general_force_name = .model_1.GFORCE_1
Adams_id = 1
i_marker_name = .model_1.part_1.marker_1
j_floating_marker_name = .model_1.part_2.marker_2
ref_marker_name = .model_1.part11.marker_1
Description:

general_force_name String Specifies the name of the new general_force. You may use this
name later to refer to this general_force.
Adams_id Integer Specifies an integer used to identify this element in the Adams
data file.
i_marker_name String Specifies the marker at which Adams applies the forces and/or
torques.
j_floating_marker_name String
j_part_name String Specifies the part on which Adams View creates a floating
marker. Adams subsequently applies the reaction forces and/or
torques to this "floating" J marker.
j_marker_id Integer Specifies the Adams ID for the floating marker which is
automatically created on the J part by Adams View.
ref_marker_name String Specifies a marker that acts as a coordinate reference for the
definition of three orthogonal force and/or torque
components.
x_force_function String Specifies the x component of the translational force for this
element. Adams applies this force parallel to the x axis of the
reference marker specified in the REF_MARKER_NAME
parameter.
force 17

y_force_function String Specifies the y component of the translational force for this
element. Adams applies this force parallel to the y axis of the
parameter.
z_force_function String Specifies the z component of the translational force for this
element. Adams applies this force parallel to the z axis of the
parameter.
To enter a function expression, you enter a series of quoted

strings.
x_torque_function String Specifies the x component of the rotational torque for this
element.
y_torque_function String Specifies the y component of the rotational torque for the
element.
z_torque_function String Specifies the z component of the rotational torque for this
element.
user_function String Specifies up to 30 values for Adams to pass to a userwritten
subroutine. See the Adams User's Manual for information on
writing user-written subroutines.
Routine String
1. A GENERAL_FORCE defines a complete force element, consisting of three mutually orthogonal
translational force components and three orthogonal torque components. The two resultant vectors
formed by the three component forces and the three component torques determine the direction of
the force and torque actions, respectively. The user defines these force and torque components along
and about the "reference" marker axes. The reactions are equal and opposite to the action. The user
may define the GENERAL_FORCE in Adams View through user-specified function expressions or
by specifying up to 30 user-defined parameters that are passed to a user-written subroutine (a
"GFOSUB") the user links with Adams.
2. The GENERAL_FORCE corresponds to the Adams GFORCE statement.
3. A GENERAL_FORCE creates a six component force element that applies the forces between two
parts of the system. Here, force means three orthogonal translational components and three
orthogonal rotational components. The element applies actions to the part to which the I marker
belongs and corresponding reactions to the part to which a "floating_marker" belongs. This "floating
marker" is automatically created by Adams View and is positioned to be coincident with the I marker.
Subsequently, the GENERAL_FORCE internally establishes the position of the "floating_marker".
As the system moves, Adams moves the "floating_marker"on its part to keep the "floating_marker"
and I markers always superimposed. Thus, Adams applies the reaction force to the part containing
the "floating_marker" marker at the instantaneous position of the I marker.
4. The magnitude of the force depends on expressions or subroutines that the user supplies. The value
of the force is the resultant (i.e. the square root of the sum of the squares) of (up to) three mutually
orthogonal force components together with the resultant (i.e. the square root of the sum of the
squares) of (up to) three mutually orthogonal torque components.
5. The resultant vector formed by the three user-defined component forces along the reference marker
axes defines the direction of the translational force action. The reaction is equal and opposite to the
action. The resultant vector formed by the three component torques determines the direction of the
rotational torque action. The user defines these torques about the reference marker axes. The reaction
is equal and opposite to the action.
6. The general_force_name parameter specifies the name of the new general_force. You may use this
name later to refer to this general_force. Adams View will not allow you to have two general_forces
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 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. 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 theentity 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:
be assigned to it.
7. Specifies an integer used to identify this element in the Adams data file. When you use the FILE
Adams_DATA_SET WRITE command, Adams View writes an Adams data file for your model.
Adams requires that each modeling element be identified by a unique integer identifier. If you use
this parameter to specify a non-zero identifier, Adams View will use it in the corresponding
internally generated identifier. Adams View will permanently store this identifier with the element
just as if you had entered it yourself. Normally, you would let all identifiers default to zero, and
Adams View would generate the identifiers for you. You are never required to enter a non-zero
stored with the object. Comments in the data file can be associated with the model. These comments
force 19
j_part at a point coincident with the I marker. The "floating" marker is automatically created by
Adams View on the part specified in the J_PART_NAME parameter.
11. Specifies the Adams ID for the floating marker which is automatically created on the J part by Adams
View. This allows you to reference the floating marker in a request or function by the ID you specify,
instead of letting Adams View generate one.
12. The x-force function specifies the x component of the translational force for this element. Adams
applies this force parallel to the x axis of the reference marker specified in the
REF_MARKER_NAME parameter. To enter a function expression, you enter a series of quoted
strings. The easiest way to enter a function expression in Adams View is to use the text editor in
combination with the function builder. To invoke the text editor for entering a function expression,
highlight the function field and then either pick the "EDIT" button at the top of the panel or type a
^t (control-t). The Adams View "function builder" is discussed below. The syntactical correctness of
a function expression can be investigated by using the "VERIFY" button at the upper right of the text
editor. If there is a syntax error, a message is printed and the cursor is put near the problem. Proper
unit consistency is not checked during function expression verification.
13. The y-force function specifies the y component of the translational force for this element. Adams
applies this force parallel to the y axis of the reference marker specified in the
REF_MARKER_NAME parameter. To enter a function expression, you enter a series of quoted
14. The z-force function specifies the z component of the translational force for this element. Adams
applies this force parallel to the z axis of the reference marker specified in the
REF_MARKER_NAME parameter. To enter a function expression you enter a series of quoted
force create direct multi_point_force
15. The user_function parameter specifies up to 30 values for Adams to pass to a user-written
subroutine. See the Adams User's Manual for information on writing user-written subroutines.

Allows you to create a multiple point force. A MULTI_POINT_FORCE creates a multi-point force element
which establishes linear force-displacement (stiffness) and/or force-velocity (damping) relationships between
(up to) 351 markers in the model. This force corresponds to the Adams NFORCE statement.
Format:
multi_point_force_name = model_name.force_name
Adams_id = integer
i_marker_name = model_name_.part_name.marker_name
j_marker_name = model_ name.part_name.marker_name
stiffness_matrix_name = model_name.stiffness_matrix_name
damping_matrix_name = model_name.damping_matrix_name
damping_ratio = real_number
length_matrix_name = model_name.length_matrix_name
force_matrix_name = model_name.force_matrix_name
Example:
force create direct multi_point_force &
multi_point_force_name = FORCE_11 &
Adams_id = 1 &
i_marker_name = model1_i_marker_1 &
j_marker_name = model1.part1.marker_2 &
stiffness_matrix_name = model1_name.stf_1 &
damping_matrix_name = model1_name.dp_1 &
damping_ratio = 0.5 &
length_matrix_name = model_1.lm_1 &
force_matrix_name = model_name.fm_1
force 21
Description:

Multi_point_force_name String Specifies the name of the new multi_point_force. You may use
this name later to refer to this multi_point_force. Adams View
will not allow you to have two multi_point_forces with the
same name, so you must provide a unique name.
Adams_id Integer Specifies an integer used to identify this element in the Adams
data file.
i_marker_name String Specifies a marker on the first of two parts connected by this
force element.
j_marker_name Specifies a marker on the second of two parts connected by this
force element.
Stiffness_matrix_name String Specifies the name of the matrix that the multi_point_force
uses as its stiffness matrix.
Damping_matrix_name String Specifies the name of the matrix that the multi_point_force
uses as its damping matrix.
Damping_ratio Real Specifies the proportional damping ratio for the
MULTI_POINT_FORCE.
Length_matrix_name String Specifies the name of the matrix that defines a reference
location for each of the I markers with respect to the J marker,
measured in the coordinate system of the J marker.
Force_matrix_name String Specifies the name of the matrix that contains the forces and
torques that the multi_point_force would produce if all the I
markers were at the positions given in the length_matrix.
1. The MULTI_POINT_FORCE supplies a three-component force and a three component torque at
each of the markers that define it. The force is a linear function of the relative displacement and of
the relative velocity of the markers.These linear relationships are defined by using a stiffness and/or
damping matrix, or by using a stiffness matrix and a proportional (viscous) damping factor. Most
typically, the MULTI_POINT_FORCE relationships will be defined as finite element stiffness and
damping relationships. For each MULTI_POINT_FORCE, one of the markers (the J marker) must
be specified as the datum or reference location (and orientation) for the forces defining the
MULTI_POINT_FORCE. The stiffness matrix used by Adams is the equilibrated stiffness matrix
and corresponds to the finite element stiffness matrix with the rows and columns corresponding to
the J marker freedoms eliminated.
2. Formulation The MULTI_POINT_FORCE creates a set of forces and torques, which act between
the I and J markers, which appear in the MULTI_POINT_FORCE. These forces and torques are
linear functions of the relative displacements and velocities of the markers, in a manner equivalent to
the finite element method. For each MULTI_POINT_FORCE, one marker (J) is used as the
reference marker. The velocities are resolved into the J markers reference frame and expressed in the
J markers coordinate system. The force and torque components computed by the
MULTI_POINT_FORCE are also given in the J markers coordinate system. The force-displacement
and force-velocity relationships are specified using stiffness and damping matrices, or by using a
stiffness matrix and a proportional damping ratio. These matrices are defined using MATRIX
statements in the data set. The stiffness and damping matrices that Adams requires are defined for the
I markers only, i.e. they should be derived normally using the (6n+1) J marker and I marker degrees-
of-freedom, but are input using only the rows and columns corresponding to the I marker degrees-
of-freedom. This is equivalent, in finite element terminology, to applying fixed boundary conditions
at the J marker by simply removing the corresponding rows and columns from the matrices. Adams
will automatically compute and apply the correct reaction forces at the J marker based on the I
markers responses.
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:
be assigned to it.
a unique, internally generated identifier. Adams View will permanently store this identifier with the
Values are: AN INTEGER GREATER THAN OR EQUAL TO 0 LESS THAN OR EQUAL TO
99999999
force 23
6. The i_marker_name specifies a marker on the first of two parts connected by this force element.
Adams View connects this element to one part at the I marker and to the other at the J marker.
7. The j_marker_name specifies a marker on the second of two parts connected by this force element.
Adams View connects this element to one part at the I marker and to the other at the J marker.
8. This stiffness matrix is a 6n x 6n matrix (n is the number of I markers) that defines the linear
relationships between the I marker displacements relative to the J marker and elastic forces generated
by the multi_point_force. The stiffness matrix is derived in the J markers coordinate system. Marker
translational and rotational displacements appear sequentially in DX-DY-DZ-AX-AY-AZ order,
while the markers appear in the same sequence as in the i_marker_name parameter. You may identify
a matrix by typing its name or by picking it from the screen. Since a matrix does not have a geometric
position, Adams View displays matrix icons at or near the model origin. If the matrix icon is not
if the matrix icon is displayed. If you created the matrix by reading an Adams data set or graphics file,
the matrix name is the letters MAT followed by the Adams data set matrix ID number. For example,
the name of Adams MATRIX/101 is MAT101. If you created the matrix during preprocessing, you
will have given it a name at that time. If a matrix is owned by the default model, you may identify it
by entering only its name. If it is not, you must enter its full name. To identify a matrix under a
specify matrix 'control_points' from model 'road_surface' by entering
".road_surface.control_points'". If you type a "?", Adams View will list the matrix available by default.
You must separate multiple matrix names by commas. If the matrix is visible in one of your views,
you may identify it by picking on any of the graphics associated with it. You need not separate
multiple matrix picks by commas.
9. The damping matrix is a 6n x 6n matrix (n is the number of I markers) that defines the linear
relationships between the I marker velocities relative to the J marker and the viscous forces generated
by the multi_point_force. The damping matrix is derived in the J markers coordinate system. If
neither damping matrix nor the damping ratio is given, the multi_point_force will be undamped.
Marker translational and rotational velocities appear sequentially in VX-VY-VZ-WX-WY-WZ order,
while the markers appear in the same sequence as in the i_marker_name parameter. You may identify
a matrix by typing its name or by picking it from the screen. Since a matrix does not have a geometric
position, Adams View displays matrix icons at or near the model origin. If the matrix icon is not
if the matrix icon is displayed. If you created the matrix by reading an Adams data set or graphics file,
the matrix name is the letters MAT followed by the Adams data set matrix ID number. For example,
the name of Adams MATRIX/101 is MAT101. If you created the matrix during preprocessing, you
will have given it a name at that time. If a matrix is owned by the default model, you may identify it
by entering only its name. If it is not, you must enter its full name. To identify a matrix under a
specify matrix 'control_points' from model 'road_surface' by entering

you may identify it by picking on any of the graphics associated with it. You need not separate
multiple matrix picks by commas.
10. The elements of the damping matrix are determined by multiplying the corresponding stiffness
matrix element value by this number. If direct input of the damping properties is desired, the
DAMPING_MATRIX_NAME parameter may be used. If neither DAMPING_MATRIX_NAME
nor DAMPING_RATIO is given, the MULTI_POINT_FORCE will be undamped. The user must
specify a STIFFNESS_MATRIX_NAME with the DAMPING_RATIO parameter.
11. The length matrix is a 3n x 1 matrix (n is the number of I markers) of translational displacements
only, in DX-DY-DZ order. Usually, the length matrix will be used to specify the system's free (no
internal force) lengths when they differ from the input positions. If the length matrix is not given, the
multi_point_force assumes that the input positions of the I markers are at the reference locations. You
may identify a matrix by typing its name or by picking it from the screen. Since a matrix does not
have a geometric position, Adams View displays matrix icons at or near the model origin. If the matrix
icon is not visible on the screen, you must type the name. You may also find it convenient to type the
name even if the matrix icon is displayed. If you created the matrix by reading an Adams data set or
graphics file, the matrix name is the letters MAT followed by the Adams data set matrix ID number.
For example, the name of Adams MATRIX/101 is MAT101. If you created the matrix during
preprocessing, you will have given it a name at that time. If a matrix is owned by the default model,
you may identify it by entering only its name. If it is not, you must enter its full name. To identify a
matrix under a different model, for instance, you may need to enter the model name as well. For
example, you may specify matrix 'control_points' from model 'road_surface' by entering
you may identify it by picking on any of the graphics associated with it.
12. The force_matrix is a 6n x 1 matrix (n is the number of I markers) of forces and torques, appearing
sequentially for each marker in FXFY- FZ-TX-TY-TZ order, while the markers appear in the same
sequence as in the I_MARKER_NAME parameter. The force and torque components are expressed
in the coordinate system of the J marker. When the LENGTH_MATRIX_NAME will be used to
specify the system's free lengths, the FORCE_MATRIX_NAME gives the matrix of external
preloads. If the FORCE_MATRIX_NAME is not given, the multi_point_force acts as though a
matrix of zeros were input. You may identify a matrix by typing its name or by picking it from the
screen. Since a matrix does not have a geometric position, Adams View displays matrix icons at or
near the model origin. If the matrix icon is not visible on the screen, you must type the name. You
may also find it convenient to type the name even if the matrix icon is displayed. If you created the
matrix by reading an Adams data set or graphics file, the matrix name is the letters MAT followed by
the Adams data set matrix ID number. For example, the name of Adams MATRIX/101 is MAT101.
If you created the matrix during preprocessing, you will have given it a name at that time. If a matrix
is owned by the default model, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a matrix under a different model, for instance, you may need to enter
force 25
force create direct single_component_force
the model name as well. For example, you may specify matrix 'control_points' from model
'road_surface' by entering ".road_surface.control_points'". If you type a "?", Adams View will list the
matrix available by default. You must separate multiple matrix names by commas. If the matrix is
Tips:
 You need not separate multiple matrix picks by commas.

Allows you to create a single component force object.
A single-component force applies force or a torque to two parts. You specify a marker on each part for force
or torque application. You may define the magnitude of the force as a function of any combination of
displacements, velocities, other applied forces, user-defined variables, and time. The force applied can be
action-reaction forces or action-only forces.
For translational action-reaction forces, Adams applies the user-defined force along the line connecting the I
and the J markers. The force exerted on I is directed from J towards I, while the force exerted on J is directed
from I towards J.
For translational action-only forces, Adams applies the force on the I marker only. There is no reaction on
the J marker. The force on the I marker is directed along the z axis of the J marker.
For rotational action-reaction forces, Adams applies the torque on the I marker about the z axes of the J
marker. Furthermore, Adams assumes that the z axes of the I and the J markers are constrained to always be
parallel for this type of single-component force.
For rotational action-only forces, Adams applies the torque only on the I marker. There is no reaction on the
J marker. The torque on the I marker is directed along the z axis of the J marker.
You write a FUNCTION expression or a user-written subroutine (an SFOSUB) to define the constitutive
equation for the force applied at the I marker. Adams evaluates the reaction forces at the J marker.
Format:
single_component_force_name= new single component force
Adams_id= geom_id
comments= string
type_of_freedom= translational/rotational
action_only= on/off
function= function
user_function= Real
routine= string

error= real
i_part_name= an existing body
j_part_name= an existing body
location= location
orientation= orientation
along_axis_orientation= location
in_plane_orientation= location
relative_to= existing model or part or
marker
i_marker_name= existing marker
j_marker_name= existing marker
Example:
force create direct single_component_force &
single_component_force_name = MY_FORCE &
function = "PI+10" &
j_part_name = PART_2 &
Description:

single_component_force_ New single_component Specifies the name of the new
name force single_component_force. You may use this name
later to refer to this single_component_force.
Adams_id Geom_id Specifies an integer used to identify this element
or modified.
type_of_freedom Rotational/Translational Specifies the type of force (rotation or translation)
to be applied.ROTATIONAL designates a
rotational force, i.e. a
torque.TRANSLATIONAL designates a
translational force.
force 27

action_only On/Off Specifies whether the force is action-only or
action-reaction. For an action-reaction force,
Adams applies a force between the I and J
markers. For an action-only force, Adams applies
a force on the I marker directed by the Z axis of
the J marker, but does not apply a reaction force
at the J marker.
function Function Specifies the function expression definition that is
used to compute the value of this variable. To
enter a function expression, you enter a series of
quoted strings.
user-written subroutine. See the Adams User's
subroutines.
routine String
Error Real
i_part_name Existing body Specifies the part, that is the first of the two parts
that this force acts between. Adams View applies
the force on one part at the I marker and the other
at the J marker. These markers are automatically
generated using this method of force creation.
j_part_name Existing body Specifies the part, that is the second of the two
parts that this force acts between. Adams View
applies the force on one part at the J marker and
the other at the I marker. These markers are
automatically generated using this method of
force creation.
position of a force during its creation.
force being created using three rotation angles.
The I marker is oriented based on the J marker
orientation and the requirements of the particular
force being created. These markers are created
automatically.
about the axis.

relative_to AN EXISTING Specifies the coordinate system that location
MODEL, PART OR coordinates and orientation angles correspond to.
MARKER
i_marker_name Existing marker Specifies a marker on the first of the two parts
connected by this force element. Adams View
connects this element to one part at the I marker
and to the other at the J marker.
verification.
Components Examples
force 29
NUMBERS
OPERATORS
SYSTEM CONSTANTS
BLANKS
 You cannot put a blank space in the middle of a number.
 Adams does not accept a blank space between a function and its left bracket. (This is true for both,
FORTRAN-77 functions and Adams functions.)
CONTINUATION COMMAS
comma and the continuation comma. You may use more than one continuation comma to extend an
expression over several lines.
FUNCTION BUILDER
SYSTEM VARIABLES
ARITHMETIC IFS
follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
MAX, SIN, SQRT, and TAN in your expression. For more information about these functions, see a
FORTRAN reference manual. Invoke the text edit window and pick the FUNCTIONS button to
Adams FUNCTIONS
force 31
be accessed.
Names Purposes
CUBSPL Accesses the data in a SPLINE statement and uses the traditional cubic method
to fit a cubic curve (a spline) to the data.
2. Adams View will not allow you to have two single_component_forces with the same name, so you
must provide a unique name.
be assigned to it.
system.
force 33
force create direct torque_vector
system.
8. If the “RELATIVE_TO” parameter is not specified, the default coordinate system is used. The
default coordinate system is initially your model, i.e. the global coordinate system. You may change
the default coordinate system using the 'defaults coordinate_system' command.

Allows you to create a vector torque.
The TORQUE_VECTOR is a rotational force (that is, a torque) that consists of three orthogonal
components. The direction of the torque action is determined by the resultant vector formed by the three
component torques defined by the user along the "reference marker" axes. The reaction is equal and opposite
to the action. The user may define the TORQUE_VECTOR components in Adams View through user-
specified function expressions, or by specifying up to 30 user-defined parameters that are passed to a user-
written subroutine (a "VTOSUB") the user links with Adams.
The TORQUE_VECTOR corresponds to the Adams VTORQUE statement.
The TORQUE_VECTOR creates an Adams rotational force element (that is, torque) that applies the forces
between two parts of the system. The element applies an action to the part to which the I marker belongs and
a corresponding reaction to the part to which the "floating" J marker belongs. This "floating marker" is
automatically created by Adams View and is positioned to be coincident with the I marker. Subsequently,
the TORQUE_VECTOR establishes the position of the "floating" J marker. As the system moves, Adams
moves the "floating" J marker on its part to keep the "floating" J and I markers superimposed. Thus, Adams
applies the reaction torque to the "floating" J markers part.
The components of the torque depends on expressions or subroutines that the user supplies. Its value will be
the resultant (i.e. the square root of the sum of the squares) of the three mutually orthogonal torque
components.
Format:
torque_vector_name= New torque name
Adams_id= geom._id
comments= String
i_marker_name= existing marker name
j_floating_marker_name= existing marker name
j_part_name= existing body

j_marker_id= integer
ref_marker_name= existing marker
error= real number
x_torque_function= Function
y_torque_function= Function
z_torque_function= Function
xyz_torque_function= Function
user_function= Real
routine= String
Description:

torque_vector_name String Specifies the name of the new torque_vector
Adams_id Geom_id Specifies an integer used to identify this element in
modified.
i_marker_name Existing marker name Specifies the marker at which Adams applies the
j_floating_marker_name Existing marker name Specifies marker for j floating marker.
j_part_name An existing body Specifies the part on which Adams View creates a
floating marker.
j_marker_id Integer Specifies the Adams ID for the floating marker
which is automatically created on the J part by
Adams View. This allows you to reference the
floating marker in a request or function by the ID
you specify, instead of letting Adams View
generate one.
ref_marker_name Existing marker Specifies a marker that acts as a coordinate
reference for the definition of three orthogonal
force and/or torque components. These
components make up the force and/or torque
being defined.
error Real
force 35

x_torque_function Function Specifies the x component of the rotational torque
for this element. Adams applies this torque
parallel to the x axis of the reference marker in the
sense of the right-hand rule, that is, a positive
torque causes a counterclockwise rotation if you
are looking along the axis from positive to
negative.
y_torque_function Function Specifies the y component of the rotational torque
for the element.
Adams applies this torque parallel to the y axis of

the reference marker in the sense of the right-hand
rule, that is, a positive torque causes a
counterclockwise rotation if you are looking along
the axis from positive to negative.
z_torque_function Function Specifies the z component of the rotational torque
for the element.
Adams applies this torque parallel to the z axis of

the reference marker in the sense of the right-hand
rule, that is, a positive torque causes a
counterclockwise rotation if you are looking along
the axis from positive to negative.
xyz_torque_function Function
subroutines.
routine String
1. You may use this name later to refer to this torque_vector. Adams View will not allow you to have
two torque_vector with the same name, so you must provide a unique name.
be assigned to it.
stored with the object. Comments in the data file can be associated with the model. These comments
the "floating" J marker around on the j_part to keep it superimposed on the I marker, meaning, the
6. The user must ensure that the reference_marker is fixed on a part (i.e. not a "floating" marker). The
reference_marker may be the same as the I marker and may be on any part in the model.
force 37
name at that time.
verification.
Components Examples
NUMBERS
OPERATORS
words, Adams executes exponentiation (**) before all other operators and executes multiplication
(*) and division (/) before addition (+) and subtraction (-).
SYSTEM CONSTANTS
 PI Value of pi (to eighteen significant digits)
 DTOR Value of pi/180 for converting degrees to radians
 RTOD Value of 180/pi for converting radians to degrees
BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
force 39
SYSTEM VARIABLES
ARITHMETIC IFS
follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
be accessed.
force create element_like beam
Names Purposes

Allows you to create a beam object.
Example:
force create element_like beam &
beam_name = BEAM_1 &
adams_id = 2 &
Comments = “” &
Ixx = 2.11 &
Iyy = 1.8 &
Izz = 1.9 &
Length = 10
force 41
Description:

beam_name String Specifies the name of the new beam. You may use this name
later to refer to this beam. View will not allow you to have two
beams with the same name, so you must provide a unique
name.
data file.
Ixx Real number Specifies the polar area moment of inertia about the X axis of
greater than 0 a cross section perpendicular to the length of the beam.
Iyy Real number Specifies the principal area moment of inertia about the Y axis
greater than 0 of a cross section perpendicular to the length of the beam.
Izz Real number Specifies the principal area moment of inertia about the z axis
greater than 0 of a cross section perpendicular to the length of the beam.
y_shear_area_ratio Real number Specifies the shear area ratio in the y direction. This is the
greater than 0 correction factor for shear deflection in the y direction for
Timeshenko beams.
z_shear_area_ratio Real number Specifies the shear area ratio in the y direction. This is the
greater than 0 correction factor for shear deflection in the z direction for
Timeshenko beams.
Youngs_modulus Real number Specifies Young's modulus of elasticity for the beam material.
greater than 0
Shear_modulus Real number Specifies the shear modulus of elasticity for the beam material.
greater than 0
length Real number Specifies the undeformed length of the beam along the x axis
greater than 0 of the J marker.
area_of_cross_section Real number Specifies the uniform area of the beam cross section.
greater than 0
Damping ratio Real number Specifies a ratio for calculating the structural damping matrix
greater than 0 for the beam. Adams multiplies the stiffness matrix by the
value of DAMPING_RATIO to obtain the damping matrix.
matrix_of_damping_ Specifies a six-by-six structural damping matrix for the beam.
terms
location Specifies the locations to be used to define the position of a
force during its creation.
Orientation Specifies the orientation of the J marker for the force being
created using three rotation angles.

Along_axis_orientati Specifies the orientation of a coordinate system (e.g. marker or
on part) by directing one of the axes. Adams View will assign an
arbitrary rotation about the axis.
in_plane_orientation Specifies the orientation of a coordinate system (e.g. marker or
part) by directing one of the axes and locating one of the
coordinate planes.
i_part_name Specifies the part that is the first of the two parts that this force
acts between.
(Required)
j_part_name Specifies the part that is the second of the two parts that this
force acts between. Adams View applies the force on one part
(Required) at the J marker and the other at the I marker. These markers
are automatically generated using this method of force
creation.
i_marker_name Specifies a marker on the first of two parts connected by this
force element. Adams View connects this element to one part
(Required) at the I marker and to the other at the J marker.
j_marker_name Specifies a marker on the second of two parts connected by this
force element. Adams View connects this element to one part
at the I marker and to the other at the J marker.
Specifies the theory to be used to define the force this element
will apply. By default the LINEAR theory is used. If the
NONLINEAR option is used, the full non linear Euler-
Bernoulli theory is used. If the STRING option is used, a
simplified non linear theory is used. The simplified non linear
theory may speed up your simulations with little performance
penalties.
1. The beam, which is massless and has a uniform cross section, is modeled as a linear translational and
a linear rotational action-reaction force between two markers. The forces the beam produces are
linearly dependent on the relative displacements and the relative velocities of the markers at its
endpoints. The x-axis of the J marker defines the centroidal axis of the beam. The y-axis and the z-
axis of the J marker are the principal axes of the cross section. They are perpendicular to the x-axis
and to each other. When the beam is in an undeflected position, the I marker has the same angular
orientation as the J marker, and the I marker lies on the x-axis of the J marker. The following
constitutive equations define how Adams uses the data you input for a beam to apply a force and a
torque to the I marker depending on the displacement and velocity of the I marker relative to the J
marker. Adams applies a force of equal magnitude and opposite direction to the J marker.
[Fx] [K11 0 0 0 0 0 ] [x]
[Fy] [0 K22 0 0 0 K26] [y]
force 43
[Fz] = - [0 0 K33 0 K35 0 ] [z]

[Tx] [0 0 0 K44 0 0 ] [a]
[Ty] [0 0 K35 0 K55 0 ] [b]
[Tz] [0 K26 0 0 0 K66] [c]
[C11 C21 C31 C41 C51 C61] [Vx]
[C21 C22 C32 C42 C52 C62] [Vy]
-[C31 C32 C33 C43 C53 C63] [Vz]
[C41 C42 C43 C44 C54 C64] [Wx]
[C51 C52 C53 C54 C55 C65] [Wy]
[C61 C62 C63 C64 C65 C66] [Wz]
Note that both matrices, Cij and Kij, are symmetric, i.e. Cij=Cji and Kij=Kji. You define the twenty-
one unique damping coefficients when you write the BEAM statement. Adams defines the Kij's in
the following way:
K11 = E A / L
K22 = 12 E Izz /[L**3 (1+Py)]
K26 = -6 E Izz /[L**2 (1+Py)]
K33 = 12 E Iyy /[L**3 (1+Pz)]
K35 = 6 E Iyy /[L**2 (1+Pz)]
K44 = G Ixx / L
K55 = (4+Pz) E Iyy /[L (1+Pz)]
K66 = (4+Py) E Izz /[L (1+Py)]
where Py = 12 E Izz ASY/(G A L**2) and Pz = 12 E Iyy ASZ/(G A
L**2)
2. The BEAM statement implements a force in the same way the FIELD statement does, but the BEAM
statement requires you to input only the values of the beam's physical properties, which Adams uses
to calculate the matrix entries. For a force request, the forces returned are the forces the J marker exerts
upon the I marker.
3. The constitutive equations shown above define the forces and moments exerted on the I marker.
These forces and moments are due to relative displacements and velocities of the I marker with respect
to the J marker. Because of force transfer, the reaction moments at the J marker are usually not the
same as the applied moments at the I marker.
be assigned to it.
6. By definition, the beam lies along the positive X axis of the J marker. You should compute IXX about
the X axis of the J marker. Values for the Ixx parameter are:A REAL NUMBER GREATER THAN 0
7. By definition, the beam lies along the positive X axis of the J marker. You should compute IYY about
the Y axis of the J marker.
8. By definition, the beam lies along the positive X axis of the J marker. You should compute IZZ about
the Z axis of the J marker.
9. The y_shear_ratio is the area of the beam cross section divided by the area of the beam cross section
that resists y-direction shear forces. If you want to neglect the deflection due to y-direction shear, set
the ratio to zero.
10. The z_shear_ratio specifies the shear area ratio in the z direction. This is the correction factor for
shear deflection in the z direction for Timeshenko beams.
11. Because the ‘matrix_of_damping _terms’ matrix is symmetric, you need to specify only one-half of
it. The following matrix shows the values to input:
[r01 ] [r02 r07 ] [r03 r08 r12 ]
[r04 r09 r13 r16 ] [r05 r10 r14 r17 r19 ] [r06 r11 r15
r18 r20 r21]
Enter the elements by columns from top to bottom, then from left to right. If you do not use either
CMATRIX or CRATIO, CMATRIX defaults to a matrix with thirty-six zero entries; i.e. r1 through
r21, each default to zero.
12. The I and J markers will be automatically created at the location specified by the ‘location’ parameter
on the I_PART_NAME and J_PART_NAME respectively. By default, you supply Cartesian (x, y, z)
coordinates. You may use the 'defaults units coordinate_system_type =' command to change this
convention. For example, selecting 'cylindrical' means you will subsequently be supplying r, theta,
and z coordinates. Adams View applies your location coordinates in the coordinate system you
identify with the RELATIVE_TO parameter. The default for the RELATIVE_TO parameter is the
default coordinate system. (See the RELATIVE_TO parameter for this command).
force being created. These markers are created automatically.
force 45
force create element_like bushing
system.
same way as the vector from the first location to the second. Note that this does not completely dictate
the orientation of the coordinate system. Adams View will position the coordinate system with an
arbitrary rotation about the axis. If you must completely control the coordinate system orientation,
use ORIENTATION or IN_PLANE_ORIENTATION. By default, you direct the z-axis of the
coordinate system. You may change this convention with the 'DEFAULTS
ORIENT_AXIS_AND_PLANE AXIS_AND_PLANE_SETTING=' command. For example,
selecting either X_AXIS_XY_PLANE or X_AXIS_XZ_PLANE means you will subsequently be
directing the x-axis. The plane-convention setting does not affect this parameter. Adams View applies
your location coordinates in the coordinate system you identify with the RELATIVE_TO parameter.
The default for the RELATIVE_TO parameter is the default coordinate system.
15. You may enter either two or three locations for the in_plane_orientation parameter. If you enter two
specify three locations, the axis will be parallel to, and pointing the same way as the vector from the
By default, you direct the z-axis of the coordinate system and locate the ZX plane. You may use the
be directing the x-axis and locating the XY plane. Adams View applies your location coordinates in
Cautions:
 The centroidal axis must be orthogonal to the cross section specified by the area_of_cross_section
parameter.

Allows you to create a bushing object.
Description:

bushing_name String Specifies the name of the new bushing. You may use this
name later to refer to this bushing. Adams View will not
allow you to have two bushings with the same name, so you
Adams_id Integer Specifies an integer used to identify this element in the
Adams data file.
modified.
damping Real number Specifies three viscous damping coefficients for the bushing
greater than or force.
equal to 0
stiffness Real number Specifies three stiffness coefficients for the bushing force.
greater than 0
force_preload Real number Specifies a vector of three constant terms for the bushing
force.
tdamping Real number Specifies three viscous damping coefficients for the bushing
greater than or torque.
equal to 0
shear_modulus Real number Specifies the shear modulus of elasticity for the beam
greater than 0 material.
length Real number Specifies the undeformed length of the beam along the x-
greater than 0 axis of the J marker.
location Specifies the locations to be used to define the position of a
force during its creation.
Orientation Specifies the orientation of the J marker for the force being
created using three rotation angles.
Along_axis_orientation Specifies the orientation of a coordinate system (e.g. marker
or part) by directing one of the axes. Adams View will assign
an arbitrary rotation about the axis.
in_plane_orientation Specifies the orientation of a coordinate system (e.g. marker
or part) by directing one of the axes and locating one of the
coordinate planes.
force 47

relative_to Specifies the coordinate system that location coordinates
and orientation angles correspond to.
i_marker_name Specifies a marker on the first of two parts connected by this
force element. Adams View connects this element to one
(Required) part at the I marker and to the other at the J marker.
j_marker_name Specifies a marker on the second of two parts connected by
this force element. Adams View connects this element to
one part at the I marker and to the other at the J marker.
1. Bushing is a massless force with linear stiffness and damping properties. It applies a force and a torque
to two parts. You specify a marker on each part for force or torque application. Each force consists of
three components in the coordinate system of the J marker, one in the x-axis direction, one in the y-
axis direction, and one in the z-axis direction. Likewise each torque consists of three components in
the coordinate system of the J marker, one about the x-axis, one about the y-axis, and one about the
z-axis. The magnitude of the force is linearly dependent upon the relative displacement and the
relative velocity of the two markers. The magnitude of the torque is dependent upon the relative angle
of rotation and the relative rotational velocity of the parts containing the specified markers.
2. A bushing has the same constitutive relation forms as a field. The primary difference between the two
forces is that certain coefficients (Kij and Cij, where i is not equal to j) are zero for the bushing. You
define only the diagonal coefficients (Kii and Cii) when you write the bushing. The following
constitutive equations define how Adams uses the data you input for a bushing to apply a force and
a torque to the I marker depending on the displacement and velocity of the I marker relative to the J
[Fx] [K11 0 0 0 0 0 ] [x]
[Fy] [0 K22 0 0 0 0 ] [y]
[Fz] = - [0 0 K33 0 0 0 ] [z]
[Tx] [0 0 0 K44 0 0 ] [a]
[Ty] [0 0 0 0 K55 0 ] [b]
[Tz] [0 0 0 0 0 K66] [c]
[C11 0 0 0 0 0 ] [Vx] [F1]
[0 C22 0 0 0 0 ] [Vy] [F2]
- [0 0 C33 0 0 0 ] [Vz] + [F3]
[0 0 0 C44 0 0 ] [Wx] [T1]
[0 0 0 0 C55 0 ] [Wy] [T2]
[0 0 0 0 0 C66] [Wz] [T3]
3. Fx, Fy, and Fz are the measure numbers of the translational force components parallel to the axes of
the Cartesian coordinate system of the J marker. The terms x, y, and z are the translational
displacements of the I marker with respect to the J marker measured in the Cartesian coordinate
system of the J marker. The terms Vx, Vy, and Vz are the time derivatives of x, y, and z, respectively.
The terms F1, F1, and F3 represent the measure numbers of any constant force components parallel
to the axes of the Cartesian coordinate system of the J marker. Tx, Ty, and Tz are the rotational force
components parallel to the axes of the Cartesian coordinate system of the J marker. The terms a, b,
and c are the rotational displacements of the I marker about the x-axis, the y-axis, and the zaxis,
respectively, of the J marker. The terms Wx, Wy, and Wz are the time derivatives of a, b, and c,
respectively, in the J marker reference frame. The terms T1, T2, and T3 are the measure numbers of
any constant torque components acting parallel to the axes of the Cartesian coordinate system of the
J marker.
4. For the rotational constitutive equations (K1, K2, and K3) to be accurate, at least two of the rotations
(a, b, c) must be small. Therefore, the bushing force calculations may not be accurate unless two of
the three values remain small (i.e. smaller than 10 degrees). It does not matter which rotation is
largest.
be assigned to it.
8. The three damping coefficients multiply the translational velocity components of the I marker along
the x-axis, the y-axis, and the z-axis of the J marker. The force due to damping is zero when there is
no relative translational velocity between the two markers. DAMPING must be in units of force per
unit of displacement per unit of time.
force 49
9. The three stiffness coefficients multiply the three translational displacement components of the
origin of the I marker along the x-axis, the y-axis, and the z-axis of the J marker. STIFFNESS must
be in units of force per unit of displacement.
10. The force pre-load terms are the constant force components along the x-axis, the y-axis, and the z-
axis of the J marker.
11. The three tdamping coefficients multiply the rotational velocity components of the body in which
the I marker is fixed about the x-axis, the y-axis, and the z-axis of the J marker. The torque due to
damping is zero when there is no relative rotational velocity between the two markers.
12. The I and J markers defined by the location parameter will be automatically created at this location
on the I_PART_NAME and J_PART_NAME respectively. By default, you supply Cartesian (x, y, z)
coordinates. You may use the 'defaults units coordinate_system_type =' command to change this
convention. For example, selecting 'cylindrical' means you will subsequently be supplying r, theta,
and z coordinates. Adams View applies your location coordinates in the coordinate system you
identify with the RELATIVE_TO parameter. The default for the RELATIVE_TO parameter is the
default coordinate system. (See the RELATIVE_TO parameter for this command).
force being created. These markers are created automatically.
system.
14. For the ‘along_axis_parameter’, you may enter either one or two locations to direct the axis. If you
enter one location, the axis will point toward the location. If you specify two locations, the axis will
be parallel to, and pointing the same way as the vector from the first location to the second. Note that
this does not completely dictate the orientation of the coordinate system. Adams View will position
the coordinate system with an arbitrary rotation about the axis. If you must completely control the
coordinate system orientation, use ORIENTATION or IN_PLANE_ORIENTATION. By default,
you direct the Z axis of the coordinate system.
force create element_like friction
15. You may enter either two or three locations for the ‘referencein_plane_orientation’ parameter. If you
enter two locations, the axis will point toward the first location and the plane will fall on the second.
If you specify three locations, the axis will be parallel to, and pointing the same way as, the vector from
the first location to the second and the plane will be parallel to the plane defined by the three
locations. By default, you direct the Z axis of the coordinate system and locate the ZX plane. You may
use the 'DEFAULTS ORIENT_AXIS_AND_PLANE AXIS_AND_PLANE_SETTING='
command to change this convention. For example, selecting X_AXIS_XY_PLANE means you will
subsequently be directing the X axis and locating the XY plane. Adams View applies your location
coordinates in the coordinate system you identify with the RELATIVE_TO parameter. The default
for the RELATIVE_TO parameter is the default coordinate system.
16. If this parameter is not specified, the default coordinate system is used. The default coordinate
system is initially your model, i.e. the global coordinate system. You may change the default
coordinate system using the 'defaults coordinate_system' command.

Format:
Friction_name = new friction name
Adams_id = geom._id
Comments = string
Joint_name = existing joint
Yoke = i_yoke/j_yoke
Mu_static = real
Mu_dynamic = real
Reaction_arm = real
Friction_arm = real
Initial_overlap = real
Pin_radius = real
Ball_radius = real
Bending_factor = real
max_stiction_deformation = real
friction_force_preload = real
max_friction_force = real
max_friction_torque = real
transition_velocity_coefficient = real
force 51

overlap_delta = INCREASE/ DECREASE/ CONSTANT
effect = ALL/ STICTION/ SLIDING
smooth = real
torsional_moment = on/off
bending_moment = on/off
preload = on/off
reaction_force = on/off
Description:

friction_name A new friction
Adams_id Adams_id Specifies an integer used to identify this element in the
Adams data file.
modified.
joint_name Existing joint name Specifies the translational, revolute, or cylindrical joint
associated with this entity. Some entities constrain
motion at, or are otherwise associated with, specific
joints. You use this parameter to identify that joint.
yoke I_yoke/J_yoke
mu_static Real Specifies a real number greater than zero.
mu_dynamic Real Specifies a real number greater than zero.
reaction_arm Real Specifies a real number greater than zero.
friction_arm Real Specifies a real number greater than zero.
initial_overlap Real
pin_radius Real Specifies a real number greater than zero.
ball_radius Real Specifies a real number greater than zero.
bending_factor Real Specifies a real number greater than zero.
stiction_transition_ve Real Specifies a real number greater than zero.
locity
max_stiction_deform Real Specifies a real number greater than zero.
ation
friction_force_preloa Real Specifies a real number greater than or equal to zero.
d

friction_torque_prelo Real Specifies a real number greater than or equal to zero.
ad
max_friction_force Real Specifies a real number greater than zero.
max_friction_torque Real Specifies a real number greater than zero.
transition_velocity_co Real Specifies a real number greater than zero.
efficient
overlap_delta INCREASE, Can take the values INCREASE, DECREASE,
DECREASE, CONSTANT
CONSTANT
effect ALL, STICTION, Specifies the friction effect required.
SLIDING
Smooth Real
torsional_moment On/Off
bending_moment On/Off
preload On/Off
reaction_force On/Off
force 53
force create element_like rotational_spring_damper
followed by the Adams data set joint ID number. For example, the name of Adams JOINT/101 is
JOI101. If you created the joint during preprocessing, you will have given it a name at that time.
If a joint is available by default, you may identify it by entering only its name. If it is not, you must
associated with it.

Allows you to create a rotational spring damper object.
The spring damper force applies a rotational or a translational spring damper between two markers. For a
rotational spring damper, the z-axis of the I marker and the z-axis of the J marker must be parallel and must
point in the same direction. Because the spring- damper force is always an action-reaction force, the direction
of the translational force is the line of sight between the I and the J markers. Thus, if the force is positive, the
markers experience a repelling force along this line, and if the force is negative, the markers experience an
attracting force. The magnitude of the translational force applied to the parts containing the two markers is
linearly dependent upon the relative displacement and velocity of the two markers. The following linear
constitutive equation describes the force applied at the I marker:
force = -C*db/dt - K*(b-LENGTH) + FORCE
Adams automatically computes the terms db/dt and b. The force value is the force on the I marker from the
J marker; the force on the J marker is equal and opposite. The term b is the distance between the I and the J
markers. Adams assumes that b is always greater than zero. The following linear constitutive equation
describes the torque applied at the I marker:
torque = -CT*da/dt - KT*(a-ANGLE) + TORQUE
Adams automatically computes the terms da/dt and a. The torque is applied to the I marker about the positive
z-axis of the I marker; the torque on the J marker is equal and opposite to the torque on the I marker. The
right-hand rule defines a positive torque. The term a is the angle between the x-axes of the I and the J markers.
Adams takes into account the total number of complete turns.
Considerations:
 If the z-axis of the I marker is not parallel to, and/or not pointed in the same direction as, the z-axis
of the J marker for a rotational spring-damper, the results are unpredictable.
 Since the line-of-sight method determines the direction of a translational spring damper force, the I
and the J markers cannot be coincident.
Format:
spring_damper_name= New spring damper force name
Adams_id= geom._id
comments= string
damping= TORSION_DAMP
stiffness= TORSION_STIFF
preload= torque(real)
displacement_at_preload= angle(integer)
i_part_name= an existing body
j_part_name= an existing body
location= location
relative_to= existing model,part or marker
i_marker_name= an existing marker
j_marker_name= an existing marker
Example:
force create element_like rotational_spring_damper &
spring_damper_name = FORCE_1 &
j_part_name = PART_2
Description:

spring_damper_name String Specifies the name of the new spring damper force. You
may use this name later to refer to this spring damper.
Adams_id Geom_id Specifies an integer used to identify this element in the
Adams data file.
modified.
Damping Real number Specifies the viscous damping coefficient for the spring
damper.
force 55

stiffness Real number Specifies the spring stiffness coefficient for the spring
damper.
preload Real Specifies the reference force or torque for the spring. This
is the force the spring exerts when the displacement
between the I and J markers is equal to
DISPLACEMENT_AT_PRELOAD (the reference length
of the spring).
displacement_at_preload real Specifies the reference length for the spring. If PRELOAD
(the reference force of the spring) is zero,
DISPLACEMENT_AT_PRELOAD equals the free
length.
i_part_name Existing body Specifies the part that is the first of two parts that this force
acts between. Adams View applies the force on one part at
the I marker and the other at the J marker. These markers
are automatically generated using this method of force
creation.
j_part_name Existing body Specifies the part that is the second of the two parts that this
force acts between. Adams View applies the force on one
part at the J marker and the other at the I marker. These
markers are automatically generated using this method of
force creation.
location Location Specifies the locations to be used to define the position of a
force during its creation. The I and J markers will be
automatically created at this location on the
orientation orientation Specifies the orientation of the J marker for the force being
created using three rotation angles. The I marker is
oriented based on the J marker orientation and the
requirements of the particular force being created. These
markers are created automatically.
along_axis_orientation location Specifies the orientation of a coordinate system (e.g. marker
or part) by directing one of the axes. Adams View will
assign an arbitrary rotation about the axis.
in_plane_orientation Location Specifies the orientation of a coordinate system (e.g. marker
or part) by directing one of the axes and locating one of the
coordinate planes.

relative_to An existing Specifies the coordinate system that location coordinates
model, part or and orientation angles correspond to.
marker
i_marker_name An existing Specifies a marker on the first of the two parts connected by
marker this force element. Adams View connects this element to
j_marker_name An existing Specifies a marker on the second of two parts connected by
marker this force element. Adams View connects this element to
1. Adams View will not allow you to have two spring dampers with the same name, so you must provide
a unique name.
be assigned to it.
yourself.
force 57
RELATIVE_TO parameter. The default for the RELATIVE_TO parameter is the default
coordinate system. (See the RELATIVE_TO parameter for this command).
coordinate system.
same way as the vector from the first location to the second.
By default, you direct the z-axis of the coordinate system. You may change this convention with the
subsequently be directing the x- axis. The plane convention setting does not affect this parameter.
coordinate system.
7. For the plane orientation, you may enter either two or three locations. If you enter two locations, the
axis will point toward the first location and the plane will fall on the second. If you specify three
locations, the axis will be parallel to, and pointing the same way as the vector from the first location
to the second and the plane will be parallel to the plane defined by the three locations.
force create fe_load
By default, you direct the z-axis of the coordinate system and locate the ZX plane. You may use the
be directing the x-axis and locating the XY plane.
coordinate system.
coordinate system is your model, i.e. the global coordinate system. You may change the default
force create fe_load

Allows you to create a new entity of the type fe_load in the Adams session. An fe_load defines a distributed
load acting on an existing fe_part.
Format:
force create direct fe_load
feload_name = new fe_load name
ref_fe_part = refer existing fe_part
ref_orientation_marker = refer existing marker
adams_id = real
fx = function expression
fy = function expression
fz = function expression
tx = function expression
ty = function expression
tz = function expression
user_function = function expression
routine = string
force_display = ON / OFF
Example:
force create direct fe_load
feload_name = .MODEL_1.FE_Load_1
ref_fe_part = FE_Part_1
ref_orientation_marker = MARKER_1
force 59
force delete
adams_id = 1
fx = SD(1)
fy = SD(1)
fz = SD(1)
tx = SD(1)
ty = SD(1)
tz = SD(1)
force_display = ON
This will create an fe_load with the name FE_Load_1 with provided parameters.
Description:

feload_name New fe_load Specifies the name of the fe_load to be created.
ref_fe_part Existing fe_part Specifies the already created fe_part on which the fe_load
will act.
ref_orientation_marker Existing marker Specifies the already created marker which defines the
orientation of the fe_load.
fx
fy
fz
tx
ty
tz
user_function String Specifies up to 30 values for Adams to pass to a user written
subroutine. See the Adams User's Manual for information
on writing user-written subroutines.
routine String
force_display String
force delete
Allows you to delete an existing force.
You must enter the name of the force you wish to delete by either picking it from the screen or specifying the
full name.
force modify body gravitational
Format:
force delete
force delete force_name= Existing force
Example:
force delete &
force delete force_name= gravity
Description:

Force_name Existing Force Specifies the force to be deleted
associated with it.
Tips:
 Any Adams View object you delete, may be "undeleted" by using the UNDO commands. If you
have deleted something you would like back, enter the command "undo backward", or pick on the
fixed menu entry, 'UNDO'.

Allows modification of the gravitational body object.
force 61
Format:
gravity_field_name = existing_gravity_field_name
new_gravity_field_nam= new_gravity_field_name
comments = comment_string
units_consistency_factor = real_number
x_component_gravity = real_number
y_component_gravity = real_number
z_component_gravity = real_number
Example:
force modify body gravitational &
gravity_field_name = gravity &
new_gravity_field_name = ACCGRAV__1 &
comments = comment_string &
units_consistency_factor = 0.1 &
x_component_gravity = 0.99 &
y_component_gravity = 0.88 &
z_component_gravity = 0.9
Description:

gravity_field_name An Existing Specifies the gravity field to modify. You use this
Gravity Field parameterto identify the existing gravity field to affect
with thiscommand.
new_gravity_field_name A New Gravity Specifies the name of the new gravity field. You may use
Field this name later to refer to this gravity field. Adams
Viewwill not allow you to have two gravity fields with the
same full name, so you must provide a unique name.
modified.
units_consistency_factor Real Specifies a conversion factor to make your force, mass,
length, and time units consistent. If you do not specify
UNITS_CONSISTENCY_FACTOR, or specify it as
zero, Adams View will calculate it for you when it writes
theAdams data set.

x_component_gravity Acceleration Specifies the x component of gravitational acceleration
with respect to the ground reference frame
y_component_gravity Acceleration Specifies the y component of gravitational acceleration
z_component_gravity Acceleration Specifies the z component of gravitational acceleration
1. In conjunction with the part masses, the gravitational field defines a body force atthe center of gravity
of each part. The force direction is defined by the X_COMPONENT_GRAVITY,
Y_COMPONENT_GRAVITY, and Z_COMPONENT_GRAVITY parameters. The force
magnitude is the part mass multiplied by the magnitude of the gravity vector. Each gravity field is
written as an Adams ACCGRAV statement. Although Adams View allows you to create more than
one gravity field, you should only use one, since Adams only allows one ACCGRAV statement.
2. You may also specify UNITS_CONSISTENCY_FACTOR in a gravity field.Adams View writes this
as the GC parameter in the ACCGRAV statement. AlthoughUNITS_CONSISTENCY_FACTOR
affects the reporting of all forces, not justgravitational, it is included here because it also appears in
the ACCGRAVstatement.
3. You may identify a gravity field by typing its name or by picking it from the screen. If the gravity field
is not visible on the screen, you must type the name. You may also find it convenient to type the name
even if the gravity field is displayed.
If you created the gravity field by reading an Adams data set file, the gravity field name is 'acc'. If you
created the gravity field during preprocessing, you gave it a name at that time. If a gravity field is
available by default, you may identify it.
by entering its name only. If it is not, you must enter its full name. To identify a gravity field under
a different model, for instance, you may need to enter the model name as well. For example, you may
specify gravity field 'grav' from model 'robot' by entering ".robot.grav". You must separate multiple
gravity-field names by commas.
If the gravity field is visible in one of your views, you may identify it by picking on any of the graphics
associated with it. You need not separate multiple gravity-field picks by commas.
name when entering it. 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
force 63
force modify direct force_vector
5. The number of levels used varies from case to case and the parentage must exist before an entity can
be assigned to it.
7. You may select any force, mass, length, or time units you wish. In order for Adams results to be
meaningful, however, you or Adams View must compute a factor such that the equationForce = (Mass
/ UNITS_CONSISTENCY_FACTOR) * Accelerationis satisfied. For example, if you use Newtons,
kilograms, millimeters, and seconds, UNITS_CONSISTENCY_FACTOR is 1000. Adams
documentation and Data Set Language refer to this factor as GC, on the ACCGRAV card. The only
case in which you should set UNITS_CONSISTENCY_FACTOR yourself is when you are using a
set of units Adams View does not support. Otherwise, you should probably let Adams View compute
it for you. If you do use this command to set UNITS_CONSISTENCY_FACTOR to a non-zero
value, Adams View will write your value to an Adams data set.Adams View will not change your value,
even if you later change your force, mass, length, or time units. If you explicitly set
UNITS_CONSISTENCY_FACTOR, then later change your units, remember to
updateUNITS_CONSISTENCY_FACTOR.
Tips:
 If you type a "?", Adams View will list the gravity fields available by default.

Allows you to modify an existing vector force.
Format:
force_vector_name= existing vforce
new_force_vector_name= new vforce
Adams_id = geom._id
comments = string
j_floating_marker_name= existing marker
x_force_function = function

y_force_function = function
z_force_function = function
user_function= real
Description:

force_vector_name An existing vforce Specifies the force_vector to modify.
new_force_vector_name A new vforce Specifies the name of the new force_vector.
Adams_id integer Specifies an integer used to identify this element in
modified.
j_floating_marker_name Existing marker
floating marker.
ref_marker_name Existing marker Specifies a marker that acts as a coordinate reference
for the definition of three orthogonal force and/or
torque components. These components make up the
force and/or torque being defined.
x_force_function, Function Specifies the x component of the translational force
the x axis of the reference marker specified in the
y_force_function, Function Specifies the y component of the translational force
z_force_function Function Specifies the y component of the translational force
force 65
1. The FORCE_VECTOR is a translational vector force that is specified using three orthogonal
components. The resultant vector determines the direction of the force action. This resultant vector
is formed by the three component forces that the user defines along the "reference marker" axes. The
reaction is equal and opposite to the action. The user may define the FORCE_VECTOR
components in Adams View through user-specified function expressions or by specifying up to 30
user-defined parameters that are passed to a user-written subroutine (a "VFOSUB") linked to Adams.
The FORCE_VECTOR corresponds to the Adams VFORCE statement.
The FORCE_VECTOR creates an Adams translational vector force element that applies the forces
between two parts of the system. The element applies an action force to the part that contains the I
marker and a corresponding reaction force to the part to which the a "floating" J marker belongs. This
"floating marker" is automatically created by Adams View and is positioned to be coincident with the
I marker. Subsequently, the FORCE_VECTOR establishes the position of the "floating" J marker.
As the system moves, Adams moves the "floating" J marker on its part to keep the "floating" J and I
markers superimposed. Thus, Adams applies the reaction force to the "floating" J markers part at the
instantaneous position of the I marker.
The total vector force that Adams supplies is the vector sum of the individual force components that
the user specifies. The magnitude of the total vector force is the square root of the sum of the
components squared. Its value will be the resultant (i.e., the square root of the sum of the squares) of
the three mutually-orthogonal force components.
2. You may identify a force vector by typing its name or by picking it from the screen.
If the force vector is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the force vector is displayed.
If you created the force vector by reading an Adams data set or graphics file, the force vector name is
the letters VFO followed by the Adams data set force vector ID number. The name of Adams
VFORCE/101 is VFO101, for example. If you created the force vector during preprocessing, you
If a force vector is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a force vector under another model, for instance, you may need
to enter the model name as well. For example, you may specify force vector 'spring' from the model
'suspension' by entering ".suspension.spring". If you type a "?", Adams View will list the force vector
You must separate multiple force vector names by commas.
If the force vector is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple force vector picks by commas.
be assigned to it.
verification.
force 67
Components Examples
NUMBERS
OPERATORS
SYSTEM CONSTANTS
BLANKS
You cannot put a blank space in the middle of a number.
Adams does not accept a blank space between a function and its left bracket. (This is true for both,
CONTINUATION COMMAS
FUNCTION BUILDER
window.
SYSTEM VARIABLES
In general, you use a function character string (such as DM, VX, or FZ) and a list of values (for
example, i1, i2, and i3) to access a system variable in an expression. For example, the value i1 may be
the name of the marker for which you want to measure a quantity (such as displacement, velocity,
acceleration, or force), i2 is the name of the marker with respect to which you want to measure the
quantity, and i3 is the name of the marker you want to use to resolve the components of the quantity.
If you do not specify marker i3, Adams computes the result in the ground reference frame.
ARITHMETIC IFS
Arithmetic IFs allow you to conditionally define FUNCTION. The format for arithmetic IFs follows.
force 69
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
be accessed.
Names Purposes
Cautions:
 The user must ensure that the reference_marker is fixed on a part (i.e. not a "floating" marker). The
force modify direct general_force
Tips:
1. You use the force vector name parameter to identify the existing force_vector to affect with this
command.
2. You may use the new force vector name later to refer to this force_vector. Adams View will not allow
you to have two force_vectors with the same full name, so you must provide a unique name.

Allows you to modify an existing general force.
Format:
General_force_name= existing genforce
new_general_force_name= new genforce
Adams_id= geom._id
comments= string
, j_part_name= existing body
x_torque_function= function
y_torque_function= function
z_torque_function= function
user_function= real
x_force_function = function
y_force_function = function
z_force_function = function
Description:

General_force_name Existing genforce Specifies the general force to modify.
new_general_force_name New genforce Specifies the name of the new general_force.
Adams_id integer Specifies an integer used to identify this element
force 71

or modified.
j_part_name Existing body Specifies the part on which Adams View creates
a floating marker.
ref_marker_name Existing marker Specifies a marker that acts as a coordinate
reference for the definition of three orthogonal
force and/or torque components. These
components make up the force and/or torque
being defined.
x_torque_function Function Specifies the x component of the rotational
torque for this element.
y_torque_function Function Specifies the y component of the rotational
z_torque_function Function Specifies the y component of the rotational
subroutines.
X_force_function Function Specifies the x component of the translational
force for this element. Adams applies this force
parallel to the x axis of the reference marker
specified in the REF_MARKER_NAME
parameter.
Y_force_function Function Specifies the y component of the translational
parallel to the y axis of the reference marker
parameter.
z_force_function Function Specifies the z component of the translational
parallel to the z axis of the reference marker
parameter.
formed by the three component forces and the three component torques determines the direction of
The GENERAL_FORCE corresponds to the Adams GFORCE statement.
A GENERAL_FORCE creates a six component force element that applies the forces between two
As the system moves, Adams moves the "floating_marker" on its part to keep the "floating_marker"
the "floating_marker" marker at the instantaneous position of the I marker. The magnitude of the
force depends on expressions or subroutines that the user supplies. The value of the force is the
resultant (i.e., the square root of the sum of the squares) of (up to) three mutually orthogonal force
components together with the resultant (i.e., the square root of the sum of the squares) of (up to) three
mutually orthogonal torque components.
The resultant vector formed by the three user-defined component forces along the reference marker
action.
The resultant vector formed by the three component torques determines the direction of the
rotational torque action. The user defines these torques about the reference marker axes. The
reaction is equal and opposite to the action.
2. You may identify a general force by typing its name or by picking it from the screen.
If the general force is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the general force is displayed.
If you created the general force by reading an Adams data set or graphics file, the general force name
is the letters GFO followed by the Adams data set general force ID number. The name of Adams
GFORCE/101 is GFO101, for example. If you created the general force during preprocessing, you
If a general force is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a general force under another model, for instance, you may need
to enter the model name as well. For example, you may specify general force 'spring' from the model
'suspension' by entering ".suspension.spring". If you type a "?", Adams View will list the general force
You must separate multiple general force names by commas.
force 73
If the general force is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple general force picks by commas.
be assigned to it.
time.
verification.
Components Examples
Continuation Commas FUNCTION = 1 + 1 + 1 + 1 + 1 + 1, + 1 + 1 + 1 + 1 + 1 + 1 + 1
NUMBERS
force 75
OPERATORS
From greatest to the least, the operators have the following priorities. ** then * / then + -. In other
When a statement has operators of the same priority, Adams executes them from left to right.
You can use parentheses to alter the precedence of operators. For example, in the equation,
SYSTEM CONSTANTS
BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
window.
SYSTEM VARIABLES
ARITHMETIC IFS
follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
force 77
be accessed.
Names Purposes
Cautions:
1. The user must ensure that the reference_marker is fixed on a part (that is, not a "floating" marker).
The reference_marker may be the same as the I marker and may be on any part in the model.
Tips:
1. You use the General force name parameter to identify the existing torque _vector to affect with this
command.
2. You may use the new general force name later to refer to this general_force. Adams View will not
allow you to have two general_forces with the same full name, so you must provide a unique name.
3. Adams applies x_torque_function parallel to the x axis of the reference marker in the sense of the
right-hand rule, i.e., a positive torque causes a counterclockwise rotation if you are looking along the
axis from positive to negative.
4. Adams applies this y_torque_function parallel to the y axis of the reference marker in the sense of the
5. Adams applies this z_torque_function parallel to the z axis of the reference marker in the sense of the
force modify direct single_component_force

Allows modification of the single component force object.
Format:
Force modify direct single_component_force
single_component_force_name= an existing single-component force
new_single_component_force_name= a new single-component force
Adams_id= geom_id
comments= string
type_of_freedom= translational/rotational
action_only= on/off
function= function
user_function= real
routine= string
error= real
Description:

single_component_force_na AN EXISTING Specifies the single_component_force to modify.
me SINGLE-
COMPONENT
FORCE
new_single_component_forc A NEW SINGLE- Specifies the name of the new
e_name COMPONENT single_component_force.
FORCE
Adams_id Integer Specifies an integer used to identify this element in
modified.
type_of_freedom translational/rotation Specifies what type of force (rotation or translation)
al to apply.
action_only On/off Specifies whether the force is action-only or action-
reaction.
force 79

Function Function Specifies the function expression definition that is
used to compute the value of this variable.
written subroutine. See the Adams User's Manual
for information on writing user-written
subroutines.
I_marker_name Existing marker Specifies a marker on the first of two parts
Error Real
routine String
1. A single-component force applies a force or a torque to two parts. You specify a marker on each part
for force or torque application. You may define the magnitude of the force as a function of any
combination of displacements, velocities, other applied forces, user-defined variables, and time. The
force applied can be action-reaction forces or action-only forces.
For translational action-reaction forces, Adams applies the user-defined force along the line
connecting the I and the J markers. The force exerted on I is directed from J toward I, while the force
exerted on J is directed from I toward J.
For translational action-only forces, Adams applies the force on the I marker only. There is no
reaction on the J marker. The force on the I marker is directed along the z axis of the J marker.
For rotational action-reaction forces, Adams applies the torque on the I marker about the z axes of
the J marker. Furthermore, Adams assumes that the z axes of the I and the J markers are constrained
to always be parallel for this type of single-component force.
For rotational action-only forces, Adams applies the torque on the I marker only. There is no reaction
on the J marker. The torque on the I marker is directed along the z axis of the J marker.
You write a FUNCTION expression or a user-written subroutine (an SFOSUB) to define the
constitutive equation for the force applied at the I marker. Adams evaluates the reaction forces at the
J marker.
2. You may identify a single-component force by typing its name or by picking it from the screen.
If the single-component force is not visible on the screen, you must type the name. You may also find
it convenient to type the name even if the single-component force is displayed.
If you created the single-component force by reading an Adams data set or graphics file, the single-
component force name is the letters SFO followed by the Adams data set single-component force ID
number. The name of Adams SFORCE/101 is SFO101, for example. If you created the single-
component force during preprocessing, you gave it a name at that time.
If a single-component force is available by default, you may identify it by entering its name only. If
it is not, you must enter its full name. To identify a single-component force under another model, for
instance, you may need to enter the model name as well. For example, you may specify single-
component force 'spring' from the model 'suspension' by entering ".suspension.spring". If you type
a "?", Adams View will list the single-component forces available by default.
You must separate multiple single-component force names by commas.
If the single-component force is visible in one of your views, you may identify it by picking on any of
You need not separate multiple single-component force picks by commas.
3. Adams View will not allow you to have two single_component_forces with the same full name, so
be assigned to it.
force 81
5. For an action-reaction force, Adams applies a force between the I and J markers. For an action-only
force, Adams applies a force on the I marker directed by the Z axis of the J marker, but does not apply
a reaction force at the J marker.
verification.
Components Examples
System constants FUNCTION = PI + 20
System variables FUNCTION = AX(1040, 2010)
Arithmetic IFs FUNCTION = IF(DX(3, 5): -1, 0, 1)
FORTRAN-77 functions FUNCTION = ABS(NUM) - 6
Continuation commas FUNCTION = 1 + 1 + 1 + 1 + 1 + 1, + 1 + 1 + 1 + 1 + 1 + 1 + 1
Adams functions FUNCTION = POLY(0, 0, 6.28)
NUMBERS
OPERATORS
• You can use parentheses to alter the precedence of operators.
For example, in the equation

SYSTEM CONSTANTS
PI Value of pi (to eighteen significant digits)

DTOR Value of pi/180 for converting degrees to radians
RTOD Value of 180/pi for converting radians to degrees
The following example of a FUNCTION with a system constant multiplies the system
constant PI by the displacement of marker 10 with respect to marker 14:
BLANKS
• Adams does not accept a blank space between a function and its left bracket. (This is true for both
CONTINUATION COMMAS
you break the expression at a comma that is part of the expression, you must use both the expression
FUNCTION BUILDER
The FUNCTIONS button at the right side of the Adams View text editor provides a means of
SYSTEM VARIABLES
force 83
computations. These values are access through a collection of functions. The accessible system
FUNCTIONS button to ge a list of functions that can be accessed.
ARITHMETIC IFS
follows.
Adams evaluates expression 1. If expression 1 is less than zero, the arithmetic IF equals
expression 2; if expression 1 equals zero, the arithmetic IF equals expression 3; and if
expression 1 is greater than zero, the arithmetic IF equals expression 4.
A FUNCTION expression with an arithmetic IF and its four expressions is below.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
ge a list of functions that can be accessed.
Adams FUNCTIONS
Invoke the text edit window and pick the FUNCTIONS button to be a list of functions that can be
accessed.
force modify direct_torque_vector
Names Purposes
AKISPL Accesses the data in a SPLINE statement and uses the Akima cubic method to fit a cubic
curve(a spline) to the data.
BISTOP Evaluates a force restricting displacement of a part in two opposite directions.
CUBSPL Accesses the data in a SPLINE statement and uses the traditional cubic method to fit a
cubic curve (a spline) to the data.
FORCO Evaluates a Fourier cosine series
S
HAVSIN Evaluates a haversine function.
IMPAC Evaluates a force restricting displacement of a part in one direction.
T
POLY Evaluates a polynomial.
SHF Evaluates a simple harmonic function.
STEP Approximates a step function with a cubic polynomial.
Tips:
1. ROTATIONAL designates a rotational force, that is, a torque.
2. TRANSLATIONAL designates a translational force.
3. You use the single component force parameter to identify the existing single_component_force to
affect with this command.
4. You may use the new single component force name later to refer to this single_component_force.

Allows you to modify an existing vector torque.
Format:
torque_vector_name= existing vtorque
new_torque_vector_name= new vtorque
Adams_id= geom._id
comments= string
force 85

j_part_name= existing body
x_torque_function= function
y_torque_function= function
z_torque_function= function
user_function= real
Description:

torque_vector_name Existing vtorque Specifies the torque_vector to modify.
new_torque_vector_name New Vtorque Specifies the name of the new torque_vector.
Adams_id integer Specifies an integer used to identify this element in the
Adams data file.
modified.
i_marker_name Existing marker Specifies the marker at which Adams applies the forces
and/or torques.
floating marker.
ref_marker_name Existing marker Specifies a marker that acts as a coordinate reference for
the definition of three orthogonal force and/or torque
components. These components make up the force
and/or torque being defined.
x_torque_function Function Specifies the x component of the rotational torque for
this element. Adams applies this torque parallel to the
x axis of the reference marker in the sense of the right-
hand rule, i.e., a positive torque causes a
counterclockwise rotation if you are looking along the

y_torque_function Function Specifies the y component of the rotational torque for
y axis of the reference marker in the sense of the right-
z_torque_function Function Specifies the y component of the rotational torque for
y axis of the reference marker in the sense of the right-
1. The TORQUE_VECTOR is a rotational force (i.e, a torque) that consists of three orthogonal
components. The direction of the torque action is determined by the resultant vector formed by the
three component torques defined by the user along the "reference marker" axes. The reaction is equal
and opposite to the action. The user may define the TORQUE_VECTOR components in Adams
View through user-specified function expressions or by specifying up to 30 user-defined parameters
that are passed to a user-written subroutine (a "VTOSUB") the user links with Adams.
The TORQUE_VECTOR corresponds to the Adams VTORQUE statement.
The TORQUE_VECTOR creates an Adams rotational force element (i.e., torque) that applies the
forces between two parts of the system. The element applies an action to the part to which the I
marker belongs and a corresponding reaction to the part to which the "floating" J marker belongs.
This "floating marker" is automatically created by Adams View and is positioned to be coincident
with the I marker. Subsequently, the TORQUE_VECTOR establishes the position of the "floating"
J marker. As the system moves, Adams moves the "floating" J marker on its part to keep the "floating"
J and I markers superimposed. Thus, Adams applies the reaction torque to the "floating" J markers
part.
The components of the torque depends on expressions or subroutines that the user supplies. Its value
will be the resultant (i.e., the square root of the sum of the squares) of the three mutually orthogonal
torque components.
2. You may identify a torque vector by typing its name or by picking it from the screen.
If the torque vector is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the torque vector is displayed.
force 87
If you created the torque vector by reading an Adams data set or graphics file, the torque vector name
is the letters VTO followed by the Adams data set torque vector ID number. The name of Adams
VTORQUE/101 is VTO101, for example. If you created the torque vector during preprocessing,
you gave it a name at that time.
If a torque vector is available by default, you may identify it by entering its name only. If it is not,
you must enter its full name.To identify a torque vector under another model, for instance, you may
need to enter the model name as well. For example, you may specify torque vector 'spring' from the
model 'suspension' by entering ".suspension.spring". If you type a "?", Adams View will list the torque
vector available by default.
You must separate multiple torque vector names by commas.
If the torque vector is visible in one of your views, you may identify it by picking on any of the
You need not separate multiple torque vector picks by commas.
be assigned to it.
time.
verification.
force 89
Components Examples
NUMBERS
OPERATORS
SYSTEM CONSTANTS
BLANKS

CONTINUATION COMMAS
FUNCTION BUILDER
window.
SYSTEM VARIABLES
In general, you use a function character string (such as DM, VX, or FZ) and a list of values (for
example, i1, i2, and i3) to access a system variable in an expression. For example, the value i1 may be
the name of the marker for which you want to measure a quantity (such as displacement, velocity,
acceleration, or force), i2 is the name of the marker with respect to which you want to measure the
quantity, and i3 is the name of the marker you want to use to resolve the components of the quantity.
If you do not specify marker i3, Adams computes the result in the ground reference frame.
ARITHMETIC IFS
Arithmetic IFs allow you to conditionally define FUNCTION. The format for arithmetic IFs follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
force 91
Adams FUNCTIONS
be accessed.
Names Purposes
Cautions:
 You must ensure that the reference_marker is fixed on a part (i.e. not a "floating" marker). The
Tips:
1. You use the torque vector name parameter to identify the existing torque _vector to affect with this
command.
force modify element_like beam
2. You may use the new torque vector name later to refer to this torque_vector. Adams View will not
allow you to have two torque_vectors with the same full name, so you must provide a unique name.

Allows modification of the beam object.
Format:
beam_name = beam1
new_beam_name = beam2
Adams_id = integer
ixx= real number
iyy = real number
izz= real number
y_shear_area_ratio= real number
z_shear_area_ratio= real number
youngs_modulus = real number
shear_modulus = real number
length = real number
area_of_cross_section = real number
damping_ratio = real number
matrix_of_damping_terms = a 6x6 matrix
i_marker_name = existing_marker_name
j_marker_name = existing_marker_name
Example:
force modify element_like beam &
beam_name = beam1 &
new_beam_name = beam2 &
Adams_id = 1 &
ixx = 4 &
iyy = 2 &
izz = 3 &
y_shear_area_ratio = 0.9 &
z_shear_area_ratio = 0.8 &
force 93
force modify element_like beam &

youngs_modulus = 0.4&
shear_modulus = 0.2 &
length = 2 &
area_of_cross_section = 1.5 &
damping_ratio = 2 &
matrix_of_damping_terms = a 6x6 matrix &
Description:

beam_name An Existing Beam Specifies the name of the new beam. You may use this
name later to refer to this beam.
new_beam_name A New Beam Specifies the name of the new beam. You may use this
name later to refer to this beam. Adams View will not
allow you to have two beams with the same full name, so
Adams data file.
modified.
ixx Area_inertia Specifies the polar area moment of inertia about the X
axis of a cross section perpendicular to the length of the
beam.By definition, the beam lies along the positive X
axis of the J marker. You should compute IXX about the
X axis of the J marker.
Iyy Area_inertia Specifies the principal area moment of inertia about the
Y axis of a cross section perpendicular to the length of the
beam. By definition, the beam lies along the positive X
axis of the J marker. You should compute IYY about the
Y axis of the J marker.
Izz Area_inertia Specifies the principal area moment of inertia about the
Z axis of a cross section perpendicular to the length of the
beam. By definition, the beam lies along the positive X
axis of the J marker. You should compute IZZ about the
Z axis of the J marker.
y_shear_area_ratio Real Specifies the shear area ratio in the y direction.

z_shear_area_ratio Real Specifies the shear area ratio in the z direction.
youngs_modulus Pressure Specifies Young's modulus of elasticity for the beam
material.
shear_modulus Pressure Specifies the shear modulus of elasticity for the beam
material.
length Length Specifies the undeformed length of the beam along the x
axis of the J marker.
area_of_cross_section Area Specifies the uniform area of the beam cross section. The
centroidal axis must be orthogonal to this cross section.
damping_ratio Time Specifies a ratio for calculating the structural damping
matrix for the beam. Adams multiplies the stiffness
matrix by the value of DAMPING_RATIO to obtain the
damping matrix.
matrix_of_damping_ter Real Specifies a six-by-six structural damping matrix for the
ms beam.
by this force element. Adams View connects this element
to one part at the I marker and to the other at the J
marker.
Specifies the theory to be used to define the force this
element will apply. By default the LINEAR theory is
used. If the NONLINEAR option is used, the full non
linear Euler-Bernoulli theory is used. If the STRING
option is used, a simplified non linear theory is used. The
simplified non linear theory may speed up your
simulations with little performance penalties.
1. The beam, which is massless and has a uniform cross section, is modeled as alinear translational and
a linear rotational action-reaction force between twomarkers. The forces the beam produces are
linearly dependent on the relativedisplacements and the relative velocities of the markers at its
endpoints. The xaxisof the J marker defines the centroidal axis of the beam. The y-axis and the zaxisof
the J marker are the principal axes of the cross section. They areperpendicular to the x-axis and to each
other. When the beam is in an undeflectedposition, the I marker has the same angular orientation as
the J marker, and the Imarker lies on the x-axis of the J marker.
force 95
The following constitutive equations define how Adams uses the data you input for a beam to apply
a force and a torque to the I marker depending on the displacement and velocity of the I marker
relative to the J marker. Adams appliesa force of equal magnitude and opposite direction to the J
marker.
[Fx] [K11 0 0 0 0 0 ] [x]
[Fy] [0 K22 0 0 0 K26] [y]
[Fz] = - [0 0 K33 0 K35 0 ] [z]
[Tx] [0 0 0 K44 0 0 ] [a]
[Ty] [0 0 K35 0 K55 0 ] [b]
[Tz] [0 K26 0 0 0 K66] [c]
[C11 C21 C31 C41 C51 C61] [Vx]
[C21 C22 C32 C42 C52 C62] [Vy]
- [C31 C32 C33 C43 C53 C63] [Vz]
[C41 C42 C43 C44 C54 C64] [Wx]
[C51 C52 C53 C54 C55 C65] [Wy]
[C61 C62 C63 C64 C65 C66] [Wz]
Note that both matrices, Cij and Kij, are symmetric, that is, Cij=Cji and Kij=Kji. You define the
twenty-one unique damping coefficients when you write the BEAMstatement. Adams defines the
Kij's in the following way:
K11 = E A / L
K22 = 12 E Izz /[L**3 (1+Py)]
K26 = -6 E Izz /[L**2 (1+Py)]
K33 = 12 E Iyy /[L**3 (1+Pz)]
K35 = 6 E Iyy /[L**2 (1+Pz)]
K44 = G Ixx / L
K55 = (4+Pz) E Iyy /[L (1+Pz)]
K66 = (4+Py) E Izz /[L (1+Py)]
where Py = 12 E Izz ASY/(G A L**2) and
Pz = 12 E Iyy ASZ/(G A L**2)
2. The BEAM statement implements a force in the same way the FIELD statementdoes, but the BEAM
statement requires you to input only the values of the beam'sphysical properties, which Adams uses
to calculate the matrix entries. For a forcerequest, the forces returned are the forces the J marker exerts
upon the I marker.
3. The constitutive equations shown above define the forces and moments exerted on the I marker.
These forces and moments are due to relative displacements andvelocities of the I marker with respect
to the J marker. Because of force transfer,the reaction moments at the J marker are usually not the
same as the appliedmoments at the I marker.
then you may over ride the default parent. In most cases, when creatingan entity, Adams View will
be assigned to it.
then you may over ride the default parent. In most cases, when creatingan entity, Adams View will
be assigned to it.
6. Specifies an integer used to identify this element in the Adams data file. When you use the FILE
Adams_DATA_SET WRITE command, Adams View writes an Adams data file for your model.
Adams requires that each modeling element be identified by a unique integer identifier. If you use
this parameter to specify a non-zero identifier,Adams View will use it in the corresponding statement
in the Adams data file. You may also enter zero as an identifier, either explicitly or by default. The
next time you write an Adams file, Adams View will replace the zero with a unique,
internallygenerated identifier. Adams View will permanently store this identifier with the element just
as if you had entered it yourself. Normally, you would let all identifiers default to zero, and Adams
8. The y_shear_area_ratio is a correction factor for shear deflection in the y direction for Timeshenko
beams. (Oden, J.T., and E. Ripperger. Mechanics of Elastic Structures, Second Edition, p. 351. New
York: McGraw-Hill, 1981). This ratio is the area of the beam cross section divided by the area of the
beam cross section that resists y-direction shear forces. If you want to neglect the deflection due toy-
direction shear, set the ratio to zero.
9. z_shear_area_ratio is the correction factor for shear deflection in the z direction for Timeshenko
beams. (Oden, J.T., and E. Ripperger. Mechanics of Elastic Structures, Second Edition, p. 351. New
York: McGraw-Hill, 1981). This ratio is the area of the beam cross section divided by the area of the
beam cross section that resists z-direction shear forces. If you want to neglect the deflection due to
directionshear, set the ratio to zero.
force 97
force modify element_like bushing
10. Specifies Young's modulus of elasticity for the beam material.

11. Because the matrix_of_damping_terms matrix is symmetric, you need to specify only one-half of it.
The following matrix shows the values to input:
[r01 ]
[r02 r07 ]
[r03 r08 r12 ]
[r04 r09 r13 r16 ]
[r05 r10 r14 r17 r19 ]
[r06 r11 r15 r18 r20 r21]
CMATRIX or CRATIO, CMATRIX defaults to a matrix with thirty-six zeroentries; that is, r1
through r21 each default to zero.
Cautions:
 Adams View will not allow you to have two beams with the same full name, so you must provide a
unique name.
Tips:

Allows you to modify of the bushing object.
Format:
bushing_name = existing bushing name
new_bushing_name = new bushing name
Adams_id = integer
comments = string
damping= damping coeff matrix
stiffness = stiffness coeff matrix
tdamping = tdamping coeff matrix
tstiffness = tstiffness coeff matrix
force_preload = force preload coeff matrix
torque_preload = toruqe preload coeff matrix
Example:
force modify element_like bushing &
bushing_name = BUSHING__1 &
new_bushing_name = BUSHING__2 &
Adams_id = 1 &
comments = comment &
damping = 0.1 , 0.2, 0.1 &
stiffness = 0.1, 0.2, 0.1 &
tdamping = 0.1 , 0.2 , 0.1 &
tstiffness = 0.1 , 0.2 , 0.1 &
force_preload = 0.1 , 0.2 , 0.1 &
torque_preload = 0.1 , 0.2 , 0.2 &
Description:

bushing_name An Existing Bushing Specifies the name of the existing bushing.
new_bushing_name A New Bushing Specifies the name of the new bushing.
Adams data file.
modified.
damping Damping Specifies three viscous damping coefficients for the
bushing force. The three coefficients multiply the
translational velocity components of the I marker along
the x-axis, the y-axis, and the z-axis of the J marker. The
force due to damping is zero when there is no relative
translational velocity between the two markers.
DAMPING must be in units of force per unit of
displacement per unit of time.
stiffness Stiffness Specifies three stiffness coefficients for the bushing force.
force_preload Force Specifies a vector of three constant terms for the bushing
force. These terms are the constant force components
along the x-axis, the y-axis, and the z-axis of the J marker.
tdamping Torsion_damp Specifies three viscous damping coefficients for the
bushing torque.
force 99

tstiffness Torsion_stiff Specifies three stiffness coefficients for the bushing torque.
The three coefficients multiply the three rotational
displacement components of the body in which the I
marker is fixed about the x-axis, the y-axis, and the z-axis
of the J marker.
torque_preload Torque Specifies a vector of three constant terms for the bushing
torque. These terms are the constant torque components
about the x-axis, the y-axis, and the z-axis of the J marker.
by this force element. Adams View connects this element
to one part at the I marker and to the other at the J marker.
1. The bushing is a massless force with linear stiffness and damping properties. A bushing applies a force
and a torque to two parts. You specify a marker on each part for force or torque application. Each
force consists of three components in the coordinate system of the J marker, one in the x-axis
direction, one in the y-axis direction, and one in the z-axis direction. Likewise each torque consists of
three components in the coordinate system of the J marker, one about the x-axis, one about the y-
axis, and one about the z-axis. The magnitude of the force is linearly dependent upon the relative
displacement and the relative velocity of the two markers. The magnitude of the torque is dependent
upon the relative angle of rotation and the relative rotational velocity of the parts containing the
specified markers.
2. A bushing has the same constitutive relation forms as a field. The primary difference between the two
forces is that certain coefficients (Kij and Cij, where i is not equal to j) are zero for the bushing. You
define only the diagonal coefficients (Kii and Cii) when you write the bushing. The following
constitutive equations define how Adams uses the data you input for a bushing to apply a force and
a torque to the I marker depending on the displacement and velocity of the I marker relative to the J
[Fx] [K11 0 0 0 0 0 ] [x]
[Fy] [0 K22 0 0 0 0 ] [y]
[Fz] = - [0 0 K33 0 0 0 ] [z]
[Tx] [0 0 0 K44 0 0 ] [a]
[Ty] [0 0 0 0 K55 0 ] [b]
[Tz] [0 0 0 0 0 K66] [c]
[C11 0 0 0 0 0 ] [Vx] [F1]
[0 C22 0 0 0 0 ] [Vy] [F2]
- [0 0 C33 0 0 0 ] [Vz] + [F3]
[0 0 0 C44 0 0 ] [Wx] [T1]
[0 0 0 0 C55 0 ] [Wy] [T2]
[0 0 0 0 0 C66] [Wz] [T3]
Fx, Fy, and Fz are the measure numbers of the translational force components parallel to the axes of
the Cartesian coordinate system of the J marker.
The terms x, y, and z are the translational displacements of the I marker with respect to the J marker
measured in the Cartesian coordinate system of the J marker. The terms Vx, Vy, and Vz are the time
derivatives of x, y, and z, respectively. The terms F1, F1, and F3 represent the measure numbers of
any constant force components parallel to the axes of the Cartesian coordinate system of the J marker.
3. . Tx, Ty, and Tz are the rotational force components parallel to the axes of the Cartesian coordinate
system of the J marker. The terms a, b, and c are the rotational displacements of the I marker about
the x-axis, the y-axis, and the zaxis, respectively, of the J marker. The terms Wx, Wy, and Wz are the
time derivatives of a, b, and c, respectively, in the J marker reference frame. The termsT1, T2, and
T3 are the measure numbers of any constant torque components acting parallel to the axes of the
Cartesian coordinate system of the J marker.
For the rotational constitutive equations (K1, K2, and K3), to be accurate, at least two of the rotations
(a, b, c) must be small. Therefore, the bushing force calculations may not be accurate unless two of
the three values remain small (that is, smaller than 10 degrees). It does not matter which rotation is
largest.
4. You may use this name later to refer to this bushing. Adams View will not allow you to have two
bushings with the same full 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 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. 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 over ride 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, or course, delete this name and use
your own. The form of a full name is:
be assigned to it.
force 101
force modify element_like field
7. The three stiffness coefficients multiply the three translational displacement components of the origin
of the I marker along the x-axis, the y-axis, and the z-axis of the J marker. STIFFNESS must be in
units of force per unit of displacement.
8. The three stiffness coefficients multiply the rotational velocity components of the body in which the
I marker is fixed about the x-axis, the y-axis, and the z-axis of the J marker. The torque due to
damping is zero when there is no relative rotational velocity between the two markers.
Cautions:
 Adams View will not allow you to have two bushings with the same full name, so you must provide
a unique name.

Allows you to modify of the field object.
Format:
field_name = model_1.field1
new_field_name = FIELD__1
Adams_id = 1
comments = comment1
i_marker_name = marker_1
translation_at_preload = matrix of 3 values
rotation_at_preload = matrix of 3 values
force_preload = matrix of 3 values
torque_preload = matrix of 3 values
stiffness_matrix = matrix of 6x6 values
damping_ratio = real_number
matrix_of_damping_terms = 6x6 matrix of real values
user_function = real number
Example:
force modify element_like field &
field_name = model_1.field1 &
new_field_name = FIELD__1 &
Adams_id = 1 &
comments = comment1 &
translation_at_preload = 0.5, 0.2, 0.5 &
rotation_at_preload = 0.5, 0.2, 0.4 &
force_preload = 0.2, 0.1, 0.5 &
torque_preload = 0.4, 0.1, 0.8
Description:

field_name An Existing Field Specifies the field to modify. You use this parameter to
identify the existing field to affect with this command.
new_field_name A New Field Specifies the name of the new field. You may use this
name later to refer to this field.
Adams data file.
modified.
i_marker_name An Existing Specifies a marker on the first of two parts connected by
Marker this force element. Adams View connects this element to
j_marker_name An Existing Specifies a marker on the second of two parts connected
Marker by this force element. Adams View connects this element
marker.
translation_at_preload Length Defines a vector of reference translations.
rotation_at_preload Angle Defines a vector of reference rotations.
force_preload Force Specifies a vector of three constant terms for the bushing
force. These terms are the constant force components
along the x-axis, the y-axis, and the z-axis of the J marker.
force 103

torque_preload Torque Defines a vector of reference torques at the angular
displacement specified in the parameter
ROTATION_AT_PRELOAD. The values r1, r2, r3 are
the torque components about the x-axis, the y-axis, and
the z axis of the J marker.
stiffness_matrix Real Specifies a six-by-six matrix of stiffness coefficients.
damping_ratio Real Specifies the ratio of MATRIX_OF_DAMPING to
STIFFNESS_MATRIX. If you input
DAMPING_RATIO, Adams multiplies
STIFFNESS_MATRIX by this parameter to obtain
MATRIX_OF_DAMPING_TERMS.
matrix_of_damping_ter Real Specifies a six-by-six matrix of viscous damping
ms coefficients.
user_function Real Specifies up to 30 values for Adams to pass to a user
FORMULATION By default, the LINEAR option is used. The LINEAR
option matches the behavior of previous releases. The
NONLINEAR option forces Adams Solver to add a
geometric stiffness term; this option is useful if the
FIELD is being used to model beams.
Default: LINEAR
LENGTH_TOL When using FORMULATION=NONLINEAR, the
geometric stiffness uses the larger of the current length
and length tolerance.
Default: 1.e-05
1. A field is a translational and a rotational action-reaction force applied between two markers. If you
want to specify a linear field, use the arguments in the command to specify constants for the six-by-
six stiffness matrix, a six-element reference length vector, and a six-by-six damping matrix. The
stiffness and damping matrices must be positive semi definite, but need not be symmetric. If you want
to specify a nonlinear field, use the Adams user-written subroutine FIESUB to define the three force
components and the three torque components and use the Adams View parameter
USER_FUNCTION=r1[,...,r30] to pass constants to FIESUB. The following constitutive equations
define how Adams uses the data you input for a linear field to apply a force and a torque to the I
marker depending on the displacement and velocity of the I marker relative to the J marker. Adams
applies a force of equal magnitude and opposite direction to the J marker. The torque on the J marker
has two components. The first component is equal and opposite to the torque on the I marker. The
second component is due to the couple generated by the equal and opposite forces acting at the I and
J markers.
[Fx] [K11 K12 K13 K14 K15 K16] [x-xo]
[Fy] [K21 K22 K23 K24 K25 K26] [y-yo]
[Fz] = - [K31 K32 K33 K34 K35 K36] [z-zo]
[Tx] [K41 K42 K43 K44 K45 K46] [a-ao]
[Ty] [K51 K52 K53 K54 K55 K56] [b-bo]
[Tz] [K61 K62 K63 K64 K65 K66] [c-co]
[C11 C12 C13 C14 C15 C16] [Vx] [F1]
[C21 C22 C23 C24 C25 C26] [Vy] [F2]
- [C31 C32 C33 C34 C35 C36] [Vz] + [F3]
[C41 C42 C43 C44 C45 C46] [Wx] [T1]
[C51 C52 C53 C54 C55 C56] [Wy] [T2]
[C61 C62 C63 C64 C65 C66] [Wz] [T3]
For a nonlinear field, you define the following constitutive equations in the FIESUB
subroutine:
Fx = f (x,y,z,a,b,c,Vx,Vy,Vz,Wx,Wy,Wz)
1
Fy = f (x,y,z,a,b,c,Vx,Vy,Vz,Wx,Wy,Wz)
2
Fz = f (x,y,z,a,b,c,Vx,Vy,Vz,Wx,Wy,Wz)
3
Tx = f (x,y,z,a,b,c,Vx,Vy,Vz,Wx,Wy,Wz)
4
Ty = f (x,y,z,a,b,c,Vx,Vy,Vz,Wx,Wy,Wz)
5
Tz = f (x,y,z,a,b,c,Vx,Vy,Vz,Wx,Wy,Wz)
6
Adams applies the defined forces and torques at the I marker. In the linear and the nonlinear
equations, Fx, Fy, and Fz are the three translational force measure numbers, and Tx, Ty, and Tz are
the three rotational force measure numbers associated with unit vectors directed along the x-axis, the
y-axis, and the z-axis of the coordinte system fixed in the J marker reference frame; K is the stiffness
matrix; xo,yo, zo, ao, bo, and co are the free lengths; x, y, z, a, b, and c are the translational and the
rotational displacements of the I marker with respect to the J marker expressed in the reference frame
of the J marker; Vx, Vy, Vz, Wx, Wy, and Wz are the scalar time derivatives of x, y, z, a, b, and c,
respectively; C is the damping matrix; and F1, F2, F3, T1, T2, and T3 are the translational and the
rotational pre-tensions. All variables and time derivatives are computed in the J marker coordinate
system.
2. You may identify a field by typing its name or by picking it from the screen.
If the field is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the field is displayed. If you created the field by reading an Adams data set file,
the field name is 'FIE'. If you created the field during preprocessing, you gave it a name at that time.
If a field is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a field under a different model, for instance, you may need to enter
the model name as well. For example, you may specify field 'fld1' from model 'robot' by entering
force 105
".robot.fld1". If you type a "?", Adams View will list the fields available by default. You must separate
multiple field names by commas. If the field is visible in one of your views, you may identify it by
picking on any of the graphics associated with it. You need not separate multiple field picks by
commas..
be assigned to it.
6. The ‘translation_at-preload’ parameter defines a vector of reference translations. This is the nominal
position of the I marker with respect to the J marker, resolved in the J marker coordinate system. The
values r1, r2, r3 are the x, y, and z translational components of the translation. Adams uses the
translational distance specified in TRANSLATION_AT_PRELOAD to calculate the resultant
torque on the J marker. If the reference force is zero, TRANSLATION_AT_PRELOAD is the same
as the free translation.
7. The rotation_at_preload parameter defines a vector of reference rotations. This defines the nominal
orientation of the I marker with respect to the J marker, resolved in the J marker coordinate system.
The terms r1, r2, r3 the x, y, and z rotational components. Adams uses the angular displacements
specified in ROTATION_AT_PRELOAD to calculate the resultant torque on the J marker. If the
reference force is zero, ROTATION_AT_PRELOAD is the same as the free rotation.entries.
force modify element_like friction
8. The stiffness_matrix parameter specifies a six-by-six matrix of stiffness coefficients. The following
matrix shows the values to input:
[r01 r07 r13 r19 r25 r31]
[r02 r08 r14 r20 r26 r32]
[r03 r09 r15 r21 r27 r33]
[r04 r10 r16 r22 r28 r34]
[r05 r11 r17 r23 r29 r35]
[r06 r12 r18 r24 r30 r36]
Enter the elements by columns from top to bottom, then from left to right. If you do not use both
CRATIO and KMATRIX, Adams cannot calculate the damping coefficients; in that case, you must
define CMATRIX if you want to include damping coefficients in the calculation of the field forces.
KMATRIX defaults to a matrix with thirtysix zero entries.
9. The matrix_of_damping_terms parameter specifies a six-by-six matrix of viscous damping
coefficients. The following matrix shows the values to input:
[r01 r07 r13 r19 r25 r31]
[r02 r08 r14 r20 r26 r32]
[r03 r09 r15 r21r27 r33]
[r04 r10 r16 r22 r28 r34]
[r05 r11 r17 r23 r29 r35]
[r06 r12 r18 r24 r30 r36]
CMATRIX or both CRATIO and KMATRIX, CMATRIX defaults to a matrix with thirty-six zero
entries.
Cautions:
1. Adams View will not allow you to have two fields with the same full name, so you must provide a
unique name.
2. Do not use the ‘damping_ratio’ parameter without also using STIFFNESS_MATRIX.
Tips:

Format:
Friction_name = existing friction name
New_friction_name = new friction name
Adams_id = geom._id
Comments = string
Joint_name = existing joint
force 107

Yoke = i_yoke/j_yoke
Mu_static = real
Mu_dynamic = real
Reaction_arm = real
Friction_arm = real
Initial_overlap = real
Pin_radius = real
Ball_radius = real
Bending_factor = real
max_stiction_deformation= real
friction_force_preload= real
max_friction_force = real
max_friction_torque = real
transition_velocity_coefficient = real
overlap_delta = INCREASE/ DECREASE/ CONSTANT
effect = ALL/ STICTION/ SLIDING
smooth = real
torsional_moment = on/off
bending_moment = on/off
preload= on/off
reaction_force = on/off
Description:

friction_name An existing friction name
New_friction_name New friction name
Adams_id Adams_id Specifies an integer used to identify this

joint_name Existing joint name Specifies the translational, revolute, or
cylindrical joint associated with this entity.
Some entities constrain motion at, or are
otherwise associated with, specific joints. You
use this parameter to identify that joint.
yoke I_yoke/J_yoke
mu_static Real Specify a real number greater than zero.
mu_dynamic Real Specify a real number greater than zero.
reaction_arm Real Specify a real number greater than zero.
friction_arm Real Specify a real number greater than zero.
initial_overlap Real
pin_radius Real Specify a real number greater than zero.
ball_radius Real Specify a real number greater than zero.
bending_factor Real Specifies a real number greater than zero.
stiction_transition_veloci Real Specify a real number greater than zero.
ty
max_stiction_deformatio Real Specify a real number greater than zero.
n
friction_force_preload Real Specify a real number greater than or equal to
zero.
friction_torque_preload Real Specify a real number greater than or equal to
zero.
max_friction_force Real Specify a real number greater than zero.
max_friction_torque Real Specify a real number greater than zero.
transition_velocity_coeffi Real Specify a real number greater than zero.
cient
overlap_delta INCREASE, DECREASE, Can take the values INCREASE,
CONSTANT DECREASE, CONSTANT
effect ALL, STICTION, SLIDING Specify the friction effect required.
Smooth Real
torsional_moment On/off
bending_moment On/off
preload On/off
reaction_force On/off
force 109
force modify element_like rotational_spring_damper
associated with it.

Allows modification of the rotational spring damper object.
Format:
spring_damper_name = existing spring damper force
new_spring_damper_name = new spring damper force
Adams_id = integer
comments = string
damping = real number
stiffness = real number
preload = real number
displacement_at_preload = real number
Example:
force modify element_like rotational_spring_damper &
spring_damper_name = SPRING_1 &
new_spring_damper_name = SPRING_2 &
Adams_id = 2 &
damping = 0.5 &
stiffness = 0.2 &
preload = 1.2 &
displacement_at_preload = 0.02 &
force 111
Description:

spring_damper_name An Existing Spring-damper Specifies the spring-damper force to
Force modify. You use this parameter to identify
the existing spring-damper to affect with
this command. You may identify a spring-
damper force by typing its name or by
picking it from the screen.
new_spring_damper_name A New Spring-damper Force Specifies the name of the new spring-
damper force. You may use this name later
to refer to this spring-damper.Adams View
will not allow you to have two spring-
dampers with the same full name, so you
Adams_id Integer Specifies an integer used to identify this
damping Damping Specifies the viscous damping coefficient
for the spring damper.
stiffness Stiffness Specifies the spring stiffness coefficient for
the spring damper.
preload Force Specifies the reference force or torque for
the spring. This is the force the spring exerts
when the displacement between the I and J
markers is equal to
DISPLACEMENT_AT_PRELOAD (the
reference length of the spring).

displacement_at_preload Length Specifies the reference length for the spring.
If PRELOAD (the reference force of the
spring) is zero,
DISPLACEMENT_AT_PRELOAD
equals the free length
connected by this force element. Adams
View connects this element to one part at
the I marker and to the other at the J
marker.
j_marker_name An Existing Marker Specifies a marker on the second of two
parts connected by this force element.
Adams View connects this element to one
part at the I marker and to the other at the
J marker.
1. The springdamper force applies a rotational or a translational spring-damperbetween two markers.
For a rotational spring-damper, the z-axis of the I markerand the z-axis of the J marker must be
parallel and must point in the samedirection. Because the spring- damper force is always an action-
reaction force, thedirection of the translational force is the line of sight between the I and the
Jmarkers. Thus, if the force is positive, the markers experience a repelling forcealong this line, and if
the force is negative, the markers experience an attractingforce. The magnitude of the translational
force applied to the parts containing thetwo markers is linearly dependent upon the relative
displacement and velocity ofthe two markers. The following linear constitutive equation describes the
forceapplied at the I marker:
2. Adams automatically computes the terms db/dt and b. The force value is the force on the I marker
from the J marker; the force on the J marker is equal and opposite. The term b is the distance between
the I and the J markers. Adams assumes that b is always greater than zero. The following linear
constitutive equation describes the torque applied at the I marker:
3. Adams automatically computes the terms da/dt and a. The torque is applied to the I marker about
the positive z-axis of the I marker; the torque on the J marker isequal and opposite to the torque on
the I marker. The right-hand rule defines apositive torque. The term a is the angle between the x-axes
of the I and the Jmarkers. Adams takes into account the total number of complete turns.
Considerations:
If the z-axis of the I marker is not parallel to, and/or not pointed in the samedirection as, the z-axis
of the J marker for a rotational spring-damper, theresults are unpredictable.
force 113
Since the line-of-sight method determines the direction of a translationalspring-damper force, the I
and the J markers cannot be coincident.
4. You may identify a spring-damper force by typing its name or by picking it from the screen. If the
spring-damper force is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the spring-damper is displayed. If you created the spring-damper
force by reading an Adams data set, the spring-damper name is the letters SPR followed by the Adams
data set spring-damper ID number. The name of Adams SPRINGDAMPER/101 is SPR101, for
example. If you created the spring-damper during preprocessing, you gave it a name at that time. If a
spring-damper is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a spring-damper under a different model, for instance, you may
need to enter the model name as well. For example, you may specify spring-damper 'left' from model
'sla' by entering ".sla.left". You must separate multiple spring-damper names by commas. If the
spring-damper is visible in one of your views, you may identify it by picking on any of the graphics
associated with it. You need not separate multiple spring-damper picks by commas.
be assigned to it.
identifier. If you use this parameter to specify a non-zero identifier,Adams View will use it in the
a unique, internallygenerated identifier. Adams View will permanently store this identifier with the
force modify element_like translational_spring_damper
Tips:
 If you type a "?", Adams View will list the spring-dampers available by default.

Allows modification of the translational spring damper object.
Format:
spring_damper_name = existing spring damper force
new_spring_damper_name = new spring damper force
Adams_id = integer
comments = string
damping = real number
stiffness = real number
preload = real number
displacement_at_preload = real number
Example:
Force modify element_like translational_spring_damper &
spring_damper_name = SPRING_1 &
new_spring_damper_name = SPRING_2 &
Adams_id = 2 &
damping = 0.5 &
stiffness = 0.2 &
preload = 1.2 &
displacement_at_preload = 0.02 &
force 115
Description:

spring_damper_name An Existing Specifies the spring-damper force to modify. You use this
Spring-damper parameter to identify the existing spring-damper to affect
Force with this command.
new_spring_damper_name A New Spring- Specifies the name of the new spring-damper force. You
damper Force may use this name later to refer to this spring-damper.
Adams View will not allow you to have two spring-

dampers with the same full name, so you must provide a
unique name.
Adams data file.
modified.
damping Damping Specifies the viscous damping coefficient for the spring
damper.
stiffness Stiffness Specifies the spring stiffness coefficient for the spring
damper.
preload Force Specifies the reference force or torque for the spring. This
is the force the spring exerts when the displacement
between the I and J markers is equal
toDISPLACEMENT_AT_PRELOAD (the reference
length of the spring).
displacement_at_preload Length Specifies the reference length for the spring. If
PRELOAD (the reference force of the spring) is zero,
DISPLACEMENT_AT_PRELOAD equals the free
length
i_marker_name An Existing Specifies a marker on the first of two parts connected by
Marker this force element. Adams View connects this element to
j_marker_name An Existing Specifies a marker on the second of two parts connected
Marker by this force element. Adams View connects this element
marker.
1. The spring damper force applies a rotational or a translational spring-damper between two markers.
For a rotational spring-damper, the z-axis of the I marker and the z-axis of the J marker must be
parallel and must point in the same direction. Because the spring- damper force is always an action-
reaction force, the direction of the translational force is the line of sight between the I and the J
markers. Thus, if the force is positive, the markers experience a repelling force along this line, and if
the force is negative, the markers experience an attracting force. The magnitude of the translational
force applied to the parts containing the two markers is linearly dependent upon the relative
displacement and velocity of the two markers. The following linear constitutive equation describes
the force applied at the I marker:
2. Adams automatically computes the terms db/dt and b. The force value is the force on the I marker
from the J marker; the force on the J marker is equal and opposite. The term b is the distance between
the I and the J markers. Adams assumes that b is always greater than zero. The following linear
constitutive equation describes the torque applied at the I marker:
3. Adams automatically computes the terms da/dt and a. The torque is applied to the I marker about
the positive z-axis of the I marker; the torque on the J marker is equal and opposite to the torque on
the I marker. The right-hand rule defines a positive torque. The term a is the angle between the x-
axes of the I and the J markers. Adams takes into account the total number of complete
turns.Considerations:
• If the z-axis of the I marker is not parallel to, and/or not pointed in the same direction as, the z-axis
of the J marker for a rotational spring-damper, the results are unpredictable.
• Since the line-of-sight method determines the direction of a translational spring-damper force, the
I and the J markers cannot be coincident.
4. You may identify a spring-damper force by typing its name or by picking it from the screen. If the
spring-damper force is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the spring-damper is displayed. If you created the spring-damper
force by reading an Adams data set, the spring-damper name is the letters SPR followed by the Adams
data set spring-damper ID number. The name of Adams SPRINGDAMPER/101 is SPR101, for
example. If you created the spring-damper during preprocessing, you gave it a name at that time. If a
spring-damper is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a spring-damper under a different model, for instance, you may
need to enter the model name as well. For example, you may specify spring-damper 'left' from model
'sla' by entering ".sla.left". You must separate multiple spring-damper names by commas. If the
spring-damper is visible in one of your views, you may identify it by picking on any of the graphics
associated with it. You need not separate multiple spring-damper picks by commas.
force 117
force modify fe_load
be assigned to it.
identifier. If you use this parameter to specify a non-zero identifier,Adams View will use it in the
a unique, internallygenerated identifier. Adams View will permanently store this identifier with the
Tips:
 If you type a "?", Adams View will list the spring-dampers available by default.

Allows you to modify an entity of the type fe_load in the Adams session. An fe_load defines a distributed load
acting on an existing fe_part.
Format:
force modify direct fe_load
feload_name = new fe_load name
ref_fe_part = refer existing fe_part
ref_orientation_marker = refer existing marker
fx = function expression
fy = function expression
fz = function expression
tx = function expression
ty = function expression
tz = function expression
user_function = function expression
routine = string
force_display = ON / OFF
Example:
force modify direct fe_load
feload_name = .MODEL_1.FE_Load_1
ref_fe_part = FE_Part_1
ref_orientation_marker = MARKER_1
adams_id = 1
fx = SD(1)
fy = SD(1)
fz = SD(1)
tx = SD(1)
ty = SD(1)
tz = SD(1)
force_display = ON
Description:

feload_name New fe_load Specifies the name of the fe_load to be modified.
ref_fe_part Existing fe_part Specifies the already created fe_part on which the fe_load
will act.
ref_orientation_marker Existing marker Specifies the already created marker which defines the
orientation of the fe_load.
fx
fy
fz
force 119

tx
ty
tz
user_function String Specifies up to 30 values for Adams to pass to a user written
routine String
force_display String
function 1
function create
function
function create
A function allows you to define a new function in terms of an Adams View expression. The function create
command allows you to create a function. You may reverse this creation at a later time with an UNDO
command.
Format:
function create
function_name = new expr_function
text_of_expression = string
argument_names = string
type = result_type
comments = string
category = func_category
Example:
As a simple example, we write a function which adds two numbers together
function create function_name=SUM argument_names=x,y &
text_of_expression="x + y"
Now we use this function to compute the sum of two numbers:
marker create marker=mar1 location=(SUM(1, 2)), 0, 0
If we examine the location of the marker mar1 we find that its location is 3,0,0 as expected.
Here we have a little more sophisticated example which computes the distance between two points:
function create function_name=DISTANCE argument_names=p1, p2 &
text_of_expression="sqrt((p1[1]-p2[1])**2 + (p1[2]-p2[2])**2 +
(p1[3]-p2[3])**2)"
You could then use the distance function in any appropriate context (assuming the existence of a model
containing par1 and par2).
variable create variable=dist1 real=(DISTANCE(par1.location,
par2.location))
function create
Description:

function_name New Expr_function Specifies the name of the user-written function
you are creating or modifying. You should choose
a name which is meaningfully related to the
operation that the function is performing.
text_of_expression String The TEXT_OF_EXPRESSION parameter
defines the computation to be performed by the
function.
argument_names String The ARGUMENT_NAMES parameter allows
you to specify the names of the formal arguments
in your function.
type Array, Integer, The TYPE parameter of a function indicates the
Location_orientation, Object, type of the returned value.
Real, String
comments String Allows you to add comments to the function for
documentation purposes. The strings are stored in
the database and written to command files.
category User, String, Math, Modelling, Specifies which category this function should be
Loc_ori, classified under.
Matrix_array,database_object,
Misc
1. Remember that the value of the argument “text_of_expression” should be a character string, NOT
an expression.
FUNCTION CREATE FUNCTION_NAME=SSQDIF &
ARGUMENT_NAMES=Array1, Array2 &
TEXT_OF_EXPRESSION="SSQ(Array1-Array2)" &
COMMENT_STRING="Compute sum of squares of differences between
arguments" &
TYPE=real
2. The argument_names you specify are associated by position with the actual arguments when you
invoke the function, using the following as an example:
FUNCTION CREATE FUNCTION_NAME=MyFunc ARGUMENT_NAMES=Arg1, Fred &
TEXT_OF_EXPRESSION="sqrt(Fred) * Arg1"
VARIABLE CREATE VARIABLE_NAME=TestVariable &
REAL_VALUE=(MyFunc(1+1, 9) + 4)
The first formal argument "Arg1" is associated with the value 2 (computed from 1+1); the second
argument, "Fred", is associated with the value 9. The resulting value for "TestVariable" is sqrt(9) * 2
+ 4 = 10.
function 3
function delete
function delete
Allows you to delete an existing function.
You must enter the name of the function you wish to delete by specifying the full name.
Format:
function delete
function_name = existing expr_function
Example:
If function get_name already exists
function delete &

function_name = get_name
This will delete the function get_name.
Description:

Function_name Existing Expr_function FUNCTION_NAME is a required parameter, in which
you specify the name of the user-written function you are
deleting.
function modify
A function allows you to define a new function in terms of an Adams View expression. The function modify
command allows you to modify an existing user written function.
You may reverse this modification at a later time with an UNDO command.
Format:
function modify
function_name = existing expr_function
new_function_name = new expr_function
argument_names = string
type = result_type
function modify
function modify
comments = string
category = func_category
Example:
! Already have a function named "This"

VARIABLE CREATE VARIABLE_NAME=Example REAL_VALUE=(This(1))
FUNCTION MODIFY FUNCTION_NAME=This NEW_FUNCTION_NAME=That
LIST_INFO VARIABLE VARIABLE_NAME=Example
! You will see that the real value is (That(1))
Description:

function_name, Existing Expr_function Specifies the name of the user-written function you
are modifying. You should choose a name which is
meaningfully related to the operation that the
function is performing.
New_function_name New Expr_function Allows you to change the name of an already existing
function. When you change the function's name, all
references to it also change.
text_of_expression, String The TEXT_OF_EXPRESSION parameter defines
the computation to be performed by the function.
argument_names String The ARGUMENT_NAMES parameter allows you
to specify the names of the formal arguments in your
function.
type Array, Integer, The TYPE parameter of a function indicates the type
Location_orientation, of the returned value.
Object, Real, String
omments String The COMMENTS parameter allows you to add
comments to the function for documentation
purposes. The strings are stored in the database and
written to command files.
category User, String, Math, Specifies which category this function should be
Modelling, Loc_ori, classified under.
Matrix_array,
Database_object, Misc
function 5
function modify
1. Remember that the value of the argument “text_of_expression” should be a character string, NOT
an expression.
FUNCTION CREATE FUNCTION_NAME=SSQDIF &
ARGUMENT_NAMES=Array1, Array2 &
TEXT_OF_EXPRESSION="SSQ(Array1-Array2)" &
COMMENT_STRING="Compute sum of squares of differences between
arguments" &
TYPE=real
2. The argument_names you specify are associated by position with the actual arguments when you
invoke the function.
Using the following as an example:
FUNCTION CREATE FUNCTION_NAME=MyFunc ARGUMENT_NAMES=Arg1, Fred &
TEXT_OF_EXPRESSION="sqrt(Fred) * Arg1"
VARIABLE CREATE VARIABLE_NAME=TestVariable &
REAL_VALUE=(MyFunc(1+1, 9) + 4)
The first formal argument "Arg1" is associated with the value 2 (computed from 1+1); the second
argument "Fred" is associated with the value 9. The resulting value for "TestVariable" is sqrt(9) * 2
+ 4 = 10.
function modify
geometry 1
geometry attributes
geometry
geometry attributes
Allows the specification of attributes to be set on individual pieces of geometry or a group of geometry.
Format:
geometry attributes
render_mode = render_mode
Example:
geometry attributes &
geometry attributes geometry_name = link_56 &
geometry attributes visibility = on &
geometry attributes transparency = 20 &
geometry attributes color = black &
geometry attributes render_mode = filled
Description:

geometry_name An Existing Geometric Entity Specifies the geometry to modify.
color An Existing Color Specifies the color the modeling entity should be
drawn in.
entity_scope Color_scope The ENTITY_SCOPE parameter is used to
control how a color modification is to affect a
particular graphic entity.
geometry attributes

render_mode Render_mode This command specifies the rendering mode of
individual or groups of graphic objects
active On_off_no_opinion When you set ACTIVE=NO, that element is
written to the data set as a comment
dependents_active On_off_no_opinion When you set ACTIVE=NO, that element is
1. You can set the following attributes on a marker.
- VISIBILITY. You may set an individual geometric entity's visibility ON, OFF or TOGGLE the
current setting. When you set a piece of geometry's visibility OFF, the geometry will not be drawn.
When you set a piece of geometry's visibility ON, you allow that geometry to be drawn.
- COLOR. You may set the color of a piece of geometry with this parameter.
- ENTITY_SCOPE. This parameter is used in conjunction with COLOR, to limit the application
of the color.
- RENDER_MODE. You may choose a rendering mode for geometry. When you choose a
render_mode of FILLED, the geometry chosen can be displayed as shaded, filled or in wireframe;
depending on the render_mode of the view in which it is displayed. When you choose
WIREFRAME, you limit the rendering of this piece of geometry to only wireframe.
INHERITANCE may be either TOP_DOWN or BOTTOM_UP.
2. You use this parameter to identify the existing geometry to affect with this command.
You may identify geometry by typing its name or by picking it from the screen.
If the geometry is not visible on the screen, you must type the name. You may also find it convenient
to type the name even if the geometry is displayed.
If geometry is available by default, you may identify it by entering its name only. If it is not, you must
default.
geometry 3
geometry attributes
associated with it.
Example 1:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
ALL.
of the facets (or areas filled by the FILL_COLOR) of a graphic that can be shaded. The
OUTLINE_COLOR represents the color of the lines that make up those graphics that can not be
shaded or filled, like an outline graphic statement consisting of two points or the coil of a
springdamper. Finally, the ALL value indicates that all three entity types, FILL_COLOR,
EDGE_COLOR, and OUTLINE_COLOR will be affected by the color change.
6. The render mode is an attribute that is attached to each of the specific graphic entities and works in
tandem with a view's RENDER attribute (see below).
Graphic objects that can have their rendering mode altered include:
arcs, outlines, boxes, circles, cylinders, frustums, and spring damper graphics.
geometry attributes
The selection of graphic objects can be based on association to a particular analysis, part, or by
individual graphic name. When the rendering mode of a part is specified, all graphic objects fixed to
that part are drawn with the rendering mode of the part. Graphics that span parts can only be selected
by graphic name.
Adams View supports WIREFRAME and FILLED rendering modes.
This command should not be confused with the VIEW MANAGEMENT... RENDER parameter.
The RENDER parameter in view control sets an attribute associated with a particular view. So, if the
view render mode is wireframe, all the graphics will be drawn in wireframe mode regardless of the
value of a specific graphic object's render mode attribute. However, if the view render mode is set to
SOLIDS or SHADED, then a specific graphic entity will be drawn in the mode specified by the
DISPLAY_ATTRIBUTES RENDER_MODE command. In other words, the view RENDER
parameter is an attribute of the view and the display_attribute render mode is an attribute of the
specific graphic element. Or, WIREFRAME is the dominant mode and regardless of how it is set
(either RENDER by view or RENDERING_MODE by graphic object).
following command:
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
geometry 5
geometry copy
following command:
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
Cautions:
 You need not separate multiple geometry picks by commas.
Tips:
 The ENTITY_SCOPE parameter is optional and if not entered, will be set to FILL_COLOR.
geometry copy
Allows you to create replica geometry.
Format:
geometry copy
new_geometry_name = a new geometric entity
geometry copy
Example:
geometry copy &
geometry_name = link_56
Description:

geometry_name An Existing Geometric Entity Specifies an existing geometry.
new_geometry_name A New Geometric Entity Specifies the name of the new geometry
1. This replica geometry will be identical to the original with the exception of the geometry name.
Geometry must have unique names relative to other geometry in a given model. The replica will be
completely independent of the original, and may be modified without effecting the original.
The replica geometry will have replica markers created for it. The replica markers will be copies of the
markers on the original geometry object.
Dynamic geometry objects (springdampers, gforces, and outlines whose markers span multiple parts)
may not be copied from model to model.
default.
associated with it.
3. Specifies the name of the new geometry. You may use this name later to refer to this geometry.
Adams View will not allow you to have two pieces of geometry with the same full name, so you must
geometry 7
geometry create curve arc
Cautions:
Tips:
1. The number of levels used varies from case to case and the parentage must exist before an entity can
be assigned to it.

Allows for creation of the arc object.
Format:
arc_name = a new arc
adams_id = adams_id
comments = string
center_marker = an existing marker
angle_extent = angle
radius = length
ref_radius_by_marker = an existing marker
close = arc_closure
Example:
geometry create curve arc &
arc_name = arc__1 &
adams_id = 2 &
comments = "a new arc" &
center_marker = origin &
angle_extent = 150 &
geometry create curve arc &

radius = 10 &
segment_count = 10 &
close = sector
Description:

arc_name A New Arc Specifies the name of the new arc.
Adams data file.
center_marker An Existing Marker Specifies the marker at the center of a circle, an arc, the
bottom of a cylinder, or the bottom of a frustum.
angle_extent Angle Specifies a subtended angle measured positive (according to
the right-hand rule) about the z-axis of the center marker
radius Length Specifies the radius of a circle, an arc, or a cylinder.
ref_radius_by_marker An Existing Marker Specifies the radius of a circle, an arc, or a cylinder to be the
distance from the center marker Z axis to this radius marker.
segment_count Integer Specifies the number of straight line segments Adams View
uses to draw a circle or an arc.
close Arc_closure Specifies the type of closure to perform when Adams View
creates the arc.
1. Arcs are truncated circles that can be closed into a pie shape or using a cord between the end points.
An arc is a 2 dimensional graphics image which is defined as a curve with a specified radius drawn
around a center marker. The length of the arc is determined by the angle_extent, and its smoothness
by the number of segments in the arc. The radius can be given explicitly by using the 'RADIUS='
parameter, or by using the 'ref_radius_by_marker' parameter, If 'REF_RADIUS_BY_MARKER' is
used, a radius will be calculated from the center marker. An arc will move with the center marker
given in the parameter 'CENTER_MARKER'.
2. You may use this name later to refer to this arc. Adams View will not allow you to have two arcs
with the same full name, so you must provide a unique name.
geometry 9
be assigned to it.
4. If you are creating a circle or an arc, orient the center marker so that its z-axis is normal to the plane
of the circle or to the plane of the arc. Similarly, if you are defining a cylinder or a frustum, orient
the center marker so that its z-axis is normal to the bottom of the cylinder or the frustum.
5. The angle starts at the positive x-axis of the center marker and subtends the arc, the arc of the cylinder,
or the arc of the cone frustum.
6. When you specify 'NO' for the ‘close’ parameter, Adams View will create a 2 dimensional arc. 'NO'
is the default value. When you specify 'CHORD' for this parameter, Adams View will close the arc
from the starting point, to the ending point on the arc.
When you specify 'SECTOR' for this parameter, Adams View will close the arc, such that a "pie"
shape is created.
Cautions:
1. Adams View stores the radius value, not the marker name. If you later move the marker specified by
the ref_radius_by_marker, the radius will not change.
geometry create curve bspline

Allows you to create a bspline.
Format:
bspline_name = a new gcurve
adams_id = adams_id
comments = string
ref_curve_name = an existing acurve
ref_marker_name = an existing marker
ref_profile_name = an existing Wire_Geometry
spread_points = boolean
closed = boolean
num_new_pts = integer
Examples:
geometry create curve bspline &
bspline_name = gcurve__1 &
adams_id = 100 &
comments = "a new bspline" &
ref_marker_name = origin &
ref_curve_name = curve__1 &
segment_count = 100
geometry create curve bspline &

adams_id = 100 &
comments = "a new bspline" &
ref_profile_name = CHAIN_1 &
closed = yes &
num_new_pts = 150
geometry 11
Description:

bspline_name A New Gcurve Specifies the name of the new BSPLINE.
data file.
ref_curve_name An Existing Specifies an existing CURVE that will be used to create and
Acurve display the BSPLINE geometric element.
ref_profile_name An Existing Wire Specifies an existing GWire geometry, from which to create and
Geometry display the BSPLINE geometric element.
ref_marker_name An Existing Specifies an existing MARKER that will be used to locate and
Marker orient the BSPLINE geometric element.
spread_points Boolean Specifies whether the bspline be created in a way that the points
(as defined by a reference profile) are equally spaced or
otherwise. The parameter will be ignored if a ref_curve_name is
specified.
closed Boolean Specifies whether that the generated bspline is a closed one or
otherwise.
num_new_pts Integer Specifies the number of points on the created bspline. The
parameter is valid only if the spread_points parameter is set to
'yes' (and as such can be valid only when a reference profile is
specified).
segment_count Integer Specifies the number of polynomial segments Adams View uses
for fitting the CURVE_POINTS when FIT_TYPE is set to
CURVE_POINTS.
1. To create a BSPLINE you must first create a CURVE DATA_ELEMENT or specify an existing
GWire geometry. The CURVE definition depends on first creating a MATRIX of control points or
a user-subroutine.
A BSPLINE is the geometric counterpart to the CURVE data_element. The difference being that
the BSPLINE is displayed with the Adams View model and the CURVE is not. The BSPLINE
references a CURVE for its definition and a REF_MARKER for it position. A single CURVE can be
referenced by multiple BSPLINEs.
For completeness the CURVE definition is repeated below.
A CURVE element defines a three-dimensional parametric curve that may be referenced by

parameter, u. As u varies from its minimum value to its maximum value, the functions x(u), y(u), and
z(u) sweep out points on the curve. A simple example of a parametric curve is the helix defined by the
following equations:
x = cos(u)
y = sin(u)
z = u
Adams View allows you to create curves in three ways: by entering control points for a uniform cubic
A uniform B-spline is a piecewise cubic polynomial spline used in many CAD (computer-aided-
ending at +1.
A more direct way to define the curve is to supply curve points. Adams will compute a uniform B-
spline that will fit the curve points. Again, Adams parameterizes the curve from -1 to +1. If you specify
the number of spline segments (SEGMENT_COUNT) as three less than the number of curve points,
the computed curve will exactly match the curve points. If you specify fewer segments, Adams will
use a least-squares fit to compute the closest fit to the points. In general, fewer segments give a
smoother curve, but do not come as close to the data points.
In order to use a different type of curve, or to model an analytically-defined curve such as the helix,
A curve can be open or closed. A CLOSED curve meets at the ends, connecting the curve at minimum
and maximum parameter values. Note for a closed curve defined by curve points, you can specify a
maximum of 5 segments less that the number of curve points. Note that because three segments less
than the number of curve points are required for an exact fit, a closed curve will not exactly fit the
curve points.
2. You may use the name specified by the bspline_name parameter, later to refer to this BSPLINE.
Adams View will not allow you to have two BSPLINEs with the same full name, so you must provide
a unique name.
geometry 13
be assigned to it.
5. A BSPLINE is the geometric counterpart to the CURVE data_element. The difference being that the
BSPLINE is displayed with the Adams View model and the CURVE is not. The BSPLINE references
a CURVE for its definition and a REF_MARKER for it position. A single CURVE can be referenced
by multiple BSPLINEs.
You may identify a curve by typing its name or by picking it from the screen.
Since curves do not have a geometric position, Adams View displays curve icons at or near the model
origin. If the curve icon is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the curve icon is displayed.
Curves can be draw by referencing a curve name in the definition of a BSPLINE geometry element.
Therefore, the BSPLINE element is the geometric counterpart of the CURVE data element.
If you created the curve by reading an Adams data set or graphics file, the curve name is the letters
CUR followed by the Adams data set curve ID number. The name of Adams CURVE/101 is
CUR101, for example. If you created the curve during preprocessing, you gave it a name at that time.
If a curve is owned by the default model, you may identify it by entering its name only. If it is not,
you must enter its full name. To identify a curve under a different model, for instance, you may need
to enter the model name as well. For example, you may specify curve 'CAM_PROFILE' from model
'VALVE_TRAIN' by entering ".VALVE_TRAIN.CAM_PROFILE'". If you type a "?", Adams
View will list the curve available by default.
You must separate multiple curve names by commas.
If the curve is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple curve picks by commas.
6. The reference marker must exist before the BSPLINE can be created.
This marker acts as a coordinate reference for the coordinate values used to define the CURVE that
acts as a template for the creation of the bspline.
A BSPLINE is the geometric counterpart to the CURVE data_element. The difference being that
references a CURVE for its definition and a REF_MARKER for it position. A single CURVE can
be referenced by multiple BSPLINEs.
time.
7. A BSPLINE is the geometric counterpart to the CURVE data_element. The difference being that
geometry 15
associated with it.
8. The segment_count parameter is not used if you have specified the FIT_TYPE as
CONTROL_POINTS.
For an open CURVE, Adams View will default to a SEGMENT_COUNT that is three less than the
number of CURVE_POINTS, which gives an exact fit to the CURVE_POINTS. Specifying fewer
segments will result in a smoother curve, but the curve will not pass exactly through the
CURVE_POINTS. You must specify at least four CURVE_POINTS to create an open curve.
than the number of CURVE_POINTS, the computed curve will exactly match the curve points. If
you specify fewer segments, Adams will use a least-squares fit to compute the closest fit to the points.
Closed curves must be defined by at least eight CURVE_POINTS, and may have a maximum of five
segments less than the number of CURVE_POINTS.
For a closed curve defined by CURVE_POINTS, Adams will default a SEGMENT_COUNT of five
segments less than the number of CURVE_POINTS.
Note that because three segments less than the number of curve points are required for an exact fit, a
closed curve will not exactly fit the curve points.
9. The 'spread_points' parameter when specified to ‘yes’, in conjunction with a reference profile
(otherwise the parameter is invalid and will be ignored) specifies that the set of points generated for
the bspline are such that they are equally spaced. Thus specifying the parameter to ‘yes’, means use of
a different algorithm for generating a bspline (from the gwire geometry), wherein all the points on the
bspline are equally spaced).
10. The 'num_new_pts' is valid only when the spread points parameter is set to ‘yes’ (otherwise the
parameter will be ignored). The parameter defines the number of points generated for the bspline
using the new algorithm. Note that the points will be equally spaced.
geometry create curve chain
11. The 'closed' parameter is a Boolean value that specifies whether the generated bspline is a closed curve
or otherwise.

Links together wire construction geometry to create a complex profile, which you can then extrude.
Format:
chain_name = a new chain
adams_id = adams_id
comments = string
objects_in_chain = an existing gwire
Example:
geometry create curve chain &
chain_name = chain__1 &
adams_id = 12376
Description:

chain_name A New Chain Specifies the name of the chain you want to create or modify
data file.
objects_in_chain An Existing Gwire Specifies the geometry to be chained together
1. The geometry to be chained together must touch at one endpoint and cannot be closed geometry. It
adds the final chained geometry to the part that owns the first geometry that you selected.
geometry 17
geometry create curve circle
yourself.

Allows for creation of the circle object.
Format:
circle_name = a new circle
adams_id = adams_id
comments = string
radius = length
Example:
eometry create curve circle &
circle_name = circle__1 &
adams_id = 10 &
comments = "a new circle" &
radius = 10 &
segment_count = 10
Description:

circle_name A New Circle Specifies the name of the new circle.
Adams data file
modified.
center_marker An Existing Specifies the marker at the center of a circle, an arc, the
Marker bottom of a cylinder, or the bottom of a frustum.
ref_radius_by_marker An Existing Specifies the radius of a circle, an arc, or a cylinder to be
Marker the distance from the center marker Z axis to this radius
marker.
segment_count Integer Specifies the number of straight line segments Adams View
uses to draw a circle or an arc.
1. The circle is segmented and therfore can look like a square or triangle if needed.
The circle is defined as a radius drawn around a center marker. The circle's orientation is dependent
upon the orientation of its center marker. Its radius is determined by either the
'REF_RADIUS_BY_MARKER' or 'RADIUS=' parameter. The number of sides on the circle is
controlled by the 'SEGMENT_COUNT=' parameter. A circle will move with the part its center
marker is located on.
2. You may use the name specified by the circle_name parameter later to refer to this circle. Adams View
will not allow you to have two circles with the same full name, so you must provide a unique name.
be assigned to it.
geometry 19
geometry create curve curve_trace
Cautions:

Creates traces that follow the motion of a curve as it moves relative to a second part
Format:
curve_type = curve_type
close = yes_no_auto
Example:
geometry create curve curve_trace &
geometry_name = LINK_56 &
base_marker = MARKER_84 &
curve_type = polyline
Description:

geometry_name An Existing Geometric Specifies an existing geometry.
Entity
base_marker An Existing Marker This parameter is used to specify a marker whose
position will be frozen in the view as the model animates
curve_type Curve_type Specifies the type of curve to be created, either bspline
or polyline
close Yes_no_auto Causes the info window to close down.
analysis_name An Existing Analysis Specifies an existing analysis
1. A trace that follows a curve creates a two-dimensional spline. The point can move in any direction
relative to the part on which the trace was created. Adams View creates the curve in the xy plane of
the base marker(the marker on the part on which the trace was created). Adams View assumes the
circle is parallel to the plane or the cylinder is perpendicular to the plane, and that the motion is in
this plane.
default.
associated with it.
geometry 21
3. base_marker 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.
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.
Specifies an existing marker.
time.
4. Any text that was in the info window while open, will be flushed out. The next time the info window
is opened, only the new text will be present.
Closing the info window does not change its size. The next time the info window is opened, its size
will be the same as the previous time.
All scroll positions are returned to the first line in the info window.
5. You may identify a analysis by typing its name or by picking it from the screen.
geometry create curve ellipse
graphics file without the '.gra' extension.
be entered.
associated with it.

Allows for creation of the ellipse object.
Format:
ellipse_name = a new ellipse
adams_id = adams_id
comments = string
major_radius = length
minor_radius = length
start_angle = angle
end_angle = angle
Example:
geometry create curve ellipse &
ellipse_name = ellipse__1 &
comments = "a new ellipse" &
major_radius = 10 &
minor_radius = 6 &
start_angle = 0 &
end_angle = 180
geometry 23
Description:

ellipse_name A New Ellipse Specifies a new ellipse object
adams_id Adams_id Specifies an integer used to identify this element in the Adams data
file.
center_marker An Existing Specifies the marker at the center of a circle, an arc, the bottom of a
Marker cylinder, or the bottom of a frustum.
major_radius Length The MAJOR_RADIUS parameter is used to specify the radius for
the circular spine of the torus.
minor_radius Length The MINOR_RADIUS parameter is used to specify the radius for
the circular cross-sections of the torus.
start_angle Angle
end_angle Angle
geometry create curve nurb_curve

Format:
nurb_curve_name = a new nurb_curve
comments = string
degree = integer
rational = boolean
periodic = boolean
control_points = location
weights = real
knots = real
Example:
geometry create curve nurb_curve &
nurb_curve degree = 3 &
nurb_curve rational = yes &
nurb_curve periodic = yes &
nurb_curve control_points = 1,5,3 &
nurb_curve knots = 5
Description:

nurb_curve_name A New Nurb_curve
degree Integer
rational Boolean
periodic Boolean
control_points Location
weights Real
knots Real
geometry 25
geometry create curve outline

Allows for creation of the outline object.
Format:
outline_name = a new outline
adams_id = adams_id
comments = string
visibility_between_markers = on_off
image_file_name = string
horizontal = clamp_repeat
vertical = clamp_repeat
close = boolean
Example:
:
geometry create curve outline &

outline_name = OUTLINE__1 &
adams_id = 1 &
comments = " a new outline" &
marker_name = Origin , CM &
visibility_between_markers = on &
close = yes
Description:

outline_name A New Outline Specifies the name of the new outline
modified.
marker_name An Existing Marker Specifies the marker associated with this entity.
visibility_between_markers On_off Specifies whether the outline is visible between two
markers.
image_file_name String Specifies the name of an image file on disk. File
types supported include .bmp, .jpg, .gif, and .png.
horizontal Clamp_repeat Controls how the desired polygon is horizontally
filled with the image
vertical Clamp_repeat Controls how the desired polygon is vertically filled
with the image
close Boolean Specifies the whether or not Adams View should
close the outline when it is created.
1. Outlines are line segments (open or closed) that are define by a series of markers.
An outline is composed of at least two and not more than 2500 markers.
These markers are connected by line segments to form the outline.
If all of the markers of an outline lie on the same part, the parent of the outline is this part, and the
outline moves with this part.
If some of the markers lie on different parts, the parent of the outline is the model. As the parts move,
the outline is stretched or "rubber-banded" to fit the new marker locations.
2. You may use this name later to refer to this graphic. Adams View will not allow you to have two
outlines with the same full name, so you must provide a unique name.
geometry 27
be assigned to it.
5. Many entities are attached to, or otherwise associated with, a specific marker. You use this parameter
to identify that marker.
time.
geometry create curve point_trace
6. When you create an outline, by default a line will be drawn between each of the markers specified.
Using the VISIBILITY_BETWEEN_MARKERS parameter, you can turn turn off the visibility
between desired markers. For example, the following commands:
model create model_name=MOD1 marker create marker=MAR1
location=1,1,0
marker create marker=MAR2 location=2,1,0 marker create
marker=MAR3
location=2,2,0 marker create marker=MAR4 location=1,2,0
geometry
create curve outline outline_name=.MOD1.ground.OUT1 &
marker_name=MAR1,MAR2,MAR3,MAR4 &
visibility_between_markers=ON,ON,OFF,ON
will draw lines from MAR1 to MAR2, and from MAR3 to MAR4 there will be no line segment from
MAR2 to MAR3.
If you specify the VISIBILITY_BETWEEN_MARKERS parameter with less values than the number
of markers, the rest of the visibilities will default to ON. If for example you have an outline with some
of the visibilities turned off and you want to turn them all on, you can specify a single ON value.
When you render the outline in solid or shaded mode, each of the contiguously visible segments will
be rendered as objets. In the above example, the outline would not be draw as a solid object, but as
two lines.
Setting the visibility to OFF for a marker is equivalent to using a negative marker id on the
OUTLINE statement in the Adams DATA SET.
7. When you specify 'NO' for the ‘close’ parameter, Adams View will create a outline through the
markers specified, and will not attempt to close the start and end points with an additional line
segment. 'NO' is the default value.
When you specify 'YES' for this parameter, Adams View will create the outline, through the markers
specified, and add an additional line segment from the end marker to the starting marker.

Creates traces that follow the motion of a point as it moves relative to a second part
Format:
trace_marker = an existing marker
curve_type = curve_type
close = yes_no_auto
geometry 29
Example:
geometry create curve point_trace &
trace_marker = marker_71 &
base_marker = marker_84 &
curve_type = polyline
Description:

trace_marker An Existing Marker Specifies the names of one or more markers for which you want
Adams View to create traces
base_marker An Existing Marker This parameter is used to specify a marker whose position will
be frozen in the view as the model animates
curve_type Curve_type Specifies the type of curve to be created, either bspline or
polyline
close Yes_no_auto Causes the info window to close down.
analysis_name An Existing Analysis Specifies an existing analysis
1. A trace that follows a point creates a three-dimensional spline. The point can move in any direction
relative to the part on which the trace was created.
2. base_marker 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.
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.
Specifies an existing marker.
geometry create curve polyline
time.
3. Any text that was in the info window while open, will be flushed out. The next time the info window
is opened, only the new text will be present.
Closing the info window does not change its size. The next time the info window is opened, its size
will be the same as the previous time.
All scroll positions are returned to the first line in the info window.
be entered.
associated with it.

Allows you to create a polyline.
geometry 31
Format:
polyline_name = a new polyline
comments = string
location = location
path_curve = an existing gwire
close = boolean
Example:
geometry create curve polyline &
polyline_name = polyline__1 &
location = 1,5,3 &
image_file_name = "c:\users\ashish\image"
Description:

polyline_name A New Polyline Specifies the name of the new POLYLINE
modified.
location Location Specifies the locations to be used to define the polyline.
path_curve An Existing Gwire Specifies the locations to be used to define the polyline
from an existing graphical object.
Marker coordinates are with respect to.
close Boolean Specifies if the polyline is to be open or closed
1. The POLYLINE command provides a means to create a segmented curve that may be open or closed.
If closed, the POLYLINE becomes a polygon that can be filled (i.e. shaded). The end points of the
POLYLINE do not need to be coincident for you to close it. By setting the CLOSED parameter to
"YES" the two end points will be connected with a straight line segment.
The POLYLINE is displayed by connecting any number of LOCATIONS together, in the order in
which the LOCATIONS are input, using straight line segments.
The POLYLINE differs from the OUTLINE Adams View geometric element in that the outline
requires that you provide a series of markers to define the locations to be connected. The OUTLINE
can span multiple parts and the POLYLINE cannot. POLYLINEs are more space efficient than
OUTLINEs, taking approximately 40% of the memory required when compared to storing
OUTLINEs. Finally, POLYLINEs are not written to the Adams data set, and therefore, do not
appear in the Adams graphics file. POLYLINE definitions can be stored in a command file, written
to a WaveFront file, and, of course, the binary Adams View file.
In light of being more memory efficient, POLYLINEs are the most efficient means of storing
geometry translated from IGES files.
2. Specifies the name of the new POLYLINE. You may use this name later to refer to this POLYLINE.
Adams View will not allow you to have two POLYLINE with the same full name, so you must provide
a unique name.
be assigned to it.
5. The PATH_CURVE is any member of the WIRE_GEOMETRY class (which includes arcs, circles,
spline curves, polylines and outlines). When you specify a PATH_CURVE, the values of the vertices
are extracted from the specified object and used to compose the polyline.
geometry 33
geometry create feature blend
system is initially your model, that is, the global coordinate system. You may change the default
7. If closed, the polyline can be filled (that is, shaded). The end points of the polyline do not need to be
coincident for you to close it. By setting the CLOSED parameter to "YES" the two end points will
be connected with a line segment. If the CLOSE parameter is set to "NO" the polyline will appear
as a segmented curve.

Creates a chamfer or fillet (blend) on a vertex or edge on a rigid body.
Format:
blend_name = a new blend
subtype = sub_type
subids = integer
chamfer = boolean
radius1= length
radius2 = length
reference_marker = an existing marker
locations = location
Example:
geometry create feature blend &
blend_name = BLEND__1 &
subtype = edge &
subids = 10 &
chamfer = yes &
radius1 = 0.15 &
reference_marker = Origin
geometry create feature hole
Description:

blend_name A New Blend Specifies the name of the blend to be created or modified.
subtype Sub_type Specifies whether you are creating the blend on an edge or
vertex:
subids Integer Specifies the Parasolid tags identifying the vertices or edges
based on the selected subtype.
chamfer Boolean Specifies whether or not to chamfer the edge or vertex
radius1 Length Specifies the width of the chamfer bevel or radius of the fillet.
radius2 Length Specifies the end radius for a fillet. Adams View uses the value
you enter for radius1 as the starting radius of the variable fillet.
reference_marker An Existing Marker Specifies the marker that is used to define the location of the
blend.
locations Location Specifies the location of the vertices or edges used to define the
blend relative to the reference marker.
1. The subtype parameter specifies whether you are creating the blend on an edge or vertex:
• edge - Creates the blend on the edge of an object.
• vertex - Creates the blend on the vertex of an object.
2. The chamfer parameter specifies whether or not to chamfer the edge or vertex:
• no - Creates a fillet instead of a chamfer.
• yes - Creates a chamfer.
Tips:
1. If you do not specify a reference marker, Adams View uses the reference marker of the geometry.

Allows you to create a hole feature.
Format:
hole_name = a new hole
subid = integer
center = location
geometry 35

countersink = boolean
radius = length
depth = length
Example:
geometry create feature hole &
hole_name = hole__1 &
subid = 12 &
center = 10 , 2 , 1 &
countersink = yes &
radius = 3 &
depth = 4
Description:

hole_name A New Hole Specifies the name of the hole to be created
subid Integer Specifies the Parasolid tag identifying the face on which the hole or boss will
be created.
center Location Specifies the location of the center of the hole or boss on the object.
countersink Boolean Specifies whether to create a hole or a boss:
radius Length Specifies radius of the hole or boss.
depth Length Specifies depth of the hole or the height of the boss.
1. You can use the name specified by the hole_name parameter, 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.
when entering it.
geometry create feature thinshell
be assigned to it.
2. The countersink parameter specifies whether to create a hole or a boss:
• yes - Creates a boss.
• no - Creates a hole.
Cautions:
1. You cannot specify the radius and depth of a hole so that it splits the current geometry into two
separate geometries.

Allows you to hollow out one or more faces of a solid object to create a shell.
Format:
thin_shell_name = a new thin_shell
subids = integer
thickness = length
Example:
geometry create feature thinshell &
thin_shell_name = thin_shell__1 &
subids = 10 &
thickness = 0.15
geometry 37
geometry create point
Description:

thin_shell_name A New Thin_shell Specifies the name of the thinshell to be created or modified.
subids Integer Specifies the Parasolid tag(s) identifying the face(s) that will be
removed to create the thinshell.
thickness Length Specifies the thickness of the remaining shell after you hollow the
object.
locations Location Specifies the location(s) of the face(s) that will be removed to
create the thinshell.
1. You can use the name specified by the thin_shell_name parameter, 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.
when entering it.
be assigned to it.

Defines locations in three-dimensional space upon which you can build your model.
Format:
point_name = a new point
adams_id = integer
comments = string
geometry create shape block
Example:
geometry create point &
point_name = point__1 &
adams_id = 1 &
comments = " a new point" &
ref_marker_name = marker_1
Description:

point_name A New Point Specifies the name of the point to create or modify.
adams_id Adams_id Assigns a unique ID number to the geometry.
comments String Adds any comments about the geometry to help you manage and
identify it.
ref_marker An Existing Specifies a marker that defines the location of the point
Marker

Allows for creation of the block object.
Format:
block_name = a new block
adams_id = adams_id
comments = string
corner_marker = an existing marker
diag_corner_coords = length
Example:
geometry create shape block &
block_name = box__1 &
corner_marker = marker_82 &
diag_corner_coords = 2,4,6
geometry 39
Description:

block_name A New Block Specifies the name of the new block.
Adams data file
corner_marker An Existing Marker Specifies the marker that defines the anchor point for the
definition of a block.
diag_corner_coords Length Specifies the location (x, y, z) of the opposite diagonal corner
from the corner_marker for a block. These coordinates are
with respect to the corner marker x, y, and z axes. This
location, along with the corner_marker, define the
boundaries of the block.
1. A block is a box with parallel edges and orthogonal vertices. You position and orient a block by means
of a corner marker. You specify the dimensions of the box by supplying three coordinates for the
opposite corner.
2. Specifies the name of the new block. You may use this name later to refer to this block. Adams View
will not allow you to have two blocks with the same full name, so you must provide a unique name.
be assigned to it.
geometry create shape cylinder
5. These coordinates are with respect to the corner marker x, y, and z axes. This location, along with
the corner_marker, define the boundaries of the block.

Allows for creation of the cylinder object.
Format:
cylinder_name = a new cylinder
adams_id = adams_id
comments = string
length = length
radius = length
side_count_for_body = integer
segment_count_for_ends = integer
Example:
geometry create shape cylinder &
cylinder_name = CYLINDER__1 &
center_marker = MARKER_82 &
angle_extent = 60 &
length = 25 &
ref_radius_by_marker = MARKER_72
geometry 41
Description:

cylinder_name A New Cylinder Specifies the name of the new cylinder.
Adams data file.
modified.
bottom of a cylinder, or the bottom of a frustum
angle_extent Angle Specifies a subtended angle measured positive
(according to the right-hand rule) about the z-axis of
the center marker.
length Length Specifies the height of a cylinder or a frustum.
Radius Length Specifies the radius of a circle, an arc, or a cylinder.
ref_radius_by_marker An Existing Marker Specifies the radius of a circle, an arc, or a cylinder to be
the distance from the center marker Z axis to this radius
marker.
side_count_for_body Integer Specifies the number of flat sides Adams View draws on
a cylinder or a frustum.
segment_count_for_ends Integer Specifies the number of straight line segments Adams
View uses to draw the circles at the ends of a cylinder or
a frustum.
1. A cylinder is an extruded circle whose top and bottom are perpendicular to the cylinder central axis.
The cylinder is placed at the marker named 'CENTER_MARKER='. The circles at the top and at the
bottom of the cylinder have a radius specified by a radius, or radius reference marker. The cylinder
length is along the positive z-axis of the center marker, and is specified by 'LENGTH='. The number
of sides can be chosen using the 'SIDE_COUNT_FOR_BODY' parameter. The number of edges on
the end circles can be specified using the 'SEGMENT_COUNT_FOR_END=' parameter. The
cylinder will move with the part who owns the center marker.
2. Specifies the name of the new cylinder. You may use this name later to refer to this cylinder. Adams
View will not allow you to have two cylinders with the same full 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 any length.
of the circle or to the plane of the arc. Similarly, if you are defining a cylinder or a frustum, orient the
center marker so that its z-axis is normal to the bottom of the cylinder or the frustum.
7. Because the two circles at the ends of a cylinder or a frustum are both perpendicular to the z-axis of
the center marker, they are parallel. Adams View uses the value of LENGTH to specify the z distance
between the two circles. A positive value specifies a cylinder or a frustum along the positive z-axis of
the center marker, and a negative value specifies a cylinder or a frustum along the negative z-axis of
the center marker.
8. Adams View stores the radius value, not the marker name. If you later move this marker, the radius
will not change.
Cautions:
1. cylinder_name: The number of levels used varies from case to case and the parentage must exist before
an entity can be assigned to it.
geometry 43
geometry create shape ellipsoid

Allows for creation of the ellipsoid object.
Format:
ellipsoid_name = a new ellipsoid
comments = string
x_scale_factor = length
y_scale_factor = length
z_scale_factor = length
Example:
geometry create shape ellipsoid &
ellipsoid_name = ELLIPSOID__1 &
x_scale_factor = 2
Description:

ellipsoid_name A New Ellipsoid Specifies the name of the new ellipsoid
center_marker An Existing Marker Specifies the marker at the center of a circle, an arc, the bottom
of a cylinder, or the bottom of a frustum
x_scale_factor Length The X_SCALE_FACTOR parameter is used to specify the
scaling of the initial unit sphere along the center marker's x axis.
y_scale_factor Length The Y_SCALE_FACTOR parameter is used to specify the
scaling of the initial unit sphere along the center marker's y axis.
z_scale_factor Length The Z_SCALE_FACTOR parameter is used to specify the
scaling of the initial unit sphere along the center marker's z axis.
1. An ellipsoid is a unit sphere that has been scaled in the x, y, and z directions. The ellipsoid is placed
at the marker named 'CENTER_MARKER='. The X_SCALE_FACTOR, Y_SCALE_FACTOR,
and Z_SCALE_FACTOR parameters are used to specify the scaling of the initial unit sphere along
the center marker's x, y, z axes. The ellipsoid will move with the part which owns the center marker.
geometry create shape extrusion
2. Specifies the name of the new ellipsoid. You may use this name later to refer to this ellipsoid. Adams
View will not allow you to have two ellipsoids with the same full name, so you must provide a unique
name.
be assigned to it.
4. Specifies the marker at the center of a circle, an arc, the bottom of a cylinder, or the bottom of a
frustum. If you are creating a circle or an arc, orient the center marker so that its z-axis is normal to
the plane of the circle or to the plane of the arc. Similarly, if you are defining a cylinder or a frustum,
orient the center marker so that its z-axis is normal to the bottom of the cylinder or the frustum.

Allows for creation of the extrusion object.
Format:
extrusion_name = a new extrusion
adams_id = adams id
comments = string
geometry 45

profile_curve = an existing gwire
points_for_profile = location
path_points = location
length_along_z_axis = length
analytical = boolean
Example:
geometry create shape extrusion &
extrusion_name = extrusion__1 &
comments = "a new extrusion" &
reference_marker = origin &
profile_curve = arc__1 &
path_curve = circle__1 &
analytical = no
Description:

extrusion_name A New Extrusion Specifies the name of the new extrusion.
Adams data file.
modified.
reference_marker An Existing Specifies the marker used to place and orient an extrusion.
Marker
profile_curve An Existing Gwire Specifies the object used to define the profile of the
extrusion.
points_for_profile Location Specifies the points used to define the profile of the
extrusion. The points are relative to the extrusion's
reference marker.
path_curve An Existing Gwire Specifies the object used to define the path of the
extrusion.

path_points Location Specifies the points used to define the path of the
extrusion.
length_along_z_axis Length Specifies the legth along the Z axis of the reference marker
to extrude the profile curve of the extrusion.
relative_to An Existing Specifies the coordinate system that location coordinates
Model, Part Or are with respect to.
Marker
analytical Boolean
1. An extrusion is defined by a path polyline curve and a profile curve, which may be either a polyline
or a data element curve. The profile curve is in the X-Y plane of its parent part. Z coordinate values
of the profile curve are ignored. The path curve is a polyline that describes how the profile will be
swept along. The extrusion is placed with respect to the marker named 'REFERENCE_MARKER='
using the same orientation that the path curve has with respect to its parent part. The extrusion will
move with the part which owns the reference marker.
2. You may use the name specified by the extrusion_name parameter, later to refer to this extrusion.
Adams View will not allow you to have two extrusions with the same full name, so you must provide
a unique name.
be assigned to it.
geometry 47
geometry create shape force
4. You may specify an arc, circle, spline curve, polyline, or outline for the path_curve parameter. The
object defines the path along which the profile curve will be swept.
5. The points specified by the path_points parameter are relative to the extrusion's reference marker.
The points defines the path along which the profile curve will be swept.
Tips:
1. You may specify an arc, circle, spline curve, polyline, or outline for the profile_curve parameter The
object should be in the X-Y plane of the extrusions reference marker.

Allows you to create a force graphic on an element. Force graphics are arrows whose magnitudes and
directions reflect the scaled, relative magnitudes and directions of the force vectors acting on your model
during a simulation.
Force graphics help you gauge how large your forces become and in what directions they are applied during
a simulation.
Figure 1 Force Graphics on an Animation
To see force graphics during animations, you must specify those force elements in your model for which you
would like to see the associated force graphics. To turn force graphics on or off for particular forces, refer to
the Adams View documentation that describe how to modify a force or a motion.
You can specify the following for the display of force graphics during an animation:
 Scale factor used to control the graphic’s relative size compared to the objects in the model.
 Whether or not the force magnitudes are displayed numerically. The numerical values appear near
the arrowheads.
 Whether or not the force graphics are drawn in wireframe or shaded mode when the model is
animated in shaded mode.
 Whether the force graphic is always drawn in front of other geometry. This is particularly useful
when viewing forces inside geometry, such as three-dimensional contacts.
There are two different scale factors: one for forces and one for torques. Adams applies the force scale factor
to all force graphics in your model to maintain their proper relative sizing, while it applies the torque scale
factor to all torque graphics in your model.
Finding force and torque scale factors that are good for the entire animation might require some trial and
error. It is often useful to set your scale factors while viewing the frame for which the largest force reaches its
peak value.
Format:
force_name = new force symbol
adams_id = integer
comments = string
force_element_name = existing force
jprim_name = existing primitive joint
all_force_elements = true_only
applied_at_marker_name = existing triad
Example:
geometry create shape force &
force_name = force_1_1 &
force_element_name = vforce_1 &
applied_at_marker_name = marker_4
geometry 49
Description:

Force_name New Force Symbol Specifies the name of the force graphic to be
created
Adams_id Integer Specifies a new name for the geometry. Assigns a
unique ID number to the geometry.
Comments String Adds any comments about the geometry to help
you manage and identify it.
Force_element_name Existing Force Specifies the name of the force element whose
force is to be displayed by the force graphic.
Joint_name Existing Joint Specifies the name of the joint element whose
Jprim_name Existing Primitive Joint Specifies the name of the joint primitive element
whose force the force graphic is to display.
Curve_curve_name Existing Ccurve Specifies the name of the curve_curve element
Point_curve_name Existing Pcurve Specifies the name of the point_curve element
All_force_elements True Specifies that all the forces from all the force
elements acting on the marker that
applied_at_marker_name specifies, are summed
together to determine the force that the force
graphic displays. The only value allowed is true.
There must be at least one force element acting
on the marker.
Applied_at_marker_name Existing Triad Specifies the name of the marker where Adams
View displays the force graphic.
refer to this entity. Adams View does not allow you to have two entities with the same full 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.
when entering it.
be assigned to it.
2. The force element can be:
• Beam
• Bushing
• Field
• Translational spring damper
• Rotational spring damper
• Tire
• Single-component force
• Force vector
• Torque vector
• General force
• Multi-point force
3. The joint element can be:
• Translational
• Revolute
• Cylindrical
• Univesal
• Spherical
• Planar
• Rackpin
• Screw
4. The joint primitive element can be:
• At point
• Inline
• Inplane
• Orientation
• Parallel_axis
geometry 51
geometry create shape frustum
• Perpendicular
5. If you use the all_force_elements=true argument, the marker must have at least one force applied to it.
If you enter a specific force type using joint_name, jprim_name, force_element_name, point_curve_name, or
curve_curve_name parameters, then the marker named in this parameter must be one of the markers
on which the specified force acts.

Allows for creation of the frustum object.
Format:
frustum_name = a new frustum
adams_id = adams_id
comments = string
length = length
top_radius = length
bottom_radius = length
Example:
geometry create shape frustum &
frustum_name = frustum__1 &
adams_id = 101 &
comments = "a new frustum" &
length = 10 &
side_count_for_body = 10
Description:

frustum_name A New Frustum Specifies the name of the new frustum
Adams data file
modified.
(according to the right-hand rule) about the z-axis of the
center marker.
side_count_for_body Integer Specifies the number of flat sides Adams View draws on
a cylinder or a frustum.
top_radius Length Specifies the radius at the top of a frustum.
bottom_radius Length Specifies the radius at the bottom of a frustum.
View uses to draw the circles at the ends of a cylinder or
a frustum.
1. A frustum is a specialized cone whose top and bottom are perpendicular to the cone central axis. A
frustum will move with the part that the center marker belongs to.
2. You may use the name specified by the frustum_name parameter later to refer to this frustum. Adams
View will not allow you to have two frustums with the same full name, so you must provide a unique
name.
geometry 53
geometry create shape gcontact
be assigned to it.
the center marker.
7. The top of the furstum is perpendicular to the center marker z-axis, and the center of the top is at the
position on the center marker z-axis that LENGTH specifies. Also, The bottom is perpendicular to
the center marker z-axis, and the center of the bottom is at the center marker origin.

Allows you to create a new contact force graphic object.
Format:
contact_force_name = a new contact_force_graphic
adams_id = adams_id
comments = string

contact_element_name = an existing contact element
force_display = force_display_options
Example:
geometry create shape gcontact &
contact_force_name = gcontact__1 &
adams_id = 1 &
comments = "a new contact force graphic" &
contact_element_name = sphere_plane_contact_5 &
force_display = both
Description:

contact_force_name A New Contact_force_graphic Specifies the name of the contact force
graphic to be created
adams_id Adams_id Assigns a unique ID number to the geometry
comments String Adds any comments about the geometry to
help you manage and identify it.
contact_element_name An Existing Contact Element Specifies the name of the contact element
whose force is to be displayed by the force
graphic.
force_display Force_display_options Specifies the options for displaying the force
graphics
1. A gcontact is a force graphic for a contact element. The gcontact can display graphics for component
or aggregate forces of a contact.
• none - Displays no force graphics.
• components - Displays force graphics for the normal force, friction force, and torque at each
incident of a contact for each frame. Multiple incidents at a frame display multiple force graphics.
• aggregate - Displays force graphics for the sum of all forces (normal and friction) and all torques
on the contact at each frame. Sums multiple incidents at a frame and displays one force graphic.
• both - Displays both component and aggregate force graphics.
geometry 55
geometry create shape link

Allows for creation of the link object.
Format:
link_name = a new glink
comments = string
i_marker = an existing marker
j_marker = an existing marker
width = length
depth = length
Example:
geometry create shape link &
link_name = LINK__1 &
comments = "a new link" &
i_marker = MK124 &
j_marker = MK112 &
width = 25 &
depth = 5
Description:

link_name A New Glink Specifies the name of the new link
i_marker An Existing Marker Specifies the marker at one end of a link object.
j_marker An Existing Marker Specifies the marker at one end of a link object.
width Length Specifies the width of the link.
depth Length Specifies the depth of the link.
1. A link is a three-dimensional object used to represent a connecting part. It has its length defined by
the distance between I_MARKER and the J_MARKER. It also has a WIDTH and DEPTH that
may be specified. The ends of the link are semi-circular. The J_MARKER must lie in the XY plane
of the I_MARKER.
geometry create shape nurb_surf
2. You may use the name specified by the link_name parameter later, to refer to this link. Adams View
will not allow you to have two links with the same full name, so you must provide a unique name.
be assigned to it.
Cautions:
1. The j_marker must lie along the i_marker's x-axis and it must have the same orientation as the
i_marker.
i_marker.

Format:
nurb_surf_name = new surf_name
comments = string
udegree = integer
vdegree = integer
rational = boolean
geometry 57
geometry create shape picture

uperiodic = boolean
vperiodic = boolean
num_uctrlpts = integer
num_vctrlpts = integer
weights = real
uknots = real
vknots = real
Description:

nurb_surf_name New Surface Name Specifies the name of the nurb surface created. You can refer to
this geometry in future using this name.
comments String Specifies any comments to be associated with the nurb surface
geometry created.
udegree Integer Specifies an integer greater than 0 and less than or equal to 20.
vdegree Integer Specifies an integer greater than 0 and less than or equal to 20.
rational Yes/no Specifies a Boolean value
uperiodic Yes/no Specifies a Boolean value
vperiodic Yes/no Specifies a Boolean value
num_uctrlpts Integer Specifies the number of control points.
num_vctrlpts Integer Specifies the number of control points.
control_points Location Specifies the location of the control points.
weights Real Specifies the weight.
uknots Real Specifies a real number
vknots Real Specifies a real number

Allows you to create a picture.
geometry create shape plane
Format:
picture_name = new picture
image_file_name = name of image
height = integer
location = location
Example:
geometry create shape picture &
picture_name = picture_1 &
image_file_name = "c:\documents and settings\car.jpg" &
height = 50
Description:

picture_name New Picture Specifies the new picture to be created.
image_file_name String Specifies the file name containing the image.
height Integer Specifies the height of the picture.
location Location Specifies the location of the picture.

Allows you to create a two-dimensional box.
Plane Tool is a two-dimensional box that gets created. You can draw a plane’s length and width in the
plane of the screen or the working grid, if it is turned on. You will find planes most useful when you are
creating contact forces between objects
When you create a plane, you can select to create a new part consisting of the plane geometry or add the plane
geometry to an existing part or ground. If you create a new part, it has no mass since it is composed of only
wire geometry.
Format:
plane_name = new plane
adams_id = integer
geometry 59

comments = string
x_minimum = real
x_maximum = real
y_minimum = real
y_maximum = real
Example:
geometry create shape plane &
plane_name = plane_1 &
ref_marker_name = marker_5 &
x_minimum = 100 &
x_maximum = 500.9 &
y_minimum = 100 &
y_maximum = 788
Description:

plane_name New Plane Name Specifies the name of the plane to be created.
adams_id Integer Assigns a unique ID number to the plane.
Comments String Adds any comments about the plane that you want to enter to
help you manage and identify it.
ref_marker_name Existing Marker Specifies the reference marker used to locate and orient the plane.
x_minimum Real Specifies the location of one corner of the plane in coordinates
relative to the reference marker
x_maximum Real Specifies the location of the opposite corner of the plane in
coordinates relative to the reference marker.
y_minimum Real Specifies the location of one corner of the plane in coordinates
relative to the reference marker. If all values are positive, the
values indicate the lower left corner of the plane.
y_maximum Real Specifies the location of the opposite corner of the plane in
coordinates relative to the reference marker.
geometry create shape plate
when entering it.
be assigned to it.
2. An Adams Solver ID is an integer used to identify the element in the Adams Solver dataset (.adm)
file. You only need to specify an ID number if you have user-written subroutines.
3. Enter a 0 to have Adams Solver assign the ID for you.
4. For comments, you can enter any alphanumeric characters. The comments that you create appear in
the Information window when you select to display information about the object, in the Adams View
log file, and in a command or dataset file when you export your model to these types of files. (Note
that design variables are not output to datasets; therefore, neither are their comments.)
5. If all values of x_minimum,y_minimum,x_maximum,y_maximum are positive, the values indicate
the lower left corner of the plane. For example, the values of x_minimum = 10 and y_minimum =
20, place the lower left corner at 10,20 in the reference marker's coordinate system.

Allows you to create a plate object.
Format:
plate_name = a new plate
comments = string
width = length
radius = length
geometry 61
Example:
geometry create shape plate &
plate_name = plate__1 &
comments = "a new plate" &
marker_name = mk112 , mk124 , cm &
width = 15 &
radius = 5
Description:

plate_name A New Plate Specifies a new plate object
width Length Specifies the width of the plate
radius Length Specifies the plate radius
2. Many entities are attached to, or otherwise associated with, a specific marker. You use the
marker_name parameter to identify that marker. You may identify a marker by typing its name or by
picking it from the screen.
name at that time.
geometry create shape revolution
You must separate multiple marker names by commas. The z-axis of the first marker must be
perpendicular to the plate created by the multiple markers.

Allows for creation of the revolution object.
Format:
revolution_name = a new revolution
adams_id = Adams id
comments = string
number_of_sides = integer
Example:
geometry create shape revolution &
revolution_name = revolution__1 &
comments = "a new revolution" &
profile_curve = circle__1 &
angle_extent = 50 &
number_of_sides = 10 &
analytical = no
geometry 63
Description:

revolution_name A New Revolution Specifies the name of the new revolution.
data file.
reference_marker An Existing Specifies the marker used to place and orient a revolution.
Marker
profile_curve An Existing Gwire Specifies the object used to define the profile of the revolution.
points_for_profile Location Specifies the points used to define the profile of the revolution.
angle_extent Angle Specifies a subtended angle measured positive (according to the
right-hand rule) about the z-axis of the center marker.
number_of_sides Integer Specifies the number of flat sides Adams View draws on a
revolution.
Note: This will be used only when analytical option is

unchecked.
relative_to An Existing Specifies the coordinate system that location coordinates are
Model, Part Or with respect to.
Marker
analytical Boolean
1. For more detail about revolutions, see Revolution Tool dbox help.
2. A revolution is defined by a profile polyline curve which is revolved about the Z axis of the marker
named 'REFERENCE_MARKER='. The profile curve is a polyline that is in the X-Y plane of its
parent part. Z coordinate values of the profile curve are ignored. The revolution will move with the
part which owns the reference marker.
3. You may use the name specified by the revolution_name parameter, later to refer to this revolution.
Adams View will not allow you to have two revolutions with the same full name, so you must provide
a unique name.
geometry create shape shell
be assigned to it.
5. For the profile_curve parameter, you may specify an arc, circle, spline curve, polyline, or outline. The
coordinates of the object points, relative to the object's parent part, will be used to define a profile
relative to the revolution's reference marker. The profile defined by the points will be swept around
the reference marker's z-axis.
Tips:

Allows you to create the shell object.
Format:
shell_name = a new shell
comments = string
file_name = string
wireframe_only = boolean
geometry 65
Example:
geometry create shape shell &
shell_name = shell__1 &
comments = " a new shell" &
reference_marker = mk112 &
file_name = "c:\shell1.shl" &
wireframe_only = no
Description:

shell_name A New Shell Specifies the name of the new shell.
reference_marker An Existing Specifies the marker used to place and orient a shell.
Marker
file_name String Specifies the name of a file that contains the definition of the
shell.
wireframe_only Boolean
1. A shell is defined by a number of node points and the connectivity between those node points. The
shell is represented as polygons defined by connecting node points with straight line segments.
Polygons are not necessarily flat. The points and connectivety are read from a file named
"FILE_NAME=". The shell is placed at the marker named "REFERENCE_MARKER=". The shell
will move with the part that owns the reference marker.
2. You may use the name specified by the shell_name parameter later to refer to this shell. Adams View
will not allow you to have two shells 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.
geometry create shape solid_shell
be assigned to it.
Shell file format: The first line in a shell file has the form: int int float. The first integer represents the
number of points in the shell file. The second integer represents the number of polygons are described
in the file. The float value represent a scaling factor which is applied to all of the point coordinates.
The lines immediately following the first line consist of the x, y, and z coordinate floating point values
for the points. There is one xyz triplet per line. You may use multiple spaces or tabs to separate the
x, y, and z values.
Immediately following the coordinate values are the lines for defining the polygon connectivity. The
first number on one of these lines is the number of vertices that should be connected to form the
polygon. The following integers are the offsets into the list of points. For example, 4 5 6 2 1 means
that the polygon will be formed by 4 points and those points are the 5th, 6th, 2nd, and 1st points in
the list of points in the shell file. Note that it is not necessary to explicitly close each polygon by going
back to the start point. You may use multiple spaces or tabs to separate the values.
A sample shell file for a cube:
861.0
-1.0-1.01.0
-1.0 1.0 1.0
1.0 1.0 1.0
1.0 -1.01.0
-1.0-1.0 -1.0
-1.0 1.0 -1.0
1.0 1.0 -1.0
1.0 -1.0 -1.0
41234
45621
3267
43784
41485
48765

Allows you to create a solid shell. A solid shell is an internal function used to map STEP and IGES faces to
view. The solid shell object was created to combine a number of these faces as a solid.
geometry 67
Surface-based solid modeling is the least common modeling method used to define solids. Using this method,
the solid is defined as the internal volume surrounded by the defining surfaces.
Format:
solid_shell_name = new solid_shell
faces = existing face
Example:
geometry create shape solid_shell &
solid_shell_name = solid_shell_1 &
faces = face_1
Description:

Solid_shell_name New solid shell Specifies the name of the solid to be created
faces Existing face Specifies the faces making up the solid shell.
when entering it.
be assigned to it.
geometry create shape spring_damper
name of the graphics file without the .gra extension

Allows you to create the graphics spring damper object.
A spring-damper is a graphic representation of a spring and damper drawn between two markers. The spring
damper stretches along the axis created by its I and J markers.
The figure below illustrates the display options you can set.
The diameter_of_spring parameter defines the diameter of the spring, while damper_diameter_at_ij defines the
diameters of the dampers at the I and J markers.
The number of coils drawn in the spring is defined using coil_count. The distances between the ends of the
dampers and the I and J markers is defined using tip_length_at_ij. The lengths of the damper caps at the I and
J markers is defined using cup_length_at_ij.
geometry 69
Format:
spring_damper_name = new spring damper
adams_id = integer
comments = string
coil_count = integer
diameter_of_spring = length
damper_diameter_at_ij = length
tip_length_at_ij = length
cup_length_at_ij = length
Description:

spring_damper_name New Spring Damper Specifies the name of the spring-damper graphic to be
created
adams_id Integer Assigns a unique ID number to the geometry.
comments String Adds comments about the graphic that you want to
enter to help you manage and identify it.
i_marker_name Existing Marker Specifies a marker on the first of two parts connected by
this spring-damper graphic.
j_marker_name Existing Marker Specifies a marker on the second of two parts connected
by this spring-damper graphic.
coil_count Integer Enter the number of coils drawn in the spring.
diameter_of_spring Length Specifies the diameter of the spring.
geometry create shape torus

damper_diameter_at_ij Length Specifies the diameters of the damper cups in a spring-
damper graphic.
tip_length_at_ij Length Specifies the distances between the ends of the dampers
and the I and J markers.
cup_length_at_ij Length Specifies the length of the damper cups in a spring-
damper graphic.
when entering it.
be assigned to it.
Enter a 0 to have Adams Solver assign the ID for you.
3. Adams View draws this graphic between one part at the I marker and the other at the J marker.
4. For the damper_diameter_at_ij, the first value defines the diameter of the cup at the I marker. The
second value defines the diameter of the cup at the J marker.
5. For the cup_length_at_ij parameter, the first value defines the length of the cup at I marker.
AdamsAdams View measures the length from the bottom of the cup to its top along the line that I
and J define.
The second value defines the length of the cup at J. Adams View measures the length from the bottom
of the cup to the top along the line that I and J define.

Allows for creation of the torus object.
geometry 71
Format:
torus_name = a new torus
adams_id = Adams id
comments = string
side_count_for_perimeter = integer
Example:
geometry create shape torus &
torus_name = torus__1 &
comments= "a new torus" &
major_radius= 10 &
minor_radius = 5 &
side_count_for_perimeter = 10 &
segment_count = 10
Description:

torus_name A New Torus Specifies the name of the new torus
Adams data file.
modified.
angle_extent Angle Specifies a subtended angle measured positive (according
to the right-hand rule) about the z-axis of the center
marker.

major_radius Length The parameter is used to specify the radius for the
circular spine of the torus.
minor_radius Length The parameter is used to specify the radius for the
circular cross-sections of the torus.
side_count_for_perimet Integer The parameter is used to specify the number of circular
er cross-sections to create along the spine of the torus.
segment_count Integer The SEGMENT_COUNT parameter is used to specify
the number of sides for each of the circular cross-sections
of the torus.
1. A torus is defined by a circular spine with a circular cross-section at each point on the spine. The
torus is placed at the marker named 'CENTER_MARKER='. The radius for the circular spine of the
torus is defined by the MAJOR_RADIUS parameter. The radius for the circular cross-sections is
defined by the MINOR_RADIUS parameter. The number of circular cross-sections to create along
the spine may be specified with the SIDE_COUNT_FOR_PERIMETER parameter. The number
of sides for each of the circular cross-sections may be specified with the SEGMENT_COUNT
parameter. The torus will move with the part which owns the center marker.
2. You may use the name specified by the torus_name parameter, later to refer to this torus. Adams
View will not allow you to have two tori with the same full name, so you must provide a unique name.
be assigned to it.
geometry 73
geometry delete
5. The angle specified by the angle_extent parameter starts at the positive x-axis of the center marker and
subtends the arc, the arc of the cylinder, or the arc of the cone frustum.
Tips:
geometry delete
Allows you to delete an existing piece of geometry.
Format:
geometry delete
Example:
geometry delete &
geometry_name = LINK_56
Description:

geometry_name An Existing Geometric Entity Specifies the geometry to delete.
1. You must enter the name of the geometry you wish to delete by either picking it from the screen or
menu entry 'UNDO'.
You may identify geometry by typing its name or by picking it from the screen.
geometry modify curve arc
the model and part names as well. For example, you may specify arc 'end' on part 'arm' in model 'susp'
by entering ".susp.arm.end". If you type a "?", Adams View will list the geometrys available by default.
associated with it.
Cautions:
Tips:

Allows for modification of the arc object.
Format:
arc_name = an existing arc
new_arc_name = a new arc
adams_id = adams_id
comments = string
radius = length
close = arc_closure
Example:
geometry modify curve arc &
arc_nameb = ARC__1 &
new_arc_name = ARC__2 &
adams_id = 2 &
comments = "a new arc" &
geometry 75
geometry modify curve arc &

center_marker = Origin &
radius = 10 &
segment_count = 10 &
close = sector
Description:

arc_name An Existing Arc Specifies the name of an existing arc.
new_arc_name A New Arc Specifies the name of the new arc.
Adams data file.
modified.
marker
ref_radius_by_marker An Existing Marker Specifies the radius of a circle, an arc, or a cylinder to be
the distance from the center marker Z axis to this radius
marker.
segment_count Integer Specifies the number of straight line segments Adams
View uses to draw a circle or an arc.
close Arc_closure Specifies the type of closure to perform when Adams
View creates the arc.
1. Arcs are truncated circles that can be closed into a pie shape or using a cord between the end points.
An arc is a 2 dimensional graphics image which is defined as a curve with a specified radius drawn
around a center marker. The length of the arc is determined by the angle_extent, and its smoothness
by the number of segments in the arc. The radius can be given explicitly by using the 'RADIUS='
parameter, or by using the 'ref_radius_by_marker' parameter, If 'REF_RADIUS_BY_MARKER' is
used, a radius will be calculated from the center marker. An arc will move with the center marker
given in the parameter 'CENTER_MARKER'.
2. You may use this name later to refer to this arc. Adams View will not allow you to have two arcs with
the same full name, so you must provide a unique name.
be assigned to it.
7. When you specify 'NO' for the ‘close’ parameter, Adams View will create a 2 dimensional arc. 'NO'
is the default value. When you specify 'CHORD' for this parameter, Adams View will close the arc
from the starting point, to the ending point on the arc.
geometry 77
geometry modify curve bspline
When you specify 'SECTOR' for this parameter, Adams View will close the arc, such that a "pie"
shape is created.
Cautions:

Allows you to modify an existing bspline.
Format:
bspline_name = a new gcurve
adams_id = adams_id
comments = string
ref_curve_name = an existing acurve
ref_profile_name = an existing Wire_Geometry
spread_points = boolean
close = boolean
Examples:
geometry modify curve bspline &
new_bspline_name = gcurve__2 &
adams_id = 100 &
comments = "a modifed bspline" &
ref_marker_name = origin&
ref_curve_name = curve__1&
segment_count = 100

adams_id = 100 &

ref_profile_name = CHAIN_1 &
closed = yes &
Description:

bspline_name An Existing Specifies the name of an existing BSPLINE to modify
Gcurve
new_bspline_name A New Gcurve Specifies the name of the new BSPLINE.
Adams data file.
modified.
ref_curve_name An Existing Specifies an existing CURVE that will be used to create
Acurve and display the BSPLINE geometric element.
ref_marker_name An Existing Specifies an existing MARKER that will be used to
Marker locate and orient the BSPLINE geometric element.
ref_profile_name An Existing Wire Specifies an existing GWire geometry, from which to
Geometry create and display the BSPLINE geometric element.
spread_points Boolean Specifies whether the bspline be created in a way that the
points (as defined by a reference profile) are equally
spaced or otherwise. The parameter will be ignored if a
ref_curve_name is specified.
closed Boolean Specifies whether that the generated bspline is a closed
one or otherwise.
num_new_pts Integer Specifies the number of points on the created bspline.
The parameter is valid only if the spread_points
parameter is set to 'yes' (and as such can be valid only
when a reference profile is specified).
segment_count Integer Specifies the number of polynomial segments Adams
View uses for fitting the CURVE_POINTS when
FIT_TYPE is set to CURVE_POINTS.
1. To create a BSPLINE you must first create a CURVE DATA_ELEMENT or specify an existing
GWire geometry. The CURVE definition depends on first creating a MATRIX of control points or
a user-subroutine.
geometry 79
A BSPLINE is the geometric counterpart to the CURVE data_element. The difference being that the
For completeness the CURVE definition is repeated below.
A CURVE element defines a three-dimensional parametric curve that may be referenced by
parameter, u. As u varies from its minimum value to its maximum value, the functions x(u), y(u), and
z(u) sweep out points on the curve. A simple example of a parametric curve is the helix defined by
the following equations:
x = cos(u)
y = sin(u)
z = u
Adams View allows you to create curves in three ways: by entering control points for a uniform cubic
A uniform B-spline is a piecewise cubic polynomial spline used in many CAD (computer-aided-
ending at +1.
A more direct way to define the curve is to supply curve points.
In order to use a different type of curve, or to model an analytically-defined curve such as the helix,
A curve can be open or closed. A CLOSED curve meets at the ends, connecting the curve at
minimum and maximum parameter values. Note for a closed curve defined by curve points, you can
specify a maximum of 5 segments less that the number of curve points. Note that because three
segments less than the number of curve points are required for an exact fit, a closed curve will not
exactly fit the curve points.
2. You may use the name specified by the bspline_name parameter, later to refer to this BSPLINE.
Adams View will not allow you to have two BSPLINEs with the same full name, so you must provide
a unique name.
be assigned to it.
geometry 81
5. A BSPLINE is the geometric counterpart to the CURVE data_element. The difference being that
associated with it.
6. The reference marker must exist before the BSPLINE can be created.
This marker acts as a coordinate reference for the coordinate values used to define the CURVE that
acts as a template for the creation of the bspline.
A BSPLINE is the geometric counterpart to the CURVE data_element.The difference being that the
time.
7. A BSPLINE is the geometric counterpart to the CURVE data_element. The difference being that the
associated with it.
8. The segment_count parameter is not used if you have specified the FIT_TYPE as
CONTROL_POINTS.
For an open CURVE, Adams View will default to a SEGMENT_COUNT that is three less than the
number of CURVE_POINTS, which gives an exact fit to the CURVE_POINTS. Specifying fewer
segments will result in a smoother curve, but the curve will not pass exactly through the
CURVE_POINTS. You must specify at least four CURVE_POINTS to create an open curve.
than the number of CURVE_POINTS, the computed curve will exactly match the curve points. If
you specify fewer segments, Adams will use a least-squares fit to compute the closest fit to the points.
geometry 83
geometry modify curve chain
Closed curves must be defined by at least eight CURVE_POINTS, and may have a maximum of five
segments less than the number of CURVE_POINTS. For a closed curve defined by
CURVE_POINTS, Adams will default a SEGMENT_COUNT of five segments less than the
number of CURVE_POINTS.
Note that because three segments less than the number of curve points are required for an exact fit, a
closed curve will not exactly fit the curve points.
9. The 'spread_points' parameter when specified to ‘yes’, in conjunction with a reference profile
(otherwise the parameter is invalid and will be ignored) specifies that the set of points generated for
the bspline are such that they are equally spaced. Thus specifying the parameter to ‘yes’, means use of
a different algorithm for generating a bspline (from the gwire geometry), wherein all the points on the
bspline are equally spaced).
10. The 'num_new_pts' is valid only when the spread points parameter is set to ‘yes’ (otherwise the
parameter will be ignored). The parameter defines the number of points generated for the bspline
using the new algorithm. Note that the points will be equally spaced.
11. The 'closed' parameter is a Boolean value that specifies whether the generated bspline is a closed curve
or otherwise.

Format:
chain_name = a new chain
new_chain_name = a new chain
comments = string
objects_in_chain = an existing gwire
Example:
geometry modify curve chain &
chain_name = CHAIN__1 &
new_chain_name = CHAIN__2
geometry modify curve circle
Description:

chain_name A New Chain Specifies the name of the chain you want to create or
modify
new_chain_name A New Chain Specifies a new name for the geometry
modified.
objects_in_chain An Existing Gwire Specifies the geometry to be chained together
1. The geometry to be chained together must touch at one endpoint and cannot be closed geometry. It
adds the final chained geometry to the part that owns the first geometry that you selected.

Allows for modification of an existing circle object.
Format:
circle_name = an existing circle
new_circle_name = a new circle
adams_id = adams_id
comments = string
radius = length
geometry 85
Example:
geometry modify curve circle &
circle_name = circle__1 &
new_circle_name = circle__2 &
adams_id = 10 &
comments = "a modified circle" &
radius = 10 &
segment_count = 10
Description:

circle_name An Existing Circle Specifies the name of the new circle.
new_circle_name A New Circle Specifies the name of the new circle.
Adams data file
modified.
ref_radius_by_marker An Existing Specifies the radius of a circle, an arc, or a cylinder to be
Marker the distance from the center marker Z axis to this radius
marker.
segment_count Integer Specifies the number of straight line segments Adams
View uses to draw a circle or an arc.
1. The circle is segmented and therfore can look like a square or triangle if needed.
The circle is defined as a radius drawn around a center marker. The circle's orientation is dependent
upon the orientation of its center marker. Its radius is determined by either the
'REF_RADIUS_BY_MARKER' or 'RADIUS=' parameter. The number of sides on the circle is
controlled by the 'SEGMENT_COUNT=' parameter. A circle will move with the part its center
marker is located on.
2. You may use the name specified by the circle_name parameter later to refer to this circle. Adams View
will not allow you to have two circles with the same full name, so you must provide a unique name.
be assigned to it.
Cautions:
geometry 87
geometry modify curve ellipse

Allows for modification of an existing ellipse object.
Format:
ellipse_name = an existing ellipse
new_ellipse_name = a new ellipse
adams_id = adams_id
comments = string
start_angle = angle
end_angle = angle
Example:
geometry modify curve ellipse &
ellipse_name = ELLIPSE__1 &
new_ellipse_name = ELLIPSE__2 &
comments = "a modified ellipse" &
center_marker = Origin &
major_radius = 10 &
minor_radius = 6 &
start_angle = 0 &
end_angle = 180
Description:

ellipse_name An Existing Specifies an existing ellipse object
Ellipse
new_ellipse_name A New Ellipse Specifies a new ellipse object
Adams data file.
modified.
geometry modify curve outline

major_radius Length The MAJOR_RADIUS parameter is used to specify
the radius for the circular spine of the torus.
minor_radius Length The MINOR_RADIUS parameter is used to specify
the radius for the
circular cross-sections of the torus.

start_angle Angle
end_angle Angle

Allows for modification of an existing outline object.
geometry 89
Format:
outline_name = an existing outline
new_outline_name = a new outline
adams_id = adams_id
comments = string
visibility_between_markers = on_off
image_file_name = string
horizontal = clamp_repeat
vertical = clamp_repeat
close = boolean
Example:
geometry modify curve outline &
outline_name = OUTLINE__1 &
new_outline_name = OUTLINE__2 &
adams_id = 1 &
comments = "modifying an existing outline" &
marker_name = Origin , CM &
visibility_between_markers = on &
close = yes
Description:

outline_name An Existing Outline Specifies the name of an existing outline
new_outline_name A New Outline Specifies the name of a new outline
modified.
visibility_between_marker On_off Specifies whether the outline is visible between two
s markers.

image_file_name String Specifies the name of an image file on disk. File types
supported include .bmp, .jpg, .gif, and .png.
horizontal Clamp_repeat Controls how the desired polygon is horizontally
filled with the image
vertical Clamp_repeat Controls how the desired polygon is vertically filled
with the image
close Boolean Specifies the whether or not Adams View should close
the outline when it is created.
1. Outlines are line segments (open or closed) that are define by a series of markers.
An outline is composed of at least two and not more than 2500 markers. These markers are connected
by line segments to form the outline.
If all of the markers of an outline lie on the same part, the parent of the outline is this part, and the
outline moves with this part.
If some of the markers lie on different parts, the parent of the outline is the model. As the parts move,
the outline is stretched or "rubber-banded" to fit the new marker locations.
2. You may use the name specified by the new_outline_name later, to refer to this graphic. Adams View
will not allow you to have two outlines with the same full name, so you must provide a unique name.
be assigned to it.
3. Specifies the outline to modify. You use this parameter to identify the existing outline to affect with
this command.
You may identify an outline by typing its name or by picking it from the screen.
If the outline is not visible on the screen, you must type the name. You may also find it convenient
to type the name even if the outline is displayed.
geometry 91
If you created the outline by reading an Adams data set or graphics file, the outline name is the letters
OUT followed by the Adams data set outline ID number. The name of Adams GRAPHIC/101,
OUTLINE is OUT101, for example. If you created the outline during preprocessing, you gave it a
name at that time.
If an outline is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a outline under another part, for instance, you may need to enter
the model and part names as well. For example, you may specify outline 'profile' on part 'cam' from
model 'gizmo' by entering ".gizmo.cam.profile". If you type a "?", Adams View will list the outlines
Note that outlines may be children of models or parts, depending on whether all the markers are on
the same part.
You must separate multiple outline names by commas.
If the outline is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple outline picks by commas.
6. Many entities are attached to, or otherwise associated with, a specific marker. You use this parameter
to identify that marker.
time.
geometry modify curve polyline
7. When you create an outline, by default a line will be drawn between each of the markers specified.
Using the VISIBILITY_BETWEEN_MARKERS parameter, you can turn turn off the visibility
between desired markers. For example, the following commands:
model create model_name=MOD1 marker create marker=MAR1
location=1,1,0
marker create marker=MAR2 location=2,1,0 marker create
marker=MAR3
location=2,2,0 marker create marker=MAR4 location=1,2,0
geometry
create curve outline outline_name=.MOD1.ground.OUT1 &
marker_name=MAR1,MAR2,MAR3,MAR4 &
visibility_between_markers=ON,ON,OFF,ON
will draw lines from MAR1 to MAR2, and from MAR3 to MAR4 there will be no line segment from
MAR2 to MAR3.
If you specify the VISIBILITY_BETWEEN_MARKERS parameter with less values than the number
of markers, the rest of the visibilities will default to ON. If for example you have an outline with some
of the visibilities turned off and you want to turn them all on, you can specify a single ON value.
When you render the outline in solid or shaded mode, each of the contiguously visible segments will
be rendered as objets. In the above example, the outline would not be draw as a solid object, but as
two lines.
Setting the visibility to OFF for a marker is equivalent to using a negative marker id on the
OUTLINE statement in the Adams DATA SET.
8. When you specify 'NO' for the ‘close’ parameter, Adams View will create a outline through the
markers specified, and will not attempt to close the start and end points with an additional line
segment. 'NO' is the default value.
When you specify 'YES' for this parameter, Adams View will create the outline, through the markers
specified, and add an additional line segment from the end marker to the starting marker.

Specifies the POLYLINE to modify.
geometry 93
Format:
polyline_name = a existing polyline
new_polyline_name = a new polyline
comments = string
location = location
close = boolean
Example:
geometry modify curve polyline &
polyline_name = POLYLINE__1 &
location = 1,5,3 &
image_file_name = "C:\users\ashish\image"
Description:

polyline_name Existing Polyline Specifies an existing POLYLINE.
NEW_POLYLINE_NAME A New Polyline Specifies the name of the new POLYLINE.
location Location Specifies the locations to be used to define
the polyline.
path_curve An Existing Gwire Specifies the locations to be used to define
the polyline from an existing graphical
object.
Marker coordinates are with respect to.
close Boolean Specifies if the polyline is to be open or
closed
1. Specifies the POLYLINE to modify. You use this parameter to identify the existing POLYLINE to
affect with this command.
You may identify a POLYLINE by typing its name or by picking it from the screen.
If the POLYLINE is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the POLYLINE is displayed.
Since a POLYLINE can not be defined in an Adams data set or graphics file, the POLYLINE can not
be created by reading in one of these files. The only way to create a POLYLINE is to do it
interactively, by reading a command file, or by reading an IGES file. POLYLINEs are owned by
parts.
If a POLYLINE is available by default, you may identify it by entering its name only. You may need
to enter the full name of the POLYLINE if you wish to identify a POLYLINE that is not on the
default PART. For example, you may specify POLYLINE "front_face" on the part named "shell"
from the model named "test" by entering ".test.shell.front_face". If you type a "?", Adams View will
list the POLYLINEs available by default.
You must separate multiple POLYLINE names by commas.
If the POLYLINE is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You may identify a POLYLINE by typing its name or by picking it from the screen.
If the POLYLINE is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the POLYLINE is displayed.
Since a POLYLINE can not be defined in an Adams data set or graphics file, the POLYLINE can not
interactively, by reading a command file, or by reading an IGES file. POLYLINEs are owned by
parts.
If a POLYLINE is available by default, you may identify it by entering its name only. You may need
associated with it.
You need not separate multiple POLYLINE picks by commas.
3. Specifies the name of the new POLYLINE. You may use this name later to refer to this POLYLINE.
Adams View will not allow you to have two POLYLINE with the same full name, so you must provide
a unique name.
geometry 95
geometry modify feature blend
be assigned to it.
coordinate system. (See the RELATIVE_TO parameter for this command).
6. The PATH_CURVE is any member of the WIRE_GEOMETRY class (which includes arcs, circles,
spline curves, polylines and outlines). When you specify a PATH_CURVE, the values of the vertices
are extracted from the specified object and used to compose the polyline.
system is initially your model, i.e. the global coordinate system. You may change the default
8. If closed, the polyline can be filled (i.e. shaded). The end points of the polyline do not need to be
coincident for you to close it. By setting the CLOSED parameter to "YES" the two end points will
be connected with a line segment. If the CLOSE parameter is set to "NO" the polyline will appear
as a segmented curve.
Cautions:
1. You need not separate multiple POLYLINE picks by commas.

Allows you to modify a chamfer or fillet (blend) on a vertex or edge on a rigid body.
geometry modify feature hole
Format:
blend_name = an existing blend
new_blend_name = a new blend
radius1 = length
radius2 = length
Example:
geometry modify feature blend &
blend_name = blend__1 &
blend_name = blend__2 &
radius1 = 0.15
Description:

blend_name An Existing Blend Specifies the name of an existing blend to be modified.
new_blend_name A New Blend Specifies the new name of the blend being modified
radius1 Length Specifies the width of the chamfer bevel or radius of the
fillet.
radius2 Length Specifies the end radius for a fillet. Adams View uses the
value you enter for radius1 as the starting radius of the
variable fillet.

Allows you to modify a hole feature.
Format:
hole_name = an existing hole
new_hole_name = a new hole
subid = integer
center = location
countersink = boolean
geometry 97

radius = length
depth = length
Example:
geometry modify feature hole &
hole_name = hole__1 &
subid = 12 &
center = 10 , 2 , 1 &
countersink = yes &
radius = 3 &
depth = 4
Description:

hole_name An Existing Hole Specifies the name of an existing hole to be modified
new_hole_name A New Hole Specifies a new name for the hole being modified
subid Integer Specifies the Parasolid tag identifying the face on which the
hole or boss will be created.
center Location Specifies the location of the center of the hole or boss on the
object.
countersink Boolean Specifies whether to create a hole or a boss
radius Length Specifies radius of the hole or boss.
depth Length Specifies depth of the hole or the height of the boss.
1. You can use the name specified by the hole_name parameter, 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.
when entering it.
geometry modify feature thinshell
be assigned to it.
2. The countersink parameter specifies whether to create a hole or a boss:
• yes - Creates a boss.
• no - Creates a hole.
Cautions:
1. You cannot specify the radius and depth of a hole so that it splits the current geometry into two
separate geometries.

Allows you to modify an existing thinshell.
Format:
thin_shell_name = a new thin_shell
subids = integer
thickness = length
Example:
geometry modify feature thinshell &
thin_shell_name = thin_shell__1 &
subids = 10 &
thickness = 0.15
geometry 99
geometry modify point
Description:

thin_shell_name An Existing Thin_shell Specifies the name of an existing thin shell to be
modified.
new_thin_shell_nam A New Thin_shell Specifies the new name for the thinshell being
e modified.
thickness Length Specifies the thickness of the remaining shell
after you hollow the object.
1. You can use the name specified by the thin_shell_name parameter, 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.
when entering it.
be assigned to it.

Modifies an existing location in three-dimensional space upon which you can build your model.
Format:
point_name = an existing point
new_point_name = a new point
adams_id = integer
comments = string
geometry modify shape block
Example:
geometry modify point &
point_name = point__1 &
new_point_name = point__2 &
adams_id = 1 &
comments = “modifying a point” &
ref_marker_name = marker_1
Description:

point_name An Existing Point Specifies the name of the point to create or modify.
new_point_name A New Point Specifies the ‘new name’ for an existing point.
adams_id Adams_id Assigns a unique ID number to the geometry.
comments String Adds any comments about the geometry to help you manage
and identify it.
ref_marker An Existing Specifies a marker that defines the location of the point
Marker

Allows modification of the block object
Format:
block_name = an existing block
new_block_name = a new block
comments = string
corner_marker = an existing marker
diag_corner_coords = length
Example:
geometry modify shape block &
block_name = box__1 &
new_block_name = box__2 &
corner_marker = marker_82 &
diag_corner_coords = 2,4,6
geometry 101
Description:

block_name An Existing Block Specifies the block to modify
new_block_name A New Block Specifies the name of the new block
corner_marker An Existing Marker Specifies the marker that defines the anchor point for the
definition of a block.
diag_corner_coords Length Specifies the location (x, y, z) of the opposite diagonal corner
from the corner_marker for a block. These coordinates are
with respect to the corner marker x, y, and z axes. This
location, along with the corner_marker, define the
boundaries of the block.
1. A block is a box with parallel edges and orthogonal vertices. You position and orient a block by means
of a corner marker. You specify the dimensions of the box by supplying three coordinates for the
opposite corner.
2. Specifies the block to modify. You use this parameter to identify the existing block to affect with this
command.
You may identify a block by typing its name or by picking it from the screen.
If the block is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the block is displayed.
If you created the block by reading an Adams data set or graphics file, the block name is the letters
BOX followed by the Adams data set block ID number. The name of Adams GRAPHIC/101, BOX
is BOX101, for example. If you created the block during preprocessing, you gave it a name at that
time.
If a block is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a block under a different part, for instance, you may need to enter the
model and part names as well. For example, you may specify block 101 from the model named test,
on the part name arm, by entering ".test.arm.box101". If you type a "?", Adams View will list the
blocks available by default.
You must separate multiple block names by commas.
If the block is visible in one of your views, you may identify it by picking it.
3. Specifies the name of the new block. You may use this name later to refer to this block. Adams View
will not allow you to have two blocks with the same full name, so you must provide a unique name.
geometry modify shape cylinder
be assigned to it.
4. These coordinates are with respect to the corner marker x, y, and z axes. This location, along with
the corner_marker, define the boundaries of the block.
Cautions:
1. You need not separate multiple block picks by commas.

Allows modification of the cylinder object.
Format:
cylinder_name = an existing cylinder
new_cylinder_name = a new cylinder
adams_id = adams_id
comments = string
length = length
radius = length
geometry 103
Example:
geometry modify shape cylinder &
cylinder_name = CYLINDER__1 &
new_cylinder_name = CYLINDER__2 &
angle_extent = 60 &
length = 25 &
ref_radius_by_marker = MARKER_72
Description:

cylinder_name An Existing Cylinder Specifies the cylinder to modify
new_cylinder_name A New Cylinder A NEW CYLINDER
modified.
center_marker An Existing Marker Specifies the marker at the center of a circle, an arc,
the bottom of a cylinder, or the bottom of a frustum
the center marker.
Radius Length Specifies the radius of a circle, an arc, or a cylinder.
ref_radius_by_marker An Existing Marker Specifies the radius of a circle, an arc, or a cylinder to
be the distance from the center marker Z axis to this
radius marker.
side_count_for_body Integer Specifies the number of flat sides Adams View draws
on a cylinder or a frustum.
View uses to draw the circles at the ends of a cylinder
or a frustum.
1. A cylinder is an extruded circle whose top and bottom are perpendicular to the cylinder central axis.
The cylinder is placed at the marker named 'CENTER_MARKER='. The circles at the top and at
the bottom of the cylinder have a radius specified by a radius, or radius reference marker. The
cylinder length is along the the positive z-axis of the center marker, and is specified by 'LENGTH='.
The number of sides can be chosen using the 'SIDE_COUNT_FOR_BODY' parameter. The
number of edges on the end circles can be specified using the 'SEGMENT_COUNT_FOR_END='
parameter. The cylinder will move with the part who owns the center marker.
2. Specifies the cylinder to modify. You use this parameter to identify the existing cylinder to affect with
this command.
You may identify a cylinder by typing its name or by picking it from the screen.
If the cylinder is not visible on the screen, you must type the name.You may also find it convenient
to type the name even if the cylinder is displayed.
If you created the cylinder by reading an Adams data set or graphics file, the cylinder name is the
letters CYL followed by the Adams data set cylinder ID number. The name of Adams
GRAPHIC/101, CYLINDER is CYL101, for example, If you created the cylinder during
If a cylinder is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a cylinder under a different part, for instance, you may need to
enter the part and model names as well. For example, you may specify cylinder 'rod' on part 'arm' in
model 'test' by entering ".test.arm.rod". If you type a "?", Adams View will list the cylinders available
by default.
You must separate multiple cylinder names by commas.
If the cylinder is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
3. Specifies the name of the new cylinder. You may use this name later to refer to this cylinder. Adams
View will not allow you to have two cylinders with the same full name, so you must provide a unique
name.
assumed.You may, or course, delete this name and use your own. The form of a full name is:
geometry 105
geometry modify shape ellipsoid
the center marker.
9. Adams View stores the radius value, not the marker name. If you later move this marker, the radius
will not change.
Cautions:
1. You need not separate multiple cylinder picks by commas.

Allows modification of the ellipsoid object.
Format:
ellipsoid_name = existing ellipsoid
new_ellipsoid_name = a new ellipsoid
comments = string
x_scale_factor = length
y_scale_factor = length
z_scale_factor = length
Example:
geometry modify shape ellipsoid &
ellipsoid_name = ellipsoid__1 &
new_ellipsoid_name = ellipsoid__2 &
center_marker = marker_74 &
x_scale_factor = 2
Description:

ellipsoid_name An Existing Ellipsoid Specifies the ellipsoid to modify.
new_ellipsoid_name A New Ellipsoid Specifies the name of the new ellipsoid
modified.
bottom of a cylinder, or the bottom of a frustum
x_scale_factor Length The X_SCALE_FACTOR parameter is used to specify
the scaling of the initial unit sphere along the center
marker's x axis.
y_scale_factor Length The Y_SCALE_FACTOR parameter is used to specify
marker's y axis.
z_scale_factor Length The Z_SCALE_FACTOR parameter is used to specify
marker's z axis.
geometry 107
1. An ellipsoid is a unit sphere that has been scaled in the x, y, and z directions. The ellipsoid is placed
at the marker named 'CENTER_MARKER='. The X_SCALE_FACTOR, Y_SCALE_FACTOR,
and Z_SCALE_FACTOR parameters are used to specify the scaling of the initial unit sphere along
the center marker's x, y, z axes. The ellipsoid will move with the part which owns the center marker.
2. You use this parameter to identify the existing ellipsoid to affect with this command.
You may identify a ELLIPSOID by typing its name or by picking it from the screen.
If the ELLIPSOID is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the ELLIPSOID is displayed.
Since a ELLIPSOID can not be defined in an Adams data set or graphics file, the ELLIPSOID can
not be created by reading in one of these files. The only way to create a ELLIPSOID is to do it
interactively or by reading a command file. ELLIPSOIDs are owned by parts.
If a ELLIPSOID is available by default, you may identify it by entering its name only. You may need
to enter the full name of the ELLIPSOID if you wish to identify a ELLIPSOID that is not on the
default PART. For example, you may specify ELLIPSOID "blimp" on the part named "par1" from
the model named "test" by entering ".test.par1.blimp". If you type a "?", Adams View will list the
ELLIPSOIDs available by default.
You must separate multiple ELLIPSOID names by commas.
If the ELLIPSOID is visible in one of your views, you may identify it by picking on any of the
3. Specifies the name of the new ellipsoid. You may use this name later to refer to this ellipsoid. Adams
View will not allow you to have two ellipsoids with the same full name, so you must provide a unique
name.
be assigned to it.
geometry modify shape extrusion
5. Specifies the marker at the center of a circle, an arc, the bottom of a cylinder, or the bottom of a
frustum. If you are creating a circle or an arc, orient the center marker so that its z-axis is normal to
the plane of the circle or to the plane of the arc. Similarly, if you are defining a cylinder or a frustum,
orient the center marker so that its z-axis is normal to the bottom of the cylinder or the frustum.
Cautions:
1. You need not separate multiple ELLIPSOID picks by commas.

Allows for modification of the extrusion object.
Format:
extrusion_name = an existing extrusion
new_extrusion_name = a new extrusion
adams_id = adams id
comments = string
path_points = location
length_along_z_axis = length
Example:
geometry modify shape extrusion &
extrusion_name = extrusion__1 &
new_extrusion_name = extrusion__2&
geometry 109
geometry modify shape extrusion &

comments = “a modified extrusion” &
profile_curve = arc__1 &
path_curve = circle__1 &
analytical = no
Description:

extrusion_name An Existing Specifies the name of an existing extrusion.
Extrusion
new_extrusion_name A New Extrusion Specifies the name of the new extrusion.
Adams data file.
modified.
reference_marker An Existing Specifies the marker used to place and orient an
Marker extrusion.
extrusion.
extrusion. The points are relative to the extrusion's
reference marker.
path_curve An Existing Gwire Specifies the object used to define the path of the
extrusion.
path_points Location Specifies the points used to define the path of the
extrusion.
length_along_z_axis Length Specifies the legth along the Z axis of the reference
marker to extrude the profile curve of the extrusion.
relative_to An Existing Specifies the coordinate system that location
Model, Part Or coordinates are with respect to.
Marker
analytical Boolean
1. An extrusion is defined by a path polyline curve and a profile curve, which may be either a polyline
or a data element curve. The profile curve is in the X-Y plane of its parent part. Z coordinate values
of the profile curve are ignored. The path curve is a polyline that describes how the profile will be
swept along. The extrusion is placed with respect to the marker named 'REFERENCE_MARKER='
using the same orientation that the path curve has with respect to its parent part. The extrusion will
move with the part which owns the reference marker.
2. You may use the name specified by the extrusion_name parameter, later to refer to this extrusion.
Adams View will not allow you to have two extrusions with the same full name, so you must provide
a unique name.
be assigned to it.
4. You may specify an arc, circle, spline curve, polyline, or outline for the path_curve parameter. The
object defines the path along which the profile curve will be swept.
5. The points specified by the path_points parameter are relative to the extrusion's reference marker.
The points defines the path along which the profile curve will be swept.
geometry 111
geometry modify shape force
7. The extrusion can be created by selecting points on screen, Gwire, polyline or a Gcurve. But, in
Adams Solver data file, it is necessary to represent the profile/path in the form of a unique curve for
each profile and path. If the selected profile/path is other than a Gcurve (points_on_screen, Gwire,
polyline, length_along_Z) Adams creates two Gcurves (generator_profile and generator_path
respectively) from the selected profile/path. If the selected profile/path is a Gcurve then
generator_profile/generator_path refer to the same. These Gcurves are replica of the user-selected
geometry and are superimposed on the same. The visibility attribute of the Gcurve is adjusted to be
off to avoid the user from selecting hot-points on Gcurves. This setting will enable the user to select
the hot-points on profile/path geometry.
Tips:
1. You may specify an arc, circle, spline curve, polyline, or outline for the profile_curve parameter The
object should be in the X-Y plane of the extrusions reference marker.

Allows you to modify a force graphic on an element. Force graphics are arrows whose magnitudes and
directions reflect the scaled relative magnitudes and directions of the force vectors acting on your model
during a simulation.
Force graphics help you gauge how large your forces become and in what directions they are applied during
a simulation.
Figure 2 Force Graphics on an Animation
To see force graphics during animations, you must specify those force elements in your model for which you
would like to see the associated force graphics. To turn force graphics on or off for particular forces, refer to
the Adams View documentation that describe how to modify a force or a motion.
You can specify the following for the display of force graphics during an animation:
 Scale factor used to control the graphic’s relative size compared to the objects in the model.
 Whether or not the force magnitudes are displayed numerically. The numerical values appear near
the arrowheads.
 Whether or not the force graphics are drawn in wireframe or shaded mode when the model is
animated in shaded mode.
 Whether the force graphic is always drawn in front of other geometry. This is particularly useful
when viewing forces inside geometry, such as three-dimensional contacts.
There are two different scale factors: one for forces and one for torques. Adams applies the force scale
factor to all force graphics in your model to maintain their proper relative sizing, while it applies the
torque scale factor to all torque graphics in your model.
Finding force and torque scale factors that are good for the entire animation might require some trial
and error. It is often useful to set your scale factors while viewing the frame for which the largest force
reaches its peak value.
Format:
force_name = existing force symbol
new_force_name = new name for force symbol
adams_id = integer
comments = string
force_element_name = existing force
jprim_name = existing primitive joint
all_force_elements = true_only
applied_at_marker_name = existing triad
Example:
geometry modify shape force &
force_name = force_1_1 &
new_force_name = force_graphics_1 &
force_element_name = vforce_1 &
applied_at_marker_name = marker_4
geometry 113
Description:

Force_name Existing Force Symbol Specifies the name of the force graphic to be
modified
New_force_name New Name For Force Specifies the new name of the force symbol.
Symbol
Adams_id Integer Specifies a new name for the geometry. Assigns a
unique ID number to the geometry.
Comments String Adds comments about the geometry to help you
manage and identify it.
Force_element_name Existing Force Specifies the name of the force element whose
Joint_name Existing Joint Specifies the name of the joint element whose
Jprim_name Existing Primitive Joint Specifies the name of the joint primitive element
whose force the force graphic is to be displayed.
Curve_curve_name Existing Ccurve Specifies the name of the curve_curve element
Point_curve_name Existing Pcurve Specifies the name of the point_curve element
All_force_elements True Specifies that all the forces from all the force
elements acting on the marker that
applied_at_marker_name specifies are summed
together to determine the force that the force
graphic displays. The only value allowed is true.
There must be at least one force element acting
on the marker.
Applied_at_marker_name Existing Triad Specifies the name of the marker where Adams
View displays the force graphic.
when entering it.
be assigned to it.
2. The force element can be:
• Beam
• Bushing
• Field
• Translational spring damper
• Rotational spring damper
• Tire
• Single-component force
• Force vector
• Torque vector
• General force
• Multi-point force
3. The joint element can be:
• Translational
• Revolute
• Cylindrical
• Univesal
• Spherical
• Planar
• Rackpin
• Screw
4. The joint primitive element can be:
• At point
• Inline
• Inplane
• Orientation
• Parallel_axis
geometry 115
geometry modify shape frustum
• Perpendicular
5. If you use the all_force_elements=true argument, the marker must have at least one force applied to it.
If you enter a specific force type using joint_name, jprim_name, force_element_name, point_curve_name, or
curve_curve_name parameters, then the marker named in this parameter must be one of the markers
on which the specified force acts.

Allows for the modification of the frustum object.
Format:
frustum_name = an existing frustum
new_frustum_name = a new frustum
adams_id = adams_id
comments = string
length = length
top_radius = length
bottom_radius = length
Example:
geometry modify shape frustum &
frustum_name = frustum__1 &
new_frustum_name = frustum__2&
adams_id = 101 &
comments = "a modified frustum" &
length = 10 &
side_count_for_body = 10
Description:

frustum_name An Existing Frustum Specifies the name of an existing frustum
new_frustum_name A New Frustum Specifies the name of the new frustum
the Adams data file
modified.
center_marker An Existing Marker Specifies the marker at the center of a circle, an arc,
the bottom of a cylinder, or the bottom of a frustum.
the center marker.
side_count_for_body Integer Specifies the number of flat sides Adams View draws
on a cylinder or a frustum.
top_radius Length Specifies the radius at the top of a frustum.
bottom_radius Length Specifies the radius at the bottom of a frustum.
View uses to draw the circles at the ends of a cylinder
or a frustum.
1. . A frustum is a specialized cone whose top and bottom are perpendicular to the cone central axis. A
frustum will move with the part that the center marker belongs to.
2. You may use the name specified by the frustum_name parameter later to refer to this frustum. Adams
View will not allow you to have two frustums with the same full name, so you must provide a unique
name.
geometry 117
geometry modify shape gcontact
be assigned to it.
the center marker.
7. The top of the furstum is perpendicular to the center marker z-axis, and the center of the top is at the
position on the center marker z-axis that LENGTH specifies. Also, The bottom is perpendicular to
the center marker z-axis, and the center of the bottom is at the center marker origin.

Allows you to modify an existing contact force graphic object.
Format:
contact_force_name = an existing contact_force_graphic
new_contact_force_name = a new contact_force_graphic
adams_id = adams_id
comments = string
contact_element_name = an existing contact element
force_display = force_display_options
Example:
geometry modify shape gcontact &
contact_force_name = gcontact__1 &
new_contact_force_name = gcontact__2 &
adams_id = 1 &
comments = "a modified contact force graphic" &
contact_element_name = sphere_plane_contact_5 &
force_display = both
Description:

contact_force_name An Existing Specifies the name of an existing contact
Contact_force_graphic force graphic to be modified
new_contact_force_name A New Contact_force_graphic Specifies the name of a new contact force
graphic
adams_id Adams_id Assigns a unique ID number to the
geometry
comments String Adds any comments about the geometry
to help you manage and identify it.
contact_element_name An Existing Contact Element Specifies the name of the contact element
whose force is to be displayed by the force
graphic.
force_display Force_display_options Specifies the options for displaying the
force graphics
geometry 119
geometry modify shape link
A gcontact is a force graphic for a contact element. The gcontact can display graphics for component or
aggregate forces of a contact.
 none - Displays no force graphics.
 components - Displays force graphics for the normal force, friction force, and torque at each
incident of a contact for each frame. Multiple incidents at a frame display multiple force graphics.
 aggregate - Displays force graphics for the sum of all forces (normal and friction) and all torques on
the contact at each frame. Sums multiple incidents at a frame and displays one force graphic.
 both - Displays both component and aggregate force graphics.

Allows for creation of the link object.
Format:
link_name = an existing glink
new_link_name = a new glink
comments = string
i_marker = an existing marker
j_marker = an existing marker
width = length
depth = length
Example:
geometry modify shape link &
link_name = link__1 &
comments = "a modified link" &
i_marker = mk124 &
j_marker = mk112 &
width = 25 &
depth = 5
Description:

link_name An Existing Glink Specifies the name of an existing link
new_link_name A New Glink Specifies the name of the new link
modified.
i_marker An Existing Specifies the marker at one end of a link object.
Marker
j_marker An Existing Specifies the marker at one end of a link object.
Marker
width Length Specifies the width of the link.
depth Length Specifies the depth of the link.
1. A link is a three-dimensional object used to represent a connecting part. It has its length defined by
the distance between I_MARKER and the J_MARKER. It also has a WIDTH and DEPTH that
may be specified. The ends of the link are semi-circular. The J_MARKER must lie in th XY plane
of the I_MARKER.
2. You may use the name specified by the link_name parameter later, to refer to this link. Adams View
will not allow you to have two links with the same full name, so you must provide a unique name.
be assigned to it.
geometry 121
geometry modify shape nurb_surf
Cautions:
i_marker.
i_marker.

Modifies an existing nurb surface.
Format:
nurb_surf_name = existing surf_name
new_nurb_surf_name = new surf_name
comments = string
udegree = integer
vdegree = integer
rational = boolean
uperiodic = boolean
vperiodic = boolean
num_uctrlpts = integer
num_vctrlpts = integer
weights = real
uknots = real
vknots = real
geometry modify shape picture
Description:

nurb_surf_name Existing Surface Specify an existing nurb surface that has to be
modified.
New_nurb_surf_name New Name For The Surface Specify the new name for the nurb surface.
comments String Specify any comments to be associated with the
nurb surface geometry created.
udegree Integer Specify an integer greater than 0 and less than or
equal to 20.
vdegree Integer Specify an integer greater than 0 and less than or
equal to 20.
rational Yes/no Specify a Boolean value
uperiodic Yes/no Specify a Boolean value
vperiodic Yes/no Specify a Boolean value
num_uctrlpts Integer Specify the number of control points.
num_vctrlpts Integer Specify the number of control points.
control_points Location Specify the location of the control points.
weights Real Specify the weight.
uknots Real Specify a real number
vknots Real Specify a real number
geometry modify shape picture

Allows you to modify a picture.
Format:
geometry modifies shape picture
picture_name = existing picture
new_picture_name = new picture
image_file_name = name of image
height = integer
location = location
geometry 123
geometry modify shape plane
Example:
geometry modify shape picture &
picture_name = picture_1 &
image_file_name= "c:\documents and settings\car.jpg" &
height= 50
Description:

picture_name Existing Picture Specifies the picture to be modified
New_picture_name New Name For The Picture Specifies the new name for the picture.
image_file_name String Specifies the file name containing the
image.
height Integer Specifies the height of the picture
location Location Specifies the location of the picture
Allows you to modify a two-dimensional box .
Plane Tool is a two-dimensional box that gets created. You can draw a plane’s length and width in the plane
of the screen or the working grid, if it is turned on. You will find planes most useful when you are creating
contact forces between objects
When you create a plane, you can select to create a new part consisting of the plane geometry or add the plane
geometry to an existing part or ground. If you create a new part, it has no mass since it is composed only of
wire geometry.
Format:
plane_name = existing plane
new_plane_name = new name for the plane
adams_id = integer
comments = string
x_minimum = real

x_maximum = real
y_minimum = real
y_maximum = real
Example:
geometry modify shape plane &
plane_name = plane_1 &
ref_marker_name = marker_5 &
x_minimum = 100 &
x_maximum = 500.9 &
y_minimum = 100 &
y_maximum = 788
Description:

plane_name Existing Plane Name Specifies the name of the plane to be modified
new_plane_name New Name For The Plane Specifies a new name for the geometry.
adams_id Integer Assigns a unique ID number to the plane.
Comments String Adds comments about the plane that you want to enter
to help you manage and identify it.
ref_marker_name Existing Marker Specifies the reference marker used to locate and orient
the plane.
x_minimum Real Specifies the location of one corner of the plane in
coordinates relative to the reference marker
x_maximum Real Specifies the location of the opposite corner of the plane
in coordinates relative to the reference marker.
y_minimum Real Specifies the location of one corner of the plane in
coordinates relative to the reference marker. If all values
are positive, the values indicate the lower left corner of
the plane.
y_maximum Real Specifies the location of the opposite corner of the plane
in coordinates relative to the reference marker.
geometry 125
geometry modify shape plate
when entering it.
be assigned to it.
4. If all values of x_minimum,y_minimum,x_maximum,y_maximum are positive, the values indicate
the lower left corner of the plane. For example, the values of x_minimum = 10 and y_minimum =
20, place the lower left corner at 10,20 in the reference marker's coordinate system.

Allows you to modify a plate object.
Format:
plate_name = an existing plate
new_plate_name = a new plate
comments = string

width = length
radius = length
Example:
geometry modify shape plate &
plate_name = plate__1 &
new_plate_name = plate__2 &
comments = "a new plate" &
marker_name = mk112 , mk124 , cm &
width = 15 &
radius = 5
Description:

plate_name An Existing Plate Specifies an existing plate object
new_plate_name A New Plate Specifies a new plate object
modified.
width Length Specifies the width of the plate
radius Length Specifies the plate radius
2. Many entities are attached to, or otherwise associated with, a specific marker. You use the
marker_name parameter to identify that marker.
geometry 127
geometry modify shape revolution
name at that time.

Allows for modification of the revolution object.
Format:
revolution_name = an exsiting revolution
new_revolution_name = a new revolution
adams_id = adams id
comments = string
number_of_sides = integer
Example:
geometry modify shape revolution &
revolution_name = revolution__1 &
new_revolution_name = revolution__2 &
comments = “a modified revolution” &
geometry modify shape revolution &

profile_curve = circle__1 &
angle_extent = 50 &
number_of_sides = 10 &
analytical = no
Description:

revolution_name An Existing Specifies the name of an existing revolution.
Revolution
new_revolution_name A New Revolution Specifies the name of the new revolution.
Adams data file.
modified.
reference_marker An Existing Specifies the marker used to place and orient a
Marker revolution.
revolution.
revolution.
marker.
number_of_sides Integer Specifies the number of flat sides Adams View draws on
a revolution.
relative_to An Existing Specifies the coordinate system that location coordinates
Model, Part Or are with respect to.
Marker
analytical Boolean
1. For more detail about revolutions, see Revolution Tool dbox help.
geometry 129
geometry modify shape shell
2. A revolution is defined by a profile polyline curve which is revolved about the Z axis of the marker
named 'REFERENCE_MARKER='. The profile curve is a polyline that is in the X-Y plane of its
parent part. Z coordinate values of the profile curve are ignored. The revolution will move with the
part which owns the reference marker.
3. You may use the name specified by the revolution_name parameter, later to refer to this revolution.
Adams View will not allow you to have two revolutions with the same full name, so you must provide
a unique name.
be assigned to it.
5. For the profile_curve parameter, you may specify an arc, circle, spline curve, polyline, or outline. The
coordinates of the object points, relative to the object's parent part, will be used to define a profile
relative to the revolution's reference marker. The profile defined by the points will be swept around
the reference marker's z-axis.
Tips:

Allows you to modify an existing shell object.
Format:
shell_name = an existing shell
new_shell_name= a new shell
comments = string
file_name = string
wireframe_only = boolean
Example:
geometry create shape shell &
shell_name = shell__1 &
comments = "a new shell" &
reference_marker = mk112&
file_name = "c:\shell1.shl"&
wireframe_only = no
Description:

shell_name An Existing Shell Specifies the name of an existing shell.
new_shell_name A New Shell Specifies the name of the new shell.
modified.
reference_marker An Existing Marker Specifies the marker used to place and orient a shell.
file_name String Specifies the name of a file that contains the
definition of the shell.
wireframe_only Boolean
1. A shell is defined by a number of node points and the connectivity between those node points. The
shell is represented as polygons defined by connecting node points with straight line segments.
Polygons are not necessarily flat. The points and connectivety are read from a file named
"FILE_NAME=". The shell is placed at the marker named "REFERENCE_MARKER=". The shell
will move with the part that owns the reference marker.
2. You may use the name specified by the shell_name parameter, later to refer to this shell. Adams View
will not allow you to have two shells with the same name, so you must provide a unique name.
geometry 131
be assigned to it.
Shell file format: The first line in a shell file has the form: int int float. The first integer represent how
many points are in the shell file. The second integer represents how many polygons are described in
the file. The float value represent a scaling factor which is applied to all of the point coordinates.
The lines immediately following the first line consist of the x, y, and z coordinate floating point values
for the points. There is one xyz triplet per line. You may use multiple spaces or tabs to separate the
x, y, and z values.
Immediately following the coordinate values are the lines for defining the polygon connectivity. The
first number on one of these lines is the number of vertices that should be connected to form the
polygon.
The following integers are the offsets into the list of points. For example, 4 5 6 2 1 means that
the polygon will be formed by 4 points and those points are the 5th, 6th, 2nd, and 1st points in the
list of points in the shell file. Note that it is not necessary to explicitly close each polygon by going
back to the start point. You may use multiple spaces or tabs to separate the values.
A sample shell file for a cube:
861.0
-1.0-1.01.0
-1.0 1.0 1.0
geometry modify shape solid_shell
1.0 1.0 1.0

1.0 -1.01.0
-1.0-1.0 -1.0
-1.0 1.0 -1.0
1.0 1.0 -1.0
1.0 -1.0 -1.0
41234
45621
3267
43784
41485
48765

Allows you to modify a solid shell. A solid shell is an internal function used to map STEP and IGES faces to
view. The solid shell object was created to combine a number of these faces as a solid.
Surface-based solid modeling is the least common modeling method used to define solids. Using this method,
the solid is defined as the internal volume surrounded by the defining surfaces
Format:
solid_shell_name = existing solid_shell
new_solid_shell_name = new name for the solid_shell
faces = existing face
Example:
geometry modify shape solid_shell &
solid_shell_name = solid_shell_1 &
faces = face_1
Description:

solid_shell_name Existing Solid Shell Specifies the name of the solid to be modified
new_solid_shell_name New Solid_shell Name Specify new name for the solid shell
faces Existing Face Specifies the faces making up the solid shell.
geometry 133
when entering it.
be assigned to it.
geometry modify shape spring_damper

Allows you to modify the graphics spring damper object.
A spring-damper is a graphic representation of a spring and damper drawn between two markers. The spring
damper stretches along the axis created by its I and J markers.
The equation below illustrates the display options you can set.
E
G = ---------------------
2(1 + υ)
The figure below illustrates the display options you can set.
The diameter_of_spring parameter defines the diameter of the spring, while damper_diameter_at_ij defines the
diameters of the dampers at the I and J markers.
The number of coils drawn in the spring is defined using coil_count. The distances between the ends of the
dampers and the I and J markers is defined using tip_length_at_ij. The lengths of the damper caps at the I and
J markers is defined using cup_length_at_ij.
Format:
spring_damper_name = existing spring damper
new_spring_damper_name = new name for damper
adams_id = integer
comments = string
coil_count = integer
diameter_of_spring = length
damper_diameter_at_ij = length
tip_length_at_ij = length
cup_length_at_ij = length
geometry 135
Description:

spring_damper_name Existing spring damper Specifies the name of the spring-damper
graphic to be modified
New_spring_damper_name New spring damper Specifies the new name of the spring-damper
graphic.
adams_id Integer Assigns a unique ID number to the
geometry.
comments String Adds any comments about the graphic that
you want to enter to help you manage and
identify it.
connected by this spring-damper graphic.
connected by this spring-damper graphic.
coil_count Integer Enter the number of coils drawn in the
spring.
diameter_of_spring Length Specifies the diameter of the spring.
E
G = ---------------------
2(1 + υ)
damper_diameter_at_ij Length Specifies the diameters of the damper cups in

a spring-damper graphic.
tip_length_at_ij Length Specifies the distances between the ends of
the dampers and the I and J markers.
cup_length_at_ij Length Specifies the length of the damper cups in a
spring-damper graphic.
when entering it.
be assigned to it.
3. Adams View draws this graphic between one part at the I marker and the other at the J marker.
4. For the damper_diameter_at_ij, the first value defines the diameter of the cup at the I marker. The
second value defines the diameter of the cup at the J marker.
5. For the cup_length_at_ij parameter, the first value defines the length of the cup at I marker. Adams
View measures the length from the bottom of the cup to its top along the line that I and J define.
The second value defines the length of the cup at J. Adams View measures the length from the bottom
of the cup to the top along the line that I and J define.
geometry 137
geometry modify shape torus

Allows for modification of an existing torus object.
Format:
torus_name = an existing torus
new_torus_name = a new torus
adams_id = Adams id
comments = string
side_count_for_perimeter = integer
Example:
geometry modify shape torus &
torus_name = torus__1 &
new_torus_name = torus__2 &
comments = "a modified torus" &
major_radius = 10 &
minor_radius = 5 &
side_count_for_perimeter = 10 &
segment_count = 10
Description:

torus_name An Existing Torus Specifies the name of the new torus
new_torus_name A New Torus Specifies the name of the new torus
Adams data file.
modified.
marker.
major_radius Length The parameter is used to specify the radius for the circular
spine of the torus.
minor_radius Length The parameter is used to specify the radius for the circular
cross-sections of the torus.
side_count_for_perimete Integer The parameter is used to specify the number of circular
r cross-sections to create along the spine of the torus.
segment_count Integer The SEGMENT_COUNT parameter is used to specify
the number of sides for each of the circular cross-sections
of the torus.
1. A torus is defined by a circular spine with a circular cross-section at each point on the spine. The
torus is placed at the marker named 'CENTER_MARKER='. The radius for the circular spine of the
torus is defined by the MAJOR_RADIUS parameter. The radius for the circular cross-sections is
defined by the MINOR_RADIUS parameter. The number of circular cross-sections to create along
the spine may be specified with the SIDE_COUNT_FOR_PERIMETER parameter. The number
of sides for each of the circular cross-sections may be specified with the SEGMENT_COUNT
parameter. The torus will move with the part which owns the center marker.
2. You may use the name specified by the torus_name parameter, later to refer to this torus. Adams
View will not allow you to have two tori with the same full name, so you must provide a unique name.
geometry 139
be assigned to it.
5. The angle specified by the angle_extent parameter starts at the positive x-axis of the center marker and
subtends the arc, the arc of the cylinder, or the arc of the cone frustum.
Tips:
graphic_results 1
graphic_results animate
graphic_results
Allows you to view a pseudo dynamic representation of the model motion simulated with Adams.
Format:
time_range = time
offset = location
fullscreen_animation = on_off
bitmap_animation = bitmap_opts
record_to_laser_disc = on_off
animate_page = boolean
Example:
graphic_results animate &
increment_frame_by = 2 &
base_marker = psmar &
fullscreen_animation = on &
icon_visibility = on &
colors = plum &
graphic_results animate &

contour_plots = off &
superimposed = on
Description:

analysis_name An Existing Analysis This parameter specifies an analysis name. When
Adams View reads a graphics file (.GRA), a request
file (.REQ), or a results file (.RES) an analysis name
is created. By default, the name of the analysis is the
view_name An Existing View Specifies the view for the display
number_of_cycles Integer Parameter used to specify the number of complete
cycles to animate. This means, based on this
parameter, the animation will continuously run
through all the specified frames, the specified number
of times.
increment_frame_by Integer Parameter used to specify the number of frames to
skip between each animation step. 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.
time_range Time Parameter to specify the analysis output Adams
simulation output time steps at which to start and
stop the animation (in that respective order).
frame_range Integer Parameter to specify the analysis frame number
(output time step) at which to start and stop the
animation (in that respective order).
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
one another.
base_marker An Existing Marker This parameter is used to specify a marker whose
position will be frozen in the view as the model
animates
camera_ref_marker An Existing Marker This parameter is used to identify a marker which
specifies the viewing direction as the model animates.
graphic_results 3

point_trace_marker An Existing Marker This parameter is used to specify 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.
offset Location Specifies the offset of the axis line from the plot
border.
colors An Existing Color Modify the red, green, and blue components of
existing colors.
fullscreen_animation On_Off Specifies the animation should be done using the
entire application window.
bitmap_animation Bitmap_Opts Specifies options regarding generating and replaying
a bitmap animation.
record_to_laser_disc On_Off Causes a single video frame to be recorded on the laser
disc.
animate_page Boolean
1. Animation is created by requesting a series of "frames" (or a "time range" corresponding to a series of
frames) to be displayed in rapid succession. These frames correspond to pictures of the model at each
output time step in the Adams simulation. The speed of the animation depends on the hardware
Adams View is running on, the complexity of the graphics being displayed, and the draw mode of the
graphics being displayed (wireframe, solid filled, or shaded; wireframe being the fastest).
2. Adams View provides various options for specifying how the animation frames are to be displayed.
These options include starting and ending frame number or time, the number of frames (simulation
output time steps) to be skipped between displayed frames, the number of complete cycles the
animation should go through, etc. If none of these options are specified, the system will animate in
the active view, use all frames, and cycle through them once. Other advanced features are provided
such as BASE_MARKER, SUPERIMPOSE, CAMERA_REF_MARKER, and
POINT_TRACE_MARKER, which are not used unless specified. These options provide:
- BASE_MARKER - a way to freeze a model position in the view during the animation
- SUPERIMPOSE - overlaying the frames of the animation,
- CAMERA_REF_MARKER - a model mounted viewing position,
- POINT_TRACE_MARKER - tracing marker paths during the animation in respective order, and
- CAMERA_REF_MARKER + BASE_MARKER - a view direction from the camera marker to the
base marker.
3. Adams View requires that Adams simulations have unique names and the default name of an analysis
may be overridden when reading the file(s) using the file_nameparameter. When referring to an
analysis name that already exists quotes are not necessary. When processing any command that
requires an analysis name the system will default to the default analysis name. The default analysis
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.
5. If entered, the NUMBER_OF_CYCLES parameter must be a positive integer. This value will be
optional and if not entered, will default initially to 1 (until updated by the user).
6. If entered, the INCREMENT_FRAMES_BY parameter must have an absolute value less than the
to 1.
7. If entered, the 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 end in 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).
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.
8. If entered, the frame_range 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 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).
graphic_results 5
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
This is an optional parameter and if not entered, then no superimposed frames will be drawn. The
the animation. OFF, the default, indicates that frames will not be superimposed during theanimation.
10. The base_marker parameter is used to specify a marker whose position will be frozen in the view as
the model animates. 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. You may identify a marker by typing its name or by picking it from the screen. If the marker
is not visible on the screen, you must type the name. You may also find it convenient to type the name
even if the marker is displayed. If you created the marker by reading an Adams data set or graphics
file, the marker name is the letters MAR followed by the Adams data set marker ID number. For
example, the name ofAdams MARKER/101 is MAR101. If you created the marker during
preprocessing, you will have given it a name at that time. If a marker is available by default, you may
identify it by entering only its name. If it is not, you must enter its full name. To identify a marker
under a different part, for instance, you may need to enter the model and part names, as well. For
example, you may specify marker 'pivot' from model 'links', part 'lower_arm' by entering
".links.lower_arm.pivot". If you type a "?", Adams View will list the markers available by default. You
must separate multiple marker names by commas. If the marker is visible in one of your views, you
may identify it by picking on it. You need not separate multiple marker picks by commas.
11. The camera_ref_marker parameter connects the viewing camera to the "z" axis of a marker. The
animation is then viewed from the moving location of that marker in the "z" direction. This is
particularly useful when a "drivers eye" or "pilots eye" viewing perspective is desired. This parameter
can be used with the BASE_MARKER to create a different effect on the viewing direction. When the
is "from" theCAMERA_REF_MARKER position "to" the BASE_MARKER position. In addition
distance.
12. The point_trace_marker parameter is used to specify marker(s) whose position will be traced in the
view as the model animates. This is particularly useful when a marker undergoes complicated motion,
on the wheel center would be appropriate. Note that 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.
13. Entering 'ON' for the icon_visibility parameter will cause Adams View to display the icons during
animation. This will cause slower animation times. For this reason, 'OFF' is the default value.
14. The fullscreen_animation parameter specifies the animation should be done using the entire
application window. This includes the areas for all the displayed views, the menu/panel area, fixed
menu area , and the command/message areas. The application window will return to the
configuration in effect prior to theanimation command when the animation is complete.
15. Bitmap animation is a platform dependent feature that may be used to obtain faster animations. The
value for this parameter may be one of the following:
- OFF - perform no bitmap animation operations.
- RECORD - record frames for the bitmap animation using the current window size.
- RECORD_SHRINK - record frames for the bitmap animation, but first shrink the Adams View
window so that it is approximately 20% of the total screen size. This is to obtain a faster animation
by using a smaller amount of screen space.
- PLAY - play back the last recorded bitmap animation.
- FREE_MEM - free any memory resources that were allocated for bitmap animations. Each time you
record a new bitmap animation, any previous bitmap animation will be deleted. When you exit
Adams View, any bitmap animations will be deleted. It issuggested that after you have finished with
a bitmap animation to use the FREE_MEM option so that you can make available the memory
resources used by theanimation. It should be noted that there is a direct correlation between the size
of the Adams View window and the memory requirements for recording and the speed upon
playback. A large Adams View window on a color machine may require a significant amount of
memory to perform bitmap animation. In addition, playback speeds are going to be slower for a large
window as opposed to a smaller window because more pixels per frame need to be drawn. Currently,
this feature is only available on Sun workstations, running the SunView windowing system.
16. Single frame recording allows you to render complex graphics images using the highest quality
rendering modes and record the images sequentially on the laser disc. Upon playback, the recorded
frames are displayed at the standard video rate of 30 frames/sec, allowing for smooth, high-quality
animation of modeling or analysis graphics. In addition, laser disc devices allow you to vary the
playback rate (unlike video tape systems) to speed up or slow down the resulting animation sequence.
graphic_results 7
graphic_results deformed_mode_shape
Tips:
Here are some tips to improve animation performance in Adams View.
1. Animate only a single view. If you animate multiple views simultaneously, animation will be slower.
You can use the Delete command box on the View Control Panel or the 'VIEW MANAGEMENT
DELETE' command to delete views that are not needed. You may also erase a view with the 'VIEW
ERASE' command. Erasing a view leaves the view window in the display, but erases the contents, so
they will not be animated.
2. Animate in wireframe mode rather than in solid fill or shaded mode. Animate a subset of the available
frames by using the INCREMENT_FRAME_BY parameter on the 'GRAPHIC_RESULTS
ANIMATE' command. Remove unnecessary geometry with the 'DISPLAY_ATTRIBUTES
VISIBILITY GEOMETRY VISIBILITY=OFF' command. You can remove entire parts with the
'DISPLAY_ATTRIBUTES VISIBILITY PART VISIBILITY=OFF' command.
Avoid excessive detail in your geometry. For example, avoid creating a cylinder with 60 sides if it looks
acceptable with 20 sides.
3. Remove or replace "rubber-band" geometry. In general, geometry that "rubberbands" (i.e. changes
size or shape with each time step) takes longer to display than similar geometry that does not. Spring-
dampers, force vectors, and outlines that go between parts are examples of "rubber-banding"
geometry. Turn off the view name and triad with the command 'VIEW MANAGEMENT MODIFY
NAME_VISIBILITY=OFF TRIAD_VISIBILITY=OFF'.
Allows you to display the model at maximum deformation from the operating point of the requested natural
frequency of the EIGEN_SOLUTION.
Format:
eigen_solution_name = an existing eigen
mode_number = integer
frequency = real
translation_maximum = length
rotation_maximum = angle
display_undeformed_shape = boolean
color_of_undeformed_shape = an existing color
Example:
graphic_results deformed_mode_shape &
eigen_solution_name = eigen__1 &
mode_number = 1 &
translation_maximum = 0.15 &
color_of_undeformed_shape = salmon &
display_undeformed_shape = yes &
contour_plots = off
Description:

eigen_solution_name An Existing Eigen Specifies an existing eigen_solution.You may identify
an eigen_solution by typing its name.
view_name An Existing View Specifies an existing view
mode_number Integer Specifies which mode shape of the
EIGEN_SOLUTION is to be used to calculate the
deformation of the model.
frequency Real The FREQUENCY parameter is used to determine
which mode shape of the EIGEN_SOLUTION is to
be used to calculate the deformation of the model.
translation_maximum Length Specifies the maximum amount the parts will
translate from their undeformed position.
rotation_maximum Angle Specifies the maximum amount the parts are allowed
to rotate from their undeformed position.
display_undeformed_shape Boolean Specifies whether the undeformed model is to be
displayed with the deformed shape superimposed on
top of it. YES indicates that the undeformed model
will be displayed.
color_of_undeformed_shape An Existing Color Specifies the color of the undeformed model. If no
color is specified, the undeformed model will be
displayed with the same color as the deformed mode.
1. Adams linearizes the model at an operating point you specify and calculates the eigenvalues and
eigenvectors. This information is communicated to Adams View in the output files. Adams View then
can use this command to display the deformed shape as predicted from the EIGEN_SOLUTION.
Because the linear solution eigenvectors are normalized you can specify what the maximum excursion
of the deformed shape should be for best visualization. You can specify the mode by entering the
graphic_results 9
MODE_NUMBER, or the FREQUENCY of the mode. If you specify the FREQUENCY, the mode
closet to the specified FREQUENCY will be used. If neither the mode parameter or the
FREQUENCY parameter is specified, the model is deformed using the first mode. You can display
the model in its undeformed state, as well as its deformed state using the
DISPLAY_UNDEFORMED_SHAPE parameter. The amount of deformation is controlled with the
MAXIMUM_TRANSLATION and MAXIMUM_ROTATION parameters. The deformations are
all scaled, so that no part is translated more than the specified MAXIMUM_TRANSLATION, or
rotated more than the specified MAXIMUM_ROTATION.
2. If an eigen_solution is available by default, you may identify it by entering only its name. The
EIGEN_SOLUTION must be in an existing analysis that is associated to an existing model.
Therefore, any reference to the EIGEN_SOLUTION can include the model and analysis name. For
example, assume you have read a result file called "SECOND_GEAR.RES", and this result file
contains the analysis "SECOND_GEAR". If you wish to refer to the EIGEN_SOLUTION named
"EIG1" for the model "TRANSMISSION", enter .TRANSMISSION.SECOND_GEAR.EIG1
(the.TRANSMISSION.SECOND_GEAR. may be omitted if SECOND_GEAR is the current
default analysis_name). SECOND_GEAR refers to the analysis name that the result set came from
(or is stored under). If you type a "?", Adams View will list the eigen_solutions available by default.
The eigen_solution name begins with the letters EIG and ends with the eigen_solution ID number.
You must separate multiple eigen_solution names by commas. If the eigen_solution is visible in one
of your views, you may identify it by picking on any of the graphics associated with it.
4. If neither MODE_NUMBER or FREQUENCY is specified the first mode in the
EIGEN_SOLUTION is used. To get a list of the available modes and the orresponding frequencies
use the LIST_INFO EIGEN command.
5. The mode shape (i.e. eigenvector) of the mode closest to the specified FREQUENCY is used. If
neither MODE_NUMBER nor FREQUENCY is specified, the first mode in the
EIGEN_SOLUTION is used. To get a list of the available modes and the corresponding frequencies
6. The reason why the translation_maximum parameter is needed is because the eigenvectors are
normalized during the eigen_solution. Therefore, to get a meaningful animation or deformed shape
you must sometimes set this value to scale the maximum deformation to get a recognizable shape.
7. The reason why the rotation_maximum parameter is required is because the eigenvectors are
normalized during the EIGEN_SOLUTION. Therefore, to get a meaningful animation or deformed
shape, you must sometimes set this value to scale the maximum deformation to get a recognizable
shape.
graphic_results mode_shape_animation
Tips:
1. If the MAXIMUM_TRANSLATION parameter is not specified, 20 percent of the model size is used.
2. If the MAXIMUM_ROTATION parameter is not specified, 20 degrees is used.
3. To get a list of the modes and frequencies to select from, use the LIST_INFO EIGEN_VALUE
command.
4. The undeformed model is displayed in dashed lines.
Allows you to view the model oscillating at one of its natural frequencies.
Format:
mode_number = integer
frequency = real
translation_maximum = length
rotation_maximum = angle
show_time_decay = boolean
frames_per_cycle = integer
fullscreen_animation = on_off
bitmap_animation = bitmap_opts
record_to_laser_disc = on_off
Example:
graphic_results mode_shape_animation &
eigen_solution_name = eigen__1 &
mode_number = 1 &
translation_maximum = 0.15 &
record_to_laser_disc = on
graphic_results 11
Description:

eigen_solution_name An Existing Eigen Specifies an existing eigen_solution.You may identify a
eigen_solution by typing its name.
view_name An Existing View Specifies an existing view
mode_number Integer Specifies which mode shape of the EIGEN_SOLUTION is
to be used to calculate the deformation of the model.
frequency Real The FREQUENCY parameter is used to determine which
mode shape of the EIGEN_SOLUTION is to be used to
calculate the deformation of the model.
translation_maximum Length Specifies the maximum amount the parts will translate to
from their undeformed position.
rotation_maximum Angle Specifies the maximum amount the parts are allowed to
rotate from their undeformed position.
show_time_decay Boolean Specifies whether the amplitudes of the deformations are to
remain constant or decay due to the damping factor
calculated in the EIGEN_SOLUTION.
frames_per_cycle Integer Specifies the number of frames to be displayed for each
cycle for this MODE_SHAPE_ANIMATION.
number_of_cycles Integer Parameter used to specify the number of complete cycles to
animate. This means, based on this parameter, the
animation will continuously run through all the specified
frames the specified number of times.
superimposed On_Off Parameter used with the animation command to specify
individually or superimposed on top of one another.
icon_visibility On_Off Specifies whether or not to display icons during an
animation. Entering 'ON' will cause Adams View to display
the iconsduring animation. This will cause slower
fullscreen_animation On_Off Specifies the animation should be done using the entire
application window.
bitmap_animation Bitmap_Opts
record_to_laser_disc On_Off Causes a single video frame to be recorded on the laser disc.
1. This animation cycles through the model deformation from the operating point of the requested
natural frequency of the EIGEN_SOLUTION. Adams linearizes the model at an operating point you
specify and calculates the eigenvalues and eigenvectors. This information is communicated to Adams
View in the output files. Adams View then can use this command to display the animated deformed
shape as predicted from the EIGEN_SOLUTION. Because the linear solution eigenvectors are
normalized you can specify what the maximum excursion of the animated deformed shape should be
for best visualization.
2. Animation is created by requesting a series of "frames" to be displayed in rapidsuccession. These
frames correspond to a pictures of the model interpolated between the maximum deformation in the
positive and negative directions. The animation then cycles through the deformation of the model
mode shape, from undeformed, to maximum deformed, to negative maximum deformed, and finally,
to the undeformed shape. This deformation is about the operating point of the requested natural
mode of the EIGEN_SOLUTION.
3. The number of frames per cycle is controlled with the FRAMES_PER_CYCLE parameter. The
interpolation between the frames is done with trigonometric functions, therefore, the frames will tend
to be segregated at the maximum deformation in the positive and negative directions.
4. You can see the effect of the damping in the MODE_SHAPE_ANIMATION with the
SHOW_TIME_DECAY parameter. If not specified, the amplitude of the deformations will not
change as each frame is calculated. Only periodic eigen modes can be animated. Therefore, there is
no animation of modes that do not have periodic data (i.e. modes with an imaginary component of
the eigenvalue = 0). You can specify the mode by entering the MODE_NUMBER, or the
FREQUENCY of the mode. If you specify the FREQUENCY, the mode closet the specified
FREQUENCY will be used. If neither the mode parameter or the FREQUENCY parameter is
specified, the model is deformed using the first mode.
The amount of deformation is controlled with the MAXIMUM_TRANSLATION and
MAXIMUM_ROTATION parameters. The deformations are all scaled so that no part is translated
more than the specified MAXIMUM_TRANSLATION, or rotated more than the specified
MAXIMUM_ROTATION. The speed of the animation depends on the hardware Adams View is
running on, the complexity of the graphics being displayed, and the draw mode of the graphics being
displayed (wireframe, solid filled, or shaded; wireframe being the fastest).
5. If an eigen_solution is available by default, you may identify it by entering only its name. The
EIGEN_SOLUTION must be in an existing analysis that is associated to an existing model.
Therefore, any reference to the EIGEN_SOLUTION can include the model and analysis name. For
example, assume you have read a result file called "SECOND_GEAR.RES", and this result file
contains the analysis "SECOND_GEAR". If you wish to refer to the EIGEN_SOLUTION named
"EIG1" for the model "TRANSMISSION", enter .TRANSMISSION.SECOND_GEAR.EIG1
(the .TRANSMISSION.SECOND_GEAR. may be omitted if SECOND_GEAR is the current
default analysis_name). SECOND_GEAR refers to the analysis name that the result set came from
(or is stored under). If you type a "?", Adams View will list the eigen_solutions available by default.
graphic_results 13
7. If neither MODE_NUMBER nor FREQUENCY is specified, the first mode in the
EIGEN_SOLUTION is used. To get a list of the available modes and the corresponding frequencies
8. The mode shape (i.e. eigenvector) of the mode closest to the specified FREQUENCY is used. If
neither MODE_NUMBER nor FREQUENCY is specified, the first mode in the
EIGEN_SOLUTION is used. To get a list of the available modes and the corresponding frequencies,
9. The reason why the translation_maximum parameter is needed is because the eigenvectors are
normalized during the eigen_solution. Therefore, to get a meaningful animation or deformed shape
you must sometimes set this value to scale the maximum deformation to get a recognizable shape.
10. The reason why the rotation_maximum parameter is required is because the eigenvectors are
normalized during the EIGEN_SOLUTION. Therefore, to get meaningful animation or deformed
shape, you must sometimes set this value to scale the maximum deformation to get a recognizable
shape.
11. A full cycle goes from undeformed, to maximum positive displacement, back to undeformed, then
to maximum displacement in the negative direction, and finally back to undeformed. The
interpolation between the frames is done with trigonometric functions, therefore, the frames will tend
to be segregated at the maximum deformation in the positive and negative directions.
12. If entered the NUMBER_OF_CYCLES parameter must be a positive integer. This value will be
optional and if not entered will default initially to 1 (until updated by the user).
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 superimposed
during the animation. OFF, the default, indicates that frames will not be superimpose during the
animation.
14. The fullscreen_animation parameter specifies the animation should be done using the entire
application window. This includes the areas for all the displayed views, the menu/panel area, fixed
menu area, and the command/message areas. The application window will return to the configuration
in effect prior to the animation command when the animation is complete.
15. Bitmap animation is a platform dependent feature that may be used to obtain faster animations. The
value for this parameter may be one of the following:- OFF perform no bitmap animation operations.
- RECORD - record frames for the bitmap animation using the current window size.
- RECORD_SHRINK - record frames for the bitmap animation, but first shrink the Adams View
window so that it is approximately 20% of the total screen size. This is to obtain a faster animation
by using a smaller amount of screen space.
- PLAY - play back the last recorded bitmap animation.
- FREE_MEM - free any memory resources that were allocated for bitmap animations. Each time you
record a new bitmap animation, any previous bitmap animation will be deleted. When you exit
Adams View, any bitmap animations will be deleted. It is suggested that after you have finished with
a bitmap animation to use the FREE_MEM option so that you can make available the memory
resources used by the animation. It should be noted that there is a direct correlation between the size
of the Adams View window and the memory requirements for recording and the speed upon
playback. A large Adams View window on a color machine may require a significant amount of
memory to perform bitmap animation. In addition, playback speeds are going to be slower for a large
window as opposed to a smaller window because more pixels per frame need to be drawn. Currently,
this feature is only available on Sun workstations running the SunView windowing system.
16. Single frame recording allows you to render complex graphics images using the highest quality
rendering modes and record the images sequentially on the laser disc. Upon playback, the recorded
frames are displayed at the standard video rate of 30 frames/sec, allowing for smooth, high-quality
animation of modeling or analysis graphics. In addition, laser disc devices allow you to vary the
playback rate (unlike video tape systems) to speed up or slow down the resulting animation sequence.
Tips:
1. If the MAXIMUM_TRANSLATION parameter is not specified, 20 percent of the model is used.
2. If the MAXIMUM_ROTATION parameter is not specified, 20 degrees is used.
3. To get a list of the modes and frequencies use LIST_INFO EIGEN_VALUE
4. Animate only a single view. If you animate multiple views simultaneously,animation will be slower.
You can use the Delete command box on the View Control Panel or the "VIEW MANAGEMENT
DELETE" command to delete unneeded views.
You may also erase a view with the "VIEW ERASE" command. Erasing a view leaves the view window
in the display, but erases the contents so they will not be animated.
5. Animate in wireframe mode rather than in solid fill or shaded mode.
6. Remove unnecessary geometry with the "DISPLAY_ATTRIBUTES VISIBILITY GEOMETRY
VISIBILITY=OFF" command. You can remove entire parts with the"DISPLAY_ATTRIBUTES
VISIBILITY PART VISIBILITY=OFF" command.
Avoid excessive detail in your geometry. For example, avoid creating a cylinder with 60 sides if it looks
acceptable with 20 sides.
7. Remove or replace "rubber-band" geometry. In general, geometry that "rubberbands" (i.e. changes
size or shape with each time step) takes longer to display than similar geometry that does not. Spring-
dampers, force vectors, and outlines that go between parts are examples of "rubber-banding"
geometry.
Turn off the view name and triad with the command "VIEW MANAGEMENT
MODIFYNAME_VISIBILITY=OFF TRIAD_VISIBILITY=OFF".
graphic_results 15
graphic_results single_frame_display
Allows you to display the model geometry based on Adams simulation results, one frame at a time. These
frames correspond to "simulation output time steps".
Format:
rame_number = f integer
time = time
offset = location
contour_plots = on
Example:
graphic_results single_frame_display &
frame_number = 10 &
base_marker = mar_3 &
camera_ref_marker = psmar &
colors = pink &
offset = 10 , 10 , 10 &
contour_plots = on
Description:

analysis_name An Existing Analysys This parameter specifies the name of an analysis name.
view_name An Existing View Specifies the view for the display
frame_number Integer The FRAME_NUMBER parameter is used to specify the
frame number (Adams simulation output time step) at
which to configure a model during the

Time Time The TIME parameter allows you to identify the frame
number (Adams simulation output time step) at which to
configure the model in the SINGLE_FRAME_DISPLAY
command.
Configuration Display_Frame This parameter is used to specify what output frame, or
output time step, of the simulation results is to be
displayed for the single_frame_display command.
Base_marker An Existing Marker This parameter is used to specify a marker whose position
will be frozen in the view as the model animates.
Camera_ref_marker An Existing Marker This parameter is used to identify a marker which specifies
the viewing direction as the model animates.
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.
contour_plots on/off
1. Options are provided to control the single-frame-at-a-time display mode. The options effect what
model configuration is to be displayed. They include, specifying the Adams output
FRAME_NUMBER, TIME, or CONFIGURATION (CONFIGURATION options include:
model_input, initial_conditions, equilibrium, forward, and backward). This command also allows
the user to view the results of multiple models simultaneously. Each simulation result is read and
associated to an analysis name.
This ANALYSIS_NAME can be viewed in any number of views at one time.
analysis name without reading in an analysis file use, the "defaults analysis" command.
MANAGEMENT CREATE' command, and save/restore their attributes.
graphic_results 17
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.
Note: Even if only one view_name is provided, the frame number will be applied to the
5. The frame with the closest time value to the time specified in the TIME parameter will be selected.
Adams View will display the last frame if the time entered is greater than the time for the last frame
in the simulation. This parameter is optional and mutually exclusive with the CONFIGURATION
and FRAME_NUMBER parameters. If none of the three are entered, the first frame will be
displayed.
6. The legal values for the configuration 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
• BACKWARD, one frame backward from the current one displayed.
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).
7. The base_marker parameter is used to specify a marker whose position will be frozen in the view as
the model animates. 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
is "from" the CAMERA_REF_MARKER position "to" the BASE_MARKER position. In addition
distance.
8. You may identify a marker by typing its name or by picking it from the screen.If the marker is not
if the marker is displayed. If you created the marker by reading an Adams data set or graphics file, the
marker name is the letters MAR followed by the Adams data set marker ID number. For example, the
name of Adams MARKER/101 is MAR101. If you created the marker during preprocessing, you will
have given it a name at that time. If a marker is available by default, you may identify it by entering
only its name. If it is not, you must enter its full name. To identify a marker under a different part,
for instance, you may need to enter the model and part names, as well. For example, you may specify
marker 'pivot' from model 'links', part 'lower_arm' by entering ".links.lower_arm.pivot. You must
separate multiple marker names by commas. If the marker is visible in one of your views, you may
identify it by picking on it. You need not separate multiple marker picks by commas.
9. The camera_ref_marker parameter connects the viewing camera to the "z" axis of a marker. The
animation is then viewed from the moving location of that marker in the "z" direction. This is
particularly useful when a "driver’s eye" or "pilot’s eye" viewing perspective is desired. This parameter
can be used with the BASE_MARKER to create a different effect on the viewing direction. When the
is "from" the CAMERA_REF_MARKER position "to" the BASE_MARKER position. In addition
"y" axis (that is, 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
distance.
Cautions:
 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), any views that contain the model
indicated by analysis_name will be affected.
Tips:
1. f the VIEW_NAME parameter is used, the desired view can be identified by picking in the window
2. ". If you type a "?", Adams View will list the markers available by default.
group 1
group attributes
group
group attributes
Allows the specification of attributes to be set on a group
Format:
group attributes
group_name = an existing group
size_of_icons = real
member_dependents_active = on_off_no_opinion
Example:
group attributes &
group_name = group_1 &
visibility = on &
color = blue &
line_thickness = 0.19 &
line_type = dash &
entity_scope = fill_color &
active = on d &
member_dependents_active = on_off_no_opinion
group attributes
Description:

group_name An Existing Group Specifies the group to be modified. You use this
parameter to identify the existing group to be
current icon size.
visibility On / Off / No_opinion / Toggle Specifies the visibility of graphic entities
name_visibility On / Off / No_opinion / Toggle The NAME_VISIBILITY parameter provides
control over the visibility of the view name
displayed at the top center position of a given
view.
color An Existing Color Specifies the color the modeling entity should
be drawn in.
line_thickness Real Specifies the thickness of the line for a curve
line_type Line_style This parameter allows the selection of the line
type for a curve.
active On / Off / No_opinion Controls the activity of the group and thereby
all objects in the group. Specifying no_opinion
leaves the existing activity state unchanged.
When you set ACTIVE=OFF, that element is

dependents_active On / Off / No_opinion Specifies whether dependents of the objects are
to be acted upon in the same way as the active
parameter does.
member_dependents On / Off / No_opinion Controls the activity of the dependents of all
_active objects in the group
1. If a group has attributes associated with it, any object in the group will inherit the group's attribute.
If an object is in more than one group, the object will inherit the attribute of the last group it was
added to.
2. You may identify a group by typing its name.
group 3
group attributes
If a group is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. If you type a "?", Adams View will list the group available by default.
You must separate multiple group names by commas.
in length.
When you specify SCALE_OF_ICONS, a new size is calculated by multiplying the current size by
in length.
For Example:
.model ---------------------- SIZE_OF_ICONS =.15 meters
For Example:
5. Specifies the visibility of graphic entities. The visibility parameter is used to control whether graphic
entities, such as markers, joints, and parts, are to be drawn in an Adams View viewport.
and if not entered the name will be visible (i.e. will be ON).
Note that if the visibility of the view name is turned off the only indication that a view is "active" will
Example 1:
group attributes
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
8. The line type describes how the line will look when displayed on a plot. Adams View supports solid,
dash, dotdash, and dot.
-------------------------------------
solid _______________
dash _ _ _ _ _ _ _ _
dotdash . _ . _ . _ . _
dot . . . . . . . .
9. The legal values for the entity_scope parameter are FILL_COLOR,
EDGE_COLOR,OUTLINE_COLOR, and ALL. FILL_COLOR is the color of those areas of a
graphic that can be shaded (they include sides of a cylinders, frustums, boxes, etc.) The
EDGE_COLOR is the color of the lines making up the edges of the facets (or areas filled by the
FILL_COLOR) of a graphic that can be shaded.
springdamper.
following command:
group 5
group copy
changed individually. Elements affected are:
 Group
 Part
 Differential Equation
 Marker
 Geometry
 Constraints
 Forces
 Data Elements
 Output Control
MEMBER_DEPENDENTS_ACTIVE parameter acts in the same fashion as the DEPENDENTS_ACTIVE
parameter, but it operates on the dependencies of each object in the group
group copy
Allows you to copy an existing group to a new group.
All objects that are referenced by the first group will be referenced by the new group.
When objects in a group are copied, they are copied in the same manner as other copy operations in Adams
View. That is, a replica of the original objects are created, reference markers for the new object are created as
needed and a new name is automatically generated.
Format:
group copy
new_group_name = new name for group
Example:
group copy &
group_name = my_part_group &
new_group_name = my_part_copy
group create
Description:

Group_name Existing Group Specifies the group name to be copied.
New_group_name New Group Specifies the new name for the group.
group create
Allows you to create a new Adams View group.
An Adams View group is a collection of any Adams View objects except other groups. Groups can be used
to control object's attributes, like visibility and color.
Format:
group create
group_name = new group name
comments = string
objects_in_group = existing entity
type_filter = entity
expand_groups = yes/no
expr_active = integer
Example:
group create &
group_name = pendulum_parts &
comments = "group containing all parts of a pendulum" &
objects_in_group = .model_1.part_2,.model_1.part_3 &
type_filter = part &
expand_groups = no &
expr_active = 1
group 7
group delete
Description:

group_name New Group Name Specifies the name of the new group. You may use this
name later to refer to this group.
comments String Specifies comments for the group being created or
modified.
objects_in_group Entity Specifies the objects to be in the group.
type_filter Entity Type Specifies the type of objects allowed.
expand_groups Yes/no Specifies a Boolean value
expr_active Integer EXPR_ACTIVE allows you to set the activity of the
group using an integer value, which allows
parameterization.
1. Adams View will not allow you to have two group with the same name, so you must provide a unique
name.
You may identify a group by typing its name. If a group is available by default, you may identify it
by entering only its name. If it is not, you must enter its full name. If you type a "?", Adams View
will list the group available by default.
2. The “objects_in_group” parameter takes one or more of any existing Adams View objects. If a wild
card is used to specify the objects, the TYPE_FILTER parameter can be used to accept only objects
of a particular type.
3. Adams View at this time does not allow expressions when specifying option lists. To allow the activity
of a group to be set parametrically, the parameter EXPR_ACTIVE was added to the GROUP
CREATE and GROUP MODIFY commands. This parameter takes on integer value.
expression, then the standard activity rules apply.
If the EXPR_ACTIVE is set to an expression that evaluates to zero (FALSE), the objects in the group
will be in active (and will not be included by Adams Solver in any simulation). If the value is the
default or non-zero (TRUE), then the objects will be active (and will be included in simulations).
group delete
Allows the deletion of an Adams View group. When objects in a group are deleted, they are deleted in the
same manner as other delete operations in Adams View. That is, they are checked for dependent objects,
and if any dependencies are found the object can not be deleted.
group empty
Format:
group delete
Example:
group delete &
group_name = my_part_group
Description:

Group_name Existing group Specifies the group to delete.
menu entry 'UNDO'.
You may identify a group by typing its name.If a group is available by default, you may identify it by
entering its name only. If it is not, you must enter its full name. If you type a "?", Adams View will
list the group available by default.
group empty
Removes all objects from the group. Group continues to exist unlike the use of “group delete” command that
deletes the group as well.
Format:
group empty
Example:
group empty &
group_name = my_part_group
group 9
group modify
Description:

Group_name Existing Group Specifies the group to empty. You use this parameter
to identify the existing group to be affected with this
command.
group modify
Allows the modification of an existing Adams View groups.
An Adams View group is a collection of any Adams View objects except other groups. Groups can be used
to control object's attributes, like visibility and color.
Format:
group modify
group_name = existing group name
new_group_name = new group name
comments = string
objects_in_group = existing entity
type_filter = entity
expr_active = integer
Example:
group modify &
group_name = pend_parts_and_joints &
comments = "group containing all parts and joints" &
objects_in_group = model_1.part_2,.model_1.part_3,.model_1.joint_1
group objects add
Description:

group_name Group Name Specifies the name of the existing group to be
modified.
New_group_name New Group Name Specifies the new name for the group. You may
us e this name later to refer to this group.
comments String Specifies comments for the group being
objects_in_group Entity Specify the objects to be in the group.
type_filter Entity Type Specify the type of objects allowed.
expand_groups Yes/no Specify a Boolean value
expr_active Integer EXPR_ACTIVE allows you to set the activity
of the group using an integer value, which
allows parameterization.
1. Adams View will not allow you to have two group with the same full name, so you must provide a
unique name.
You may identify a group by typing its name.
If a group is available by default, you may identify it by entering its name only. If it is not, you must
2. The “objects_in_group” parameter takes one or more of any existing Adams View objects. If a
wldcaring is used to specify the objects, the TYPE_FILTER parameter can be used to accept only
objects of a particular type.
3. Adams View at this time does not allow expressions when specifying option lists. To allow the activity
of a group so to be set parametrically the parameter EXPR_ACTIVE was added to the GROUP
CREATE and GROUP MODIFY commands. This parameter takes on integer value.
expression, then the standard activity rules apply.
If the EXPR_ACTIVE is set to an expression that evaluates to zero (FALSE), the objects in the group
will be in active (and will not be included by Adams Solver in any simulation). If the value is the
default or non-zero (TRUE), then the objects will be active (and will be included in simulations).
group objects add

Allows you to add objects to an Adams View group.
group 11
group objects attributes
Format:
group objects add
objects_in_group = existing entities
type_filter = entity type
Example:
group objects add &
objects_in_group = .model_1.part_2, .model_1.part_3 &
type_filter = part
Description:

Group_name Existing Group Name Specifies the group to be modified. You use this
Objects_in_group Existing Entity/entities Specifies the objects to be added or removed from
the group.
Expand_groups Yes, No Specifies a Boolean value.
Type_filter Entity Type Specifies the type of objects allowed.
1. The “objects_in_group” parameter takes one or more of any existing Adams View objects.
If a wildcard is used to specify the objects, the TYPE_FILTER parameter can be used to accept only
2. When specifying the objects for the “type_filter” operation a wild cards can be used, which may result
in too many objects being found. For example, if all the parts for model MOD1 are desired, specifying
.MOD1.* will get not only the parts, but all children of the model, like joints, forces and so on. Using
the parameter TYPE_FILTER=part will result in only the parts being processed by this command.

Allows the specification of attributes on all objects in a group which can take attributes.
Format:
type_filter = ent
Example:
group objects attributes &
visibility = on &
color = blue &
line_thickness = 0.19 &
line_type = dash &
entity_scope = fill_color &
active = on d &
dependents_active = on &
type_filter = color
group 13
Description:

current icon size.
visibility On_off_with_toggle Specifies the visibility of graphic entities
name_visibility On_off_with_toggle The NAME_VISIBILITY parameter provides
control over the visibility of the view name
displayed at the top center position of a given
view.
color An Existing Color Specifies the color the modeling entity should be
drawn in.
line_thickness Real Specifies the thickness of the line for a curve
line_type Line_style This parameter allows the selection of the line
type for a curve.
active On_off_no_opinion When you set ACTIVE=NO, that element is
dependents_active On_off_no_opinion Specifies whether children of the objects are to
be acted upon in the same way as the active
parameter does.
type_filter Ent Specifies the type of objects allowed.
transperency Integer Sets the transparency
in length.
When you specify SCALE_OF_ICONS, a new size is calculated by multiplying the current size, by
in length.
For Example:
.model ---------------------- SIZE_OF_ICONS =15 meters
.part-------------------- SIZE_OF_ICONS =.125 meters
For Example:
4. Specifies the visibility of graphic entities. The visibility parameter is used to control whether graphic
entities, such as markers, joints, and parts, are to be drawn in an Adams View viewport.The legal
values for this parameter are: ON, OFF, and TOGGLE. ON will make the desired entity visible.
OFF will make the desired entity invisible. TOGGLE will take the current state of an entity’s
Example 1:
.model -------------------------NO_COLOR
.part---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part---------------------- RED
group 15

Example 3:
.model -------------------------NO_COLOR
.part---------------------- NO_COLOR
7. The line type describes how the line will look when displayed on a plot. Adams View supports solid,
dash, dotdash, and dot.
solid _______________
dash _ _ _ _ _ _ _ _
dotdash . _ . _ . _ . _
dot . . . . . . . .
shaded (they include sides of a cylinders, frustums, boxes, etc.) The EDGE_COLOR is the color of
be shaded.
springdamper.
following command:
• Group
group objects copy
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
10. When specifying the objects for this operation a wild cards can be used, which may result in too many
objects being found. For example, if all the parts for model MOD1 are desired, specifying .MOD1.*
will get not only the parts, but all children of the model, like joints, forces, etc. Using the parameter
TYPE_FILTER=part will result in only the parts being processed by this command.
group objects copy

Allows you to create replicas of all objects in the group.
Format:
group objects copy
new_group_name = a new or existing group
type_filter = ent
search_for_string = string
replace_string = string
Example:
group objects copy &
new_group_name = group_2 &
type_filter = color &
search_for_string = "ab" &
replace_string = "ba"
group 17
group objects delete
Description:

group_name An Existing Group Specifies the group to be modified. You use this parameter
to identify the existing group to be affected with this
command.
new_group_name A New Or Existing Specifies the group the copied objects are to be added to.
Group
type_filter Ent Specifies the type of objects allowed.
search_for_string String
replace_string String
1. When objects in a group are copied, they are copied in the same manner as other copy operations in
Adams View. That is, a replica of the original objects are created, reference markers for the new object
are created as needed and a new name is automatically generated.
The newly created objects can be placed into a new or an existing group as they are being copied with
the NEW_GROUP_NAME parameter.
2. You may identify a group by typing its name. If a group is available by default, you may identify it by
3. If a new group is specified, the group is created.
You may identify a group by typing its name. If a group is available by default, you may identify it by

Allows the deletion of all objects in a group.
Format:
remove_unused_references = boolean
expand_groups = boolean
type_filter = ent
Example:
group objects delete &
new_group_name = group_2 &
search_for_string = "ab" &
replace_string = "ba"
Description:

group_name An Existing Group Specifies the group to modify. You use this parameter to
identify the existing group to affect with this command.
remove_unused_referen Boolean Parameter used to specify whether or not to delete any
ces unused references found for the objects being deleted.
expand_groups Boolean
type_filter Ent Specify the type of objects allowed.
1. When objects in a group are deleted, they are deleted in the same manner as other delete operations
in Adams View. That is, they are checked for dependent objects, and if any dependencies are found
they are deleted.
will get not only the parts, but all children of the model, like joints, forces and so on. Using the
parameter TYPE_FILTER=part will result in only the parts being processed by this command.
group 19
group objects remove
4. As an example for the remove_unused_references parameter, if a circle is being deleted, and its center
marker is not being used by anything other than the circle, then it is an unused reference.

Allows objects to be removed from an Adams View group.
Format:
objects_in_group = existing entities
type_filter = entity type
Example:
group objects remove &
objects_in_group = .model_1.part_3 &
type_filter = part
Description:

Group_name Existing Group Name Specifies the group to be modified.You use
this parameter to identify the existing
group to be affected with this command.
Objects_in_group Existing Entity/entities Specifies the objects to be removed from
the group.
Type_filter Entity Type Specifies the type of objects allowed.
1. The “objects_in_group” parameter takes one or more of any existing Adams View objects.
If a wildcard is used to specify the objects, the TYPE_FILTER parameter can be used to accept only
2. When specifying the objects for the “type_filter” operation a wild cards can be used, which may result
in too many objects being found. For example, if all the parts for model MOD1 are desired,
specifying .MOD1.* will get not only the parts, but all children of the model, like joints, forces and
so on. Using the parameter TYPE_FILTER=part will result in only the parts being processed by this
command.
group objects rename

Allows you to modify the name of an existing group object
Format:
prefix_string = string
suffix_string = string
type_filter = ent
Example:
group objects rename &
prefix_string = gr_ &
type_filter = color
Description:

group_name An Existing Group Specifies the group to modify. You use this parameter to
identify the existing group to affect with this command.
prefix_string String String to be prefixed to the name
suffix_string String String to be suffixed to the name
type_filter Ent Specify the type of objects allowed.
hardcopy 1
hardcopy
Allows you to send screen output to hard copy file. The user may specify the view_name to be sent to the
desired hard copy file name. The FILE_NAME parameter provides a means to specify the name of the hard
copy file the screen image(s) selected by the user will be written to. The FILE_NAME is an optional
parameter, and if not entered, a default name will be constructed. If entered, the file name must be enclosed
in quotes.
The ORIENTATION parameter is used to specify how to orient the image sent to a hard copy file. There
are two legal values for this parameter: LANDSCAPE and PORTRAIT.
The LANGUAGE parameter is used to specify that plotting language is to be used for the image sent to a
hardcopy file. The legal values for this parameter are: BMP, XPM, JPG, TIFF and PNG.
Note: This command will only function in Adams View sessions launched in interactive mode. It will
not function in batch mode Adams View. See “Running Adams Products – On Windows” and
“On Linux” for more detail about the difference between interactive and batch modes.
Format:
hardcopy
window_name = existing gi_window
view_name = existing view
file_name = string
orientation = landscape, portrait
paper_type = default, eight_by_eleven, a0, a1, a2, a3, a4, b5, b, c, d, e, f
send_to_printer = boolean
language = BMP, XPM, JPG, TIFF and PNG
image_width_height = real,real
force_black_and_white = on/off
setup_only = boolean
include_toolbars = boolean
Example:
hardcopy &
view_name = view_1 &
file_name = “c:\my_files\my_view” &
orientation = portrait &
hardcopy &
paper_type = default &
image_width_height = 0.5,0.25
Description:

window_name Existing Gi_window Specifies an existing window name whose screen
output is required
view_name Existing View_name Specifies existing view name
page_name Existing Page_name Specifies existing page name
file_name String Specifies the name of the hard copy file the screen
image(s) selected by the user will be written to
orientation Portrait/landscape Specifies how the image sent to a hardcopy file is to be
oriented
paper_type Default, Specifies the size of paper that needs to be used
Eight_by_eleven, A0, A1,
A2, A3, A4, B5, B, C, D,
E, F
send_to_printer Boolean Specifies if a printout of the screen output is required
language BMP, XPM, JPG, TIFF Specifies the plotting language to be used for the
and PNG image sent to a hardcopy file
image_width_height Real,real Specifies the size of the hardcopy output in the format
( x, y )
print_control_panel On/off Allows the user to print the control panel graphics
when screen output is sent to a hard copy file.
force_black_and_whit Boolean Specifies whether or not to override all color
e specifications in a scene and produce a hardcopy
image which is solely black and white.
Include_toolbar Boolean Specifies whether the toolbar is to be included in the
screen output
hardcopy 3
2. The FILE_NAME is an optional parameter and if not entered, a default name will be constructed.
The file name constructed will be of the form fig_000x.bmp (where x is 1 - 9) if the BMP language
is chosen or fig_000x.jpg if the JPG language is chosen. The integer value x will be automatically
incremented each time a new default hard copy name is requested. The value x will expand and take
the place of the zeros in every order of magnitude increase. Therefore, the tenth file would be named
fig_0010.bmp, the 100th file would be named fig_0100.bmp and so on. In this manner, 9999 default
hardcopy files can be created, named: fig_0001.bmp up to fig_9999.bmp (or other format’s file
extensions).
If entered, the file name must be enclosed in quotes.
3. There are two legal values for the orientation parameter: LANDSCAPE and PORTRAIT. The
LANDSCAPE value will cause the image to be oriented such that the top of the image (as seen on the
terminal screen) will be along the "long" edge of the paper. The PORTRAIT value will cause the
image to be oriented such that the top of the image (as seen on the terminal screen) will be along the
"short" edge of the paper.
The ORIENTATION parameter is optional and if not entered, will be set to LANDSCAPE.
4. The legal values for the language parameter are: BMP, XPM, JPG, TIFF and PNG. The resulting file
should be printable on any device supporting those languages.
The LANGUAGE parameter is optional, and if not entered, will be set to BMP.
5. The largest possible dimensions for hardcopy output are 1 x 1 ( IMAGE_WIDTH_HEIGHT= 1,1).
These hardcopy dimensions specify a "window" for the image to be fit into. If 1x1 is the maximum,
then .5 x .5 will result in an image half as big. Dimensions that are not symmetrical will result in the
image being "stretched" or "compressed" to fit the dimensions.
All hard copy output, regardless of its dimensions, is centered on the page.
6. Normally, when a hard copy operation is performed, only the views and their associated graphics are
set to the hard copy file. This command allows the control panel graphics to be printed in addition
to the view graphics. This way the user gets a hardcopy file which looks exactly the way he sees it on
the screen.
7. If the “force_black_and_white” parameter is set to "ON", all of the text and geometry in the hard
copy will be black and white. All text, polylines and edges will be black. Polygon faces will be white
if the polygon edges are visible, otherwise, they will be black. If this is set to OFF, the colors that you
have specified for geometry and text will be present in the hard copy file. Black and white hard copy
devices may use shades of gray to represent various colors. If the shades of gray are undesirable, you
may set the FORCE_BLACK_AND_WHITE parameter to ON to ensure that the output will
consist of solely black and white colors.
Cautions:
 Care should be taken when attempting to get a hard copy. The choice of draw modes in the view
(wireframe, solid, shaded, set in the view manage modify command or from the control panel) will
have impact on the image sent to the hard copy file. If solid or shaded mode is "On" in the desired
view, some graphics may "seem" to disappear. This happens if the image of an entity is such that the
edges of the shaded entity obscured the shaded or filled area. To avoid this, use wireframe draw
mode or ensure "facet" interiors are visible before the hardcopy is attempted. The choice of
background colors can have a similar effect.
help 1
help
Allows you to do the following.
 Request Command Navigator help on any command, keyword or a topic.
 Turn context sensitive help on or off.
 Turn the status bar messages on or off.
Format:
help
command_or_topic = string
context_sensitive = true
tips = on_off_toggle
Example:
help &
help command_or_topic = analysis
Description:
:

Command_or_topic String The value of this parameter is the command or topic name about
which command navigator help is to be requested.
Context_sensitive True The value of this parameter decides if the context sensitive help
should be displayed or not.
Tips On/off/toggle The value of this parameter decides if advice/tips should be
provided or not.
The “Command_or_topic” parameter cannot be used in conjuction with the parameters, context_sensitive
or tips.
highlight 1
highlight
The HIGHLIGHT command changes the appearance of an object, so that you can see its position in the
model. Optionally, you can also see the other entities it depends upon or which depend on it.
You can change the color or the line style of the object to highlight it. Adams View will change the appearance
of the objects being highlighted, then wait for you to enter input from the mouse or keyboard before
continuing, or wait for a given time period, if specified.
You can specify which entities, related to the selected object, are to be highlighted. This must be one of SELF,
DEPENDENTS, REFERENTS, PARTS, or ALL.
SELF indicates that only the selected object is to be highlighted.
DEPENDENTS indicates that the entities that are dependent on the selected object are to be highlighted. If
a marker is selected, this would show any constraints, forces, geometry, or parts (if the marker is the center of
mass or inertia marker) that depend on it. If a joint is selected, this would show any motions or couplers that
depend on it.
REFERENTS indicates that the entities on which the selected object is dependent, are to be highlighted. For
constraints, forces, and geometry, this will show any markers that they depend on. For motions and couplers,
this will show the joints they depend on.
PARTS indicates that any part on which the selected object are dependent, usually indirectly through one of
the part's markers, are to be highlighted. For constraints and forces, this will show the parts that the object
affects directly. For dynamic (part-connecting) graphics, this will show the parts that will affect their
appearance.
ALL indicates that the selected object plus entities, that would be highlighted by the DEPENDENTS,
REFERENTS, and PARTS arguments, are to be highlighted.
Format:
highlight
marker_name = existing marker name
geometry_name = existing geometry name
part_name = existing part name
constraint_name = existing constraint name
force_name = existing force name
line_type = solid, dash, dotdash, dot, none
time_delay = real
entity = self, dependents, referents, parts, all
Example:
highlight &
color = green &
line_type = dotdash &
time_delay = 5 &
entity = self
This command will highlight only the MARKER_28. It will display it in green color in the dotdash format.
This will be highlighted for 5 seconds
This command will highlight the MARKER_28, as well as all the entities that are dependant it, and all parts
on which it is dependant. It will display it in green color in the dotdash format. This will be highlighted for
5 seconds.
Description:

marker_name Existing Marker Specifies the name of the marker to be highlighted
geometry_name Existing Geometric Entity Specifies the name of the geometric object to be
highlighted. The geometric element may be one of
OUTLINE, ARC, CIRCLE, BSPLINE, BLOCK,
CYLINDER, FRUSTUM, SPRING_DAMPER, or
FORCE.
part_name Existing Body Specifies the name of the part to be highlighted.
constraint_name Existing Constraint Specifies the name of the constraint object to be
highlighted. The constraint element may be one of
JOINT, JOINT_PRIMITIVE,
HIGHER_PAIR_CONTACT,
MOTION_GENERATOR, or USER_DEFINED.
force_name Existing Force Specifies the name of the force object to be highlighted.
The force element may be one of BEAM, BUSHING,
FIELD, TRANSLATIONAL_SPRING_DAMPER,
ROTATIONAL_SPRING_DAMPER, TIRE,
SINGLE_COMPONENT_FORCE,
FORCE_VECTOR, TORQUE_VECTOR,
GENERAL_FORCE, or MULTI_POINT_FORCE.
color Existing Color Specifies what COLOR an object should be changed to,
when it is highlighted.
highlight 3

line_type Solid, Dash, Dotdash, Dot, Specifies the selection for the LINE_TYPE for the
None object or objects being highlighted.
time_delay Real The TIME_DELAY parameter is used to specify the
number of seconds to temporarily halt command
processing. Command processing will resume after the
specified number of seconds has elapsed or when the
user types any character on the keyboard or makes a pick
with the mouse in the Adams View window.
entity Self, Dependents, Specifies which entities related to the selected object are
Referents, Parts, All to be highlighted.
name at that time.
the model and part names, as well. For example, you may specify marker 'pivot' from model 'links',
the model and part names, as well. For example, you may specify arc 'end' on part 'arm' in model
default.
associated with it.

associated with it.
of the Adams statement type followed by the Adams data set constraint ID number. For example, the
name of Adams JOINT/101 is JOI101. If you created the constraint during preprocessing, you will
must enter its full name. To identify a constraint under a different model, for instance, you may need
to enter the model name as well. For example, you may specify constraint 'servo_motor' from model
'test' by entering ".test.servo_motor". If you type a "?", Adams View will list the constraints available
by default.
If the constraint is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple constraint picks by commas.
highlight 5
associated with it.
6. The object is defined by what you have selected to highlight and the associated objects that are
specified in the ENTITY parameter. Therefore, when the COLOR of an object is specified, all
objects specified in the entity parameter associated to that object are drawn with the specified
COLOR. Adams View supports the following COLOR: black, white, red, green, blue, cyan,
magenta, and yellow.
NOTE: If you choose the COLOR of an entity to be drawn in the view background color (typically
white or black ), it may not show up. See help for hardcopy.
7. The LINE_TYPE describes how the lines drawn for the wireframe representation of the highlighted
objects will look during highlighting. Adams View supports solid, dash, dotdash, and dot. Note that
objects highlighted with non-solid line types may look more indistinct as you zoom away from them.
---------------------------------------
solid -----------
dash - - - - - -
dotdash . _ . _ . _
dot . . . . . .
8. The “entity” parameter must be one of SELF, DEPENDENTS, REFERENTS, PARTS, or ALL.
SELF indicates that only the selected object is to be highlighted.
DEPENDENTS indicates that the entities that are dependent on the selected object are to be
highlighted. If a marker is selected, this would show any constraints, forces, geometry, or parts (if the
marker is the center of mass or inertia marker) that depend on it. If a joint is selected, this would show
any motions or couplers that depend on it.
REFERENTS indicates that the entities, on which the selected object is dependent, are to be
highlighted. For constraints, forces, and geometry, this will show any markers that they depend on.
For motions and couplers, this will show the joints they depend on.
PARTS indicates that any parts on which the selected object is dependent, usually indirectly through
one of the part's markers, are to be highlighted. For constraints and forces, this will show the parts
that the object affects directly. For dynamic (part-connecting) graphics, this will show the parts that
will affect their appearance.
ALL indicates that the selected object plus entities, that would be highlighted by the
DEPENDENTS, REFERENTS, and PARTS arguments, are to be highlighted.
hotspots 1
hotspots display
hotspots
hotspots display
Allows you to display hotspots. Hot spots are locations of high stress or strain on a flexible body or rigid stress
object. You can easily locate and view hot-spot information during animation displays in the Adams
PostProcessor. When the Adams Durability plugin is loaded, a Hot Spots tab is available on the Adams
PostProcessor dashboard for Animation displays. This tab allows you to define the hot spots and control their
display.
Hot-spot information is derived from the data that is generated and cached for a flexible body (or rigid stress
object) during contour animations. This allows the display and control of hot-spot information to be
completely interactive.
Hot spot visualization is currently supported for durability-type contours, such as stress, strain, or fatigue.
Deformations are not supported.
Format:
hotspots display
animation_name = existing animation
visibility = on/off
Example:
hotspots display &
visibility = on
Description:

Animation_name Existing Animation Specifies the animation on which the hotspot should be
displayed.
Visibility On/off Sets the visibility of the hotspot to ON or OFF.
hotspots filter
Allows you to filter the hotspots for display.
hotspots filter
Format:
hotspots filter
animation_name = Existing animation
type = count, threshold, percentage
value = real
sort = minimum, maximum, absolute
radius = real
Example:
hotspots filter &
type = threshold value = 29 &
sort = maximum&
radius = 0.8
Description:

Animation_name Existing Animation Name Specifies the name of an existing animation in which
the hotspots are to be filtered.
Type Count, Threshold, Percentage Selects the type of hot spots to be displayed
Value Real Selects the value of hot spots to be displayed
Sort Minimum, Maximum, Specifies the sorting option
Absolute
Radius Real Enters the distance between hot spots
1. Hot spots are locations of high stress or strain on a flexible body or rigid stress object. You can easily
locate and view hot-spot information during animation displays in the Adams PostProcessor. When
the Adams Durability plugin is loaded, a Hot Spots tab is available on the Adams PostProcessor
dashboard for Animation displays. This tab allows you to define the hot spots and control their
display.
Hot-spot information is derived from the data that is generated and cached for a flexible body (or
rigid stress object) during contour animations. This allows the display and control of hot-spot
information to be completely interactive.
Hot spot visualization is currently supported for durability-type contours, such as stress, strain, or
fatigue. Deformations are not supported.
hotspots 3
hotspots label
2. Hotspots could be of the following types:

• Count - Enter the number of top hot spots to be displayed.
• Threshold - Display only those hot spots that meet or exceed this value.
• Percentage - Specify the number of hot spots to be displayed as a percentage
3. Specify one of the following sorting options for the sort parameter:
• Absolute - The sign of the value is ignored when sorting hot spots. You would use this option
when only the magnitude is important and not the sign or direction (in case of stress or strain).
• Maximum - Hot spots are ranked from maximum to minimum.
• Minimum - Hot spots are ranked from minimum to maximum.
4. All nodes that fall within the radius specified by the radius parameter are candidates for the same hot
spot. A value of 0.0 considers all nodes to be potential hot spots.
hotspots label
Allows you to specify the settings for the label of the hotspot.
Format:
hotspots label
Animation_name = existing animation
Ranking = Boolean
Value = Boolean
Frame = Boolean
Node_id = boolean
Example:
hotspots label &
ranking = on &
value = on &
frame = on &
node_id = on
hotspots label
Description:

Animation_name Existing Animation Specifies the name of the animation in which the hotspot labels
need to be altered.
Ranking On/off Displays the sorting order of each hot spot, if turned ON.
Value On/off Displays the value of each hot spot, if turned ON.
Frame On/off Displays the frame when the value occurred, if turned ON.
NodE_id On/off Displays the node ID for that hot spot, if turned ON.
Tips:
1. If you do not select any of these options, Adams PostProcessor only displays a cross hair at each hot-
spot location.
2. The color of the hot-spot graphics is the same as the flexible body color.
3. Hot-spot graphics can be hidden by other graphics. For better viewing of hot spot graphics, try
rotating the display, making the flexible body transparent, or displaying only one body at a time using
the Component display feature in the Animation tab.
if 1
if
You can use the IF command with or without the ELSE command.
Format:
if
end
else
end
Example:
if condition=(db_exists ("mar1"))
marker modify marker= mar1 location=2,0,0
else
marker create marker=mar1 location=2,0,0
end
In the above example, if the marker MAR1 exists, Adams View modifies its location. If the marker does not
exist, Adams View creates it and sets its location.
Description:

Condition Expression If the expression evaluates to a non-zero value, Adams View executes the
commands following the IF or ELSEIF command up to the ELSE, when
present, or the END, if you do not use the ELSE. If the expression
evaluates to zero and you used ELSE, Adams View executes the
commands between the ELSE and the END commands.
else
end
real = (EVAL((variable_a < variable_b)? variable_a :
variable_b))
Tips:
1. You can have any number of ELSEIF CONDITION commands.
info_window 1
info_window close
info_window
info_window close
Allows you to close an info_window.
Adams view uses the Information window to display many different types of information about your model,
simulation, or motion data. In addition to just viewing information about your model, you can perform a
variety of operations in the Information window.
The information includes:
 Topology on the different objects in your model
 Object information, such as information about a part or a view
 Model verification results
 Measurements from one coordinate system marker to another
 Result set component information
 View attributes
 Results from a system command you run using the Tools -> System Command
The displayed info_window can be closed by using this command.
All the information about the model, simulation or motion data is displayed into the info_window. This
information can be saved to a file or the info_window can be emptied by ‘empty’ command. When not
needed it can be closed by using the ‘close’ command.
info_window empty
Allows you to empty the contents of an info_window.
 View attributes
info_window read
The contents of a info_window can be cleared by using this command.
1. The info_window contents can be cleared by using this command. The saved information about the
model, simulation or motion data can be read into the info_window by using ‘read’ command.
info_window read
Allows you to read the contents of a remote file to an info_window.
 View attributes
The contents of a saved file can be read into the info_window by using this command.
Format:
info_window read
file_name = string
Example:
info_window read &
file_name = "C:\ aview.log"
Description:

file_name String Specifies a remote file name from which the saved information can be
read.
info_window 3
info_window read
The saved information about the model, simulation or motion data can be read into the info_window by
using this command.
info_window read
interface 1
interface btn_stack create
interface
Allows you to create a new button stack.
The button stack is a stack of buttons which has multiple buttons attached to one button tab. The button
stack can be created by using this command.
Format:
btn_stack_name = a new GI_btn_stack
enabled = boolean
help_text = string
documentation_text = string
units = int_units
horiz_resizing = int_h_resize
vert_resizing = int_v_resize
location = real
height = real
width = real
Example:
interface btn_stack create &
btn_stack_name = .gui.cntrl.btn &
location = 0.0, 0.0 &
height = 0.5 &
width = 0.5 &
enabled = yes &
help_text = "help2text" &
documentation_text = "doc2text” &
units = relative &
horiz_resizing = attach_left &
vert_resizing = attach_top
interface btn_stack delete
Description:

btn_stack _name A New Specifies the name of a new button stack
GI_btn_stack
enabled Boolean Activates the btn stack
help_text String Specifies the help text
documentation_text String Specifies the documentation text
units Int_units Specifies the btn_stack size as pixel or relative to dialog box
window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for the btn_stack
vert_resizing Int_v_resize Specifies the attachment and scaling option for the btn_stack
location Real Specifies the location of the btn_stack on the dialog box
height Real Specifies the height of the btn_stack in terms of relative units
or pixel
width Real Specifies the width of the btn_stack field in terms of relative
units or pixel
1. The preliminary parameters of the btn_stack like size, placement and label are set using this
command.
2. The pop-up help and documentation help can be specified in appropriate columns.
3. The size of the btn_stack can be specified either in terms of number of pixels. Alternatively, the size
can also be stated as relative to the dialog box window
4. The vertical and horizontal resizing options are used to adjust the placement of the btn_stack on
existing dialog box. For example, attach_left; attach_top options for Horiz_resizing and Vert_resizing
will place the btn_stack on the top left corner of the dialog box. The location can also be specified
from the top left corner by adjusting the parameter ‘location’
5. The size of the btn_stack can be specified with respect to the dialog box window size. The value for
parameter height and width should be a real number between 0.0 and 2.0, where 2.0 represents the
height of the dialog window. Therefore, a value of 1.0 will set the btn_stack field window to be one
half as high as the dialog box window.

Allows you to delete an existing button stack.
interface 3
interface btn_stack display
Format:
btn_stack_name = an existing GI_btn_stack
Example:
interface btn_stack delete &
btn_stack_name = btn
Description:

btn_stack _name An Existing GI_btn_stack Specifies the name of an existing button stack
The btn_stack can be deleted by using this command.

Allows you to display an existing button stack.
The button stack may not be always displayed and it can be displayed by using this command.
Format:
Example:
interface btn_stack display &
Description:

interface btn_stack modify
The closed btn_stack can be displayed using this command

Allows you to modify an existing button stack.
Format:
new_btn_stack_name = a new btn_stack
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
Example:
interface btn_stack modify &
btn_stack_name = .gui.cntrl.btn &
new_btn_stack_name = .gui.cntrl.btn1 &
location = 0.0, 0.0 &
height = 0.5 &
width = 0.5 &
enabled = yes &
documentation_text = "doc2text” &
units = relative &
interface 5
Description:

btn_stack _name An Existing Specifies the name of an existing button stack
GI_btn_stack
new_btn_stack_name A New Specifies a new name for an existing btn_stack
GI_btn_stack
enabled Boolean Activates the btn stack
units Int_units Specifies the btn_stack size as pixel or relative to dialog box
window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for the
btn_stack
vert_resizing Int_v_resize Specifies the attachment and scaling option for the
btn_stack
location Real Specifies the location of the btn_stack on the dialog box
height Real Specifies the height of the btn_stack in terms of relative units
or pixel
width Real Specifies the width of the btn_stack field in terms of relative
units or pixel
1. The preliminary parameters of the btn_stack like size, placement, and name can be modified by using
this command.
3. The size of the btn_stack can be specified either in terms of number of pixels. Alternatively, the size
can also be stated as relative to the dialog box window
4. The vertical and horizontal resizing options are used to adjust the placement of the btn_stack on
will place the btn_stack on the top left corner of the dialog box. The location can also be specified
5. The size of the btn_stack can be specified with respect to the dialog box window size. The value for
height of the dialog window. Therefore, a value of 1.0 will set the btn_stack field window to be one
interface btn_stack undisplay

Allows you to close an existing button stack.
The button stack may not be always need to be displayed and hence it can be closed by using this command.
Format:
Example:
interface btn_stack undisplay &
Description:

The displayed btn_stack can be closed by using this command
interface cmd_window
Allows you to display the command window.
The command window displays is used to enter the command statements. It also prompts the error messages
for the bad syntax. The window help is available for completing the commands and syntax.
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. 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, when you type ‘?’ after initial letter of the command.
when you type ‘?’ after a command parameter, 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.
interface 7
interface container create
Format:
interface cmd_window
display = on_off_with_toggle
Example:
interface cmd_window &
display = toggle
Description:

display On_off_with_toggle Specify the mode of displaying the command window
The command window can be displayed or closed as and when required by using this command.

Allows you to create a new container on an existing dialog box.
The container is a submenu on the dialog box, which can collect other interface objects like buttons, option
menus, sliders and so on. The container can be used to segregate and ‘contain’ a set of menus and buttons on
the dialog box.
The container size and location is decided by this command.
Format:
container_name = a new GI_container
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real

start_commands = string
finish_commnads = string
sash_type = sash_type
position_of_sash = real
tab_label = string
Example:
interface container create &
container_name = .gui.dgbox.cntr &
enabled = yes &
help_text = "text2help" &
documentation_text = "txt2doc" &
units = relative &
vert_resizing = attach_top &
location = 0.0, 0.0 &
height = .4 &
width = .4 &
start_commands = "view center view=.gui.main.front
object=431.34, 7.4886913511, 0.0" &
finish_commands = "view center view=.gui.main.front object=-
431.34, -7.4886913511, 0.0" &
execution_commands = "view zoom view=.gui.main.front zoom=2." &
sash_type = horizontal &
position_of_sash = 0.9 &
tab_label = "contain"
Description:

container_name A New GI_container Specifies the name for a new container to be created
enabled Boolean Activates the container
interface 9

units Int_units Specifies the container size as pixel or relative to Adams
window
container
container
location Real Specifies the location of the container on the dialog box
height Real Specifies the height of the container in terms of relative
units or pixel
width Real Specifies the width of the container field in terms of
relative units or pixel
start_commands String Specifies the command associated with the container
finish_commands String Specifies the command associated with the container
execution_commnads String Specifies the command associated with the container
sash_type Sash_type Specifies the type of sash
position_of_sash Real Specifies the position of sash
tab_label String Specifies the label of the container
1. The preliminary parameters of the container like size, associated commands and editing capability are
set using this command.
2. The pop-up help and documentation help can be specified initially.
3. The size of the container can be specified either in terms of number of pixels. Alternatively, the size
can also be stated as relative to the Adams window.
4. The vertical and horizontal resizing options are used to adjust the placement of the container menu
on existing dialog box. For example, attach_left; attach_top options for Horiz_resizing and
Vert_resizing will place the container on the top left corner of the dialog box. The location can also
be specified from the top left corner by adjusting the parameter ‘location’.
5. The size of the container window can be specified with respect to the dialog box size value for
height of the dialog window. Therefore, a value of 1.0 will set the container field window to be one
half as high as the dialog box.
interface container delete
6. Each of the parameters start, finish and execution commands specifies the command associated with
the container. Each of these command will get executed for specific event. The command ‘display
container’ will execute the associated ‘start command’. The command ‘undisplay container’ will
execute associated ‘finish command’. The associated ‘execute command’ is executed explicitly by
running the ‘container execute command’.
7. You may want to expand the width, height of the container so you have more space for entering the
text. To expand the container, point to the sash on its border. When the cursor changes to a double-
sided arrow, drag the cursor to increase the container size. The value for ‘position_of_sash’ is 0.0 to
1.0.

Allows you to delete an existing container on the dialog box.
the dialog box.
The command is used to delete the container on the dialog box.
Format:
container_name = an existing GI_container
Example:
interface container delete &
container_name = ctr1
Description:

container_name An Existing GI_container Specifies the name for an existing container
1. The command is used to delete an existing container on the dialog box window.
interface container display

Allows you to display an existing container on the dialog box.
interface 11
interface container execute
the dialog box.
The container can be displayed by using this command.
Format:
interface container display
container_name = An Existing GI_container
Example:
interface container display &
container_name = .gui.dgbox.cntr1
Description:

 The container can be displayed or closed as the need arises by using the ‘container display’ and
‘container undisplay’ command.

Allows you to execute an existing container on the dialog box.
the dialog box.
The command is used to execute the container on the dialog box.
Format:
Example:
interface container execute &
container_name= contro1
interface container modify
Description:

 The command is used to execute an existing container on the dialog box window.

Allows you to modify an existing container on the dialog box.
the dialog box.
The container properties and name can be edited by this command.
Format:
new_container_name = A New GI_container
enabled = Boolean
help_text = String
documentation_text = String
units = Int_units
horiz_resizing = Int_h_resize
vert_resizing = Int_v_resize
location = Real
height = Real
width = Real
start_commands = String
finish_commnads = String
sash_type = Sash_type
position_of_sash = Real
tab_label = String
interface 13
Example:
interface container create &
container_name = .gui.dgbox.cntr &
enabled = yes &
documentation_text = "txt2doc" &
units = relative &
location = 0.0, 0.0 &
height = .4 &
width = .4 &
start_commands = "view center view=.gui.main.front
object=431.34, 7.4886913511, 0.0" &
finish_commands = "view center view=.gui.main.front object=-
431.34, -7.4886913511, 0.0" &
execution_commands = "view zoom view=.gui.main.front zoom=2." &
sash_type = horizontal &
position_of_sash = 0.9 &
tab_label = "contain"
Description:

new_container_name A New GI_container Specifies a new name for an existing container
enabled Boolean Activates the container
units Int_units Specifies the container size as pixel or relative to
Adams window
container
container

location Real Specifies the location of the container on the
dialog box
height Real Specifies the height of the container in terms of
width Real Specifies the width of the container field in terms
of relative units or pixel
start_commands String Specifies the command associated with the
container
finish_commands String Specifies the command associated with the
container
execution_commnads String Specifies the command associated with the
container
sash_type Sash_type Specifies the type of sash
position_of_sash Real Specifies the position of sash
tab_label String Specifies the label of the container
1. The container will be replaced by new name for any value of parameter ‘new_container_name’. The
preliminary parameters of the container like size, associated commands and editing capability are set
using this command.
3. The size of the container can be specified either in terms of number of pixels. Alternatively, the size
4. The vertical and horizontal resizing options are used to adjust the placement of the container menu
Vert_resizing will place the container on the top left corner of the dialog box. The location can also
5. The size of the container window can be specified with respect to the dialog box size value for
height of the dialog window. Therefore, a value of 1.0 will set the container field window to be one
half as high as the dialog box.
6. Each of the parameters start, finish and execution commands specifies the command associated with
the container. Each of these command will get executed for specific event. The command ‘display
container’ will execute the associated ‘start command’. The command ‘undisplay container’ will
execute associated ‘finish command’. The associated ‘execute command’ is executed explicitly by
running the ‘container execute command’.
interface 15
interface container undisplay
7. You may want to expand the width, height of the container so you have more space for entering the
text. To expand the container, point to the sash on its border. When the cursor changes to a double-
sided arrow, drag the cursor to increase the container size. The value for ‘position_of_sash’ is 0.0 to
1.0.

Allows you to close an existing container on the dialog box.
the dialog box.
The container can be closed by using this command.
Format:
container_name = an existing GI_container
Example:
interface container undisplay &
container_name = .gui.dgbox.cntr1
Description:

1. The container can be displayed or closed as the need arises by using the ‘container display’ and
‘container undisplay’ command.
interface coord_window
Allows you to display the coordinate window.
The coordinate window displays the coordinates of the location of the cursor on the Adams View window.
This shows the instantaneous coordinates of the cursor as it moves along the Adams View window. The
window can be displayed as and when required.
interface data_table clear
Format:
interface coord_window
display = on_off_with_toggle
Example:
interface coord_window &
display = toggle
Description:

display On_off_with_toggle Specify the mode of displaying the coordinate window
The coordinates of the cursor location on the Adams view window are displayed live in the coordinate
window. The window display can be controlled by ON, OFF, or TOGGLE mode.

Allows you to erase the contents of a data table.
The data table is similar to a excel workbook where a categorized data can be stored as array, locating each
item by its row and column index. The data table can be created on a dialog box and the data is displayed
using this command.
This command helps to clear any cell contents of the data table.
Format:
data_table_name = an existing GI_data_table
clear_target = clear_opts
Example:
interface data_table clear &
data_table_name = .gui.param.dtable &
clear_target = changed_cell_highlights
interface 17
interface data_table create
Description:

data_table _name An Existing GI_data_table Specifies the name of an existing data table
clear_target Clear_opt Specifies the action to be taken on the cell contents
1. The contents of a data table can be erased by clear command, when the ‘clear_target’ option is set to
‘cell_contents’
2. The contents of a cell in the data table get highlighted when the data table is edited. The highlighting
can be cleared by choosing ‘changed_cell_highlights’ for clear command. This will preserve the
contents of a cell, but the highlighting will be removed.
Tips:
The parameters ‘cell contents’ and ‘changed_cell_highlights’ are mutually exclusive.

Allows you to create a new data table.
using this command .
Format:
data_table_name = A New GI_data_table
enabled = Boolean
help_text = String
units = Int_units
location = Real
height = Real
width = Real
cell_select_commands = String
commands = String

editable = Boolean
auto_add_rows = Boolean
Example:
interface data_table create &
enabled = yes &
documentation_text = "text4doc" &
units = pixel &
location = 0.0, 0.0 &
height = 280 &
width = 360 &
commands = "interface dialog display dialog=.gui.about_Adams" &
cell_select_commands = “int dialog dis dialog=.gui.moag”&
editable = yes &
auto_add_rows = yes
Description:

data_table _name A New Specifies the name for a new data table to be created
GI_data_table
enabled Boolean Activates the data table
units Int_units Specifies the data table size as pixel or relative to Adams
window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for the data table
vert_resizing Int_v_resize Specifies the attachment and scaling option for the data table
location Real Specifies the location of the data table on the dialog box
height Real Specifies the height of the data table in terms of relative units
or pixel
interface 19
interface data_table delete

width Real Specifies the width of the data table field in terms of relative
units or pixel
cell select commands String Specifies the command to be executed whenever any cell is
selected
commands String Specifies the command to be executed
editable Boolean Allows editing the data table contents
auto_add_rows Boolean When paste area differs in size from copied selection, then it
will auto generate the rows to match copied selection.
1. The preliminary parameters of the data table like size, associated commands and editing capability are
set using this command. The data table is then by filled by entering the appropriate fields for row and
column. The data table with specified name is created on the dialog box If parameter ‘Enabled’ is set
to ON, the data table is be preactivated.
3. The size of the data table can be specified either in terms of number of pixels. Alternatively, the size
can also be stated as relative to the Adams window
4. The vertical and horizontal resizing options are used to adjust the placement of the data table menu
Vert_resizing will place the data table on the top left corner of the dialog box. The location can also
be specified from the top left corner by adjusting the parameter ‘location’
5. The size of the data table window can be specified with respect to the Adams window size. The value
for parameter height and width should be a real number between 0.0 and 2.0, where 2.0 represents
the height of the dialog window. Therefore, a value of 1.0 will set the data table field window to be
one half as high as the Adams View window.
6. ‘Cell select command’ gets executed whenever any cell is selected for editing.
7. The parameter ‘command’ specifies the name of the command to be executed.
8. The data table can be edited after initializing it if the BOOLEAN option is ‘yes’ for the parameter
‘editable’

Allows you to delete an existing data table.
using this command.
This command is used to delete any data table.
interface data_table display
Format:
Example:
interface data_table delete &
data_table_name = .gui.param2.dtable
Description:

data_table _name An Existing Specifies the name of an existing data table to be deleted
GI_data_table
The data table can be deleted by choosing the appropriate data_table_name for the command ‘interface
data_table delete’

Allows you to display an existing data table.
using this command.
The data table need not be always displayed on the screen. Whenever required, the appropriate data table can
be displayed by using this command.
Format:
Example:
interface data_table display &
data_table_name = .gui.atv.dtable
interface 21
interface data_table execute
Description:

data_table _name An Existing Specifies the name of an existing data table to be displayed
GI_data_table
The data table can be displayed by choosing the appropriate data_table_name and running the ‘display’
command.

Allows you to execute a command specified while creating a data table.
using this command
The data table may be linked to a relevant command to be executed. The command is run explicitly by this
command.
Format:
Example:
interface data_table execute &
data_table_name = .gui.param2.dtable
Description:

data_table _name An Existing Specifies the name of an existing data table for the
GI_data_table execution of a command.
Any command listed in the data table gets executed when the data table is edited, alternatively, this command
can be directly executed by the ‘execute’ option.
interface data_table insert column

Allows you to insert columns in a data table field.
Format:
width = integer
label = string
index = integer
value_type = text_type : string/integer/real/default
db_object_type = Ent
push_button_label = string
push_button_command = string
option_menu_choices = string
option_menu_command = string
toggle_button_label = string
toggle_button_command = string
Example:
1. Default Column
interface data_table insert column &
width = 3 &
label = length &
index = 1
2. Column cell value as Integer

width = 3 &
label = length &
index = 1 &
value_type = integer
interface 23
3. Column cell as push button widget

width = 3 &
label = length &
index = 1 &
push_button_label = "Modify" &
push_button_command = "marker modify marker_name=%1 location=%2,%3,%4"
Description:

data_table _name An Existing GI_data_table Specifies the name of an existing data table.
width Integer Specifies the width of a column.
label String Specifies the column label.
index Integer Specifies the column index.
value_type text_type Specifies column's cell text as string, integer,
real or default.
Column as database object
db_object_type Ent Specifies the entity type for column.
Column as push button
push_button_label String Specifies push button label for column.
push_button_command String Specifies the command to be executed on
push button click.
Column as option menu
option_menu_choices String Specifies option menu choices for column on
option change.
option_menu_command String Specifies the command to be executed.
Column as toggle button
toggle_button_label String Specifies toggle button label for column on
toggles buttons state change.
toggle_button_command String Specifies the command to be executed.
1. After creating the data table, the rows and columns can be created by using the ‘insert’ command.
2. The width of a column can be specified by the parameter 'width', similar to a spreadsheet. The width
can also be entered in mm or inches as desired.
3. The column can be labelled via the parameter 'label'. Moreover, the column can be directly accessed
using its index. The index of a column identifies its location similar to a 'label'.
4. Different data (value) types can be set per column. Data types are String, Integer, Real and Default.
Cell validation is based upon this setting. To set data type for a column set value_type as
a. String: This accepts only alpha numeric character string where first character is not a number or
a special character.
b. Integer: This accepts only integer value.
c. Real: This accepts floating value and integer value.
d. Default: This accepts all types (except widgets). Cell validation will NOT happen in this case.
5. Apart from basic data types, column can be of type Widgets.
• value_type and widgets are mutually exclusive to each other.
• Adams command can be associated with Widget type column.
• Adams command will be executed on Widget click operation.
• Adams command is single line command and is same for all widgets in that column.
• Column's cell values of that row can be used using %1, %2, %3 and so on, while writing Adams
command for Widget. Here, %1 is associated with the first cell of that row and %2 is associated
with the second cell of that row, and so on.
• Modifying column's Widget property will reset values of that Widget.
• Following widgets can be used.
a. DB object: Data table cell can accept exiting DB object.
On this object, standard RMB operations will be available.
b. Option Menu: Data table cell act as option menu.
c. Push Button: Data table cell act as push button.
d. Toggle Button: Data table cell act as toggle button.
Value of toggle button is "on" or "off".
Tips:
If the index of a column to be created already exists, then the existing column is shifted to the n+1th index,
where, n is the original index of the column.
To get the value of cells/widgets in CMD language use following function:
TABLE_GET_CELLS (table_name, start_row_index, end_row_index,
start_column_index, end_column_index, "blank", 0))
Users can set cell of the table using following Adams command:
"interface data_table set cell data_table_name= DATA_TABLE
row_index=index column_index=index string='value' "
interface 25
interface data_table insert row

Allows you to insert row in a data table field.
using this command.
This command is used to insert rows in a data table.
Format:
row_number = integer
number_to_insert = integer
column_indices = integer
insert_action = insert_actiion
Example:
interface data_table insert row&
row_number = 3 &
number_to_insert = 5 &
column_indices = 2,3 &
insert_action = before
Description:

data_table _name An Existing Specifies the name of an existing data table
GI_data_table
row_number Integer Specifies the row number where the row are to be added
number_to_insert Integer Specifies the number of rows to be added
column_indices Integer Specifies the column index to which the row is added
insert_action Insert_action Specifies whether the rows are to be added before or after the
‘row_number’
After creating the data table, the rows and columns can be created by using the ‘insert’ command.
interface data_table modify
The ‘row_number’ the row index where the row will be added . The number of rows added to this location
are decided by the parameter ‘number_to_insert’. Similarly, the parameter ‘insert action’ decides whether the
row will be added ‘before’ or ‘after’ the row indexed by the parameter ‘row_number’. As illustrated in the
above example five rows will be added after second row shifting the row 3 to 8th place.
Tips:
The rows and columns created will be symmetric independent of the column indices specified.

Allows you to modify existing data table
using this command
Once created, the parameters of the data table can be modified by using this command. It will not change
the contents of the cell but it will change the table properties.
Format:
new_data_table_name = a new data GI table
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
cell_select_commands = string
commands = string
editable = boolean
auto_add_rows = boolean
interface 27
Example:
interface data_table modify &
new_data_table_name = .gui.param2.dtable &
enabled = yes &
units = pixel &
location = 0.0, 0.0 &
height = 280 &
width = 360 &
cell_select_commands = “int dialog dis dialog=.gui.moag” &
editable = yes
auto_add_rows = yes
Description:

GI_data_table
new_data_table_name A New Specifies a new name for the existing data table
GI_data_table
enabled Boolean Activates the data table
units Int_units Specifies the data table size as pixel or relative to
Adams window
data table
data table
location Real Specifies the location of the data table on the dialog
box
interface data_table read

height Real Specifies the height of the data table in terms of
width Real Specifies the width of the data table field in terms of
cell select commands String Specifies the command to be executed for selecting a
cell
editable Boolean Allows editing the data table contents
auto_add_rows Boolean When paste area differs in size from copied selection,
then it will auto generate the rows to match copied
selection.
1. The preliminary parameters of the data table like size, associated commands and editing capability are
set using this command. The data table is then by filled by entering the appropriate fields for row and
column. The data table with specified name is created on the dialog box If parameter ‘Enabled’ is set
to ON, the data table is be preactivated. A new name can be applied to an existing data table by filling
the parameter ‘NEW GI TABLE NAME’
3. The size of the data table can be specified either in terms of number of pixels. Alternatively, the size
4. The vertical and horizontal resizing options are used to adjust the placement of the data table menu
Vert_resizing will place the data table on the top left corner of the dialog box. The location can also
be specified from the top left corner by adjusting the parameter ‘location’
5. The size of the data table window can be specified with respect to the Adams window size. The value
the height of the dialog window. Therefore, a value of 1.0 will set the data table field window to be
8. The data table can be edited after initializing it if the BOOLEAN option is ‘yes’ for the parameter
‘editable’

Allows you to read a remote file and importing the data to a data table field.
interface 29
interface data_table remove column
using this command.
Any existing numerical tabular data, for example, a tab delimited text file can be read into a data table, instead
of entering the elements manually.
Format:
file_name = string
Example:
interface data_table read &
data_table_name = .gui.atv.dtable1 &
file_name = "C:/data_1.txt"
Description:

data_table _name An Existing Specifies the name of an existing data table to be displayed
GI_data_table
file_name String Specifies the remote file name to be accessed
Specifies the name of the file that is to be read, written, or executed. 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.

Allows you to delete column in a data table field
using this command. This command is used to remove any column of the data table.
interface data_table remove row
Format:
data_table_name = An Existing GI_data_table
range = Integer
column_indices = Integer
use_column_selected = True_only
Example:
interface data_table remove column &
data_table_name = dtable &
range = 3,4
Description:

range Integer Specifies the range of columns to be removed
column_indices Integer Specifies the index of the column to be removed
use_column_selected True_only Specifies the selected column to be removed
1. Any number of columns can be removed either by selecting range or index of the column or by
selecting the column itself. Anyone of the parameters namely, 1) ‘range’, 2) column_indices, and, 3)
use selected column can be used to indicate the column to be removed. If the range is specified 2-7,
the value from 2 through 7 of the column index are selected to be removed. It set NONE for not
removing any column
Tips:
The parameters namely, 1) ‘range’, 2) column_indices, and, 3) use selected column are mutually exclusive to
each other.

Allows you to delete a row in a data table field.
using this command. This command is used to delete any row form the data table.
interface 31
Format:
range = Integer
row_numbers = Integer
use_row_selected = True_only
column_indices = Integer
Example:
interface data_table remove row &
data_table_name = .gui.atv.dtable &
range = 4,5 &
column_indices = 2
Description:

GI_data_table
range Integer Specifies the range of rows to be removed
row_numbers Integer Specifies the row numbers where the contents are to
be removed
use_row_selected True_only Specifies the rows from which the contents are to be
removed
column_indices Integer Specifies the index of the column to be in which the
row contents are to be removed
1. Any number of cell contents in a row can be removed either by selecting any of the three
combinations, namely, 1) range and column indices, 2) row_numbers and the column indices, or 3)
selected_row and column indices. Anyone of the parameters namely, 1) range, 2) row numbers and,
3) use selected row can be combined selected column to indicate the cell contents to be removed. If
the range is specified 2-7, the value from 2 through 7 of the row index are selected to be removed. It
set NONE for not removing any row.
Tips:
The parameters namely, 1) range, 2) row numbers, and, 3) use row selected are mutually exclusive to each
other.
interface data_table set cell

Allows you to alter the cells in a data table field.
using this command. The cell properties like width, contents and associated command can be edited by using
the set command.
Format:
use_cell_selected = True_only
row_range = Integer
column_range = Integer
order = Matrix_input_order
repeat_strings = Boolean
strings = String
reals = Real
action = Col_action
Example:
interface data_table set cell &
row_range = 18,19 &
column_range= 1,2 &
order = by_row &
repeat_strings = yes &
strings = this_is_to_append &
action = prefix
Description:

use_cell_selected True_only Specifies the cell of cells to be altered
use_row_selected True_only Specifies the row or rows to be altered
interface 33
interface data_table set column

row_range Integer Specifies the range of rows to be altered
column_range Integer Specifies the range of columns to be altered
order Matrix_input_order Specifies the of ascending/ descending arrangement
of cell content
repeat_strings Boolean Specifies the whether strings in the cell to be repeated
strings String Specifies the string to be appended
reals Real Specifies the REAL value to be inserted
action Col_action Specifies the insertion point of the string or reals
1. The contents of an existing cell of a data table can be altered using the ‘SET’ command. The cells
which will be altered can be specified by multiple – mutually exclusive – choices like
‘use_cell_selected’, ‘use_row_selected’, ‘row_range’, or ‘column _range’. The parameters
‘use_row_selected’ and ‘use_cells_selected’ can directly indicate the row or cells to be affected.
Alternatively, the range of cell or rows can be entered in the ‘row_range’ and column_range’
parameters. The order of the resulting rows or columns can be set by the parameter ‘order’, which
specifies whether the result set component is to be listed in ascending or descending order. If entered,
this parameter is used regardless of whether the values are to be printed to the terminal or to a file.
This parameter is optional and if not entered, it will default to "ascending" order. The two values for
the ORDER parameter are ‘by_row’ and ‘by_column’, which specifies whether the column or the row
is to be arranged in order.
2. If the cell contains the same strings or reals as the one to be entered after alteration, then whether the
strings is to be repeated or not is decided by the parameter ‘repeat_strings’. If the ‘repeat strings’ is set
to ‘yes’ then all the rows in the column will be replaced by new contents. On the other hand, if the
‘repeat_strings’ is set to ‘no’, then only first row of the column will be replaced by the new contents.
3. The parameter ‘string’ or ‘real’ is used to specify the new contents of the cell which may replace,
append or prefix the existing contents of the cell. To specify how the new contents would be inserted
in the existing cell contents, the parameter ‘action’ which has multiple options like ‘replace’, ‘append’,
or ‘prefix’ is used.
Tips:
The parameters ‘use_row_selected’ and ‘row_range’ are mutually exclusive.

Allows you to alter the columns in a data table field.
The data table is similar to a spreadsheet where categorized data can be stored as an array locating each item
by its row and column index. The data table can be created on a dialog box and the data is displayed using
this command.
The properties of an entire column within a data table can be edited using this command.
Format:
data_table_name= An Existing GI_DATA_TABLE
widths = Integer
labels = String
range = Integer
indices = Integer
strings = String
reals = Real
integers = Integer
repeat_strings = Boolean: yes/no
enabled = Boolean: yes/no
action = Col_action: replace/append/prefix
value_type = text_type
db_object_type = Ent
push_button_label = string
push_button_command = string
option_menu_choices = string
option_menu_command = string
toggle_button_label = string
toggle_button_command = string
Example:
1. Change cell value of column

interface data_table set column &
widths = 3 &
labels = Frequency, amplitude &
range = 1,2 &
reals = 1001 &
interface 35

enabled = yes &
action = replace
2. Set columns value type

widths = 3 &
range = 1,2 &
value_type = integer
3. Use column as widget

widths = 3 &
range = 1,2 &
push_button_label = "Modify" &
push_button_command = "marker modify marker_name=%1 location=%2,%3,%4"
Description:

data_table _name An Existing Specifies the name of an existing data table.
GI_data_table
widths Integer Specifies the new widths for existing columns.
labels String Specifies the new labels for existing columns.
use_column_selected True_only Specifies the range of columns to be altered.
range Integer Specifies the range of columns to be altered.
indices Integer Specifies the range of columns to be altered.
strings String Specifies the new STRING contents for the cells.
reals Real Specifies the new REAL contents for the cells.
integers Integer Specifies the new INTEGER contents for the cells.
repeat_strings Boolean Specifies whether same STRING or REAL will be inserted
to all marked cells; valid options are yes/no.

enabled Boolean Specifies if the columns are read only or editable; valid
options are yes/no.
action Col_action Specifies the mode of insertion of new contents in to the
cells; valid options are replace/append/prefix.
value_type text_type Specifies column's cell text as string, integer, real or default.
Column as database object
db_object_type Ent Specifies the entity type for column.
Column as push button
push_button_label String Specifies push button label for column.
push_button_command String Specifies the command to be executed on push button
click.
Column as option menu
option_menu_choices String Specifies option menu choices for column on option
change.
option_menu_command String Specifies the command to be executed.
Column as toggle button
toggle_button_label String Specifies toggle button label for column on toggles buttons
state change.
toggle_button_command String Specifies the command to be executed.
‘use_cell_selected’, ‘range’, or ‘indices’. The parameter ‘use_cells_selected’ can directly indicate the
cells to be affected. Alternatively, the range of cell in a column can be entered in the ‘range’ or indices
parameters. Specifying the range as ‘1,6’ or entering respective column numbers as ‘1,2,3,4,5,6’ will
alter the columns with indices 1 through 6. As the three parameters namely, 1) use_column_selected,
2) range, and 3) indices are mutually exclusive, any one of the parameter is sufficient to specify the
columns to be altered.
2. The parameter 'repeat_strings' is used to determine if all rows in the column should be set with the
same values. If 'repeat strings' is set to 'yes' then all the rows in the column will be replaced by new
contents. On the other hand, if 'repeat_strings' is set to 'no', then only the first row of the columns
will be replaced by the new contents, hence the new contents will appear only once in each column.
If the values should be repeated for all the rows then the parameter 'repeat strings' needs to be set to
'yes'.
3. The parameter 'strings' or 'reals' is used to specify the new contents of the cell which may replace,
append or prefix the existing contents of the cell. To specify how the new contents should be inserted
in the existing cell contents, the parameter 'action' has the options 'replace', 'append', or 'prefix'.
interface 37
4. The parameter 'enabled' is used to specify if the specified columns can be editable or not. The rows
are specified using the use_column_selected/range/indices parameter as discussed earlier.
5. Changing columns data, value_type and widgets are mutually exclusive.
6. Different data (value) types can be set per column. Data types are String, Integer, Real and Default.
Cell validation is based upon this setting. To set the data type for a column set value_type as
a. String: This accepts only alpha numeric character string where first character is not a number or
a special character.
b. Integer: This accepts only integer value.
c. Real: This accepts floating value and integer value.
d. Default: This accepts all types (except widgets). Cell validation will NOT happen in this case.
7. Apart from the basic data types, columns can be of type Widgets.
• value_type and widgets are mutually exclusive to each other.
• Adams command can be associated with Widget type column
• Adams command will be executed on widget click operation.
• Adams command is single line command and is same for all widgets in that column.
• Column's cell values of that row can be used using %1, %2, %3 and so on, while writing Adams
command for Widget. Here, %1 is associated with the first cell of that row and %2 is associated
with the second cell of that row, and so on.
• Modifying column's Widget property will reset values of that Widget.
• Following widgets can be used.
a. DB object: Data table cell can accept exiting DB object.
On this object, standard RMB operations will be available.
b. Option Menu: Data table cell act as option menu.
c. Push Button: Data table cell act as push button.
d. Toggle Button: Data table cell act as toggle button.
Valid values of any toggle button are "on" or "off".
Tips:
The parameters ‘use_column_selected’, ‘range’ and ‘indices’ are mutually exclusive. Any one of those is
sufficient to indicate the cell to be altered.
To get the value of cells in CMD language use following function:
TABLE_GET_CELLS (table_name, start_row_index, end_row_index,
start_column_index, end_column_index, "blank", 0))
Users can set cells of the table using following Adams command:
"interface data_table set cell data_table_name= DATA_TABLE
row_index=index column_index=index string='value'"
interface data_table set row

Allows you to alter the rows in a data table field.
using this command.
The row properties of a data table can be edited using the ‘set row’ command.
Format:
use_row_selected = true_only
range = integer
indices = integer
strings = string
reals = real
repeat_strings = boolean
enabled = boolean
action = col_action
Example:
interface data_table set row &
indices = 2,4 &
strings = none &
action = replace &
enabled = yes
Description:

GI_data_table
use_row_selected True_only Specifies the range of rows to be altered
range Integer Specifies the range of rows to be altered
indices Integer Specifies the range of rows to be altered
interface 39
interface data_table set selected

strings String Specifies the new STRING contents for the cells in the row
reals Real Specifies the new REAL contents for the cells in the row
repeat_strings Boolean Specifies whether same STRING or REAL contents will be
inserted to all marked cells
action Col_action Specifies the mode of insertion of new contents in to the cells
of the row
enabled Boolean Specifies if the rows are read only or editable
‘use_row_selected’, ‘range’, or ‘indices’. The parameter ‘use_row_selected’ can directly indicate the
cells to be affected. Alternatively, the range of rows can be entered in the ‘range’ or indices parameters.
Specifying the range as ‘1,6’ or entering respective row numbers as ‘1,2,3,4,5,6’ will alter the rows
with indices 1 through 6. As the three parameters namely, 1) use_column_selected, 2) range, and 3)
indices are mutually exclusive, any one of the parameter is sufficient to specify the rows to be altered.
2. If the cell contains the same strings or reals as the one to be entered after alteration, then whether the
strings is to be repeated or not is decided by the parameter ‘repeat_strings’. If the ‘repeat strings’ is set
to ‘yes’ then all the cells in the rows will be replaced by new contents. On the other hand, if the
‘repeat_strings’ is set to ‘no’, then only first cell of the row will be replaced by the new contents, hence
the new contents will appear only once in each row. If the values are repeated for all the cells in a row
then the parameter ‘repeat strings’ need to be set to ‘yes’.
3. The parameter ‘string’ or ‘real’ is used to specify the new contents of the cell which may replace,
append or prefix the existing contents of the cell. To specify how the new contents would be inserted
in the existing cell contents, the parameter ‘action’ which has multiple options like ‘replace’, ‘append’,
or ‘prefix’ is used.
4. The parameter 'enabled' is used to specify if the specified rows can be editable or otherwise. The rows
are specified using the use_row_selected/range/indices parameter as discussed earlier.
Tips:
The parameters ‘use_row_selected’, ‘range’ and ‘indices’ are mutually exclusive. Any one of those is sufficient
to indicate the cell to be altered.

Allows you to alter the selected cells in a data table field
using this command.
The selected cell of a data table can be edited using the ‘set selected’ command.
Format:
strings = string
reals = real
repeat_strings = boolean
action = col_action
Example:
interface data_table set selected &
strings = select_new &
action = replace &
repeat_strings = yes
Description:

GI_data_table
strings String Specifies the new STRING contents for the selected cells
reals Real Specifies the new REAL contents for the selected cells
repeat_strings Boolean Specifies whether same STRING or REAL contents will be
inserted to all marked cells
action Col_action Specifies the mode of insertion of new contents in to the
selected cells
The contents of an existing cell of a data table can be altered using the ‘SET’ command. The cells which will
be altered can be are selected first and then the command is entered.
If the cell contains the same strings or reals as the one to be entered after alteration, then whether the strings
is to be repeated or not is decided by the parameter ‘repeat_strings’. If the ‘repeat strings’ is set to ‘yes’ then
all the selected will be replaced by new contents. On the other hand, if the ‘repeat_strings’ is set to ‘no’, then
only first selected of the group will be replaced by the new contents, hence the new contents will appear only
once. If the values are repeated for all the selected cells then the parameter ‘repeat strings’ need to be set to
‘yes’.
interface 41
interface data_table sort
The parameter ‘string’ or ‘real’ is used to specify the new contents of the cell which may replace, append or
prefix the existing contents of the cell. To specify how the new contents would be inserted in the existing cell
contents, the parameter ‘action’ which has multiple options like ‘replace’, ‘append’, or ‘prefix’ is used.
Tips:
Select the cell to be altered first and then execute the command.

Allows you to arrange the cell contents in a data table field.
using this command.
The elements of a table can be sorted using the ‘table sort’ command
Format:
sort_column_index = Integer
affected columns = Integer
order = Sort_order
Example:
Interface data_table sort &
data_table_name = dtable &
sort_column_index = 1 &
affected_columns = 2 &
order = ascending &
type_of_sort = alphabetic
Description:

GI_data_table
interface data_table undisplay

sort_column_index Integer Specifies the index of the column to be sorted
affected columns Integer Specifies the range of columns associated with the
column to be sorted
order Sort_order Specifies the mode of sorting the cell contents
1. The contents of a column can be sorted in ascending or descending order. The sorting can be numeric
or alphabetical. Generally, the column will have one or more associated columns which will get
affected due to reallocation of the column to be sorted. Hence, the associated column contents also
need to be repositioned in accordance with the column sorted. This can be easily achieved by directly
choosing the ‘affected columns’. Hence, there is no need of repositioning of the cell contents of
associated columns.

Allows you to close an existing data table.
using this command.
The data table need not be always displayed, whenever required it can be closed by using this command.
Format:
Example:
interface data_table undisplay &
data_table_name = .gui.atv.dtable
Description:

data_table _name An Existing GI_data_table Specifies the name of an existing data table to be closed
The data table can be closed by choosing the appropriate data_table_name and running the ‘undisplay’
command
interface 43
interface data_table write

Allows you to write the contents of a data table field to a file.
using this command.
The contents of a data table can be directly stored in a file, for example, excel sheet or a tab delimited text file.
Format:
file_name = String
row_labels = Boolean
column_labels = Boolean
Example:
interface data_table write &
data_table_name = .gui.atv.dtable1 &
file_name = "C:/data_2.xls"
Description:

data_table _name An Existing GI_data_table Specifies the name of an existing data table to be
displayed
row_labels String Specifies whether existing row labels to be exported
column_labels String Specifies whether existing column labels to be
exported
1. ‘File_name’ specifies the name of the file that is to be read, written, or executed. The proper extension
is 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. If the BOOLEAN value for ‘row labels’ and ‘column labels’ is ‘yes’ then existing labels of the rows
and columns are exported along with the data_table contents.
interface database_navigator
Allows the creating a database_navigator.
The Database Navigator has several modes in which you can display object information. It can be set to just
let you browse for objects or you can set it to rename objects, view information about the objects, such as
view how the object relates to other objects, and view dependencies. The Database Navigator only displays
the types of objects that are appropriate for the command you are executing. For example, if you are renaming
a model, it only displays models in your database. On the other hand, if you are searching for any modeling
object in the database, it displays all types of modeling objects. You can also set a filter for the types of objects
that the Database Navigator displays. The Database Navigator shows objects in their database hierarchy. The
following figure shows the Database Navigator with the top-level modeling objects in a small database that
contains one model, model_1. These objects do not have parents. Double-click the name of a model, in this
case model_1, to find all the objects belonging to that model. The associativity, for example, the i_marker
and j_marker for a link can also be displayed. The display mode can thus be browse, graphical_topology,
topology_by_parts, topology_by_connections, associativity, information, rename, comments, select_list, and
display_attribute. The database navigator can also display the topology of the parts, that is, kind of
connectivity among the objects. It can display the same by graphical topology which is very convenient to
understand the model topology.
Format:
top_object = an_existing_entity
name_filter = string
type_filter = ent
display = on_off
mode = mode_options
Example:
interface database_navigator &
top_object = model_1 &
name_filter = link &
type_filter = joint &
display = on &
mode = graphical_topology
interface 45
interface dialog_box build
Description:

top_object An Existing Entity Specifies the top object, all the objects belonGIng to it will be
displayed
name_filter String Specifies the name of a object under top object, all the objects
belonGIng to it will be displayed
type_filter Ent Specifies the type of entities which will be displayed
display On_off Specifies the default parameter for displaying database navigator
mode Mode_options Specify the mode of displaying the objects beneath the
top_object
1. The ‘top_object’ is the object under which all the objects are arranged in hierarchical form in the
database navigator. If the ‘model’ is chosen as the ‘top_object’, it will list all the objects in the model.
On the other hand if a entity in the model, for example, ‘PART_4’ is chosen as the ‘top_object’ then
the listing starts from the ‘PART_4’ covering all the objects under ‘PART_4’.
2. The ‘name filter’ specifies the name of the object for the all the dependent parts are to be displayed.
For example, name filter ‘PART_1’ will display all the objects belonGIng to the ‘PART_1’
irrespective of the type of objects, for example, revolute joint, measure, marker and so on.
3. The ‘type filter’ specify the type of objects allowed. When specifying the objects for this operation a
wild cards can be used, which may result in too many objects being found. For example, if all the parts
for model MOD1 are desired, specifying .MOD1.* will get not only the parts, but all children of the
model, like joints, forces and so on. Using the parameter TYPE_FILTER=part will result in only the
parts being processed by this command.
4. The default parameter for ‘display’ can be set ‘on’ or ‘off’. The database navigator has several modes
of display as browse, graphical_topology, topology_by_parts, topology_by_connections,
associativity, information, rename, comments, select_list, and display_attribute. Depending on the
user requirement any useful mode can be selected such as for renaming few objects from the database,
the database can be opened in ‘renaming’ mode, it will display the names in database which can be
renamed as required. Similarly, if the display attributes like, color, transparency and so on, are to be
changed then the models can be browsed in that mode where one can change the display attributes
selectively.

Allows you to build-up and edit a dialog box, as well as create menus on the dialog box.
The dialog box is a blank interface window created where various buttons and option menus can be placed.
The build command opens up a building-box window with various option, which help one to edit the dialog
box properties as well as creating new menus and buttons on the existing dialog box.
interface dialog_box create
Format:
dialog_box_name = An Existing GI_dbox
Example:
interface dialog_box build &
dialog_box_name = .gui.dgbox
Description:

dialog_box _name An Existing GI_dbox Specifies the name of an existing dialog box
1. The blank dialog box is created with initial size, appearance and editing options. This dialog box can
grab various kinds of input like, push buttons, container, option menus and so on. To create these
interface options on the dialog box window. The build command can be used. The build command
opens up a new dialog box building window, with which we can edit the existing dialog box, as well
as add different menus on it.
2. The build window offers option like layout, appearance, command and help.
3. With appearance tab on build window we can edit the location and size of the dialog box. The
appearance tab on the build window helps to edit the properties like resizing ability, decorating and
iconification and so on. The command tab is used to specify the ‘start’, ‘finish’ and ‘execute’
commands.
4. The create tab on the build window is used to create various interface options like field, separator,
radio button, option menu, and so on.
5. The build box offers other capabilities like, edit, create, option, preference for building a complete
dialog box.

Allows you to create a new dialog box window.
The size and editing capabilities are set by this command for the dialog box.
interface 47
Format:
dialog_box_name = a new GI_dbox
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
title = string
icon_label = string
start_commnads = string
finish_commands = string
execution_commands = string
decorate = boolean
resizable = boolean
width_minimum = real
width_maximum = real
height_minimum = real
height _maximum = real
grab_all_input = boolean
iconifiable = boolean
Example:
interface dialog_box create &
dialog_box_name = dbox &
enabled = yes &
help_text = text2help &
documentation_text = text2doc &
units = relative &
interface dialog_box create &

location = 0.4,0 &
height = 0.4 &
width = 0.4 &
title = dbox &
icon_label = iconic_label &
start_commands = "interface coord_window display=toggle" &
finish_commands = "view zoom view=.gui.main.front zoom=1.1" &
execution_commands = "interface dialog display dialog=.gui.about_Adams" &
decorate = yes &
resizable = yes &
width_minimum = 0.3 &
width_maximum = 0.6 &
height_minimum = 0.3 &
height_maximum = 0.6 &
grab_all_input = no &
iconifiable = yes
Description:

dialog_box _name A New GI_dbox Specifies the name of a new dialog box
enabled Boolean Activates the info dialog box
units Int_units Specifies the dialog box window size as pixel or relative
to Adams window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for dialog
box
vert_resizing Int_v_resize Specifies the attachment and scaling option for dialog
box
location Real Specifies the location of the dialog box
height Real Specifies the height of the dialog box in terms of relative
units or pixel
interface 49

width Real Specifies the width of the dialog box in terms of relative
units or pixel
title String Specifies the title for the dialog box
iconic_label String Specifies the label to appear on a minimized window
icon
start_commands String Specifies the command associated with the dialog box
finish_commands String Specifies the command associated with the dialog box
execution_commands String Specifies the command associated with the dialog box
decorate Boolean Specifies the peripheral outline decorating for dialog
box
resizable Boolean Specifies the resizing ability of the dialog box
width_minimum Real Specifies the minimum size of the window to be dragged
width_maximum Real Specifies the maximum size of the window to be dragged
height_minimum Real Specifies the maximum size of the window to be dragged
height_maximum Real Specifies the maximum size of the window to be dragged
grab_all_input Boolean Specifies the input type
iconifiable Boolean Specifies whether the window can be iconified
1. A new dialog box created if a dialog box with specified name do not exist. The dialog box can grab all
kinds of interface inputs on the push_button, toggle_button, option menu, and so on. The dialog
box is enabled by setting the parameter to yes.
2. The dialog box is displayed by using ‘display’ command.
3. . The pop-up help and documentation help is be specified for the respective parameters.
4. The size of the dialog box can be specified either in terms of number of pixels. Alternatively, the size
5. The vertical and horizontal resizing options are used to adjust the placement of the dialog box on
will place the dialog on the top left corner of the dialog box. The location can also be specified from
the top left corner by adjusting the parameter ‘location’
6. The size of the dialog box can be specified with respect to the Adams window size. The value for
height of the Adams View window. Therefore, a value of 1.0 will set the info window to be one half
as high as the Adams View window.
interface dialog_box delete
7. Initial height and width of the dialog box appearing on screen can be set by ‘height’ and ‘width’. If
the dialog box is made ‘resizable’ it can be dragged to resize. The resizing limits are set by the
parameters ‘height_minimum’, ‘height_maximum’, ‘width_minimum’, and ‘width_maximum’
respectively.
8. If the dialog box is made iconifiable, then it can be minimized or maximized by clicking the ‘_ ‘ and
square appearing on upper right corner. Once minimized the icon on the taskbar shows the label set
by the parameter ‘iconic_label’
9. The ‘decorate’ parameter if set to ‘no’, it will show a blank dialog box without any peripheral
decorating outline.
10. The ‘start_commands’, ‘finish_commands’, and ‘execution_commands’ are the commands
associated with the dialog box, which can be executed explicitly. The ‘start command’ gets executed
when the dialog box is displayed, whereas the ‘finish_command’ gets executed when the dialog box
is closed and the ‘execute_command’ will be run when the ‘dialog_box execute’ command is run
explicitly.

Allows you to delete an existing dialog box window.
The dialog box can be deleted by this command.
Format:
dialog_box_name = An Existing GI_dbox
Example:
interface dialog_box delete &
Description:

1. The dialog box can be deleted by using this command. It will delete all the child-menus like buttons,
option menus and menus created on the dialog box.
interface 51
interface dialog_box display

Allows you to display existing dialog box window.
The dialog box may not be required to be displayed always. It can be displayed by the command as the need
arises.
Format:
dialog_box_name = an existing GI_dbox
parameter = string
Example:
interface dialog_box display &
dialog_box_name = .gui.dgbox &
parameter = STRING
Description:

parameter String Specifies the parameter for dialog box display
1. The dialog box may not be required to be displayed every time, and can be displayed or closed by
using the ‘dialog_box display’ and ‘dialog_box undisplay’ commands respectively.
2. The ‘start_command’ associated with the dialog get executed when the dialog box is displayed.
interface dialog_box execute

Allows you to execute of the command associated with the dialog box.
The ‘execute command’, if specified is run when the ‘dialog box execute’ command is run. The dialog box
may be closed after the execution of the command, if specified.
interface dialog_box modify
Format:
interface dialog_box execute
undisplay = boolean
Example:
interface dialog_box execute &
undisplay = yes
Description:

undisplay Boolean Specifies if the dialog box is closed after execution
1. The command specified as ‘execution_command’ get executed with this command statement.
2. If the parameter ‘undisplay’ is set to ‘yes’, the dialog box will be closed with execution of the this
command.

Allows you to modify an existing dialog box window.
The size and editing capabilities are modified by this command for the dialog box.
Format:
new_dialog_box_name = a new GI_dbox
enabled = boolean
help_text = string
units = int_units
interface 53

location = real
height = real
width = real
title = string
icon_label = string
start_commnads = string
finish_commands = string
execution_commands = string
decorate = boolean
resizable = boolean
height _maximum = real
grab_all_input = boolean
iconifiable = boolean
Example:
interface dialog_box modify &
new_dialog_box_name = .gui.dgbox2 &
enabled = yes &
help_text = text2help &
documentation_text = text2doc &
units = relative &
location = 0.4,0 &
height = .4 &
width = 0.4 &
title = dbox &
icon_label = minimized_dgbox &
start_commands = "interface coord_window display=toggle" &
interface dialog_box modify &

finish_commands = "view zoom view=.gui.main.front zoom=1.1" &
execution_commands = "interface dialog display dialog=.gui.about_Adams" &
decorate = yes &
resizable = yes &
width_minimum = 0.3 &
width_maximum = 0.6 &
height_minimum = 0.3 &
height_maximum = 0.6 &
grab_all_input = yes &
iconifiable = yes
Description:

dialog_box _name An Existing Specifies the name of an existing dialog box
GI_dbox
new_dialog_box_name A New GI_dbox Specifies a new name for an existing dialog box
enabled Boolean Activates the info dialog box
units Int_units Specifies the dialog box window size as pixel or relative
to Adams window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for dialog
box
vert_resizing Int_v_resize Specifies the attachment and scaling option for dialog
box
location Real Specifies the location of the dialog box
height Real Specifies the height of the dialog box in terms of relative
units or pixel
width Real Specifies the width of the dialog box in terms of relative
units or pixel
title String Specifies the title for the dialog box
iconic_label String Specifies the label to appear on a minimized window
icon
start_commands String Specifies the command associated with the dialog box
finish_commands String Specifies the command associated with the dialog box
interface 55

execution_commands String Specifies the command associated with the dialog box
decorate Boolean Specifies the peripheral outline decorating for dialog
box
resizable Boolean Specifies the resizing ability of the dialog box
width_minimum Real Specifies the minimum size of the window to be
dragged
width_maximum Real Specifies the maximum size of the window to be
dragged
height_minimum Real Specifies the maximum size of the window to be
dragged
height_maximum Real Specifies the maximum size of the window to be
dragged
grab_all_input Boolean Specifies the input type
iconifiable Boolean Specifies whether the window can be iconified
1. The existing dialog box will be renamed if the parameter ‘new_dialog_box_name’ is specified. The
dialog box can grab all kinds of interface inputs on the push_button, toggle_button, option menu,
and so on. The dialog box is enabled by setting the parameter to yes.
2. The dialog box is displayed by using ‘display’ command
3. The pop-up help and documentation help is be specified for the respective parameters.
4. The size of the dialog box can be specified either in terms of number of pixels. Alternatively, the size
5. The vertical and horizontal resizing options are used to adjust the placement of the dialog box on
will place the dialog on the top left corner of the dialog box. The location can also be specified from
6. The size of the dialog box can be specified with respect to the Adams window size. The value for
height of the Adams View window. Therefore, a value of 1.0 will set the info window to be one half
7. Initial height and width of the dialog box appearing on screen can be set by ‘height’ and ‘width’. If
the dialog box is made ‘resizable’ it can be dragged to resize. The resizing limits are set by the
parameters ‘height_minimum’, ‘height_maximum’, ‘width_minimum’, and ‘width_maximum’
respectively.
8. If the dialog box is made iconifiable, then it can be minimized or maximized by clicking the ‘_ ‘ and
square appearing on upper right corner. Once minimized the icon on the taskbar shows the label set
by the parameter ‘iconic_label’
interface dialog_box undisplay
9. The ‘decorate’ parameter if set to ‘no’, it will show a blank dialog box without any peripheral
decorating outline.
10. The ‘start_commands’, ‘finish_commands’, and ‘execution_commands’ are the commands
associated with the dialog box, which can be executed explicitly. The ‘start command’ gets executed
when the dialog box is displayed, whereas the ‘finish_command’ gets executed when the dialog box
is closed and the ‘execute_command’ will be run when the ‘dialog_box execute’ command is run
explicitly.

Allows you to close an existing dialog box window.
The dialog box may not be required to be displayed always. It can be displayed by the command as the need
arises.
Format:
Example:
interface dialog_box undisplay &
Description:

1. The dialog box may not be required to be displayed every time, and can be displayed or closed by
using the ‘dialog_box display’ and ‘dialog_box undisplay’ commands respectively.
2. The ‘finish_command’ associated with the dialog get executed when the dialog box is closed.
interface entity modify

Is used to modify the 'enabled' and 'display' attributes of any GUI entity, such as a label, push button, filed
or even a dialog box.
interface 57
Format:
entity_name = GRAPHIC_USER_INTERFACE
enabled = YES_NO_NO_OPINION
displayed = YES_NO_NO_OPINION
Example:
interface entity modify &
entity_name = .gui.spline_cremod.c_tabular &
enabled = NO &
displayed = No_OPINION
Description:

entity_name AN EXISTING Specifies the name of an existing Graphic User
GRAPHIC_USER_INTERFACE Interface such as a push button, field, label, dialog
box and so on.
enabled YES_NO_NO_OPINION Specifies if the entity is editable or otherwise. A no-
opinion means that the enabled state of the entity is
maintained "as-is".
displayed YES_NO_NO_OPINION Specifies if the entity is visible or otherwise. A no-
opinion means that the enabled state of the entity is
maintained "as-is".
1. The command is used to modify the "enabled" and "displayed" attributes of GUI entities such as a
field, push button dialog and so on.
2. Remember that the rules of hierarchy apply here. For example, if a container is disabled (enabled is
set to 'no'), then all elements on the container become disabled as well. When the container is enabled
thereafter, the elements on the container, will regain their previous states. For example, if a field on
the container were disabled (explicitly) before the container was disabled, it will remain so, even after
the container is enabled again.
3. A no-opinion for the displayed/enabled attributes means that the attribute of the entity in
consideration will remain unchanged. This is particularly useful, when only one of the attributes
(either "displayed" or "enabled") needs to be changed, without altering the other.
interface field copy

Allows you to copy the contents of a field to another field.
A field is a space on a dialog box where a data elements can be entered and displayed.
The field contents can be copied to another location by using this command.
Format:
field_name = An Exisitng GI_field
Example:
interface field copy &
field_name = .gui.ATC.flde
Description:

field _name An Existing GI_field Specifies the name of an existing field
 The command allows copying the contents of a field to another field.
interface 59
interface field create

Allows you to create a new field menu.
Format:
field_name = A New GI_field
enabled = Boolean
help_text = String
units = Int_units
location = Real
height = Real
width = Real
preload_strings = String
commands = String
scrollable = Boolean
editable = Boolean
required = Boolean
execute_cmds_on_exit= Boolean
number_of_values= Integer
string_type= Str_type
add_quotes= Add_quotes
object_type = New_old_any
type_filter = Ent
name_filter = String
numeric_type = Num_type
lower_check = Low_check
lower_limit = Real
upper_check = Upp_check
upper_limit = Real

file_type = New_old_any
directory = String
filter = String
alert_on_overwrite = Boolean
browse_action = Open_save
word_wrap = Boolean
Example:
interface field create &
field_name = .gui.ATC.flde &
enabled = yes &
help_text = hlp_txt &
documentation_text = doc_txt &
units = relative &
location = 0.1,0.1 &
height = 0.3 &
width = 0.3 &
preload_string = predefined_txt_display &
commands = "interface coord_window display=toggle" &
scrollable = yes &
editable = yes &
required = yes &
execute_cmds_on_exit = yes &
number_of_values = 1 &
string_type = alpha_numeric &
add_quotes = yes
interface 61
Description:

field _name A New GI_field Specifies the name of a new field
enabled Boolean Activates the field
units Int_units Specifies the field size as pixel or relative to Adams
window
filed
field
location Real Specifies the location of the field on the dialog box
height Real Specifies the height of the field in terms of relative
units or pixel
width Real Specifies the width of the field in terms of relative units
or pixel
preload strings String Specifies the initial text to be displayed
commands String Specifies the command to be executed after exiting the
field
scrollable Boolean Specifies the scroll bar option of the field
editable Boolean Allows editing the field contents
required Boolean Specifies whether field is required or optional
execute_cmds_on_exit Boolean Sets the BOOLEAN parameter for execution of
command after exiting field
number_of_values Integer Specifies the number of values allowed in the field
string_type add_quotes Add_quotes Specifies addition of quotes to the string
object_type New_old_any Specifies the object allowed in the field
name_filter String Specifies the name_filter for the object
numeric_type Num_type Specifies the type of numeric objects allowed
lower_check Low_check Specifies the applicability of lower check
lower_limit Real Specifies lower limit for lower check of numeric value
upper_check Upp_check Specifies the applicability of upper check
upper_limit Real Specifies upper limit for upper check of numeric value

file_type New_old_any Specifies the types of file allowed in the field
directory String Specifies the directory for the file
filter String Tests each value of the component
alert_on_overwrite Boolean Sets alert for file overwrite
browse_action Open_save Specifies if the button in the file browser window
should be labelled "Open" or "Save".
word_wrap Boolean If set to "yes" text longer than the field width will wrap
onto the next line. By default the behavior is as if this
is set to "no" and therefore text longer than the field
width will remain on a single line and run beyond the
field border.
1. The field with specified name is created on the dialog box. If parameter ‘Enabled’ is set to ON, the
field is be preactivated.
3. The size of the field can be specified either in terms of number of pixels. Alternatively, the size can
also be stated as relative to the Adams window.
4. The vertical and horizontal resizing options are used to adjust the placement of the field menu on
will place the option menu on the top left corner of the dialog box. The location can also be specified
from the top left corner by adjusting the parameter ‘location.’
5. The size of the field window can be specified with respect to the Adams window size. The value for
height of the Adams View window. Therefore, a value of 1.0 will set the field window to be one half
6. The preload string is used to specify a predefined text to be displayed in the field. Thus a string ia
preloaded in to the dialog box initially.
7. The parameter ‘command’ specifies the name of the command to be executed while exiting the field.
8. If the contents of the field do not fit the field window, then the field can be added with horizontal
and vertical scrollbars making it ‘scrollable’. The contents of a field can be edited if the field is made
‘editable’ by choosing appropriate BOOLEAN value.
9. The execution of the associated command after exiting the window can be activated by setting the
BOOLEAN option to ‘yes’. The number of values allowed in the field can be set by stating an integer
value for the parameter ‘number_of_values’.
interface 63
interface field cut
will get not only the parts, but all children of the model, like joints, forces, and so on. Using the
Similarly, use of the NAME_FILTER will set the types of object allowed depending on the name of
the object.
11. The numeric type of the object that is, integer, real or entering the node_id is allowed, where a check
on the upper or lower limit of the numeric value can be set by choosing the upper and lower limits.
This limit will filter the value above and below the specified value depending the parameter
UPPER_CHECK and LOWER_CHECK.
12. The file type tobe read or written and its default directory can be chosen by specifying directory. if
the ‘FILTER’ value is above the specified maximum value, or below the specified minimum value, set
it to zero. For example: if the component is a discrete sampling of a sinusoidal wave with an amplitude
of one (1), and filter is requested with a maximum value of .9 (above_value=.9), All the values of the
corresponding to 'sin (x) > .9' will be set to 0.
interface field cut

Allows you to eliminate the contents of a field to paste elsewhere.A field is a space on a dialog box where a
data elements can be entered and displayed. The filed contents can be cut and pasted elsewhere by using this
command.
Format:
interface field cut
field_name = an existing GI_field
Example:
interface field cut &
Description:

field _name A New GI_field Specifies the name of a new field
1. The contents of a field can be cut and pasted elsewhere by using the ‘cut’ command to editing a
document.
interface field delete

Allows you to delete a field menu.
Format:
Example:
interface field delete &
Description:

1. Allows the deletion of the field with specified name
interface field display

Allows you to display a field on the dialog box.
Whenever required a field can be displayed using the command.
Format:
interface field display
Example:
interface field display &
interface 65
interface field execute
Description:

field _name An Existing GI_field Specifies the name of an existing field to be displayed
1. The field created can be displayed on appropriate dialog box by the ‘DISPLAY’ command.
Alternatively, it can be closed by the ‘UNDISPLAY’ command.

Allows you to execute a command associated with the field.
The command associated with the field can be executed explicitly by using this command.
Format:
Example:
interface field execute &
Description:

field _name An Existing GI_field Specifies the name of a new field
1. If any command is specified while creating a field, the command is executed while exiting the field.
Alternatively, the same command can be executed by running the execute command for any specific
filed name
interface field modify

Allows you to modify an already existing field.
The field properties can be modified by using this command.
Format:
field_name = An Existing GI_field
new_field_name = A New GI_field
enabled = Boolean
help_text = String
units = Int_units
location = Real
height = Real
width = Real
preload_strings = String
commands = String
scrollable = Boolean
editable = Boolean
required = Boolean
execute_cmds_on_exit = Boolean
number_of_values = Integer
string_type = Str_type
add_quotes = Add_quotes
object_type = New_old_any
type_filter = Ent
name_filter = String
numeric_type = Num_type
lower_check = Low_check
lower_limit = Real
upper_check = Upp_check
upper_limit = Real
file_type = New_old_any
directory = String
filter = String
alert_on_overwrite = Boolean
interface 67

browse_action = Open_save
word_wrap = Boolean
Example:
interface field modify &
field_name = .gui.naresh.flde &
new_field_name = .gui.naresh.flde1 &
enabled = Yes &
help_text = hlp_txt &
documentation_text = doc_txt &
units = relative &
horiz_resizing = attach_right &
location = 0.15,0.15 &
height = 0.4 &
width = 0.4 &
preload_string = new_predefined_txt_display &
scrollable = yes &
editable = yes &
required = yes &
execute_cmds_on_exit = no &
number_of_values = 1 &
string_type = literal &
add_quotes = yes
Description:

field _name An Existing GI_field Specifies the name of a new field
new_field_name A New GI_field Specifies a new name for an existing field
enabled Boolean Activates the field

units Int_units Specifies the field size as pixel or relative to Adams
window
filed
field
location Real Specifies the location of the field on the dialog box
height Real Specifies the height of the field in terms of relative
units or pixel
width Real Specifies the width of the field in terms of relative
units or pixel
preload strings String Specifies the initial text to be displayed
commands String Specifies the command to be executed after exiting
the field
scrollable Boolean Specifies the scroll bar option of the field
editable Boolean Allows editing the field contents
required Boolean Specifies whether field is required or optional
execute_cmds_on_exit Boolean Sets the BOOLEAN parameter for execution of
command after exiting field
number_of_values Integer Specifies the number of values allowed in the field
string_type add_quotes Add_quotes Specifies addition of quotes to the string
object_type New_old_any Specifies the object allowed in the field
name_filter String Specifies the name_filter for the object
numeric_type Num_type Specifies the type of numeric objects allowed
lower_check Low_check Specifies the applicability of lower check
lower_limit Real Specifies lower limit for lower check of numeric
value
upper_check Upp_check Specifies the applicability of upper check
upper_limit Real Specifies upper limit for upper check of numeric
value
file_type New_old_any Specifies the types of file allowed in the field
directory String Specifies the directory for the file
filter String Tests each value of the component
interface 69

alert_on_overwrite Boolean Sets alert for file overwrite
browse_action Open_save Specifies if the button in the file browser window
should be labelled "Open" or "Save".
word_wrap Boolean If set to "yes" text longer than the field width will
wrap onto the next line. By default the behavior is as
if this is set to "no" and therefore text longer than the
field width will remain on a single line and run
beyond the field border.
1. The field with specified name is created on the dialog box If parameter ‘Enabled’ is set to ON, the
field is be preactivated. If a new name is specified, the field will be renamed.
3. The size of the field can be specified either in terms of number of pixels. Alternatively, the size can
also be stated as relative to the Adams window.
4. The vertical and horizontal resizing options are used to adjust the placement of the field menu on
from the top left corner by adjusting the parameter ‘location’.
5. The size of the field window can be specified with respect to the Adams window size. The value for
height of the Adams View window. Therefore, a value of 1.0 will set the field window to be one half
6. The preload string is used to specify a predefined text to be displayed in the field. Thus a string ia
preloaded in to the dialog box initially.
7. The parameter ‘command’ specifies the name of the command to be executed while exiting the field
8. If the contents of the field do not fit the field window, then the field can be added with horizontal
and vertical scrollbars making it ‘scrollable’. The contents of a field can be edited if the field is made
‘editable’ by choosing appropriate BOOLEAN value.
9. The execution of the associated command after exiting the window can be activated by setting the
BOOLEAN option to ‘yes’. The number of values allowed in the field can be set by stating an integer
value for the parameter ‘number_of_values’.
will get not only the parts, but all children of the model, like joints, forces, and so on. Using the
Similarly, use of the NAME_FILTER will set the types of object allowed depending on the name of
the object.
interface field paste
11. The numeric type of the object that is, integer, real or entering the node_id is allowed, where a check
on the upper or lower limit of the numeric value can be set by choosing the upper and lower limits.
This limit will filter the value above and below the specified value depending the parameter
UPPER_CHECK and LOWER_CHECK.
12. The file type to be read or written and its default directory can be chosen by specifying directory. if
the ‘FILTER’ value is above the specified maximum value, or below the specified minimum value, set
it to zero. For example: if the component is a discrete sampling of a sinusoidal wave with an amplitude
of one (1), and filter is requested with a maximum value of .9 (above_value=.9), All the values of the
corresponding to 'sin (x) > .9' will be set to 0.

Allows you to paste a copied contents of a field to another field.
Format:
field_name = an exisitng GI_field
Example:
interface field paste &
Description:

field _name An Existing Specifies the name of an existing field where the contents are to be
GI_field pasted
1. The command allows pasting of the contents of a remote field to another field.
interface field read

Allows you to read/ execute the contents of a file to a field. A field is a space on a dialog box where a data
elements can be entered and displayed.
interface 71
interface field set
Format:
interface field read
field_name = an exisitng GI_field
file_name = string
Example:
interface field read &
file_name = “c:/spring_data.txt”
Description:

file_name String Specifies the file name to be read
1. Specifies the name of the file that is to be read, written, or executed. The proper extension is 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.
interface field set

Allows you to set the execution parameters and the editing the contents of a field. A field is a space on a dialog
box where a data elements can be entered and displayed.
The field properties can be set using the command
Format:
interface field set
field_name = An Exisitng GI_field
strings = String
database_fields = String
action = Field_action
execute = Boolean
interface field undisplay
Example:
interface field set &
field_name = .gui.naresh.fldst &
strings = append_text &
action = append &
execute = yes
Description:

strings String Specifies the strings to be added to the field
database_field String Specifies the database_filed to be added
action Field_action Specifies whether the new addition will replace or add to the
existing contents
execute Boolean Sets the execution of the command to ‘yes’ or ‘no’
 A string/ database field can be added, appended or inserted to the existing contents of a field
depending upon the parameter ‘action’. The command, if specified, associated with the particular
dialog box is executed depending on the BOOLEAN parameter ‘yes’ or ‘no’.
Tips:
 The parameters ‘strings’ and ‘database fields’ are mutually exclusive to each other.

Allows closing of an displayed field on the dialog box
It may not be necessary to display the field always and hence it can be closed by the command.
Format:
interface 73
interface field write
Example:
interface field undisplay &
Description:

field _name An Existing GI_field Specifies the name of an displayed field
1. The displayed field can be closed by choosing the field name and running the command ‘undisplay’.
It can be displayed again by the command ‘display’ specifying the field name.

Allows writing the contents of a field to a file
A field is a space on a dialog box where a data elements can be entered and displayed. The contents of a field
can be directly written to a file like excel workbook or a tab delimited .txt file.
Format:
file_name = string
Example:
interface field write &
file_name = c:/write_backup.txt
Description:

field _name An Existing GI_field Specifies the name of an existing field to be displayed
file_name String Specify here a new or existing file name to be written or
overwritten
interface grid copy
1. The contents of the field can be written to a new or existing file by ‘write’ command. If an existing
file name is suggested then the file will be overwritten after a prompt warning. The new file can be
specified with extension like .txt or .doc. If no extension is specified then the file will be created with
an extension .tab. 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.
interface grid copy

Allows you to copy an existing grid.
A new grid can be created independent of the default grid, which can be located or oriented as per the
preference. The grid oriGIn can be conveniently located at any location other than the global oriGIn.
The grid can be copied and displayed in a new view. The grid is copied by this command.
Format:
interface grid copy
grid_name = an existing grid
new_grid_name = a new grid
Example:
interface grid copy &
grid_name = .model_1.grd &
new_grid_name = grd4
Description:

grid_name An Existing Grid Specifies the name of an existing grid
new_grid_name A New Grid Specifies a new name for the copied grid
1. The grid can be copied and displayed in a new view. This reduces the task of repeating the grid
creation for a new view.
Cautions:
The grid settings should not exceed the maximum number of points as specified by the environment variable
'MDI_MAX_GRID_POINTS'. The default maximum is 10000 points.
interface 75
interface grid create

Allows you to create a new grid in an existing view.
preference. The grid origin can be conveniently located at any location other than the global origin.
The grid size, mesh, appearance and snapping ability can be decided by this command.
Format:
grid_name = a new grid
location = location
snapping_enabled = boolean
view_normal = boolean
extent = length
spacing = length
maximum_radius = length
circle_spacing = length
radial_increments = integer
triad_visible = boolean
lines_visible = boolean
line_weight = integer
line_style = line_style
line_color = an existing color
dots_visible = boolean
dot_size = integer
dot_color = an existing color
axes_visible = boolean
axis_weight = integer
Example:
interface grid create &
location = .model_1 &
interface grid create &

orientation = .model_1 &
snapping_enabled = yes &
view_normal = yes &
extent = 1000,1000 &
spacing = 100,100 &
triad_visible = yes &
lines_visible = yes &
line_weight = 2 &
line_style = solid &
line_color = .colors.RED &
dots_visible = yes &
dot_size = 3 &
dot_color = .colors.BLUE &
axes_visible = yes &
axis_weight = 3 &
axis_color = .colors.GREEN
Description:

grid_name A New Grid Specifies the name for a new grid
location Location Specifies the location of the grid oriGIn
orientation Orientation Specifies the orientation of the grid
snapping_enabled Boolean Specifies the ability to snap to grid points
view_normal Boolean Keeps the grid always normal to the viewer irrespective of
actual orientation
extent Length Specifies the extent of the grid in two axial directions in model
units
spacing Length Specifies the spacing of the grid points
maximum_radius Length Specifies the maximum radius of the polar grid
circle_spacing Length Specifies the circular spacing of the polar grid
radial_increments Integer Specifies the radial increments in case of polar grid
triad_visible Boolean Specifies the visibility of triad
lines_visible Boolean Specifies the visibility of grid lines
line_weight Integer Specifies the line weight
interface 77

line_style Line_style Specifies the line style for the grid line
line_color An Existing Color Specifies the grid line color
dots_visible Boolean Specifies the visibility of the grid dots
dot_size Integer Specifies the size of the grid dots
dot_color An Existing Color Specifies the grid dot color
axes_visible Boolean Specifies the visibility of the axes
axis_weight Integer Specifies the axes line weight
axis_color An Existing Color Specifies the axis line color
1. The new working grid can be defined with the name ‘grid_name’. The location can be at global origin
or any other location which can be entered as coordinates of ‘picked-up’ from the view window.
Either you can keep the global origin, that is, 0,0,0, to set the center location of the grid to the center
of the view window or pick or click a location on the screen to set as the center of the working grid.
2. By orientation, select how you want to orient the grid. You can set its orientation by picking points
or by aligning it with the screen plane. Note that if you select Pick for orientation, you will also set
the location of the working grid. This orients the grid axes to the global axes.
3. By enabling the ‘snapping’, you can snap a closest grid point with the cursor. When you drag an item
with the mouse to move or resize it, the mouse position will snap to the nearest grid point.
4. The parameter ‘view normal’ always orients the grid normal to the viewer irrespective of the actual
orientation of the grid. Thus, if the grid is oriented at angle, as you change the orientation of the
object view, the grid realigns itself normal to the viewer. But if the parameter is not enabled, then the
grid will remain oriented in space as per the specified orientation.
5. The extents specifies the length of the grid in x,y directions in the model length units. The spacing
specifies the distance between the grid points in x and y directions in models length units.
6. Maximum radius specifies the radius of the outermost grid circle from the grid oriGIn and
circle_spacing specifies amount of space between each circle in the working grid. The smaller the
spacing, the more circles Adams View defines.
For radial increments, enter the number of lines radiating from the origin of the working grid. Adams
View spaces the lines equally around the working grid. The lines do not include the axes. The number
of lines (N) determines the angle increment between lines (q), as shown in the formula:
θ = 360×/N
7. You can hide the new grid triad or display it by the parameter ‘triad_visible’. The visibility of lines
and axes on the grid can be switched ON or OFF by the parameter ‘lines_visible’ and ‘axes_visible’.
The line and axes weight can be set by using the ‘line_weight’ and ‘axes_weight’ parameters. The value
range for this weight is 1 to 5. The color of the lines and axes is set by using the ‘axes_color’ and
‘line_color’ parameter. The line style can be chosen form various line style options like solid, dash and
so on.
interface grid delete
8. The dot properties like size, color and visibility are set by using the parameters ‘dot_size’, ‘dot_color’
and ‘dot_visible’ parameter. The dot_size range is from 1 to 3 screen pixel.
Cautions:

Allows you to delete an existing grid in the view.
The grid created can be deleted by this command.
Format:
Example:
interface grid delete &
grid_name = grd4
Description:

view_name An Existing View Specifies view_name of displayed grid
1. The existing grid can be deleted by this command.
Tips:
The grid may not be deleted if any views or objects are dependent on it. You must first delete the dependent
objects.
Cautions:
interface 79
interface grid display

Allows you to display an existing grid in the view.
preference. The grid origin can be conveniently located at any location other than the global origin.
The grid created can be displayed by this command.
Format:
Example:
interface grid display &
grid_name = .model_1.grd5 &
view_name = front
Description:

1. The existing grid can be displayed by this command.
Cautions:
interface grid modify

Allows you to modify an existing grid in the view.
The grid size, mesh, appearance and snapping ability can be modified by this command.
Format:
new_grid_name = a new grid
location = location
snapping_enabled = boolean
view_normal = boolean
extent = length
spacing = length
maximum_radius = length
circle_spacing = length
radial_increments = integer
triad_visible = boolean
lines_visible = boolean
line_weight = integer
line_style = line_style
line_color = an existing color
dots_visible = boolean
dot_size = integer
dot_color = an existing color
axes_visible = boolean
axis_weight = integer
Example:
interface grid modify &
new_grid_name = .model_1.grd2 &
location = .model_1 &
orientation = .model_1 &
snapping_enabled = yes &
view_normal = yes &
extent = 1000,1000 &
spacing = 100,100 &
interface 81
interface grid modify &

triad_visible = yes &
lines_visible = yes &
line_weight = 2 &
line_style = solid &
line_color = .colors.RED &
dots_visible = yes &
dot_size = 3 &
dot_color = .colors.BLUE &
axes_visible = yes &
axis_weight = 3 &
axis_color = .colors.GREEN
Description:

new_grid_name A New Grid Specifies a new name for an existing grid
location Location Specifies the location of the grid oriGIn
orientation Orientation Specifies the orientation of the grid
snapping_enabled Boolean Specifies the ability to snap to grid points
view_normal Boolean Keeps the grid always normal to the viewer
irrespective of actual orientation
extent Length Specifies the extent of the grid in two axial
directions in model units
spacing Length Specifies the spacing of the grid points
maximum_radius Length Specifies the maximum radius of the polar grid
circle_spacing Length Specifies the circular spacing of the polar grid
radial_increments Integer Specifies the radial increments in case of polar
grid
triad_visible Boolean Specifies the visibility of triad
lines_visible Boolean Specifies the visibility of grid lines
line_weight Integer Specifies the line weight
line_style Line_style Specifies the line style for the grid line
line_color An Existing Color Specifies the grid line color
dots_visible Boolean Specifies the visibility of the grid dots

dot_size Integer Specifies the size of the grid dots
dot_color An Existing Color Specifies the grid dot color
axes_visible Boolean Specifies the visibility of the axes
axis_weight Integer Specifies the axes line weight
axis_color An Existing Color Specifies the axis line color
1. The new working grid can be defined with the name ‘grid_name’. The location can be at global
oriGIn or any other location which can be entered as coordinates of ‘picked-up’ from the view
window. Either you can keep the Global OriGIn, that is, 0,0,0, to set the center location of the grid
to the center of the view window or pick or click a location on the screen to set as the center of the
working grid.
The ‘new_grid_name’ replaces the name of the existing grid.
2. By orientation, select how you want to orient the grid. You can set its orientation by picking points
or by aligning it with the screen plane. Note that if you select Pick for orientation, you will also set
the location of the working grid. This orients the grid axes to the global axes.
3. By enabling the ‘snapping’, you can snap a closest grid point with the cursor. When you drag an item
with the mouse to move or resize it, the mouse position will snap to the nearest grid point.
4. The parameter ‘view normal’ always orients the grid normal to the viewer irrespective of the actual
orientation of the grid. Thus, if the grid is oriented at angle, as you change the orientation of the
object view, the grid realigns itself normal to the viewer. But if the parameter is not enabled, then the
grid will remain oriented in space as per the specified orientation.
5. The extents specifies the length of the grid in x,y directions in the model length units. The spacing
specifies the distance between the grid points in x and y directions in models length units.
6. Maximum radius specifies the radius of the outermost grid circle from the grid oriGIn and
circle_spacing specifies amount of space between each circle in the working grid. The smaller the
spacing, the more circles Adams View defines.
For radial increments, enter the number of lines radiating from the origin of the working grid. Adams
View spaces the lines equally around the working grid. The lines do not include the axes. The number
of lines (N) determines the angle increment between lines (q), as shown in the formula:
θ = 360×/N
7. You can hide the new grid triad or display it by the parameter ‘triad_visible’. The visibility of lines
and axes on the grid can be switched ON or OFF by the parameter ‘lines_visible’ and ‘axes_visible’.
The line and axes weight can be set by using the ‘line_weight’ and ‘axes_weight’ parameters. The value
range for this weight is 1 to 5. The color of the lines and axes is set by using the ‘axes_color’ and
‘line_color’ parameter. The line style can be chosen form various line style options like solid, dash and
so on.
interface 83
interface grid undisplay
8. The dot properties like size, color and visibility are set by using the parameters ‘dot_size’, ‘dot_color’
and ‘dot_visible’ parameter. The dot_size range is from 1 to 3 screen pixel.
Cautions:

Allows you to close an existing grid in the view.
The grid can be closed by this command.
Format:
Example:
interface grid undisplay &
grid_name = .model_1.grd5 &
view_name = front
Description:

1. The existing grid can be closed by this command.
Cautions:
interface label create

Allows creation of a new label on the dialog box.
Specifies a label for an axis which will be displayed near the axis, its placement depending on where the axis
is placed. The label can be of unlimited length, but may not all fit on the plot if it's very long. If the string
contains spaces, it must be enclosed in quotation marks.
Format:
label_name = a new GI_label
location = real
height = real
width = real
enabled = boolean
help_text = string
units = int_units
text = string
icon_file = string
justified = justified
Example:
interface label create &
label_name = .gui.dbox.lbl &
location = 0.0, 0.0 &
height = 0.8 &
width = 0.8 &
enabled = yes &
documentation_text = "doc2text" &
units = relative &
interface 85
interface label create &

text = "this_is_label" &
justified = center
Description:

label _name A New GI_label Specifies the name of a new label
enabled Boolean Activates the label
units Int_units Specifies the label size as pixel or relative to dialog box window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for the label
vert_resizing Int_v_resize Specifies the attachment and scaling option for the label
location Real Specifies the location of the label on the dialog box
height Real Specifies the height of the label in terms of relative units or pixel
width Real Specifies the width of the label field in terms of relative units or
pixel
icon_file String Specifies the address of the image to be displayed for iconic label
text String Specifies the text to be displayed on the label
justified Justified Specifies the text justification on the window
1. The preliminary parameters of the label like size and text to be displayed are set using this command.
3. The size of the label can be specified either in terms of number of pixels. Alternatively, the size can
also be stated as relative to the dialog box window
4. The vertical and horizontal resizing options are used to adjust the placement of the label menu on
will place the label on the top left corner of the dialog box. The location can also be specified from
5. The size of the label window can be specified with respect to the dialog box window size. The value
the height of the dialog window. Therefore, a value of 1.0 will set the label field window to be one
interface label delete
6. The ‘text’ specifies the text string(s) that will comprise the note text. You may enter the text string(s)
for this parameter without double quote marks, if the string contains no "blanks" or special characters
such as *&^%$#@!-/><. If the text string(s) do have any of these special characters the string must be
quoted. To enter a multiline note, each line must be entered as a separate string, separated by a
comma. An Example: note create note=.front.n1 screen_coords=0,0 & TEXT="This is a","multi line
note" size = .12
This example command would produce a two line note located at the center of the view named
'front', and at a height of .12 units.
7. By default ‘label’ is left justified, but it can be adjusted center or right by parameter ‘JUSTIFIED’
8. The parameter ‘iconic_file’ specifies the name of the file that contains the icon definition for use on
an iconic menu.

Allows deletion of a existing label on the dialog box.
Specification of a label for an axis is displayed near the axis, its placement depending on where the axis is
placed. The label can be of unlimited length, but may not all fit on the plot if it's very long. If the string
Format:
label_name = an existing GI_label
Example:
interface label delete &
label_name = .gui.dobx.lbl
Description:

label _name An Existing GI_label Specifies the name of an existing label
The label can be deleted by choosing the appropriate ‘label_name’ while the ‘delete’ command.
interface label display

Allows displaying the existing label on the dialog box.
interface 87
interface label modify
Format:
interface label display
Example:
interface label display &
Description:

The label can be displayed or closed using the ‘display’ and ‘undisplay’ commands respectively as the need
arises.

Allows modification of an existing label on the dialog box.
Format:
new_label_name = a new GI_lable
location = real
height = real
width = real
enabled = boolean
help_text = string

units = int_units
text = string
icon_file = string
justified = justified
Example:
interface label modify &
new_label_name = .gui.dbox.lbl &
location = 0.0, 0.0 &
height = 0.8 &
width = 0.8 &
enabled = yes &
units = relative &
text = "this_is_label" &
justified = center
Description:

new_label_name A New GI_label Specifies a new name for an existing label
enabled Boolean Activates the label
units Int_units Specifies the label size as pixel or relative to dialog box
window
interface 89

label
label
location Real Specifies the location of the label on the dialog box
height Real Specifies the height of the label in terms of relative
units or pixel
width Real Specifies the width of the label field in terms of
icon_file String Specifies the address of the image to be displayed for
iconic label
text String Specifies the text to be displayed on the label
justified Justified Specifies the text justification on the window
1. The preliminary parameters of the label like size and text to be displayed are set using this command.
The name of the label can also be change by adding parameter ‘new_label_name’.
3. The size of the label can be specified either in terms of number of pixels. Alternatively, the size can
4. The vertical and horizontal resizing options are used to adjust the placement of the label menu on
will place the label on the top left corner of the dialog box. The location can also be specified from
5. The size of the label window can be specified with respect to the dialog box window size. The value
the height of the dialog window. Therefore, a value of 1.0 will set the label field window to be one
6. The ‘text’ specifies the text string(s) that will comprise the note text. You may enter the text string(s)
for this parameter without double quote marks, if the string contains no "blanks" or special characters
such as *&^%$#@!-/><. If the text string(s) do have any of these special characters the string must be
quoted. To enter a multiline note, each line must be entered as a separate string, separated by a
comma. An Example: note create note=.front.n1 screen_coords=0,0 & TEXT="This is a","multi line
note" size = .12
7. By default ‘label’ is left justified, but it can be adjusted center or right by parameter ‘JUSTIFIED’
interface label set
8. The parameter ‘iconic_file’ specifies the name of the file that contains the icon definition for use on
an iconic menu.
interface label set

Allows setting-up of initial appearance parameters for the existing label on the dialog box.
Format:
interface label set
rgb_color = real
Example:
interface label set &
rgb_color = 0.3,0.4,0.1
Description:

color An Existing Color Specifies the color of the label
rgb_color Real Specifies the color of the label as real numbers
1. The label appearance can be changed by choosing label color as either available colors or entering the
color code as real numbers, that is, rgb_color.
The ‘color’ specifies the COLOR of a graphic object. A graphic object is an object that may be drawn
on the screen by Adams View, these include curves, parts, markers, arcs, outlines, boxes, circles,
cylinders, frustums, spring damper graphics, force graphics, and plot curves and symbols. When the
COLOR of a part is specified, all graphic objects fixed to that part are drawn with the COLOR of the
part. Adams View supports the following COLOR: black, white, red, green, blue, cyan, magenta, and
yellow.
interface 91
interface label undisplay
Note: If you choose the COLOR of an entity to be drawn in the view background color (typically
white or black...) it may not show up. See help for hardcopy also.
2. The RGB_COLOR is specified as reals ranGIng from 0,0,0 to 1,1,1

Allows closing the existing label on the dialog box.
Format:
Example:
interface label undisplay &
Description:

The label can be displayed or closed using the ‘display’ and ‘undisplay’ commands respectively as the need
arises.
interface menu create

Allows you to create a new row for a new or existing menu.
The ‘interface menu’ allows you to create, manage, and display menus. Adams view displays menus below the
Command Line. You may enter Adams view commands by picking on menus, and filling out the resulting
panels. If you have menus loaded and displayed, you have your choice between typing commands in the
Command Line, and picking through the menus. If you are unfamiliar with a command, you will probably
find the menus easier to use. If you know exactly which command to enter, you may find it quicker to type
it directly.
Adams view menus are data base objects. You create, modify, and delete them as you would any other objects
in Adams view. With your Adams view distribution, you received a predefined set of menus and panels that
closely match the Adams view command structure. You may use them as they are, or modify them to suit
your own needs and tastes.
The main menu is named '.gui.root'. The names of other menus are derived from the keywords they
represent. The fixed menu, at the bottom of the display, is a special menu named '.gui.fixed_menu'. You may
add, modify, or delete items from the fixed menu, but you may not delete the menu itself. To get the name
of any particular menu, type on the command line (while the desired menu is displayed): "list_info pick
<CR>". Then pick the desired menu and then it's full definition, including the name, will be displayed in
the information window.
Menus work very simply. Each menu item has a command string associated with it. When you select an item
by picking on it, Adams view executes the command associated with the item. Many times, this command
will display a new menu next to the current one, allowing you to work your way down the command
structure. The final menu item will display the panel associated with the command you are entering, if it has
parameters, or issue the command immediately, if it has no parameters.
This command is used to create a menu on the menubar.
Format:
menu_name = a new GI_menu
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
label = string
Example:
interface menu create &
menu_name = .gui.win.mnbr1.zoom &
enabled = yes &
interface 93
interface menu create &

units = relative &
location = 0.0, 0.0 &
height = 0.3 &
width = 0.3 &
label = "zoom control"
Description:

menu_name A New GI_menu Specifies the name for a new menu
enabled Boolean Activates the menu
units Int_units Specifies the menu size as pixel or relative to Adams window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for the menu
vert_resizing Int_v_resize Specifies the attachment and scaling option for the menu
location Real Specifies the location of the menu on the window
height Real Specifies the height of the menu in terms of relative units or
pixel
width Real Specifies the width of the window field in terms of relative units
or pixel
label String Specifies the label to appear on menubar
1. The ‘menu_name’ specifies the name of an existing menu which you want to modify. You identify a
menu by typing its name. If a menu is available by default, you may identify it by entering its name
only. If it is not, you must enter its full name. To identify a menu under a different library, for
instance, you may need to enter the library name as well. For example, you may specify menu 'menu1'
from library 'gui', by entering ".gui.menu1". If you type a "?", Adams View will list the menus
2. A menubar contains various menus. Each of these menus may be associated with different commands.
The menus on this menubar can be created by this command, adding commands to the menus is done
by ‘interface menubar build’ command. The menubar can be displayed on the main_window,
popup_window, ppt_main_window, or a user defined custom window.
interface menu delete
3. The menu is enabled by the parameter ‘enabled’. The popup_help_text and documentation is
specified. The size of the menu can be specified either in terms of number of pixels. Alternatively, the
size can also be stated as relative to the Adams window. The vertical and horizontal resizing options
are used to adjust the placement of the menu on existing window. For example, attach_left;
attach_top options for Horiz_resizing and Vert_resizing will place the window on the top left corner
of the window. The location can also be specified from the top left corner by adjusting the parameter
‘location’
4. The ‘label’ will appear on menu created on the menubar.

Allows you to delete an existing menu on the menubar.
The ‘interface menu’ allows you to create, manage, and display menus. Adams View displays menus below
the Command Line. You may enter Adams View commands by picking on menus, and filling out the
resulting panels. If you have menus loaded and displayed, you have your choice between typing commands
in the Command Line, and picking through the menus. If you are unfamiliar with a command, you will
probably find the menus easier to use. If you know exactly which command to enter, you may find it quicker
to type it directly.
Adams View menus are data base objects. You create, modify, and delete them as you would any other objects
in Adams View. With your Adams View distribution, you received a predefined set of menus and panels that
closely match the Adams View command structure. You may use them as they are, or modify them to suit
by picking on it, Adams View executes the command associated with the item. Many times, this command
This command is used to delete an existing menu on the menubar.
Format:
menu_name = an exisitng GI_menu
interface 95
interface menu display
Example:
interface menu delete &
menu_name = zoom
Description:

menu_name An Exisitng GI_menu Specifies the of an existing menu
1. An existing menu can be deleted from the menubar by using this command.
2. All the menus need not be displayed every time. The menus can be selectively displayed and close by
using the ‘interface menu display’ and ‘interface menu undisplay’ commands respectively by
specifying the ‘menu_name’.

Allows you to display an existing menu on the menubar.
The ‘interface menu’ allows you to create, manage, and display menus. Adams View displays menus below
the Command Line. You may enter Adams View commands by picking on menus, and filling out the
resulting panels. If you have menus loaded and displayed, you have your choice between typing commands
in the Command Line, and picking through the menus. If you are unfamiliar with a command, you will
probably find the menus easier to use. If you know exactly which command to enter, you may find it quicker
to type it directly.
closely match the Adams View command structure. You may use them as they are, or modify them to suit
by picking on it, Adams View executes the command associated with the item.Many times, this command
This command is used to display an existing menu on the menubar.
interface menu modify
Format:
Example:
interface menu display &
menu_name = zoom
Description:

1. All the menus need not be displayed everytime. The menus can be selectively displayed and close by

Allows you to modify an existing row for an existing menu.
Command Line. You may enter Adams View commands by picking on menus, and filling out the resulting
it directly.
interface 97
This command is used to modify a menu on the menubar.
Format:
menu_name = An Existing GI_menu
new_menu_name = A New GI_menu
enabled = Boolean
help_text = String
units = Int_units
location = Real
height = Real
width = Real
label = String
Example:
interface menu modify &
menu_name = .gui.win.mnbr1.zoom &
new_menu_name = .gui.win.mnbr1.zoom1 &
enabled = yes &
units = relative &
location = 0.0, 0.0 &
height = 0.3 &
width = 0.3 &
label = "zoom control"
Description:

menu_name An Existing GI_menu Specifies the name of an existing menu
new_menu_name A New GI_menu Specifies a new name for the existing menu
enabled Boolean Activates the menu
units Int_units Specifies the menu size as pixel or relative to Adams
window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for the menu
vert_resizing Int_v_resize Specifies the attachment and scaling option for the menu
location Real Specifies the location of the menu on the window
height Real Specifies the height of the menu in terms of relative units
or pixel
width Real Specifies the width of the window field in terms of relative
units or pixel
label String Specifies the label to appear on menubar
1. The ‘menu_name’ specifies the name of an existing menu which you want to modify. You identify a
menu by typing its name. If a menu is available by default, you may identify it by entering its name
only. If it is not, you must enter its full name. To identify a menu under a different library, for
instance, you may need to enter the library name as well. For example, you may specify menu 'menu1'
from library 'gui', by entering ".gui.menu1". If you type a "?", Adams View will list the menus
The menus on this menubar can be created by this command, adding commands to the menus is done
3. The ‘new_menu_name’ will specify a new name for a menu. The new name must be unique, since
you are not allowed to have two menus with the same name.
4. The menu is enabled by the parameter ‘enabled’. The popup_help_text and documentation is
specified. The size of the menu can be specified either in terms of number of pixels. Alternatively, the
size can also be stated as relative to the Adams window. The vertical and horizontal resizing options
are used to adjust the placement of the menu on existing window. For example, attach_left;
attach_top options for Horiz_resizing and Vert_resizing will place the window on the top left corner
of the window. The location can also be specified from the top left corner by adjusting the parameter
‘location’
interface 99
interface menu read
5. The ‘label’ will appear on menu created on the menubar.
interface menu read

Allows you to add commands to existing menus.
it directly.
in Adams view. With your Adams View distribution, you received a predefined set of menus and panels that
by picking on it, Adams View executes the command associated with the item. Many times, this command
This command is used to add command to a menu on the menubar.
Format:
interface menu read
file_name = string
Example:
interface menu read &
menu_name = .gui.win.mnbr1.zoom.vwc_pop_up &
file_name = "D:/naresh/20 sept/z1.mnu"
interface menu undisplay
Description:

file_name String Specifies the name of a *.mnu file from which the commands
are to be read
field_name An Exisitng GI_field Specifies the existing interface field name
1. The commands can be added to a menu by the ‘interface menu read’ command. The command can
be added by reading a .mnu file already created or accessing an existing field.
2. The .mnu consists of a commands which can be written by ‘interface menu write’ and accessed by
‘interface menu read’.
for example, the zoom operation will need the following command set which is written to a .menu file
-----------------------------
NAME=vwc_pop_up
BUTTON2 Zoom In/Out <z>
HELP=Dynamically zoom the view
CMD=interface mode repeat=push mode=dyn_view_zoom
---------------------------
The above mentioned contents from a .mnu file can be read by this command, which will display the menu
zoom-in and zoom-out buttons against the already created zoom-menu.

Allows you to close an existing menu on the menubar.
it directly.
Adams View menus are data base objects. You create, modify, and delete them as you would any other objects
interface 101
interface menu write
This command is used to close an existing menu on the menubar.
Format:
Example:
interface menu undisplay &
menu_name = zoom
Description:

1. All the menus need not be displayed everytime. The menus can be selectively displayed and close by

Allows you to write the commands associated with a menu to a file.
it directly.
This command is used to write the commands associated with a menu to a file.
Format:
menu_name = An Exisitng GI_menu
file_name = String
field_name = An Existing GI_field
Example:
interface menu write &
menu_name = .gui.win.mnbr1.zoom.vwc_pop_up &
file_name = "D:/naresh/20 sept/z1.mnu"
Description:

file_name String Specifies the name of a *.mnu file to which the commands
are to be written
field_name An Exisitng GI_field Specifies the existing interface field name
1. The commands associated with a menu can be written to a .mnu file by ‘interface menu write’
command. This file can further be accessed to build another menu. Also an existing interface field can
be written by using ‘interface menu write’ command.
interface 103
interface menubar build
2. The .mnu consists of a commands which can be written by ‘interface menu write’.
for example, the zoom operation tab on the menu has the following commands set which is written
to a .mnu file
--------------------
NAME=vwc_pop_up
---------------------------
The above mentioned contents from a .mnu file can be read by ‘interface menu read’ command, which will
display the menu zoom-in and zoom-out buttons against the already created zoom-menu.

Allows you to build an existing menubar to add button and commands to it.
The menubar can be created on main_window, popup_window, ppt_main_window, or a user defined
custom window.
This menubar is built up by adding menus, which are associated with Adams commands.
Format:
menubar_name = An Existing GI_menubar
Example:
interface menubar build &
menubar_name = mnbr1
Description:

menubar_name An Existing GI_menubar Specifies the name of an existing menubar
1. The command ‘interface menubar build’ will ask for the ‘menubar name’. Enter the name of an
existing menubar created by ‘create’ command.
interface menubar create
2. A ‘menubar builder’ will open up. It will have two object tabs namely, 1) Menu bar and 2) Edit. The
‘Edit’ tab can be used to edit the text contents of the menubar window. The ‘Menu bar’ tab has
various command options namely, 1) Load, 2) Apply, 3) Reload, 4) Import text, 5) Export text and
6) Exit.
3. Add the commands to the text window of the Menu-bar, and click ‘Load’ tab which will open a
database navigator to prompt for a GUI where the menubar should be loaded. Select the proper GUI
to load the menubar. If you do any further changes to the text in menubar-text-window, click reload
to update the changes. Lastly, click ‘Apply’ to display the menubar on GUI.
As an Example, to create a zoom menu on menubar write the following into the menubar-text-
window
MENU1= zoom control
NAME=vwc_pop_up__1
-------------------------------------------------------
After writing the text into menubar-text-window, select ‘Load’ from the main menu. It will prompt
the GUI namely, 1) main_window, 2) popup_window, 3) ppt_main_window, and 4) user defined
custom window (if already created).
Select the option 4, to display the menubar on a user defined custom window. It will display the zoom
tab on the menubar on the custom window.
By clicking this tab to perform zooming on the Adams View window.

Allows you to create a new menubar.
custom window. The menubar can further be built up by adding menus, which are associated with Adams
commands.
This command is used to create a menubar which is then used to add menus for execution of various
commands. For adding the menus and activating the menubar refer to ‘menubar_build’.
Format:
menubar_name = a new GI_menubar
enabled = boolean
help_text = string
units = int_units
interface 105

Example:
interface menubar create &
menubar_name = .gui.win.mbar &
enabled = yes &
units = relative &
Description:

menubar_name A New GI_menubar Specifies the name for a new menubar
enabled Boolean Activates the menubar
units Int_units Specifies the menubar size as pixel or relative to Adams
window
menubar
menubar
Such a menubar can be created by this command. adding menus and commands to the buttons is
done by ‘interface menubar build’ command. The menubar can be displayed on the main_window,
2. The menubar is enabled by the parameter ‘enabled’. The popup_help_text and documentation is
specified. The size of the menubar can be specified either in terms of number of pixels. Alternatively,
the size can also be stated as relative to the Adams window.
interface menubar delete
3. The vertical and horizontal resizing options are used to adjust the placement of the menu on existing
window. For example, attach_left; attach_top options for Horiz_resizing and Vert_resizing will place
the menu on the top left corner of the window box. The location can also be specified from the top
left corner by adjusting the parameter ‘location’

Allows you to delete of an existing menubar.
custom window. The menubar can further be built up by adding buttons, which are associated with Adams
commands.
This command is used to delete an existing menubar.
Format:
menubar_name = an existing GI_menubar
Example:
interface menubar delete &
Description:

1. The existing menubar can be deleted by using this command.
interface menubar display

Allows you to display an existing menubar.
commands.
This command is used to display an existing menubar.
interface 107
interface menubar modify
Format:
interface menubar display
Example:
interface menubar display &
Description:

1. The existing menubar can be displayed or closed as per the requirement of command menus on the
menubar, by the command ‘interface menubar display’ and ‘interface menubar undisplay’
respectively.

Allows you to modify an existing menubar.
commands.
This command is used to modify a menubar which may be further used to add menus for execution of various
commands. For adding the menus and activating the menubar refer to ‘menubar_build’.
Format:
new_menubar_name = a new GI_menubar
enabled = boolean
help_text = string
units = int_units
Example:
interface menubar modify &
menubar_name = .gui.win.mnbr &
new_menubar_name = mnbr1 &
enabled = yes &
units = relative &
Description:

new_menubar_name A New GI_menubar Specifies a new name for an existing menubar
enabled Boolean Activates the menubar
units Int_units Specifies the menubar size as pixel or relative to
Adams window
menubar
menubar
1. The ‘new_menubar_name’ will replace the existing menubar with the new name.
Such a menubar can be created by this command. adding menus and commands to the menus is done
interface 109
interface menubar read
3. The menubar is enabled by the parameter ‘enabled’. The popup_help_text and documentation is
specified. The size of the menubar can be specified either in terms of number of pixels. Alternatively,
the size can also be stated as relative to the Adams window. The vertical and horizontal resizing
options are used to adjust the placement of the menubar on existing window. For example,
attach_left; attach_top options for Horiz_resizing and Vert_resizing will place the menu on the top
left corner of the window box. The location can also be specified from the top left corner by adjusting
the parameter ‘location’

Allows you to read the menubar building commands from a file.
custom window.
This menubar is built up by adding menus, which are associated with Adams commands. Those commands
can be written to a file with .mnu extension.
This file can be read to build a new menubar by using this command. Or else, a field can be written to and
read back by using this command.
Format:
file_name = string
Example:
interface menubar read &
menubar_name = .gui.win.mnbr1 &
file_name = "C:/menubar_data.mnu"
Description:

file_name String Specifies a remote file name from where the menubar
commands are to be read
1. The menubar commands data for any menubar are written to a file with extension .mnu. This file can
be accessed while using the ‘menubar read’ command to create a new menubar with same commands.
interface menubar undisplay
2. Alternatively, the same file can be written by using the ‘import text’ tab from the ‘menubar builder’.
As an Example, to create a zoom menu on menubar, following text appears in the menubar-text-
window.
------------------------------------------------------
MENU1 zoom control
NAME=vwc_pop_up__1
-------------------------------------------------------
which can be read from of a file with extension .mnu writtenm previously. This file can be read
directly to create similar menubar on a window.
3. Similarly, a individual ‘field’ previously written can be accessed by selecting the parameter
‘field_name’, which will read data related to a field.

Allows you to close an existing menubar.
commands.
This command is used to close an existing menubar.
Format:
Example:
interface menubar undisplay &
Description:

1. The existing menubar can be displayed or closed as per the requirement of command menus on the
menubar, by the command ‘interface menubar display’ and ‘interface menubar undisplay’
respectively.
interface 111
interface menubar write

Allows you to write the menubar building commands to a file
custom window.
This menubar is built up by adding menus, which are associated with Adams commands. Those commands
can be written to a file with .mnu extension. This file can be further read to build a new menubar.
Format:
file_name = string
Example:
interface menubar write &
menubar_name = .gui.win.mnbr1 &
file_name = "C:/menubar_data.mnu"
Description:

file_name String Specifies a remote file name where the menubar
commands are to be written
1. The menubar commands data for any menubar can be written to a file with extension .mnu. This file
can be accessed while using the ‘menubar read’ command to create a new menubar with same
commands.
2. Alternatively, the same file can be written by using the ‘export text’ tab from the ‘menubar builder’
As an Example, to create a zoom menu on menubar, following text appears in the menubar-text-
window
MENU1 zoom control
NAME=vwc_pop_up__1
which can be written in the form of a file with extension .mnu. This file can be read directly to create
similar menubar on a window.
interface message
interface message
Allows the setting the mode of display in plot panel in the plot window
Allows you to set the messages displayed in the message window and clear the messages from the window. By
default, the message window only displays error and fatal messages and messages from commands that you
execute from the user interface (for example, menus and dialog boxes). You can also display messages that you
execute from the Command Window, Command Navigator, and command files. In addition, you can set the
severity level of the messages displayed, from informational to fatal messages.
Format:
interface message
graphic_window_level = msg_gui_level
command_window_level = msg_gui_level
start_up_level = msg_gui_level
threshold_severity = severity
message = string
enabled = boolean
Example:
interface message &
graphic_window_level = brief &
command_window_level = brief &
startup_level = brief
Description:

graphic_window_level Msg_gui_level Specifies the message type displayed for graphic
window event
command_window_level Msg_gui_level Specifies the message type displayed for command
window event
start_up_level Msg_gui_level Specifies the message type displayed for start up
threshold_severity Severity Specifies the threshold limit above which a message
is displayed
message String Specifies the message dtring to be displayed
enabled Boolean Enables the message setting
interface 113
interface model_browser undisplay
1. By default, the Message window only displays error and fatal messages and messages from commands
that you execute from the user interface (for example, menus and dialog boxes). You can also display
messages that you execute from the command window, Command navigator, and command files. In
addition, you can set the severity level of the messages displayed, from informational to fatal messages.
2. You can set the message level displayed for ‘graphics_window’, ‘command_window’ and at the
‘start_up’ as either of the ‘quiet’, ‘brief’ or ‘verbose’. Thus, if the parameter is set to ‘quiet’, no message
will appear, and if the parameter is set to ‘verbose’ a detail message will appear.
3. On the other hand, you can the threshold severity or severity to either of the ‘information’, ‘warning’,
‘error’ or ‘fault’. Thus the minimum level for displaying a message will be occurrence of error if the
level is set to ‘error’. Elsewise, you can set a message string by the parameter ‘message’. The limit set
to information will display messages about what is occurring during a command. Setting the message
window to display these types of messages helps you understand what is happening in Adams View
but requires no action from you. Warning message will display messages that warn you that
something unusual occurred but the operation can continue. You may want to fix or change
something to complete the operation without warnings. The error display messages that indicate that
the operation cannot be executed. You need to fix or change something to complete the operation.
The fatal error or fault displays messages that indicate that a programming error occurred. You should
report the message to MSC's Technical Support staff.

Allows you to undisplay the model browser.
Format:
Example:
Undisplays the model browser.
interface model_browser display

Allows you to display the model browser.
Format:
Example:
interface model_browser refresh
Displays the model browser in the last displayed state (docked, undocked).

Allows you to refresh the model browser.
Format:
Example:
Refreshes the model browser.
interface model_browser undock

Allows you to undock the model browser.
Format:
Example:
Undocks the model browser from its docking area.
interface model_browser dock

Allows you to dock the undocked model browser on the specified position.
Format:
interface model_browser dock
position = left or right
interface 115
interface model_browser mbfilter create
Example:
interface model browser dock &
position = left
Description:

position left or right Specifies the position for docking the model
browser
Docks the model browser to the specified position (left or right). Defaults to left if the position is un-
specified.

Allows you to create a filter object in the database.
Format:
mbfilter_name = name of the filter
objects_in_mbfilter = object list
dynamic = static or dyanamic filter
name_filters = list of name filters
type_filters = list of type filters
state_filters = list of object state filters
Example:
interface model_browser mbfilter create &
mbfilter_name = Filter1 &
name_filters = "*" &
type_filters = modeling &
state_filters = active &
dynamic = false
interface object_table copy_object
Description:

mbfilter_name String Name of the filter
objects_in_mbfilter String List of objects in the mbfilter. Used for saving non-
dynamic filters to command models
dynamic: true or false Boolean To set the state of the filter to static or dynamic
name_filters String List of name filters for the model browser filter
type_filters: String List of type filters for the model browser filter
State_filters: String List of the object state filters for the model browser
filter
Creates a model browser filter object in the database with the specified parameters.

Allows you to copy an existing object in a object_table
The object_table is used to list one or more types of objects in a modeling environment. For example, a type
of entities like link, center_marker or properties like mass, inertia can be selectively listed and displayed using
this command. The objects listed can be edited, or copied as required.
The objects in a object_table can be copied using this command.
Format:
object_table_name = a exisitng GI_otable
use_row_selected = true_only
row_index = integer
new_object_name = string
Example:
interface object_table copy_object &
object_table_name = .gui.obj.objt &
row_index = 2 &
new_object_name = "new_object"
interface 117
interface object_table create
Description:

object_table _name An Existing Specifies the name of the object_table from which
GI_otable an object is to be copied
use_row_selected True_only Specifies the row of the object to be copied
row_index Integer Specifies the index of the row to be copied
new_object_name String Specifies a new name for the copied object
‘Row index’ specifies the row position of each of the N entries in the VALUES parameter for a SPARSE
MATRIX. Therefore, for each non-zero value in the SPARSE MATRIX each entry for this parameter defines
to the position in the matrix of the corresponding entry in the VALUES parameter. For example, the third
value entered for the ROW_INDEX parameter defines what matrix row the third value entered for the
VALUES parameter is located on.
The object copied can be accessed through the Adams view window, Similarly, the object copied can be
displayed in the object_table by modifying the ‘object_table’ and adding the copied object name to the
parameter ‘displayed entities’ or selecting to ‘display existing all’.

Allows you to create of a new object_table.
Format:
object_table_name = A New GI_otable
enabled = Boolean
help_text = String
units = Int_units
location = Real
height = Real
width = Real

commands = String
cell_select_commands = String
entity_type = Ent
fields_for_columns = String
column_widths = Integer
filter_function = An Existing Expr_func
displayed_entities = An Existing Entity
parent_entity = An Existing Entity
sorting_column_index = Integer
type_of_sort = Sort_type
ground_reference_frame = Boolean
editable = Boolean
Example:
interface object_table create &
object_table_name = .gui.obj.otb &
enabled = yes &
units = relative &
location = 0.0, 0.0 &
height = 0.6 &
width = 0.6 &
cell_select_commands = "int dialog dis dialog=.gui.moag" &
entity_type = link &
fields_for_columns = i_marker,j_marker,depth &
column_widths = 5 &
displayed_entities = LINK_1,LINK_2,BOX_3,BOX_6,LINK_4,LINK_5,BOX_3,LINK_4 &
parent_entity = .model_1 &
sorting_column_index = 1 &
type_of_sort = alphabetic &
interface 119
interface object_table create &

ground_reference_frame = no &
editable = yes
Description:

object_table _name A New Specifies the name for a new object_table to be created
GI_data_table
enabled Boolean Activates the object_table
units Int_units Specifies the object_table size as pixel or relative to
Adams window
object_table
object_table
location Real Specifies the location of the object_table on the dialog
box
height Real Specifies the height of the object_table in terms of
width Real Specifies the width of the object_table field in terms of
cell select commands String Specifies the command to be executed whenever any cell
is selected
entity type Ent Specifies the entity types to be listed in the object_table
fields_for_columns String Specifies the fields associated with the object to be
entered in the columns
column_widths Integer Specifies the column width for a object_table to be
created
filter_function An Existing Expr Specifies the type of filter to be applied for listing the
Func object types
displayed entities An Existing Entity Specifies the list of entities to be displayed
parent entity An Existing Entity Specifies the parent entity to which the object belongs
sorting column index Integer Specifies the index of the column to be sorted

type of sort Sort_type Specifies the mode of sorting the table contents
ground reference frame Boolean Specifies the ground reference frame
editable Boolean Specifies whether the table contents can be edited or not
1. The preliminary parameters of the object_table like size, associated commands and editing capability
are set using this command. The object_table is then prepared by choosing the types of object,
filtering function and the parent type. The object_table with specified name is created on the dialog
box If parameter ‘Enabled’ is set to ON, the data table is be preactivated.
3. The size of the object_table can be specified either in terms of number of pixels. Alternatively, the size
4. The vertical and horizontal resizing options are used to adjust the placement of the object_table menu
Vert_resizing will place the object_table on the top left corner of the dialog box. The location can also
5. The size of the object_table window can be specified with respect to the Adams window size. The
value for parameter height and width should be a real number between 0.0 and 2.0, where 2.0
represents the height of the dialog window. Therefore, a value of 1.0 will set the object_table field
window to be one half as high as the Adams View window.
8. The ‘entity_type’ is the type of object to be listed in the table. The object types can be link, box, joint,
spline and so on. If the object type is ‘link’ and the ‘parent_type’ is ‘Part_1’, then the links associated
with the Part_1 will be listed.
9. ‘Fields for columns’ are the parameters of a an object type to be selected for listing in the object_table.
For example, the ‘field for columns’ has three parameters namely, 1) mass, 2) center_marker, and 3)
inertia_marker as fields under a model ‘Model_1’ then mass, center_marker, and inertia_marker for
all the parts under ‘Model_1’ will be enlisted in the object_table.
10. The column width for field of the object_table can be specified in terms of units like mm or inches.
If not specified, it will take the default unit for the width values entered.
11. ‘Filter_function’ is used to limit the scope of the search, if you want, to include all objects beneath a
particular object in the database hierarchy by entering the name of the object. For example, enter
.model_1 to display all objects under your entire model or enter .model_1.PART_3 to display objects
belonGIng only to PART_3.
12. ‘Displayed entities’ can be limited to a few by choosing the entities of interest. Otherwise all the
entities for a particular filed will be listed in the object_table. By default the ‘displayed entities’ are
‘Existing all’.
interface 121
interface object_table delete
13. The displayed object can further be limited a parent part by choosing ‘parent type’. For example, the
‘field for column’ has the STRING ‘joints’ with ‘parent type’ as PART_1, all the joint applied to the
PART_1 will be listed in the object_table.
14. All the data listed in the object_table can be sorted either ‘alphabetically’ or ‘numerically’ as required
by choosing the parameter ‘type_of_sort’. Moreover, the all the data will be sorted in accordance with
cell contents of the column marked by ‘sorting column index’. The cell contents of the other affected
columns will be repositioned according to the sorted cell contents of the column marked by ‘sorting
column’. The ‘ground reference frame’ is marked if the BOOLEAN option for ‘ground reference
frame’ is ‘yes’.
15. object_table can be edited after initializing it if the BOOLEAN option is ‘yes’ for the parameter
‘editable’

Allows you to delete the existing object_table.
The object can be directly deleted from the modeling environment by using this command.
Format:
object_table_name = A Exisitng GI_otable
Example:
interface object_table delete &
object_table_name = .gui.obj.otb
Description:

object_table _name An Existing Specifies the name of an existing object_table to be deleted
GI_otable
1. The object_table is deleted by specifying the appropriate ‘object_table name’ in the ‘delete’ command
interface object_table display

Allows you to display the existing object_table.
interface object_table execute
The object_table may not be displayed always, it can be displayed as the need arises by this command.
Format:
interface object_table display
Example:
interface object_table display &
Description:

object_table An Existing Specifies the name of an existing object_table to be displayed
_name GI_otable
1. The object_table is displayed by specifying the appropriate ‘object_table name’ in the ‘display’
command

Allows you to execute the command associated with the object_table.
The command associated with the object_table can be explicitly run by the execute command.
Format:
Example:
interface object_table execute &
interface 123
interface object_table modify
Description:

object_table _name An Existing Specifies the name of the object_table for which the
GI_otable command is to be executed
1. The object_table has ‘command’ as optional parameter. If any command is specified in the field, it
will be executed when the execute command is provided with the appropriate ‘object_table name’.
Tips:
The ‘cell select command gets executed whenever we switch from one cell to another

Allows you to modify the contents of an existing object_table.
The object_table properties can be modified as any table properties in a document like Microsoft Word.
Format:
new_object_table_name = a new GI_otable
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
commands = string
cell_select_commands = string
entity_type = ent

fields_for_columns= string
column_widths= integer
filter_function= an existing expr_func
displayed_entities = an existing entity
parent_entity = an existing entity
sorting_column_index = integer
type_of_sort = sort_type
ground_reference_frame = boolean
editable = boolean
Example:
interface object_table modify &
object_table_name = .gui.obj.otb &
new_object_table_name = .gui.obj.objt &
enabled = yes &
units = relative &
location = 0.4, 0.4 &
height = 0.6 &
width = 0.6 &
cell_select_commands = "int dialog dis dialog=.gui.moag" &
entity_type = link &
fields_for_columns = i_marker,j_marker,depth &
column_widths = 5 &
displayed_entities = LINK_1,LINK_2,BOX_3,BOX_6,LINK_4,LINK_5,BOX_3, LINK_4 &
parent_entity = .model_1 &
sorting_column_index = 1 &
type_of_sort = alphabetic &
ground_reference_frame = no &
editable = yes
interface 125
Description:

object_table _name An Existing Specifies the name of an existing object_table to be
GI_otable modified
new_object_table_na A New GI_otable Specifies a new name for an existing object_table
me
enabled Boolean Activates the object_table
units Int_units Specifies the object_table size as pixel or relative to Adams
window
object_table
object_table
location Real Specifies the location of the object_table on the dialog box
height Real Specifies the height of the object_table in terms of relative
units or pixel
width Real Specifies the width of the object_table field in terms of
cell select commands String Specifies the command to be executed whenever any cell is
selected
entity type Ent Specifies the entity types to be listed in the object_table
fields_for_columns String Specifies the fields associated with the object to be entered
in the columns
column_widths Integer Specifies the column width for a object_table to be created
filter_function An Existing Expr Specifies the type of filter to be applied for listing the
Func object types
displayed entities An Existing Entity Specifies the list of entities to be displayed
parent entity An Existing Entity Specifies the parent entity to which the object belongs
sorting column index Integer Specifies the index of the column to be sorted
type of sort Sort_type Specifies the mode of sorting the table contents
ground reference Boolean Specifies the ground reference frame
frame
editable Boolean Specifies whether the table contents can be edited or not
1. The preliminary parameters of the object_table like size, associated commands and editing capability
are set using this command. The object_table is then prepared by choosing the types of object,
filtering function and the parent type. If the object_table is to be renamed, then fill the parameter
‘new_object_table_name’ with the new suggested name. The object_table with specified name is
created on the dialog box If parameter ‘Enabled’ is set to ON, the data table is be preactivated.
3. The size of the object_table can be specified either in terms of number of pixels. Alternatively, the size
4. The vertical and horizontal resizing options are used to adjust the placement of the object_table menu
on existing dialog box. For example, attach_left, attach_top options for Horiz_resizing and
Vert_resizing will place the object_table on the top left corner of the dialog box. The location can also
5. The size of the object_table window can be specified with respect to the Adams window size. The
represents the height of the dialog window. Therefore, a value of 1.0 will set the object_table field
8. The ‘entity_type’ is the type of object to be listed in the table. The object types can be link, box, joint,
spline and so on. If the object type is ‘link’ and the ‘parent_type’ is ‘Part_1’, then the links associated
with the Part_1 will be listed.
9. ‘Fields for columns’ are the parameters of a an object type to be selected for listing in the object_table.
For example, the ‘field for columns’ has three parameters namely, 1) mass, 2) center_marker, and 3)
inertia_marker as fields under a model ‘Model_1’ then mass, center_marker, and inertia_marker for
all the parts under ‘Model_1’ will be enlisted in the object_table.
10. The column width for field of the object_table can be specified in terms of units like mm or inches.
If not specified, it will take the default unit for the width values entered.
11. ‘Filter_function’ is used to limit the scope of the search, if you want, to include all objects beneath a
particular object in the database hierarchy by entering the name of the object. For example, enter
.model_1 to display all objects under your entire model or enter .model_1.PART_3 to display objects
belonGIng only to PART_3.
12. ‘Displayed entities’ can be limited to a few by choosing the entities of interest. Otherwise all the
entities for a particular filed will be listed in the object_table. By default the ‘displayed entities’ are
‘Existing all’.
13. The displayed object can further be limited a parent part by choosing ‘parent type’. For example, the
‘field for column’ has the STRING ‘joints’ with ‘parent type’ as PART_1, all the joint applied to the
PART_1 will be listed in the object_table.
interface 127
interface object_table set cell
14. All the data listed in the object_table can be sorted either ‘alphabetically’ or ‘numerically’ as required
by choosing the parameter ‘type_of_sort’. Moreover, the all the data will be sorted in accordance with
cell contents of the column marked by ‘sorting column index’. The cell contents of the other affected
columns will be repositioned according to the sorted cell contents of the column marked by ‘sorting
column’. The ‘ground reference frame’ is marked if the BOOLEAN option for ‘ground reference
frame’ is ‘yes’.
15. object_table can be edited after initializing it if the BOOLEAN option is ‘yes’ for the parameter
‘editable’

Allows you to alter the contents of single or multiple cells in a object tableThe object_table is used to list one
or more types of objects in a modeling environment. For example, a type of entities like link, center_marker
or properties like mass, inertia can be selectively listed and displayed using this command. The objects listed
can be edited, or copied as required.
The properties of a single of multiple cells can be edited by using this command.
Format:
use_cell_selected= True_only
row_range= Integer
object_rows = An Existing Entity
use_column_selected= True_only
column_range= Integer
field_name_of_column = String
string = String
action = Col_action
Example:
interface object_table set cell &
row_range = 4,5 &
column_range = 1,1 &
strings = stationary &
action = replace
interface object_table set column
Description:

object_table _name An Existing Specifies the name of the object_table in which the cells
GI_otable are to be altered
use_cell_selected True_only Specifies the cell to be altered directly
row_range Integer Specifies the range of rows to be altered
use_row_selected True_only Specifies the row in which cells are altered
object_rows An Existing Entity Specifies the row to be altered by entering the object
name for the row
use_column_selected True_only Specifies the column in which the cells are altered
column_range Integer Specifies the range of columns in which the cells are to
be altered
field_name_of_column String Specifies the column in which the cells are altered by
entering the field name
string String Specifies the new contents of the cell
action Col_action Specifies the mode of insertion of new contents
1. The cells to be altered are initially addressed by the ‘object_table name’. Next, the exact location of
the cells can be specified by various choices like, ‘use_cell_selected’, ‘row_range’, ‘use_row_selected’,
‘object rows’, ‘use_column_selected’, ‘column range’, and ‘field_name_of_ columns’.
2. The single of multiple cells to be altered can be directly selected with the choice ‘use_cell_selected’.
3. All the cells in a column or a row can be directly selected by choosing the ‘use_column_selected’ and
‘use_row_selected’ parameters.
4. Specifying ‘row range’ and ‘column range’ allows to modify the contents of multiple cells. For
example, row range = 1,2 and column range = 3 will alter the cells (1,3) and (2,3).
5. Alternatively, the row or a column can be selected by specifying the name of the ‘object name’ or the
‘field name for the column’. For example, to rename ‘i_marker’ of the ‘part_3’, the ‘object_rows’ =
part_3 and the ‘field_name_for_column’ = i_marker.
6. The parameter ‘string’ specifies the new contents of the respective cells. The mode of insertion of the
new contents depends on the choice ‘append’, ‘prefix’ or ‘replace’ denoted by the parameter ‘action’

Allows you to alter the contents of single or multiple columns in a object_table
interface 129
The column properties of the object_table can be edited using this command.
Format:
column_width = Integer
column_range = Integer
field_name_of_column = String
string = String
action = Col_action
Example:
interface object_table set column &
column_width = 5 &
column_range = 1,2 &
strings = new_str &
action = replace
Description:

object_table _name An Existing Specifies the name of the object_table in which the
GI_otable cells are to be altered
column_width Integer Specifies a new width for the columns
use_column_selected True_only Specifies the columns in which cells are altered
column_range Integer Specifies the range of columns in which the cells are
to be altered
field_name_of_column String Specifies the column in which the cells are altered by
entering the field name
string String Specifies the new contents of the cell
action Col_action Specifies the mode of insertion of new contents
interface object_table set row
1. The cells to be altered are initially addressed by the ‘object_table name’. Next, the columns to be
altered are marked by various choices like, ‘use_column_selected’, ‘column_range, and
‘field_name_of_ columns’.
2. The width of the columns can be changed by entering a new value of ‘column_width’. The column
width can be specified in units like mm or inches. If not specified, the unit for the parameter field will
be the default length unit.
3. All the cells in a column are selected with the choice ‘use_column_selected’
4. Specifying ‘column range’ allows to modify the contents of multiple cells. For example, column range
= 1,2 will change all the cells in column 1,2.
Alternatively, a column can be selected by specifying the ‘field name for the column’. For example, to
rename cells in column ‘i_marker’ (which is field_name_of_column) the ‘field_name_for_column’ =
i_marker.
The parameter ‘string’ specifies the new contents of the respective cells. The mode of insertion of the
new contents depends on the choices like ‘append’, ‘prefix’ or ‘replace’ denoted by the parameter
‘action’

Allows you to alter the contents of single or multiple rows in a object_table
The row properties of a object_table can be edited using this command.
Format:
use_row_selected= True_only
row_range= Integer
object_rows= An Existing Entity
new_row_entity = An Existing Entity
row_action = Row_action
strings = String
interface 131
Example:
interface object_table set row &
row_range = .model_1.PART_3.LINK_2 &
new_row_entity = .model_1.PART_2.LINK_1 &
row_action = replace
Description:

object_table _name An Existing Specifies the name of the object_table in which the cells are
GI_otable to be altered
Use_row_selected True_only Specifies a row to be altered
row_range Integer Specifies the range of multiple rows to be altered
object_rows An Existing Entity Specifies the object name listed in the row
new_row_entity An Existing Entity Specifies the new object which will be added to the table
row_action Row_action Specifies the mode of insertion of new row
Strings String Specifies the new contents of the cells in a modified row
1. The cells to be altered are initially addressed by the ‘object_table name’. Next, the rows to be altered
are marked by various choices like, ‘use_row_selected’, ‘row_range’, and ‘object_rows’.
2. Specifying ‘row range’ allows to modify the contents of multiple cells in a row. For example, row range
= 1,2 will change all the cells in rows 1,2.
3. Alternatively, the row can be marked by the name of the ‘object’ contained within the row.
4. The row can be altered in two ways, namely, 1) ‘string action’ and 2) ‘object_action’.
5. The choice ‘string action’ will replace all the contents in that row with the new contents specified. On
the other hand if the ‘object action’ is specified, then keeping the ‘field for columns’ same all the
contents of the row for old entity will be replaced with values of ‘field for column’ for the new entity
mentioned.
For example, in the example above, the entity listed in the row is ‘i_marker’ for entity
‘PART_3.LINK_2’ under ‘model_1’. With the execution of the command, the field for the columns
will be replaced by the similar values for the ‘PART_2.LINK_1’ under ‘model_1’.
6. The mode of insertion of the new row contents depends on the choices like ‘before’, ‘after’, ‘delete’
or ‘replace’ denoted by the parameter ‘row_action’.
interface object_table set selected

Allows you to alter the contents of single or multiple selected cells in a object_table
The selected cell properties are edited by using this command.
Format:
strings = string
action = col_action
Example:
interface object_table set selected &
strings = new_str &
action = replace
Description:

object_table _name An Existing Specifies the name of the object_table in which the selected cells
GI_otable are to be altered
strings String Specifies the new contents of the cells in selected cells
action Col_action Specifies the mode of insertion of new cell contents
1. The cells to be altered are initially addressed by the ‘object_table name’. Next, the cells to be altered
are marked by selecting the required cells.
2. The parameter ‘strings’ will replace all the contents in the selected cells with the new contents
specified.
3. The mode of insertion of the new row contents depends on the choices like ‘append’, ‘prefix’, or
‘replace’ denoted by the parameter ‘action’.
interface 133
interface object_table undisplay

Allows you to close the displayed object_table.
The object_table can be closed whenever required by using this command.
Format:
Example:
interface object_table undisplay &
Description:

object_table _name An Existing Specifies the name of an existing object_table to be
GI_otable closed
1. The object_table is closed by specifying the appropriate ‘object_table name’ in the ‘undisplay’
command
interface object_table write

Allows you to write the contents of a object_table field to a file.
The contents of a object_table can be directly written to a excel or tab delimited text file directly by using this
command.
interface option_menu create
Format:
interface object_table write
file_name = String
Example:
interface object_table write &
file_name = c:/objt_1.xls
Description:

object_table _name An Existing GI_otable Specifies the name of the object_table contents of which
are to be written to a file
1. ‘File_name’ specifies the name of the file that is to be read, written, or executed. The proper extension
is 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.

Allows you to create a new information window.
Format:
option_menu_name = a new GI_opt_menu
enabled = boolean
help_text = string
units = int_units
interface 135

location = real
height = real
width = real
choices = string
values = string
commands = string
current_choice = string
Example:
interface option_menu create &
option_menu_name = test &
enabled = yes &
help_text = help &
documentation_text = doc &
units = relative &
location = 0,0 &
height = 1 &
width = 1 &
choices = one, two, three &
values = "10,20,30" &
commands = "model display fit_to_view = no view_name =
all","interface dialog & undisplay dialog=
.gui.moag","interface dialog display
dialog=.gui.moag" &
current_choice = two
Description:

option_menu_name A New Specifies the name of a new information window
GI_opt_menu
enabled Boolean Activates the information window
units Int_units Specifies the information window size in pixels or units
relative to Adams window
horiz_resizing Int_H_Resize Specifies the attachment and scaling option for menu
vert_resizing Int_V_Resize Specifies the attachment and scaling option for menu
location Real Specifies the location of the menu
height Real Specifies the height of the menu in terms of relative units
or pixels
width Real Specifies the width of the menu in terms of relative units
or pixels
choices String Specifies the names of the choices
values String Specifies values of each of the choices
commands String Specifies the command name to be executed associated
with the choice
current_choice String Specifies the current command from the choices
1. A new option menu is created if the menu with the specified name does not exist. This menu has
multiple choices offered as various options or commands are to be executed. Each option or choice
has an associated command.
2. If parameter ‘Enabled’ is set to ON, the menu will be preactivated.
3. The pop-up help and documentation help can be specified in appropriate dialog boxes.
4. The size of the info window can be specified in terms of the number of pixels. Alternatively, the size
5. The vertical and horizontal resizing options are used to adjust the placement of the option menu on
the existing dialog box. For example, attach_left; attach_top options for Horiz_resizing and
Vert_resizing will place the option menu on the top left corner of the dialog box. The location can
also be specified from the top left corner by adjusting the parameter ‘location’.
interface 137
interface option_menu delete
6. The size of the option menu window can be specified with respect to the Adams window size. The
represents the height of the Adams View window. Therefore, a value of 1.0 will set the info window
to be half as high as the Adams View window.
7. Multiple choices can be specified for a number of commands to be executed. The choice can be
offered as any string variable. Similarly, the choices can also be specified as values by specifying the
parameter, ‘value’9. The number of commands equal to the choices offered are entered within
quotation marks, separated by commas.
8. While executing the option menu, the default command to be executed is selected from the
parameter, ‘current choice’.
Tips:
If the values of the choices in item 12 above are numeric, it should be quoted as a string. Similarly, the
complete commands should be entered with quotations. Multiple commands are separated by commas.

Allows you to delete an existing option menu.
Format:
option_menu_name = an existing GI_opt_menu
Example:
interface option_menu delete &
option_menu_name = test
Description:

option_menu_name An Existing Specifies the name of an existing menu to be deleted
GI_opt_menu
An option menu with the specified name is deleted.
interface option_menu display

Allows you to display the existing information.
interface option_menu execute
Format:
interface option_menu display
Example:
interface option_menu display &
option_menu_name = info
Description:

option_menu_name An Existing Specify the name of an information window to be
GI_OPT_Menu displayed.
An existing information will be displayed.

Allows you to execute the command from the option menu.
Format:
Example:
interface option_menu execute &
option_menu_name = test
Description:

option_menu_name An Existing Specifies the name of an existing menu which is to be
GI_opt_menu executed
interface 139
interface option_menu modify
As the information window of the option menu has multiple choices, the default choice GIven as the current
choice determines the associated command to be executed. The command with parameter, ‘current choice’,
is executed.

Allows you to modify an existing option menu.
Format:
new_option_menu_name = a new GI_opt_menu
enabled = boolean
help_text = string
Iunits = int_units
location = real
height = real
width = real
choices = string
values = string
commands = string
current_choice = string
Example:
interface option_menu modify &
option_menu_name = test &
new_option_menu_name = new_test &
enabled = yes &
help_text = help for info window &
documentation_text = doc for the command &
units = relative &
interface option_menu modify &

location = 0,0 &
height = 1 &
width = 1 &
choices = one, two, three &
values = "10,20,30" &
commands = "model display fit_to_view = no view_name =
all","interface dialog &
undisplay dialog=.gui.moag","interface dialog
display dialog=.gui.moag" &
current_choice = two
Description:

option_menu_name A New Specifies the name of an existing information window
GI_opt_menu
new_option_menu_name A New Specifies a new name for the existing information
GI_opt_menu window
enabled Boolean Activates the information window
units Int_units Specifies the info window size in pixels or units relative
to Adams window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for menu
vert_resizing Int_v_resize Specifies the attachment and scaling option for menu
location Real Specifies the location of the menu
height Real Specifies the height of the menu in terms of relative
units or pixels
width Real Specifies the width of the menu in terms of relative
units or pixels
choices String Specifies the names of the choices
values String Specifies value of each of the choices
commands String Specifies the command name to be executed
current_choice String Specifies the current command from the choices
interface 141
interface option_menu set
1. The name of the existing menu can be changed by specifying the parameter
new_option_menu_name. This menu has multiple choices offered as various option or commands
are to be executed. Each option or choice has an associated command.
2. If the parameter, ‘Enabled’, is set to ON, the menu will be preactivated.
5. The vertical and horizontal resizing options are used to adjust the placement of the option menu in
Vert_resizing will place the option menu in the top left corner of the dialog box. The location can
also be specified from the top left corner by adjusting the parameter, ‘location’.
to be half as high as the Adams View window.
7. Multiple choices can be specified for a number of commands to be executed. The choice can be
offered as any string variable. Similarly, the choices can also be specified as values by specifying the
parameter, ‘value’.
8. The number of commands equal to the choices offered are entered within quotation marks, separated
by commas.
9. While executing the option menu, the default command to be executed is selected from the
parameter, ‘current choice’.
Tips:
 If the values of the choices, in item 12 above, are numeric, then it should be quoted as a string.

Allows you to enable the commands from an existing information window.
Format:
choice = string
value = string
execute = boolean
interface option_menu undisplay
Example:
interface option_menu set &
option_menu_name = info &
choice = one &
execute = yes
Description:

option_menu_name An Existing Specifies the name of an existing info window
GI_opt_menu
choice String Specifies any of the multiple choices for an existing
option_menu
value String Specifies any of the multiple values for an existing option_menu
execute Boolean Specifies the BOOLEAN value for enabling and disabling a
choice
The parameter, ‘choice’, lists the options available for an option menu. Alternatively, same choices can be
represented by the parameter, ‘value’. By choosing any of the ‘choice’ or ‘value’ options, the default command
to be run is selected. The execution will run the specified command.
Tips:
The parameters, “choice” and “value”, are mutually exclusive.

Allows you to close an existing information window displayed.
Format:
Example:
interface option_menu undisplay &
option_menu_name = info
interface 143
interface page create
Description:

option_menu_name An Existing Specifies the name of an information window displayed to be
GI_OPT_Menu closed
An existing information window displayed, with the specified name, is closed.

Allows you to create a new page.
The page can be created without opening the Adams postprocessor. The page is used to display plots to show
the results, or to display the model in animation mode. The page properties and layout can be set by using
this command.
Format:
page_name = a new page
layout_type = layout_type
expanded = boolean
header_left_text = string
header_center_text = string
header_right_text = string
footer_left_text = string
footer_center_text = string
footer_right_text = string
header_left_image_file = string
header_center_image_file = string
header_right_image_file = string
footer_left_image_file = string
footer_center_image_file = string
footer_right_image_file = string
display = boolean

set_contents = boolean
page_type = plot_page
Example:
interface page create &
page_name = page_5 &
layout_type = page2x1 &
expanded = yes &
header_left_text = header_left &
header_center_text = header_center &
header_right_text = header_right &
footer_left_text = footer_left &
footer_center_text = footer_center &
footer_right_text = footer_right &
header_left_image_file = "C:/lefthead.bmp" &
header_center_image_file = "C:/centerhead.bmp" &
header_right_image_file = "C:/righthead.bmp" &
footer_left_image_file = "C:/leftfoot.bmp" &
footer_center_image_file = "C:/centerfoot.bmp" &
footer_right_image_file = "C:/rightfoot.bmp" &
display = yes &
color = .colors.RED &
set_contents = yes &
Description:

page_name A New Page Specifies the name of a new page
layout_type Layout_type Specifies the layout of the plot page
expanded Boolean Specifies the page display parameters
header_left_text String Specifies the header text to be displayed
header_center_text String Specifies the header text to be displayed
header_right_text String Specifies the header text to be displayed
interface 145

footer_left_text String Specifies the footer text to be displayed
footer_center_text String Specifies the footer text to be displayed
footer_right_text String Specifies the footer text to be displayed
header_left_image_file String Specifies the image to be displayed at the header
space
space
header_center_image_file String Specifies the image to be displayed at the header
space
header_right_image_file String Specifies the image to be displayed at the header
space
footer_left_image_file String Specifies the image to be displayed at the footer space
footer_center_image_file String Specifies the image to be displayed at the footer space
footer_right_image_file String Specifies the image to be displayed at the footer space
display Boolean Specifies the page display parameter
color An Existng Color Specifies the color of the plot page
set_contents Boolean Specifies the contents of the plot page
page_type Plot_page Specifies the page type
adjoined yes_no Specifies whether the plots on a page are to be
separated by margins or otherwise. The default value
is no (spacing exists between the plots). Applicable to
page1x2, page1x3, page1x4 and page1x5 layouts
only

relative_widths REAL numbers Specify the relative widths (as percentages) for each
plot of a 1xn configuration. Partial values are
supported. In that case, the rest of the plots will be
equally distributed over the remaining width.
For example for a page1x4 layout, if the

relative_widths parameter is specified as 15, 25 then
the first column will occupy 15% of the page width,
the second 25% and the rest of the two will occupy
30% each.
sync_axis [none, vertical, Specifies the axis to sync the zoom on, for all plots on
horizontal] a page. The pre-requisite to this functionality to
work is that there should be only one axis in the
specified direction for all plots on the page and that
the units must be identical.
The default is none (no zoom syncing)

sync_legends yes_no Sync the legend heights across all plot legends on the
specified page. The parameter is applicable only to
page1x2, page1x3, page1x4 and page1x5 layouts and
when all legends have the placement specified as
'plot'.
1. The ‘page’ is a plot window where either a result plot or a model can be displayed. The properties of
the page can be initially set by this command. A blank plot or model page with specified properties
will be displayed with this command.
2. The layout type allows one to display multiple plot windows on the same page where more than one
results can be displayed simultaneously. For example, PAGE 2X1 will display two horizontal plots,
one above the other. On the other hand PAGE 1X2 will display the two plots side by side on the same
page.
3. Any one of the plots on a page can be expanded fully as the need arises by parameter ‘expanded’. If
the ‘expanded’ is set to ‘yes’ one of the multiple plots will occupy full page.
4. The header and footer text can be displayed at left, center or right to add information to the plot by
selecting appropriate ‘header_text’ or ‘footer_text’. Alternatively, an image may be displayed at left,
center or right location of the header or footer to make the plot page self-explanatory. If both the
image and text is specified the image may hide the header of footer text specified. Address of any
remote image file with proper extension should be entered in the parameters ‘header_image_file’ and
‘footer_image_file’ for left, right or center location.
5. The plot will be displayed in the page in the post-processor if the parameter ‘display’ is set to ‘yes’.
6. The background ‘color’ of the page can be chosen from the ‘EXISTING COLORS’.
interface 147
interface page delete
7. The ‘set_contents’ places empty plots in the views if in plotting mode or empty ‘model_space’ in
animation mode.
8. The ‘page type’ is by default ‘plot_page’.

Allows deletion an existing page or plot.
this command.
This command allows the deletion of a panel or its fields, buttons, or text.
Format:
delete_plots = boolean
delete_contents = boolean
display_next = boolean
delete_ptemplates = boolean
Example:
interface page delete &
delete_plots = yes &
delete_ptemplates = yes &
display_next = yes
Description:

page_name An Existing Page Specifies the name of an existing page
delete_plots Boolean Allows deleting a plot
delete_contents Boolean Allows deleting the contents of a plot
display_next Boolean Allows displaying next plot
delete_ptemplates Boolean Allows deleting ptemplates
interface page display
2. The plot can be deleted or the contents of a plots can be deleted keeping the page setting same by
choosing ‘delete_plots’ and ‘delete_contents’ respectively.
3. Once the plot is deleted from the page_window, the next plot will occupy the space if the
‘display_next’ option is set to ‘yes’.
4. The templates are deleted by choosing the parameter ‘delete_ptemplates’

Allows displaying an existing page
this command.
Format:
Example:
interface page display &
page_name = page_5
Description:

1. The ‘page’ can be displayed or undisplayed from the plot window in the postprocessor as and when
required by choosing the appropriate ‘page_name’ while ‘display’ command.
interface page load_view

Allows loading of page_contents on an existing page or plot
interface 149
this command.
Format:
view_index = integer
model = an existing model
plot = an existing plot
ptemplate = an existing ptemplate
Example:
interface page load_view &
view_index = 1 &
model = model_1
Description:

view index Integer Specifies the plot index
model An Existing Model Specifies the model name
plot An Existing Plot Specifies the name of the plot to be displayed
ptemplates An Existing Ptemplate Specifies the name of an existing page template
2. The index of the page can be set by entering ‘view_index‘. The parameter ‘model’ state the existing
‘model_name’, where a model allows you to create and manage models. A model contains a complete
description of a mechanism, including parts, markers, joints, forces and geometry. In order to build
a mechanism in Adams View, you must first create a model object in the Adams View database. You
then add parts and other objects to the model. As you are developing your model, you may display it,
verify it, and change its attributes. Once you have created a model, you add parts to it with the 'PART
CREATE RIGID_BODY NAME_AND_POSITION' command. After you have created your first
interface page modify
part or two, you can continue creating parts, or you may wish to start putting markers on the parts
so you can add geometry, constraints, and forces. You use the 'MARKER CREATE' command to
add markers to a part. Adding markers may help you position other parts, and creating geometry with
markers will help you visualize your model as you are constructing it. When your model is complete,
you use the OUTPUT_CONTROL' command to request Adams output, write an Adams data set,
and then analyze it with Adams. If your analysis is fairly simple, you may use the 'SUBMIT'
command to write the dataset and invoke Adams.
3. The ‘plot’ refers to an existing plot showing results or output. The page templates can also be loaded
in to the ‘page’
Tips:
1. The model, plot and ptemplates are mutually exclusive to each other.

Allows modifying an existing page.
this command.
Format:
layout_type = layout_type
expanded = boolean
header_left_text = string
header_center_text = string
header_right_text = string
footer_left_text = string
footer_center_text = string
footer_right_text = string
header_center_image_file = string
header_right_image_file = string
footer_left_image_file = string
footer_center_image_file = string
footer_right_image_file = string
interface 151

display = boolean
set_contents = boolean
Example:
interface page modify &
layout_type = page2x1 &
expanded = yes &
header_left_text = header_left &
header_center_text = header_center &
header_right_text = header_right &
footer_left_text = footer_left &
footer_center_text = footer_center &
footer_right_text = footer_right &
header_left_image_file = "C:/lefthead.bmp" &
header_center_image_file = "C:/centerhead.bmp" &
header_right_image_file = "C:/righthead.bmp" &
footer_left_image_file = "C:/leftfoot.bmp" &
footer_center_image_file = "C:/centerfoot.bmp" &
footer_right_image_file = "C:/rightfoot.bmp" &
display = yes &
color = .colors.BLUE &
set_contents = no &
Description:

layout_type Layout_type Specifies the layout of the plot page
expanded Boolean Specifies the page display parameters
header_left_text String Specifies the header text to be displayed

header_center_text String Specifies the header text to be displayed
header_right_text String Specifies the header text to be displayed
footer_left_text String Specifies the footer text to be displayed
footer_center_text String Specifies the footer text to be displayed
footer_right_text String Specifies the footer text to be displayed
space
space
header_center_image_file String Specifies the image to be displayed at the header
space
header_right_image_file String Specifies the image to be displayed at the header
space
footer_left_image_file String Specifies the image to be displayed at the footer
space
footer_center_image_file String Specifies the image to be displayed at the footer
space
footer_right_image_file String Specifies the image to be displayed at the footer
space
display Boolean Specifies the page display parameter
color An Existng Color Specifies the color of the plot page
set_contents Boolean Specifies the contents of the plot page
page_type Plot_page Specifies the page type
adjoined yes_no Specifies whether the plots on a page are to be
separated by margins or otherwise. The default
value is no (spacing exists between the plots).
Applicable to page1x2, page1x3, page1x4 and
page1x5 layouts only
interface 153

relative_widths REAL numbers Specify the relative widths (as percentages) for
each plot of a 1xn configuration. Partial values
are supported. In that case, the rest of the plots
will be equally distributed over the remaining
width.
For example for a page1x4 layout, if the

relative_widths parameter is specified as 15, 25
then the first column will occupy 15% of the
page width, the second 25% and the rest of the
two will occupy 30% each.
sync_axis [none, vertical, Specifies the axis to sync the zoom on, for all
horizontal] plots on a page. The pre-requisite to this
functionality to work is that there should be only
one axis in the specified direction for all plots on
the page and that the units must be identical.
The default is none (no zoom syncing)

sync_legends yes_no Sync the legend heights across all plot legends on
the specified page. The parameter is applicable
only to page1x2, page1x3, page1x4 and page1x5
layouts and when all legends have the placement
specified as 'plot'.
2. The layout type allows one to display multiple plot windows on the same page where more than one
results can be displayed simultaneously. For example, PAGE 2X1 will display two horizontal plots,
one above the other. On the other hand PAGE 1X2 will display the two plots side by side on the same
page.
3. Any one of the plots on a page can be expanded fully as the need arises by parameter ‘expanded’. If
the ‘expanded’ is set to ‘yes’ one of the multiple plots will occupy full page.
4. The header and footer text can be displayed at left, center or right to add information to the plot by
selecting appropriate ‘header_text’ or ‘footer_text’. Alternatively, an image may be displayed at left,
center or right location of the header or footer to make the plot page self-explanatory. If both the
image and text is specified the image may hide the header of footer text specified. Address of any
remote image file with proper extension should be entered in the parameters ‘header_image_file’ and
‘footer_image_file’ for left, right or center location.
5. The plot will be displayed in the page in the post-processor if the parameter ‘display’ is set to ‘yes’.
interface page undisplay
6. The background ‘color’ of the page can be chosen from the ‘EXISTING COLORS’.
7. The ‘set_contents’ places empty plots in the views if in plotting mode or empty ‘model_space’ in
animation mode.
8. The ‘page type’ is by default ‘plot_page’.

Allows closing an existing page
this command.
Format:
page_name = An Existing Page
Example:
interface page undisplay &
page_name = page_5
Description:

Page_name An Existing Page Specifies The Name Of An Existing Page
1. The ‘page’ can be displayed or undisplayed from the plot window in the postprocessor as and when
required by choosing the appropriate ‘page_name’ while ‘display’ command.
interface plot panel mode_set

Allows the setting the mode of display in plot panel in the plot window
The plot window can display plots, model, animation as well as reports. The plot panel is displayed below
the plot window enables to select the mode of display in the plot window.
The mode of the display can be any of the following: object, request, measure, result, eigen, default, dac, rpc,
and so on.
interface 155
interface plot panel reload
Format:
interface plot panel mode_set
mode = plot_panel_modes
Example:
interface plot panel mode_set &
mode = object
Description:

mode Plot_panel_modes Specify the mode of display of plot panel parameters
1. The plot panel lists the available items under a parameter like object, request, measure, result, eigen,
default, dac, rpc and so on. For example, if the mode is set to ‘object’, then the panel will display all
the objects under the model with default filters applied. One can choose any object and its
characteristics to be measured from this panel. For example, a simple pendulum modeled in Adams
View may have objects as link with filter ‘body’. The link has characteristics like CM_position,
CM_velocity and so on. for which the x,y, or z components can be displayed in the plot. Otherwise
if the mode is set to measure, then the panel will display all the measure created under the model and
any characteristic components of the same can be chiosen to be displayed.

Allows the reloading the information from the model to the plot panel.
The plot window can display plots, model, animation as well as reports. The plot panel is displayed below
the plot window enables to select the mode of display in the plot window.
The mode of the display can be any of the following: object, request, measure, result, eigen, default, dac, rpc
and so on.
Whenever, the model is edited the it may have few elements added of deleted. This command updates the
information in the plot panel.
Format:
Example:
interface plot window set mode
1. The plot panel lists the available items under a parameter like object, request, measure, result, eigen,
default, dac, rpc, and so on. For example, if the mode is set to ‘object’, then the panel will display all
the objects under the model with default filters applied. One can choose any object and its
characteristics to be measured from this panel. For example, a simple pendulum modeled in Adams
View may have objects as link with filter ‘body’. The link has characteristics like CM_position,
CM_velocity and so on. for which the x,y, or z components can be displayed in the plot.
2. Whenever, the model is edited, the new information of the model can be reloaded into the plot panel
by this command. For example, a new measure created in the model will get displayed in the plot
panel it is ‘reloaded’.
Tips:
The command needs no parameter.

Allows the setting the mode of display in the plot window
The plot window is created in the Adams postprocessor. The plot page can be opened to display plots showing
the results, or to display the model in animation mode.
Any of the modes needs to be set to show particular attribute. This command is used to set the plot window
to any of the modes like plotting , animation, reports or 3dplots
Format:
mode = plot_win_mode
Example:
interface plot window set mode &
mode = plot3d
Description:

mode Plot_win_mode Specifies the mode of display in the plot window
interface 157
interface plot window update_toolbar
1. The plot window can show 2D, 3D plots, animation of the model or reports. The display mode for
a particular window needs to be set to either of these to show the respective windows. Thus, one can
select the ‘animation’ mode and overlay the model to see the animation or plot any result by choosing
‘plots’

Allows to update the page specific icons and fields on toolbar
Format:
Interface plot window update_toolbar
Example:
1. Update page specific icons and fields on toolbar and status window, specifically the page number
fields in the status bar and the page layout icon on the toolbar
Tips:
No parameter needed to be specified.
interface plot window close

Allows closing the plot window of the postprocessor
Format:
Interface plot window close
Example:
interface plot window close
The plot page in the Adams postprocessor can be opened and closed by running the command ‘interface plot
window open’ and ‘’interface plot window close’. It needs no parameter and the default page in the plot
window is opened or the window is closed.
interface plot window create_new_page
interface plot window create_new_page

Allows the creating a new page in the plot window
A new page can be created by using this command which may have a default layout or predefined template.
Format:
interface plot window create new page
default_layout = boolean
display = boolean
Example:
interface plot window create_new_page &
default_layout = yes &
display = yes
Description:

default_layout Boolean Specify a default layout for the plot
display Boolean Specifies the whether the new page should occupy the plot window
1. A new page will be added to the plot window by this command. By default it will have a default layout
with no header or footer.
2. The ‘display’ option set to ‘yes’ will overlay the new page on the existing plot. Otherwise, a new page
will be created but the plot window will have the current page already displayed.
interface plot window delete_page

Allows the deletion of an existing page in the plot window
An existing page in the plot window is deleted by using this command.
interface 159
interface plot window load_view
Format:
delete_ptemplates = boolean
delete_plots = boolean
Example:
Description:

page_name An Existing Page Specify the name of the page to be deleted
delete_ptemplates Boolean Allows page template to be deleted
delete plots Boolean Allows the displayed plot to be deleted
The page can be deleted by choosing the page_name. Similarly, the ‘page template delete’ will also deleted the
page having the specified template.
The ‘delete plots’ will delete the plot in the plot window and the page name is GIven to successive page.

Allows the selective plotting or loading of new contents in the plot window.
The selective plotting from multiple plots can be done by choosing the plot name, animation name, analysis
name, eigen solution name or report name.
Format:
view = An Exisitng View
model_name = An Existing Model
plot_name = An Existing Plot
animation_name = An Existing Animaton
analysis_name = An Existing Analysis

eigen_solution_name = An Existing Eigen Solution
report_name = An Existing Report
Example:
interface plot window load_view &
view = .gui.ppt_main.sash1.sash2.gfx.page_2.view_1 &
plot_name = .plot_3
Description:

view Plot_page_modes Specifies the name of the view
model name An Existing Model Specifies the name of the model to be displayed
plot name An Existing Plot Specifies the name of the plot to be displayed
animation name An Existing Animation Specifies the name of the animation page to be
displayed
analysis name An Existing Analysis Specifies the name of the analysis to be displayed
eigen solution name An Existing Eigen Solution Specifies an existing eigen solution
report name An Existing Report Specifies an existing report to be displayed
1. The selective output from multiple pages and plots in the postprocessor can be displayed in the plot
window by choosing any of the parameter namely; model_name, plot_name, animation_name,
analysis_name, eigen_solution_name, or report_name.
2. The Adams View program provides a set of operations for viewing the Adams model. Some of the
operations are activate, center, erase, fill screen, translate, rotate, zoom, management and so on.
Adams View also provides support and controls for multiple windows. Views can be created,
modified, deleted, saved, restored, and so on. using the view management command. A maximum of
eight windows can exist at any GIven time. Adams View prevents the last window from being deleted.
There is always one view window which is considered the active window. The color of the view name
text and existence of the view name outlining box indicate the active view. The other view windows
have a different view name text color, as well as not having an outlining box around the view name.
The active window is selected by the user using the "view activate" command. It is important to
recognize that a view is made up of three separate parts:
• the contents (the analysis, plot and so on),
• the viewport itself (has size and location), and
• the viewport attributes (the model LOCATION and ORIENTATION in the
interface 161
interface plot window open
• viewport, the RENDER, PROJECTION, TRIAD_VISIBILITY, and

• NAME_VISIBILITY parameters, and so on.)
This is important because different commands are used to manipulate the three part. Some overlap
in control exists but still the distinction exists. The contents of a viewport are controlled by the
GRAPHICS_RESULTS, XY_PLOT, VIEW (other than the "view management" commands), and
so on. The viewport size and location is controlled by the "view management" commands, create and
modify in particular. Finally the viewport attributes are controlled by the "view management"
commands, create and modify, as well as, save and restore. The ‘action’ helps to choose the page
directly by the choice like first, last, previous and next without specifying the names or indices.
3. The ‘model name’ specifies an existing model. You may identify a model by typing its name or by
picking it from the screen. If the model is not visible on the screen, you must type the name. You may
also find it convenient to type the name even if the model is displayed. You must separate multiple
model names by commas. If the model is visible in one of your views, you may identify it by picking
on any of the graphics associated with it. You need not separate multiple model picks by commas.
4. The plot name is a string of characters that identifies a plot. Plot names are assigned when plots are
created. After a plot has been created, it may be referenced by its name until it is deleted. A plot may
NOT have the same name as another plot. A plot_name may be arbitrarily long and a combination
of letters of the alphabet and numbers may be used. The leading character must be a letter.
5. The analysis_name specifies an existing analysis. You may identify a analysis by typing its name or by
picking it from the screen. An analysis may be picked from the screen if you have read an Adams
Graphics file, and use the GRAPHIC_RESULTS command to display it. If the analysis is not visible
analysis is displayed. You may have explicitly named the analysis when you created it by reading one
or more Adams output files. By default, the name of the analysis is the root name of the Adams output
files. If you created the analysis by reading an Adams Graphics file, for instance, the analysis name is
the name of the graphics file without the '.gra' extension. You may get a list of analysis by typing a
"?" in response to a parameter that requires an analysis name be entered. You must separate multiple
analysis names by commas. If the analysis is visible in one of your views, you may identify it by picking
on any of the graphics associated with it. You need not separate multiple analysis picks by commas.

Allows opening the plot window in the postprocessor
Format:
Interface plot window open
Example:
interface plot window page_display
The plot page in the Adams postprocessor can be opened and closed by running the command ‘interface plot
window open’ and ‘’interface plot window close’. It needs no parameter and the default page in the plot
window is opened or the window is closed.
interface plot window page_display

Allows the selective plotting in the plot window
The selective plotting from multiple plots can be done by choosing the plot number, or page_name, else the
successive plots can be displayed.
Format:
interface plot window page display
action = plot_page_modes
number = integer
Example:
interface plot window page_display &
action = next
Description:

action Plot_page_modes Specifies the next, previous, first or last page to be displayed
page_name An Existing Page Specifies the name of the page to be displayed
number Integer Specifies the page number of the page to be displayed
The selective output from multiple pages and plots in the postprocessor can be displayed in the plot window
by choosing any of the parameter namely 1) action, 2) page_name and 3) number.
The ‘action’ helps to choose the page directly by the choice like first, last, previous and next without specifying
the names or indices.
The ‘page_name’ parameter will display the mentioned page in the plot window, alternatively the page can
be accessed by stating its index, that is, the number of the page.
interface 163
interface push_button create
Tips:
1. The action, page_name and number are mutually exclusive to each other. Specifying any of the same
will perform the action.

Allows creation of a push button.
Format:
push_button_name = a new GI_push_btn
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
label = string
icon_file= string
commands = string
dbl_commands = string
default = true_false
Example:
push_button_name = DISP_WIN &
enabled = yes &
help_text = "help_text" &
documentation_text = "doc_text" &
units = relative &
location = 0.0, 0.0 &
height = 0.3 &
width = 0.3 &

label = "label_button" &
icon_file = "c:/images.jpg" &
commands = "interface dialog display dialog=.gui.info_window" &
dbl_commands = "interface dialog display dialog=.gui.about_adams" &
default = true
Description:

push_button_name A New Specifies the name of a new push button
GI_Push_BTN
enabled Boolean Activates the push button
units INT_Units Specifies the push button size as pixel or relative to
Adams window
horiz_resizing INT_H_Resize Specifies the attachment and scaling option for push
button
vert_resizing INT_V_Resize Specifies the attachment and scaling option for push
button
location Real Specifies the location of the push button
height Real Specifies the height of the push button in terms of
width Real Specifies the width of the push button in terms of
label String Specifies label for the push button
icon_file String Specifies the name and location of the image for icon
commands String Specifies the command to be executed with single
click
dbl_commands String Specifies the command name to be executed with
double click
default True_False Set the current status for parameter ‘dbl_command’
interface 165
interface push_button delete
1. The push button has a command associated with it which is created if the push button with specified
name. The parameter ‘Enable’ activates the push button depending on the Boolean value which is
either yes or no
2. If parameter ‘Enabled’ is set to ON, the menu will be preactivated.
4. The size of the info window can be specified either in terms of number of pixels. Alternatively, the
size can also be stated as relative to the Adams window
to be one half as high as the Adams View window.
7. The label which should appear on the button is specified by the parameter ‘label’.
8. Specify the name of the file that contains the icon definition for use on an iconic menu. If an icon file
is selected for the push button, the image will appear on the button instead of the string ‘label’. Its
placement depends on where the axis is placed. The label can be of unlimited length, but may not all
fit on the plot if it's very long. If the string contains spaces, it must be enclosed in quotation marks.
9. The parameter ‘command’ specifies the command to be executed by clicking the push button. You
can also specify a different command for double clicking of the push button. Thus, the push button
can execute two different commands depending upon the single or double click.
Tips:
If the iconic image is selected for display, the display label may not appear

Allows deletion of a push button
Format:
push_button_name = a existing GI_push_btn
Example:
interface push_button delete &
push_button_name = operate
interface push_button display
Description:

push_button_name An Existing GI_Push_BTN Specifies the name of an existing push button
The name of the push button is specified to delete an existing push button.

Allows you to display the push button.
Format:
push_button_name = an existing GI_push_btn
Example:
interface push_button display &
push_button_name = _2
Description:

push_button_name An Existing GI_Push_BTN Specifies the name of an existing push button
The push button is displayed with iconic image, if specified, or the button carries the command name.
interface push_button execute

Allows you determine the mode of the push button operation.
Format:
interface push_button execute
action = push_btn_action
interface 167
interface push_button modify
Example:
interface push_button execute &
push_button_name = _2 &
action = single_click
Description:

push_button_name An Existing Specifies the name of an existing push button
GI_push_btn
action Push_btn_action Determines the mode of the push button operation
The push button can execute the associated commands with a single or double-click, depending on the choice
specified by this command. A single click will carry the execution of ‘command’, while, a double-click will
carry the execution of ‘dbl command’.

Allows you to modify an existing push button.
Format:
new_push_button_name = a new GI_push_btn
enabled = boolean
help_text = string
units = int_units
horiz_resizing = int_H_resize
vert_resizing = int_V_resize
location = real
height = real
width = real
label = string
icon_file= string

commands = string
dbl_commands = string
default = true_false
Example:
interface push_button create &
push_button_name = operate &
new_push_button_name = operate_new&
enabled = yes &
help_text = text_help &
documentation_text = doc_help &
units = relative &
horiz_resizing = expand &
vert_resizing = expand &
location = location = 0,0 &
height = 0.5 &
width = 0.5 &
label = button_label &
icon_file = "C:\ images.jpg" &
dbl_commands = "interface dialog display dialog=.gui.about_adams" &
default = true
Description:

push_button_name A New Specifies the name of an existing push button
GI_push_btn
new_push_button_name A New Specifies a new name for an existing push button
GI_push_btn
enabled Boolean Activates the push button
units Int_units Specifies the push button size in pixels or units relative
to Adams window
interface 169

horiz_resizing Int_H_Resize Specifies the attachment and scaling option for push
button
vert_resizing Int_V_Resize Specifies the attachment and scaling option for push
button
location Real Specifies the location of the push button
height Real Specifies the height of the push button in terms of
relative units or pixels
width Real Specifies the width of the push button in terms of
label String Specifies label of the push button
icon_file String Specifies the name and location of the image for icon
commands String Specifies the command to be executed with a single
click
dbl_commands String Specifies the command name to be executed with a
double-click
default True_False Set the current status for parameter ‘dbl_command’
1. The push button has a command associated with it, which is created if the push button with specified
name. The parameter ‘Enable’ activates the push button depending on the Boolean value, which is
either yes or no. The name of the existing push button can be changed by specifying the
‘new_push_button_name’
2. If the parameter ‘Enabled’ is set to ON, the menu will be preactivated.
from the top left corner by adjusting the parameter, ‘location’
represents the height of the Adams View window. Therefore, a value of 1.0 will set the information
window to be half as high as the Adams View window.
7. The label which should appear on the button is specified by the parameter, ‘label’.
interface push_button undisplay
Specify the name of the file that contains the icon definition for use on an iconic menu. If an icon
file is selected for the push button, the image will appear on the button instead of the string,‘label’.
Its placement depends on where the axis is placed. The label can be of unlimited length, but may not
all fit on the plot if it is very long. If the string contains spaces, it must be enclosed in quotation marks.
8. The parameter ‘command’ specifies the command to be executed by clicking the push button. You
can also specify a different command for double-clicking the push button. Thus, the push button can
execute two different commands, depending upon single or double click.

Allows you to close the displayed push button.
Format:
Example:
interface push_button undisplay &
push_button_name = _2
Description:

push_button_name An Existing Specifies the name of an existing push button
GI_Push_BTN
interface radio_box create

Allows you to create a new radio box
Format:
interface radio box create
radio_box_name = A New GI_radio_box
enabled = Boolean
help_text = String
units = Int_units
interface 171
interface radio box create

location = Real
height = Real
width = Real
choices = String
values = String
commands = String
current_choice = String
Example:
interface radio_box create &
radio_box_name = .gui.rdbx..rdbx1 &
enabled = yes &
help_text = help_text &
documentation_text = doc_text &
units = relative &
height = 0.3 &
width = 0.3 &
choices = yes,no &
values = "1,2" &
commands = "intrface coord_window display=toggle" &
current_choice = yes
Description:

radio_box_name A New GI_radio Specifies a new name for an existing radio box
Box
enabled Boolean Activates the radio box

units Int_units Specifies the radio box size as pixel or relative to
Adams window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for radio
box
vert_resizing Int_v_resize Specifies the attachment and scaling option for radio
box
location Real Specifies the location of the radio box
height Real Specifies the height of the radio box in terms of
width Real Specifies the width of the radio box in terms of
choices String Specifies labels of the choices to be displayed for the
radio box
values String Specifies the real values to be stored in result
component
commands String Specifies the command to be executed by the radio
box
current choice String Specifies the default choice to be executed by the
radio box
1. The name of the radio box to be created is specified initially. If parameter ‘Enabled’ is set to ON, the
radio box button will be preactivated.
3. The size of the radio box can be specified either in terms of number of pixels. Alternatively, the size
4. The vertical and horizontal resizing options are used to adjust the placement of the radio box on
will place the radio box on the top left corner of the dialog box. The location can also be specified
from the top left corner by adjusting the parameter ‘location’.
5. The size of the radio box window can be specified with respect to the Adams window size. The value
the height of the Adams View window. Therefore, a value of 1.0 will set the button window to be one
interface 173
interface radio_box delete
6. The parameter ‘command’ specifies the name of the command to be executed when the radio box is
clicked. If multiple commands are entered then the command to be executed is decided by the
parameter ‘choice’. Alternatively, the values specifies the real values to be stored in the result set
component, The values can be a list of numbers, or an expression referencing an array of existing
values. The ‘current choice’ parameter decides the default value for the radio box from the choices
offered.
interface radio_box delete

Allows deletion of an existing radio box
Format:
interface radio box delete
radio_box_name = An Existing GI_radio_box
Example:
interface radio_box delete &
radio_box_name = .gui.rdbx..rdbx1
Description:

radio_box_name An Existing Specifies the name for an existing radio box to be deleted
GI_radio Box
1. The radio box can be deleted by specifying the appropriate name in the ‘delete’ dialog box.
interface radio_box display

Allows displaying the radio box
Format:
interface radio box display
interface radio_box execute
Example:
interface radio_box display &
radio_box_name = .gui.naresh.rdbx &
choice = "yes" &
execute = no
Description:

radio_box_name An Existing GI_radio Box Specifies the name for an existing radio box to be
displayed
1. The radio box can be displayed on the dialog box by entering appropriate name during the ‘display’
command
interface radio_box execute

Allows execution of a command associated with the radio box
Format:
interface radio box execute
radio_box_name = an existing GI_radio_box
Example:
interface radio_box execute &
radio_box_name = .gui.rdbx..rdbx1
Description:

radio_box_name An Existing Specifies the name for an existing radio box of which the
GI_radio Box command is to be executed
1. The command associated with the radio box can be explicitly executed by the ‘execute’ command,
which is alternatively, executed by clicking the radio box.
interface 175
interface radio_box modify

Allows modifying an existing radio box
Format:
interface radio box modify
new_radio_box_name = A New GI_radio Box
enabled = Boolean
help_text = String
units = Int_units
location = Real
height = Real
width = Real
choices = String
values = String
commands = String
current_choice = String
Example:
interface radio_box modify &
radio_box_name = .gui.obj.rdbx &
enabled = yes &
help_text = "help_text" &
documentation_text = "doc_text" &
units = relative &
height = 0.4 &
width = 0.4 &
choices = yes &
values = “1” &
interface radio_box modify &

current_choice = "yes"
Description:

radio_box_name An Existing Specifies the name of an existing radio box
GI_radio Box
new_radio_box_name A New Specifies a new name for an existing radio box
GI_radio_box
enabled Boolean Activates the radio box
units Int_units Specifies the radio box size as pixel or relative to Adams
window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for radio
box
vert_resizing Int_v_resize Specifies the attachment and scaling option for radio
box
location Real Specifies the location of the radio box
height Real Specifies the height of the radio box in terms of relative
units or pixel
width Real Specifies the width of the radio box in terms of relative
units or pixel
choices String Specifies labels of the choices to be displayed for the
radio box
values String Specifies the real values to be stored in result
component
commands String Specifies the command to be executed by the radio box
current choice String Specifies the default choice to be executed by the radio
box
1. The name of the radio box to be created is specified initially. If parameter ‘Enabled’ is set to ON, the
radio box button will be preactivated. A new name can be suggested for the radio box by specifying
the parameter ‘new_radio_box_name’.
interface 177
interface radio_box set
3. The size of the radio box can be specified either in terms of number of pixels. Alternatively, the size
4. The vertical and horizontal resizing options are used to adjust the placement of the radio box on
will place the radio box on the top left corner of the dialog box. The location can also be specified
5. The size of the radio box window can be specified with respect to the Adams window size. The value
the height of the Adams View window. Therefore, a value of 1.0 will set the button window to be one
6. The parameter ‘command’ specifies the name of the command to be executed when the radio box is
clicked. If multiple commands are entered then the command to be executed is decided by the
parameter ‘choice’. Alternatively, the values specifies the real values to be stored in the result set
component, The values can be a list of numbers, or an expression referencing an array of existing
values. The ‘current choice’ parameter decides the default value for the radio box from the choices
offered.
interface radio_box set

Allows setting up of initial parameters of the radio box
Format:
interface radio box set
choices = String
value= String
execute= Boolean
Example:
interface radio_box set &
radio_box_name = .gui.rdbox.rdbx &
choice = "yes" &
execute = yes
interface radio_box undisplay
Description:

radio_box_name An Existing GI_radio Box Specifies the name for an existing radio box to be
displayed
choices String Specifies the choice for the commands to be executed
value String Specifies the choice for the commands to be executed
execute Boolean Specifies the default parameter for the execution of the
command
1. The command associated with the radio box is specified while creating it. The execution of the same
can be made ON or OFF depending on the BOOLEAN parameter ‘yes’ or ‘no’ for the parameter
‘execute’. Moreover, the selective execution of a command from multiple commands can be done by
specifying the ‘choice’
Tips:
The parameters ‘choice’ and ‘value’ mutually exclusive
interface radio_box undisplay

Allows closing a displayed radio box
Format:
interface radio box undisplay
radio_box_name = an existing GI_radio_box
Example:
interface radio_box undisplay &
radio_box_name= .gui.rdbx..rdbx1
Description:

radio_box_name An Existing Specifies the name for an existing radio box to be closed
GI_radio Box
interface 179
interface separator create
1. The displayed radio box can be closed by entering appropriate radio box name during the ‘undisplay’
command

Allows creation of a new separator
The separator is a is a line look-alike to a embossing element separating two entities on the dialog box. It is
an element to improve the readability of the contents of the dialog box.
This command helps to create the separator on the dialog box, the length of which is specified ‘width’ and
the ‘height’ will specify its placement from top of the dialog box.
Specifies whether or not Adams will write separators to the Request, Graphics, Results, and Tabular Output
Files when you modify the model topology in the middle of a simulation. You can change the model topology
by adding Adams commands to your ACF file to activate an element, deactivate an element, change a marker
position, or change the type or point of application of a force or constraint during a simulation. If you specify
SEPARATOR=ON (this is the default) the analysis information will be read into Adams View, one analysis
for each block of output between the separators. If you specify SEPARATOR=OFF the analysis information
will be read into Adams View as a single analysis. This allow you to plot or animate the analysis from
beGInning to end.
Format:
separator_name = a new GI_separator
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
Example:
interface separator create &
separator_name = .gui.dbox.sepr &
enabled = yes &
interface separator create &

units = relative &
location = 0.0, 0.0 &
height = 0.4 &
width = 0.4
Description:

separator _name A New GI_separator Specifies the name for a new separator to be created
enabled Boolean Activates the separator
units Int_units Specifies the separator size as pixel or relative to dialog
window
separator
separator
location Real Specifies the location of the separator on the dialog box
from upper left corner
height Real Specifies the placement of separator from upper corner
width Real Specifies the width of the separator in terms of relative units
or pixel
1. The preliminary parameters of the separator like location and width are set using this command.
3. The separator is a element look-alike to embossing, which separated two entities on the dialog box.
It has no command or function associated. It is used to improve the readability of the contents of the
dialog box. The placement of the separator on the dialog box is decided by the location, which is the
starting point of the separator line from upper left corner on the dialog box.
4. From the point specified by ‘location’ the placement of the separator below the ‘location’ is decided
by the height and the length of the separator line is decided by the parameter ‘width’
interface 181
interface separator delete

Allows deletion of an existing separator.
beGInning to end.
This command allows deletion of an existing separator.
Format:
separator_name = an existing GI_separator
Example:
interface separator delete &
separator_name = .gui.dbox.sepr
Description:

separator _name An Existing Specifies the name of an existing separator
GI_separator
1. . The separator is deleted by entering the appropriate separator name in the parameter
‘separator_name’ while ‘delete’ command.
interface separator display

Allows displaying of an existing separator
interface separator modify
beginning to end.
This command allows displaying of an existing separator.
Format:
interface separator display
Example:
interface separator display &
Description:

separator _name An Existing GI_separator Specifies the name of an existing separator
1. The separator is displayed by entering the appropriate separator name in the parameter
‘separator_name’ while ‘display’ command.

Allows modifying of an existing separator
interface 183
beGInning to end.
Format:
new_separator_name= a new GI_separator
enabled= boolean
help_text = string
units = int_units
location = real
height = real
width = real
Example:
interface separator modify &
separator_name = .gui.dbox.sepr &
new_separator_name = .gui.dbox.sepr1 &
enabled = yes &
units = relative &
location = 0.2, 0.0 &
height = 0.6 &
width = 0.7
interface separator undisplay
Description:

separator _name An Existing Specifies the name of an existing separator
GI_separator
new_separator_name A New GI_separator Specifies a new name for the existing separator
enabled Boolean Activates the separator
units Int_units Specifies the separator size as pixel or relative to dialog
window
separator
separator
location Real Specifies the location of the separator on the dialog box
from upper left corner
height Real Specifies the placement of separator from upper corner
width Real Specifies the width of the separator in terms of relative
units or pixel
1. The preliminary parameters of the separator like location and width are set using this command. A
new name can be specified for an existing separator by the parameter ‘new_separator_name’.
3. The separator is a element look-alike to embossing, which separated two entities on the dialog box.
It has no command or function associated. It is used to improve the readability of the contents of the
dialog box. The placement of the separator on the dialog box is decided by the location, which is the
starting point of the separator line from upper left corner on the dialog box.
4. From the point specified by ‘location’ the placement of the separator below the ‘location’ is decided
by the height and the length of the separator line is decided by the parameter ‘width’

Allows closing of an existing separator.
interface 185
interface slider create
beGInning to end.
This command allows undisplaying of an existing separator.
Format:
Example:
interface separator undisplay &
Description:

separator _name An Existing GI_separator Specifies the name of an existing separator
1. The separator is closed by entering the appropriate separator name in the parameter ‘separator_name’
while ‘undisplay’ command.

Allows you to create of a new slider on the dialog box.
The slider is an element on the dialog box, specifying a variable parameter, the dragGIng of the slider bar,
will vary the parameter value between minimum and maximum depending on the current position of the
slider.
Format:
slider_name = A New GI_slider
enabled = Boolean
help_text = String

units = Int_units
location = Real
height = Real
width = Real
commands = String
value = Integer
minimum = Integer
maximum = Integer
live_drag = Boolean
show_value = Boolean
Example:
interface slider create &
slider_name = .gui.dbox.sldr &
enabled = yes &
units = relative &
location = 0.2, 0.2 &
height = 0.2 &
width = 0.6 &
commands = "view zoom view=.gui.main.front zoom=1.0" &
value = 1 &
minimum = 0 &
maximum = 10 &
live_drag = yes &
show_value = yes
interface 187
Description:

slider _name A New GI_slider Specifies the name of a new slider
enabled Boolean Activates the slider
units Int_units Specifies the slider size as pixel or relative to dialog box
window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for the slider
vert_resizing Int_v_resize Specifies the attachment and scaling option for the slider
location Real Specifies the location of the slider on the dialog box
height Real Specifies the height of the slider in terms of relative units
or pixel
width Real Specifies the width of the slider field in terms of relative
units or pixel
commands String Specifies the command to be executed while the slider is
dragged
value Integer Specifies the default value of the command
minimum Integer Specifies the minimum value at the beGInning of slider
maximum Integer Specifies the maximum value at the end of slider
live_drag Boolean Specifies the live display of current value on the slider
show_value Boolean Specifies the default parameter for displaying the current
slider value
1. The preliminary parameters of the slider like size, associated commands and range of values are set
using this command.
3. The size of the slider can be specified either in terms of number of pixels. Alternatively, the size can
4. The vertical and horizontal resizing options are used to adjust the placement of the slider menu on
will place the slider on the top left corner of the dialog box. The location can also be specified from
interface slider delete
5. The size of the slider window can be specified with respect to the dialog box window size. The value
the height of the dialog window. Therefore, a value of 1.0 will set the slider field window to be one
6. The parameter ‘command’ specifies the name of the command to be executed, when the slider is
dragged. The parameters ‘minimum’ and ‘maximum’ shows the slider lower and upper limit values,
the instantaneous or current value of which is displayed over the slider, if the parameter ‘show_value’
is set to ‘yes’. Similarly, if the command to be executed concurrently with the slider movement, when
the slider is dragGIng, the parameter ‘live_drag’ needs to be set to ‘yes’.

Allows deletion of an existing slider on the dialog box.
slider.
Format:
slider_name = An Existing GI_slider
Example:
interface slider delete &
slider_name = .gui.dbox.sldr
Description:

slider _name An Existing Specifies the name of an existing slider
GI_slider
1. The slider can be deleted by specifying the appropriate name for the parameter ‘slider_name’ in the
delete dialog box.
interface slider display

Allows displaying of an existing slider on the dialog box.
interface 189
interface slider execute
slider.
Format:
interface slider display
slider_name = an existing GI_slider
Example:
interface slider display &
Description:

slider _name An Existing GI_slider Specifies the name of an existing slider
1. The slider can be displayed by specifying the appropriate name for the parameter ‘slider_name’ in the
display dialog box.

Allows execution of a command associated with the slider.
slider.
The optional command associated with the slider can be explicitly run by this command.
Format:
Example:
interface slider execute &
interface slider modify
Description:

1. The slider has an optional parameter, ‘command’, if specified gets executed explicitly without
dragGIng the slider bar by the command ‘execute’.

Allows modifying of an existing slider on the dialog box.
slider.
Format:
new_slider_name = A New GI_slider
enabled = Boolean
help_text = String
units = Int_units
location = Real
height = Real
width = Real
commands = String
value = Integer
minimum = Integer
maximum = Integer
live_drag = Boolean
show_value = Boolean
interface 191
Example:
interface slider modify &
new_slider_name = .gui.dbox.sldr1 &
enabled = yes &
units = relative &
height = 0.2 &
width = 0.6 &
value = 0 &
minimum = 0 &
maximum = 1 &
live_drag = yes &
show_value = yes
Description:

slider _name An Existing Specifies the name of an existing slider
GI_slider
new_slider_name Specifies a new name for the slider
enabled Boolean Activates the slider
units Int_units Specifies the slider size as pixel or relative to dialog box
window
horiz_resizing Int_h_resize Specifies the attachment and scaling option for the slider
vert_resizing Int_v_resize Specifies the attachment and scaling option for the slider
location Real Specifies the location of the slider on the dialog box
height Real Specifies the height of the slider in terms of relative units
or pixel
interface slider set

width Real Specifies the width of the slider field in terms of relative
units or pixel
commands String Specifies the command to be executed while the slider is
dragged
value Integer Specifies the default value of the command
minimum Integer Specifies the minimum value at the beGInning of slider
maximum Integer Specifies the maximum value at the end of slider
live_drag Boolean Specifies the live display of current value on the slider
show_value Boolean Specifies the default parameter for displaying the current
slider value
1. The preliminary parameters of the slider like size, associated commands and range of values are set
using this command. A new name can be specified for the slider by using parameter
‘new_slider_name’.
3. The size of the slider can be specified either in terms of number of pixels. Alternatively, the size can
4. The vertical and horizontal resizing options are used to adjust the placement of the slider menu on
will place the slider on the top left corner of the dialog box. The location can also be specified from
5. The size of the slider window can be specified with respect to the dialog box window size. The value
the height of the dialog window. Therefore, a value of 1.0 will set the slider field window to be one
6. The parameter ‘command’ specifies the name of the command to be executed, when the slider is
dragged. The parameters ‘minimum’ and ‘maximum’ shows the slider lower and upper limit values,
the instantaneous or current value of which is displayed over the slider, if the parameter ‘show_value’
is set to ‘yes’. Similarly, if the command to be executed concurrently with the slider movement, when
the slider is dragGIng, the parameter ‘live_drag’ needs to be set to ‘yes’.

Allows setting-up of initial parameters for an existing slider on the dialog box.
slider.
interface 193
interface slider undisplay
Format:
value = Integer
execute = Boolean
Example:
interface slider set &
value = 3 &
execute = yes
Description:

slider _name An Existing Specifies the name of an existing slider.
GI_slider
value Integer Specifies the current value of the slider position.
execute Boolean Specifies whether the associated command will be executed
or not.
1. The slider can be set to default parameter by choosing the parameter ‘value’, which denotes the
instantaneous current value of the slider position between the minimum and maximum values
specified. The execute option specifies the whether the associated command will be executed or not,
when the slider is dragged.

Allows closing of an existing slider on the dialog box.
slider.
Format:
slider_name = an existing GI_slider
interface tab_container create
Example:
interface slider undisplay &
Description:

1. The slider can be closed by specifying the appropriate name for the parameter ‘slider_name’ in the
‘undisplay’ dialog box.

Allows you to create of a new tab_container.
Tab_container is similar to a container but can be added to a dialog box or another container. When you add
a tab_container, a tab appears in the parent container.
Format:
interface object tab_container create
object_table_name = A New GI_tab_container
enabled = Boolean
help_text = String
units = Int_units
location = Real
height = Real
width = Real
commands = String
current choice = String
interface 195
Example:
interface tab_container create &
tab_container_name = .gui.cntr.tabcnt &
enabled = yes &
units = relative &
location = 0.0, 0.0 &
height = 0.4 &
width = 0.4 &
Description:

tab _container_name A New GI_tab_container Specifies the name for a new tab_container to
be created
enabled Boolean Activates the tab_container
units Int_units Specifies the tab_container size as pixel or
horiz_resizing Int_h_resize Specifies the attachment and scaling option
for the tab_container
vert_resizing Int_v_resize Specifies the attachment and scaling option
for the tab_container
location Real Specifies the location of the tab_container on
the dialog box
height Real Specifies the height of the tab_container in
terms of relative units or pixel
interface tab_container delete

width Real Specifies the width of the tab_container field
in terms of relative units or pixel
current choice String Specifies the default option for the command
to be executed
1. The preliminary parameters of the tab_container like size, associated commands and editing
capability are set using this command.
3. The size of the tab_container can be specified either in terms of number of pixels. Alternatively, the
size can also be stated as relative to the Adams window
4. The vertical and horizontal resizing options are used to adjust the placement of the tab_container
menu on existing dialog box. For example, attach_left; attach_top options for Horiz_resizing and
Vert_resizing will place the tab_container on the top left corner of the dialog box. The location can
also be specified from the top left corner by adjusting the parameter ‘location’
5. The size of the tab_container window can be specified with respect to the Adams window size. The
represents the height of the dialog window. Therefore, a value of 1.0 will set the tab_container field
6. The parameter ‘command’ specifies the name of the command to be executed, whereas the current
choice determines the default choice for the execution of the command.
interface tab_container delete

Allows deleting an existing tab_container.
Format:
interface object tab_container delete
tab_container_name = an exisitng GI_tab_container
Example:
interface tab_container delete &
tab_container_name = .gui.cntr.tabcnt
interface 197
interface tab_container display
Description:

tab_container_name An Existing Specifies the name of an existing tab_container to be deleted
GI_tab_container
1. The tab_container can be deleted by choosing the appropriate name for the ‘tab_container’ during
the ‘delete’ command
interface tab_container display

Allows displaying an existing tab_container.
The tab_container can be displayed or closed as the need arises
Format:
interface object tab_container display
tab_container_name = an exisitng gi_tab_container
Example:
interface tab_container display &
Description:

tab_container_name An Existing Specifies the name of an existing tab_container
GI_tab_container to be displayed
1. The tab_container can be displayed by choosing the appropriate name for the ‘tab_container’ during
the ‘display’ command
interface tab_container execute

Allows executing a command associated with an existing tab_container.
interface tab_container modify
The tab_container has an optional command parameter, if specified a command, it gets executed while
running the ‘execute’ command.
Format:
interface object tab_container execute
Example:
interface tab_container execute &
Description:

tab _container_name An Existing Specifies the name of an existing tab_container the
GI_tab_container command for which needs to be executed
1. The tab_container associated command can be executed by running explicitly the ‘execute’
command.

Allows modifying the tab_container properties.
Format:
interface object tab_container modify
new_ tab_container_name = a new gi_tab_container
enabled = boolean
help_text = string
units = int_units
interface 199
interface object tab_container modify

location = real
height = real
width = real
commands = string
current choice = string
Example:
interface tab_container create &
enabled = yes &
units = relative &
location = 0.0, 0.0 &
height = 0.4 &
width = 0.4 &
Description:

tab_container_name An Existing Specifies the name of an existing tab_container to
GI_tab_container be modified
new_tab_container_name A New GI_tab_container Specifies a new name for the tab_container
enabled Boolean Activates the tab_container
units Int_units Specifies the tab_container size as pixel or relative
to Adams window
interface tab_container set

horiz_resizing Int_h_resize Specifies the attachment and scaling option for
the tab_container
vert_resizing Int_v_resize Specifies the attachment and scaling option for
the tab_container
location Real Specifies the location of the tab_container on the
dialog box
height Real Specifies the height of the tab_container in terms
of relative units or pixel
width Real Specifies the width of the tab_container field in
terms of relative units or pixel
current choice String Specifies the default option for the command to
be executed
1. The preliminary parameters of the tab_container like size, associated commands and editing
capability are set using this command. To rename the tab_container, fill the parameter
‘new_tab_container_name’.
3. The size of the tab_container can be specified either in terms of number of pixels. Alternatively, the
size can also be stated as relative to the Adams window.
4. The vertical and horizontal resizing options are used to adjust the placement of the tab_container
menu on existing dialog box. For example, attach_left; attach_top options for Horiz_resizing and
Vert_resizing will place the tab_container on the top left corner of the dialog box. The location can
also be specified from the top left corner by adjusting the parameter ‘location’.
5. The size of the tab_container window can be specified with respect to the Adams window size. The
represents the height of the dialog window. Therefore, a value of 1.0 will set the tab_container field
6. The parameter ‘command’ specifies the name of the command to be executed, whereas the current
choice determines the default choice for the execution of the command.
interface tab_container set

Allows setting up of default parameters for a tab_container
interface 201
interface tab_container undisplay
The tab_container has an optional command parameter, if specified a command, it gets executed while
running the ‘execute’ command.
Format:
interface object tab_container set
choice = stirng
execute = boolean
Example:
interface tab_container set &
choice = "1" &
execute = yes
Description:

tab _container_name An Existing Specifies the name of an existing tab_container the command
GI_tab_container for which needs to be executed
choice String Specifies the choice of the command to be executed
execute Boolean Specifies the default parameter for execution of the command
1. The tab_container associated command can be executed by running explicitly the ‘execute’
command. The default state for running a command depends on the BOOLEAN value of the
parameter ‘execute’ in the ‘set’ command.
interface tab_container undisplay

Allows closing an existing tab_container.
The tab_container can be displayed or closed as the need arises
interface toggle_button create
Format:
interface object tab_container undisplay
Example:
interface tab_container undisplay &
Description:

tab _container_name An Existing Specifies the name of an existing tab_container to be
GI_tab_container closed
1. The tab_container can be closed by choosing the appropriate name for the ‘tab_container’ during the
‘undisplay’ command

Allows you to create a new toggle button
Format:
toggle_button_name = a new GI_toggl_btn
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
label = string
state = on_off
interface 203

on_value = string
off_value = string
commands = string
icon_file = string
hit_icon_file = string
Example:
interface toggle_button create &
toggle_button_name = tgb &
enabled = yes &
help_text = text_help &
documentation_text = doc_help &
units = relative &
location = 0.0, 0.0 &
height = 0.5 &
width = 0.5 &
label = button_label &
state = on &
on value = on &
off value = off &
icon file = c:/images.jpg &
Hit icon file = c:/images1.jpg
Description:

toggle_button_name A New GI_toggl_btn Specifies the name of a new toggle button
enabled Boolean Activates the toggle button

units Int_units Specifies the toggle button size in pixels or units
horiz_resizing Int_h_resize Specifies the attachment and scaling option for toggle
button
vert_resizing Int_v_resize Specifies the attachment and scaling option for toggle
button
location Real Specifies the location of the toggle button
height Real Specifies the height of the toggle button in terms of
width Real Specifies the width of the toggle button in terms of
label String Specifies label of the toggle button
state On_Off Specifies the current status of the toggle button
value String Specifies the current status of the toggle button
commands String Specifies the command to be executed for the toggle
button operation
icon_file String Specifies the address of the image for icon when button
is inactive
Hit_icon file String Specifies the address of the image for icon when the
button is active
1. The name of the toggle button to be created is specified initially. If parameter ‘Enabled’ is set to ON,
the toggle button will be preactivated.
3. The size of the toggle button can be specified in terms of the number of pixels. Alternatively, the size
4. The vertical and horizontal resizing options are used to adjust the placement of the option menu in
Vert_resizing will place the option menu on the top left corner of the dialog box. The location can
also be specified from the top left corner by adjusting the parameter, ‘location’.
5. The size of the toggle button window can be specified with respect to the Adams window size. The
window to be half as high as the Adams View window.
interface 205
interface toggle_button delete
6. If the Label is specified, then the string associated will appear with a toggle window, where click and
unclick will be denoted by a ‘tick’. Alternatively, if the iconic image is selected for the toggle button,
then the iconic button will be displayed with corresponding image on it, with no label of ‘tick-mark’.
The label for an axis will be displayed near the axis, its placement depending on where the axis is
placed. The label can be of unlimited length, but may not all fit on the plot if it is very long. If the
string contains spaces, it must be enclosed in quotation marks. The parameter ‘icon_file’ specifies the
name of the file that contains the icon definition for use on an iconic menu.
7. The default state of the toggle button is specified by ‘state’, whether it is on or off. Otherwise, the
values are specified as string where the status of the toggle button can marked. It is mutually exclusive
with the ‘state’ mentioned above.
8. The parameter ‘command’ specifies the name of the command to be executed when the toggle button
status is ON.
9. The push button iconic image can be changed by specifying the ‘Hit_icon_file’, that is, when the
push button is active, it will show one image on the button, and when it is toggled or inactive, the
iconic image will toggle to another image file specified.
Tips:
The parameters, ‘state’ and ‘value’, are mutually exclusive. The display and undisplay of commands work
when any menu box is open, as the button will be created on existing menu

Allows you to delete an existing toggle button.
Format:
toggle_button_name = an existing GI_toggl_btn
Example:
interface toggle_button delete &
toggle_button_name = tgb
Description:

toggle_button_name An Existing GI_toggl_btn Specifies the name of an existing toggle button
An existing toggle button is deleted by specifying the name of the toggle button.
interface toggle_button display

Allows you to display an existing toggle button.
Format:
Example:
interface toggle_button display &
Description:

The toggle button appears on any of the menus displayed.
Tips:
Atleast one menu needs to be displayed initially to place a toggle button.
interface toggle_button execute

Allows you to execute a toggle button command.
Format:
interface toggle_button execute
Example:
interface toggle_button execute &

toggle_button_name An Existing Specifies the name of an existing toggle button
GI_toggl_btn
interface 207
interface toggle_button modify
The command associated with a toggle button can be executed directly, without clicking the button.

Allows you to modify an existing toggle button.
Format:
new_toggle_button_name = a new GI_toggl_btn
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
label = string
state = on_off
on_value = string
off_value = string
commands = string
icon_file = string
hit_icon_file = string
Example:
interface toggle_button modify &
new_toggle_button_name = tgb2 &
enabled = yes &
help_text = "text_help" &
documentation_text = "text_doc" &
units = relative &
interface toggle_button modify &

height = 0.3 &
width = 0.3 &
label = "button_label" &
state = on &
on_value = "on" &
off_value = "off" &
icon_file = "c:/images.jpg" &
hit_icon_file = "c:/images1.jpg"
Description:

GI_toggl_btn
new_toggle_button_nam A New GI_toggl_btn Specifies a new name for an existing toggle button
e
enabled Boolean Activates the toggle button
units Int_units Specifies the toggle button size in pixels or units
horiz_resizing Int_h_resize Specifies the attachment and scaling option for toggle
button
vert_resizing Int_v_resize Specifies the attachment and scaling option for toggle
button
location Real Specifies the location of the toggle button
height Real Specifies the height of the toggle button in terms of
width Real Specifies the width of the toggle button in terms of
label String Specifies label of the toggle button
state On_off Specifies the current status of the toggle button
interface 209

value String Specifies the current status of the toggle button
commands String Specifies the command to be executed for the toggle
button operation
icon_file String Specifies the address of the image for icon when
button is inactive
Hit_icon file String Specifies the address of the image for icon when the
button is active
1. The name of an existing toggle button is specified initially. If parameter ‘Enabled’ is set to ON, the
toggle button will be preactivated.
3. The size of the toggle button can be specified in terms of the number of pixels. Alternatively, the size
from the top left corner by adjusting the parameter, ‘location’.
5. The size of the toggle button window can be specified with respect to the Adams window size. The
window to half as high as the Adams View window.
6. If the Label is specified, then the string associated will appear with a toggle window, where click and
unclick will be denoted by a ‘tick’. Alternatively, if the iconic image is selected for the toggle button,
then the iconic button will be displayed with corresponding image on it, with no label of ‘tick-mark’.
The label for an axis will be displayed near the axis, its placement depending on where the axis is
placed. The label can be of unlimited length, but may not all fit on the plot if it is very long. If the
string contains spaces, it must be enclosed in quotation marks. The parameter, ‘icon_file’ specifies the
name of the file that contains the icon definition for use on an iconic menu.
7. The default state of the toggle button is specified by ‘state’, whether it is on or off. Otherwise, the
values are specified as string where the status of the toggle button can be marked. It is mutually
exclusive with the ‘state’ mentioned above.
8. The parameter ‘command’ specifies the name of the command to be executed when the toggle button
status is ON.
9. The push button iconic image can be changed by specifying the ‘Hit_icon_file’, that is, when the push
button is active, it will show one image on the button, and when it is toggled or inactive, the iconic
image will toggle to another image file specified.
interface toggle_button set
Tips:
The parameters, ‘state’ and ‘value’, are mutually exclusive.
The commands display and undisplay works when any menu box is open, as the button will be created on
an existing menu.

Allows you to set up the initial parameters of the toggle button
Format:
state = on_off
value = string
execute = boolean
Example:
interface toggle_button set &
state = on &
execute = yes
Description:

GI_toggl_btn
state On_Off Specifies the current state of the toggle button
value String Specifies the current state of the toggle button
execute Boolean Specifies the execution of the associated command
1. The state or the value denotes the current status of the button when it is displayed. Thus, if the status
is ON, the toggle button will be ON when displayed.
2. The SET command is used to setup the initial condition of the parameters when the button is
displayed or activated.
interface 211
interface toggle_button undisplay
Tips:
The parameters, ‘value’ and ‘state’, are mutually exclusive.

Allows you to close a displayed toggle button.
Format:
Example:
interface toggle_button display &

The toggle button displayed on of the any menus, is closed.
interface toolbar create

Allows you to create a new toolbar.
The toolbar can be created on a existing pop_window or a window, where various toolbar buttons can be
placed.
Format:
toolbar_name = a new GI_toolbar
enabled = boolean
help_text = string
units = int_units
location = real

height = real
width = real
rank = integer
top = boolean
Example:
interface toolbar create &
toolbar_name = .gui.ppwndw.tlbr &
location = 0.2, 0.2 &
height = 0.2 &
width = 0.9 &
enabled = yes &
units = relative &
rank = 2 &
top = yes
Description:

toolbar _name A New GI_toolbar Specifies the name of a new toolbar
enabled Boolean Activates the toolbar
units Int_units Specifies the toolbar size as pixel or relative to
pop_up window
toolbar
toolbar
location Real Specifies the location of the toolbar on the pop_up
window
interface 213
interface toolbar delete

height Real Specifies the height of the toolbar in terms of
width Real Specifies the width of the toolbar field in terms of
rank Integer Specifies the rank of the toolbar in case of multiple
toolbars
top Boolean Keeps the toolbar on the top of other windows
1. The preliminary parameters of the toolbar like size, rank and label are set using this command.
3. The size of the toolbar can be specified either in terms of number of pixels. Alternatively, the size can
also be stated as relative to the pop_up window
4. The vertical and horizontal resizing options are used to adjust the placement of the toolbar menu on
existing pop_window. For example, attach_left; attach_top options for Horiz_resizing and
Vert_resizing will place the toolbar on the top left corner of the pop_up. The location can also be
specified from the top left corner by adjusting the parameter ‘location’
5. The size of the toolbar window can be specified with respect to the pop_up window size. The value
the height of the window. Therefore, a value of 1.0 will set the toolbar to be one half as high as the
pop_up window.
6. The toolbar remains on the ‘top’ of other windows if specified ‘yes’ for the parameter ‘top’

Allows deletion of an existing toolbar.
placed.
Format:
toolbar_name = an existing GI_toolbar
Example:
interface toolbar delete &
toolbar_name = .gui.ppwndw.tlbr
interface toolbar display
Description:

toolbar _name An Existing GI_Toolbar Specifies the name of an existing toolbar
1. The toolbar can be deleted by specifying the ‘toolbar name’ while the ‘delete’ command.

Allows displaying of an existing toolbar.
placed.
Format:
Example:
interface toolbar display &
toolbar_name = .gui.new_window.tlbr
Description:

toolbar _name An Existing Gi_toolbar Specifies the name of an existing toolbar
1. The toolbar can be displayed or closed as the need arises by using the ‘display’ and ‘undisplay’
commands.
interface toolbar modify

Allows you to modify an existing toolbar.
placed.
interface 215
Format:
new_toolbar_name = a new GI_toolbar
enabled = boolean
help_text = string
units = nt_units
location = real
height = real
width = real
rank = integer
top = boolean
Example:
interface toolbar modify &
toolbar_name = .gui.ppwndw.tlbr &
new_toolbar_name = .gui.ppwndw.tlbr1 &
location = 0.2, 0.2 &
height = 0.2 &
width = 0.9 &
enabled = yes &
units = relative &
rank = 2 &
top = yes
Description:

toolbar _name An Existing Specifies the name of an existing toolbar
GI_toolbar
new_toolbar_name A New GI_toolbar Specifies a new name for an existing toolbar
enabled Boolean Activates the toolbar
units Int_units Specifies the toolbar size as pixel or relative to
pop_up window
toolbar
toolbar
location Real Specifies the location of the toolbar on the pop_up
window
height Real Specifies the height of the toolbar in terms of
width Real Specifies the width of the toolbar field in terms of
rank Integer Specifies the rank of the toolbar in case of multiple
toolbars
top Boolean Keeps the toolbar on the top of other windows
1. The preliminary parameters of the toolbar like size, rank and label are set using this command.
3. The size of the toolbar can be specified either in terms of number of pixels. Alternatively, the size can
also be stated as relative to the pop_up window
4. The vertical and horizontal resizing options are used to adjust the placement of the toolbar menu on
existing pop_window. For example, attach_left; attach_top options for Horiz_resizing and
Vert_resizing will place the toolbar on the top left corner of the pop_up. The location can also be
specified from the top left corner by adjusting the parameter ‘location’
5. The size of the toolbar window can be specified with respect to the pop_up window size. The value
the height of the window. Therefore, a value of 1.0 will set the toolbar to be one half as high as the
pop_up window.
interface 217
interface toolbar undisplay
6. The toolbar remains on the ‘top’ of other windows if specified ‘yes’ for the parameter ‘top’

Allows closing of an existing toolbar
placed.
Format:
Example:
interface toolbar undisplay &
toolbar_name = .gui.ppwndw.tlbr
Description:

toolbar _name An Existing GI_Toolbar Specifies the name of an existing toolbar
1. The toolbar can be displayed or closed as the need arises by using the ‘display’ and ‘undisplay’
commands.
interface view create

Allows you to create a new view with user defined location and orientation
The Adams view has some preset views, viz., .gui.main.front, .gui.main.right. The user can create a custom
view with predefined orientation and display specifications, which can be created on the main view window
or a separate window. The view can be set-up by parameters like eye, target, and up_vector.
Format:
Interface view create
view_name = a new view
enabled = boolean
help_text = string
Interface view create

units = int_units
location = real
height = real
width = real
eye = location
target = location
up_vector = location
Example:
interface view create &
view_name = .gui.win.user_view &
enabled = yes &
units = relative &
location = 0.0, 0.0 &
height = .4 &
width = .4 &
eye = 0,0,1000 &
target = 500,0,0 &
up_vector = 0,1000,0
Description:

view_name A New View Specifies the name for a new view
enabled Boolean Activates the view
interface 219

units Int_units Specifies the view size as pixel or relative to Adams
or custom window
the view
the view
location Real Specifies the location of the view on the dialog
box
height Real Specifies the height of the view in terms of relative
units or pixel
width Real Specifies the width of the view field in terms of
eye Location Specifies the camera position and orientation
target Location Specifies the target location which should be
centered on the view window
up_vector Location Specifies the upward vector for the view window
to describe inclination
1. A view name is string of characters that identifies a viewport or set of viewport attributes stored in the
database. View_names are assigned by the user when a view is created. After a view has been created,
it may be referenced by its name until it is deleted. A view may not have the same name as another
view. A view_name may be arbitrarily long and a combination of letters of the alphabet and numbers
may be used. The leading character must be a letter.
3. The size of the view window can be specified either in terms of number of pixels. Alternatively, the
size can also be stated as relative to the Adams or custom window.
4. The vertical and horizontal resizing options are used to adjust the placement of the view window on
will place the view window on the top left corner of the Adams or custom window. The location can
5. The size of the view window can be specified with respect to the custom of Adams window size value
the height of the Adams or custom window. Therefore, a value of 1.0 will set the view field window
to be one half as high as the Adams or custom window.
6. The ‘eye’ is similar to a camera position. The eye is specified by its x,y,z coordinates which specifies
the location from where the object is being viewed.
interface view delete
7. The parameter ‘target’ is the location to which is camera is targeted. The ‘target’ is also specified by
its x,y and z coordinates. This location will be positioned at the center of the view window to be
created.
8. The ‘up_vector’ determines the inclination of the of the camera or the upward direction of the model.
For example, setting the up_vector to 0,1000,0, the global y axis will be directed upwards showing
the front view of the object, if the eye is set at 0,0,0. Note that, if the eye is set at 0,0,0 which implies
that the camera is set at oriGIn, it will not capture the object targeted at unless the object is at
sufficient distance in z direction.
9. The camera should be away from the object in the respective axis to view the object – specified by
parameter ‘eye’. The target location appears at the center of the view, thus if you target at the center
of a circular object, the object will be viewed with its center at the middle of the view window. The
inclination of viewing, which is similar to rotating an object, is achieved by setting the up-vector in
coordination with ‘eye’.

Allows you to delete an existing view.
or a separate window. The view can be set-up by parameters like eye, target, and up_vector. The command
displays an existing view.
Format:
Example:
interface view delete &
view_name = .gui.win.user_view
Description:

view_name An Existing View Specifies the name for an existing view
interface 221
interface view display
A new_view_name will replace the name of an existing view.
2. The view can be deleted by this command.

Allows you to display an existing view.
displays an existing view.
Format:
Example:
interface view display &
Description:

2. The view can be displayed by this command.
interface view modify

Allows you to modify an existing view.
helps us to edit the user defined view.
Format:
new_view_name = a new view
enabled = boolean
help_text = string
units = int_units
location = real
height = real
width = real
eye = location
target = location
up_vector = location
Example:
interface view modify &
view_name = .gui.win.user_view &
new_view_name = .gui.win.user_view2 &
enabled = yes &
units = relative &
location = 0.0, 0.0 &
interface 223
interface view modify &

height = .4 &
width = .4 &
eye = 0,0,2500 &
target = 0,0,0 &
up_vector = 0,0,1000
Description:

new_view_name A New View Specifies a new name for an existing view
enabled Boolean Activates the view
units Int_units Specifies the view size as pixel or relative to Adams
or custom window
the view
the view
location Real Specifies the location of the view on the dialog
box
height Real Specifies the height of the view in terms of relative
units or pixel
width Real Specifies the width of the view field in terms of
eye Location Specifies the camera position nad orientation
target Location Specifies the target location which should be
centered on the view window
up_vector Location Specifies the upward vector for the view window
to describe inclination
interface view undisplay
3. The size of the view window can be specified either in terms of number of pixels. Alternatively, the
size can also be stated as relative to the Adams or custom window
4. The vertical and horizontal resizing options are used to adjust the placement of the view window on
will place the view window on the top left corner of the Adams or custom window. The location can
5. The size of the view window can be specified with respect to the custom of Adams window size value
the height of the Adams or custom window. Therefore, a value of 1.0 will set the view field window
to be one half as high as the Adams or custom window.
6. The ‘eye’ is similar to a camera position. The eye is specified by its x,y,z coordinates which specifies
the location from where the object is being viewed.
7. The parameter ‘target’ is the location to which is camera is targeted. The ‘target’ is also specified by
its x,y and z coordinates. This location will be positioned at the center of the view window to be
created.
8. The ‘up_vector’ determines the inclination of the of the camera or the upward direction of the model.
For example, setting the up_vector to 0,1000,0, the global y axis will be directed upwards showing
the front view of the object, if the eye is set at 0,0,0. Note that, if the eye is set at 0,0,0 which implies
that the camera is set at oriGIn, it will not capture the object targeted at unless the object is at
sufficient distance in z direction.
9. The camera should be away from the object in the respective axis to view the object – specified by
parameter ‘eye’. The target location appears at the center of the view, thus if you target at the center
of a circular object, the object will be viewed with its center at the middle of the view window. The
inclination of viewing, which is similar to rotating an object, is achieved by setting the up-vector in
coordination with ‘eye’.

Allows you to close an existing view.
Adams view has some preset views, viz., .gui.main.front, .gui.main.right. The user can create a custom view
with predefined orientation and display specifications, which can be created on the main view window or a
separate window. The view can be set up by parameters like eye, target, and up_vector. The command closes
an existing view.
interface 225
interface window create
Format:
Example:
interface view undisplay &
Description:

1. A view name is a string of characters that identifies a viewport or set of viewport attributes stored in
the database. View_names are assigned by the user when a view is created. After a view has been
created, it may be referenced by its name until it is deleted. A view may not have the same name as
another view. A view_name may be arbitrarily long and a combination of letters of the alphabet and
numbers may be used. The leading character must be a letter.
2. The view can be closed by this command.

Allows creation of a window. Windows and dialog boxes look similar, although they are quite different.
Windows usually stay on the screen for some time as you work in them, while dialog boxes come and go as
you need to enter data or access controls. Windows can contain toolbars and menu bars. Both windows and
dialog boxes contain other interface objects such as buttons, labels, and so on.
Format:
window_name = new_GI_window
enabled = boolean
help_text = String
units = int_units
vert_resizing = int v_resize

location = Real
height = Real
width = Real
title = String
icon_label = String
finish_commands = String
decorate = yes/no
resizable = yes/no
height_maximum = real
grab_all_input = yes/no
Example:
interface window create &
window_name = my_window &
height = 1.0 &
width = 2.0 &
enabled = yes &
help_text = "My first window" &
width_minimum = 250 &
width_maximum = 500 &
title = "My window"
This will create a window having the title “My Window” with height =1.0[Half of the Adams View window)
and width=2.0(Same Width as Adams View window). The minimum width beyond which the user will not
be able to resize would be 250 and the maximum width would be 500. Since there is no height minimum
and maximum specified, the user can resize the window created to any size.
interface 227
Description:

window_name String Specify the name of the new window created.
enabled Yes/no Specify whether the window created will be enabled or
not.
help_text String Specify the string that should be displayed on the Adams
View status bar when the mouse cursor is over the
window created.
documentation_text String Specify the documentation text associated with this
window.
units Relative/Pixel Specify whether the units used for the window
measurements will be in pixels or relative.
horiz_resizing ATTACH_LEFT/ Specify where the horizontal resizing should occur from.
ATTACH_RIGHT
/SCALE_CENTER/
EXPAND/
SCALE_ALL
vert_resizing ATTACH_TOP/ Specify where the vertical resizing should occur from.
ATTACH_BOTTOM
/
SCALE_CENTER/
EXPAND/
SCALE_ALL
location Real The real number should be greater than or equal to zero.
height, Real Specify a height for the info window. The value should be
a real number between 0.0 and 2.0, where 2.0 represents
the height of the Adams View window. Therefore, a value
of 1.0 will set the info window to be one half as high as
the Adams View window.
Width Real Specify a width for the info window. The value should be
a real number between 0.0 and 2.0, where 2.0 represents
the width of the Adams View window. Therefore, a value
of 1.0 will set the info window to be one half as wide as
the Adams View window.
title String This parameter allows the specification of the window
title.
icon_label String Specify the label for the icon.
start_commands String Specify the commands to be executed at the start of the
window creation.
interface window delete

finish_commands String Specify the commands to be executed at the end of the
window creation.
Decorate Yes/No
resizable Yes/No Specify whether this window can be resizable or not.
width_minimum Real Specify the minimum width beyond which the window
should not be allowed to resize.
width_maximum Real Specify the maximum width beyond which the window
should not be allowed to resize
height_minimum Real Specify the minimum height beyond which the window
height_maximum Real Specify the maximum height beyond which the window
grab_all_input Yes/No Default value will be No.
1. The title is a "quoted" character string that will be displayed at the top of the window. The title will
be scaled and centered automatically.
Titles need not be unique.A title may be arbitrarily long and a combination of letters of the alphabet
and numbers may be used.

Interface window delete will delete the specified window.
Format:
Window_name = existing GI_window
Example:
interface window delete &
Window_name = WIN_1
This command will delete the window Win_1

interface 229
interface window display
Description:

Window_name String Specify name of existing GI window to be deleted.

Interface window display will display the specified window on the screen.
Format:
Window_name = existing GI_window
Parameters = string
Example:
interface window display &
Window_name = WIN_1
This command will display the window Win_1
Description:

Window_name String Specify name of existing GI window to be displayed.
Parameters String
interface window modify

Allows modification of a window. Windows and dialog boxes look similar, although they are quite different.
Windows usually stay on the screen for some time as you work in them, while dialog boxes come and go as
you need to enter data or access controls. Windows can contain toolbars and menu bars. Both windows and
dialog boxes contain other interface objects such as buttons, labels, and so on.
Format:
window_name = existing_GI_window
new_window_name = new name for the window
enabled = boolean

help_text = String
units = int_units
vert_resizing = int v_resize
location = Real
height = Real
width = Real
title = String
icon_label = String
finish_commands = String
decorate = yes/no
resizable = yes/no
height_maximum = real
grab_all_input = yes/no
Example:
interface window modify &
window_name = MY_WINDOW &
new_window_name = MODIFIED_WINDOW &
height = 1.0 &
width = 2.0 &
enabled = yes &
help_text = "My first window" &
width_minimum = 250 &
width_maximum = 500 &
title = "My window"
This will modify the window having the title “My Window” with height =1.0 [Half of the Adams View
window) and width=2.0 (Same Width as Adams View window). The minimum width beyond which the user
will not be able to resize would be 250 and the maximum width would be 500. Since there is no height
minimum and maximum specified, the user can resize the window created to any size.
Description:

window_name String Specify the name of the new window created.
enabled Yes/no Specify whether the window created will be enabled or
not.
help_text String Specify the string that should be displayed on the
Adams View status bar when the mouse cursor is over
the window created.
documentation_text String Specify the documentation text associated with this
window.
units Relative/Pixel Specify whether the units used for the window
measurements will be in pixels or relative.
horiz_resizing, ATTACH_LEFT/ Specify where the horizontal resizing should occur
ATTACH_RIGHT/ from.
SCALE_CENTER/
EXPAND/ SCALE_ALL
vert_resizing ATTACH_TOP/ Specify where the vertical resizing should occur from.
ATTACH_BOTTOM/
SCALE_CENTER/
EXPAND/SCALE_ALL
location Real The real number should be greater than or equal to
zero.
height Real Specify a height for the info window. The value should
be a real number between 0.0 and 2.0, where 2.0
represents the height of the Adams View window.
Therefore, a value of 1.0 will set the info window to be
Width Real Specify a width for the info window. The value should
be a real number between 0.0 and 2.0, where 2.0
represents the width of the Adams View window.
Therefore, a value of 1.0 will set the info window to be
one half as wide as the Adams View window.
title String This parameter allows the specification of the window
title.
icon_label String Specify the label for the icon.
start_commands String Specify the commands to be executed at the start of the
window creation.
finish_commands String Specify the commands to be executed at the end of the
window creation.
interface window undisplay

Decorate Yes/No
resizable Yes/No Specify whether this window can be resizable or not.
width_minimum Real Specify the minimum width beyond which the
window should not be allowed to resize.
width_maximum Real Specify the maximum width beyond which the
window should not be allowed to resize
height_minimum Real Specify the minimum height beyond which the
height_maximum Real Specify the maximum height beyond which the
grab_all_input Yes/No Default value will be No.
1. The title is a "quoted" character string that will be displayed at the top of the window. The title will
be scaled and centered automatically.
Titles need not be unique.A title may be arbitrarily long and a combination of letters of the alphabet
and numbers may be used.

Allows closing of an existing window
The interface window created can be closed by using this command.
Format:
window_name = an existing GI_window
Example:
interface window undisplay &
window_name = .gui.win

Window_name String Specify name of existing GI window to be undisplayed.
Parameters String
interface write
interface write
Allows the writing a set of commands for creating a GUI.
The graphic user interface (gui) is created with a set of commands. The GUI may be a window or a dialog
box created. The set of commands used to create the GUI are written to a file using the ‘write’ command.
Format:
interface write
gui_name = an existing GI_gui
file_name = string
Example:
interface write &
gui_name = .gui.dbox &
file_name = "c:/gui_text.txt"
Description:

gui_name An Existing GI_gui Specify the name of GUI for which the commands are written.
file_name String Specifies the a remote file address to which the commands are to be
written.
1. Any GUI, for example, a toolbar, window, dialog box and so on, created using a set of commands.
These commands can be written to a file, where the file_name specifies the name of the file that is to
be read, written, or executed. The proper extension is 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.
interface write
library 1
library copy
library
library copy
Allows you to copy an existing library.
The command allows copying an existing library to a new library.
Format:
library copy
library_name = an existing library
new_library_name = a new library
Example:
library copy &
library_name = .MDI.image &
new_library_name = new_images
Description:

library_name An Existing Library Specifies the name of an existing library
new_library_name A New Library Specifies a new name for the copied library
The existing library can be copied to a new library by this command, by specifying the ‘library_name’ and
the ‘new_library_name’.
library create
Allows you to create a new library.
The command allows creation of a new library in the database.
Format:
library create
library_name = a new library
library delete
Example:
library create &
library_name = .materials.LIBRARY1
Description:

library_name A New Library Specifies the name of a new library
A new library can be created by using the command, ‘library create’.
library delete
Allows you to delete an existing library.
The command allows deletion of an existing library.
Format:
library delete
Example:
library delete &
library_name = new_images
Description:

The existing library can be deleted by using the command, and specifying the ‘library_name’.
library modify
Allows you to modify an existing library.
The command allows modifying an existing library to a new library.
library 3
library modify
Format:
library modify
new_library_name = a new library
Example:
library modify &
library_name = .materials.LIBRARY1 &
new_library_name = library2
Description:

new_library_name A New Library Specifies a new name for the existing library
The existing library can be modified to a new library by this command, by specifying the ‘library_name’ and
the ‘new_library_name’.
library modify
list_info 1
list_info aggregate_mass
list_info
Computes the total mass and inertia properties of the requested parts.
Format:
part_names = existing body
relative_to = existing model/part/marker
brief = on/off
write_to_terminal = on/off
file_name = string
Example:
list_info aggregate_mass &
brief = on &
write_to_terminal = off &
file_name = “c:\AView\model_info.txt”
This will display the mass and inertia properties of the model in the file model_info.txt.
Description:

part_names Existing body Specifies the names of the parts to be included in
the aggregate mass calculation.
model_name Existing model Specifies the name of the model to be included in
the aggregate mass calculation.
to.
list_info analysis

brief On/off Specifies whether to use the brief form (default) or
an extended form of the requested information to
be displayed.
write_to_terminal On/off Specify if the information requested is to be sent to
the informational window or not.
file_name String Specify that the information requested is to be sent
to a file with the name specified with the
parameter.
Cautions:
1. The ground part, and any part with zero mass will be ignored.
list_info analysis
Specifies information about the analysis within the model such as the result set, graphics file, result file,
request file, parent etc.
Format:
list_info analysis
brief = on/off
file_name = string
Example:
list_info analysis &
brief = on
If no parameters are specified, the above command will display brief information about all the analysis
existing within the current model. If brief was turned off then it would display the details of all the steps of
the internal solver.
Object Name : .model_1.Last_Run
Object Type : Analysis
list_info 3
list_info constraint
Parent Type : Model

TITLE : 'None'
DATE : 2006-07-10 14:15:26
GRAPHICS FILE : ''
RESULTS FILE : ''
REQUEST FILE : ''
Result_Set:
PART_2_XFORM ADAMS ID: None TYPE: Result_Set
PART_3_XFORM ADAMS ID: None TYPE: Result_Set
JOINT_1 ADAMS ID: None TYPE: Result_Set
JOINT_2 ADAMS ID: None TYPE: Result_Set
Description:

Femdata_name Existing femdata Specify an existing femdata name
Brief On/off Specify whether the information needs to be specified
in brief or not.If brief is turned off, it will display the
details of all the steps in the internal solver.
Write_to_terminal On/off Specify whether writing the information to the terminal
is necessary.
File_name String Specify a location and name of file to which the
information needs to be written.
Tips:
1. Typing ? after file_name parameter will open the browse window in Windows platform making it
easier to specify the file to which the information would be written into.
lists information about the current state of the constraint in the system.
Format:
gear_name = existing gear name
coupler_name = existing coupler name
jprim_name = existing jprim name
point_curve_name = existing point_curve name
curve_curve_name = existing curve curve name
motion_name = existing motion name
user_constraint_name = existing user constraint name
brief = on/off
file_name = String
Example:
list_info constraint &
point_curve_name = PTCV_1 &
brief = off
This command will display the detailed information about the specified joint and the point curve and its
dependants on the screen in the information dialog window .
Description:

constraint_name Existing constraint name Specify an existing constraint name.
brief Yes/No Specify whether you want the marker information
in brief or not.
joint_name Existing joint name Specify an existing joint name
gear_name Existing gear name Specify an existing gear name
coupler_name Existing coupler name Specify an existing coupler name.
jprim_name Existing jprim Specify an existing jprim name
point_curve_name Existing point curve name Specify an existing point curve name.
curve_curve_name Existing curve curve name Specify an existing curve name.
motion_name Existing motion name Specify an existing motion name
user_constraint_name Existing user constraint Specify an existing user constraint name.
name
write_to_terminal Yes/No Specify whether you want the constraint
information to be displayed on the terminal.
file_name String Specify filename in which you want to save the
constraint information.
list_info 5
list_info curves
1. If the parameter “Brief” is turned on then only the information about the constraint is displayed such
as location and orientation without specifying the information on the dependants. If “Brief” is turned
off then the information about the dependents is also displayed.
Caution:
1. The directory which you specify the file_name should exist. If it does not then the constraint
information will not be copied into the specified filename.
Tips:
1. To specify file_name parameter, typing “?” after the “file_name=” will open the Browse window using
which the required filename can be specified.
2. The information in list_info constraint can be sent to the information window, a file, or both.
list_info curves
Format:
list_info curves
curve_name = existing plot curve name
brief = on/off
file_name = string
Example:
list_info curves &
Brief = on
If no parameters are specified, the above command will display brief information about all the plot curve
names existing within the current model.
Description:

Curve_name Existing plot curve name Specify an existing plot curve name.
list_info data_element

Brief On/off Specify whether the information needs to be
specified in brief or not.
Write_to_terminal On/off Specify whether writing the information to the
terminal is necessary.
Tips:
Format:
data_element_name = existing data element name
curve_name = existing curve name
spline_name = existing spline name
variable_name = existing variable name
array_name = existing array name
matrix_name = existing matrix name
plant_input_name = existing plant input
plant_output_name = existing plant output
plant_state_name = existing plant state name
string_name = existing ADAMS string name
brief = on/off
file_name = String
Example:
list_info data_element &
Curve_name = curve_1 &
Write_to_terminal = off &
list_info 7
list_info defaults
list_info data_element &

File_name = “c:\temp.txt” &
Brief = on
The above statements will write the brief information about the curve data element in the file specified. The
information window will not be displayed on the terminal as the write_to_terminal parameter is turned off.
Description:

data_element_name Existing data element name Specify an existing data element.
curve_name Existing curve name Specify an existing curve name
spline_name Existing spline name Specify an existing spline name
variable_name Existing Adams variable Specify an existing variable name
array_name Existing Adams array name Specify an existing array name
matrix_name Existing matrix name Specify an existing matrix name
plant_input_name Existing plant input name Specify an existing plant input name
plant_output_name Existing plant output name Specify an existing plant output name
plant_state_name Existing plant state name Specify an existing plant state name
string_name Existing string name Specify an existing string name
brief On/off Specifies whether the information
required is brief or not.
write_to_terminal On/Off Specifies whether the information has to
be displayed on the terminal.
file_name String Specify filename into which the
information should be written into
list_info defaults
The LIST_INFO DEFAULTS command is used to list information about the current settings of the systems
defaults. The information can be sent to the information window, a file, or both.
Format:
list_info defaults
brief = on/off
file_name = string specifying the file path
list_info eigen_values
Example:
list_info defaults &
brief = on &
file_name = "C:\info.txt"
Description:

brief ON_OFF Specifies whether to use the brief form (default) or an
extended form of the requested information to be displayed.
write_to_terminal ON_OFF Specify if the information requested is to be sent to the
informational window or not.
file_name STRING Specify that the information requested is to be sent to a file
with the name specified with the parameter.
1. The ‘write_to_terminal’ parameter is most likely be used in conjunction with the FILE_NAME
parameter to get the information put to a file only.
List information about all the eigen solution's predicted eigenvalues. You may instruct Adams View to print
this information to the "Info Window" or to a file or both.
Format:
brief = on/off
Example:
list_info eigen_values &
eigen_solution_name = eigen_1 &
brief = on &
list_info 9
Description:

eigen_solution_name AN EXISTING Specifies an existing eigen_solution.
EIGEN
extended form of the requested information to be
displayed.
1. The information includes:
• MODE_NUMBER -the sequential number of the mode that was predicted by the eigen
solution.
• FREQUENCY -the natural frequency corresponding to the mode (that is, the eigenvalue)
• DAMPING -the damping ratio for the mode (the log decrement is another way to represent
this quantity).
• EIGENVALUES -list the real and imaginary part of the eigenvalue.
2. You may identify a eigen_solution by typing its name. Specifies an EIGEN_SOLUTION in a
existing analysis. If an eigen_solution is available by default, you may identify it by entering its name
only. The EIGEN_SOLUTION must be in an existing analysis that is associated to an existing
model. Therefore, any reference to the EIGEN_SOLUTION can include the model and analysis
name. For example, assume you have read a result file called "SECOND_GEAR.RES", and this result
file contains the analysis "SECOND_GEAR". If you wish to refer to the EIGEN_SOLUTION
named "EIG1" for the model "TRANSMISSION", enter
.TRANSMISSION.SECOND_GEAR.EIG1 (the .TRANSMISSION.SECOND_GEAR. may be
omitted if SECOND_GEAR is the current default analysis_name). SECOND_GEAR refers to the
analysis name that the result set came from (or is stored under). The eigen_solution name begins with
the letters EIG and ends with the eigen_solution ID number. You must separate multiple
eigen_solution names by commas. If the eigen_solution is visible in one of your views, you may
identify it by picking on any of the graphics associated with it.
Tips:
1. If you type a "?", Adams View will list the eigen_solutions available by default.
list_info entity
list_info entity
Lists information about the variables’s in the current model.
Format:
list_info entity
Entity_name = Existing entity name
Type_filter = Object type
Brief = on/off
Write_to_terminal = on/off
File_name = string
Example:
list_info entity &
entity_name = MACRO_1
type_filter = macro
brief = off
write_to_terminal = on
file_name = "C:\Documents and Settings\aview\My Documents\my_file"
This will display the following information on the terminal as well as in the file “my_file”,
Object Name : .MACRO_1
Object Type : Macro
User Command : None specified, using the macro name
'MACRO_1'
Wrap in Undo : No
Help : None specified
Commands :
! $FIRST_MARKER: T=marker
! $SECOND_MARKER: T=marker
! $NEW_MARKER_NAME: T=new_marker
!
marker create marker_name=$NEW_MARKER_NAME &
location = (( ($FIRST_MARKER.loc_x)+($SECOND_MARKER.loc_x)
)/2 ), &
(( ($FIRST_MARKER.loc_y)+($SECOND_MARKER.loc_y) )/2 ), &
(( ($FIRST_MARKER.loc_z)+($SECOND_MARKER.loc_z) )/2 ) &
orientation = 0,0,0 &
If brief is turned on then the dependant information will not be displayed.
list_info 11
list_info executive_control equilibrium_parameters
Description:

Entity_name Existing entity name Specify an existing entity whose information has to
be listed. This entity could be a macro, gui , icons,
plots, models etc.
Type_filter Object type Specify an object type to be used as a filter. All
entities of this object type will be displayed in the
information dialog box.
Brief On/off Specify whether the variable information required
is in brief or not.
Write_to_terminal On/off Specify whether the information has to be
displayed on the terminal.
File_name String Specify filename in which the information needs to
be written.
Tips:
1. Typing “?” after “file_name=” parameter will open the file browse window in Windows environment,
making it easier to specify the file name.

Format:
model_name = existing model name
brief = on/off
file_name = string
Example:
Without specifying any parameters, the command above will display the following:
Equilibrium Analysis Settings For Model: .MODEL_2
Dynamic : No
Alimit : 10.0 deg
Error : 1.0E-004
Imbalance : 1.0E-004 newton
Maxit : 25
Pattern For Jacobian : Yes, Yes, Yes, Yes, Yes, Yes, Yes, Yes, Yes, Yes
list_info executive_control initial_conditions_parameters
Stability : 1.0E-005
Tlimit : 20.0
Global Damping : 0.0
Max Settling Time : 100.0 sec
Acceleration Error : 2.0E-002
Kinetic Energy Error : 2.0E-002
Static Method : Original
It will take the default model open as the argument and shows the equilibrium parameters for that.
Description:

Model_name Existing model Specify an existing model name
Brief On/off Specify whether the information needs to be specified in brief
or not.
Write_to_terminal On/off Specify whether writing the information to the terminal is
necessary.
File_name String Specify a location and name of file to which the information
needs to be written.
Tips:

Allows you to print out information on the parameters which control the ADAMS initial conditions analysis.
You may instruct Adams View to print this information to the "Info Window" or to a file.
Format:
model_name = an existing model name
brief = on/off
list_info 13
Example:
list_info executive_control initial_conditions_parameters &
brief = on &
Description:

model_name AN EXISTING Specifies an existing model.
MODEL
1. Initial conditions parameters include error tolerances and other parameters that control the initial
conditions analysis.
2. You would set these parameters only when requesting a dynamic, static equilibrium, or quasi-static
equilibrium analysis, and wish to change one or more of the tolerances for the initial conditions
analysis.
3. ADAMS automatically does an initial conditions analysis. An initial conditions analysis is not
necessary when the system has zero degrees of freedom because, in that case the kinematics of the
system fully determine its configuration.
4. The initial conditions analysis ensures that the system satisfies all constraints within the system. If
necessary ADAMS moves parts until both parts of each joint are in contact. This analysis involves
three separate phases. First, ADAMS makes the displacements between all parts and all joints in the
system physically consistent. This requires the use of Newton-Raphson iteration to solve a set of
nonlinear algebraic equations. Once the displacements are consistent, ADAMS makes the velocities
physically consistent. Because this requires solving a set of linear equations, iteration is not necessary.
Finally, ADAMS calculates consistent accelerations and forces. This solution also requires solving a
set of linear equations.
list_info executive_control integrator_parameters
in one of your views, you may identify it by picking on any of the graphics associated with it. You
need not separate multiple model picks by commas.
Tips:
associated with it.

displays the information on the integrator parameters such as integrator type, formulation, jacobian pattern,
etc.
Format:
brief = on/off
file_name = string
Example:
Numerical Integration Settings For Model: .MODEL_2

Integrator Type : gstiff
Formulation : i3
Error Tolerance : 1.0E-003
Pattern For Jacobian : Yes, No, No, No, Yes, No, No, No, Yes, No
Maxit Corrector Iterations : 10
Hinit Time Step : 0.0 sec
Hmin Time Step : 0.0 sec
Hmax Time Step : 0.0 sec
Adaptivity : 0.0
Scale : 1.0, 1.0, 1.0E-003, 1.0, 1.0
KMax Integrator Order : 12
Interpolate : No
Reconcile : all
Repartition Threshold : 1.0E-002, 1.0E+012
Corrector : original
Alpha : -0.3
list_info 15
list_info executive_control kinematics_parameters
Beta : 0.36
Gamma : 0.7
It will take the default model open as the argument and show the equilibrium parameters for that.
Description:

Tips:

Allows you to print out information on the current values of the parameter which control an ADAMS
kinematic analysis. You may instruct Adams View to print this information to the "Info Window" or to a file.
Format:
brief = on/off
Example:
list_info executive_control kinematics_parameters &
brief = on &
list_info executive_control numeric_integration_parameters
Description:

MODEL
1. Kinematics parameters include error tolerances and other parameters for kinematic analyses. You
would set these parameters only when you are requesting a kinematic analysis and you want to change
one or more of the tolerances and parameters from the default values. A kinematic analysis is only
appropriate when a system has zero degrees of freedom. A kinematic analysis solves for the
displacements, velocities, accelerations, and forces (if any) at a series of points in time.
2. To find the displacements, ADAMS uses Newton-Raphson iteration to solve a nonlinear set of
algebraic equations. After finding the displacements, ADAMS solves linear equations without
iteration to find the velocities, accelerations, and forces. ADAMS repeats this procedure at
successively later times until it obtains results over the period of time specified in the ADAMS
SIMULATE command.
list_info executive_control
numeric_integration_parameters
Format:
brief = on/off
list_info 17
list_info executive_control sensor

file_name = string
Description:

Tips:

The LIST_INFO SENSOR command is used to list information about a sensor. The information can be sent
to the information window, a file, or both.
Format:
brief = on/off
Example:
list_info executive_control sensor &
brief = on &
list_info executive_control solver_parameters
Description:

MODEL
displayed.
Tips:
associated with it.

Allows you to print out information about the what integrator will be used when you submit an analysis from
Adams View.
Format:
brief = on/off
list_info 19
list_info files
Example:
list_info executive_control solver_parameters &
brief = on &
Description:

MODEL
brief ON_OFF Specifies whether to use the brief form (default) or an extended
form of the requested information to be displayed.
file_name STRING Specify that the information requested is to be sent to a file with
the name specified with the parameter.
1. You can select between the harwell and calahan integration solvers in ADAMS. This selection is made
on a model by model basis. Therefore, each time you submit the model the chosen solver will be used
until this command is used to select the alternative. For a complete description of these solvers see the
ADAMS documentation.
Tips:
associated with it.
list_info files
List information about the ADAMS files that have been read. It does not list the command files or the user
data files.
list_info files
Format:
list_info files
graphics_file = an existing analysis
request_file = an existing analysis
results_file = an existing analysis
brief = on/off
Example:
list_info files &
graphics_file = Last_Run &
request_file = Last_Run &
results_file = Last_Run &
brief = on &
Description:

analysis_name AN EXISTING Specifies an existing model.
ANALYSIS
graphics_file AN EXISTING The GRAPHICS keyword indicates that the file to be read
ANALYSIS into Adams View is a graphics file (The default file extension
is .GRA) that has been generated by ADAMS.
request_file AN EXISTING The REQUEST keyword indicates that the file to be read
ANALYSIS into Adams View is a request file (.REQ) that has been
generated by ADAMS
results_file AN EXISTING The RESULTS keyword indicates that the file to be read
ANALYSIS into Adams View is a results file (.RES) that has been
generated by ADAMS.
list_info 21
list_info files

• name: the name of the file specified on the file read command, minus the path and extension.
• type: request, results, or graphics steps the number of time steps
• date: the internal time stamp placed in the file by ADAMS corresponding to when the file was
created.
• title: the internal title placed in the file by ADAMS
An analysis may be picked from the screen if you have read an ADAMS Graphics file, and use the
type the name. You may also find it convenient to type the name even if the analysis is displayed. You
may have explicitly named the analysis when you created it by reading one or more ADAMS output
files. By default, the name of the analysis is the root name of the ADAMS output files. If you created
the analysis by reading an ADAMS Graphics file, for instance, the analysis name is
the name of the graphics file without the '.gra' extension. You must separate multiple analysis names
by commas. If the analysis is visible in one of your views, you may identify it by picking on any of the
graphics associated with it. You need not separate multiple analysis picks by commas.
3. When a graphics file is read by Adams View a new analysis run is created and the information found
in the graphics file is stored under the analysis run name. The default name of the analysis run will
be the name of the graphics file excluding the extension.
4. When a request file is read by Adams View a new analysis run is created. Each block of data in the
request file that corresponds to a REQUEST statement in the ADAMS input data is stored as result
set in the analysis run. The default name of the analysis run will be the name of the request file
excluding the extension. This defaults analysis name can be overridden using the file_name
parameter. The the name of each result set will be "req" with the request statement ID appended to
it. For example, REQUEST/1508 would produce a result set name of "req1508".
5. When a results file is read by Adams View a new analysis run is created. Each block of data in the
results file corresponds to an ADAMS entity like PART JOINT,
list_info force
BUSHING, etc. The data corresponding to these entities is stored as result set in the analysis run.
The default name of the analysis run will be the name of the results file excluding the extension. This
defaults analysis name can be overridden using the file_name parameter. The the name of each result
set will be the first three letters of the entity name with the entity statement ID number appended to
it. For example, PART/101 would produce a result set name of "par101".
Tips:
1. You may get a list of analysis by typing a "?" in response to a parameter that requires an analysis name
be entered.
list_info force
This command is used to display information about the force on the terminal or in a file.
Format:
list_info force
force_name = existing force name
single_component_force_name = existing single component force name
force_vector_name = existing force vector name
torque_vector_name = existing torque vector name
general_force_name = existing general force name
multi_point_force_name = existing multi_point force
gravity_field_name = existing gravity field
beam_name = existing beam name
bushing_name = existing bushing name
field_name = existing field name
spring_damper_name = existing spring damper name,
brief = on/off
file_name = string
Example:
list_info force &
force_name = SFORCE_1 &
list_info 23
list_info force
list_info force &

brief = on &
The following will be displayed on the information window:

Object Name : .model_1.SFORCE_1
Object Type : Single_Component_Force
Parent Type : Model
Adams ID : 1
Active : NO_OPINION
I Marker : .model_1.PART_6.MARKER_16
J Marker : .model_1.ground.MARKER_17
Length : None
Mode : Translational
Actiononly : TRUE
Function : 2.7
Description:

force_name Existing force name Specify an existing force name
single_component_force_name Existing single Specify an existing single component force
component force
force_vector_name Existing force vector Specify an existing force vector
torque_vector_name Existing torque vector Specify an existing torque vector
general_force_name Existing general force Specify an existing general force
multi_point_force_name Existing multi point Specify an existing multi point force
force
gravity_field_name Existing gravity field Specify an existing gravity field
beam_name Existing beam name Specify an existing beam name
bushing_name Existing bushing name Specify an existing bushing name
field_name Existing field name Specify an existing field name
spring_damper_name Existing spring damper Specify an existing spring damper
brief On/off Specify whether the information is required
in brief or not.
write_to_terminal On/off Specify whether the information has to be
displayed on the terminal
file_name String Specify the name of the filename to which the
information should be written to.
list_info geometry
1. If the parameter brief is turned on then only the information about the force is displayed without
specifying the information on the I and the J marker. If brief is turned off then the information about
the I and J marker is also displayed.
Caution:
1. The directory which you specify the file_name should exist. If it does not then the constraint
information will not be copied into the specified filename.
list_info geometry
Will display information about the geometry. This information can be displayed either on the terminal or in
a file or both.
Format:
list_info geometry
geometry_name = existing geometry_name
arc_name = existing arc_name
block_name = existing block_name
circle_name = existing circle_name
cylinder_name = existing cylinder_name
frustum_name = existing frustrum name
force_name = existing force_name
outline_name = existing outline_name
polyline_name = existing polyline_name
spring_damper_name = existing spring_damper name
gstring_name = existing gstring name
ellipsoid_name = existing ellipsoid name
torus_name = existing torus name
revolution_name = existing revolution name
extrusion_name = existing extrusion name
plane_name = existing plane name
brief = on/off
file_name = string
list_info 25
list_info geometry
Example:
list_info geometry &
Geometry_name = LINK_1 &
Brief = off &
Write_to_terminal = on &
File_name = ” c:\geometry_info.txt”
This will display information about the Link geometry as shown below on the terminal as well as the file
“c:\geometry_info.txt”
Object Name : .model_1.PART_5.LINK_4

Object Type : Link
Parent Type : Part
J Marker : .model_1.PART_5.MARKER_6
Length : 282.8427124746 mm
Width : 28.2842712475 (28.2842712475mm) mm
Depth : 14.1421356237 (14.1421356237mm) mm
Local :
Location : -50.0, 50.0, 0.0 (mm, mm, mm)
Orientation : 315.0, 0.0, 0.0 (deg)
Global :
Location : -50.0, 50.0, 0.0 (mm, mm, mm)
J Marker : .model_1.PART_5.MARKER_6
Local :
Location : 150.0, -150.0, 0.0 (mm, mm, mm)
Global :
Location : 150.0, -150.0, 0.0 (mm, mm, mm)
Comments : None
Attributes: Value: Inherited: From:

Active NO_OPINION
Colors
Line WHITE.......CYAN.........model_1.PART_5
Edge RED.........CYAN.........model_1.PART_5
Face WHITE.......CYAN.........model_1.PART_5
Text WHITE.......CYAN.........model_1.PART_5
Visibility NO_OPINION
Name Visibility NO_OPINION..OFF..........model_1.PART_5
Render FILLED
list_info geometry

geometry_name Existing geometry name Specify name of existing geometry.
arc_name Existing arc name Specify name of existing arc.
block_name Existing block name Specify name of existing block name
circle_name Existing circle name Specify name of circle name
cylinder_name Existing cylinder name Specify name of cylinder name
frustum_name Existing frustrum name Specify name of frustrum name
force_name Existing force name Specify name of force name
outline_name Existing outline name Specify name of outline name
polyline_name Existing polyline name Specify name of polyline name
spring_damper_name Existing spring damper Specify name of spring damper name
name
gstring_name Existing gstring name Specify name of gstring name
ellipsoid_name Existing ellipsoid name Specify name of ellipsoid name
torus_name Existing torus name Specify name of torus name
revolution_name Existing revolution name Specify name of revolution name
extrusion_name Existing extrusion name Specify name of extrusion name
plane_name Existing plane name Specify name of plane name
brief On/off Specify whether the information has to be
displayed in brief.
write_to_terminal On/off Specify whether the information has to be
displayed on the terminal.
file_name String Specify name of filename in which the
information has to be written into.
1. If the parameter “brief” = ON, then the information of the dependants of the geometry will not be
displayed. If brief is OFF then the information of the geometry as well as its dependants is displayed.
Tips:
1. IF no parameters are specified to the list_info geometry command, it will display the information of
all the geometry objects in the current model.
2. On typing ? after the “file_name =”, the file browse window will appear allowing the file to be
specified.
list_info 27
list_info group
list_info group
Lists information about the groups in the current model.
Format:
list_info group
group_name = Existing group name
Brief = on/off
File_name = string
Example:
list_info group &
group_name = GROUP_1 &
brief = off &
write_to_terminal = on &
file_name = "C:\My Documents\my_file"
Object Name : .model_1.GROUP1
Object Type : Group
Parent Type : Model
Objects :
PART_2 (Part)
PART_3 (Part)
Object Name : .SELECT_LIST

Object Type : Group
Objects :
MARKER_8 (Marker)
MARKER_8 above was displayed because the parameter “brief ” was turned OFF and MARKER_8 was a
dependant on the part in the group. If brief is turned on then the dependant information will not be
displayed.
list_info linear_mode_shapes
Description:

Group_name Existing group name Specify an existing group whose information has to be
listed.
Brief On/off Specify whether the group information required is in
brief or not.
Write_to_terminal On/off Specify whether the information has to be displayed on
the terminal.
File_name String Specify filename in which the information needs to be
written.
Tips:
List the mode shapes for the model's bodies and equations for a linear analysis made during the simulation.
Format:
accuracy = integer
normalize = on/off
brief = on/off
Example:
list_info linear_mode_shapes &
eigen_solution_name = eigen_1 &
accuracy = 10 &
normalize = off &
brief = on &
list_info 29
list_info macro
Description:

eigen_solution_name AN EXISTING Specifies an existing eigen_solution.
EIGEN
accuracy INTEGER Specify number of digits after the decimal point.
normalize ON_OFF Specifies whether to use the normalize procedure on mode
shapes.
1. The object type and ID number of all the objects in the mode shape are given, followed by the
coordinates of the object's mode shape, labeled with the coordinate's name.
2. You may identify a eigen_solution by typing its name. Specifies an EIGEN_SOLUTION in a
existing analysis. If an eigen_solution is available by default, you may identify it by entering its name
only. The EIGEN_SOLUTION must be in an existing analysis that is associated to an existing
model. Therefore, any reference to the EIGEN_SOLUTION can include the model and analysis
name. For example, assume you have read a result file called "SECOND_GEAR.RES", and this result
file contains the analysis "SECOND_GEAR". If you wish to refer to the EIGEN_SOLUTION
named "EIG1" for the model "TRANSMISSION", enter
.TRANSMISSION.SECOND_GEAR.EIG1 (the .TRANSMISSION.SECOND_GEAR. may be
omitted if SECOND_GEAR is the current default analysis_name). SECOND_GEAR refers to the
analysis name that the result set came from (or is stored under).
Tips:
1. If you type a "?", Adams View will list the eigen_solutions available by default.
list_info macro
Lists information about the macro’s in the current model.
list_info macro
Format:
list_info macro
Macro_name = Existing macro
Brief = on/off
File_name = string
Example:
list_info macro &
macro_name = MACRO_1 &
brief = off &
Object Name : .MACRO_1
Object Type : Macro
User Command : None specified, using the macro name
'MACRO_1'
Wrap in Undo : No
Help : None specified
Commands :
! $FIRST_MARKER: T=marker
! $SECOND_MARKER: T=marker
! $NEW_MARKER_NAME: T=new_marker
!
marker create marker_name=$NEW_MARKER_NAME &
location = (( ($FIRST_MARKER.loc_x)+($SECOND_MARKER.loc_x) )/2 ), &
(( ($FIRST_MARKER.loc_y)+($SECOND_MARKER.loc_y) )/2 ), &
(( ($FIRST_MARKER.loc_z)+($SECOND_MARKER.loc_z) )/2 ) &
list_info 31
list_info marker
Description:

Macro_name Existing macro name Specify an existing macro whose information has to be
listed.
Brief On/off Specify whether the macro information required is in
brief or not.
Write_to_terminal On/off Specify whether the information has to be displayed on
the terminal.
written.
Tips:
list_info marker
lists information about the current state of the markers in the system.
Format:
list_info marker
marker_name = existing_marker
brief = on/off
file_name = string
Example:
:
list_info marker &

Marker_name = MARKER_1 &
Brief = on &
Write_to_terminal = off &
File_name = “c:\info\information”
This command will give the brief information about the marker_1 in the file specified.
Object Name : .model_1.PART_2.MARKER_1

Object Type : Marker
Parent Type : Part
list_info marker
Adams ID : 1
Active : NO_OPINION
Local :
Location : -500.0, 300.0, 0.0 (mm, mm, mm)
Global :
Location : -500.0, 300.0, 0.0 (mm, mm, mm)
If the Write_to_terminal parameter is turned on then the marker information is displayed on the terminal as
well.
Description:

marker_name Existing marker Specify the marker name you want information to
be displayed about.
brief Yes/No Specify whether you want the marker information
in brief or not.
write_to_terminal Yes/No Specify whether you want the marker information
to be displayed on the terminal.
file_name String Specify filename in which you want to save the
marker information.
1. If the parameter “Brief” is turned on then only the information about the marker is displayed such as
location and orientation without specifying the information on the markers dependants. If “Brief” is
turned off then the information about the marker dependents is also displayed.
Example of list_info marker with Brief = on
Parent Type : Part
Adams ID : 1
Active : NO_OPINION
Local :
Location : -500.0, 300.0, 0.0 (mm, mm, mm)
Global :
Location : -500.0, 300.0, 0.0 (mm, mm, mm)
Example of list_info marker with Brief=off
Parent Type : Part
Adams ID : 1
Active : NO_OPINION
list_info 33
list_info measure
Local :
Location : -500.0, 300.0, 0.0 (mm, mm, mm)
Global :
Location : -500.0, 300.0, 0.0 (mm, mm, mm)
Marker's Dependents:
LINK_1 ADAMS ID: 0 TYPE: Link
Comments : None
Attributes: Value: Inherited: From:

Active NO_OPINION
Colors
Line WHITE.......RED..........model_1.PART_2
Edge RED.........RED..........model_1.PART_2
Face WHITE.......RED..........model_1.PART_2
Text WHITE.......RED..........model_1.PART_2
Visibility NO_OPINION
Name Visibility NO_OPINION..OFF..........model_1.PART_2
Icon Size 50.0
Caution:
1. The directory which you specify the file_name should exist. If it does not then the marker information
will not be copied into the specified filename.
Tips:
1. To specify file_name parameter, typing “?” after the “file_name=” will open the Browse window using
which the required filename can be specified.
2. The information in list_info marker can be sent to the information window, a file, or both.
list_info measure
List the distance between a marker and ground, or between two markers. The distance can be listed relative
to ground or a third marker.
The magnitude, X component, Y component, and the Z component are listed.
If the J_MARKER_NAME parameter is specified, the distance will be between the I and the J marker,
otherwise the distance will be from the I marker to ground.
If the R_MARKER_NAME parameter is specified the data will be relative to it, otherwise the data will be
relative to ground.
Because the location of the markers is time dependent, you can specify the time, frame_number, or
configuration of the model that the measurements are to be taken.
The information can be sent to the information window, a file, or both.
list_info measure
Format:
list_info measure
r_marker_name = existing marker
Configuration = display_frame
time = real
brief = on/off
file_name = string
Example:
list_info measure &
j_marker_name = MARKER_6 &
brief = off
This will measure the distance between MARKER_5 and MARKER_6 relative to the ground. The following
information will be displayed in the information window.
Measurements for the model:.model_1
The distance between MARKER_5 and MARKER_6 is:
MAG = 492.4428900898 mm
X = -200.0 mm
Y = 450.0 mm
Z = 0.0 mm
The angular offsets between MARKER_5 and MARKER_6 are:
ANG1 = 0.0 deg
ANG2 = 0.0 deg
ANG3 = 0.0 deg
list_info 35
list_info measure
Description:

i_marker_name Existing marker To specify the first of a pair of markers that will be
involved in the distance calculation.
j_marker_name Existing marker To specify the second of a pair of markers that will be
involved in the distance calculation.
r_marker_name Existing marker To specify a marker the distance calculation is to be
relative to.
model_name Existing model Specifies an existing model.
analysis_name Existing analysis name Specifies an existing analysis.
configuration MODEL_INPUT/EQUI This parameter is used to specify what output frame, or
LIBRIUM/ FORWARD/ output time step, of the simulation results is to be
BACKWARD displayed for the single_frame_display command.
Time Real The TIME parameter allows you to identify which
frame number (ADAMS simulation output time step)
at which to configure the model in the
SINGLE_FRAME_DISPLAY command.
frame_number integer To specify the frame number (ADAMS simulation
output time step) at which to configure a model during
the single_frame_display command.
brief On/off Specifies whether to use the brief form (default) or an
displayed.
write_to_terminal On/off Specify if the information requested is to be sent to the
file_name String Specify that the information requested is to be sent to a
file with the name specified with the parameter.
1. The I_MARKER_NAME parameter is used with the LIST_INFO MEASURE command to list the
distance between two markers. The I_MARKER_NAME is the marker that the measurement is
from.
The I_MARKER_NAME parameter is a required parameter and a legal marker name must be
entered.
It Specifies an existing marker.
2. The J_MARKER_NAME parameter is used with the LIST_INFO MEASURE command to list the
distance between two markers. The J_MARKER_NAME is the marker that the measurement is "to".
list_info measure
The J_MARKER_NAME parameter is a required parameter and a legal marker name must be
entered.
It specifies an existing marker.
3. The R_MARKER_NAME parameter is used with the LIST_INFO MEASURE command to list the
distance between two markers. This means that the output from the measurement calculations will
be in a coordinate system based on the definition (orientation) of the R_MARKER_NAME.
The R_MARKER_NAME parameter is an optional parameter and if not entered the measurement
will be relative to the global (ground) coordinate system. If the R_MARKER_NAME parameter is
entered a legal marker name must be entered.
It specifies an existing marker.
4. You may identify a marker/model by typing its name or by picking it from the screen.
If the marker/model is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the marker is displayed.
If you created the marker/model by reading an ADAMS data set or graphics file, the marker name is
the letters MAR/ANA/MODEL followed by the ADAMS data set marker ID number. The name of
ADAMS MARKER/101 is MAR101, for example. If you created the marker/model during
If a marker/model is available by default, you may identify it by entering its name only. If it is not,
You must separate multiple marker/model names by commas.
If the marker/model is visible in one of your views, you may identify it by picking on it.
5. An analysis may be picked from the screen if you have read an ADAMS Graphics file, and use the
You may have explicitly named the analysis when you created it by reading one or more ADAMS
output files. By default, the name of the analysis is the root name of the ADAMS output files. If you
created the analysis by reading an ADAMS Graphics file, for instance, the analysis name is the name
of the graphics file without the '.gra' extension.
be entered.
associated with it.
6. The legal values for the configuration 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,
list_info 37
list_info memory_usage parasolid
 FORWARD, one frame forward from the current one displayed, and
 BACKWARD, one frame backward from the current one displayed.
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).
7. The frame with the closest time value to the time specified in this parameter will be selected. Adams
View will display the last frame if the time entered is greater than the time for the last frame in the
simulation.
This parameter is optional and mutually exclusive with the CONFIGURATION and
FRAME_NUMBER parameters. If none of the three are entered, the first frame will be displayed.
views that contain the model indicated by analysis_name will be affected.
8. If entered the frame_number must be a positive integer corresponding to the desired frame (output
Cautions:
1. 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), any views that contain the model
indicated by analysis_name will be affected.
Tips:
1. To identify a marker under a different part, for instance, you may need to enter the model and part
names as well. For example, you may specify marker 'pivot' from model 'links', part 'lower_arm' by
entering ".links.lower_arm.pivot". If you type a "?", Adams View will list the markers available by
default.

You may instruct Adams View to print this information to the "Info Window" or to a file or both.
list_info model
Format:
brief = on/off
Example:
list_info memory_usage parasolid &
brief = on &
Description:

1. The ‘write_to_terminal’ parameter is most likely be used in conjunction withthe FILE_NAME
list_info model
The LIST_INFO MODEL command is used to list the various elements known to the system (i.e. parts,
joints, ...). The information can be sent to the information window, a file, or both.
Format:
list_info model
model_name = model_name
brief = on/off
file_name = file path
list_info 39
list_info name_generation
Example:
list_info model &
brief = on &
Description:

MODEL
type the name even if the model is displayed. You must separate multiple model names by commas.
associated with it. You need not separate multiple model picks by commas.
2. The write_to_terminal parameter is most likely be used in conjunction with the FILE_NAME
Allows the user to obtain information for the default names Adams View generates.
Information for the default name settings includes: a general prefix, an entity-specific prefix, an integer entity
identifier, and a general suffix. These prefixes, suffixes, and identifiers are combined together to form the
default name.
You may instruct Adams View to print this information to the "Info Window" or to a file.
Format:
Brief = on/off
File_name = string
Example:
list_info name_generation &
brief = on &
Name Generation Defaults:

General Prefix For Name Default : is off
Entity Prefix For Name Default : is on
ADAMS ID Suffix for Name Default : is on
General Suffix For Name Default : is off
Entity Prefix For Model is: MODEL_

Entity Prefix For Gravity_Field is: ACCGRAV_
Entity Prefix For Sensor is: SENSOR_
Entity Prefix For Part is: PART_
Entity Prefix For Differential_Equation is: DIFF_
Entity Prefix For Transfer_Function is: TFSISO_
Entity Prefix For Linear_State_Equation is: LSE_
Entity Prefix For General_State_Equation is: GSE_
Entity Prefix For Marker is: MARKER_
Entity Prefix For Floating_Marker is: FMARKER_
Entity Prefix For Point is: POINT_
Entity Prefix For Coupler is: COUPLER_
Entity Prefix For Gear is: GEAR_
Entity Prefix For Joint is: JOINT_
Entity Prefix For Primitive_Joint is: JPRIM_
Entity Prefix For Motion is: MOTION_
Entity Prefix For User_Constraint is: UCON_
Entity Prefix For Curve_Curve is: CVCV_
Entity Prefix For Beam is: BEAM_
Entity Prefix For Bushing is: BUSHING_
Entity Prefix For Field is: FIELD_
Entity Prefix For Single_Component_Force is: SFORCE_
Entity Prefix For Multi_point_Force is: NFORCE_
Entity Prefix For Force_Vector is: VFORCE_
Entity Prefix For Torque_Vector is: VTORQUE_
Entity Prefix For General_Force is: GFORCE_
list_info 41
list_info names
Entity Prefix For Spring_damper is: SPRING_

Entity Prefix For Spline is: SPLINE_
Entity Prefix For ADAMS_Variable is: VARIABLE_
Entity Prefix For ADAMS_Array is: ARRAY_
Entity Prefix For ADAMS_Matrix is: MATRIX_
Entity Prefix For Plant_Input is: PINPUT_
Entity Prefix For Plant_Output is: POUTPUT_
Entity Prefix For Plant_State is: PSTATE_
Entity Prefix For ADAMS_String is: STRING_
Entity Prefix For Arc is: ARC_
Entity Prefix For Block is: BOX_
Entity Prefix For Circle is: CIRCLE_
Entity Prefix For Cylinder is: CYLINDER_
Entity Prefix For Ellipsoid is: ELLIPSOID_
Entity Prefix For Extrusion is: EXTRUSION_
Entity Prefix For Frustum is: FRUSTUM_
Entity Prefix For Force_Graphic is: FORCE_GRAPHIC_
Entity Prefix For Note is: NOTE_
Entity Prefix For Polyline is: POLYLINE_
Entity Prefix For BSpline is: GCURVE_
Entity Prefix For Outline is: OUTLINE_
Entity Prefix For Spring_Damper_Graphic is: SPRING_DAMPER_
Entity Prefix For Revolution is: REVOLUTION_
Entity Prefix For Torus is: TORUS_
Entity Prefix For Plot is: plot_
Entity Prefix For Complex_Scatter is: scatter_
Entity Prefix For Eigen is: EIG_
Entity Prefix For FEMdata is: FEMDATA_
Entity Prefix For Request is: REQUEST_
Entity Prefix For MRequest is: MREQUEST_
Entity Prefix For View is: VIEW
Description:

Brief On/off Specify whether the information required is in brief or not.
Write_to_terminal On/off Specify whether the information has to be displayed on the terminal.
File_name String Specify filename in which the information needs to be written.
Tips:
list_info names
Allows the user to obtain information for existing database entities. You may instruct Adams View to print
list_info names
Format:
list_info names
type_filter = an existing object type
brief = on/off
Example:
list_info names &
entity_name = gui &
brief = off &
Description:

entity_name AN EXISTING Specifies any existing database entity.
ENTITY
type_filter ENT Specify the type of objects allowed.
1. You may identify a database entity by typing its name or by picking it from the screen. If the database
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 database entity is displayed. If you created the database entity by reading an
ADAMS data set or graphics file, the database entity name is the first three letters of the ADAMS
object, followed by the ADAMS data set database entity ID number. The name of ADAMS
PART/101 is PAR101, for example. If you created the database entity during preprocessing, you gave
it a name at that time.
list_info 43
list_info notes
2. If the database entity is available by default, you may identify it by entering its name only. If it is not,
you must enter its full name. For example, to identify a part under an analysis, you may need to enter
the analysis name as well. You may specify the part named par101 from the analysis named test by
entering "/test/par101". You must separate multiple database entity names by commas.
If the database entity is visible in one of your views, you may identify it by picking on any of the
Tips:
1. If you type a "?", Adams View will list the database entities available by default.
list_info notes
Allows the user to obtain information for Notes. You may instruct Adams View to print this information to
the "Info Window" or to a file or both.
Format:
list_info notes
note_name = an existing note name
brief = on/off
Example:
list_info notes &
note_name = note_1 &
brief = on &
list_info output_control debug
Description:

note_name AN EXISTING Specifies an existing model.
NOTE
1. All information for the specified note name will be displayed. This information includes note name,
type, parent name, parent type, location, and the note.The note name can be entered, or a note can
be picked from the screen.
2. You may identify a note by typing its name or by picking it from the screen.
If the note is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the note is displayed. If a note is available by default, you may identify it by
entering its name only. If it is not, you must enter its full name. To identify a note under a model,
for instance, you may need to enter the model name as well. For example, you may specify note "n1"
from the model named test by entering ".test.n1". You must separate multiple note names by
commas. If the note is visible in one of your views, you may identify it by picking on any of the
graphics associated with it. You need not separate multiple note picks by commas.
Tips:
1. If you type a "?", Adams View will list the notes available by default.

Allows you to print out information on the current values set to control the debugging of an ADAMS data
set. You may instruct Adams View to print this information to the "Info Window" or to a file.
Format:
brief = on/off
list_info 45

Example:
list_info output_control debug &
brief = on &
Description:

MODEL
1. You can expect information on the following parameters.
• DUMP Instructs Adams to write the internal representation of your data set.
• EPRINT Instructs Adams to print simulation information for each integration step and
convergence information for each iteration.
• VERBOSE Instructs Adams to output full rather than partial diagnostics.
• REQDUMP Instructs Adams to dump request output at each iteration.
• JMDUMP Instructs Adams to dump the Jacobian Matrix at each iteration.
• RHSDUMP Instructs Adams to dump the if you want to dump the state vector at each iteration.
• DOF Instructs Adams to print a degree-of-freedom table in the tabular output file.
• TOPOLOGY Instructs Adams to print topological data in the tabular output file.
list_info output_control femdata
Tips:
associated with it.

Format:
femdata_name = existing femdata
brief = on/off
file_name = string
Description:

Brief On/off Specify whether the information needs to be specified in
brief or not.
necessary.
Tips:
list_info 47
list_info output_control madata

Allows you to print out information on an existing madata entity. You may instruct Adams View to print this
information to the "Info Window" or to a file.
Format:
brief = on/off
Example:
list_info output_control madata &
brief = on &
Description:

MODEL
list_info output_control mrequest
Tips:
associated with it.

List information about the mrequest settings.
Format:
Mrequest_name = existing mrequest
brief = on/off
file_name = string
Description:

mrequest_name Existing mrequest Specify an existing mrequest name
brief or not.
necessary.
Tips:
list_info output_control output

Allows the user to obtain information for the Adams View OUTPUT settings. You may instruct Adams View
to print this information to the "Info Window" or to a file.
list_info 49
Format:
brief = on/off
Example:
list_info output_control output &
brief = on &
Description:

MODEL
1. OUTPUT controls the generation of request, graphics, and initial conditions files.
In addition, it controls the form, format, coordinates, filtering, and scaling of request data in the
tabular output file. Information generated for OUTPUT includes output name, type, parent name,
parent type, acceleration - displacement - Force and Velocity scales, acceleration - displacement -
Force and Velocity minimum values, request - graphics - and initial condition file creation, and the
formatting parameters.
list_info output_control request
Tips:
associated with it.

Format:
e:

request_name = existing mrequest
brief = on/off
file_name = string
Object Name : .MDI.Forces.vpg_tire.forces_request

Object Type : Request
Parent Type : UDE_Definition
Adams ID : 0
Active : NO_OPINION
Comment : None
Title : None
Functions :
User Function : 902.0, 3.0, 0.0 (vpg_tire.force.adams_id)
Routine : abgTire::req902
Description:

request_name Existing request Specify an existing request name
or not.
necessary.
list_info 51
list_info output_control results
Tips:

Lists information about the result settings for a model.
Format:
brief = on/off
file_name = string
Example:
Results Settings For Model: .MODEL_2
Formatted : Off
XRF : On
Accelerations : On
Applied Forces : On
Displacements : On
Reaction Forces : On
Velocities : On
Data Structures : On
System Elements : On
Linear : On
Floating Markers: On
Friction Summary: Off
Request : On
Comment : None
It will take the default model open as the argument and show the equilibrium parameters for that.
list_info part
Description:

brief or not.
necessary.
Tips:
list_info part
The LIST_INFO part command is used to list the information about a part or (various parts) in the model.
The information can be sent to the information window, a file, or both.
Format:
list_info part
flexible_body_name = an existing flexible body
point_mass_name = an existing mass name
equation_name = an existing eq
brief = on/off
file_name = file name
Example:
:
ist_info part &

brief = on &
list_info 53
list_info part
Description:

part_name AN EXISTING Specifies an existing part.
PART
flexible_body_name AN EXISTING Specifies the name of a flexible body. A flexible body
FLEX_BODY may not have the same name as another flexible body
in the
same model.
point_mass_name AN EXISTING Specifies an existing point_mass.
POINT_MASS
equation_name AN EXISTING Specifies an existing equation.
EQU
displayed.
file_name STRING Specify that the information requested is to be sent to
a file with the name specified with the parameter.
2. If you created the part by reading an ADAMS data set or graphics file, the part name is the letters
PAR followed by the ADAMS data set part ID number. The name of ADAMS PART/101 is
PAR101, for example. If you created the part during preprocessing, you gave it a name at that time.
".robot.arm". You must separate multiple part names by commas. If the part is visible in one of your
views, you may identify it by picking on any of the graphics associated with it. You need not separate
multiple part picks by commas.
3. You may identify a flexible body by typing its name, by selecting it from the database navigator's select
list or by picking its graphical representation from the screen, whichever is most convenient. If Adams
View created the flexible body by reading an ADAMS data set, the name may either come from the
"adams_view_name" field of the preceding comment, or be synthesized from the ADAMS id
number. In the case that the flexible body is created as a result of reading a results or graphics file, the
list_info part
flexible body name will be synthesized from the ADAMS id number. When the name is created by
Adams View it will be composed of "FLX" concatenated with the ADAMS data set flexible body ID
number. For example, the Adams View name of FLEX_BODY/42 would be FLX42. Flexible bodies
you create during preprocessing have userspecified names.
4. You may identify a flexible body belonging to the current default model by entering just its name.
For others, you must enter the full name. To identify a flexible body under another model, for
instance, you need to enter the model name as well. For example, you may specify flexible body
'snake' from model 'reptiles' by entering ".reptiles.snake". You can invoke the database navigator by
typing "?", which will bring up the select list from which you can pick a flexible body. For commands
which accept multiple flexible body names, you must separate the names by commas. If the flexible
body is visible in one of your views, you may identify it by picking on any of the graphics associated
with it. When you do this Adams View will automatically separate multiple flexible body picks by
commas.
5. You may identify a point_mass by typing its name or by picking it from the screen.
If the point_mass is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the point_mass is displayed. If you created the point_mass by
reading an ADAMS data set or graphics file, the point_mass name is the letters POI followed by the
ADAMS data set point_mass ID number. The name of ADAMS POINT_MASS/101 is POI101, for
example. If you created the point_mass during preprocessing, you gave it a name at that time.
If a point_mass is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a point_mass under another model, for instance, you may need
to enter the model name as well. For example, you may specify point_mass 'arm' from model 'robot'
by entering ".robot.arm". If you type a "?", Adams View will list the point_masss available by default.
You must separate multiple point_mass names by commas. If the point_mass is visible in one of your
multiple point_mass picks by commas.
it convenient to type the name even if the equation icon is displayed. If you created the equation by
reading an ADAMS data set or graphics file, the equation name is the letters DIF followed by the
ADAMS data set equation ID number. The name of ADAMS DIFF/101 is DIF101, for example. If
you created the equation during preprocessing, you gave it a name at that time. If a equation is
available by default, you may identify it by entering its name only. If it is not, you must enter its full
name. To identify a equation under a different model, for instance, you may need to enter the model
name as well. For example, you may specify equation 'fluid_volume' from model 'hydro' by entering
".hydro.fluid_volume'". If you type a "?", Adams View will list the equations available by default. You
must separate multiple equation names by commas.
If the equation is visible in one of your views, you may identify it by picking on any of the graphics
associated with it. You need not separate multiple equation picks by commas.
7. The write_to_terminal parameter is most likely be used in conjunction with the FILE_NAME
list_info 55
list_info plots
Tips:
1. If you type a "?", Adams View will list the parts available by default.
list_info plots
Lists information about the plots such as the title, subtitle, analysis, data and time stamp in a current model
Format:
list_info plots
brief = on/off
file_name = string
Example:
list_info plots &
Brief = on
If no parameters are specified, the above command will display brief information about all the plots existing
within the current model.
Object Name : .plot_1
Object Type : Plot
Title : No Title
Subtitle : No Subtitle
Analysis : No Analysis Stamp
Date : No Date Stamp
Type : None
Description:

or not.
necessary.
list_info results
1. If brief is turned off, it will display other details such as the legend visibility, the values of the
horizontal and vertical axes, colors etc
Tips:
list_info results
List information about all the result sets. You may instruct Adams View to print this information to the "Info
Window" or to a file or both.
Format:
list_info results
brief = on/off
Example:
list_info results &
brief = on &
Description:

MODEL
list_info 57
list_info statistics
 name - name of the result set.
 type - the type of result set (displacement, computed, etc.)
 comment - the internal comment of the result set provided by the user on the REQUEST statement
in ADAMS.
 number of steps* - the number of output time steps of the result set.
 I marker id** - The I marker for this request, if specified.
 J marker id** - The J marker for this request, if specified.
**These fields are displayed for result sets read from a request file only.
* All components read in from an ADAMS file will have the same number of steps.
It is possible to create components that have lengths different from the number_of_steps value in the
result set. (i.e.: numeric_results create interpolate).
Tips:
associated with it.
Allows the user to obtain information for existing database entities. You may instruct Adams View to print
Format:
type_filter = an existing object type
depth = an integer
brief = on/off
Example:
list_info statistics &
entity_name = * &
depth = 1 &
brief = on &
Description:

entity_name AN EXISTING Specifies any existing database entity.
ENTITY
type_filter ENT Specify the type of objects allowed.
depth INTEGER
1. You may identify a database entity by typing its name or by picking it from the screen. If the database
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 database entity is displayed. If you created the database entity by reading an
ADAMS data set or graphics file, the database entity name is the first three letters of the ADAMS
object, followed by the ADAMS data set database entity ID number. The name of ADAMS
PART/101 is PAR101, for example. If you created the database entity during preprocessing, you gave
3. If the database entity is available by default, you may identify it by entering its name only. If it is not,
you must enter its full name. For example, to identify a part under an analysis, you may need to enter
the analysis name as well. You may specify the part named par101 from the analysis named test by
entering "/test/par101". You must separate multiple database entity names by commas.
list_info 59
list_info topology
If the database entity is visible in one of your views, you may identify it by picking on any of the
Tips:
1. If you type a "?", Adams View will list the database entities available by default.
list_info topology
Lists information on how a model's parts are connected to each other.
When you request information about a models topology, Adams View will determine what joints, jprims,
point curves, and curve curves are owned be the model and what parts these objects are connected to by
determining the parent of the I and J markers of the connecting objects.
You can request the information to be output by part or by the object connecting the parts with the
OUTPUT_BY parameter.
If you specify OUTPUT_BY=PARTS (this is the default) every part in the model will be listed, along with
the parts it is connected to and what joint, jprim, point curve, curve curve or force is connecting it.
If you specify OUTPUT_BY=CONNECTIONS each joint, jprim, point curve, curve curve and force will
be listed and what parts it connects. A listing of the unconnected parts will also be displayed.
Format:
list_info topology
output_by = topology_output
brief = on/off
file_name = string
Example:
list_info topology &
output_by = parts &
This will display the following information:

Topology of model: model_1
Ground Part: ground
list_info triglue
Part ground
Is not connected to any parts
Part PART_2
Is connected to:
PART_3 via JOINT_1 (Revolute Joint)
Part PART_3
Is connected to:
PART_2 via JOINT_1 (Revolute Joint)
Description:

model_name Existing model Specifies an existing model.
output_by Parts/connections Specifies how the model topology is to be listed.
Brief On/off Specifies whether to use the brief form (default) or an
displayed.
write_to_terminal On/off Specify if the information requested is to be sent to the
file_name String Specify that the information requested is to be sent to a file
associated with it.
2. If you specify OUTPUT_BY=PARTS (this is the default) every part in the model will be listed, along
with the parts it is connected to and what joint, jprim, point curve, curve curve or force is connecting
it.
If you specify OUTPUT_BY=CONNECTIONS each joint, jprim, point curve, curve curve and
force will be listed and what parts it connects. A listing of the unconnected parts will also be
displayed.
list_info triglue
You may instruct Adams View to print this information to the "Info Window" or to a file or both.
list_info 61
list_info undo
Format:
list_info triglue
brief = on/off
Example:
list_info undo &
brief = on &
Description:

list_info undo
Allows you to obtain the amount of memory being consumed by the undo stack. You may instruct Adams
View to print this information to the "Info Window" or to a file or both.
Format:
list_info undo
brief = on/off
list_info variable
Example:
list_info undo &
brief = on &
Dsecription:

list_info variable
Lists information about the variables’s in the current model.
Format:
list_info variable
variable_name = Existing variable name
Brief = on/off
File_name = string
Example:
list_info variable &
variable_name = DV_1 &
brief = off &
Object Name : .model_1.DV_1
Object Type : Variable
Parent Type : Model
list_info 63
list_info views
String Value(s) : MyDesignVar

Comment String : None
Orig Value(s) : MyDesignVar
Dependents : None.
If brief is turned on then the dependant information will not be displayed.
Description:

Variable_name Existing variable name Specify an existing variable whose information has to be
listed.
Brief On/off Specify whether the variable information required is in
brief or not.
Write_to_terminal On/off Specify whether the information has to be displayed on the
terminal.
written.
Tips:
list_info views
List information about all the result sets. The information can be sent to the information window, a file, or
both.
Format:
list_info views
view_name = an existing view name
view_layout_name = an existing view layout
brief = on/off
Example:
list_info views &
view_name = view_1 &
view_layout_name = vlayout_1 &
list_info views
list_info views &

brief = on &
Description:

view_name AN EXISTING An existing view name
VIEW
view_layout_name AN EXISTING Specifies an existing view layout.
VLAYOUT
• name - the name of the view
• center - the view center in global model coordinates.
• field of view - the width (x) and the height (y) of the view in global model coordinates
• project - the view is drawn in either (orthographic or perspective) mode
• render - the view is drawn in (wireframe, solid, or shaded) mode
• saved - whether the view has been saved.
3. You may identify a view_layout by typing its name. If a view_layout is available by default, you may
identify it by entering its name only. If it is not, you must enter its full name. If you type a "?", Adams
View will list the view_layouts available by default. You must separate multiple view_layout names
by commas.
list_info 65
list_info views
Cautions:
Tips:
1. If the VIEW_NAME parameter is used, the desired view can be identified by picking in the window
list_info views
macro 1
macro create
macro
macro create
A macro is a single command that you create to execute a series of Adams View commands. To create a macro,
you give Adams View the list of commands you want executed, as well as the new command (i.e., the macro)
that will execute them.
Format:
macro create
macro_name = macro name
user_entered_command = command representing the macro
commands_to_be_executed = list of commands to be executed
wrap_in_undo = yes/no
help_file = help file path
help_string = help text
create_panel = yes/no
security_code = alpha-numeric code to run a macro
Example:
macro create &

macro_name = .TEST_MACRO &
user_entered_command = "TESTMAC" &
commands_to_be_executed = &
"!$parts:T=part:C=0", &
"!$analysis:T=analysis:D=Last_Run", &
"!END_OF_PARAMETERS", &
"!", &
"!---set the default analysis", &
"defaults analysis analysis_name = $analysis", &
"",&
"!---loop through part list", &
"for var=the_part obj=$parts", &
" defaults model part_name=(the_part)", &
" file spread_sheet write &", &
" file_name = (DB_DEFAULT(SYSTEM_DEFAULTS,\"PART\").name) &", &
" result_set_name =
((DB_DEFAULT(SYSTEM_DEFAULTS,\"PART\").name)//\"_XFORM\")", &
"end", &
"", &
"!---clean-up", &
"variable delete
variable_name=(eval(db_children($_self,\"variable\")))" &
macro create
!
wrap_in_undo = No &
help_string = "This test macro can export part XFORM results." &
create_panel = No
!
Description:

macro_name String Specifies the name of the new macro.
user_entered_command String Specifies the command string to be entered by the user to
execute the macro.
commands_to_be_ executed String Specifies the list of Adams View commands to be
executed.
wrap_in_undo Yes/No Specifies whether or not to the entire macro can be
undone with a single undo command.
help_file String Specifies the text that is to be used as the command or
topic string when getting help on a macro.
help_string String Specifies the text that is to be used as the command or
create_panel Yes/No Allows the user to specify if a panel is to be created for the
specified macro.
security_code
1. Adams View will not allow you to have two macros with the same full name, so you must provide a
unique name. You must separate multiple macro names by commas.
2. The user_entered_command is a string with list of keywords separated by blanks. The keywords can
match existing keywords, but the final command defined must be unique.
For example: user_entered_command = "force my_force create"
If this parameter is not entered, the name of the macro will become the new command.
3. You can specify the Adams View commands that are to be executed when the macro is used with the
commands_to_be_executed parameter on the macro read and macro modify commands, or from a
file on the macro read command. Adams View does not check your entries in this field for correct
syntax when you create the macro, only when the macro is executed the syntax errors will be notified.
You enter these commands as quoted strings separated by commas. You can have quotes inside a
string by proceeding them with a backslash "\". You can indicate parameters to associate with the
macro be placing a dollar sign '$' followed by the name of the parameter you want anywhere in the
commands.
macro 3
macro delete
4. The help that is obtained by help_file is the same as you would get if you supplied the help string to
the command: help command_or_topic=. You must specify the entire file name, there is no default
extension. The search path facility is used to find the specified file.
5. If there are no parameters in the macro, no panel will be created. The name of the macro panel will
be macro_ appended with the macro name. For example, if the name of macro being created or
modified is MAC1, the panel will be named macro_MAC1.
Cautions:
1. If the macro is very large turning the wrap_in_undo option to yes may decrease the speed of it's
execution.
Tips:
1. You may identify a macro by typing its name. If a macro is available by default, you may identify it
by entering its name only. If it is not, you must enter its full name. If you type a "?", Adams View will
list the macros available by default.
macro delete
Allows you to delete existing macros.
Format:
macro delete
macro_name = macro name/list
Description:
Parameters Value Type Description

macro_name String Specifies the name of an existing macro
1. Adams View will not allow you to have two macros with the same name, so you must provide a unique
name. You must separate multiple macro names by commas.
Tips:
macro modify
macro modify
A macro is a single command that you create to execute a series of Adams View commands. The macro
modify command allows edition of existing macros.
Format:
macro modify
new_macro_name = modified macro name
user_entered_command = command representing the macro
commands_to_be_executed = list of commands to be executed
security_code = alpha-numeric code to run a macro
Example:
macro modify&
macro_name = .TEST_MACRO &
new_macro_name = .TEST_MACRO_1 &
user_entered_command = "TESTMAC" &
commands_to_be_executed = &
"!$parts:T=part:C=0", &
"!$analysis:T=analysis:D=Last_Run", &
"!END_OF_PARAMETERS", &
"!", &
"!---set the default analysis", &
"defaults analysis analysis_name = $analysis", &
"",&
"!---loop through part list", &
"for var=the_part obj=$parts", &
" defaults model part_name=(the_part)", &
" file spread_sheet write &", &
" file_name = (DB_DEFAULT(SYSTEM_DEFAULTS,\"PART\").name) &", &
" result_set_name =
((DB_DEFAULT(SYSTEM_DEFAULTS,\"PART\").name)//\"_XFORM\")", &
"end", &
"", &
"!---clean-up", &
"variable delete
variable_name=(eval(db_children($_self,\"variable\")))" &
!
wrap_in_undo = No &
macro 5
macro modify
help_string = "This test macro can export part XFORM results." &
create_panel = No
!
Description:

macro_name String Specifies the name of the macro to be modified
new_macro_name String Specifies the name of the new macro
execute the macro.
commands_to_be_ executed String Specifies the list of Adams View commands to be
executed.
wrap_in_undo Yes/No Specifies whether or not to the entire macro can be
undone with a single undo command.
help_file String Specifies the text that is to be used as the command or
help_string String Specifies the text that is to be used as the command or
specified macro.
security_code
2. You may use this name later to refer to this macro. Adams View will not allow you to have two macros
with the same full 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 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. 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 over ride 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" The
number of levels used varies from case to case and the parentage must exist before an entity can be
assigned to it.
macro read
3. The user entered command is a string is a list of keywords separated by blanks. The keywords can
match existing keywords, but the final command defined must be unique. For example:
user_entered_command = "force my_force create" If this parameter is not entered, the name of the
macro will become the new command.
COMMANDS_TO_BE_EXECUTED parameter on the MACRO READ and MACRO MODIFY
commands, or from a file on the MACRO READ command. Adams View does not check your
entries in this field for correct syntax when you create the macro, only when the macro is executed.
commands (see MACRO).
5. The help that is obtained by this string is the same as you would get if you supplied the help string to
the command: help command_or_topic=. You must specify the entire file name, there is no default
extension. The search path facility is used to find the specified file.
6. If there are not parameters in the macro, no panel will be created. The name of the macro panel will
be 'macro_' appended with the macro name. For example, if the name of macro being created or
modified is MAC1, the panel will be named 'macro_MAC1'.
Tips:
macro read
Allows you to create a macro by reading the commands to be executed from a file. Thus, instead of creating
a new macro from the scratch, an existing command file can be used as a template.
Format:
macro read
file_name = file name with path
user_entered_command = command
macro 7
macro read
Example:
macro read &
macro_name = TEST_MACRO &
file_name = “C:\macros\test_mac.cmd” &
user_entered_command = “TESTMAC” &
wrap_in_undo = No &
help_string = ‘This is a test macro’ &
create_panel = No
Description:

macro_name String Specifies the name of an existing macro.
executed.
execute the macro.
wrap_in_undo Yes/No Specifies whether or not to the entire macro can be undone
with a single undo command.
help_file String Specifies the text that is to be used as the command or topic
string when getting help on a macro.
help_string String Specifies the text that is to be used as the command or topic
string when getting help on a macro.
specified macro.
2. The user_entered_command is a string with a list of keywords separated by blanks. The keywords
can match existing keywords, but the final command defined must be unique.
For example: user_entered_command = "force my_force create"
If this parameter is not entered, the name of the macro will become the new command.
commands_to_be_executed parameter on the macro read and macro modify commands, or from a
file on the macro read command. Adams View does not check your entries in this field for correct
syntax when you create the macro, only when the macro is executed the syntax errors will be notified.
macro write
commands.
4. The help that is obtained by help_file string is the same as you would get if you supplied the help
string to the command: help command_or_topic=. You must specify the entire file name, there is no
default extension. The search path facility is used to find the specified file.
5. If there are no parameters in the macro, no panel will be created. The name of the macro panel will
be macro_ appended with the macro name. For example, if the name of macro being created or
modified is MAC1, the panel will be named macro_MAC1.
Cautions:
1. If the macro is very large turning the wrap_in_undo option to yes may decrease the speed of it's
execution.
Tips:
macro write
Write the commands that are to be executed (defined by the commands_to_be_executed parameter) from
the macro to a file. The file will contain comments at the top about the macro definition and the commands
to be executed.
Format:
macro write
file_name = file name with path
Example:
macro write &
macro_name = ANALYSIS_DELETE
Case:
macro create &
macro_name=ANALYSIS_DELETE &
user_entered_command="delete analysis" &
help_string="Quickly delete an analysis" &
commands_to_be_executed ="model delete analysis_name=$analysis_name"
macro 9
macro write
macro write macro_name=ANALYSIS_DELETE
would generate the file ANALYSIS_DELETE.cmd, which contains:

! USER_ENTED_COMMAND ANALYSIS_DELETE
! WRAP_IN_UNDO YES
! HELP_STRING Quickly delete an analysis
model delete analysis_name=$analysis_name
Description:
Parameters Value Type Description

macro_name String Specifies the name of the existing macro whose commands will be
written to a file
list the macros available by default. You must separate multiple macro names by commas.
Tip:
1. You can read the macro back into Adams View with the macro read command. The default extension
for this file is '.cmd'.
macro write
marker 1
marker attributes
marker
marker attributes
Allows you to set the specification of attributes on an individual marker or a group of markers.
Format:
marker attributes
name_ visibility = on_off_with_toggle
Example:
marker attributes &
marker_name = psmar &
visibility = on &
color = blue &
active = on &
marker attributes
Description :

marker_name An Existing Marker Specifies the marker to be modified. You use this
parameter to identify the existing marker to be affected
with this command.
scale_of_icons Real Specifies a unit-less scale factor to apply to the current
icon size.
size_of_icons Real Specifies the size, in modeling units, the Adams View
icons will appear in.
name_ visibility On_Off_With_Toggle The NAME_VISIBILITY parameter provides control
over the visibility of the view name displayed at the top
center position of a given view.
color A Existing Color Specifies the color the modeling entity should be drawn
in.
active On_Off_No_Opinion Sets the activation status of the element
dependents_active On_Off_No_Opinion Sets the activation status of the dependants of an element
SIZE_OF_ICONS / SCALE_OF_ICONS. These two parameters are mutually exclusive. You may
set a size of the icon used for the marker representation in modeling units, or you may scale the size
of the icon by a non-unit scale factor.
VISIBILITY. You may set a marker's visibility ON, OFF or TOGGLE the current setting. When you
set a marker's visibility OFF, the marker will not be drawn. When you set a marker's visibility ON,
you allow that marker to be drawn.
NAME_VISIBILITY. You may set a marker's name label visibility ON, OFF or TOGGLE the
COLOR. You may set the color of a marker with this parameter.
INHERITANCE may either be TOP_DOWN or BOTTOM_UP.
is a tree structure with the model at the apex.
Parts exist beneath the model, and markers exist beneath the parts.
marker 3
marker attributes
If the icon size of the model is set to 0.1, and the default INHERITANCE is set to TOP_DOWN,
then all icons displayed within the model will be displayed at this size. However, if the icon size of a
model is set to 0.1, and then the default INHERITANCE is set to BOTTOM_UP, then any icons
set to a size other than the model's icon size will be displayed in their own size.
name at that time.
unit. For example, if the modeling units are K/M/S, a part axes icon will have triad legs, one meter in
length.
When you specify SCALE_OF_ICONS, a new size is calculated by multipling the current size by the
unit. For example, if the modeling units are K/M/S, a part axes icon will have triad legs, one meter in
length.
An Example:
If the model has SIZE_OF_ICONS set to 0.0 , and a part under that model has a SIZE_OF_ICONS
set to .125, the part's icon size will be used.
An Example:
marker attributes

at the top center position of a given view.
The legal values of this parameter are ON and OFF. This is an optional parameter and if not entered
the name will be visible (that is, will be ON).
Example 1:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
command:
marker 5
marker copy
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
marker copy
Allows you to create a replica marker within the same model.
Format:
marker copy
new_marker_name = a new marker
Example:
marker copy &
new_marker_name = marker_2

marker_name An Existing Specifies an existing marker
Marker
new_marker_name A New Marker Specifies the name of the new marker. You may use
this name later to refer to this marker.
marker copy
1. The replica marker will be identical to the original, with the exception of the marker name. Markers
must have unique names relative to other markers under a given part. You specify the replica marker's
name with the NEW_MARKER_NAME parameter. The replica will be completely independent of
the original, and may be modified without affecting the original.
name at that time.
Note that you can specify the parentage of an entity (for example, which part "owns" a marker or a
be assigned to it.
Cautions:
1. Adams View will not allow you to have two markers with the same name, so you must provide a
unique name.
marker 7
marker create
marker create
Allows you to create a marker. You may reverse this creation at a later time with an UNDO command.
Format:
marker create
marker_name = a new marker
adams_id = adams_id
comments = string
location = location
preserve_location = true_only
node_id = integer
velocity = real
vx = real
vy = real
vz = real
reference_marker_name = an existing marker
Example:
marker create &
adams_id = 1 &
comments = "a new marker" &
location = 10 , 20 , 10 &
node_id = 5 &
orientation = 10 , 10 , 10 &
relative_to = piston &
reference_marker_name = marker_33
marker create
Description:

marker_name A New Marker Specifies the name of the new marker. You may use this
name later to refer to this marker.
Adams data file.
modified.
location Location Specifies the location of the origin of a coordinate
system (for example, marker or part).
preserve_location True only An optional parameter, which when specified means
that the marker location is to be retained as specified (for
example, marker on a flexible body will not be snapped
to the nearest node). The parameter is mutually
exclusive with the 'node_id' parameter, for marker
creation.
node_id Integer Specifies a node_id on a flexible body that Adams View
will use to determine the location at which it will place
a marker.
OR
Specifies a node_label on an FE Part that Adams View

a marker. If a location is also specified, then the node
referenced here will be ignored, the location field
contents will determine the marker location and the
marker will be associated with the nearest node.
offset Location Specifies the translational offset from the specified FE
part node at which the marker is to be created. Offset is
used only in conjunction with an FE Part node. These
coordinates are relative to the FE Part node's coordinate
system (X tangent to centerline, Y and Z are normal and
binormal).
orientation Orientation Specifies the orientation of a coordinate system (for
example, marker or part) using three rotation angles.
axis.
marker 9
marker create

Model, Part Or coordinates and orientation angles correspond to.
Marker
curve_name An Existing Curve Specifies the curve name on which to create a marker
velocity Real Specifies the initial conditions
vx Real Specifies the initial conditions
vy Real Specifies the initial conditions
vz Real Specifies the initial conditions
reference_marker_name An Existing Specifies an existing marker which acts as a reference
Marker
1. Markers are attached to parts, which are contained in models. Before creating markers, you must use
the 'MODEL CREATE' and 'PART CREATE RIGID_BODY NAME_AND_POSITION'
command to create at least one model and part.
be assigned to it.
marker create
yourself.
system.
6. The preserve_location parameter is specified to indicate that the specified marker location is to be
preserved. The parameter comes into play for markers on a flex body or on an external system (where
an MNF/MD DB is specified). For example, a flex marker will not be snapped to the node nearest to
the specified location, if this parameter is specified. This parameter is mutually exclusive with the
node_id parameter for the marker create command.
7. The value must be an integer which is a valid node ID from your flexible element model.
x, y, and z angles.
system.
9. You may enter either one or two locations to direct the axis using the along_axis_orientation
paramater. If you enter one location, the axis will point towards the location. If you specify two
to the second.
marker 11
marker delete
system.
10. You may enter either two or three locations for the in_plane_orientation parameter. If you enter two
locations, the axis will point towards the first location and the plane will fall on the second. If you
system.
Cautions:
 Adams View will not allow you to have two markers with the same name, so you must provide a
unique name.
marker delete
Allows you to delete an existing marker.
Format:
marker delete
Example:
marker delete &
marker_name = marker_2
marker modify
Description:

marker_name An Existing Specifies the marker to be deleted.
Marker
1. You must enter the name of the marker you wish to delete either by picking it from the screen or
menu entry, 'UNDO'.
name at that time.
3. If a marker is available by default, you may identify it by entering only its name. If it is not, you must
Tips:
Also refer marker delete_unused in mdi command.
marker modify
Allows you to modify an existing marker.
marker 13
marker modify
Format:
marker modify
new_marker_name = a new marker
adams_id = adams_id
comments = string
location = location
preserve_location = true_only
node_id = integer
velocity = real
vx = real
vy = real
vz = real
reference_marker_name = an existing marker
Example:
marker modify &
new_marker_name = marker__2 &
adams_id = 1 &
comments = "modifying an existing marker" &
location = 10 , 20 , 10 &
node_id = 5 &
relative_to = piston &
reference_marker_name = marker_33
marker modify
Description:

marker_name
new_marker_name A New Marker Specifies the name of the new marker. You may use this
name later to refer to this marker.
Adams data file.
modified.
location Location Specifies the location of the origin of a coordinate
system (for example, marker or part).
preserve_location True only An optional parameter, which when specified means
that the marker location is to be retained as specified
(for example, marker on a flexible body will not be
snapped to the nearest node).
node_id Integer Specifies a node_id on a flexible body that Adams view
a marker.
orientation Orientation Specifies the orientation of a coordinate system (for
example, marker or part) using three rotation angles.
axis.
Part OR Marker coordinates and orientation angles correspond to.
curve_name An existing Curve Specifies the curve name on which to create a marker
velocity Real Specifies the initial conditions
vx Real Specifies the initial conditions
vy Real Specifies the initial conditions
vz Real Specifies the initial conditions
reference_marker_name An Existing Marker Specifies an existing marker which acts as a reference
marker 15
marker modify
name at that time.
You must separate multiple marker names by commas. If the marker is visible in one of your views,
you may identify it by picking on it. You need not separate multiple marker picks by commas.
be assigned to it.
yourself.
4. When an Adams Solver data file (.adm) is read into AdamsAdams View, all comments associated with
a statement (from the end of the previous statement through the end of the current statement) are
marker modify
system.
6. The preserve_location parameter is specified to indicate that the specified marker location is to be
preserved. The parameter comes into play for markers on a flex body or on an external system (where
an MNF/MD DB is specified). For example, a flex marker will not be snapped to the node nearest to
the specified location, if this parameter is specified.
This parameter can be specified with the node_id parameter during marker modification, to indicate
that the marker is NOT to be snapped to the nearest node, but instead its existing location is to be
maintained.
for example, marker create marker = .model_1.flex_body_1.marker_1 node_id = 15 location =
10,10,10
marker modify marker = .model_1.flex_body_1.marker_1 node_id = 20 preserve_location = true
The modify marker command will change the node_id of the marker to 20 and its original location
(10,10,10) will be maintained.
7. The node_id value must be an integer which is a valid node ID from your flexible element model.
x, y, and z angles.
system.
9. You may enter either one or two locations to direct the axis using the along_axis_orientation
parameter. If you enter one location, the axis will point toward the location. If you specify two
to the second.
marker 17
marker modify
system.
10. You may enter either two or three locations for the in_plane_orientation paramater. If you enter two
system.
Cautions:
 Adams View will not allow you to have two markers with the same name, so you must provide a
unique name.
Tips:
1. You must enter the name of the marker you wish to modify by either picking it from the screen or
2. You may reverse this modification at a later time with an UNDO command.
marker modify
material 1
material copy
material
material copy
Allows you to copy the existing material properties to a new material in the model database.
The material can be specified with the essential properties, namely, 1) Young’s modulus, 2) Poisson’s ratio,
and 3) Density. Any new material can be specified by entering these properties in the material database.
Format:
material copy
material_name = an existing material
new_material_name = a new material
Example:
material copy &
material_name = alloy &
new_material_name = alloy_new
Description:

material _name An Existing Material Specifies the name of an existing material
new_material_name A New Material Specifies a new name for the material
The material with its existing properties can be copied to a new material with a different name.
material create
Allows you to create a new material in the model database.
material create
Format:
material create
material_name= a new material
adams_id = adams_id
comments = string
youngs_modulus = pressure
poissons_ratio = real
density = density
Example:
material create &
material_name = .materials.alloy &
adams_id = 2 &
comments = toughened_alloy &
youngs_modulus = 2.4e5 &
poissons_ratio = 0.29 &
density = 7.8
Description:

material _name A New Material Specifies a new name for the material to be created
adams_id Adams_id Specifies an integer used to identify this element in Adams
database
comments String Specifies comments, if any, on the element
Young’s modulus Pressure Specifies the modulus of elasticity of the material
poisson’s ratio Real Specifies the data table size in pixels or units relative to Adams
window
density Density Specifies the density of the material
1. The material name specifies a new material to be defined. The ‘adams_id’ specifies an integer used to
identify this element in the Adams data file. When you use the FILE ADAMS_DATA_SET WRITE
command, Adams View writes an Adams data file for your model. Adams requires that each modeling
element be identified by a unique integer identifier. If you use this parameter to specify a non-zero
identifier, Adams View will use it in the corresponding statement in the Adams data file.
material 3
material delete
3. The Young’s Modulus specifies modulus of elasticity for the beam material and the poisson’s ratio is
also entered for the material. Specifies the part density and that the mass properties of the part are to
be automatically calculated. The calculated mass properties are based upon the solid geometry that
belongs to the part.
material delete
Allows you to delete an existing material in the model database.
Format:
material delete
Example:
material delete &
material_name = .materials.alloy
Description:

material _name An Existing Material Specifies the name of an existing material
An existing material can be removed from the database by providing the appropriate material name with the
‘delete’ command.
material modify
material modify
Allows you to modify an existing material in the model database.
and 3) Density. Any new material can be specified by entering those properties in the material database.
Format:
material modify
new_material_name = a new material
adams_id = integer
comments = string
youngs_modulus = pressure
poissons_ratio = real
density = density
Example:
material modify &
material_name = .materials.alloy &
new_material_name = .materials.modified_alloy &
adams_id = 2 &
comments = toughened_alloy &
youngs_modulus = 2.4E+005 &
poissons_ratio = 0.29 &
density = 7.8
Description:

material _name An Existing Specifies the name of an existing material
Material
new_material_name A New Material Specifies a new name for an existing material
adams_id Integer Specifies an integer used to identify this element in Adams
database
comments String Specifies comments, if any, on the element
material 5
material modify

Young’s modulus Pressure Specifies the modulus of elasticity of the material
poisson’s ratio Real Specifies the data table size in pixels or units relative to Adams
window
density Density Specifies the density of the material
1. The material name specifies the name of an existing material, which can be renamed by the parameter
‘new_material_name’. The ‘adams_id’ specifies an integer used to identify this element in the Adams
data file. When you use the FILE ADAMS_DATA_SET WRITE command, Adams View writes an
Adams data file for your model. Adams requires that each modeling element be identified by a
unique integer identifier. If you use this parameter to specify a non-zero identifier, Adams View will
use it in the corresponding statement in the Adams data file.
3. The Young’s Modulus specifies modulus of elasticity for the beam material and the Poisson’s Ratio is
also entered for the material. Specifies the part density and that the mass properties of the part are to
be automatically calculated. The calculated mass properties are based upon the solid geometry that
belongs to the part.
marker delete_unused
mdi
Identifies and deletes the markers that are unused anywhere in a single model in an Adams View or Adams
Car Template Builder session.
Format:
mdi marker delete_unused
model = an existing model
body = an existing body
Example:
mdi marker delete_unused &
model = Model_1
body = body_1
Description:

model An Existing Model Specifies the model whose unused markers are to be deleted.
body An Existing body Specifies the body whose unused markers are to be deleted.
1. You must enter the name of the model under which you wish to delete unused markers.
2. Unused markers are considered those with no dependents; that is, any marker not involved in
a. object definitions like geometry, constraints or forces
b. body definitions like center or mass or inertia reference markers
c. design-time expressions, for example for parametrization
d. run-time functions, for example defining the value of a motion or force component
Cautions:
 Markers used only by user subroutine functions hardcoded to the marker ID will be identified by
this command as unused. If you reference marker ID's directly in object runtime functions calling
user subroutines, then use this command very cautiously.
 You need not separate multiple models by commas.
mdi 7
Tips:
You may reverse this deletion immediately following the action with an UNDO command.
measure 1
measure attributes
measure
measure attributes
Allows you can set the attributes for a strip chart, including creating a legend, setting axis limits, and setting
the color and line type for the curve.
Strip chart is a monitoring device in which Adams View plots a measure. The strip chart monitors the
measure during a simulation.
Format:
measure attributes
measure_name = existing measure
comment = string
legend = string
axis_lower = real
axis_upper = real
axis_labe l= string
axis_type = axis_units
curve_color = existing color
curve_line_type = line_style
curve_thickness = real
curve_symbol_type = plot_symbols
Example:
measure attributes &
measure_name = mea_angle__1 &
comment = "change the attributes" &
legend = "angle measure" &
axis_type = linear &
curve_color = red &
curve_thickness = 2.5 &
curve_line_type = dash
measure attributes
Description:

measure_name Existing measure Specifies an existing measure whose attributes have to be
modified.
comment String Specifies any comments.
legend String Enter text that describes the data that the curve in the strip
chart represents.
axis_lower Real Parameter not supported.
axis_upper Real Parameter not supported.
axis_label String Parameter not supported.
axis_type Linear/logar/db/default Select the type of plot to be displayed in Adams
PostProcessor when you transfer the strip chart to it for
plotting.
curve_color Existing color Enter color of the curve.
curve_line_type SOLID, DASH, Sets curve_Line Type to the type of line style for the curve.
DOTDASH, DOT, For example, you can select a line that alternates between
NONE dots and dashes.
curve_thickness Real Changes the weight of the curve line. Weight values range
from 1 to 5 screen pixels.
1. The text specified in the legend parameter appears in the title bar of the strip chart. Note that you
have to redisplay the strip chart to see the effects of changing the legend.
2. There are 4 types of plots that can be specified in the axis_type parameter:
 linear - Performs no transformation of data or axis values. This is the default.
 logar (Logarithmic) - Scales the axis values so that each power of 10 is separated by the same
distance. For example, the values 1, 10, 100, 1000, and 10,000 are equally spaced.
 db (Decibel) - Displays 20 * log 10 (value) for each value.
 default - Selecting this means no specific axis type is requested and it appears in the default axis type,
which is usually linear.
Cautions:
1. You have to redisplay the strip chart to see the effects of changing the legend, color, line type, line
symbol, and line thickness. Learn about redisplaying strip charts.
The axis_Lower, axis_Upper, and axis_Label options currently are not available.
measure 3
measure copy
measure copy
Creates a copy of an existing measure.
Format:
measure copy
new_measure_name = new name for the copy
Example:
measure copy &
measure_name = my_angle_mea_1 &
new_measure_name = angle_mea_1_copy
Description:

Measure_name Existing measure Specifies the name of the measure to be copied.
New_measure_name New name for the measure Specifies the new name for the copy of the measure.
measure create angle

This command will create a new angle measure.
Format:
measure_name = new mea_angle
first_point = existing marker
middle_point = existing marker
last_point = existing marker
comments = string
legend = string
Example:
measure create angle &
measure_name = angle_between_link1_link2 &
first_point = marker_2 &
measure create angle &

last_point = marker_4 &
middle_point = marker_1 &
legend = "angle between two links" &
comments = "to track the angle between two links"
If Link1 and Link2 are connected by a revolute joint and Marker2 lies on Link1, Marker 3 lies on Link2 and
Marker 1 lies in the intersection of Link1 and Link2, then the above command will create an angle measure
to compute the angle between the two links. The title of the measure will be the string specified in the legend
parameter.
Description:

measure_name New Meaure name Specifies the name of the angle measure. You can use this name
later to specify this new angle measure created.
first_point Existing marker Specifies an existing marker on an entity.
middle_point Existing marker Specifies an existing marker on an entity.
last_point Existing marker Specifies an existing marker on an entity.
Legend String Specifies the text that will appear at the top of the Angle measure.
Comments String Specifies any comments that are to be associated with this angle
measure.
1. About Measuring Included Angle Characteristics
The included angle measure captures the instantaneous angle between two vectors defined by three
markers. For example, you can use the angle measure to find the included angle between any two links
connected by a revolute joint. The default unit for angle measures is degrees.
To create an included angle, you select three markers, as illustrated in the figure below. These three
markers define two vectors:
It is the instantaneous angle between these vectors that Adams View tracks in an included angle
measure. Note that the included angle changes over time as the markers move during a simulation.
Example of Points That Define Included Angles
measure 5
measure create computed
There are two conventions used in Adams View to define the sign and magnitude of an included angle
measure as it changes over time:
2. The sign and magnitude is always calculated so as to have an initial value within the range [0, PI]
regardless of the order in which you select the points.
3. The axis of rotation is automatically calculated as the cross-product of , which is sensitive

to the order in which you select the points. This, along with the right-hand rule, determines all
subsequent changes to the sign and magnitude of the included angle measure.

Adams View computed measures allow you to create measures in the Adams View expression language that
can be evaluated before a simulation or any time after. You build them using design-time functions and
typically use them in the initial model set up.
An Adams View computed measure is convenient because it can reference any Adams View variable. For
example, if you create two measures and you want to add or subtract them, you can use an Adams View
computed measure to do so. You can also compute data from a run-time measure.
Format:
measure_name = new computed measure
units = string
create_measure_display = boolean
legend = string
comments = string
Example:
Assuming that ADAMS_KE is an existing measure of the kinetic energy of a pendulum and MY_KE is an
existing analytical measure if the kinetic energy.
measure create function
measure create computed &

measure_name = my_measure_computed &
text_of_expression = “100*(.model_1.adams_ke - .model_1.my_ke)/322.6” &
units = “no_units” &
legend = “measure comparison of analytical and kinetic energy
results”
Description:

measure_name New measure name Specifies name of the computed measure
text_of_expression String The TEXT_OF_EXPRESSION parameter defines the
computation to be performed by the function.
Remember that the value of this argument should be a
character string, NOT an expression.
units String Specifies units of the measure.
create_measure_display Yes/No Specifies whether the strip chart has to be displayed of
the measure.
Legend String Specifies the text that will appear at the top of the created
measure.
comments String Specifies any comments.
Cautions:
1. Be careful, however, about the changes you make in your model. Making changes can cause a
potential problem because model changes can invalidate the accuracy of any measure that depends on
the results of a simulation. The simulation redefines the model data and re-evaluates your Adams
View computed measures.

An Adams Solver function measure allows you to create a measure in Adams View that Adams Solver
evaluates during simulations. Because Adams Solver function measures are only evaluated during simulations,
function measures remain unevaluated until you run a simulation. The Adams Solver function measure is
convenient because it lets you reference any user-defined Adams Solver function or subroutine. Function
measures are built from Adams Solver run-time functions.
measure 7
Format:
measure_name = new function measure
function = function
routine = string
units = string
legend = string,
comments = string
Example:
measure cre function measure = .model_1.function_mea_1 &
function = "0.5*wz(.model_1.part_2.cm)**2*(15*(50**2
+ 300**2) + 15000)/1000" &
units = no_units &
create_measure_display = yes
Description:

Measure_name New name for measure Specifies the name of the measure.
function Function Specifies function to be evaluated during the
simulation.
user_function Real Specifies a real number
routine String Specifies a string for the routine.
units String Specifies any units that have to be associated.
create_measure_display Yes/No Specifies yes if the strip chart of the measure needs
to be displayed.
legend String Specifies the text that will appear on the top of the
measure dialog.
Comments String Specifies any comments about the function
measure.
measure create object
Cautions:
1. Be careful, however, about the number of Adams Solver function measures you create because Adams
View writes each measure to the Adams Solver dataset as a VARIABLE statement. Each VARIABLE
statement adds another equation to the overall set of equations. The more equations Adams Solver
must solve, the longer your simulation takes.

Creates an object measure.
In general, all objects in your model have some pre-defined measurable characteristics. For example, you can
capture and investigate the power consumption of a motion, or measure a part’s center-of-mass velocity along
the global x-axis, taking time derivatives in the ground reference frame. The default coordinate system is the
ground coordinate system, but you can use any marker as the coordinate system.
Format:
measure cre‘ate object
measure_name = new object measure
component = coordinate_component
motion_rframe = existing marker
coordinate_rframe = existing marker
characteristic = measure_object_characteristic
object = existing object
from_first = boolean
legend = string
comments = string
Example:
measure create object &
measure_name = mea_object__1 &
from_first = yes &
component = x_component &
characteristic = angular_acceleration &
object = joint_2 &
create_measure_display = yes &
legend = "joint_2 object measure"
measure 9
Description:

measure_name New point measure Specifies the name of the new point
measure. You can use this name later to
refer to this measure.
component X_COMPONENT, Specifies the component in which you are
Y_COMPONENT, interested. The components available
Z_COMPONENT, depend on the coordinate system.
MAG_COMPONENT,
R_COMPONENT,
RHO_COMPONENT,
THETA_COMPONENT,
PHI_COMPONENT
motion_rframe Existing marker Specifies existing marker
coordinate_rframe Existing marker Specifies existing marker

characteristic ANGULAR_ACCELERATION, Specifies the object characteristic to be
ANGULAR_DEFORMATION, measured.
ANGULAR_DEFORMATION_VEL
OCITY,
ANGULAR_KINETIC_ENERGY,
ANGULAR_MOMENTUM_ABOU
T_CM, ANGULAR_VELOCITY,
AX_AY_AZ_PROJECTION_ANGLE
S, CM_ACCELERATION,
CM_ANGULAR_ACCELERATION,
CM_ANGULAR_DISPLACEMENT,
EULER_ANGLES,
CM_ANGULAR_VELOCITY,
CM_POSITION,
CM_POSITION_RELATIVE_TO_B
ODY, CM_VELOCITY,
CONTACT_POINT_LOCATION,
ELEMENT_FORCE,
ELEMENT_TORQUE,
INTEGRATOR_ORDER,
INTEGRATOR_STEPSIZE,
INTEGRATOR_TIME_STEP,
ITERATOR_STEPS,
ITERATION_COUNT,
KINETIC_ENERGY,
POTENTIAL_ENERGY_DELTA,
POWER_CONSUMPTION,
PRESSURE_ANGLE,
STATIC_IMBALANCE,
STRAIN_KINETIC_ENERGY,
TRANSLATIONAL_ACCELERATIO
N,
TRANSLATIONAL_DEFORMATIO
N,
TRANSLATIONAL_DEFORMATIO
N_VELOCITY,
TRANSLATIONAL_DISPLACEME
NT,
TRANSLATIONAL_KINETIC_ENE
RGY,
TRANSLATIONAL_MOMENTUM,
TRANSLATIONAL_VELOCITY
Object Existing object in Adams Enter the object to measure.
measure 11

legend String Specifies the text that will appear in the
top of the measure window.
comments String Specifies any comments on this measure.
Create_measure_di Yes/No Specifies yes if you want to display a strip
splay chart of the measure.
The measurable characteristics of objects are shown in the table below. Click an object characteristic to view
the description.
The object: Has these measurable characteristics:

Marker  Total force at point
 Total force at location
 Total_Torque_On_Point
 Total_Torque_At_Location
 Translational_Displacement
 Translational_Velocity
 Translational_Acceleration
 Angular_Velocity
 Angular_Acceleration
Rigid body  CM_Position

 CM_Velocity
 CM_Acceleration
 CM_Angular_Velocity
 CM_Angular_Acceleration
 Kinetic_Energy
 Translational_Kinetic_Energy
 Angular_Kinetic_Energy
 Translational_Momentum
 Angular_Momentum_About_CM
 Potential_Energy_Delta
Point mass body  CM_Position
 CM_Velocity
 CM_Acceleration
 Kinetic_Energy
measure 13

Flexible body  CM_Position
 CM_Velocity
 CM_Acceleration
 Kinetic_Energy
 Angular_Momentum_ About_CM
 Strain_Energy
Spring-damper force,  element_force
single-component  element_torque
force, field force,
 translational_displacement
bushing force
 ax_ay_az_projection_angles
 translational_velocity
 translational_acceleration
 angular_velocity
 angular_acceleration
Joint constraint,  element_force

joint primitive  element_torque
constraint
Curve-curve  pressure_angle
constraint, point-curve  element_force
constraint
 contact_point_location
measure create orient

Joint motion, general  power_consumption
point motion  element_force
 element_torque
Three-component  element_force
force, three-  element_torque
component torque,
general force/torque
Contact force  element_force
 element_torque
Double-click a ack to view:
 I_Point
 I_Normal_Force
 I_Friction_Force
 I_Normal_Unit_Vector
 I_Friction_Unit_Vector
 J_Point
 J_Normal_Force
 J_Friction_Force
 J_Normal_Unit_Vector
 J_Friction_Unit_Vector
 Slip_Deformation
 Slip_Velocity
 Penetration

Creates an orientation measure. Orientation measures capture the orientation characteristics of one part or
marker relative to another coordinate system in a specified convention. For example, you could use
orientation measures to determine the:
 Yaw angle associated with a yaw, pitch, roll, or body-fixed 321 rotation sequence.
measure 15
 First Euler parameter.

 Second rotation associated with a body-fixed 123 rotation sequence.
All such orientation characteristics are simply transformed from the direction cosine matrix.
The following example shows two markers whose orientation relative to each other can be captured using
orientation angles. When associated with a body-fixed 313 rotation sequence, the example returns the
rotation angles 1 = +90 °, 1 = +90 °, an d 1 = +90°.
Format:
measure_name = name for the orientation measure
component = orientation_component
characteristic = measure_orient_characteristic
to_frame = an existing model, part or marker
from_frame = an existing model, part or marker
legend = string
Example:
measure create orient &
measure_name = mea_orient__1 &
component = angle_1_component &
characteristic = yaw_pitch_roll &
to_frame = part_2 &
from_frame = part_3 &
legend = "orientation of yaw pitch"
Description:
measure 17

measure_name New mea_orient Specifies name for the measure to be created
component ANGLE_1_COMPONENT, Specifies the rotational component you want
ANGLE_2_COMPONENT, to measure.
ANGLE_3_COMPONENT,
PARAM_1_COMPONENT,
PARAM_2_COMPONENT,
PARAM_3_COMPONENT,
PARAM_4_COMPONENT,
MAT_1_1_COMPONENT,
MAT_1_2_COMPONENT,
MAT_1_3_COMPONENT,
MAT_2_1_COMPONENT,
MAT_2_2_COMPONENT,
MAT_2_3_COMPONENT,
MAT_3_1_COMPONENT,
MAT_3_2_COMPONENT,
MAT_3_3_COMPONENT
measure 19

characteristic EULER_ANGLES, Specifies the Characteristic convention with
YAW_PITCH_ROLL, which to associate the component.
AX_AY_AZ_PROJECTION_
ANGLES,
BRYANT_ANGLES,
BODY_1_2_3,
BODY_2_3_1,
BODY_3_1_2,
BODY_1_3_2,
BODY_2_1_3,
BODY_3_2_1,
BODY_1_2_1,
BODY_1_3_1,
BODY_2_1_2,
BODY_2_3_2,
BODY_3_1_3,
BODY_3_2_3,
SPACE_1_2_3,
SPACE_2_3_1,
SPACE_3_1_2,
SPACE_1_3_2,
SPACE_2_1_3,
SPACE_3_2_1,
SPACE_1_2_1,
SPACE_1_3_1,
SPACE_2_1_2,
SPACE_2_3_2,
SPACE_3_1_3,
SPACE_3_2_3,
EULER_PARAMETERS,
RODRIGUEZ_PARAMETE
RS, DIRECTION_COSINES
to_frame Existing model, part or marker Enter the coordinate system to which to
measure
from_frame Existing model, part or marker Enter the coordinate system from which to
measure.
create_measure_display Yes/No Specifies yes if you want to display the strip
chart.
legend String Specifies the text that will appear at the top of
the created measure.
measure create point
1. The orientation characteristics that you can measure are shown in the table below
The object: Has the measurable characteristics:

Part or  Euler angles
marker  Yaw, pitch, roll
 Ax, ay, az projection angles
 Bryant angles
 Any of 12 body - or space-fixed rotation sequences (123, 132, and so on)
 Euler parameters
 Rodriguez parameters
 Direction cosines
Notes: Euler parameters are P0, P1, P2, and P3. P0 is the cosine of one-half the
angle of rotation of the rotated frame with respect to the reference frame. P1, P2,
and P3 are the x, y, and z components, respectively, of the unit vector around
which the rotation occurs, multiplied by the sine of one-half the angle. Rodriguez
parameters (R1, R2, and R3) define the relative rotation between two frames of
reference. The relationship between Rodrigues parameters and Euler parameters is
R1 = P1/P0, R2 =P2/P0, and R3 = P3/P0. Rodriguez parameters become
undefined when P0 = 0, that is, when the angle of rotation about the vector is 180
degrees.
 Many dynamics textbooks define some or all of these orientation schemes. Refer
to:
• Meriam, Kraige. Engineering Mechanics, Vol. 2 . John Wiley & Sons, 1992.
• Greenwood. Principles of Dynamics, Second Edition. Prentice-Hall, Inc., 1988.
• Kane, Likins, Levinson. Spacecraft Dynamics. McGraw-Hill, 1983.
• Nikravesh. Computer-Aided Analysis of Mechanical Systems. Prentice-Hall Inc.,
1988.

This is a predefined measure that lets you capture and investigate Characteristics of a point, such as its
location relative to the global coordinate system or the sum of forces acting on it.
For example, you can use point measures to resolve a force at a specific location on a flexible body, or you can
determine the acceleration of the end marker of a pendulum with respect to the ground reference frame.
measure 21
Format:
measure_name = new point measure
characteristic = measure_point_characteristic
point = existing marker
legend = string
comments = string
Example:
measure create point &
measure_name = .model_1.mea_point_1 &
point = .model_1.part_3.marker_4 &
characteristic = " total_force_on_point " &
component = "mag_component" &
coordinate_rframe = .model_1.ground.marker_10&
comments = "point measure to capture the total force of
point marker_3" &
Description:

measure_name New point measure Specifies the name of the new
point measure. You can use this
name later to refer to this
measure.
component X_COMPONENT, Y_COMPONENT, Specifies the component in
Z_COMPONENT, which you are interested. The
MAG_COMPONENT, components available depend on
R_COMPONENT, the coordinate system.
RHO_COMPONENT,
THETA_COMPONENT,
PHI_COMPONENT
characteristic TOTAL_FORCE_ON_POINT, Specifies the kinematic and
TOTAL_TORQUE_ON_POINT, characteristic to be measured.
TOTAL_FORCE_AT_LOCATION,
TOTAL_TORQUE_AT_LOCATION,
TRANSLATIONAL_DEFORMATION,
ANGULAR_DEFORMATION_VELOC
ITY,
TRANSLATIONAL_DEFORMATION_
VELOCITY,
TRANSLATIONAL_DISPLACEMENT,
TRANSLATIONAL_VELOCITY,
TRANSLATIONAL_ACCELERATION,
ANGULAR_VELOCITY,
ANGULAR_DEFORMATION,
ANGULAR_ACCELERATION
point Existing marker Enter the marker or point to
measure.
legend String Specifies the text that will appear
in the top of the measure
window.
comments String Specifies any comments on this
measure.
Create_measure_display Yes/No Specifies yes if you want to
display a strip chart of the
measure.
measure 23
measure create pt2pt
Point Characteristics You Can Measure
The characteristics of markers that you can measure are shown in the table below. All types of markers have
the same measurable characteristics, but markers on flexible bodies have additional characteristics for
deformation
.
The object : Has the measurable characteristics:

Markers on a rigid body, point  total_force_on_point
mass, or flexible body  total_torque_on_point
 total_force_at_location
 total_torque_at_location
Markers on flexible body  angular_deformation
 angular_deformation_velocity
 angular_deformation_acceleration
 translational_deformation
 translational_deformation_velocity
 translational_deformation_acceleration

This is a predefined measure that lets you capture and investigate kinematic characteristics of a point relative
to another point, such as the relative velocity or acceleration. For example, you can use a point-to-point
measure to calculate the global y-component of distance between any two specified markers.
You can also obtain point-to-point characteristics for geometric vertices. When you select vertices for the
markers, Adams View automatically creates a marker at each vertex and uses it in the point-to-point measure.
Format:
measure_name = new point-to-point measure

characteristic = measure_pt2pt_characteristic
from_point = existing marker
to_point = existing marker
legend = string
comments = string
Example:
measure create pt2pt &
measure_name = .model_1.mea_pt2pt_1 &
to_point = .model_1.part_3.marker_4 &
characteristic = "translational_displacement" &
coordinate_rframe = .model_1.ground.marker_10 &
comments = "point 2 point measure to capture the
translational displacement of point marker_3" &
Description:

measure_name New point-point measure Specifies the name of the new point-
to-point measure.You can use this
name later to refer to this measure.
component X_COMPONENT, Specifies the component in which
Y_COMPONENT, you are interested. The components
Z_COMPONENT, available depend on the coordinate
MAG_COMPONENT, system.
R_COMPONENT,
RHO_COMPONENT,
THETA_COMPONENT,
PHI_COMPONENT
measure 25
measure create query

characteristic TRANSLATIONAL_DISPLACEM Specifies the kinematic characteristic
ENT, to be measured. The values you enter
TRANSLATIONAL_VELOCITY, next in the command depend on
TRANSLATIONAL_ACCELERAT whether you select a translational or
ION, ANGULAR_VELOCITY, angular characteristics.
ANGULAR_ACCELERATION
from_point Existing marker Enter the marker or point from
which to measure.
to_point Existing marker Enter the marker or point to which
to measure
legend String Specifies the text that will appear in
the top of the measure window.
measure.
Create_measure_display Yes/No Specifies yes if you want to display a
strip chart of the measure.
The point-to-point kinematic characteristics that you can measure are shown in the table below.

Two markers  Translational displacement
 Translational velocity
 Translational acceleration
 Angular velocity (not available when creating a point-to-point measure from the
Main toolbox)
 Angular acceleration (not available when creating a point-to-point measure from
the Main toolbox)

Format:
measure_name = new mea_query
gui_driver_name = existing gi_gui
delay_time = time
measure create range

legend = string
Description:

measure_name New name for the measure Specifies name for the new measure to
be created
gui_driver_name Existing graphic user interface Specifies an existing graphic user
interface
delay_time Time Specifies the time delay
initial_condition Real Specifies the initial condition
create_measure_display Yes/No Specifies yes if you want to display the
strip chart
legend String Specifies the text that will appear at the
top of the measure dialog.

Allows you to use range measures to obtain statistical feedback about any existing measure. Ranges
dynamically calculate the maximum, minimum, average, or variation characteristics of any measure.
Format:
measure_name = new mea_range
type = range_type
of_measure_name = existing measure name
legend = string
Example:
measure create range &
measure_name = range_mea_angle_measure &
tpe = maximum &
of_measure_name = my_mea_angle__1 &
measure 27
measure delete
measure create range &

legend = "maximum angle between the links"
Description:

measure_name New Name For The Range Specifies the name of the new measure to be
Measure created.
type Minimum, Maximum, Specifies type of the range measure.
Average, Variation, Same_as
of_measure_name Existing Measure Specifies existing, predefined measure to
analyze.
create_measure_display Yes/no Type Yes if you want to display the strip chart
of the measure.
legend String Specifies comments for the range measure.
Range Measure Characteristic Descriptions
The following table describes the characteristics that range measures provide. For information on the
conventions used, see Conventions.
The measure: Description: Definition/Formula:

Average Arithmetic mean of current set of measured data.
Minimum Minimum value in the current set of measured data. Min (M1, M2, ..., Mn)
Maximum Maximum value in the current set of measured data. Max (M1, M2, ..., Mn)
Variation Difference between the maximum and minimum value in Maximum - Minimum
the current set of measured data.
measure delete
This command will delete the specified marker.
measure modify angle
Format:
measure delete
Example:
measure delete &
measure_name = mea_1
Description:

Measure_name Existing measure Specifies an existing measure to be deleted.

This command will modify an existing angle measure.
Format:
measure_name = existing mea_angle
new_measure_name = new name for the measure
first_point = existing marker
middle_point = existing marker
last_point = existing marker
comments = string
legend = string
Example:
measure modify angle &
measure_name = angle_between_link1_link2 &
first_point = marker_2 &
last_point = marker_4 &
middle_point = marker_1 &
legend = "angle between two links" &
comments = "this measure will track the angle between
the two links"
measure 29
If Link1 and Link2 are connected by a revolute joint and Marker2 lies on Link1, Marker 3 lies on Link2 and
Marker 1 lies in the intersection of Link1 and Link2, then the above command will modify the existing angle
measure to compute the angle between the two links. The title of the measure will be the string specified in
the legend parameter.
Description:

measure_name Existing Meaure name Specifies the name of the existing angle measure.
New_measure_name New measure name Specifies the new name for the measure. You can use
this name later to specify this new angle measure
created.
first_point Existing marker Specifies an existing marker on an entity.
middle_point Existing marker Specifies an existing marker on an entity.
last_point Existing marker Specifies an existing marker on an entity.
Legend String Specifies the text that will appear at the top of the
Angle measure.
Comments String Specifies any comments that are to be associated with
this angle measure.
About Measuring Included Angle Characteristics
The included angle measure captures the instantaneous angle between two vectors defined by three markers.
For example, you can use the angle measure to find the included angle between any two links connected by
a revolute joint. The default unit for angle measures is degrees.
To create an included angle, you select three markers, as illustrated in the figure below. These three markers
define two vectors:
It is the instantaneous angle between these vectors that Adams View tracks in an included angle measure.
Note that the included angle changes over time as the markers move during a simulation.
Example of Points That Define Included Angles
measure modify computed
There are two conventions used in Adams View to define the sign and magnitude of an included angle
measure as it changes over time:
 The sign and magnitude is always calculated so as to have an initial value within the range [0, PI]
regardless of the order in which you select the points.
 The axis of rotation is automatically calculated as the cross-product of , which is sensitive

to the order in which you select the points. This, along with the right-hand rule, determines all
subsequent changes to the sign and magnitude of the included angle measure.

Allows you to modify an existing computed measure
Adams View computed measures allow you to create measures in the Adams View expression language that
can be evaluated before a simulation or any time after. You build them using design-time functions and
typically use them in the initial model set up.
An Adams View computed measure is convenient because it can reference any Adams View variable. For
example, if you create two measures and you want to add or subtract them, you can use an Adams View
computed measure to do so. You can also compute data from a run-time measure.
Format:
measure_name = existing computed measure
units = string
legend = string
comments = string
measure 31
measure modify function
Example:
Assuming that ADAMS_KE is an existing measure of the kinetic energy of a pendulum and MY_KE is an
existing analytical measure if the kinetic energy.
.
measure modify computed &

measure_name = my_computed_measure &
new_measure_name = ke_comparison_measure &
text_of_expression = “100*(.model_1.adams_ke - .model_1.my_ke)/322.6” &
units = “no_units” &
legend = “measure comparison of analytical and kinetic energy
results”
Description:

measure_name Existing measure name Specifies name of the existing computed measure to
be modified.
New_measure_name New measure name Specifies the new name for the measure.
text_of_expression String The TEXT_OF_EXPRESSION parameter defines
the computation to be performed by the function.
Remember that the value of this argument should be
a character string, NOT an expression.
units String Specifies units of the measure.
create_measure_display Yes/No Specifies whether the strip chart has to be displayed of
the measure.
Legend String Specifies the text that will appear at the top of the
created measure.
comments String Specifies any comments.
Cautions:
1. Be careful, however, about the changes you make in your model. Making changes can cause a
potential problem because model changes can invalidate the accuracy of any measure that depends on
the results of a simulation. The simulation redefines the model data and re-evaluates your Adams
View computed measures.

An Adams Solver function measure allows you to modify a measure in Adams View that Adams Solver
evaluates during simulations . Because Adams Solver function measures are only evaluated during
simulations, function measures remain unevaluated until you run a simulation. The Adams Solver function
measure is convenient because it lets you reference any user-defined Adams Solver function or subroutine .
Function measures are built from Adams Solver run-time functions.
Format:
measure function
measure_name = existing function measure
new_measure_name = new function measure name
function = function
routine = string
units = string
legend = string,
comments = string
Example:
measure modify function measure = .model_1.function_mea_1 &
new_measure_name = .model_1.my_function_mea &
function = "0.5*wz(.model_1.part_2.cm)**2*(15*(50**2 +
300**2) + 15000)/1000" &
units = no_units &
Description:

Measure_name String Specifies name of measure to be modified.
New_measure_name String Specifies new name of measure.
function Function Specifies function to be evaluated during the simulation.
user_function Real Specifies a real number
routine String Specifies a string for the routine.
units String Specifies any units that have to be associated.
measure 33
measure modify object

create_measure_display Yes/no Specifies yes if the strip chart of the measure needs to be
displayed.
legend String Specifies the text that will appear on the top of the
measure dialog.
Comments String Specifies any comments about the function measure.
Cautions:
1. Be careful, however, about the number of Adams Solver function measures you create because Adams
View writes each measure to the Adams Solver dataset as a VARIABLE statement. Each VARIABLE
statement adds another equation to the overall set of equations. The more equations Adams Solver
must solve, the longer your simulation takes.

Allows you to modify an existing object measure.
In general, all objects in your model have some pre-defined measurable characteristics. For example, you can
capture and investigate the power consumption of a motion, or measure a part’s center-of-mass velocity along
the global x-axis, taking time derivatives in the ground reference frame. The default coordinate system is the
ground coordinate system, but you can use any marker as the coordinate system.
Format:
measure_name = existing object measure
new_measure_name = new name for the object measure
characteristic = measure_object_characteristic
object = existing object
from_first = boolean
legend = string
comments = string
Example:
measure modify object &
measure_name = mea_object__1 &
from_first = yes &
component = y_component &
characteristic = angular_acceleration &
object = joint_2 &
legend = "joint_2 object measure"
Description:

measure_name Existing Point Measure Specifies the name of the existing point
measure that has to be modified.
New_measure_name New Name For The Point Measure Specifies the new name for the point
measure. You can use this name later to
refer to this measure.
component X_component, Y_component, Specifies the component in which you
Z_component, Mag_component, are interested. The components
R_component, Rho_component, available depend on the coordinate
Theta_component, Phi_component system.
motion_rframe Existing Marker Specifies existing marker
coordinate_rframe Existing Marker Specifies existing marker
measure 35

characteristic Angular_acceleration, Specifies the object characteristic to be
Angular_deformation, measured.
Angular_deformation_velocity,
Angular_kinetic_energy,
Angular_momentum_about_cm,
Angular_velocity,
Ax_ay_az_projection_angles,
Cm_acceleration,
cm_angular_acceleration,
Cm_angular_displacement,
Euler_angles, Cm_angular_velocity,
Cm_position,
Cm_position_relative_to_body,
Cm_velocity, Contact_point_location,
Element_force, Element_torque,
Integrator_order, Integrator_stepsize,
Integrator_time_step, Iterator_steps,
Iteration_count, Kinetic_energy,
Potential_energy_delta,
Power_consumption, Pressure_angle,
Static_imbalance, Strain_kinetic_energy,
Translational_acceleration,
Translational_deformation,
Translational_deformation_velocity,
Translational_displacement,
Translational_kinetic_energy,
Translational_momentum,
Translational_velocity
Object Existing Object In Adams Enter the object to measure.
measure.
Create_measure_displ Yes/no Specifies yes if you want to display a
ay strip chart of the measure.
The measurable characteristics of objects are shown in the table below. Click an object characteristic to view
the description.

Marker  Total force at point
 Total force at location
 Total_Torque_On_Point
 Total_Torque_At_Location
 Translational_Displacement
 Translational_Velocity
 Translational_Acceleration
 Angular_Velocity
 Angular_Acceleration
Rigid body  CM_Position

 CM_Velocity
 CM_Acceleration
 Kinetic_Energy
 Angular_Momentum_About_CM
Point mass body  CM_Position
 CM_Velocity
 CM_Acceleration
 Kinetic_Energy
measure 37

Flexible body  CM_Position
 CM_Velocity
 CM_Acceleration
 Kinetic_Energy
 Angular_Momentum_ About_CM
 Strain_Energy
Spring-damper force,  element_force
single-component force,  element_torque
field force, bushing force
Joint constraint,  element_force

joint primitive constraint  element_torque
Curve-curve constraint,  pressure_angle

point-curve constraint  element_force
 contact_point_location
measure modify orient

Joint motion, general point  power_consumption
motion  element_force
 element_torque
Three-component force,  element_force

three-component torque,  element_torque
general force/torque
Contact force  element_force

 element_torque
Double-click a rack to view:
 I_Point
 I_Normal_Force
 I_Friction_Force
 I_Normal_Unit_Vector
 I_Friction_Unit_Vector
 J_Point
 J_Normal_Force
 J_Friction_Force
 J_Normal_Unit_Vector
 J_Friction_Unit_Vector
 Slip_Deformation
 Slip_Velocity
 Penetration

Allows you to modify an orientation measure. Orientation measures capture the orientation characteristics of
one part or marker relative to another coordinate system in a specified convention. For example, you could
use orientation measures to determine the:
 Yaw angle associated with a yaw, pitch, roll, or body-fixed 321 rotation sequence.
measure 39
 First Euler parameter.

 Second rotation associated with a body-fixed 123 rotation sequence.
All such orientation characteristics are simply transformed from the direction cosine matrix.
The following example shows two markers whose orientation relative to each other you can capture using
orientation angles. When associated with a body-fixed 313 rotation sequence, the example returns the
rotation angles 1 = +90 °, 1 = +90 °, an d 1 = +90°.
Format:
measure_name = name of existing orientation measure
component = orientation_component
characteristic = measure_orient_characteristic
to_frame = an existing model, part or marker
from_frame = an existing model, part or marker
legend = string
Example:
measure modify orient &
measure_name = mea_orient__1 &
new_measure_name = mea_yaw_orient &
component = angle_1_component &
characteristic = yaw_pitch_roll &
to_frame = part_2 &
measure modify orient &

from_frame = part_3 &
legend = "orientation of yaw pitch"
Description:

measure_name New mea_orient Specifies name for the measure to be
created
component Angle_1_component, Specifies the rotational component
Angle_2_component, you want to measure.
Angle_3_component,
Param_1_component,
Param_2_component,
Param_3_component,
Param_4_component,
Mat_1_1_component,
Mat_1_2_component,
Mat_1_3_component,
Mat_2_1_component,
Mat_2_2_component,
Mat_2_3_component,
Mat_3_1_component,
Mat_3_2_component,
Mat_3_3_component
characteristic Euler_angles, Yaw_pitch_roll, Specifies the Characteristic
Ax_ay_az_projection_angles, convention with which to associate
Bryant_angles, Body_1_2_3, the component.
Body_2_3_1, Body_3_1_2,
Body_1_3_2, Body_2_1_3,
Body_3_2_1, Body_1_2_1,
Body_1_3_1, Body_2_1_2,
Body_2_3_2, Body_3_1_3,
Body_3_2_3, Space_1_2_3,
Space_2_3_1, Space_3_1_2,
Space_3_2_3, Euler_parameters,
Rodriguez_parameters,
Direction_cosines
measure 41

to_frame Existing model, part or marker Enter the coordinate system to which
to measure
from_frame Existing Model, Part Or Marker Enter the coordinate system from
which to measure.
create_measure_display Yes/no Specifies yes if you want to display the
strip chart.
legend String Specifies the text that will appear at
the top of the created measure.
1. The orientation characteristics that you can measure are shown in the table below.
.

Part or  Euler angles
marker  Yaw, pitch, roll
 Ax, ay, az projection angles
 Bryant angles
 Any of 12 body - or space-fixed rotation sequences (123, 132, and so on)
 Euler parameters
 Rodriguez parameters
 Direction cosines
Note:
 Euler parameters are P0, P1, P2, and P3. P0 is the cosine of one-half the angle of
rotation of the rotated frame with respect to the reference frame. P1, P2, and P3
are the x, y, and z components, respectively, of the unit vector around which the
rotation occurs, multiplied by the sine of one-half the angle. Rodriguez parameters
(R1, R2, and R3) define the relative rotation between two frames of reference. The
relationship between Rodrigues parameters and Euler parameters is R1 = P1/P0,
R2 =P2/P0, and R3 = P3/P0. Rodriguez parameters become undefined when P0 =
0, that is, when the angle of rotation about the vector is 180 degrees.
 Many dynamics textbooks define some or all of these orientation schemes. Refer
to:
• Meriam, Kraige. Engineering Mechanics, Vol. 2 . John Wiley & Sons, 1992.
• Greenwood. Principles of Dynamics, Second Edition. Prentice-Hall, Inc., 1988.
• Kane, Likins, Levinson. Spacecraft Dynamics. McGraw-Hill, 1983.
• Nikravesh. Computer-Aided Analysis of Mechanical Systems. Prentice-Hall Inc.,
1988.
measure modify point

Allows you to modify an existing point measure.
This is a predefined measure that lets you capture and investigate Characteristics of a point, such as its
location relative to the global coordinate system or the sum of forces acting on it.
For example, you can use point measures to resolve a force at a specific location on a flexible body, or you can
determine the acceleration of the end marker of a pendulum with respect to the ground reference frame.
Format:
measure_name = existing point measure
new_measure_name = new name for measure
characteristic = measure_point_characteristic
point = existing marker
legend = string
comments = string
Example:
measure modify point &
measure_name = .model_1.mea_point_1 &
new_measure_name = mea_my_point &
point = .model_1.part_3.marker_4 &
characteristic = " total_force_on_point " &
comments = "point measure to capture the total force of
point marker_3" &
measure 43
Description:

measure_name Existing point measure Specifies the name of an existing
point measure to be modified.
New_measure_name New name for the measure Specifies the new name for the
measure. You can use this name
later to refer to this measure.
component X_component, Y_component, Specifies the component in
Z_component, Mag_component, which you are interested. The
R_component, Rho_component, components available depend on
Theta_component, Phi_component the coordinate system.
characteristic Total_force_on_point, Specifies the kinematic and
Total_torque_on_point, characteristic to be measured.
Total_force_at_location,
Total_torque_at_location,
Translational_deformation,
Angular_deformation_velocity,
Translational_deformation_velocity,
Translational_displacement,
Translational_velocity,
Translational_acceleration, Angular_velocity,
Angular_deformation, Angular_acceleration
point Existing Marker Enter the marker or point to
measure.
legend String Specifies the text that will appear
in the top of the measure
window.
measure.
Create_measure_displa Yes/no Specifies yes if you want to
y display a strip chart of the
measure.
Point Characteristics You Can Measure
The characteristics of markers that you can measure are shown in the table below. All types of markers have
the same measurable characteristics, but markers on flexible bodies have additional characteristics for
deformation.
measure modify pt2pt
The object : Has the measurable characteristics:

Markers on a rigid body,  total_force_on_point
point mass, or flexible body  total_torque_on_point
 total_force_at_location
 total_torque_at_location
Markers on flexible body  angular_deformation
 angular_deformation_velocity
 angular_deformation_acceleration
 translational_deformation
 translational_deformation_velocity
 translational_deformation_acceleration

Allows you to modify an existing point-to-point measure.
This is a predefined measure that lets you capture and investigate kinematic characteristics of a point relative
to another point, such as the relative velocity or acceleration. For example, you can use a point-to-point
measure to calculate the global y-component of distance between any two specified markers.
You can also obtain point-to-point characteristics for geometric vertices. When you select vertices for the
markers, Adams View automatically creates a marker at each vertex and uses it in the point-to-point measure.
Format:
measure_name = existing point-to-point measure
motion_rframe= existing marker
characteristic = measure_pt2pt_characteristic
from_point = existing marker
measure 45

to_point = existing marker
legend = string
comments = string
Example:
measure modify pt2pt &
measure_name = .model_1.mea_pt2pt_1 &
new_measure_name = .model_1.mea_pt_to_pt &
to_point = .model_1.part_3.marker_4 &
characteristic = "translational_displacement" &
comments = "point 2 point measure to capture the
translational displacement of point marker_3" &
Description:

measure_name Existing point-point measure Specifies the name of an existing point-to-
point measure to be modified.
New_measure_name New name for the measure Specifies the new name for the measure.
You can use this name later to refer to this
measure.
component X_component, Y_component, Specifies the component in which you are
Z_component, Mag_component, interested. The components available
R_component, Rho_component, depend on the coordinate system.
Theta_component, Phi_component
characteristic Translational_displacement, Specifies the kinematic characteristic to be
Translational_velocity, measured. The values you enter next in
Translational_acceleration, the command depend on whether you
Angular_velocity, select a translational or angular
Angular_acceleration characteristics.
measure modify query

from_point Existing Marker Enter the marker or point from which to
measure.
to_point Existing Marker Enter the marker or point to which to
measure
comments String Specifies any comments on this measure.
Create_measure_displa Yes/No Specifies yes if you want to display a strip
y chart of the measure.
The point-to-point kinematic characteristics that you can measure are shown in the table below.

Two markers  Translational displacement
 Translational velocity
 Translational acceleration
 Angular velocity (not available when creating a point-to-point measure from the
Main toolbox)
 Angular acceleration (not available when creating a point-to-point measure from the
Main toolbox)

Allows you to modify an existing query.
Format:
measure_name = existing mea_query
new_measure_name = new name for query
gui_driver_name = existing gi_gui
delay_time = time
legend = string
measure 47
measure modify range
Description:

measure_name Existing measure Specifies name for the existing measure to be
modified.
New_measure_name New measure name Specifies the new name for the measure.
gui_driver_name Existing graphic user Specifies an existing graphic user interface
interface
delay_time Time Specifies the time delay
initial_condition Real Specifies the initial condition
create_measure_display Yes/No Specifies yes if you want to display the strip chart
legend String Specifies the text that will appear at the top of the
measure dialog.

Allows you to modify an existing range measure.
You can use range measures to obtain statistical feedback about any existing measure. Ranges dynamically
calculate the maximum, minimum, average, or variation characteristics of any measure.
Format:
measure_name = existing mea_range
new_measure_name = new mea_range name
type = range_type
of_measure_name = existing measure name
legend = string
Example:
measure modify range &
measure_name = range_mea_angle_measure &
new_measure_name = range_angle_measure &
tpe = maximum &
of_measure_name = my_mea_angle__1 &
legend = "maximum angle between the links"
Description:

measure_name existing range measure Specifies the name of the existing measure to be
modified.
New_measure_name New name for the measure Specifies the new name for the measure.
type Minimum, Maximum, Specifies type of the range measure.
Average, Variation, Same_as
of_measure_name Existing measure Specifies existing, predefined measure to
analyze.
create_measure_display, Yes/No Type Yes if you want to display the strip chart of
the measure.
legend String Specifies comments for the range measure.
1. Range Measure Characteristic Descriptions
The following table describes the characteristics that range measures provide. For information on the
conventions used, see Conventions.
The measure: Description: Definition/Formula:

Average Arithmetic mean of current set of measured
data.
Minimum Minimum value in the current set of Min (M1, M2, ..., Mn)
measured data.
Maximum Maximum value in the current set of Max (M1, M2, ..., Mn)
measured data.
Variation Difference between the maximum and Maximum - Minimum
minimum value in the current set of
measured data.
measure_display 1
measure_display create
measure_display
Allows you to transfer the plot on the strip chart to full_plot creation of a measure_display for an existing
measure.
A measure gauge particular quantities in your model during a simulation . For example, you can measure the
force in a spring throughout a simulation or the angle between two points or axes. The measure once created
can be displayed as a strip chart or can be transferred to full plot.
The measured quantity is displayed against TIME as default axis, or it can be displayed against any
‘independent_measure’ existing in the model.
Format:
measure_name = an existing measure
mea_display = a new mea_display
independent_measure_name = an existing measure
Example:
measure_display create &
mea_display = .model_1.mdsp &
measure_name = .model_1.msr &
independent_measure_name = .model_1.mea_3
Description:

measure_name An Existing Measure Specifies the name of an existing measure
mea_display A New Mea Display Specifies a new name for the new measure display
independent_measure_name An Existing Measure Specifies an existing as abscissa along which the
new measure is displayed
1. While creating a measure a strip chart of the measure can be displayed by clicking the toggle button
to ‘create strip chart’. If a display of the measure at an later stage, it can be created using this
command.
measure_display delete
2. The command ‘measure_display create’ will create a display of an existing measure, the quantity
variation being displayed along default axis as ‘TIME’, when ‘independent_measure_name’ is not
specified. For example, the ‘ANGLE’ turned by a revolute joint with respect to ‘TIME’ will give the
angular velocity measure of the joint.
3. If the quantity is to be displayed with respect to any parameter other than default ‘TIME’, e.g., the
variation in ‘FORCE’ with respect to ‘ANGLE’ turned by crank, then two measured are first created
for force and angle. Then the new measure is created for ‘measure_name’ FORCE and the
‘independent_measure_name’ as ANGLE. This will display the variation in force with respect to the
angle.
Allows deletion of a measure_display for an existing measure.
Format:
Example:
measure_display delete &
mea_display = .model_1.disp2_display
Description:

The existing measure_display can be deleted by choosing the display name while ‘delete’ command. On the
other hand, if the measure display if closed then it can be redisplayed by ‘measure’-‘display’ from the main
menu.
measure_display 3
measure_display full_plot
Allows transferring the plot on the strip chart to full_plot creation of a measure_display for an existing
measure.
Format:
mea_display = a new mea_display
independent_measure_name = an existing measure
Example:
measure_display full_plot &
mea_display = .model_1.mdsp &
measure_name = .model_1.msr &
independent_measure_name = .model_1.MEA_3
Description:

mea_display A New Mea Display Specifies a new name for the new measure display
independent_measure_name An Existing Measure Specifies an existing as abscissa along which the
new measure is displayed
1. While creating a measure a strip chart of the measure can be displayed by clicking the toggle button
to ‘create strip chart’. If a display of the measure at an later stage, it can be created using this
command.
2. The command ‘measure_display create’ will create a display of an existing measure, the quantity
variation being displayed along default axis as ‘TIME’, when ‘independent_measure_name’ is not
specified. For example, the ‘ANGLE’ turned by a revolute joint with respect to ‘TIME’ will give the
angular velocity measure of the joint.
measure_display save_curve
3. If the quantity is to be displayed with respect to any parameter other than default ‘TIME’, e.g., the
variation in ‘FORCE’ with respect to ‘ANGLE’ turned by crank, then two measured are first created
for force and angle. Then the new measure is created for ‘measure_name’ FORCE and the
‘independent_measure_name’ as ANGLE. This will display the variation in force with respect to the
angle.
Allows to save the curve on the measure_display.
A measure gauge particular quantities in your model during a simulation. For example, you can measure the
Format:
mea_display = an existing mea_display
Example:
measure_display save_curve &
mea_display = mdsp
Description:

mea_display An Existing Mea_display Specifies the name of an existing measure display
The curve on strip chart is replaced by a new curve, whenever a new simulation is carried out. In case it is
necessary to retain the current curve from current simulation to compare with a new curve displayed after a
new simulation, the current curve can be saved. Thus, the new curve will be superimposed on the current
one facilitating comparison of the curves.
model 1
model assemble
model
model assemble
Allows you to merge several models into one big model.
Format:
model assemble
new_model_name = a new model
model_names = an existing model
prefix = string
suffix = string
translation = location
rotation = orientation
duplicate_parts = dupl_part_action
add_to_group_name = a new or existing group
Example:
model assemble &
new_model_name = model__1 &
model_names = crankshaft , model_1 &
prefix = "new_" &
translation = 10 , 10 , 10 &
rotation = 0 , 0 , 0 &
duplicate_parts = rename
Description:

new_model_name A New Model The model into which the models specified by
'model_names' will be merged.
model_names An Existing Model Specifies a list of existing models in Adams View, to
be merged to create an assembled model.
prefix String This parameter specifies the list of prefixes that are
applied to all entities at the part level as they are
assembled into a destination model.
model assemble

suffix String This parameter specifies the list of suffixes that are
applied to all entities at the part level, as they are
assembled into a destination model.
translation Location Specifies the translations (relative to the global origin)
that are applied to the parts, polylines, and notes
beneath the source model before it is merged with the
destination model.
rotation Operation Specifies the rotations (about to the global origin)
that are applied to the parts, polylines, and notes
beneath the source model before it is merged with the
destination model.
duplicate_parts Dupl_Part_Action Specifies what to do when a part in the destination
model has the same name as a part in the source
model.
add_to_group_name A New or Existing Group This parameter specifies a new or existing group into
which Adams View will add all merged objects.
1. The "model_names" lists the source of the objects being merged and the "new_model_name" names
the destination model. The source models are not changed after the assemble operation.
You can specify a set of translations and rotations that are applied to the parts, polylines, and notes of
each source model before it is merged with the assembled model.
If you specify that parts with the same name in both models (duplicate parts) are to be merged, then
all of the children beneath the parts of the source model will be copied beneath the corresponding
parts in the assembled model. Otherwise, the duplicate parts in the source model will be copied and
renamed in the destination model.
MODEL MERGE VS. MODEL ASSEMBLE
Although the "model merge" and "model assemble" commands accomplish much the same thing,
there are several differences between them. These differences are
a. If ground parts are not merged during a "model assemble", then they will be constrained to
ground with an automatically created fixed joint. ("Ground" is what was originally ground in
the the first model in the "model_names" list.)
The auto-created fixed joints for the ground parts are named
"fixed_ORIGINAL_MODEL_NAME"; the markers are named,
"fixed_i_ORIGINAL_MODEL_NAME" and "fixed_j_ORIGINAL_MODEL_NAME" with
the J marker going to the assembled model's ground part and the I marker on the part that was
once a ground.
model 3
model attributes
b. In "model assemble", with the renaming of like-named parts, the ground parts for all but the first
model in the list are renamed "ground_ORIGINAL_MODEL_NAME" (unless the
prefixes/suffixes you specify are sufficient for distinguishing the ground names). In "model
merge", ground parts are renamed only if their names conflict, and then they are renamed the
same way as other parts (typically, "ground_2" or "ground_3").
c. As with "model copy", the "model assemble" command retains the Adams IDs for the first model;
all others may be changed if there are conflicts.
d. With "model assemble", you may relocate and/or reorient any of the models, including the first
one, as they are merged into the assembly.
e. With "model assemble", gravity forces are eliminated from all but the first model. If the first
model has no gravity, then there will be no gravity in the assembly. In a "model merge", duplicate
gravity forces are renamed (usually, something like "gravity_2").
f. The model assemble command is much faster than using the copy, merge strategy for creating an
assembly of models. You will often see a four-fold improvement in performance by using "model
assemble" instead of a "model copy", "model merge" sequence.
associated with it.
3. If you specify that duplicate parts are to be merged, then all the children beneath the parts of the
source model will be copied beneath the corresponding parts in the destination model. Otherwise,
the duplicate parts in the source model will be copied and renamed in the destination model.
4. The add_to_group parameter specifies a new or existing group into which Adams View will add all
merged objects. All objects that were copied from the source model into the destination model will
be added to the specified group.
Cautions:
1. The source entities are not changed by the assemble operation.
model attributes
Allows you to set specification of attributes on the entire model.
model attributes
Format:
model attributes
name_ visibility = on_off_with_toggle
Example:
model attributes &
model_name = model__1 &
visibility = on &
color = blue &
active = on &
Description:

model_name An Existing Model Specifies the model to be modified. You use this parameter
command.
scale_of_icons Real Specifies a unit-less scale factor to apply to the current icon
size.
size_of_icons Real Specifies the size, in modeling units, the Adams View icons
will appear in.
name_ visibility On_Off_With_Toggle The NAME_VISIBILITY parameter provides control over
the visibility of the view name displayed in the top center
model 5
model attributes

color An Existing Color Specifies the color the modeling entity should be drawn in.
active On_Off_No_Opinion Set the activation of the element
dependents_active On_Off_No_Opinion Set the activation of the dependants of an element
entity_scope Color_Scope The ENTITY_SCOPE parameter is used to control how a
color modification is to affect a particular graphic entity.
- SIZE_OF_ICONS / SCALE_OF_ICONS. These two parameters are mutually exclusive. You may
set a size of the icon used for the marker representation in modeling units, or you may scale the size
of the icon by a non-unit scale factor.
- VISIBILITY. You may set a marker's visibility ON, OFF or TOGGLE the current setting. When
you set a marker's visibility OFF, the marker will not be drawn. When you set a marker's visibility
ON, you allow that marker to be drawn.
- NAME_VISIBILITY. You may set a marker's name label visibility ON, OFF or TOGGLE the
- COLOR. You may set the color of a marker with this parameter.
ATTRIBUTE may be inherited from another entity. INHERITANCE may either be TOP_DOWN
or BOTTOM_UP.
is a tree structure with the model at the apex.
Parts exist beneath the model, and markers exist beneath the parts.
If the icon size of the model is set to 0.1, and the default INHERITANCE is set to TOP_DOWN,
then all icons displayed within the model will be displayed in this size. However, if the icon size of a
model is set to 0.1, and then the default INHERITANCE is set to BOTTOM_UP, then any icons
set to a size other than the model's icon size will be displayed in their own size.
associated with it.
in length.
model attributes
in length.
An Example:
If the model has SIZE_OF_ICONS set to 0.0 , and a part under that model has its
An Example:
model ---------------------- SIZE_OF_ICONS = 0.0 meters
The part's icon will be .125 meters in size.
in the top center position of a given view.
The legal values of this parameter are ON and OFF. This is an optional parameter and if not entered,
the name will be visible (that is, will be ON).
Specifying 'NO_COLOR' for a modeling entity instructs Adams View to use the default color for
Example 1:
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2:
model 7
model attributes
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3:
.model -------------------------NO_COLOR
.part ---------------------- NO_COLOR
for the dependents all the way down the dependency chain. For example, if you execute the following
command:
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
ALL.
FILL_COLOR is the color of those areas of a graphic that can be shaded (they include sides of
cylinders, frustums, boxes, etc.) The EDGE_COLOR is the color of the lines making up the edges
model copy
springdamper.
model copy
Allows you to create a replica model.
Format:
model copy
time = time
include_contact_steps = integer
Example:
model copy &
view_name = view_1
Description:

new_model_name A New Model Specifies the name of the new model. You may use this
name later to refer to this model.
analysis_name An Existing Analysis Specifies the name of an analysis.
model 9
model copy

frame_number Integer Specifies the frame number (Adams simulation
output time step) at which to configure the new
model.
time Time Allows you to identify the frame number (Adams
simulation output time step) at which to configure
the new model.
view_name An Existing View Specifies the view in which to display this model.
Include_contact_steps Integer
1. You can either copy a model as it was created, or at a specified frame/time step of an analysis.
If you use the MODEL_NAME parameter, the replica model will be identical to the original with
the exception of the model name. All modeling entities under the original model will be copied to the
replica and have the same names, including the analysis data.
If you use the ANALYSIS_NAME parameter, the replica model will contain all the modeling entities
under the original model, including the analyses. The part positions (locations and orientations) and
the dynamic polyline shapes will be modified to match what they would be at the time, or frame, you
specify.
Models must have unique names relative to other models in Adams View.
The replica will be completely independent of the original, and may be modified without affecting
the original.
associated with it.
model create
be assigned to it
analysis name without reading in an analysis file, use the "defaults analysis" command.
time step). If a value greater than the last frame number is entered, the system will display the last
frame.
6. The frame with the time value closest to the time specified in this parameter will be selected. Adams
View will use the last frame if the time entered is greater than the time for the last frame in the
simulation.
7. You may identify a view by typing its name or by picking it from the screen. In most cases, you may
enter the special view name 'all', which means all the views currently displayed.
You must separate multiple view names by commas. You need not separate multiple view picks by
commas.
Cautions:
1. Adams View will not allow you to have two models with the same name, so you must provide a unique
name.
model create
Allows you to create a model. You may reverse this creation at a later time with an UNDO command. You
can also create models as children of other models.
Format:
model create
model_name = a new model
comments = string
title = string
fit_to_view = boolean
model 11
model create
Example:
model create &
comments = "a new model" &
title = model1 &
view_name = view__1 &
fit_to_view = yes
Description:

model_name A New Model Specifies the name of the new model. You may use this name later
to refer to this model.
title String Specifies the title of model
fit_to_view Boolean The FIT_TO_VIEW parameter is used to control whether or not
to compute the extents of the model or part before displaying the
model or part in a view.
1. In order to build a mechanism in Adams View, you must first create a model object in the Adams
View database. You then add parts and other objects to the model. As you are developing your
model, you may display it, verify it, and change its attributes.
Once you have created a model, you add parts to it with the 'PART CREATE RIGID_BODY
NAME_AND_POSITION' command. After you have created your first part or two, you can
continue creating parts, or you may wish to start putting markers on the parts so you can add
geometry, constraints, and forces. You use the 'MARKER CREATE' command to add markers to a
part. Adding markers may help you position other parts, and creating geometry with markers will
help you visualize your model as you are constructing it.
When your model is complete, you use the 'OUTPUT_CONTROL' command to request Adams
output, write an Adams data set, and then analyze it with Adams. If your analysis is fairly simple, you
may use the 'SUBMIT' command to write the dataset and invoke Adams.
model delete
be assigned to it
4. The title is a character string up to 80 characters which describes the model. It is used as the TITLE
statement in the Adams DATA SET (.adm file)
commas.
Cautions:
name.
model delete
Allows you to delete an existing model.
Format:
model delete
Example:
model delete &
model_name = crankshaft
model 13
model delete
Description:

model_name An Existing Model Specifies the model to be deleted
analysis_name An Existing Analysis Specifies the analysis to be deleted
1. You must enter the name of the model you wish to delete either by picking it from the screen or
menu entry, 'UNDO'.
You may identify a model by typing its name or by picking it from the screen.
associated with it.
3. Any AdamsAdamsAdams View object you delete, may be "undeleted" by using the UNDO
commands. If you have deleted something you would like back, enter the command "undo
backward", or pick on the fixed menu entry 'UNDO'.
You may identify an analysis by typing its name or by picking it from the screen.
be entered.
associated with it.
Tips:
model display
model display
Allows you to display the model in the specified view. If no view has been specified, the model will be
displayed in the active view.
Format:
model display
fit_to_view = boolean
Example:
model display &
fit_to_view = yes
Description:

view_name An Existing View Specifies the view in which to display this model
fit_to_view Boolean The FIT_TO_VIEW parameter is used to control whether or not
to compute the extents of the model or part before displaying the
model or part in a view.
1. 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.
associated with it.
model 15
model generate_ids
commas.
model generate_ids
This command sets the adams_ids of all objects that are descendents of the specified models. The adams_ids
can be set to positive integers, as required by Adams Solver or can be all set to zero.
Format:
model generate_ids
model_names = Names of the existing models
zero_ids = yes/no
Example:
model generate_ids &
model_names = .model_1, .model_2 &
zero_ids = yes
Description:

model_names String Existing model name (s) whose descendents will have their
adams_ids set.
zero_ids yes/no If set to yes, adams_ids will be set to zero.
If set to no, adams_ids will be set to positive integers.
model merge
Allows you to merge one model into another. The 'model_name' model is the source of the objects being
merged and the 'into_model_name' model is the destination model. The rotation is performed on the model
and then it is translated.
model merge
Format:
model merge
into_model_name = an existing model
translation = location
rotation = orientation
duplicate_parts = dupl_part_action
add_to_group_name = a new or existing group
Example:
model merge &
into_model_name = crankshaft &
translation = 10 , 10 , 10 &
rotation = 0 , 0 , 0 &
duplicate_parts = merge
Description:

into_model_name An Existing Model The model into which the model specified by
'model_name' will be merged.
translation Location This parameter specifies the translations (relative to
the global origin) that are applied to the parts,
polylines, and notes beneath the source model,
before it is merged with the destination model.
rotation Orientation This parameter specifies the rotations (about the
global origin) that are applied to the parts, polylines,
and notes beneath the source model before it is
merged with the destination model.
duplicate_parts Dupl_Part_Action This parameter specifies what to do when a part in
the destination model has the same name as a part in
the source model.
add_to_group_name A New Or Existing Group This parameter specifies a new or existing group into
which Adams View will add all the merged objects.
model 17
model modify
1. The source model will not be changed after the merge operation. You can specify a set of translations
and rotations that are applied to the parts, polylines, and notes beneath the source model, before it is
merged with the destination model. If you specify that parts with the same name in both models
(duplicate parts) are to be merged, then all of the children beneath the parts of the source model will
be copied beneath the corresponding parts in the destination model. Otherwise, the duplicate parts
in the source model will be copied and renamed in the destination model.
associated with it.
3. If you specify that duplicate parts are to be merged, then all the children beneath the parts of the
source model will be copied to be beneath the corresponding parts in the destination model.
Otherwise, the duplicate parts in the source model will be copied and renamed in the destination
model.
4. The add_to_group parameter specifies a new or existing group into which Adams View will add all
merged objects. All objects that were copied from the source model into the destination model will
be added to the specified group.
model modify
Allows you to create a model. You may reverse this creation at a later time with an UNDO command.
Format:
model modify
comments = string
title = string
model modify
Example:
model modify &
comments = “a new model” &
title = model2 &
view_name = view__1
Description:

model_name An existing model Specifies the model to be modified. You use this parameter to
new_model_name A New Model Specifies the name of the new model. You may use this name
later to refer to this model.
title String Specifies the title of model
1. In order to build a mechanism in Adams View, you must first create a model object in the Adams
View database. You then add parts and other objects to the model. As you develop your model, you
may display it, verify it, and change its attributes.
Once you have created a model, you add parts to it with the 'PART CREATE RIGID_BODY
NAME_AND_POSITION' command. After you have created your first part or two, you can
continue creating parts, or you may wish to start putting markers on the parts so you can add
geometry, constraints, and forces. You use the 'MARKER CREATE' command to add markers to a
part. Adding markers may help you position other parts, and creating geometry with markers will
help you visualize your model as you are constructing it.
When your model is complete, you use the 'OUTPUT_CONTROL' command to request Adams
output, write an Adams data set, and then analyze it with Adams. If your analysis is fairly simple, you
may use the 'SUBMIT' command to write the dataset and invoke Adams.
model 19
model verify
be assigned to it
3. If the model is not visible on the screen, you must type the name.
associated with it.
5. The title is a character string up to 80 characters which describes the model. It is used as the TITLE
statement in the Adams DATA SET (.adm file)
commas.
Cautions:
name.
model verify
Allows you to verify the consistency of your model.
model verify
Format:
model verify
write_to_terminal = on_off
file_name = string
check_solver_compatibility = boolean
Example:
model verify &
file_name = "c:\model_verify.txt"
Description:

write_to_terminal On_Off Specifies whether the information requested is to be
sent to the informational window or not.
file_name String Specifies that the information requested is to be sent
to a file with the name specified with the parameter.
check_solver_compatibility Boolean
1. Adams View will perform most of the checks that Adams does during the Adams Input Check Phase,
and report the results to the Information Box.
Adams View checks marker location and alignment at joints, joint primitives, and beams, for
instance. Adams View also computes the model degrees-of-freedom using the Grubler equation.
The information Adams View generates is only advisory. You are free to ignore it, at least temporarily.
You may continue modeling or even write an Adams data set file from your model.
If Adams View reports errors, you must correct them eventually, however, or Adams will not run the
data set. Adams View may also issue warnings, usually joints that are somewhat misaligned, but not
severely enough to warrant an error. You should make sure these warnings are not the result of
mistakes.
model 21
model verify

associated with it.
3. The write_to_terminal parameter is most likely to be used in conjunction with the FILE_NAME
model verify
move 1
move control_panel
move
move control_panel
The MOVE panel provides several convenient methods to relocate a marker or a part. The MOVE control
panel is invoked by picking MOVE from the fixed menu,or by using the "MOVE CONTROL_PANEL"
command.
Format:
move control_panel
s_trans_step_and_increment = real
s_rotate_step_and_increment = real
o_trans_step_and_increment = real
o_rotate_step_and_increment = real
Example:
EXAMPLE 1:
To translate an existing marker MAR1 in the X direction of a given part LPRF (e.g.PAR1) by ten model units:
1. Assure the OBJECT type is set to marker_named by picking the cycle button to the OBJECT name
field label.
2. Put the marker name (pick MAR1 from a view or type in MAR1) in the OBJECT field.
3. Assure the reference coordinate system ENTITY type is set to "lprf_of_part" by picking the cycle
button next to the "RELATIVE TO" name field label.
4. Put the part name (pick PAR1 from a view or type in PAR1) in the "RELATIVE TO" field.
5. Assure the value in the step field below the "TRANSLATE OBJ" dial is set to 10 model units by
picking the up or down arrow beside the value.
6. Pick the X triad axis on the "TRANSLATE OBJ" dial icon once. The ROTATE OBJ dial makes use
of the orientation of the RELATIVE TO coordinate system but not the location of its origin.
Therefore, OBJECTS rotated via this method undergo pure rotation without translation.
EXAMPLE 2:
To rotate a marker (MAR1) about an axis parallel to the Z axis of another marker(MAR2) in seven moves for
a total of 35 degrees:
1. Assure the OBJECT type is set to "marker_named" by picking the cycle button next to the
"OBJECT" name field label.
2. Put the name of the marker to be rotated (pick MAR1 from a view) in the OBJECT field.
3. Assure the reference coordinate system ENTITY type is set to "marker_named" by picking the cycle
button next to the RELATIVE TO" name field label.
move control_panel
4. Put the reference marker name (pick MAR2 from a view) in the "RELATIVE TO" field.
5. Set the value in the step field below the ROTATE OBJ dial to 5 (pick the up or down arrow next to
the value).
6. Pick the Z axis on the "ROTATE OBJ" dial icon seven times. Each time the triad is picked, the
coordinate values in the "CURRENT POSITION" fields are updated (See below for more
information).
Description:

s_trans_step_and_increment Real Specifies the screen translate step and increments for the
translate button on the "move control_panel".
s_rotate_step_and_increment Real Specifies the initial values for screen rotation step on the
"move control_panel", as well as the increment that is
applied to the screen rotation step each time the scroll
icon is activated.
o_trans_step_and_increment Real Specifies the object translate step and increments for the
object translate button on the "move control_panel".
o_rotate_step_and_increment Real Specifies the object rotate step and increments for the
object rotate button on the "move control_panel".
1. The QUIT button in the upper right corner will terminate the panel. The DONE button executes
the MOVE and closes the MOVE panel. The SUBMIT button executes the MOVE and leaves the
control panel open. When a part is moved, all associated markers and geometry move with the part.
When a marker is moved, all associated geometry moves with the marker. For the rest of this
description, the marker or part to be moved will be called the OBJECT. Moving an OBJECT is
carried out in three steps:
a. Selecting the OBJECT (part or marker) to be MOVED by filling in the OBJECTname field.
b. Selecting the coordinate system for the move by filling in the RELATIVE TO field. This step is
not required if the move is done relative to screen coordinates.
c. Doing the actual move using one of the three methods:
• a. Using the TRANSLATE OBJ or ROTATE OBJ dials to move an object relative to axes
attached to another part or marker.
• b. Using the TRANSLATE or RELATIVE dials to move an object relative to the axes attached to
a view.
• c. Using the GET COORDINATE button to extract and reapply coordinates of existing parts or
markers.
THE THREE STEPS TO MOVING AN OBJECT
move 3
move control_panel
There are three steps to moving an object in Adams View. First, you must select the OBJECT (part
or marker) to be MOVED, by filling in the OBJECT name field. The OBJECT name field is
preceded by the text, "Relocate the marker named". Notice the cycle button that lets you select
whether you wish to relocate a PART or MARKER. You must, then, specify the specific OBJECT
that you wish to move, either by picking it from the graphics window or entering the hierarchical
name of the OBJECT (for example, typing .pend.par1.mar3). Then, you must select the coordinate
system for the move by filling in the RELATIVE TO ENTITY field. This indicates the coordinate
system that you wish to use in defining your relative transforms of the OBJECTs position. Again, note
that you can cycle this field between a MARKER, PART, MODEL, or a VIEW coordinate system,
and must fill in the name of the OBJECT that you wish to use as a reference for your move. Finally,
you specify the transform you wish to apply, using one of one of three methods explained in
MOVING THE OBJECT below.
Step 1: SELECTING THE OBJECT TO MOVE
The first step to moving an object is deciding which object (part or marker) to move. Select the object
to be moved, by filling in the name of the object in the OBJECTname field:
Select the OBJECT type (part or marker) to be input by picking the cycle button next to the
OBJECT name field label until the desired OBJECT type name is displayed. The object type
specification is needed so that the system can validate the name as it is being input.
Enter the name of the specific OBJECT to be moved. Pick the desired OBJECT from a view.
Alternatively, you may type the name of the OBJECT into the field. This field must be highlighted
and empty while data is being input using either method.
Use the delete or the control-u keys to erase the field.
Step 2: SELECTING THE COORDINATE SYSTEM REFERENCE
The RELATIVE TO field is the marker, part, model, or view that is to be used as the move coordinate
system reference. Therefore, the rotational and translational coordinates, applied to the OBJECT for
the move, are based on the origin and orientation of this coordinate system. The use of this coordinate
system does not affect the way the OBJECT coordinates are subsequently stored by Adams view.
Also, if this field is left blank, Adams View uses the default coordinate system as the "RELATIVE
TO" coordinate system. To specify the "RELATIVE TO" coordinate system, follow these steps:
Select the ENTITY type (marker, part, model, or view) to be input, by clicking on the cycle button
next to the "RELATIVE TO" field label until the desired ENTITY type name is displayed. The
ENTITY type specification is needed so the system can validate the name as it is being input.
Enter the name of the specific ENTITY (marker, part, model, or view) to be used as the MOVE
coordinate system reference. Pick the desired ENTITY from a view.
Alternatively, you may type the name into the field. This field must be highlighted and empty while
data is being input using either method. Use the delete key or a control-u to erase the field.
Step 3: MOVING THE OBJECT
Once you have specified the object to be moved and selected the appropriate coordinate system
reference, you must input the translation or rotation values for the OBJECT move. This is done in
one of the three ways:
move control_panel
a. Using the TRANSLATE OBJ or ROTATE OBJ (i.e. body fixed coordinate)dials to move relative
axes attached to other parts or markers .
b. Using the TRANSLATE or ROTATE (i.e. screen fixed coordinate) dials to move relative axes
attached to a view.
c. Using the GET COORDINATE button to extract and reapply coordinates of existing parts or
markers.
MOVING THE OBJECT USING BODY-FIXED COORDINATES
This section will explain moving objects using the TRANSLATE OBJ and ROTATE OBJ icons on
the move panel.
The "ROTATE OBJ" and "TRANSLATE OBJ" dials move the OBJECT based on body fixed
coordinates. The body fixed coordinate system is specified in the "RELATIVE TO" field. This type
of MOVE is incremental. Each time the mouse is clicked on one of the icon triad axes, the OBJECT
will be MOVED. The displacement magnitude of the MOVE corresponds to the number of units
displayed below the dial. The OBJECT is moved along the body fixed axis of the ENTITY specified
in the RELATIVE TO field.
The specific axis on the ENTITY used for the MOVE corresponds to the particular icon axis picked.
1. The increment specified by the trans_step_and_increment parameter is applied to the translate step
each time the scroll icon is activated. The user may change these values for personal preference or
based on the needs dictated by the scale of a particular model. If the user enters values for the
trans_step_and_increment parameter, they will be stored and used the next time the "move
control_panel" command is invoked, unless changed by the user.
2. The user may change the values specified by the s_rotate_step_and_increment parameter for personal
preference or based on the needs dictated by the scale of a particular model. If the user enters values
for the rotate_step_and_increment parameter, they will be remembered and used the next time the
"move control_panel" command is invoked, unless overridden by the user.
3. The increment specified by the o_trans_step_and_increment is applied to the translate step, each
time the translate icon is activated. The user may change these values for personal preference or based
on the needs dictated by the scale of a particular model. When you enter values for the
translate_step_and_increment parameter, they will be stored and used the next time the "move
control_panel" command is invoked, unless changed.
4. The increment specified by the o_rotate_step_and_increment parameter is applied to the rotate step
each time the rotate icon is activated. The user may change these values for personal preference or
based on the needs dictated by the scale of a particular model. If the user enters values for the
rotate_step_and_increment parameter, they will be stored and used the next time the "move
control_panel" command is invoked, unless changed by the user.
Cautions:
1. The specific coordinate system used varies for each ENTITY type. The following shows the
coordinate system used for each entity:
• marker: the markers coordinate triad.
• part: the part's local part reference frame (LPRF) triad.
move 5
move mirror
• model: the model's global coordinate system or ground part LPRF triad.
• view: the screen coordinate triad at the center of the "active" view.
move mirror
Allows you to mirror parts, markers, geometry, forces, and constraints across a plane defined by the LPRF of
a part, or a marker.
The plane that the objects are mirrored across can be the XY, YZ or the ZX plane of a part LPRF or a marker.
The plane is defined as parallel to the two specified axes through the origin of the reference frame.
Since complete mirroring would change the handedness of the mirrored part LPRF or marker, only partial
mirroring is possible. To perform partial mirroring you must choose two axes to be mirrored, with the
remaining axis pointing in the direction required to maintain a right-handed system.
As with all MOVE commands when mirroring geometry, forces and constraints it is the markers associated
with these objects that are modified.
When mirroring multiple objects, each object is mirrored independently. The resultant orientation of the
mirrored object depends on the orientation of the original object and the mirror plans. If you try to mirror
multiple objects that have different orientations you will probably get something that looks different than
you expect. For example in the following example, the relative orientation between MAR1 and MAR2 is
different after the mirror operation.
model create model_name = MOD1
!
part create rigid_body name_and_position &
part_name = PAR2 &
location = 1,0,0 &
orientation = -90,0,0
!
marker create marker_name=MAR1 location=1,0,0 relative_to=PAR2
!
part_name = PAR3 &
location = 1,0,0 &
relative_to=MOD1
!
marker create marker_name=MAR2 location=1,0,0 relative_to=PAR3
!
list_info measure i_marker=MAR1 j_marker=MAR2
!
move mirror part_name=PAR2,PAR3 axes=xy plane=yz
relative_to=ground
!
list_info measure i_marker=MAR1 j_marker=MAR2
To maintain the same orientations between the MAR2 and MAR1, you need to mirror the 'xy' axes of PAR2
and the 'zx' axes of PAR2.
move mirror part_name=PAR2 axes=xy plane=yz relative_to=ground
move mirror
move mirror part_name=PAR3 axes=zx plane=yz relative_to=ground
Format:
move mirror
marker_name = existing marker
part_name = existing body
geometry_name = existing geometry
force_name = existing force
entity_name = existing entity
Plane = mirror_axes
axes = mirror_axes
relative_to = existing model part or marker
csmodel_name = existing model
cspart_name = existing part
csmarker_name = existing marker
csview_name = existing view
csentity_name = existing entity
Example:
move mirror &
part_name = PART_2 &
plane = xy &
axes = yz
move 7
move mirror
Description:

marker_name Existing marker Specifies the marker to modify. You use this parameter
to identify the existing marker to affect with this
command.
part_name Existing part Specifies the part to modify. You use this parameter to
identify the existing part to affect with this command.
flexible_body_name Existing flex body Specifies the name of an existing flexible body to
modify.
point_mass_name Existing point mass Specifies the point_mass to modify. You use this
parameter to identify the existing point_mass to affect
with this command.
geometry_name Existing geometry Specifies the geometry to modify. You use this
parameter to identify the existing geometry to affect
with this command.
constraint_name Existing constraint Specifies the constraint to modify. You use this
parameter to identify the existing constraint to affect
with this command.
force_name Existing force Specifies the force to modify. You use this parameter to
identify the existing force to affect with this command.
group_name Existing group Specifies the group to modify. You use this parameter
to identify the existing group to affect with this
command.
entity_name Existing entity Specify 1 or more existing entities.
Plane Mirror_axes Specifies which plane of the reference frame to mirror
across.
axes Mirror_axes Specifies which two axes of the part LPRF, marker, or
markers associated with the geometry, force or
constraint are mirrored.
relative_to Existing part, body or Specifies the LPRF of a part, or a marker, through
marker which the mirror plane runs.
csmodel_name Existing model Specifies an existing model's global origin to use as the
coordinate system in a MOVE, or PANEL SET
POSITION & ORIENTATION command.
cspart_name Existing part Specifies an existing part to use as the coordinate
system in a MOVE, or PANEL SET POSITION &
ORIENTATION command.
move mirror

csmarker_name Existing marker Specifies an existing marker to use as the coordinate
csview_name Existing view Specifies an existing view's origin to use as the
csentity_name Existing entity Specifies an existing entity's origin to use as the
1. You may identify a marker/part/flexible_body/point_mass/geometry/constraint/force/group by
typing its name or by picking it from the screen.
If the marker/part/flexible_body/point_mass/geometry/constraint/force/group is not visible on the
screen, you must type the name. You may also find it convenient to type the name even if the
marker/part/flexible_body/point_mass/geometry/constraint/force/group is displayed.
If you created the marker by reading an ADAMS data set or graphics file, the marker is the letters
MAR followed by the ADAMS data set marker ID number. The name of ADAMS MARKER/101
is MAR101, for example. If you created the
marker/part/flexible_body/point_mass/geometry/constraint/force/group during preprocessing, you
If a marker/part/flexible_body/point_mass/geometry/constraint/force/group is available by default,
you may identify it by entering its name only. If it is not, you must enter its full name. To identify
a marker/part/flexible_body/point_mass/geometry/constraint/force/group under a different part, for
instance, you may need to enter the model and part names as well. For example, you may specify
marker 'pivot' from model 'links', part 'lower_arm' by entering ".links.lower_arm.pivot". If you type
a "?", Adams View will list the marker available by default.
You must separate multiple marker/part/flexible_body/point_mass/geometry/constraint/force/group
names by commas.
If the marker/part/flexible_body/point_mass/geometry/constraint/force/group is visible in one of
your views, you may identify it by picking on it.
You need not separate multiple
marker/part/flexible_body/point_mass/geometry/constraint/force/group picks by commas.
2. The plane that the objects are mirrored across can be the XY, YZ or the ZX plane of a part LPRF or
a marker. The plane is defined a parallel to the two specified axes through the origin of the reference
frame.
3. Since complete mirroring would change the handedness of the mirrored part LPRF or marker, only
partial mirroring is possible. To perform partial mirroring you must choose two axes to be mirrored,
with the remaining axis pointing in the direction required to maintain a right-handed system.
move 9
move object
4. The global origin specified in the csmodel_name becomes the coordinate system to which the relative
distances, and orientation angles will be applied.
5. The part specified in the parameter cspart_name becomes the coordinate system to which the relative
distances, and orientation angles will be applied.
6. The marker specified in the csmarker_name parameter becomes the coordinate system to which the
relative distances, and orientation angles will be applied.
7. The csview's origin becomes the coordinate system to which the relative distances, and orientation
angles will be applied.
8. The csentity's origin becomes the coordinate system to which the relative distances, and orientation
angles will be applied.
move object
Allows you to set the position of a part or marker.
Format:
move object
flexible_body_name = an existing flex_body
point_mass_name = an existing point_mass
c1 = real
c2 = real
c3 = real
a1 = real
a2 = real
a3 = real
csmodel_name = an existing model
cspart_name = an existing part
csmarker_name = an existing marker
csview_name = an existing view
move object
move object
csentity_name = an existing entity
incrementally = boolean
Example:
move object
c1 = 0.1 &
c2 = 0.12 &
c3 = 0.14 &
a1 = 0.14 &
a2 = 0.121 &
a3 = 0.11 &
csmodel_name = crankshaft &
incrementally = yes
Description:

parameter to identify the existing marker to be
part_name An Existing Part Specifies the part to be modified. You use this
parameter to identify the existing part to be affected
with this command. You may identify a part by
typing its name or by picking it from the screen.
flexible_body_na An Existing Flex_body Specifies the name of an existing flexible body to
me modify. You may identify a flexible body by typing
its name, by selecting it from the database
navigator's select list or by picking its graphical
representation from the screen, whichever is most
convenient.
point_mass_name An Existing Point_mass Specifies the point_mass to be modified. You use
this parameter to identify the existing point_mass to
move 11
move object

constraint_name An Existing Constraint Specifies the constraint to be modified. You use this
parameter to identify the existing constraint to be
force_name An Existing Force Specifies the force to be modified. You use this
affected with this command. You may identify a
group by typing its name.
entity_name An Existing Entity Specifies an existing entity
c1 Real Specifies the first location coordinate to be applied
to the marker or part you wish to move. Check the
current COORDINATE SYSTEM TYPE by using
the command LIST_INFO DEFAULTS. This first
location coordinate will be of the current coordinate
system type.
c2 Real Specifies the second location coordinate to be
applied to the marker or part you wish to move.
Check the current COORDINATE SYSTEM
TYPE by using the command LIST_INFO
DEFAULTS. This first location coordinate will be
of the current coordinate system type.
c3 Real Specifies the third location coordinate to be applied
current COORDINATE SYSTEM TYPE by using
the command LIST_INFO DEFAULTS. This first
location coordinate will be of the current coordinate
system type.
a1 Real Specifies the first orientation angle to be applied to
the marker or part you wish to move. Check the
current ORIENTATION TYPE using the
command LIST_INFO DEFAULTS, to confirm
which axis this angle will be applied to.
a2 Real Specifies the second orientation angle to be applied
move object

a3 Real Specifies the third orientation angle to be applied to
the marker or part you wish to move. Check the
csmodel_name An Existing Model Specifies an existing model's global origin to use as
the coordinate system in a MOVE, or PANEL SET
cspart_name An Existing Part Specifies an existing part to use as the coordinate
csmarker_name An Existing Marker Specifies an existing marker to use as the coordinate
csview_name An Existing View Specifies an existing view's origin to use as the
csentity_name An Existing Entity Specifies that the MOVE OBJECT command
should be done by adding the coordinates to the
existing position of the object(s) being moved
incrementally Boolean
1. You may identify a marker by typing its name or by picking it from the screen. If the marker is not
marker name is the letters MAR followed by the Adams data set marker ID number. For example,
the name of Adams MARKER/101 is MAR101. If you created the marker during reprocessing, you
will have given it a name at that time. If a marker is available by default, you may identify it by
entering only its name. If it is not, you must enter its full name. To identify a marker under a different
part, for instance, you may need to enter the model and part names as well. For example, you may
specify marker 'pivot' from model 'links', part 'lower_arm' by entering ".links.lower_arm.pivot". You
2. If the part is not visible on the screen, you must type the name. You may also find it convenient to
you will have given it a name at that time. If a part is available by default, you may identify it by
entering only its name. If it is not, you must enter its full name. To identify a part under another
model, for instance, you may need to enter the model name as well. For example, you may specify
move 13
move object
part 'arm' from model 'robot' by entering ".robot.arm". If you type a "?", Adams View will list the
parts available by default. You must separate multiple part names by commas. If the part is visible in
one of your views, you may identifyit by picking on any of the graphics associated with it. You need
not separate multiple part picks by commas.
3. If Adams View created the flexible body by reading an Adams data set, the name may either come
from the "adams_view_name" field of the preceding comment, or be synthesized from the Adams ID
flexible body name will be synthesized from the Adams ID number. When the name is created by
Adams View, it will be composed of "FLX" concatenated with the Adams data set flexible body ID
you create during preprocessing have user-specified names. You may identify a flexible body
belonging to the current default model by entering just its name. For others, you must enter the full
name. To identify a flexible body under another model, for instance, you need to enter the model
name as well. For example, you may specify flexible body 'snake' from model 'reptiles' by entering
".reptiles.snake". You can invoke the database navigator by typing "?", which will bring up the select
list from which you can pick a flexible body. For commands which accept multiple flexible body
names, you must separate the names by commas. If the flexible body is visible in one of your views,
you may identify it by picking on any of the graphics associated with it. When you do this Adams
View will automatically separate multiple flexible body picks by commas.
reading an Adams data set or graphics file, the point_mass name is the letters POI followed by the
Adams data set point_mass ID number. For example, the name of Adams POINT_MASS/101 is
POI101. If you created the point_mass during preprocessing, you will have given it a name at that
time.
If a point_mass is available by default, you may identify it by entering only its name. If it is not, you
to type the name even if the geometry is displayed. If geometry is available by default, you may
identify it by entering its name only. If it is not, you must enter its full name. To identify geometry
under another model, for instance, you may need to enter the model and part names as well. For
example, you may specify arc 'end' on part 'arm' in model 'susp' by entering ".susp.arm.end". If
youtype a "?", Adams View will list the geometrys available by default. You must separate multiple
geometry names by commas. If the geometry is visible in one of your views, you may identify it by
picking on any of the graphics associated withit. You need not separate multiple geometry picks by
commas.
move object
to type the name even if the constraint is displayed. If you created the constraint by reading an Adams
data set, the constraint name is the first three letters of the Adams statement type followed by the
Adams data set constraint ID number. For example, the name of Adams JOINT/101 is JOI101. If
you created the constraint during preprocessing, you will have given it a name at that time. If a
constraint is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a constraint under a different model, for instance, you may need to
enter the model name as well. For example, you may specify constraint 'servo_motor' from model
by default. You must separate multiple constraint names by commas. If the constraint is visible in one
separate multiple constraint picks by commas.
7. You may identify a force by typing its name or by picking it from the screen. If the force is not visible
force is displayed. If you created the force by reading an Adams data set or graphics file, the force name
is the first three letters of the Adams statement followed by the Adams data set force ID number. For
example, the name of Adams SFORCE/101 is SFO101. If you created the force during preprocessing,
you will have given it a name at that time. If a force is available by default, you may identify it by
entering only its name. If it is not, you must enter its full name. To identify a force under a
preprocessing model, for instance, you may need to enter the model name as well. For example, you
may specify the force named 'bumper' from the model named 'test' by entering ".test.bumper". If you
type a "?", Adams View will list the forces available by default. You must separate multiple force names
by commas. If the force is visible in one of your views, you may identify it by picking on any of the
graphics associated with it. You need not separate multiple force picks by commas.
8. If a group is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. If you type a "?", Adams View will list the group available by default. You must
separate multiple group names by commas.
9. For the c1 parameter,COORDINATE_SYSTEM_TYPE = cartesian ( X,Y,Z ) - C1 will be a X
coordinate.
This location coordinate will be relative to the marker, part, screen axes, or global axes specified in the
parameter RELATIVE_TO.
10. For the c2 parameter,COORDINATE_SYSTEM_TYPE = cartesian ( X,Y,Z ) - C2 will be a Y
coordinate.
11. For the c3 parameter,COORDINATE_SYSTEM_TYPE = cartesian ( X,Y,Z ) - C3 will be a Z
coordinate.
12. For the a1 parameter,• ORIENTATION_TYPE = body313 ( Euler angles ) • A1 will be applied to
the Z axis.
move 15
move object
13. For the a2 parameter,• ORIENTATION_TYPE = body313 ( Euler angles )• A2 will be applied to
the new X axis.
the new Z axis.
15. This model global origin becomes the coordinate system to which the relative distances, and
orientation angles will be applied. You may identify a model by typing its name or by picking it from
the screen. If the model is not visible on the screen, you must type the name. You may also find it
graphics associated with it. You need not separate multiple model picks by commas.
16. This part becomes the coordinate system to which the relative distances, and orientation angles will
be applied. You may identify a part by typing its name or by picking it from the screen. If the part is
not visible on the screen, you must type the name. You may also find it convenient to type the name
even if the part is displayed.
PAR101. If you created the part during preprocessing, you will have given it a name at that time. If
a part is available by default, you may identify it by entering only its name. If it is not, you must enter
its full name. To identify a part under another model, for instance, you may need to enter the model
name as well. For example, you may specify part 'arm' from model 'robot' by entering ".robot.arm".
If you type a "?", Adams View will list the parts available by default. You must separate multiple part
names by commas. If the part is visible in one of your views, you may identify it by picking on any of
the graphics associated with it. You need not separate multiple part picks by commas.
17. The marker specified by the csmarker_name parameter becomes the coordinate system to which the
relative distances, and orientation angles will be applied. You may identify a marker by typing its
name or by picking it from the screen. If the marker is not visible on the screen, you must type the
name. You may also find it convenient to type the name even if the marker is displayed. If you created
the marker by reading an Adams data set or graphics file, the marker name is the letters MAR followed
by the Adams data set marker ID number. For example, the name of Adams MARKER/101 is
MAR101. If you created the marker during preprocessing, you will have given it a name at that time.
markers available by default. You must separate multiple marker names by commas. If the marker is
visible in one of your views, you may identify it by picking on it. You need not separate multiple
marker picks by commas.
18. This view's origin becomes the coordinate system to which the relative distances, and orientation
angles will be applied. You may identify a view by typing its name or by picking it from the screen.
In most cases, you may enter the special view name 'all', which means all the views currentlydisplayed.
commas.
move rotation
19. This command can move an object to absolute coordinates relative to the specifiedcoordinate system
or the move can be done "incrementally"from the current position.When INCREMENTALLY is set
to YES the coordinates specified in the command are added to the current coordinates of the object
to be moved.
When INCREMENTALLY is set to NO the object to be moved is positioned at the absolute
coordinates specified in the command.
Tips:
 If you type a "?", Adams View will list the markers available by default.
move rotation
Allows you to rotate a part or marker from its current orientation.
Format:
move rotation
a1 = real
a2 = real
a3 = real
move 17
move rotation
Example:
move rotation &
c1 = 0.1 &
c2 = 0.12 &
c3 = 0.14 &
a1 = 0.14 &
a2 = 0.121 &
a3 = 0.11 &
csmodel_name = crankshaft
Description:

parameter to identify the existing part to be
part by typing its name or by picking it from the
screen.
flexible_body_name An Existing Flex_body Specifies the name of an existing flexible body to
be modified. You may identify a flexible body by
typing its name, by selecting it from the database
convenient.
this parameter to identify the existing point_mass
geometry_name An Existing Geometric Entity Specifies the geometry to be modified. You use
this parameter to identify the existing geometry to
constraint_name An Existing Constraint Specifies the constraint to be modified. You use
this parameter to identify the existing constraint
move rotation

about Specifies a reference frame to be used as the center
of rotation. The locations, as well as the
orientations of the objects being rotated will be
changed.
a1 Real Specifies the first orientation angle to be applied
to the marker or part you wish to move. Check
the current ORIENTATION TYPE using the
a2 Real Specifies the second orientation angle to be
Check the current ORIENTATION TYPE using
the command LIST_INFO DEFAULTS, to
confirm which axis this angle will be applied to.
a3 Real Specifies the third orientation angle to be applied
to the marker or part you wish to move. Check
the currentORIENTATION TYPE using the
command LIST_INFODEFAULTS, to confirm
which axis this angle will be appliedto.
csmodel_name An Existing Model Specifies an existing model's global origin to use
as the coordinate system in a MOVE, or PANEL
SET POSITION & ORIENTATION
command.
cspart_name An Existing Part Specifies an existing part to use as the coordinate
system in a MOVE, or PANEL SET POSITION
& ORIENTATION command.
csmarker_name An Existing Marker Specifies an existing marker to use as the
csview_name An Existing View Specifies an existing view's origin to use as the
should be doneby adding the coordinates to the
existing position of theobject(s) being moved
move 19
move rotation
Adams View it will be composed of "FLX" concatenated with the Adams data set flexible body ID
name. To identify a flexible body under another model, for instance, you need to enter the model
".reptiles.snake". You can invoke the database navigator by typing "?", whichwill bring up the select
you may identify it by picking on any of the graphics associated with it. When you do this, Adams
move rotation
time.
identify it by entering only its name. If it is not, you must enter its full name. To identify geometry
example, you may specify arc 'end' on part 'arm' in model 'susp' by entering ".susp.arm.end". If
youtype a "?", Adams View will list the geometrys available by default. You must separate multiple
picking on any of the graphics associated with it. You need not separate multiple geometry picks by
commas.
move 21
move rotation
8. If a group is available by default, you may identify it by entering only its name. If it is not, you must
the Z axis.
the new X axis.
the new Z axis.
12. Example for the about parameter, if you rotate a marker located at x=1, y=0,z=0 with an orientation
of 0,0,0 ABOUT the LPRF of its part by 0,0,90, the marker will be placed at x=0, y=1, z=0with an
orientation of 90,0,0 (all angles in degrees and SPACE123))
not visible on the screen, you must type thename. You may also find it convenient to type the name
a part is available by default, you may identify it by entering its name only. If it is not, you must enter
move translation
16. This view's origin becomes the coordinate system to which the relative distances and orientation
In most cases, you may enter the special view name 'all', which means all the views currently
displayed.
commas.
Tips:
1. If you type a "?", Adams View will list the markers available by default.
move translation
Allows you to translate a part or marker from its current position.
Format:
move translation
c1 = real
c2 = real
c3 = real
move 23
move translation
move translation
Example:
move translation &
c1 = 0.1 &
c2 = 0.12 &
c3 = 0.14 &
csmodel_name = crankshaft
Description:

parameter to identify the existing part to be
part by typing its name or by picking it from the
screen.
flexible_body_name An Existing Flex_body Specifies the name of an existing flexible body to
be modified. You may identify a flexible body by
typing its name, by selecting it from the database
convenient.
this parameter to identify the existing point_mass
geometry_name An Existing Geometric Entity Specifies the geometry to be modified. You use
this parameter to identify the existing geometry to
constraint_name An Existing Constraint Specifies the constraint to be modified. You use
this parameter to identify the existing constraint
move translation

c1 Real Specifies the first location coordinate to be
DEFAULTS. This first location coordinate will
be of the current coordinate system type.
c2 Real Specifies the second location coordinate to be
c3 Real Specifies the third location coordinate to be
csmodel_name An Existing Model Specifies an existing model's global origin to use
as the coordinate system in a MOVE, or PANEL
SET POSITION & ORIENTATION
command.
cspart_name An Existing Part Specifies an existing part to be used as the
move 25
move translation

csmarker_name An Existing Marker Specifies an existing marker to be used as the
csview_name An Existing View Specifies an existing view's origin to be used as the
should be done by adding the coordinates to the
existing position of the object(s) being moved
Adams View it will be composed of "FLX" concatenated with the Adams data set flexible body ID
name. To identify a flexible body underanother model, for instance, you need to enter the model
move translation
".reptiles.snake". You can invoke the database navigator by typing "?", which will bring up the select
you may identify it by picking on any of the graphics associated with it. When you do this, Adams
time.
identify it by entering only its name. If it is not, you must enter its full name. To identify geometry
example, you may specify arc 'end' on part 'arm' in model 'susp' by entering ".susp.arm.end". If you
type a "?", Adams View will list the geometrys available by default. You must separate multiple
picking on any of the graphics associated with it. You need not separate multiple geometry picks by
commas.
move 27
move translation
8. If a group is available by default, you may identify it by entering its name only. If it is not, you must
9. For the c1 parameter,COORDINATE_SYSTEM_TYPE = cartesian ( X,Y,Z ) - C1 will be a X
coordinate.
10. For the c2 parameter,COORDINATE_SYSTEM_TYPE = cartesian ( X,Y,Z ) - C2 will be a Y
coordinate.
11. For the c3 parameter,COORDINATE_SYSTEM_TYPE = cartesian ( X,Y,Z ) - C3 will be a Z
coordinate.
not visible on the screen, you must type the name. You may also find it convenient to type the name
a part is available by default, you may identify it by entering only its name. If it is not, you must enter
move translation
15. This view's origin becomes the coordinate system to which the relative distances, and orientation
In most cases, you may enter the special view name 'all', which means all the views currently
displayed.
commas.
Tips:
 If you type a "?", Adams View will list the markers available by default.
multi_run_analysis 1
multi_run analysis create
multi_run_analysis
Allows you to create an empty analysis. You may find this useful for reading spreadsheet data into a results
set with the NUMERIC_RESULTS READ_FROM_FILE command.
Format:
multi_run_analysis_name = new multi_run_analysis
comments= string
Example:
multi_run_analysis create &
multi_run_analysis_name = mrun__1 &
comments = "analysis for reading spreadsheet data"
Description:

multi_run_analysis_name New Multi_run Analysis Name Specifies the name of the new multi-run
analysis.
Comments String Specifies any comments to be associated
with this analysis.
When an Adams Solver data file (.adm) is read into Adams View, all comments associated with a statement
(from the end of the previous statement through the end of the current statement) are stored with the object.
Comments in the data file can be associated with model.
These comments must follow the title statement and be followed by the comment 'END OF MODEL
When an Adams Solver data file is written, the comments for an object are written before the statement
corresponding to the object.
multi_run analysis delete

Allows you to delete an existing analysis.
multi_run analysis modify
You must enter the name of the analysis you wish to delete by specifying its name on the default model or
the full name.
Format:
multi_run analysis delete
multi_run_analysis_name = existing multi_run_analysis
Example:
multi_run_analysis delete &
multi_run_analysis_name = mrun__1
Description:

multi_run_analysis_name Existing Multi_run Analysis Specifies the name of an existing multi-run
analysis.

Allows you to modify an existing analysis.
You must enter the name of the analysis you wish to delete by specifying the name of an analysis on the default
model or the full name.
You may reverse this modification at a later time with an UNDO command.
Format:
multi_run_analysis_name = existing multi_run_analysis
new_multi_run_analysis_name = new name for the multi-run analysis
comments = string
Example:
multi_run_analysis modify &
multi_run_analysis_name = mrun__1 &
new_multi_run_analysis_name = mrun_to_save_data &
comments = "analysis for reading spreadsheet data"
multi_run_analysis 3
Description:

multi_run_analysis_name Existing Multi_run Analysis Specifies the name of an existing
multi-run analysis.
new_multi_run_analysis_name New Multi-run Analysis Specifies a new name for the
multi_run analysis
Comments String Specifies comments to be associated
with this analysis, if any.
notes 1
notes attributes
notes
notes attributes
Allows you to set specification of attributes on an individual note or a group of notes.
You can set the following attributes on a note.
 SIZE. You may set a size of the note text in modeling units.
 SCALE. You may scale the size of the note text by a non-unit scale factor.
 VISIBILITY. You may set a note's visibility ON, OFF or TOGGLE the current setting. When you
set a note's visibility OFF, the note will not be drawn. When you set a note's visibility ON, you
allow that note to be drawn.
 COLOR. You may set the color of a note with this parameter.
Format:
notes attributes
note_name = existing note
size = length
unitless_size = real
point_size = integer
scale = real
visibility = on/off
Example:
notes attributes &
note_name = note_2 &
size = 2.0 &
color = red &
visibility = on
notes attributes
Description:

note_name Existing Note Specifies the note to be modified. You use this parameter to identify the
existing note to be affected with this command.
size Length Specifies the size, in modeling units, that the note height will appear in. The
width of each character in the note is approximately 60%of the height.
unitless_size Real Specifies a real number
point_size Integer Specifies an integer
scale Real Specifies the amount to scale the note size. Adams will compute the new
note size by multiplying the current note size by this scale.
color Existing Color Specifies the COLOR of a graphic object.
visibility On, Off Specifies the visibility of notes.
1. You may identify a note by typing its name or by picking it from the screen.
If the note is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the note is displayed.
If a note is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a note under a model, for instance, you may need to enter the model
name as well. For example, you may specify note "n1" from the model named test by entering
".test.n1". If you type a "?", Adams View will list the notes available by default.
You must separate multiple note names by commas.
If the note is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple note picks by commas.
2. A graphic object is an object that may be drawn on the screen by Adams View, these include curves,
parts, markers, arcs, outlines, boxes, circles, cylinders, frustums, spring damper graphics, force
graphics, and plot curves and symbols. When the COLOR of a part is specified, all graphic objects
fixed to that part are drawn with the COLOR of the part. Adams View supports the following
COLOR: black, white, red, green, blue, cyan, magenta, and yellow.
3. If you set the visibility of a note OFF, Adams View will erase it from the display. The note will remain
in the data base, and you may redisplay it by turning the visibility ON.
Cautions:
1. If you choose the COLOR of an entity to be drawn in the view background color (typically, white or
black) it may not show up.
See help for hardcopy also.
notes 3
notes copy
notes copy
Allows you to copy an existing note to a new note. A note is a single text string, or a series of text strings used
to add an annotation to an existing view or plot.
Format:
notes copy
new_note_name = new note
Example:
notes copy &
note_name = note_for_part_1 &
new_note_name = note_for_part2
Description:

Note_name Existing Note Specifies an existing note.
New_note_name New Note Specifies the name of the new note. You may use this name later to
refer to this note.
1. Adams View will not allow you to have two notes with the same name, so you must provide a unique
name.
be assigned to it.
notes create
notes create
Allows you to create a note, with an optional leader line.
Notes are general purpose text strings that can be used to add annotations to views, plots, or analyses. Notes
contain one or more lines of text. You place them by selecting the location for the upper left corner of the
text string(s). You should place the text far enough away from the border of the window to ensure that the
note will not run off the screen. If you make a mistake, use the 'NOTES MODIFY' command to move the
note.
Notes have an optional leader line that can point to a specific spot on the display. This leader line can have 1
to n points, where the last point specified is the location of an arrow head. You may specify a color for the
text and leader line.
Format:
notes create
note_name = new note
text = string
location = location
pick = location indicated by a pick in the view
screen_coords = real
size = length
bitmapped_text = on/off
leader_line = location
arrow_visibility = on/off
arrow_size = real
user_text = on/of
Example:
notes create &
note_name = notes create &
note_name = note__1 &
text = "this is a new part that i have added" &
location = 10.0,10.0,10.0
notes 5
notes create
Description:

note_name New Note Specifies the name of the new note.You may use this name later to
refer to this note.
text String Specifies the text string(s) that will comprise the note text.
location Location Specifies the location to be used to define the note. The location
coordinates for plot notes in Adams PostProcessor do not relate to the
plot coordinates themselves. They are unfortunately difficult to
predict since they depend strongly upon a number of factors
including plot aspect ratio, visibility of the title, sub-title and axis
labels, Viewport orientation and so on. This is why the direct
interactive placement is preferred. Users who really want to script the
creation of plot notes are advised to, from the command navigator
dialog, use the interactive pick option to fill the location fields. This
allows one to see the location coordinates used behind the scenes.
pick Pick Location Specifies a position in a view by picking with the mouse or pen.
screen_coords Real Specifies an x,y location in a view on the Adams View screen.
SCREEN_COORDS refers to a coordinate reference tied to the
terminal screen.
size Integer Specifies the size, in modeling units, that the note height will appear
in. The width of each character in the note is approximately 60%of
the height.
point_size Integer Specifies an integer to define the point size
bitmapped_text On, Off Specifies whether or not a note is to be drawn using bitmapped text.
leader_line Location Specifies the screen locations which define a leader line for a note.
arrow_visibility On, Off Specifies whether there should be an arrow head at the last point on
the leader line of the note.
arrow_size Real Specifies the size, in modeling units, that the arrow head of the leader
line on the note will appear. If arrow_size has not been set, or it is set
to zero, the arrowhead will be roughly the size of the text in the note.
user_text On, Off Specifies on or off.
name.
notes create
be assigned to it.
2. You may enter the text string(s) for this parameter without double quote marks, if the string contains
no "blanks" or special characters such as *&^%$#@!-/><.
If the text string(s) do have any of these special characters the string must be quoted.
To enter a multiline note, each line must be entered as a separate string, separated by a comma. An
Example:
note create note=.front.n1 screen_coords=0,0 & TEXT="This is
a","multi line note" size = .12
Notes are left-justified.
3. The “pick” parameter is used in the context of various commands. The response from a pick of the
screen is usually the view name and the screen coordinates of the pick. Some of the ways a pick is used
is to select the position to split a view to create a new view, to select the box corners of a view to zoom
in on, etc.
To enter a pick move the cursor to the location in the desired view using the mouse or pen. Once in
the desired position depress one of the mouse buttons.
4. Bitmapped text provides better looking text and can make use of the fonts available on your system.
Bitmapped text will not transform in the same manner as geometry. Only the placement point will
move.
The text will always face the screen. Non-bitmapped text (stroked text) will transform in the same
manner as geometry.
5. The screen locations are entered by using the mouse cursor. Move the mouse cursor to the desired
locations and "click" any mouse button to record the position. Adams View will create a leader line
from the first point through successive points, ending with an arrow head at the last point.
6. There is no limit to the number of points in the leader line.
notes 7
notes delete
notes delete
Allows you to delete a note. A note is a single text string, or a series of text strings used to add an annotation
to an existing view or plot.
Format:
notes delete
Example:
notes delete &
note_name = note_for_part_1
Description:

Note_name Existing Note Specifies an existing note to be deleted.
menu entry 'UNDO'.
You may identify a note by typing its name or by picking it from the screen. If the note is not visible
note isdisplayed.
If a note is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a note under a model, for instance, you may need to enter the model
name as well. For example, you may specify note "n1" from the model named test by entering
".test.n1". If you type a "?", Adams View will list the notes available by default.
You must separate multiple note names by commas.
If the note is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple note picks by commas.
notes modify
Allows you to modify an existing note.
Notes are general purpose text strings that can be used to add annotations to views, plots, or analyses. Notes
contain one or more lines of text. You place them by selecting the location for the upper left corner of the
text string(s). You should place the text far enough away from the border of the window to insure that the
notes modify
note will not run off the screen. If you make a mistake, use the 'NOTES MODIFY' command to move the
note.
Notes have an optional leader line that can point to a specific spot on the display. This leader line can have 1
to n points, where the last point specified is the location of an arrow head. You may specify a color for the
text and leader line.
Format:
notes modify
new_note_name = new note name
text = string
location = location
pick = location indicated by a pick in the view
screen_coords = real
rotation = real
alignment = justified
size = length
bitmapped_text = on/off
leader_line = location
arrow_visibility = on/off
arrow_size = real
user_text = on/off
user_location = on/off
Example:
notes modify &
note_name = note__1 &
new_note_name = my_note &
text = "this is a new part that i have added" &
location = 10.0,10.0,20.0
notes 9
notes modify
Description:

note_name Existing Note Specifies the name of an existing note.
New_note_name New Note Specifies the new name of the note
text String Specifies the text string(s) that will comprise the note text.
location Location Specifies the location to be used to define the note.
pick Pick Location Specifies a position in a view by picking with the mouse or pen.
screen_coords Real Specifies an x,y location in a view on the Adams View screen.
SCREEN_COORDS refers to a coordinate reference tied to the
terminal screen.
size Integer Specifies the size, in modeling units, that the note height will appear
in. The width of each character in the note is approximately 60% of
the height.
point_size Integer Specifies an integer to define the point size
bitmapped_text On, Off Specifies whether or not a note is to be drawn using bitmapped text.
leader_line Location Specifies the screen locations which define a leader line for a note.
arrow_visibility On, Off Specifies whether there should be an arrow head at the last point on
the leader line of the note.
arrow_size Real Specifies the size, in modeling units, that the arrow head of the leader
line on the note will appear. If arrow_size has not been set, or it is set
to zero the arrowhead will be roughly the size of the text in the note.
user_text On, Off Specifies on or off.
User_location On, Off Specifies on or off.
Rotation Real This parameter specifies the rotations (about to the global origin) that
are applied to the parts, polylines, and notes beneath the source
model before it is merged with the destination model. The source
model will not be changed after the merge operation.
Alignment Left, Center, Specifies the alignment of the text in the note.
Right
name.
notes modify
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:
be assigned to it.
You may enter the text string(s) for this parameter without double quote marks, if the string contains
no "blanks" or special characters such as *&^%$#@!-/><.
If the text string(s) do have any of these special characters, the string must be quoted.
To enter a multiline note, each line must be entered as a separate string, separated by a comma. An
Example:
note create note=.front.n1 screen_coords=0,0 & TEXT="This is
a","multi line note" size = .12
Notes are left-justified.
2. The “pick” parameter is used in the context of various commands. The response from a pick of the
screen is usually the view name and the screen coordinates of the pick. Some of the ways a pick is used
is to select the position to split a view to create a new view, to select the box corners of a view to zoom
in on, etc.
3. To enter a pick, move the cursor to the location in the desired view using the mouse or pen. Once
in the desired position depress one of the mouse buttons.
4. Bitmapped text provides better looking text and can make use of the fonts available on your system.
Bitmapped text will not transform in the same manner as geometry. Only the placement point will
move.
The text will always face the screen. Non-bitmapped text (stroked text) will transform in the same
manner as geometry.
5. The screen locations are entered by using the mouse cursor. Move the mouse cursor to the desired
locations and "click" any mouse button to record the position. Adams View will create a leader line
from the first point through successive points, ending with an arrow head at the last point.
6. There is no limit to the number of points in the leader line.
numeric_results 1
numeric_results component create
numeric_results
Allows you to create a result set component. It is the same as using numeric_results create value.
Format:
new_result_set_component_name= new result_set
units = type of units
values= real
Example:
For example, the following command generates a full-cycle sine curve with 100 points:
numeric_results component create &

new_result_set_component_name= req1.x &
values= (sin(series2(0.0, two_pi, 100)radians)))
Description:

new_result_set_c New Result Set Name Identifies the new result set
omponent_name component.
Values Real Specifies the real values to be stored
in the result set component. The
values can be a list of numbers, or an
expression defining an array of
values.
Units no_units, calculate, length, angle, mass, Specifies the type of units to be used
density, time, area, volume, velocity, for the new result set component.
acceleration, angular_velocity, Once you set the unit type, Adams
angular_acceleration, inertia, area_inertia, View can perform the proper unit
damping, stiffness, torsion_stiffness, conversion on the data.
torsion_damping, force, torque, pressure,
force_time, torque_time
1. The heirarchy of a model's results is shown below with the components of a result set under the result
set:
If you want to store the component:

• In an existing result set, the name must include the result set. For example, assume you have a
request file called SHIFT.REQ, and it contains the result set REQ1. If you want to store the new
result set component in result set REQ1 with the component name NEW, enter:
.SHIFT.REQ1.NEW (it is not necessary to include .SHIFT., if SHIFT is the current
analysis_name).
• In a new results set, named REQ99, for example, in the analysis run SHIFT, enter
.SHIFT.REQ99.NEW. The number of components to be stored is inferred by the number of
components named in this parameter. You can enter multiple names separated with commas (,).
The component name must be unique, even though it can be stored in an existing result set. A
result set name can be of any length and any combination of alphanumeric characters. The leading
character must be a letter.
request 101 from an analysis named test is often referred to as .test.req101.
The table below illustrates the default names assigned to result sets and result set components, read from
File that result

Result set type Result set name Component names is from
vx vy vz wx wy wz
accx accy accz wdx wdy wdz
numeric_results 3
numeric_results component delete
File that result

Result set type Result set name Component names is from
coupler COUxxx... fx1 fy1 fz1 tx1 ty1 tz1 fmag1 tmag1 results file
fx2 fy2 fz2 tx2 ty2 tz2 fmag2 tmag2
2. If the value for the “units” parameter is calculate, Adams View tries to determine the units to use for
this operation. For example, if velocities are added (length/time), then the calculated “units”
parameter for the new result set component is velocity (length/time). If the derivative of a velocity is
taken, the calculated “units” parameter is acceleration (length/time**2).
Adams View can only handle calculated units with a maximum exponent for the base units (force,
length, mass, time) of plus or minus four. For example, if a result set component with the units
(length/time**3) is multiplied with a result set component having the same units, it gives the
calculated units (length**2/time**6). Because the exponent of time is greater than four, Adams View
uses no_units and issues a warning.
Values are: no_units, calculate, length, angle, mass, density, time, area, volume, velocity,
acceleration, angular_velocity, angular_acceleration, inertia, area_inertia, damping, stiffness,
torsion_stiffness, torsion_damping, force, torque, pressure, force_time, torque_time.

Allows you to delete a result set component.
Format:
result_set_component_name = existing result_set component name
Example:
numeric_results delete &
result_set_component_name = res_01
Description:

result_set_component_name Existing result set component Identifies a result set component
to be deleted.
1. The components must be in an existing result set and reference to the component must include the
result set name. A result set is a storage place for any kind of numeric tabular data. A result set can
contain any number of components. A component is usually set up to contain vector components of
values such as displacement, velocity, acceleration, and force. In this case, however, a result set is
completely general and can store any numeric value in a component with few exceptions. These
exceptions are those cases when you ask the system to mix incompatible value types, such as complex
values in the same component as real values.
The result set name given must be within a particular analysis. A result set name can be of any length,
and any combination of letters and numbers. The leading character, however, must be a letter.
request 101 from an analysis named test is referred to as .test.req101.
When you read into Adams View request and result files, Adams View creates several predefined result
set types. For example, if you read in a request file named SHIFT.REQ, and this request file contains
the result information for the statement REQUEST/1, the result set is named REQ1, and can also be
referred to as being relative to the analysis name .shift.req1. If you want to refer to a component in
the same result set, the full name for the X component would be .SHIFT.REQ1.X.
request (.req) and results (.res) files
File that result is

Result set type Result set name Component names from
vx vy vz wx wy wz

numeric_results 5
numeric_results component modify
File that result is



Allows you to modify a result set component.
Format:
result_set_component_name = existing result set
values= real
Example:
For example, the following command generates a full-cycle sine curve with 100 points:
numeric_results component modify &

new_result_set_component_name= req1.x &
result_set_component_name= sine1.x
Description:

result_set_compo Existing Result Set Name Specifies an existing result set name.
nent_name
Values Real Specifies the real values to be stored
in the result set component. The
values can be a list of numbers, or an
expression defining an array of
values.
Units No_units, Calculate, Length, Angle, Mass, Specifies the type of units to be used
Density, Time, Area, Volume, Velocity, for the new result set component.
Acceleration, Angular_velocity, Once you set the unit type, Adams
Angular_acceleration, Inertia, Area_inertia, View can perform the proper unit
Damping, Stiffness, Torsion_stiffness, conversion on the data.
Torsion_damping, Force, Torque, Pressure,
Force_time, Torque_time
set:

.SHIFT.REQ1.NEW (it is not necessary to include .SHIFT., if SHIFT is the current
analysis_name).
numeric_results 7
File that result is

vx vy vz wx wy wz
numeric_results create absolute_value

Allows you to take the absolute value of a real component or the magnitude of a complex component.
Format:
result_set_component_name = an existing component
new_result_set_component_name = a new component
units = units_type_with_calc
Example:
numeric_results create absolute_value &
result_set_component_name = time &
new_result_set_component_name = rsc__1 &
units = time
Description:

result_set_component_name An Existing Component Identifies the component of an existing
result set.
new_result_set_component_name A New Component Allows you to identify where the new
data components are to be stored.
units Units_Type_With_Calc Allows you to specify the type of units to
be used for the new result set
component.
numeric_results 9
1. The component must be in an existing result set and reference to the component must include the
result set name. For example, assume you have read a request file called "SHIFT.REQ", and this
request file contains the result set REQ1. If you wish to refer to the X component in the result set
REQ1, enter .SHIFT.REQ1.X (the .SHIFT. may be omitted if shift is the current analysis_name).
SHIFT refers to the analysis name that that result set came from (or is stored under).
REQ1, and may also be referred to as being relative to the analysis name .shift.req1. If you wish to
refer to a component in the same result set, the full name for the X component would be
.SHIFT.REQ1.X.
The following table illustrates the default names assigned to result sets and result set components, read from
File that result is

vx vy vz wx wy wz


File that result is

2. If the component is to be stored in an existing result set, then the name entered must include the result
set. For example, assume you have read a request file called "SHIFT.REQ", and this request file
contains the result set REQ1. If you wish to store the new result set component in result set REQ1
with the component name NEW, enter .SHIFT.REQ1.NEW (The .SHIFT. can be left off if SHIFT
is the "current" analysis_name). If you wish to store the component in a new result set named REQ99
in the analysis run SHIFT, enter .SHIFT.REQ99.NEW. The number of components to be stored
is inferred by the number of components named in this parameter. Multiple names can be entered
separated by commas (,).
This is a required parameter and the component name given must be unique even though it may be
stored in an existing result set. A result set name may be arbitrarily long and a combination of letters
of the alphabet and numbers may be used. The leading character must be a letter.
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz

numeric_results 11
numeric_results create addition
File that result is


3. Once the unit type is set, Adams View can perform the proper unit conversion on the data. If the
value for the “units” parameter is calculate, Adams View tries to determine the units to use for this
operation. For example, if velocities are added (length/time), then the calculated “units” parameter
for the new result set component is velocity (length/time). If the derivative of a velocity is taken, the
calculated “units” parameter is acceleration (length/time**2).

Adds two components of a result set, either real or complex. The two components must:
 Have the same number of elements. Otherwise, Adams View issues an error and does not execute the
command.
 Be from the same domain: either the time domain or the frequency domain. Otherwise, Adams
View issues an error and does not execute the command.
If the two components are complex, the new component will be complex. A component containing
the magnitude of the new component is also created and is named name_MAGNITUDE. For
example, if the new component is named X, the magnitude component will be named
X_MAGNITUDE.
Format:
result_set_component_names = existing result set components
units = Type of units
Example:
numerical_results create addition &
new_result_set_component_name= dingdong.bell &
result_set_component_name= res101.x, res102.y
Description:

new_result_set_component_na New Result set name Identifies the new result set
me component.
result_set_component_names Existing result set components Identifies two result set
components on which to
perform the operation.
Units no_units, calculate, length, angle, Specifies the type of units
mass, density, time, area, volume, to be used for the new
velocity, acceleration, angular_velocity, result set component.
angular_acceleration, inertia, Once you set the unit type,
area_inertia, damping, stiffness, Adams View can perform
torsion_stiffness, torsion_damping, the proper unit conversion
force, torque, pressure, force_time, on the data.
torque_time
1. 1. The heirarchy of a model's results is shown below with the components of a result set under the
result set:
.SHIFT.REQ1.NEW (it's not necessary to include .SHIFT., if SHIFT is the
current analysis_name).
numeric_results 13
• In a new results set, for example named REQ99 in the analysis run SHIFT, enter
result set name can be any length and any combination of alphanumeric characters. The leading
See a table below that illustrates the default names assigned to result sets and result set components
read from request (.req) and results (.res) files.
vx vy vz wx wy wz

coupler COUxxx... fx1 fy1 fz1 tx1 ty1 tz1 fmag1 results file
tmag1
fx2 fy2 fz2 tx2 ty2 tz2 fmag2

tmag2

tmag3
numeric_results create definite_integral
this operation. For example, if velocities are ADDed (length/time), the calculated units for the new
result set component are a velocity (length/time). If the derivative of a velocity is is taken, the
calculated units are acceleration (length/time**2).
(length/time**3) is multiplied with a result set component with the same units, the calculated units
are (length**2/time**6). Because the exponent of time the is greater than four, Adams View uses
no_units and issues a warning.
Values are: no_units, calculate, length, angle, mass, density, time, area, volume, velocity, acceleration,
angular_velocity, angular_acceleration, inertia, area_inertia, damping, stiffness, torsion_stiffness,
torsion_damping, force, torque, pressure, force_time, torque_time.

Allows you to calculate the definite integral of an existing result set component.
Format:
result_set_component_names = 2 existing components
Example:
numeric_results create definite_integral &
result_set_component_names = rsc__1 , rsc__2 &
units = time
numeric_results 15
Description:

result_set_component_names An Existing Component Identifies two result-set components
to perform the operation on.
new_result_set_component_na A New Component Allows you to identify where the
me new data components are to be
stored.
units Units_Type_With_Calc Allows you to specify the type of
units to be used for the new result
set component.
1. The definite integral operation evaluates the area under the result set component data curve over the
closed interval represented by the result set component data.
The integral is calculated by fitting a cubic spline to the result set component data and analytically
evaluating the definite integral. In other words, the cubic spline fit gives a polynomial representation
of the segments that represent the data This polynomial in then analytically integrated over the closed
interval of the data.
SHIFT refers to the analysis name from which that result set came from (or is stored under).
refer to a component in the same result set the full name for the X component would be
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz


If one component is complex, and the other is real, the real component is promoted to complex. If
the two components are of different lengths, the longer one is truncated (only for that operation).
If the new component being created is complex, a MAGNITUDE component is automatically
generated. If the component is being added to an existing result set and a MAGNITUDE component
already exits, an error will be issued.
is inferred by the number of components named in this parameter. Multiple names can be entered,
numeric_results 17
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz


numeric_results create differentiation

Allows you to calculate the derivative function of an existing result set component.
Format:
result_set_component_names = 2 existing components
Example:
numeric_results create differentiation &
result_set_component_names = rsc1,rsc2 &
units = time
Description:

result_set_component_names An Existing Component Identifies two result-set components to
perform the operation on.
units Units_Type_With_Calc Allows you to specify the type of units
to be used for the new result set
component.
numeric_results 19
5. This operation numerically differentiates the result set component data over the closed interval
represented by its finite set of data points.
The derivative is evaluated by fitting a cubic spline to the result set component data and analytically
forming the derivative. In other words, the cubic spline fit gives a polynomial representation of the
segments that represent the data. This polynomial in then analytically differentiated over the closed
interval of the data.
.SHIFT.REQ1.X.
The following table illustrates the default names assigned to result sets and result set components read from
File that result is

vx vy vz wx wy wz


File that result is

the two components are different lengths, the longer one is truncated (only for that operation).
REQ1, and may also be referred to relatives of the analysis name .shift.req1. If you wish to refer to a
component in the same result set, the full name for the X component would be .SHIFT.REQ1.X.
The following table illustrates the default names assigned to result sets and result set components read
from request (.REQ) and results (.RES) files.
numeric_results 21
File that result is

vx vy vz wx wy wz


8. Once the unit type is set, Adams View can perform the proper unit conversion on the data.
If the value for this parameter is calculated, Adams View will try to determine the units to use for this
operation. For example, if velocities are ADDed (length/time), the calculated units for the new result
set component will be a velocity (length/time). If the derivative of a velocity is is taken, the calculated
units will be acceleration (length/time**2).
Adams View, at this time, can only handle calculated units with a maximum exponent for the base
units (force, length, mass, time) is plus or minus four (4). For example, if a result set component
with the units (length/time**3) is multiplied with a result set component with the same units, The
calculated units would be (length**2/time**6). Since the exponent is greater than 4, Adams View
will use NO_UNITS and issue a warning.
numeric_results create division

Allows you to divide two components (the first by the second), either real or complex.
Tests are made for overflow and underflow.
 Underflow is the condition where the numerator is near zero irrespective of the denominator value,
and always results in zero:
0/0-1=0
0/0 = 0
 Overflow is when the denominator is zero and results in 1E25:
1/0 = 1E25
9E100/0 = 1E25
-4/0 = 1E25
The two components must have the same number of elements, or an error is issued and the
command is aborted.
The two components must be from the same domain, either the TIME domain or the FREQUENCY
domain, or an error is issued and the command is aborted.
If the two components are complex, the new component will be complex.
A component containing the magnitude of the new component will also be created. It is named
'name_MAGNITUDE'. For example, if the new component is named 'X', the magnitude component will
be named 'X_MAGNITUDE'.
Format:
Example:
numerical_results create division &
new_result_set_component_name = dingdong.bell &
result_set_component_name = res101.x, res102.y
numeric_results 23
Description:

new_result_set_component_name New Result Set Name Identifies the new result set
component.
result_set_component_names Existing Result Set Components Identifies two result set
Units No_units, Calculate, Length, Angle, Specifies the type of units
Mass, Density, Time, Area, Volume, to be used for the new
Velocity, Acceleration, result set component.
Angular_velocity, Once you set the unit type,
Angular_acceleration, Inertia, Adams View can perform
Area_inertia, Damping, Stiffness, the proper unit conversion
Torsion_stiffness, Torsion_damping, on the data.
Force, Torque, Pressure, Force_time,
Torque_time
set:

 In an existing result set, the name must include the result set. For example, assume you have a
.SHIFT.REQ1.NEW (It is not necessary to include .SHIFT., if SHIFT
is the current analysis_name).
 In a new results set, named REQ99, for example, in the analysis run SHIFT, enter
The component name must be unique, even though it can be stored in an existing result set. A result
set name can be of any length and any combination of alphanumeric characters. The leading
File that result is

vx vy vz wx wy wz


numeric_results 25
numeric_results create dynamic_polyline

Allows you to create a result set which specifies time dependent locations for polylines.
Format:
polyline_name = an existing polyline
vertex = integer
z_result_set_component_name = z_result_set_component_name
Example:
numeric_results create dynamic_polyline &
polyline_name = an existing polyline &
vertex = 10 &
Description:

polyline_name An Existing Specifies an existing POLYLINE
Polyline
vertex Integer Specifies the vertex this result set corresponds to.
x_result_set_component_na An Existing Specifies the name of a result set component to be
me Component used to drive the vertex in the X direction over time.

y_result_set_component_na An Existing Specifies the name of a result set component to be
me Component used to drive the vertex in the Y direction over time.
z_result_set_component_na An Existing Specifies the name of a result set component to be
me Component used to drive the vertex in the Z direction over time.
Model,Part OR coordinates and orientation angles correspond to.
Marker
1. Just as a part's locations and orientations for the steps of a simulation are stored in a result set, you
can create a result set that has the time dependent locations for polylines that are children of a model.
When the model is displayed at a time step with the single_frame_display command, or is animated
with the animation command, Adams View will use these result sets to display the polylines.
This allows you to drive each component (X, Y, and Z) of a vertex of a polyline from any result test
component including the output of any Adams equation.
For example, you could model a flexible air bag as a mesh of polylines, and using Adams equations
(linear state equations, general state equations), specify the location of the vertices of the mesh over
time. When the model is animated it would show the air bag deployment.
The polylines must be children of a model.
Each result set contains the X, Y, and Z data for a vertex of a polyline The names of the result sets
created are encoded with the name of the polyline and the vertex number. The components of the
result set are named 'X', 'Y' and 'Z'. For example, if the name of the polyline is 'POL1' and the you
are creating the result set for the second vertex, the result set name will be 'POL1_LOCATION_2'.
If Adams View cannot find the result set components, it will use the location specified when the
model was created, and will not vary over time.
2. You may identify a POLYLINE by typing its name or by picking it from the screen.
If the POLYLINE is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the POLYLINE is displayed.
Since a POLYLINE cannot be defined in an Adams data set or graphics file, the POLYLINE cannot
interactively, by reading a command file, or by reading an IGES file. POLYLINEs are owned by parts.
If a POLYLINE is available by default, you may identify it by entering only its name. You may need
numeric_results 27
numeric_results create empty
associated with it.
You need not separate multiple POLYLINE picks by commas.
Tips:
1. IF no X_RESULT_SET_COMPONENT_NAME is specified, the X component of the vertex does
not change over time. This holds the same for the Y and Z components of the vertex.

Allows you to create an empty result set.
Format:
new_result_set_name = a new component
comments = string
Example:
numeric_results create empty &
new_result_set_name = rsc__empty &
comments = “an empty result set”
Description:

new_result_set_name A New Component This parameter allows you to identify where the
new data components are to be stored.
modified.
of the segments that represent the data. This polynomial in then analytically integrated over the
closed interval of the data.
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz

numeric_results 29
numeric_results create fft
File that result is



Allows you to use FFT (Fast Fourier Transform) to change a result set component from the time domain to
the frequency domain, and back.
Because the FFT algorithm requires an evenly spaced sampling of elements and the number of elements must
be a power of two (512, 1024, and so on), the data is interpolated before the FFT. The default interpolation
method is the Akima method with 1024 elements. These values can be overridden.
If the input is a real component with N interpolated elements, this operation generates a complex component
of (N+1)/2 elements with the name specified in the NEW_RESULTS_NAME parameter. It also generates
the real components, FREQUENCY and one named 'name'_MAGNITUDE of size N/2, and places these
components in the same result set as the complex component. For example, the command:
result_set_component_name=Res.timeDomain &
new_result_set_name=fft.x
results in:
fft.x - complex result in the frequency domain
fft.x_MAGNITUDE - mag (fft.x)

fft.FREQUENCY
If the input is a complex component, this command performs an inverse FFT, and generates a real component
with the name specified in the new_results_set_name parameter. It also generates the real component TIME.
For example:
result_set_component_name=res.frequencyDomain &
new_result_set_name=inverseFFT.x
Note: If you perform an FFT on a component, and then perform an inverse FFT on the result,
Adams View does not return the same data, because the original data is interpolated
There is no interpolation for an inverse FFT.
Format:
interpolate_type = interpolation_type
number_of_points = integer
Example:
numerical_results create fft &
result_set_component_name = res101.x, res102.y &
interpolate_type = linear &
number_of_points = 1024
Description:

new_result_set_c New Result Set Name Identifies the new result set component.
omponent_name
result_set_compo Existing Result Set Components Identifies two result set components on which to
nent_names perform the operation.
numeric_results 31

Interpolate_type Linear, Cubic, Akima, Cspline Specifies the method to interpolate the result set
component.
Number_of_poi Integer Specifies the number of interpolation points used
nts in the fitting of data contained in a result set
component. You might want to use this curve-
fitting operation in preparation for an FFT
operation, and so on.
Units No_units, Calculate, Length, Specifies the type of units to be used for the new
Angle, Mass, Density, Time, Area, result set component. Once you set the unit type,
Volume, Velocity, Acceleration, Adams View can perform the proper unit
Angular_velocity, conversion on the data.
Angular_acceleration, Inertia,
Area_inertia, Damping, Stiffness,
Torsion_stiffness,
Torsion_damping, Force, Torque,
Pressure, Force_time,
Torque_time
set:

.SHIFT.REQ1.NEW (It is not necessary to include .SHIFT., if SHIFT is the current
analysis_name).
result set name can be any length and any combination of alphanumeric characters. The leading
File that result is

vx vy vz wx wy wz


numeric_results 33
numeric_results create filter
3. If the interpolation operation is in preparation for an FFT, then the number of points must be an
even power of two (for example, 256, 512, and 1024).
If you do not specify this parameter, it defaults to 1024.
If you specify this parameter, you must use a positive integer.
Once you change the value of this parameter, Adams View will remember the new value and use it as
the default the next time you need this parameter.

Allows you to test each value of the component; if the value is above the specified maximum value, or below
the specified minimum value, set it to zero. For example: If the component is a discrete sampling of a
sinusoidal wave with an amplitude of one (1), and filter is requested with a maximum value of .9
(above_value=.9), all the values corresponding to 'sin (x) > .9' will be set to 0.
Format:
below_value = real
above_value = real
Example:
numeric_results create filter &
units = time
Description:

result_set_component_name An Existing Component Identifies the component of an existing
result set.
new_result_set_component_na A New Component This parameter allows you to identify where
me the new data components are to be stored.
below_value Real The BELOW_VALUE parameter is used as
a critical value evaluator in the operation to
be performed.
above_value Real The ABOVE_VALUE parameter is used as a
critical value evaluator in the operation to be
performed.
units Units_Type_With_Calc Allows you to specify the type of units to be
used for the new result set component.
.SHIFT.REQ1.X.
numeric_results 35
File that result is

vx vy vz wx wy wz

tmag1

tmag2

tmag3
in the analysis run SHIFT, enter .SHIFT.REQ99.NEW. The number of components to be stored is
inferred by the number of components named in this parameter. Multiple names can be entered
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz


numeric_results 37
numeric_results create interpolation
3. The below_value parameter is a critical value which determines the threshold below which a
particular numeric value will be modified, printed, etc. (depending on the operation to be
performed).
This parameter is optional and if not entered, no value will be passed to the application, and therefore,
no action will be taken based on the BELOW_VALUE parameter. If entered, the BELOW_VALUE
parameter must be a real number.
4. The above_value parameter is a critical value which determines the threshold above which a particular
numeric value will be modified, printed, etc. (depending on the operation to be performed).
no action will be taken based on the ABOVE_VALUE parameter. If entered, the ABOVE_VALUE

Allows you to create an evenly spaced sampling of the component.
This operation does not assume the points are evenly spaced, it uses the "TIME" or "FREQUENCY"
component as the dependent variable.
The "TIME" or "FREQUENCY" component is also interpolated to be evenly spaced. The new
TIME/FREQUENCY component is stored with the new component
Format:
interpolate_type = interpolation_type
number_of_points = integer
Example:
numeric_results create interpolation &
units = time
Description:

result_set_component_na An Existing Component Identifies the component of an existing result
me set.
new_result_set_component A New Component Allows you to identify where the new data
_name components are to be stored.
interpolate_type Interpolation_Type Specifies the three methods used to interpolate
the result set component.
number_of_points Integer Specifies the number of interpolation points
used in the fitting of data contained in a result
set component.
request file contains the result set REQ1.If you wish to refer to the X component in the result set
contains the result information for the Adams statement REQUEST/1.The result set will be named
.SHIFT.REQ1.X.
numeric_results 39
File that result is

vx vy vz wx wy wz


request REQxxx... x y z r1 r2 r3 mag amag REQUEST file
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz

tmag1

tmag2

tmag3
numeric_results 41
numeric_results create linear_equation
4. The three methods used to interpolate the result set component:
linear - uses the first order LaGrangian interpolation
cubic - uses the second order LaGrangian interpolation
akima - uses the Akima method, as documented in Journal of the Association Computing Machinery
Vol 17, No 4, October 1970.
5. This curve fitting operation could be desired by the user, in preparation for an FFT operation, etc.
If the interpolation operation is in preparation for an FFT, then the number of points must be an
even power of two. (e.g. 256, 512, 1024, etc.).
This is an optional parameter and if not entered, will be set to 1024.
If entered, the NUMBER_OF_POINTS parameter must be a positive integer.
Also, once changed by the user, the new value will be remembered and used as default the next time
the parameter is needed.

Allows you to multiply two components of a result set, either real or complex. The two components must:
command.
X_MAGNITUDE.
Format:
a_multiplier = real
b_multiplier = real

Example:
numerical_results create linear_equation &
a_multiplier = (2*365+7.2) &
b_multiplier = 25.7 &
Description:

A_multiplier Real The A_MULTIPLIER parameter is used as
a constant coefficient in the
linear_equation operation for manipulating
numeric results. The linear equation is of
the form:
A*X + B*Y = Result Where A corresponds

to the A_MULTIPLIER.
B_multiplier Real The B_MULTIPLIER parameter is used as
a constant coefficient in the
linear_equation operation for manipulating
numeric results. The linear equation is of
the form:
A*X + B*Y = Result where B corresponds to

the B_MULTIPLIER. This parameter is
optional and if not entered, it will default to
1.0. If entered, the B_MULTIPLIER must
be a real number.
numeric_results 43

new_result_set_comp New Result Set Name Identifies the new result set component.
onent_name
result_set_componen Existing Result Set Components Identifies two result set components on
t_names which to perform the operation.
Units No_units, Calculate, Length, Angle, Specifies the type of units to be used for the
Mass, Density, Time, Area, Volume, new result set component. Once you set the
Velocity, Acceleration, unit type, Adams View can perform the
Angular_velocity, proper unit conversion on the data.
Angular_acceleration, Inertia,
Area_inertia, Damping, Stiffness,
Torsion_stiffness,
Pressure, Force_time, Torque_time
set:

analysis_name).
components named in this parameter. You can enter multiple names, separated by commas (,).
File that result is

vx vy vz wx wy wz


numeric_results 45
numeric_results create multiplication

Allows you to multiply two components of a result set, either real or complex. The two components must:
command.
X_MAGNITUDE.
Format:
Example:
numerical_results create multiplication &
Description:

result_set_compo Existing Result Set Components Identifies two result set
nent_names components on which to perform
the operation.
Units No_units, Calculate, Length, Angle, Mass, Specifies the type of units to be
Density, Time, Area, Volume, Velocity, used for the new result set
Acceleration, Angular_velocity, component. Once you set the unit
Angular_acceleration, Inertia, Area_inertia, type, Adams View can perform
Damping, Stiffness, Torsion_stiffness, the proper unit conversion on the
Torsion_damping, Force, Torque, Pressure, data.
Force_time, Torque_time
set:

analysis_name).
numeric_results 47
The table below illustrates the default names assigned to result sets and result set components, read
from request (.req) and results (.res) files.
File that result is

vx vy vz wx wy wz


numeric_results create percent_difference

Allows you to calculate the percent difference of two real result set components using the formula:
((x1-x2)*100/x1)
where:
x1 is an element of the first component

x2 is an element of the second component
Note that:
 If x1 is zero and x2 is zero, the result is zero.
 If x1 is zero and x2 is nonzero, the result is +/- infinity with the sign taken from x2.
Format:
Example:
numerical_results create percent_difference &
numeric_results 49
Description:

new_result_set_component_name New ResulT Set Name Identifies the new result
set component.
Units No_units, Calculate, Length, Angle, Specifies the type of units
Mass, Density, Time, Area, Volume, to be used for the new
Velocity, Acceleration, result set component.
Angular_velocity, Once you set the unit
Angular_acceleration, Inertia, type, Adams View can
Area_inertia, Damping, Stiffness, perform the proper unit
Torsion_stiffness, Torsion_damping, conversion on the data.
Torque_time
set:

analysis_name).
File that result is

vx vy vz wx wy wz


numeric_results 51
numeric_results create scale

Allows you to multiply all the elements of a result set component, either real or complex, by some value and
then add a constant value. The form of the equation is:
Ax + B = Result
Format:
a_scale_value = real
b_offset_value = real
Example:
numeric_results create scale &
units = time
Description:

result_set_component_nam An Existing Component Identifies the component of an existing
e result set.
new_result_set_component A New Component Allows you to identify where the new data
_name components are to be stored.
a_scale_value Real The A_SCALE_VALUE parameter is used
as a constant coefficient in the scale
operation for manipulating numeric
results.
b_offset_value Real Specifies the constant real value that is to be
added to a scaled
RESULT_SET_COMPONENT
.SHIFT.REQ1.X.
numeric_results 53
Result set type Result set name Component names File that result is from
vx vy vz wx wy wz

tmag1

tmag2

tmag3
If the component is to be stored in an existing result set, then the name entered must include the result
stored in an existing result set. A result set name may be arbitrarily long, and a combination of letters
.SHIFT.REQ1.X.
The following table illustrates the default names assigned to result sets and result set components, read
vx vy vz wx wy wz


numeric_results 55
numeric_results create spline
Once the unit type is set, Adams View can perform the proper unit conversion on the data. If the
2. The scaling equation is of the form:
A*X + B = Result
where A corresponds to the A_SCALE_VALUE and B corresponds to the B_OFFSET_VALUE parameter.
3. The B_OFFSET_VALUE parameter is used as a constant coefficient in the scale operation for
manipulating numeric results. The scaling equation is of the form:
A*X + B = Result
where B corresponds to the B_OFFSET_VALUE.

Allows you to create a result set from spline data points.
Format:
new_result_set_name = new_result_set_name =
z = real
Example:
numeric_results create spline &
new_result_set_name = rsc__1 &
z = 3.1 &
units = force
Description:

spline_name An Existing Spline Specifies an existing spline.
new_result_set_name A New Result Set Allows you to identify the new result set name to
be created with this operation.
z Real
units Units_Type_With_Calc Allows you to specify the type of units to be used
for the new result set component.
1. You may plot the result set to display the data points, or use it with the 'NUMERIC_RESULTS
CREATE INTERPOLATION' command to construct an interpolated curve.
If the spline has one independent variable (x), Adams View will create a result set with two
components named 'x' and 'y'. These components will contain the x and y values you entered when
creating the spline.
If a spline has one independent variable (x), Adams View ignores parameter Z. If a spline has two
independent variables (x and z), you may optionally specify the Z parameter.
If you do not specify Z, Adams View will create a result set with components named 'x', 'z', and 'y_1',
'y_2', ... 'y_n', where 'n' is the number of z values. These components will include the x, y, and z
values you entered when creating the spline. There will be a y component for each z value, and the
lengths of the x and y components will be the same.
If you do enter a Z value, Adams View will create a result set with two components named 'x' and 'y'.
Component 'x' will contain the x values you entered when creating the spline. Adams View will create
component 'y' by finding the two z values nearest to the value you specify, and linearly interpolating
between the corresponding sets of y values.
2. You identify a spline by typing its name. If you created the spline by reading an Adams data set, the
spline name is the letters SPL followed by the Adams data set spline ID number. For example, the
name of Adams SPLINE/101 is SPL101. If you created the spline during preprocessing, you will have
given it a name at that time.
If a spline is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a spline under another model, for instance, you may need to enter the
model name as well. For example, you may specify spline 'stiffness' from model 'suspension' by
entering ".suspension.stiffness". If you type a "?", Adams View will list the splines available by default.
You must separate multiple spline names by commas.
components. Result sets are associated with an Adams analysis run and can be identified as such. A
result set associated with request 101 from and analysis named "test" is referred to as .test.req101.
numeric_results 57
This is a required parameter and the result set name given must be unique within the particular
analysis name. A result set name may be arbitrarily long, and a combination of letters of the alphabet
and numbers may be used. The leading character must be a letter.
File that result is

vx vy vz wx wy wz


numeric_results create sqrt_sum_of_squares

Allows you to add two components of a result set, either real or complex. The two components must:
command.
If the two components are complex, the new component will be complex. A component containing the
magnitude of the new component is also created and is named name_MAGNITUDE. For example, if the new
component is named X, the magnitude component will be named X_MAGNITUDE.
Format:
Example:
numerical_results create sqrt_sum_of_sqares &
numeric_results 59
Description:

new_result_set_component_nam New Result Set Name Identifies the new result set
e component.
Units No_units, Calculate, Length, Specifies the type of units to be
Angle, Mass, Density, Time, Area, used for the new result set
Volume, Velocity, Acceleration, component. Once you set the
Angular_velocity, unit type, Adams View can
Angular_acceleration, Inertia, perform the proper unit
Area_inertia, Damping, Stiffness, conversion on the data.
Torsion_stiffness,
Pressure, Force_time, Torque_time
set:

In a new results set, named REQ99, for example, in the analysis run SHIFT, enter
components named in this parameter. You can enter multiple names separated by commas (,).
The table below illustrates the default names assigned to result sets and result set components read from
File that result is

vx vy vz wx wy wz


numeric_results 61
numeric_results create subtraction

Allows you to subtract two components of a result set, either real or complex. The two components must:
 Have the same number of elements. Otherwise, AdamsAdams View issues an error and does not
execute the command.
If the two components are complex, the new component will be complex. A component containing the
magnitude of the new component is also created and is named name_MAGNITUDE. For example, if the new
component is named X, the magnitude component will be named X_MAGNITUDE.
Format:
Example:
numerical_results create subtraction &
Description:

new_result_set_component_na New Result Set Name Identifies the new result set
me component.
Units No_units, Calculate, Length, Angle, Specifies the type of units to be
Mass, Density, Time, Area, Volume, used for the new result set
Velocity, Acceleration, component. Once you set the
Angular_velocity, unit type, Adams View can
Angular_acceleration, Inertia, perform the proper unit
Area_inertia, Damping, Stiffness, conversion on the data.
Torsion_stiffness, Torsion_damping,
Torque_time
set:

analysis_name).
numeric_results 63
vx vy vz wx wy wz
tmag1
tmag2
tmag3
numeric_results create values

Allows you to create a result set by specifying the values directly.
Format:
values = real
Example:
numeric_results create values &
values = 10, 10, 11, 12, 13, 15 &
units = time
Description:

values Real Specifies the real values to be stored in
the result set component.The values
can be a list of numbers, or an
expression referencing an array of
existing values.
component.
numeric_results 65
of the segments that represent the data. This polynomial in then analytically integrated over the
closed interval of the data.
.SHIFT.REQ1.X.
vx vy vz wx wy wz


the two components are of different lengths, the longer one is truncated. (Only for that operation)
.SHIFT.REQ1.X.
numeric_results 67
File that result is

vx vy vz wx wy wz


numeric_results create zero

Allows you to zero the values of the component that correspond to TIME/FREQUENCY component which
are above a maximum value and below a minimum value.
If no corresponding TIME/FREQUENCY component exists, an error will be issued.
Format:
below_value = real
above_value = real
Example:
numeric_results create zero &
units = time
Description:

result_set_component_nam An Existing Component Identify the component of an existing
e result set.
new_result_set_component A New Component Allows you to identify where the new
_name data components are to be stored.
below_value Real The BELOW_VALUE parameter is
used as a critical value evaluator in the
operation to be performed.
above_value Real The ABOVE_VALUE parameter is
used as a critical value evaluator in the
operation to be performed.
component.
numeric_results 69
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz

tmag1

tmag2

tmag3
File that result is

2. If the component is to be stored in an existing result set, then the name entered must include the
result set. For example, assume you have read a request file called "SHIFT.REQ", and this request file
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz

numeric_results 71
File that result is


3. The below_value parameter is a critical value which determines the threshold below which a
particular numeric value will be modified, printed, etc. (depending on the operation to be
performed).
4. The above_value parameter is a critical value which determines the threshold above which a particular
numeric value will be modified, printed, etc. (depending on the operation to be performed).
numeric_results delete
Allows you to delete an entire result set.
Format:
result_set_name = existing result_set name
Example:
numeric_results delete &
result_set_name = res_01
Description:

result_set_name Existing result set Identifies a result set to be deleted.
1. A result set is a storage place for any kind of numeric tabular data. A result set can contain any number
of components. A component is usually set up to contain vector components of values such as
displacement, velocity, acceleration, and force. In this case, however, a result set is completely general
and can store any numeric value in a component with few exceptions. These exceptions are those cases
when you ask the system to mix incompatible value types, such as complex values in the same
The result set name given must be within a particular analysis. A result set name can be of any length,
and any combination of letters and numbers. The leading character, however, must be a letter.
request 101 from an analysis named test is referred to as .test.req101.
When you read into Adams View request and result files, Adams View creates several predefined result
set types. For example, if you read in a request file named SHIFT.REQ, and this request file contains
the result information for the statement REQUEST/1, the result set is named REQ1, and can also be
referred to as being relative to the analysis name .shift.req1. If you want to refer to a component in
the same result set, the full name for the X component would be .SHIFT.REQ1.X.
numeric_results 73
numeric_results list_info all
File that result is

vx vy vz wx wy wz

Allows you to use the ALL keyword to control what information about a particular result set component
should be included as it is written to the terminal or file using the NUMERICAL_RESULTS LIST_INFO
command.
Format:
file_name = string
Example:
numeric_results list_info all &
file_name = "c:\info.txt"
Description:

result_set_component_name An Existing Identifies the component of an existing result set.
Component
write_to_terminal On_Off Specifies whether the information requested is to be sent
to the informational window or not.
file_name String Specifies that the information requested is to be sent to
1. If selected, the ALL keyword will cause the MAXIMUM_VALUE, MINIMUM_VALUE,
TIME_RANGE, (or frequency, if appropriate) and NO_OF_TIME_STEPS to be output in the
form of an informational message.
If there is no time/frequency range, the value listed is zero (0).
List all the information about the specified component.
.SHIFT.REQ1.X.
numeric_results 75
numeric_results list_info maximum_value
File that result is

vx vy vz wx wy wz
3. This parameter is most likely to be used in conjunction with the FILE_NAME parameter to get the
information to be put into a file.

Allows you to use the MAXIMUM_VALUE keyword to control what information should be included about
a particular result set component as it is written to the terminal or file using the NUMERICAL_RESULTS
LIST_INFO command.
Format:

file_name = string
Example:
numeric_results list_info maximum_value &
result_set_component_name = TIME &
Description:

result_set_component_nam An Existing Identifies the component of an existing result set.
e Component
write_to_terminal On_Off Specifies whether the information requested is to be
sent to the informational window or not
file_name String Specifies that the information requested is to be sent to
1. If selected, the MAXIMUM_VALUE keyword will cause the maximum value of the desired result set
component to be output in the form of an informational message.
This command has one required parameter, which is RESULT_SET_COMPONENT_NAME. All
other parameters have default settings, or are optional.
.SHIFT.REQ1.X.
numeric_results 77
numeric_results list_info minimum_value
File that result is

vx vy vz wx wy wz

Allows you to use the MINIMUM_VALUE keyword to control what information about a particular result
set component should be included as it is written to the terminal or file using the NUMERICAL_RESULTS
LIST_INFO command.
Format:
file_name = string
Example:
numeric_results list_info minimum_value &
Description:

result_set_component_name An Existing Component Identifies the component of an existing result
set.
write_to_terminal On_Off Specifies whether the information requested
is to be sent to the informational window or
not.
file_name String Specifies that the information requested is to
be sent to a file with the name specified with
the parameter.
1. If selected, the MINIMUM_VALUE keyword will cause the minimum value of the desired result set
component to be output in the form of an informational message.
other parameters have default settings or are optional.
numeric_results 79
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz


numeric_results list_info number_of_time_steps

Allows you to use the NUMBER_OF_TIME_STEPS keyword to control what information about a
particular result set component should be included as it is written to the terminal or file using the
NUMERICAL_RESULTS LIST_INFO command.
Format:
on_off string
Example:
numeric_results list_info number_of_time_steps &
Description:

set.
write_to_terminal On_Off Specifies whether the information requested is
to be sent to the informational window or not.
the parameter.
1. If selected, this parameter will cause the NUMBER_OF_TIME_STEPS to be output in the form of
an informational message.
numeric_results 81
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz


user request UREQxxx... u1 u2 u3 u4 u5 u6 u7 u8
request REQxxx... x y z r1 r2 r3 mag amag
information to be put to a file.
numeric_results list_info time_range

Allows you to use the TIME_RANGE keyword to control what information about a particular result set
component should be included as it is written to the terminal or file using the NUMERICAL_RESULTS
LIST_INFO command.
Format:
file_name = string
Example:
numeric_results list_info time_range &
Description:

set.
write_to_terminal On_Off Specifies whether the information requested
is to be sent to the informational window or
not.
the parameter.
1. If selected, the TIME_RANGE keyword will cause the time range that the result set spans to be
output in the form of an informational message.
If there is no time range, the frequency range is listed. If there is no frequency range also, all the values
are listed as zero (0).
other parameters have default settings or are optional.
numeric_results 83
.SHIFT.REQ1.X.
File that result is

vx vy vz wx wy wz

x2 fy2 fz2 tx2 ty2 tz2 fmag2 tmag2

numeric_results modify
File that result is

information to be put to a file.
Allows you to change the units of an existing result set component. You can reverse modifications using the
undo command.
Format:
Example:
numeric_results modify &
res= req1.x &
units= "length/time"
Description:

Units no_units, calculate, length, angle, Specifies the type of units to be
mass, density, time, area, volume, used for the new result set
velocity, acceleration, component. Once you set the
angular_velocity, unit type, Adams View can
angular_acceleration, inertia, perform the proper unit
area_inertia, damping, stiffness, conversion on the data.
torsion_stiffness, torsion_damping,
force, torque, pressure, force_time,
torque_time
numeric_results 85
1. The hierarchy of a model's results is shown below with the components of a result set under the result
set:

 In a new results set, named REQ99, for example, in the analysis run SHIFT, enter
components named in this parameter. You can enter multiple names separated by commas (,).
File that result is

vx vy vz wx wy wz

numeric_results read_from_file
File that result is


Allows you to read components from an ASCII file into an existing result set or into a new result set. You can
specify the names of the components, as well as the name of the result set.
To accommodate a wide variety of formats used by third-party software, the format of the file to be read is
intentionally general. Adams View only reads the lines that begin with a number. All other lines are
considered comments and are ignored. Using this command, output files generated from finite element,
modal analysis, or custom programs can be read into Adams View and combined with data read from the
Adams output files. You can use files that numeric_results write command generates with this command.
This allows for the saving of important data between Adams View sessions.
numeric_results 87
The format supported by the Adams View file reader is a flexible one.
All lines that do not begin with a number are considered comments.
Other lines are read by Adams View. Adams View starts at the first line of the file and reads one line at a time.
Lines that do not begin with a number (digit,-,+,decimal point) are considered comments and are ignored.
The number of components to be read is determined by the number of components that are named in the
NEW_RESULT_SET_COMPONENT_NAME parameter. If only 3 components are named in this
parameter, then, only the first three components are read and all others in the file are ignored.
Format:
new_result_set_component_name= new component
number_of_steps= integer
units= string
file_name= string
Example:
numeric_results read_from_file &
new_result_component_name = res_01 &
number_of_steps = 15 &
file_name = “c:\sample_file.txt”
This sample file contains three components. The first two columns of numbers, beginning with 1 and 10.0,
are the first two components and the third column of numbers, beginning with 22, is the third component.
If you do not specify the number of steps, Adams View uses a blank line to delimit the end of a component.
In the following example, the first two components have ten numbers each. If you specify the number of steps
to be read, Adams View continues to read lines until the requested number of steps have been stored in the
component. For example, if only one component was read from the following file and the number of steps
was specified to be 15, the component would contain the values 1, 2, 3.4, -4, 5, 6, 7, 8, 9, 10, 22, 23, .24,
25, 26.
>>>>>> beginning of file <<<<<<<

This is a test file for the NUMERIC_RESULT READ command.
1 10.0
2 11.0
3.4 12.5
-4 13.0
5 +14.0
6 15.5
7 17
8 18
9 19
10 20
22
23
.24
25
26
27
28
29
30
31
>>>>>> end of file <<<<<<<
Description:

new_result_set_component_name, New component Allows you to identify where the
new data components are to be
stored.
number_of_steps, Integer Shows the number of values to be
stored in each component of a
result set being read from a file.
units, String Specifies the type of units to be
used for the new result set
component.
file_name String Specifies the name of the file to
which the information is to be
sent.
1. The hierarchy of a model's results is shown below with the components of a result set under the result
set:
numeric_results 89

 In a new results set, for example named REQ99 in the analysis run SHIFT, enter
(.RES) files.
File that result is

vx vy vz wx wy wz
File that result is

2. All components being read from a file must have the same number of steps.
Lines that do not begin with a number are considered comments and are ignored.
If you do not specify this parameter, Adams View will infer the size of the components from the
format of the file. Adams View will read a component from a file until it encounters a comment line.
A comment line marks the end of the component.
3. Once you set the unit type, Adams View can perform the proper unit conversion on the data. Values
are: no_units, calculate, length, angle, mass, density, time, area, volume, velocity, acceleration,
Cautions:
1. If a paragraph of text contains a line that begins with a number, Adams View tries to read the line.
To avoid this, precede lines that are to be ignored with a non-numeric character. Do not use +, -, or
. because these characters are valid as the first characters in a real number

This sample file contains only one component but contains the number
3 at the beginning of a line in this header paragraph. Adams View will
try to read this line because it is not considered a comment.
 1.5
3.0
4.5
6.0
>>>>>> end of file <<<<<<<
numeric_results 91
numeric_results transform

The same file, without a numerical character, ensures that Adams View does not try to read the paragraph
of text.
 1.5
3.0
4.5
6.0
>>>>>> end of file <<<<<<<
Tips:
1. Numbers can be separated by a comma (,) and they do not have to be lined up in even columns.
Allows you to get results to return at locations other than the positions reported in the result file. The
transform command only transforms the results in the part result sets (these are the result sets denoted by
names of the form xxx_XFORM, where xxx is the part name). The transform command is needed because
the result file only gives displacement, velocity, and acceleration results of the local part reference frame
(LPRF) origin position relative to ground.
You can use the transform command to transform the displacements, velocities, and accelerations of a part's
LPRF to a different position, while it is still rigidly attached to the same part. The transformed results will be
relative to the ground's reference frame as the part moves during the simulation.
You specify the part by naming the result set to be transformed. You specify the location to which you want
to transform the results, by giving its global or LPRF coordinates, or by using the coordinates of a named
marker.
Format:
result_set_name= existing result_set
new_result_set_name= new result set
marker_name= existing marker
lprf_coords= real
global_coords= real
Description:
Paramenter Value Type Descritpion

RESULT_SET_NAME Existing Result Set Allows you to identify a result set name.
NEW_RESULT_SET_NAME New Result Set Allows you to identify the new result set name
to be created with this operation.
MARKER_NAME Existing Marker The MARKER_NAME parameter specifies a
marker whose coordinates are to be used as the
reference position for transformation. The
reference position is fixed relative to the part
indicated by the RESULTS_SET_NAME
parameter throughout the simulation.
LPRF_COORDS Real The LPRF_COORDS parameter provides
the coordinates of a point where information
in a "part result set" should be transformed.
GLOBAL_COORDS Real The GLOBAL_COORDS parameter
provides the coordinates of a point where
information in a "part result set" should be
transformed.
components. A component is most usually setup to contain vector components of values like
displacement, velocity, acceleration, force and so on. However, in this case a result set is completely
general and can store any numeric value in a component with only a few exceptions. These exceptions
are those cases when the user asks the system to mix incompatible value types like complex in the same
This is a required parameter and the result set name given must be within a particular analysis. A result
set name may be arbitrarily long, and a combination of letters of the alphabet and numbers may be
used. The leading character must be a letter.
.SHIFT.REQ1.X.
from request (.REQ) and results (.RES) files
numeric_results 93
vx vy vz wx wy wz


2. If the named marker is actually attached to the part specified by the RESULTS_SET_NAME
parameter, then the marker's LPRF coordinates (which remain fixed, relative to the part throughout
the simulation) are used to perform the transformation. Using these coordinates, the results
(displacement, velocity, and acceleration) associated to the desired part are transformed into the
global (or ground) coordinate system as the part moves during the simulation. Thus creating a new
result set (named based on the NEW_RESULT_SET_NAME parameter).
If the named marker is attached to a part other than the one specified by the RESULTS_SET_NAME
parameter, the program will issue a warning, and proceed. Then, the specified marker's coordinates
are first transformed into the ground reference frame (global coordinates) at the time step
corresponding to the input step (as the model was initially defined in the Adams data set). Then the
marker's global coordinates are transformed into the LPRF of the specified part (also at the time
corresponding to the input step). From this point, these LPRF coordinates (which remain fixed,
relative to the part throughout the simulation, but are no longer associated with the named marker)
are used to perform the transformation as described above.
numeric_results write
A marker name can be entered by specifies an existing marker. You may identify a marker by typing
its name or by picking it from the screen. If the marker is not visible on the screen, you must type the
name. You may also find it convenient to type the name even if the marker is displayed.
name at that time.
You must separate multiple marker names by commas. If the marker is visible in one of your views,
you may identify it by picking on it. You need not separate multiple marker picks by commas.
3. The LPRF coordinates entered are assumed to be fixed to the part in question for purposes of the
transformation. The transformed results will be relative to the ground's reference frame as the part
moves during the simulation. The part is specified by the RESULTS_SET_NAME parameter used
with the TRANSFORM command.
The transformation used is based on the following assumption: The described LPRF coordinates are
assumed to be associated to the part at the time step that corresponds to the model input step (i.e. as
input in the Adams data set).
The LPRF_COORDS parameter consists of six real numbers. The first three coordinates are the
(x,y,z) coordinates of the desired location in the parts local coordinate system. The last three
coordinates are the Euler angles of the desired location in degrees.
4. The global coordinates entered are assumed to be fixed to the part in question for purposes of the
transformation. The transformed results will be relative to the ground's reference frame as the part
moves during the simulation. The part is specified by the RESULTS_SET_NAME parameter used
with the TRANSFORM command.
Even though the coordinates are input in the global (or ground) reference frame, the system associates
them to the part's local part reference frame as defined in the model input step (as input in the Adams
data set).
The first three coordinates are the (x,y,z) coordinates of the desired location, and the last three
coordinates are the Euler angles of the desired location in degrees.
Allows you to write the contents of one or more result set components to the information window, a file, or
both.
numeric_results 95
Format:
sort_by= results_sort
order= sort_order
write_to_terminal= on/off
file_name= string
above_value= real
below_value= real
Example:
numerical_results write &
result_set_component_name = dingdong.bell &
sort_by = by_value &
order = ascending &
file_name = “c:\result_set_file” &
above_value = 5.0 &
below_value = 100.9
The result set specified will be written in the file specified as well as on the screen. Only the values above 5.0
and below 100.9 will be printed and sorted in the ascending order.
Description:

result_set_component_name Existing Result Set Identifies the existing result set.
Component
Sort_by By_time/By_value Specifies how numerical results are sorted as
they are written to the terminal or to a file using
the NUMERICAL_RESULTS WRITE
command.
Order Sort_order Specifies whether the result set component is to
be listed in ascending or descending order.

Write_to_terminal On, Off Specifies if the information requested is to be
sent to the informational window or not. This
parameter is most likely to be used in
conjunction with the FILE_NAME parameter
to get the information put into a file.
Above_value Real The ABOVE_VALUE parameter is used as a
performed.
Below_value Real The BELOW_VALUE parameter is used as a
performed.
set:

 In a new results set, for example named REQ99 in the analysis run SHIFT, enter
numeric_results 97
File that result is

vx vy vz wx wy wz


2. The legal values for the “sort_by” parameter are BY_VALUE and BY_TIME. If BY_VALUE is
entered, then the values will be sorted by the magnitude of the result set component being written. If
BY_TIME is entered, then the values will be sorted by the simulation time associated with the result
set component being written.
This is an optional parameter and if not entered, the SORT_BY option will not be set to any value.
The result set component will be written in the order it appears in the result set.
3. If entered, the “order” parameter is used regardless of whether the values are to be printed to the
terminal or to a file.
This parameter is optional and if not entered, it will default to "ascending" order. The only legal
values for the ORDER parameter is "ascending" and "descending".
4. The “above_value” parameter determines the threshold above which a particular numeric value will
be modified, printed, etc. (depending on the operation to be performed).
5. The “Below_value” parameter determines the threshold below which a particular numeric value will
be modified, printed, etc. (depending on the operation to be performed).
optimize 1
optimize constraint evaluate
optimize
Allows you to evaluate a constraint given in an existing analysis.
You have two options for defining an optimization constraint:
1. Select a result set component and its output characteristic.
2. Specify a function which computes the objective.
The result set component/output characteristic method requires a name of the form "REQ1.R1" or
"PAR2_XFORM.THETA".
If you specify a function, use "FUNCTION CREATE FUNCTION_NAME=..." to create it. Make sure
that your function has exactly one argument named "analysis". You may or may not use this argument in the
function, but it must still be there. For example, FUN CRE FUN=objective_function ARG=analysis
TEXT="MAX(analysis.req1.r1.values)" or FUN CRE FUN=total_mass ARG=analysis TEXT="100 -
par1.mass + par2.mass"
Format:
constraint_name= existing opt_constraint
analysis_name= existing analysis
Description:

constraint_name Existing Opt_constraint Specifies the name for an optimization constraint
analysis_name Existing Analysis Specifies an existing analysis
type the name. You may also find it convenient to type the name even if the analysis is displayed.You
may have explicitly named the analysis when you created it by reading one or more Adams output
to be entered.
optimize design_of_experiments

associated with it.
The DESIGN_OF_EXPERIMENTS command allows you to perform a number of analyses on a parametric
model.
You specify which design variables are to be changed, and one or more objective functions that are to be
evaluated upon completion of each analysis.
The combinations of design variable values to be used by the DOEalgorithm are taken from a table, which
might look like this (for an experiment with three variables and four trials).
-1 -1 0
-1 +1 0
-1 0 +1
0 0 +1
The values in the table are used as indexes into the list of ALLOWED_VALUES, where 0 is meant to index
the central value (if there is one).
The tables used by Adams View in its DOE algorithm can come from one of three places:
1. An already existing disk file (possibly generated by another program).
2. They can be entered on the command line by you.
3. They can be automatically generated by Adams View.
There are three mutually exclusive groups of parameters providing different means for performing the
analysis on your model. The first two use Adams Solver with either simple values (END_TIME,
NUMBER_OF_STEPS, and so on) or the Adams command file (ACF) interface.
The third group (labelled INDEPENDENT_OF_RESULTS) allows you to perform a DOE without
invoking Adams Solver (set the DO_NOT_RUN_SOLVER parameter to TRUE). This is appropriate for
models where the objective is not dependent on any analysis results.
For example, you might define a model in which the objective is dependent upon the mass of a part. If the
mass of the part is determined by the geometry of the system, then you do not need to run Adams Solver. If
you can use this type of analysis, do so, as it reduces the amount of time required for analysis by orders of
magnitude.
Format:
model_name= existing mode
analysis_name= existing analysis
user_executable= string
optimize 3
brief= on/off
on_objective_error= stop/continue
analysis_type= analysis_type
number_of_steps= integer
end_time= real
initial_static= yes/no
adams_command_file= string
do_not_run_solver= true
objective_name= existing objective
design_variables= existing design variable
technique= doe_technique
number_of_user_trials= integer
user_matrix= integer
matrix_file_name= string
Description:

model_name Existing Model Specifies an existing model
analysis_name Existing Analysis Specifies an existing analysis
user_executable String Specifies the name of the user Adams executable to use for
this analysis. If no values are specified, the standard Adams
executable is run.
brief On, Off Specifies whether or not to display the brief form of the
information about the analysis being submitted. If set to
Off, the entire output from the Adams run will be
displayed in the info_window. If set to On, only errors and
warnings will be displayed.
on_objective_error Stop, Continue Indicates how Adams View should handle an
invalid/nonexistent objective
analysis_type Dynamics, Specifies which type of analysis you want Adams to
Kinematics, Statics, perform.
Transient
number_of_steps Integer The number of values to be stored in each component of a
result set being read from a file.

end_time Real Specifies the end time for a dynamic, kinematic, or quasi-
static equilibrium analysis.
initial_static Yes, No Specifies whether or not Adams is to execute a static
solution prior to the main simulation.
adams_command_file String Specifies the contents of the Adams command file to use to
control the execution of the Adams simulation.
do_not_run_solver True When you set DO_NOT_RUN_SOLVER to TRUE (its
only possible value), you are indicating that the DOE or
optimization is to take place without using Adams Solver.
This is only possible when you have a model whose design
functions (objectives or constraints) are not dependent
upon analysis results in any way.
objective_name Existing Objective Specifies the names of the objectives that are to be
evaluated at every run during the Design of Experiments
analysis.
design_variables Existing Design The DESIGN_VARIABLES parameter allows you to
Variable specify which Adams View variables are to be modified for
the DOE runs. Each variable must have its
ALLOWED_VALUES specified for the DOE algorithms
to operate.
technique Doe Technique When you perform a Design of Experiments analysis, you
may select a built-in technique for creating the trial matrix.
number_of_user_trials Integer Use the NUMBER_OF_USER_TRIALS parameter with
the USER_MATRIX parameter to indicate how many user
trials are being entered.
user_matrix Integer The USER_MATRIX parameter specifies indexes to the
levels for each variable.
matrix_file_name String Specifies the file in which the DOE trials are described
You must separate multiple model names by commas. If the model is visible in one of your views, you
may identify it by picking on any of the graphics associated with it.
optimize 5
to be entered.
associated with it.
3. If on_objective_error is "stop", the simulations will stop if Adams View detects an
invalid/nonexistent objective during the simulations. If on_objective error is "continue", the
simulations will continue if Adams View detects an invalid/nonexistent objective.
On_objective_error defaults to "stop".
4. There are 4 different analysis types:
 DYNAMIC: Specifies that Adams is to integrate the dynamics equations.
If you request a dynamic analysis for a model with zero degrees-of-freedom, Adams issues a warning
message and integrates the equations instead of using kinematic analysis. Kinematic analysis is faster.
 KINEMATICS: Specifies that Adams is to run a kinematic analysis. If you request a kinematic
analysis for a model with one or more degrees-of-freedom, Adams issues an error message and
ignores the entire command.
 STATICS: Specifies that Adams is to run either a static equilibrium analysis or a quasi-static
equilibrium analysis. If you choose STATICS and fail to specify an END_TIME, or
NUMBER_OF_STEPS, Adams performs a static equilibrium analysis at the current time. If you
choose STATICS and specify an end time and one or more steps, Adams performs a quasi- static
equilibrium analysis.
 TRANSIENT: Specifies that Adams is to run a kinematic analysis if the model has zero degrees of
freedom, or a dynamic analysis if the system has one or more degrees-of-freedom.
You may use the 'MODEL VERIFY' command to display the number of degrees-of-freedom in your
model.-
5. All components being read from a file must have the same number of steps. Lines that do not begin
with a number are considered comments and ignored.
If this parameter is not specified, the size of the components will be inferred from the format of the
file. A component will be read from a file until a comment line is encountered. This comment line
marks the end of the component.
6. END_TIME must be greater than the begin time.
Since the begin time must be greater than zero, this means that the end time must also be greater that
zero.
7. If you select YES for the initial_static parameter, Adams will run a static analysis before starting the
simulation you have specified with the ANALYSIS_TYPE, NUMBER_OF_STEPS, and
END_TIME parameters.
You may wish to set this parameter to YES when running a vehicle model, for instance, to allow the
vehicle to settle on its suspension before starting a transient analysis.
8. Adams View allows you to create your own Adams Command File by using the text edit window.
You can control the Adams simulation parameters and commands by putting all commands in the
command file just as you would enter them during an interactive Adams analysis session. When
Adams View submits the Adams analysis run, the command file "View_Ana.acf" will be created, and
Adams will use this command file to control the simulation.
See the Adams documentation for a complete description of the Adams Command File.
To invoke the text edit window for modification of the ACF file, just pick the "EDIT" button on the
SUBMIT command panel while the ADAMS_COMMAND_FILE parameter field in active.
Below, is a description of the text editor.
The Text Edit Window provides a flexible means of entering large amounts of text into a panel field.
 Invoking the text edit window:
The Text Edit Window is displayed by either typing control-t or picking the EDIT button on a
panel.
When the text edit window is displayed, the contents of the current active field are placed into it. If
the contents of the current active field consist of multiple quoted strings, then each string will be
placed on a separate line in the text edit window.
 Cursor placement: Point and click. You can place the text cursor anywhere within the text by placing
the mouse cursor at the desired location and clicking. Arrow keys can be used to move the cursor
left, right, up and down within the text in the window. The up and down arrow keys will also scroll
the window if there are more than 8 lines of text. Carriage-return advances to the next line.
 Buttons:
 OK - The OK button is used when you are satisfied with the text in the window and that you wish
it to be placed into the panel from which it originated. A verification will be performed, and if there
are no problems, the contents of the text edit window will be placed into the originating field. If the
verification failed, the cursor will be placed at or near the location where the parser detected a
problem.
 CANCEL - The CANCEL button is used to terminate the current use of the text edit window, and
to return to the originating panel without changing the contents of the current active panel field.
 VERIFY - The VERIFY button is used to perform a verification on the current contents of the text
edit window. It checks for the proper syntax required by the active field on the originating panel. A
message will be output indicating success or failure. In the case of a failure, the text cursor will be
placed at or near the location where the parser detected a problem.
optimize 7
 GET_NAME - The GET_NAME button is used to place the name of a marker into the text in the
window at the current text cursor location. After the MARKER button has been picked, you may
then pick a marker and its name will be inserted at the current text cursor location.
 FUNCTIONS - The FUNCTIONS button provides a means of constructing an Adams function
string. Upon picking the FUNCTIONS button, you will be presented with the list of available
functions in the "selection window". After you select the desired function, a panel will appear with
fields representing the various parameters for the function. You will have full access to on-line help
with this panel just like you have with regular panels. After you have completed the panel and
selected the DONE button on the panel, the function string will be constructed and inserted at the
current text cursor location in the text edit window.
 INSERT/OVERSTRIKE - The INSERT/OVERSTRIKE button toggles between insert mode and
overstrike mode. In insert mode, as characters are typed, any characters to the right of the insertion
point on the current line are shifted further to the right. In overstrike mode, as characters are typed,
they will replace any characters to their right that they may encounter.
 CUT - The CUT button will cut out the line that currently contains the text cursor. The line is
remembered until a subsequent CUT is performed. The information in the CUT buffer is
accessible for PASTE operations for the duration of the Adams VIEW session.
 PASTE - The PASTE button will insert the text that was last CUT. The insertion will be
performed at the current text cursor location.
 Control characters: control-i set for insert mode, control-o set for overstrike mode, control-d
equivalent to OK button, control-q equivalent to CANCEL button, control-x equivalent to CUT
button, control-v equivalent to PASTE button
9. One simple means for generating the trial matrix is by using the the case number as an index into the
allowed values of the design variables. This is called the CASEWISE technique. You end up with N
trials, where N is the number of levels for the design variables.
The FULL_FACTORIAL technique is a simple "brute force" algorithm that generates all possible
permutations (there are N**M of them, where N is the number of levels for the design variables and
M is the number of design variables; all design variables must have the same number of levels). This
can quickly get out of hand, so it is often the case that you will choose a "reduced factorial" trial
matrix.
CENTRAL_COMPOSITE is a reduced factorial algorithm that selects design points on the axis and
adds the "star points", i.e. the corners of the design space.
BOX_BEHNKEN is a reduced factorial algorithm that selects the points on the planes of the design
space.
USER1, USER2 and USER3 are used to invoke user-written code for generating tables.
A comparison of how many runs are required for a given algorithm is shown in the following table.
nDV nLv FF BB CC
--- --- -- -- --
2 3 9 5 9
2 5 25 9 17
2 7 49 13 25
3 3 27 13 15
3 5 125 49 29
optimize fit_response_surface
3 7 343 109 43
4 3 81 33 25
4 5 625 257 49
4 7 2401 865 73
5 3 243 81 43
5 5 3125 1281 85
5 7 16807 6481 127
6 3 729 193 77
6 5 15625 6145 153
6 7 117649 46657 229
7 3 2187 449 143
7 5 78125 28673 285
7 7 823543 326593 427
where:
nDV = number of design variables

NLv = number of levels on each design variable
FF = number of trials for a Full Factorial experiment
BB = number of trials for a Box-Behnken experiment
CC = number of trials for a Central Composite experiment
10. The indexes specified in the user_matrix parameter should be centered. This means that for a two-
level variable, the only possible values are -1 and +1; for three-levels, -1, 0 and +1; for four-levels, -2,
-1, +1, +2; and so on.
11. The following is an example which could be used for an experiment with two variables with three
levels each. There would be four trials in the experiment.
NUMBER_OF_USER_TRIALS=4 USER_MATRIX=0,+1, -1, 0, +1,-1, +1,+1
12. The first line of the file contains three numbers. The first is the number of variables for this DOE.
The second number is the number of levels for each variable. The third number is the number of trials
to be found on the subsequent lines of the file.
Each line that follows contains indexes to the levels for each variable. These indexes should be
centered. This means that for a two-level variable, the only possible values are -1 and +1; for three-
levels, -1, 0 and +1; for four-levels, -2, -1, +1, +2; and so on.
The following is an example of a file which could be used for an experiment with two variables with
three levels each. There would be four trials in the experiment.
2 3 4
0 +1
-1 0
+1 -1
+1 +1
The FIT_RESPONSE_SURFACE command fits a surface of arbitrary polynomial degree to a given set of
result set components. Usually, the dependent data is the response component produced by a DOE, and the
independent data values are the design variable values used to compute the response.
optimize 9
The polynomial data can be stored in a new result set, and also written to a file (say, for use by a spreadsheet
program).
Format:
result_set_name= result_set name
dependent_variable= existing component
independent_variables= existing component
polynomial_degrees= integer
file_name= string
Description:

result_set_name Result Set Name This parameter allows you to identify a result set name
dependent_variable Existing Component The DEPENDENT_VARIABLE specifies the result set
which is the left-hand side of the fit equation.
DEPENDENT_VARIABLE =
F(INDEPENDENT_VARIABLES)
Usually, this result set is the response values of an

experiment.
independent_variables Existing Component The INDEPENDENT_VARIABLES specify the result
sets which are the right-hand side of the fit equation.
DEPENDENT_VARIABLE =
F(INDEPENDENT_VARIABLES) Usually, these
result sets were the experimental values of the design
variables in an experiment.
polynomial_degrees Integer The POLYNOMIAL_DEGREES parameter specifies
the highest degree for each of the indpendent variables.
file_name String Specifies the name of the file that is to be read, written,
or executed.
components. A component is most usually setup to contain vector components of values like
displacement, velocity, acceleration, force, etc. However, in this case a result set is completely general
and can store any numeric value in a component with only few exceptions. These exceptions are those
cases when the user asks the system to mix incompatible value types like complex in the same
This is a required parameter and the result set name given must be within a particular analysis. A
result set name may be arbitrarily long and a combination of letters of the alphabet and numbers may
The following table illustrates the default names assigned to result sets and result set components read
Result set type Result set name Component Name File that result is from
Part AR xxx x y z e le2e3 e4mag vx vy vz Result file
wx wy wz acc
diff diffxxx q dq results file
joint JOIxxx fx fy fz tx ty tzfmag tmag results file
jprim JPRxxx.. fx fy fz tx ty tz fmag tmag results file
gear GEAxxx.. fx fy fz results file
fmag1 tmag1
spring damp SPRxxx.. fx fy fz tx ty tz fmag tmag results file
Bushing BUSxxx... fx fy fz tx ty tz fmag tmag results file
Beam BEAxxx... fx fy fz tx ty tz fmag tmag results file
Field FIExxx... fx fy fz tx ty tz fmag tmag results file
User Request UREQxxx... x y z r1 r2 r3 mag amag Request file
Ucon Not implemented+
request REQxxx...
optimize 11
2. For example, if you have specified two independent variables, you would enter
POLYNOMIAL_DEGREES=1,1 for a linear approximation. For a polynomial fit which is cubic in
the first variable and linear in the second, you would enter POLYNOMIAL_DEGREES=3,1.
3. The proper extension for the file_name parameter is the default but can be overridden by simply
output_control
output_control attributes femdata
Allows you to change the color and visibility of a femdata icon.
Format:
femdata_name= .model.femdata_name
visibility = on/off
color = color_string
active= on/off
dependents_active = on/off
Example:
output_control attributes femdata &
mrequest_name = .test.link_forces &
visibility = on &
color = PINK &
active = on &
Description:

femdata_name String Specifies the femdata to be modified. You use this parameter
to identify the existing femdata to be affected with this
command.
visibility String Specifies the visibility of graphic entities. The visibility
parameter is used to control whether graphic entities, such
as markers, joints, and parts, are to be drawn in an Adams
View viewport.

color String Specifies the color the modeling entity should be drawn in.
active On/Off/No_opi When you set ACTIVE=NO, that element is written to the
nion data set as a comment.
dependents_active On/Off/No_opi The DEPENDENTS_ACTIVE parameter acts in the same
nion fashion as that of the ‘active’ parameter, but sets the
ACTIVE attribute for the dependents all the way down the
dependency chain.
1. You identify a femdata by typing its name. If you created the femdata by reading an Adams data set,
the femdata name is the letters FEM followed by the Adams data set femdata ID number. For
example, the name of Adams FEM/101 is FEM101. If you created the femdata during preprocessing,
If a femdata is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a femdata under a different model, for instance, you may need to enter
the model name as well. For example, you may specify femdata 'link_forces' from model 'test' by
entering ".test.link_forces". You must separate multiple femdata names by commas.
3. Specifies the color the modeling entity should be drawn in. Adams View allows you to specify the
following colors for modeling entities: BLACK, WHITE, RED, GREEN, BLUE, CYAN,
MAGENTA, YELLOW, and NO_COLOR. Specifying 'NO_COLOR' for a modeling entity,
modeling entity.
Example 1
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3
.model -------------------------NO_COLOR
output_control 3
output_control attributes mrequest
.part---------------------- NO_COLOR
5. The DEPENDENTS_ACTIVE parameter acts in the same fashion, but sets the ACTIVE attribute
command:
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
Tips:
1. If you type a "?", Adams View will list the mrequests available by default.

Allows you to change the color and visibility of an mrequest icon.
Format:
mrequest_name= .model.mrequest_name
visibility= on/off
color= color_string

active = on/off
Example:
output_control attributes mrequest &
mrequest_name= .model.m01 &
visibility = on &
color = PINK &
active = on &
Description:

mrequest_name String Specifies the mrequest to be modified. You use this
parameter to identify the existing mrequest to be affected
with this command.
parameter is used to control whether graphic entities,
such as markers, joints, and parts, are to be drawn in an
Adams View viewport.
color String Specifies the color the modeling entity should be drawn
in.
active On/Off/No_opini When you set ACTIVE=NO, that element is written to
on the data set as a comment.
dependents_active On/Off/No_opini The DEPENDENTS_ACTIVE parameter acts in the
on same fashion as that of the ‘active’ parameter, but sets the
ACTIVE attribute for the dependents, all the way down
the dependency chain.
1. You may identify an mrequest by typing its name. If you created the mrequest by reading an Adams
data set or graphics file, the mrequest name is the letters MRE followed by the Adams data set
mrequest ID number. For example, the name of Adams MREQ/101 is MRE101F. If you created the
mrequest during preprocessing, you will have given it a name at that time. If a mrequest is available
output_control 5
by default, you may identify it by entering only its name. If it is not, you must enter its full name. To
identify an mrequest under another analysis, for instance, you may need to enter the analysis name as
well. For example, you may specify mrequest 101 from the analysis named test by entering
".test.mre101".
modeling entity.
Example 1
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3
.model -------------------------NO_COLOR
.part---------------------- NO_COLOR
command:
output_control attributes request

• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
Tips:

Allows you to change the color and visibility of a request icon.
Format:
request_name = .model.request_name
visibility = on/off
color = color_string
active = on/off
Example:
output_control attributes request &
request_name = .model.m01 &
visibility = on &
color = PINK &
active = on &
output_control 7
Description:

request_name String Specifies the request to be modified. You use this
parameter to identify the existing request to be affected
with this command.
parameter is used to control whether graphic entities, such
as markers, joints, and parts, are to be drawn in an Adams
View viewport.
color String Specifies the color the modeling entity should be drawn
in.
active On/Off/No_opinio When you set ACTIVE=NO, that element is written to
n the data set as a comment.
dependents_active On/Off/No_opinio The DEPENDENTS_ACTIVE parameter acts in the
n same fashion as that of the ‘active’ parameter, but sets the
ACTIVE attribute for the dependents all the way down
the dependency chain.
1. You may identify a request by typing its name. If you created the request by reading an Adams data
set or graphics file, the request name is the letters MRE followed by the Adams data set request ID
number. For example, the name of Adams MREQ/101 is MRE101. If you created the request during
preprocessing, you will have given it a name at that time. If a request is available by default, you may
identify it by entering only its name. If it is not, you must enter its full name. To identify a request
under another analysis, for instance, you may need to enter the analysis name as well. For example,
you may specify request 101 from the analysis named test by entering ".test.req101".
TOGGLE will take the current state of an entity’s visibility and reverse it.
modeling entity.
Example 1
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 2
output_control copy femdata
.model -------------------------NO_COLOR
.part ---------------------- RED
Example 3
.model -------------------------NO_COLOR
.part---------------------- NO_COLOR
command:
• Group
• Part
• Marker
• Geometry
• Constraints
• Forces
• Data Elements
• Output Control
Tips:
1. If you type a "?", Adams View will list the requests available by default.

Allows you to create a replica of an existing femdata object. This replica will be an exact copy of the original,
except for the name.
output_control 9
Format:
femdata_name = model_name.femdata_name
new_femdata_name = model.new_femdata_name
Example:
output_control copy femdata &
femdata_name = model_name.femdata1 &
new_femdata_name = model.femdata2
Description:

femdata_name String Specifies an existing femdata. You identify a femdata by typing
its name.
new_femdata_name String Specifies the name of the new femdata. You may use this name
later to refer to this femdata.
1. FEMDATA is used to produce a special data file containing all reaction forces and all applied forces
(except gravity) acting on each part. So that inertia forces can be calculated, this file also contains the
displacement, velocity, and acceleration of each part center of mass. You or your systems support
personnel can write a small program to convert this file into boundary condition input for a
commercial finite element program.
2. If you created the femdata by reading an Adams data set, the femdata name is the letters FEM
followed by the Adams data set femdata ID number. For example, the name of Adams FEM/101 is
FEM101. If you created the femdata during preprocessing, you will have given it a name at that time.
If a femdata is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a femdata under a different model, for instance, you may need to enter
the model name as well. For example, you may specify femdata 'link_forces' from model 'test' by
entering ".test.link_forces". You must separate multiple femdata names by commas.
output_control copy mrequest
be assigned to it.
Cautions:
1. Adams View will not allow you to have two femdatas with the same name, so you must provide a
unique name for the new_femdata_name parameter
Tips:
1. If you type a "?", Adams View will list the femdatas available by default.

Allows you to create a replica mrequest for a model. This mrequest is will be an exact copy of the original
except the name. You may modify the replica without any harm done to the original.
Format:
mrequest_name = string
new_mrequest_name = string
Example:
output_control copy mrequest &
mrequest_name = mrequest1 &
new_mrequest_name = mrequest2
Description:

mrequest_name String Specifies an existing mrequest. You may identify an
mrequest by typing its name.
new_mrequest_name String Specifies the name of the new mrequest. You may use this
name later to refer to this mrequest. Adams View will not
allow you to have two mrequests with the same name, so
output_control 11
1. The MREQUEST indicates multiple sets of data you want Adams to output. You can request sets of
displacements, velocities, accelerations, or forces for system elements such as parts, joints, joint
primitives, or applied forces in your system.
Except for rotational displacements, all the information types are vectors. For example, joint velocities
are actually translational and rotational velocity difference vectors of the joint I marker with respect
to the joint J marker. Joint accelerations are actually translational and rotational acceleration
difference vectors of the joint I marker with respect to the joint J marker. In other words, if V is a
translational vector quantity and W is a rotational vector quantity,
Vij = Vi - Vj,
and Wij = Wi - Wj
V'ij = V'i - V'j
and W'ij = W'i - W'j
Because two markers (I and J) define each joint, joint primitive, and applied force, Adams measures
the request information for one of of these at the I marker with respect to the J marker. Because a
center-of-mass marker is the only marker that is necessary to define a part, Adams measures the
request information for a part at its center-of-mass marker with respect to ground or with respect to
an alternative marker you specify. Regardless of the system information you want, you can use a
reference marker (R_MARKER_NAME) to resolve the component information into any coordinate
system you wish. Note that the units for rotational displacement data in the request output of the
tabular output file default to degrees. The units for all other angular output data default to radians.
2. You may identify a mrequest by typing its name. If you created the mrequest by reading an Adams
data set or graphics file, the mrequest name is the letters MRE followed by the Adams data set
mrequest ID number. For example, the name of Adams MREQ/101 is MRE101. If you created the
mrequest during preprocessing, you will have given it a name at that time. If an mrequest is available
by default, you may identify it by entering only its name. If it is not, you must enter its full name. To
identify a mrequest under another analysis, for instance, you may need to enter the analysis name as
well. For example, you may specify mrequest 101 from the analysis named test by entering
".test.mre101". You must separate multiple mrequest names by commas.
then you may override the default parent. In most cases, when creating an entity, Adams View will
it has assumed. You may, of course, delete this name and use your own. The form of a full name is:
be assigned to it.
output_control copy request
Cautions:
1. Adams View will not allow you to have two mrequests with the same name, so you must provide a
unique name for the new request to be created.
Tips:

Allows you to create a replica request. This replica request will be an exact copy of the original with the
exception of the name.
Format:
request_name = string
new_request_name = string
Example:
output_control copy mrequest &
mrequest_name = mrequest1 &
new_mrequest_name = mrequest2
Description:

request_name String Specifies an existing request. You may identify an mrequest by
typing its name.
new_request_name String Specifies the name of the new request. You may use this name
later to refer to this mrequest. Adams View will not allow you
to have two mrequests with the same name, so you must
1. A REQUEST indicates a set of data you want Adams to output. Using a REQUEST, you can output
a set of displacements, velocities, forces, or accelerations, with respect to markers in your system; or
you can use the user-written subroutine REQSUB to define nonstandard output. Adams calculates
all data in the ground reference frame, although you can specify that the data be resolved in another
reference frame. This is of no importance in the case of force data, but it can be very important in the
case of displacements and time derivatives, that is, velocities and accelerations. Except for rotational
displacements, all the information types are vectors. For example, joint velocities are actually
output_control 13
translational and rotational velocity difference vectors of the joint I marker with respect to the joint J
marker. Joint accelerations are actually translational and rotational acceleration difference vectors of
the joint I marker with respect to the joint J marker. In other words, if V is a translational vector
quantity and W is an rotational vector quantity,
Vij = Vi - Vj,
and Wij = Wi - Wj
V'ij = V'i - V'j
and W'ij = W'i - W'j
Note that the units for rotational displacement data in the request output of the tabular output file
default to degrees. The units for all other angular output data default to radians.
2. If you created the request by reading an Adams data set or graphics file, the request name is the letters
MRE followed by the Adams data set request ID number. For example, the name of Adams
MREQ/101 is MRE101. If you created the request during preprocessing, you will have given it a
name at that time. If a request is available by default, you may identify it by entering only its name.
If it is not, you must enter its full name. To identify a request under another analysis, for instance,
you may need to enter the analysis name as well. For example, you may specify request 101 from the
analysis named test by entering "/test/req101". You must separate multiple request names by
commas.
then you may override the default parent. In most cases, when creating an entity, Adams View will
be assigned to it
Cautions:
1. Adams View will not allow you to have two requests with the same name, so you must provide a
unique name for the new request to be created.
Tips:
1. If you type a "?", Adams View will list the requests available by default.
output_control create femdata

Produces data files of component loads, deformations, stresses, or strains for input to subsequent finite
element or fatigue life analysis for use in third party products. Adams View will not output to any files unless
you specify the format.
Format:
femdata_name = .model_name.femdata_name
adams_id = geom._id
output_type = loads/loads_on_flex/,odal_deformation/stress/strain
r_marker_name = .marker_name
no_inertia = yes/no
peak_slice= fx/fy/fz/fmag/gmag/tx/ty/tz/tmag/none/all
flex_body= .model_name.flexible_body_name
datum = integer_number
nodes = integer_number
hotspots = integer_number
radius = real _number
criterion = von_mises/max_principle/min_principle/max_shear/normal_x/normal_y/no
rmal_z/shear_xy/shear_yz,shear_xz
start = real_number
end = real_number
skip = integer_number
Example:
Output_control create femdata &
femdata_name = fem_data_1 &
adams_id = 100 &
output_type = stress &
r_marker_name = .marker_name &
flex_body = 101 &
hotspots = 7 &
radius = 0.5 &
output_control 15
Output_control create femdata &

criterion = max_principle &
file_name = hotspots_101
These statements create a text file named hotspots_101.tab containing hot spot information for the flexible
body 101. Seven hot spots with a radius of 0.5 based on maximum principal stress are requested. The names
of the DAC files are given the prefix “hotspots_101” as specified in the file_name format.
Description:

femdata_name String Specifies the name of the FEMDATA element in the modeling database to be
created.
adams_id Integer Specifies an integer used to identify this element in the Adams data file.
output_type loads/loads_on_fl Specifies the information you want as output:

ex/modal_defor
mation/stress/stra  Loads on rigid body/Flex body- Output all external forces (reaction
in and applied forces except gravity) acting on the specified body and,
optionally, inertial forces of the specified body (angular velocity and
acceleration, including effects of gravity) as a function of time. Load
data will be output in the simulation set of units.
 Modal Deformation - Outputs modal deformations as a function of
time of the specified flexible body. Adams View will only export
coordinates of the active modes in the simulation.
 Nodal Deformation - Outputs nodal deformations as a function of
time of the specified flexible. Adams View writes the deformations in
the simulation set of units.
 Strain - Outputs strain information if strain modes are available in the
modal neutral file (MNF) of the specified flexible body and an Adams
Durability license is available. Adams Durability outputs all six
components of strain (normal-X, normal-Y, normal-Z, shear-XY,
shear-YZ, shear-ZX). It outputs strains in the basic FEA coordinate
system of the flexible body except where specified below.
 Stress - Outputs stress information if modal stresses are available in
the MNF of the flexible body and an Adams Durability license is
available. Adams Durability outputs all six components of stress
(normal-X, normal-Y, normal-Z, shear-XY, shear-YZ, shear-ZX). It
outputs stresses in the simulation set of units in the basic FEA
coordinate system of the flexible body except where specified below.
r_marker_name String Specifies the rigid body marker to be the reference coordinate system to output
loads. Because Adams Solver resolves all loads acting on the rigid body in the
coordinate system of the specified marker, the marker should represent the
FEA basic coordinate system of the part's finite element (FE) model.
output_control 17

no_inertia yes/no Specifies ‘yes’ for Adams View to include inertial loads (linear acceleration,
angular acceleration, and velocity) when outputting the loads acting on the
body. Otherwise, Adams View outputs no inertial loads and you will need to
rely on an inertia relief capability in the finite element program to balance the
external loads with the internal loads.
peak_slice fx/fy/fz/fmag/gm Specifies that FE model load data are to be output only at those time steps
ag/tx/ty/tz/tmag/ where the specified peak load occurred in the simulation. When you set the
none/all Time options, Adams View only checks the time steps within those
specifications for the peak load.
flex_body String Enters the flexible body whose data Adams View outputs. Adams View outputs
the data in the FE model basic coordinate system that is inherent to the flexible
body.
datum Integer Enters the node ID of the flexible body to be the datum of the nodal
displacements.
nodes Integer Enters the node numbers of a flexible body whose data is to be output.
hotspots Integer Enters the number of hot spots to locate and output. With this option, a text
file containing a tab-delimited table of hot spot information, such as node ID,
maximum value, time when the maximum value occurred, and location, is
generated.
radius Real Enter a radius that defines the spherical extent of each hotspot. A default value
of 0.0 (zero) means that all nodes in the flexible body will be hotspot
candidates.
von_mises/max_ Specifies the value of stress/strain in determining hotspots from one of Von
criterion principle/min_pr Mises, Max Prin., Min Prin., Max Shear, Normal-X, Normal-Y, Normal-Z,
inciple/max_shea Shear-XY, Shear-YZ, or Shear-ZX.
r/normal_x/norm
al_y/normal_z/sh
ear_xy/shear_yz,s
hear_xz
file_name String Enters the output file name for the FE model data. You can specify an existing
directory, root name, and/or extension. By default, the file name will be
composed of the Adams run and body IDs according to the type of data and
file format that you specified in Solver -> Settings -> Output -> More ->
Durability Files
start Real Specifies the time at which to start outputting the data. The default is the start
of the simulation.
end Real Specifies the time at which to end the output of the data or the search of a peak
load. The default is to output to the end of the simulation.
skip Integer
1. If you do not specify a node list, Adams View exports nodal data at each attachment point of the
flexible body. Adams Solver issues a warning if a node ID is specified that does not belong to the
flexible body.
2. Adams Solver computes all nodal displacements relative to the datum node ID. If you do not specify
a datum node, Adams Solver generates an arbitrary relative set of nodal displacements. It displays a
warning message if the specified node does not belong to the flexible body.
3. You can use the FILE_NAME argument to specify the directory, name, and/or extension
(directory/name.extension) for the output file. If you do not specify a directory, FEMDATA creates
all its output files except DAC files in the current working directory. Because several DAC files are
typically generated for a FEMDATA statement, FEMDATA creates them in a separate directory
named after the body. It creates this directory in the current working directory if it does not exist.
If a file name is not specified in the FILE argument, default file names are assigned according to the
type of FEM data and file format (which is specified in the OUTPUT statement) as shown in the
table below.
FEMDATA Default File Names and Extensions
Type of data Format* File name Extension

(none) (none) <run_name> .fem
Loads DAC <run_name>_<channel_id> .dac
NASTRAN <run_name>_<body_name> .dat
ABAQUS <run_name>_<body_name> .dat
ANSYS <run_name>_<body_name> .dat
RPC <run_name> .rsp
Modal DAC <run_name>_<channel_id> .dac
Deformation Generic <run_name>_<body_name .mdf
NASTRAN <run_name>_<body_name> .mdf
PUNCH <run_name>_<body_name> .mdf
ANSYS <run_name> .out
RPC <run_name> .rsp
Nodal Generic <run_name>_<body_name> .ndf
Deformation NASTRAN <run_name>_<body_name> .spc
ANSYS <run_name>_<body_name> .inp
Strain DAC <run_name>_<node_id>e_<channel_id> .dac
Generic <run_name>_<body_name> .nsf
Hotspots <run_name>_body_name>_hots .tab
Stress DAC <run_name>_<node_id>se_<channel_id> .dac
Hotspots <run_name>_<body_name>_hote .tab
output_control 19
*Specified in the OUTPUT statement

4. Peak Loads
Except for FMAG, GMAG, and TMAG, each PEAK_SLICE load specification (FX, FY, FZ, TX, TY,
TZ) generates two output time steps for each marker force of the component, one for the maximum
(peak) and one for the minimum (valley). For FMAG and TMAG, only one time step is output for
each marker force since these quantities are load magnitudes and generate only positive values. With
GMAG, only one time step is output per body. If:
• Fm(t) represents the force acting on the body at Marker m.
• rˆx, rˆy, rˆz represents the unit vector of the reference coordinate system of the rigid body (FEA
coordinate system of the flexible body).
• r(t) represents the position of the reference marker (RM) in that coordinate system.
ˆ ˆ ˆ
• || || represents taking the magnitude or length of a vector (that is, || ( r x, r y, r z ) || = 1)
Then the following conditions apply:
• FX = Output loads at time t when F m ( t ) ⋅ rˆx ( t ) is a maximum and minimum for each marker
m.
• FY = Output loads at time t when F m ( t ) ⋅ rˆy ( t ) is a maximum and minimum for each marker
m.
• FZ = Output loads at time t when F m ( t ) ⋅ rˆz ( t ) is a maximum and minimum for each marker
m.
• FMAG = Output loads at time t when F m ( t ) ⋅ r̂ ( t ) is a maximum for each marker m.
• GMAG = Output loads at time t when
 
MAX   F m ( t ) ⋅ r x ( t ),  F m ( t ) ⋅ r y ( t ),  F m ( t ) ⋅ r z ( t )
m m m

Note: Similar expressions exist for TX, TY, TZ, and TMAG. The PEAK_SLICE argument is
not available when you specify a time history OUTPUT load format (DAC or RPC).
Caution:
1. Using FEMDATA to output loads encounters the same limitations as exporting FEA Loads in Adams
View.
2. Note that all FEMDATA are output in the Adams modeling units. This causes a problem when the
Adams units are inconsistent with those used in the finite element model, and the data that is output
will be included in a subsequent finite element analysis.
For example, when outputting FEMDATA of type LOADS to ANSYS or MSC Nastran for inclusion
in the FE analysis, the Adams and FE modeling units must be consistent. This is also true when
outputting FEMDATA of type NODAL_DEFORMATION when the OUTPUT format is ANSYS
or MSC Nastran and the data will be used as input to the FE analysis.
output_control create mrequest
3. In the case of outputting FEMDATA of type MODAL_DEFORMATION, the only concern for
units is when MSC Nastran (or PUNCH) has been specified as the OUTPUT format. This is because
rigid body motion is included in the output file along with the modal coordinates. By definition,
modal coordinates are unitless, so the modal stresses (or strains) will be recovered correctly in MSC
Nastran irregardless of unit settings. However, for the overall displacement of the component to be
correctly recovered, the unit of length must be consistent between models.

Allows you to create mrequest files. The MREQUEST statement specifies multiple sets of data that you want
Adams Solver (FORTRAN) to write in the tabular output file and request file. You can request sets of
displacements, velocities, accelerations, or forces for system elements such as parts, joints, joint primitives, or
applied forces in the system.
Format:
mrequest_name = .model_name.mrequest_name
adams_id = geom_id
j_marker_name = marker_name
r_marker_name = marker_name
comment = string
output_type = displacement/velocity/acceleration/force
part_name = .model.part_name
joint_name = .model.joint_name
jprim_name = .model.primitive_joint_name
force_name = .model.existing_force_name
Example:
output_control create mrequest &
mrequest_name = mrequest__1 &
comment = 'sample output control creation' &
output_type= displacement
This MREQUEST statement requests displacement data for Part 2. For the part, Adams Solver
(FORTRAN) outputs eight headings and eight columns of data to the tabular output file. The same
information also goes to the request file. Because this statement does not supply arguments J and RM, Adams
Solver (FORTRAN) measures the displacements with respect to the ground coordinate system (GCS), and
resolves the displacements in the global coordinate system.
output_control 21
Description:

Mrequest_name String Specifies the name of the mrequest to be created. You use this
parameter to identify the existing mrequest to be affected with this
command.
Adams_id Integer Specifies an integer used to identify this element in the Adams data
file.
J_marker_name String Specifies a single base marker for measuring the displacements,
velocities, or accelerations of the center-of-mass of the parts. Adams
Solver (FORTRAN) makes all measurements for parts on the
center-of-mass marker on each part with respect to the J marker you
specify. The J marker defaults to the ground coordinate system
(GCS).
 id1 [ ,...,id
JOINTS = 
 ALL
Indicates that you want to output displacements, velocities,
accelerations, or forces for as many as thirty JOINT statements or
for all JOINT statements. Adams Solver (FORTRAN) makes these
measurements on the I marker with respect to the J marker.
 id1 [ ,...,id
JPRIMS = 
 ALL
accelerations, or forces for as many as thirty JPRIM statements or for
all JPRIM statements. Adams Solver (FORTRAN) makes these
measurements on the I marker with respect to the J marker.
 id1 [ ,...,id
PARTS = 
 ALL
Indicates that you want to output displacements, velocities, or
accelerations for as many as thirty center-of-mass of parts in the
model (to which the PART statement identifiers refer) or for the
centers of mass of all parts (except the ground part). Adams Solver
(FORTRAN) makes these measurements on the center-of-mass
marker of the part with respect to the marker specified by the J
argument. The PARTS argument cannot be used for massless parts.
The PARTS argument cannot be used with the FORCE argument.
R_marker_name String Identifies the reference marker with respect to which you want to
resolve information. RM defaults to zero, which causes Adams
Solver (FORTRAN) to resolve components in the ground
coordinate system (GCS).

Comment String Specifies a title for the top of each set of information the
MREQUEST statement outputs. The entire comment must be on
one line. Because the COMMENT argument can be only eighty
characters long at most, the title can be from seventy-two characters
long (if you do not abbreviate COMMENT=) to seventy-eight
characters long (if you abbreviate COMMENT= to C=). Blank
spaces and all alphanumeric characters can be used. However, the
comma (,), the semicolon (;), the ampersand (&), and the
exclamation point (!) cannot be used.
DISPLACEME See extended definition for details on each output_type
output_type NT/VELOCITY
/ACCELERATI
ON/FORCE
part_name String Specifies names of part with which you want to output
displacements,velocities, or accelerations.
joint_name String Specifies name of joint with which you want to output
jprim_name String Specifies name of joint primitive with which you want to output
force_name String Specifies name of force or a list of forces with which you want to
output displacements,velocities, or accelerations.
All Parts/joints/jpri Specifies that Adams is to output data for all parts, joints, joint
ms/forces primitives, or forces. Rather than entering each name individually,
you may use this parameter to request data for all entities of a
particular type.
1. The MREQUEST statement indicates multiple sets of data you want Adams Solver (FORTRAN) to
write in the tabular output file and request file. You can request sets of displacements, velocities,
accelerations, or forces for system elements such as parts, joints, joint primitives, or applied forces in
the system.
2. Acceleration -Generates acceleration requests that output the accelerations for the markers that define
part centers of mass, joints, joint primitives, or applied forces. This argument generates nine headings
and nine columns of output for each part, joint, joint primitive, or applied force. The columns in the
Tabular Output file include the time (TIME), the translational magnitude (ACCM), the x
component (ACCX), the y component (ACCY) the z component (ACCZ), the rotational magnitude
(WDTM), the rotational x component (WDTX), the rotational y component (WDTY), and the
rotational z component (WDTZ). The same data without the magnitude are written in the Request
file.
output_control 23
 id1 [ ,...,id30] 
APPFORS =  
 ALL 
Indicates that you want to output displacements, velocities, accelerations, or forces for as many as
thirty BEAM, BUSHING, FIELD, GFORCE, NFORCE, SFORCE, SPRINGDAMPER,
VFORCE, and VTORQUE statements or for all of these statements. For action-reaction forces,
Displacement- Generates displacement requests that output the displacements for the markers that
define part centers of mass, joints, joint primitives, or applied forces. This argument generates eight
headings and eight columns of output for each part, joint, joint primitive, or applied force. The
columns in the tabular output file include the time (TIME), the translational magnitude (MAG), the
x component (X), the y component (Y), the z component (Z), the psi angle (PSI), the theta angle
(THETA), and the phi angle (PHI). The same data without the magnitude are written in the Request
file. For joints, joint primitives, and applied forces, the psi, theta, and phi angles are the Euler angle
displacements of the I marker with respect to the J marker. For parts, the psi, theta, and phi angles
are the Euler rotations of the part center-of-mass marker with respect to the ground coordinate system
(GCS) or with respect to a J marker you specify.
Force -Generates force requests that output the forces for the markers that define joints, joint
primitives, or applied forces. This argument generates nine headings and nine columns of output for
each joint, joint primitive, or applied force. The columns in the Tabular Output file include the time
(TIME), the translational force magnitude (FM), the translational x component (FX), the
translational y component (FY), the translational z component (FZ), the rotational force magnitude
(TM), the rotational x component (TX), the rotational y component (TY), and the rotational z
component (TZ). The same data without the magnitudes are written to the Request file. The FORCE
argument cannot be used with the PARTS argument.
3. Adams Solver (FORTRAN) measures the force that the J marker applies on the I marker. For action-
only forces, Adams Solver (FORTRAN) measures the external forces acting on the I marker. If an
MREQUEST statement is issued with an APPFORS argument that requests information for an
identifier that is used for two or more applied force statements, Adams Solver (FORTRAN) outputs
information for the first applied force statement with that identifier. To avoid problems, you may
want to use a different identifier for each applied force statement in the dataset.
Adams Solver (FORTRAN) calculates all time derivatives in the ground coordinate system (GCS),
although you can specify that the data be resolved in another reference frame. This is of no
importance in the case of force data, but it can be very important in the case of velocities and
accelerations. For example, joint velocities are actually translational and rotational velocity difference
vectors of the joint I marker and the joint J marker in ground. Joint accelerations are actually
translational and rotational acceleration difference vectors of the joint I marker in ground and the
joint J marker in ground.
4. Because two markers (I and J) define each joint, joint primitive, and applied force, Adams Solver
(FORTRAN) measures the request information for one of these at the I marker with respect to the J
marker. Because a center-of-mass marker is the only marker that is necessary to define a part, Adams
Solver (FORTRAN) measures the request information for a part at its center-of-mass marker with
respect to ground or with respect to an alternative marker you specify. Regardless of the system
information you want, a reference marker (RM) can be used to resolve the component information
into any coordinate system you wish.
Cautions:
1. Note that the units for rotational displacement data in the request output of the tabular output file
2. For any argument =ALL, Adams Solver (FORTRAN) ignores any invalid selections.
3. Applied forces and torques are those generated by beams, bushings, fields, general forces
(GFORCEs), n-component forces (NFORCEs), single-component forces (SFORCEs),
springdampers (SPRINGDAMPERs), vector forces (VFORCEs), and vector torques (VTORQUEs).
Adams Solver (FORTRAN) outputs the applied forces and torques acting at the request I marker
(which may be either the applied force I marker or the applied force J marker).
The magnitude and point of force application on the part containing the applied force J marker varies
with the type and source of the force.
• For springdampers, action-reaction single-component forces, general forces, vector forces, and
vector torques, the forces and torques acting at the J marker are equal and opposite to the forces
and torques acting at the I marker.
• For action-only single-component forces, no force or torque acts at the applied force J marker.
• For beams, fields, bushings, and multi-point forces, the forces acting at the applied force J marker
are equal and opposite to the forces acting at the applied force I marker.
4. As long as the applied force I marker and the applied force J marker are coincident, the torques acting
at the applied force J marker are equal and opposite to the torques acting at the applied force I marker.
If there is a finite separation distance between the I and J markers, the torques acting at the applied
force J marker are not necessarily opposite or equal, to the torques acting at the applied force I marker.
5. Reaction forces and torques are those generated by constraint-inducing elements. For revolute,
spherical, and universal joints and for atpoint, orientation, parallel axes, and perpendicular joint
primitives, Adams Solver (FORTRAN) outputs the reaction forces and torques acting at the request
I marker (which may be either the constraint I marker or the constraint J marker). Depending on the
type of constraint, some or all of the torques acting at the I marker are zero. The force and torque
acting at the request J marker are equal and opposite to the force and torque acting at the request I
marker.
6. Determining reaction forces-and torques for cylindrical, planar, rack-and-pinion, screw, and
translational joints and for inline and inplane joint primitives is more complex. If the request I marker
corresponds to the constraint I marker, then Adams Solver (FORTRAN) outputs the force and
torque acting at the constraint I marker. If the request I marker corresponds to the constraint J
marker, then Adams Solver (FORTRAN) outputs the force and torque acting at the instantaneous
location of the constraint I marker, but on the part containing the constraint J marker. The force
output_control 25
output_control create request
translated to the constraint J marker is the same as computed above. If the I and J markers are
coincident, the torque translated to the constraint J marker is the same as computed above. But if
there is a finite separation between the I and J markers, the torque translated to the constraint J marker
is different from the one computed above (because of the moments contributed by the reaction
forces).
7. The MREQUEST statement is not scheduled to be supported in Adams Solver (C++). You are
encouraged to migrate away from this statement and use the REQUEST statement instead.

Allows you to create a replica request. This replica request will be an exact copy of the original with the
exception of the name.
A REQUEST indicates a set of data you want Adams to output. Using a REQUEST, you can output a set
of displacements, velocities, forces, or accelerations, with respect to markers in your system; or you can use
the user-written subroutine REQSUB to define nonstandard output.
Adams calculates all data in the ground reference frame, although you can specify that the data be resolved in
another reference frame. This is of no importance in the case of force data, but it can be very important in
the case of displacements and time derivatives, i.e. velocities and accelerations.
Except for rotational displacements, all the information types are vectors. For example, joint velocities are
actually translational and rotational velocity difference vectors of the joint I marker with respect to the joint
J marker. Joint accelerations are actually translational and rotational acceleration difference vectors of the
joint I marker with respect to the joint J marker. In other words, if V is a translational vector quantity and W
is a rotational vector quantity,
Vij = Vi – Vj,
And Wij = Wi – Wj,
V’ij = V’i- V’j
And W’ij = W’I – W’j
Note that the units for rotational displacement data in the request output of the tabular file default to degrees.
The units for all other angular output data defaults to radians.
Format:
output_control create &
request_name = .model_name.request_name&
adams_id= geom._id&
comment = string&
component_names = string&
component_units = string&
component_labels = string&
results_name = string&
title = string&
output_control create &

output_type = displacement/velocity/acceleration/force&
i_marker_name = marker_name&
j_marker_name = marker_name&
r_marker_name = marker_name&
user_function = real number&
f1 = run time function&
variable_name = variable name&
routine = string
Description:

Request_name String Specifies the name of the new request to be created. You may
later identify a request by typing its name.
Adams data file.
Output_type Displacement/velo Specifies whether you want the request to output
city/acceleration/fo displacement, velocity, acceleration, force, or user data.
rce/user
I_marker_name An existing triad Specifies the marker for which you wish Adams to generate
data.
J_marker_name An existing triad Specifies the marker with respect to which you wish Adams
to generate the data.
output_control 27

R_marker_name An existing triad Specifies the marker with respect to which you want Adams
to resolve the data. Adams computes the data identified by
the I and J markers, then reports the data as x, y, and z
components in the reference frame of the reference marker.
Angular displacements, which are not vectors, are not
affected by reference marker. If you do not supply this
parameter, Adams will resolve the data in the ground
reference frame.
Comment String Specifies a comment for the request. The comment can
contain up to 80 characters, and can be comprised of letters
of the alphabet (a-z, A-Z), numbers (0-9), and underscores.
You may also use spaces and special characters (*&^%$#) if
you enclose the comment in quotation marks.
Examples:
comment=the_first_request
comment="Displacement of wheel
center 1 wrt ground"
User_function Real Specifies up to 30 values for Adams to pass to a user-written
Title String Specifies any of the eight alphanumeric headings for
columns of request output in the request file.
Note: Enter function expressions in the boxes f2 , f3 , f4 , f6 , f7 , and f8 . Do not use f1 and f5 . Adams
Solver uses them to hold magnitudes for the three functions that follow. You do not need to
enter a function in every text box.
F1 Function Specifies the function expression that is the first component
of the request that is being created or modified. The f1
parameter allows you to generate user-defined output
variables and have them reported by Adams to the request
file.
F2 Function Specifies the function expression that is the second
component of the request that is being created or modified.
The f2 parameter allows you to generate user-defined
output variables and have them reported by Adams to the
request file.
F3 Function Specifies the function expression that is the third
request file.

F4 Function Specifies the function expression that is the fourth
request file.
F5 Function Specifies the function expression that is the fifth component
of the request that is being created or modified. The f5
parameter allows you to generate user-defined output
variables and have them reported by Adams to the request
file.
F6 Function Specifies the function expression that is the sixth
request file.
F7 Function Specifies the function expression that is the Seventh
request file.
F8 Function Specifies the function expression that is the eight
request file.
Routine String Specifies an alternative library and name for the user
subroutine REQSUB.
Component_names String This option is available only for XML format. By default,
there are eight components per results set, and they have
generic names, such as X, Y, Z, and MAG.. You can specify
more descriptive names for them or specify a particular unit
label or unit type associated with each component.
Component_units String This option is available only for XML format. Specify the
unit dimension of the result ser components. If you do not
specify units, then the units of the components are
predefined based upon standard request type (For example,
displacement, velocity and acceleration)
output_control 29

Component_labels String This option is available only for XML format. Specify the
labels to be used when plotting the result set components.
Labels can be strings that include white space. Quotes must
be used to define the string if you see special characters or
white space.
Results_name String Specifies the name of the results set in which all result set
components are placed. If there is an existing result set with
this name, then the result set components are placed in that
result set.
Variable_name String Specifies one or more variables that represent the
components associates with a request. This option is only
available if the format of the results files is set to XML.
1. Normally, request names are composed of alphabetic, numeric, or '_' (underscore) characters, and
be assigned to it.
3. You may choose one of the following values for the output_type.
a. DISPLACEMENT
Adams outputs the displacement of the I marker with respect to the J marker. This argument
generates eight headings and eight columns of output. The columns include the time (Time), the
translational magnitude (Mag), the x component (X), the y component (Y), the z component (Z),
the psi angle (Psi), the theta angle (Theta), and the phi angle (Phi).
The psi, theta, and phi angles are the Euler angle displacements of the I marker with respect to
the J marker. Adams calculates this displacement data in the global coordinate system. If you
specify R_MARKER_NAME, Adams resolves the translational x component, the translational y
component, and the translational z component in the coordinate system of the R marker. The R
marker does not affect psi, theta, and phi.
If you enter the 'OUTPUT_CONTROL SET OUTPUT YPR=ON' command, psi, theta, and
phi rotations become yaw, pitch, and roll rotations.
Rotational displacement information differs from all other standard output. Whether this
information is in psi, theta, and phi coordinates or in yaw, pitch, and roll coordinates, the rotation
sequence is not a vector. As a result, Adams outputs no magnitude column. In addition, the
sequence of coordinates is independent of any frame external to the I and the J markers.
Therefore, the R_MARKER_NAME parameter has no effect on the angular coordinates.
b. VELOCITY
Adams outputs the velocity of the I marker with respect to the J marker. This argument generates
nine headings and nine columns of data for velocity. The nine columns include the time (Time),
the translational magnitude (Vm), the translational x component (Vx), the translational y
component (Vy), the translational z component (Vz), the rotational magnitude (Wm), the
rotational x component (Wx), the rotational y component (Wy), and the rotational z component
(Wz).
Adams calculates this velocity data (the first derivative of the displacement of the I marker with
respect to the J marker) in the global coordinate system. If you specify R_MARKER_NAME,
Adams resolves the translational x component, the translational y component, the translational z
component, the rotational x component, the rotational y component, and the rotational z
component in the coordinate system of the R marker.
c. ACCELERATION
Adams outputs the acceleration of the I marker with respect to the J marker. This argument
generates nine headings and nine columns of output. The columns include the time (Time), the
magnitude of translational acceleration (Accm), the translational x component (Accx), the
translational y component (Accy), the translational z component (Accz), the magnitude of
rotational acceleration (Wmdot), the rotational x component (Wxdot), the rotational y
component (Wydot), and the rotational z component (Wzdot). Adams calculates this
acceleration data (the second derivative of the displacement of the I marker with respect to the J
marker) in the global coordinate system. If you specify R_MARKER_NAME, Adams resolves
the translational x component, the translational y component, the translational z component, the
rotational x component, the rotational y component, and the rotational z component in the
coordinate system of the R marker.
output_control 31
d. FORCE
Adams outputs the force associated with the I and the J markers or, if only the I marker is given,
outputs the action-only forces on the I marker. When both, the I and the J markers are given,
Adams sums the forces on the I marker of those forces associated with the I and the J markers.
These forces can include both, applied forces (such as SPRINGDAMPERs and BUSHINGs) and
reaction forces from constraint elements (such as JOINTs and MOTIONs). When only the I
marker is given, Adams sums all of the action-only forces that are applied to the I marker. Adams
reports the components of the resulting vectors in the reference frame of the R marker if you
specify R_MARKER_NAME.
If you do not specify R_MARKER_NAME, Adams reports the components in the ground
reference frame. This argument generates nine columns of output. The columns include the
time, the translational force magnitude, the three components of the translational force, the
rotational force (torque) magnitude, and the three components of the torque.
Applied forces and torques are those generated by beams, bushings, fields, single-component
forces, and spring-dampers. Adams outputs the applied forces and torques acting at the request I
marker (which may be either the applied force I marker or the applied force J marker). The
magnitude and point of force application on the part containing the applied force J marker varies
according to the type and source of the force. For spring-dampers and action-reaction single-
component forces, the forces and torques acting at the J marker are equal and opposite to the
forces and torques acting at the I marker. For action-only single-component forces, there is no
force or torque acting at the applied force J marker. For beams, fields, and bushings, the forces
acting at the applied force J marker are equal and opposite to the forces acting at the applied force
I marker. As long as the applied force I marker and the applied force J marker are coincident, the
torques acting at the applied force J marker are equal and opposite to the torques acting at the
applied force I marker. If there is a finite separation between the I and the J markers, the torques
acting at the applied force J marker are opposite, but not equal, to the torques acting at the applied
force I marker.
Reaction forces and torques are those generated by constraint-inducing elements. For revolute,
primitives, Adams outputs the reaction forces and torques acting at the request I marker (which
may be either the constraint I marker or the constraint J marker). The force and torque acting at
the request J marker are equal and opposite to the force and torque acting at the request I marker.
Depending on the type of constraint, some or all of the torques acting at the I marker are zero.
You must be careful when requesting a force with the I and the J markers reversed from those
specified in the force-producing element. Adams reports the force as if it were applied to the J
marker of the force-producing element. The translational force on the J marker of the force
element will be equal and opposite to the translational force on the I marker of the force element
if it is not action only. The force will be zero if it is action only. The torque on the J marker of
the force element has an extra component that may have significance. The torque is the sum of
two contributions. The first contribution is the opposite of the torque on the I marker. The
second contribution is due to the force acting across the separation between the I and the J
markers. If the force acts along the line of sight of the two markers, this extra torque will be zero.
To minimize misunderstandings, attach your REQUEST markers in the same order as the
markers on the force-producing element.
e. USER
Adams will output the values computed by the user-written subroutine REQSUB. If you choose
a USER request type, you must also supply the USER_FUNCTION parameter to define the
constants Adams will pass to the REQSUB.
4. If you are requesting displacement, velocity, or acceleration data, you must supply the J_marker.
Adams will measure the displacement, velocity, or acceleration of the I marker with respect to the J
marker.
If you are requesting force data for action-reaction forces, you must supply the J marker. Adams will
sum the forces on the I marker of those forces associated with the I and J markers.
If you are requesting force data for action-only forces, do not supply the parameter, J_marker. Adams
will sum all of the action-only forces applied to the I marker.
5. Each title heading can have as many as eight alphanumeric characters, and underscores. No leading
or internal white-space characters are allowed. The first character in each heading must be alphabetic.
You can use all alphanumeric characters. You cannot use the comma (,), the semicolon (;), the
ampersand (&), or the exclamation point (!). These are limitations dictated by the Adams data-set
parser. If you do not want to specify a title for a particular column, use two quotation marks with no
characters in between the quotations marks.
If you want to unset all of the titles, use only two quotation marks with no characters in between the
quotations marks ("").
Examples:
title = First, Second,"", DISP_X, Last, ANG_disp, AMAG, ""
6. To enter a function expression, you enter a series of quoted strings.
verification.
output_control 33
Components Examples
NUMBERS
OPERATORS
• In a FUNCTION expression, Adams allows any of the operators **, *, /, +, and -. Adams executes
SYSTEM CONSTANTS

BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
SYSTEM VARIABLES
ARITHMETIC IFS
follows.
output_control 35
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
In some ways, you may treat IF as a variable. For example, you can place it anywhere in the expression.
In addition, you can nest arithmetic IFs nine levels deep.
Adams FUNCTIONS
FUNCTION expression. he following table lists all the Adams functions and their purposes. Invoke
the text edit window and pick the FUNCTIONS button to get a list of functions that can be accessed.
Names Purposes
directions.
output_control delete femdata
7. Result sets are helpful if you want to group the output from multiple requests into a single results set.
For example, you might have several different requests measuring driver input for a vehicle, and you
might want to place them all within a result set named Driver_Inputs for easier viewing in Adams
PostProcessor.
8. Units for component_labels may be:
MASS AREA
TIME VOLUME
FORCE TORQUE
LENGTH PRESSURE
VELOCITY DENSITY
ACCELERATION ENERGY
ANGLE TORSION_STIFFNESS
ANGULAR_VELOCITY TORSION_DAMPING
ANGULAR_ACCELERATION FREQUENCY
INERTIA AREA_INERTIA
STIFFNESS FORCE_TIME
DAMPING TORQUE_TIME

Allows you to delete an existing femdata object.
Format:
femdata_name = .model.femdata_name
Example:
output_control delete femdata &
request_name= . test.link_forces
Description:

femdata_name String Specifies the femdata to delete.
output_control 37
output_control delete mrequest
menu entry 'UNDO'. You identify a femdata by typing its name. If you created the femdata by
reading an Adams data set, the femdata name is the letters FEM followed by the Adams data set
femdata ID number. For example, the name of Adams FEM/101 is FEM101. If you created the
femdata during preprocessing, you will have given it a name at that time. If a femdata is available by
default, you may identify it by entering only its name. If it is not, you must enter its full name. To
identify a femdata under a different model, for instance, you may need to enter the model name as
well. For example, you may specify femdata 'link_forces' from model 'test' by entering
".test.link_forces". If you type a "?", Adams View will list the femdatas available by default.
2. You must separate multiple femdata names by commas.
Tips:
1. If you realize that this deletion was a mistake, deletion of a request can be reversed by using an UNDO
command.
2. ". If you type a "?", Adams View will list the femdata available by default.

Allows you to delete an existing mrequest. You specify the name of the mrequest you wish to delete by using
the MREQUEST_NAME parameter.
Format:
mrequest_name = string
Example:
output_control delete mrequest &
mrequest_name= .test.mre101
Description:

mrequest_name String Specifies an existing mrequest to be deleted. You may
identify a mrequest by typing its name.
output_control delete request
1. Any Adams View object you delete may be "undeleted" by using the UNDO commands. If you have
menu entry 'UNDO'. You may identify a mrequest by typing its name. If you created the mrequest
by reading an Adams data set or graphics file, the mrequest name is the letters MRE followed by the
Adams data set mrequest ID number. For example, the name of Adams MREQ/101 is MRE101. If
you created the mrequest during preprocessing, you will have given it a name at that time. If an
mrequest is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify an mrequest under another analysis, for instance, you may need to
enter the analysis name as well. For example, you may specify mrequest 101 from the analysis named
test by entering ".test.mre101". If you type a "?", Adams View will list the mrequests available by
default. You must separate multiple mrequest names by commas.
Tips:
1. If you realize that this deletion was a mistake, deletion of an mrequest can be reversed by using an
UNDO command.

Allows you to delete an existing request. You specify the name of the request you wish to delete by using the
REQUEST_NAME parameter.
Format:
request_name = string
Example:
output_control delete request &
request_name = .test.mre101
Description:

request_name String Specifies the request to be deleted
output_control 39
output_control modify femdata
menu entry 'UNDO'. You may identify a request by typing its name. If you created the request by
reading an Adams data set or request file, the request name is the letters REQ followed by the Adams
data set request ID number. For example, the name of Adams REQUEST/101 is REQ101. If you
created the request during preprocessing, you will have given it a name at that time.
If a request is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a request under an analysis, for instance, you may need to enter the
analysis name as well. For example, you may specify request 101 from the analysis named test by
entering "/test/req101. You must separate multiple request names by commas.
Tips:
1. If you realize that this deletion was a mistake, deletion of a request can be reversed by using an UNDO
command.
2. ". If you type a "?", Adams View will list the requests available by default.

Allows you to modify data files of component loads, deformations, stresses, or strains for input to subsequent
finite element or fatigue life analysis for use in third party products. Adams View will not output to any files
unless you specify the format.
Format:
femdata_name = .model_name.femdata_name
new_femdata_name = .model_name.new_femdata_name
adams_id = geom._id
output_type = loads/loads_on_flex/,odal_deformation/stress/strain
r_marker_name = .marker_name
no_inertia = yes/no
peak_slice= fx/fy/fz/fmag/gmag/tx/ty/tz/tmag/none/all
flex_body= .model_name.flexible_body_name
datum = integer_number
nodes = integer_number
hotspots= integer_number
radius= real _number

criterion = von_mises/max_principle/min_principle/max_shear/nor
mal_x/normal_y/normal_z/shear_xy/shear_yz,shear_xz
start = real_number
end = real_number
skip = integer_number
Example:
output_control modify femdata &
femdata_name = fem_data_1 &
new_femdata_name = fem_new_name &
adams_id = 100 &
output_type = stress &
r_marker_name = .marker_name &
flex_body = 101 &
hotspots = 7 &
radius = 0.5 &
criterion = max_principle &
file_name = hotspots_101
These statements create a text file named hotspots_101.tab containing hot spot information for the flexible
body 101. Seven hot spots with a radius of 0.5 based on maximum principal stress are requested. The names
of the DAC files are given the prefix “hotspots_101” as specified in the file_name format.
output_control 41
Description:

femdata_name String Specifies the name of the FEMDATA element in the
modeling database to be created.
New_femdata_name String Specifies the new name of the FEMDATA element in the
modeling database to be created.

Adams data file.

output_type loads/loads_on_ Specifies the information you want as output:
flex/modal_defo
rmation/stress/st  Loads on rigid body/Flex body- Output all external
rain forces (reaction and applied forces except gravity)

acting on the specified body and, optionally, inertial
forces of the specified body (angular velocity and
acceleration, including effects of gravity) as a
function of time. Load data will be output in the
simulation set of units.
 Modal Deformation - Outputs modal deformations
as a function of time of the specified flexible body.
Adams View will only export coordinates of the
active modes in the simulation.
 Nodal Deformation - Outputs nodal deformations
as a function of time of the specified flexible. Adams
View writes the deformations in the simulation set
of units.
 Strain - Outputs strain information if strain modes
are available in the modal neutral file (MNF) of the
specified flexible body and an Adams Durability
license is available. Adams Durability outputs all six
components of strain (normal-X, normal-Y, normal-
Z, shear-XY, shear-YZ, shear-ZX). It outputs strains
in the basic FEA coordinate system of the flexible
body except where specified below.
 Stress - Outputs stress information if modal stresses
are available in the MNF of the flexible body and an
Adams Durability license is available. Adams
Durability outputs all six components of stress
(normal-X, normal-Y, normal-Z, shear-XY, shear-
YZ, shear-ZX). It outputs stresses in the simulation
set of units in the basic FEA coordinate system of
the flexible body except where specified below.
r_marker_name String Specifies the rigid body marker to be the reference coordinate
system to output loads. Because Adams Solver resolves all
loads acting on the rigid body in the coordinate system of the
specified marker, the marker should represent the FEA basic
coordinate system of the part's finite element (FE) model.
output_control 43

no_inertia yes/no Specify ‘yes’ if you want Adams View to include inertial loads
(linear acceleration, angular acceleration, and velocity) when
outputting the loads acting on the body. Otherwise, Adams
View outputs no inertial loads and you will need to rely on
an inertia relief capability in the finite element program to
balance the external loads with the internal loads.
peak_slice fx/fy/fz/fmag/g Specifies that FE model load data are to be output only at
mag/tx/ty/tz/tm those time steps where the specified peak load occurred in
ag/none/all the simulation. When you set the Time options, Adams
View only checks the time steps within those specifications
for the peak load.
flex_body String Enters the flexible body whose data Adams View outputs.
Adams View outputs the data in the FE model basic
coordinate system that is inherent to the flexible body.
datum Integer Enters the node ID of the flexible body to be the datum of
the nodal displacements.
nodes Integer Enters the node numbers of a flexible body whose data is to
be output.
hotspots Integer Enters the number of hot spots to locate and output. With
this option, a text file containing a tab-delimited table of hot
spot information, such as node ID, maximum value, time
when the maximum value occurred, and location, is
generated.
radius Real Enters a radius that defines the spherical extent of each
hotspot. A default value of 0.0 (zero) means that all nodes in
the flexible body will be hotspot candidates.
von_mises/max_ Specifies the value of stress/strain in determining hotspots
criterion principle/min_p from one of Von Mises, Max Prin., Min Prin., Max Shear,
rinciple/max_sh Normal-X, Normal-Y, Normal-Z, Shear-XY, Shear-YZ, or
ear/normal_x/no Shear-ZX.
rmal_y/normal_
z/shear_xy/shear
_yz,shear_xz
file_name String Enters the output file name for the FE model data. You can
specify an existing directory, root name, and/or extension. By
default, the file name will be composed of the Adams run
and body IDs according to the type of data and file format
that you specified in Solver -> Settings -> Output -> More -
> Durability Files

start Real Specifies the time at which to start outputting the data. The
default is the start of the simulation.
end Real Specifies the time at which to end the output of the data or
the search of a peak load. The default is to output to the end
of the simulation.
skip Integer
1. If you do not specify a node list, Adams View exports nodal data at each attachment point of the
flexible body. Adams Solver issues a warning if a node ID is specified that does not belong to the
flexible body.
2. Adams Solver computes all nodal displacements relative to the datum node ID. If you do not specify
a datum node, Adams Solver generates an arbitrary relative set of nodal displacements. It displays a
warning message if the specified node does not belong to the flexible body.
3. You can use the FILE_NAME argument to specify the directory, name, and/or extension
(directory/name.extension) for the output file. If you do not specify a directory, FEMDATA creates
all its output files except DAC files in the current working directory. Because several DAC files are
typically generated for a FEMDATA statement, FEMDATA creates them in a separate directory
named after the body. It creates this directory in the current working directory if it does not exist.
If a file name is not specified in the FILE argument, default file names are assigned according to the
type of FEM data and file format (which is specified in the OUTPUT statement) as shown in the
table below.
FEMDATA Default File Names and Extensions

(none) (none) <run_name> .fem
Loads DAC <run_name>_<channel_id> .dac
NASTRAN <run_name>_<body_name> .dat
ABAQUS <run_name>_<body_name> .dat
ANSYS <run_name>_<body_name> .dat
RPC <run_name> .rsp
Modal DAC <run_name>_<channel_id> .dac
Deformation Generic <run_name>_<body_name .mdf
NASTRAN <run_name>_<body_name> .mdf
PUNCH <run_name>_<body_name> .mdf
ANSYS <run_name> .out
RPC <run_name> .rsp
output_control 45

Nodal Generic <run_name>_<body_name> .ndf
Deformation NASTRAN <run_name>_<body_name> .spc
ANSYS <run_name>_<body_name> .inp
Strain DAC <run_name>_<node_id>e_<channel_id> .dac
Hotspots <run_name>_body_name>_hots .tab
Stress DAC <run_name>_<node_id>se_<channel_id> .dac
Hotspots <run_name>_<body_name>_hote .tab
*Specified in the OUTPUT statement

4. Peak Loads
Except for FMAG, GMAG, and TMAG, each PEAK_SLICE load specification (FX, FY, FZ, TX, TY,
TZ) generates two output time steps for each marker force of the component, one for the maximum
(peak) and one for the minimum (valley). For FMAG and TMAG, only one time step is output for
each marker force since these quantities are load magnitudes and generate only positive values. With
GMAG, only one time step is output per body. If:
• Fm(t) represents the force acting on the body at Marker m.
• rˆx, rˆy, rˆz represents the unit vector of the reference coordinate system of the rigid body (FEA
coordinate system of the flexible body).
• r(t) represents the position of the reference marker (RM) in that coordinate system.
ˆ ˆ ˆ
• || || represents taking the magnitude or length of a vector (that is, || ( r x, r y, r z ) || = 1)
Then the following conditions apply:
• FX = Output loads at time t when F m ( t ) ⋅ rˆx ( t ) is a maximum and minimum for each marker
m.
• FY = Output loads at time t when F m ( t ) ⋅ rˆy ( t ) is a maximum and minimum for each marker
m.
• FZ = Output loads at time t when F m ( t ) ⋅ rˆz ( t ) is a maximum and minimum for each marker
m.
• FMAG = Output loads at time t when F m ( t ) ⋅ r̂ ( t ) is a maximum for each marker m.
• GMAG = Output loads at time t when
 
MAX   F m ( t ) ⋅ r x ( t ),  F m ( t ) ⋅ r y ( t ),  F m ( t ) ⋅ r z ( t )
m m m

Note: Similar expressions exist for TX, TY, TZ, and TMAG. The PEAK_SLICE argument is not
available when you specify a time history OUTPUT load format (DAC or RPC).
output_control modify mrequest
Cautions:
1. Using FEMDATA to output loads encounters the same limitations as exporting FEA Loads in Adams
View.
2. Note that all FEMDATA are output in the Adams modeling units. This causes a problem when the
Adams units are inconsistent with those used in the finite element model, and the data that is output
will be included in a subsequent finite element analysis.
3. For example, when outputting FEMDATA of type LOADS to ANSYS or MSC Nastran for inclusion
in the FE analysis, the Adams and FE modeling units must be consistent. This is also true when
outputting FEMDATA of type NODAL_DEFORMATION when the OUTPUT format is ANSYS
or MSC Nastran and the data will be used as input to the FE analysis.
In the case of outputting FEMDATA of type MODAL_DEFORMATION, the only concern for
units is when MSC Nastran (or PUNCH) has been specified as the OUTPUT format. This is because
rigid body motion is included in the output file along with the modal coordinates. By definition,
modal coordinates are unitless, so the modal stresses (or strains) will be recovered correctly in MSC
Nastran irregardless of unit settings. However, in order for the overall displacement of the component
to be correctly recovered, the unit of length must be consistent between models.

Allows you to modify mrequest files. The MREQUEST statement specifies multiple sets of data that you
want Adams Solver (FORTRAN) to write in the tabular output file and request file. You can request sets of
displacements, velocities, accelerations, or forces for system elements, such as parts, joints, joint primitives,
or applied forces in the system.
Format:
mrequest_name= .model_name.mrequest_name
new_mrequest_name= .model_name.mrequest_name
adams_id= geom_id
comment = string
part_name = .model.part_name
joint_name = .model.joint_name
jprim_name = .model.primitive_joint_name
force_name = .model.existing_force_name
all = parts/joints/jprims/forces
output_control 47
Example:
output_control modify mrequest &
mrequest_name = mrequest__1 &
comment = 'sample output control creation' &
all = parts &
output_type = displacement
This MREQUEST statement requests displacement data for all Parts. For the part, Adams Solver
(FORTRAN) outputs eight headings and eight columns of data to the tabular output file. The same
information also goes to the request file. Because this statement does not supply arguments J and RM, Adams
Solver (FORTRAN) measures the displacements with respect to the ground coordinate system (GCS), and
resolves the displacements in the global coordinate system.
Description:

mrequest_name String Specifies the name of the mrequest to be modified. You use
this parameter to identify the existing mrequest to be
new_Mrequest_na String Specifies the new name of the mrequest. You use this
me parameter to identify the existing mrequest to be affected
with this command.
Adams data file.

J_marker_name String Specifies a single base marker for measuring the
displacements, velocities, or accelerations of the center-of-
mass of the parts. Adams Solver (FORTRAN) makes all
measurements for parts on the center-of-mass marker on
each part with respect to the J marker you specify. The J
marker defaults to the ground coordinate system (GCS).
 id1 [ ,...,id
JOINTS = 
 ALL
accelerations, or forces for as many as thirty JOINT
statements or for all JOINT statements. Adams Solver
(FORTRAN) makes these measurements on the I marker
with respect to the J marker.
 id1 [ ,...,id
JPRIMS = 
 ALL
accelerations, or forces for as many as thirty JPRIM
statements or for all JPRIM statements. Adams Solver
(FORTRAN) makes these measurements on the I marker
with respect to the J marker.
 id1 [ ,...,id
PARTS = 
 ALL
or accelerations for as many as thirty center-of-mass of parts
in the model (to which the PART statement identifiers
refer) or for the centers of mass of all parts (except the
ground part). Adams Solver (FORTRAN) makes these
measurements on the center-of-mass marker of the part
with respect to the marker specified by the J argument. The
PARTS argument cannot be used for massless parts. The
PARTS argument cannot be used with the FORCE
argument.
r_marker_name String Identifies the reference marker with respect to which you
want to resolve information. RM defaults to zero, which
causes Adams Solver (FORTRAN) to resolve components
in the ground coordinate system (GCS).
output_control 49

comment String Specifies a title for the top of each set of information the
MREQUEST statement outputs. The entire comment
must be on one line. Because the COMMENT argument
can be only eighty characters long at most, the title can be
from seventy-two characters long (if you do not abbreviate
COMMENT=) to seventy-eight characters long (if you
abbreviates COMMENT= to C=). Blank spaces and all
alphanumeric characters can be used. However, the comma
(,), the semicolon (;), the ampersand (&), and the
exclamation point (!) cannot be used.
DISPLACEMENT/V See extended definition for details on each output_type
output_type ELOCITY/ACCELE
RATION/FORCE
part_name String Specifies names of part with which you want to output
joint_name String Specifies name of joint with which you want to output
jprim_name String Specifies name of joint primitive with which you want to
output displacements,velocities, or accelerations.
force_name String Specifies name of joint with which you want to output
1. The MREQUEST statement indicates multiple sets of data you want Adams Solver (FORTRAN) to
write in the tabular output file and request file. You can request sets of displacements, velocities,
accelerations, or forces for system elements such as parts, joints, joint primitives, or applied forces in
the system.
Acceleration -Generates acceleration requests that output the accelerations for the markers that define
part centers of mass, joints, joint primitives, or applied forces. This argument generates nine headings
and nine columns of output for each part, joint, joint primitive, or applied force. The columns in the
Tabular Output file include the time (TIME), the translational magnitude (ACCM), the x
component (ACCX), the y component (ACCY) the z component (ACCZ), the rotational magnitude
(WDTM), the rotational x component (WDTX), the rotational y component (WDTY), and the
rotational z component (WDTZ). The same data without the magnitude are written in the Request
file.
Indicates that you want to output displacements, velocities, accelerations, or forces for as many as
thirty BEAM, BUSHING, FIELD, GFORCE, NFORCE, SFORCE, SPRINGDAMPER,
VFORCE, and VTORQUE statements or for all of these statements. For action-reaction forces,
 id1 [ ,...,id30] 
APPFORS =  
 ALL 
Displacement- Generates displacement requests that output the displacements for the markers that
define part centers of mass, joints, joint primitives, or applied forces. This argument generates eight
headings and eight columns of output for each part, joint, joint primitive, or applied force. The
columns in the tabular output file include the time (TIME), the translational magnitude (MAG), the
x component (X), the y component (Y), the z component (Z), the psi angle (PSI), the theta angle
(THETA), and the phi angle (PHI). The same data without the magnitude are written in the Request
file. For joints, joint primitives, and applied forces, the psi, theta, and phi angles are the Euler angle
displacements of the I marker with respect to the J marker. For parts, the psi, theta, and phi angles
are the Euler rotations of the part center-of-mass marker with respect to the ground coordinate system
(GCS) or with respect to a J marker you specify.
Force -Generates force requests that output the forces for the markers that define joints, joint
primitives, or applied forces. This argument generates nine headings and nine columns of output for
each joint, joint primitive, or applied force. The columns in the Tabular Output file include the time
(TIME), the translational force magnitude (FM), the translational x component (FX), the
translational y component (FY), the translational z component (FZ), the rotational force magnitude
(TM), the rotational x component (TX), the rotational y component (TY), and the rotational z
component (TZ). The same data without the magnitudes are written to the Request file. The FORCE
argument cannot be used with the PARTS argument.
2. Adams Solver (FORTRAN) measures the force that the J marker applies on the I marker. For action-
only forces, Adams Solver (FORTRAN) measures the external forces acting on the I marker. If a
MREQUEST statement is issued with an APPFORS argument that requests information for an
identifier that is used for two or more applied force statements, Adams Solver (FORTRAN) outputs
information for the first applied force statement with that identifier. To avoid problems, you may
want to use a different identifier for each applied force statement in the dataset.
3. Adams Solver (FORTRAN) calculates all time derivatives in the ground coordinate system (GCS),
although you can specify that the data be resolved in another reference frame. This is of no
importance in the case of force data, but it can be very important in the case of velocities and
accelerations. For example, joint velocities are actually translational and rotational velocity difference
vectors of the joint I marker and the joint J marker in ground. Joint accelerations are actually
translational and rotational acceleration difference vectors of the joint I marker in ground and the
joint J marker in ground.
4. Because two markers (I and J) define each joint, joint primitive, and applied force, Adams Solver
(FORTRAN) measures the request information for one of these at the I marker with respect to the J
marker. Because a center-of-mass marker is the only marker that is necessary to define a part, Adams
Solver (FORTRAN) measures the request information for a part at its center-of-mass marker with
respect to ground or with respect to an alternative marker you specify. Regardless of the system
information you want, a reference marker (RM) can be used to resolve the component information
into any coordinate system you wish.
output_control 51
Cautions:
1. Note that the units for rotational displacement data in the request output of the tabular output file
2. For any argument =ALL, Adams Solver (FORTRAN) ignores any invalid selections.
3. Applied forces and torques are those generated by beams, bushings, fields, general forces
(GFORCEs), n-component forces (NFORCEs), single-component forces (SFORCEs),
springdampers (SPRINGDAMPERs), vector forces (VFORCEs), and vector torques (VTORQUEs).
Adams Solver (FORTRAN) outputs the applied forces and torques acting at the request I marker
(which may be either the applied force I marker or the applied force J marker).
The magnitude and point of force application on the part containing the applied force J marker varies
with the type and source of the force.
• For springdampers, action-reaction single-component forces, general forces, vector forces, and
vector torques, the forces and torques acting at the J marker are equal and opposite to the forces
and torques acting at the I marker.
• For action-only single-component forces, no force or torque acts at the applied force J marker.
• For beams, fields, bushings, and multi-point forces, the forces acting at the applied force J marker
are equal and opposite to the forces acting at the applied force I marker.
4. As long as the applied force I marker and the applied force J marker are coincident, the torques acting
at the applied force J marker are equal and opposite to the torques acting at the applied force I marker.
If there is a finite separation distance between the I and J markers, the torques acting at the applied
force J marker are not necessarily opposite or equal, to the torques acting at the applied force I marker.
5. Reaction forces and torques are those generated by constraint-inducing elements. For revolute,
primitives, Adams Solver (FORTRAN) outputs the reaction forces and torques acting at the request
I marker (which may be either the constraint I marker or the constraint J marker). Depending on the
type of constraint, some or all of the torques acting at the I marker are zero. The force and torque
acting at the request J marker are equal and opposite to the force and torque acting at the request I
marker.
6. Determining reaction forces-and torques for cylindrical, planar, rack-and-pinion, screw, and
translational joints and for inline and inplane joint primitives is more complex. If the request I marker
corresponds to the constraint I marker, then Adams Solver (FORTRAN) outputs the force and
torque acting at the constraint I marker. If the request I marker corresponds to the constraint J
marker, then AdamsAdams Solver (FORTRAN) outputs the force and torque acting at the
instantaneous location of the constraint I marker, but on the part containing the constraint J marker.
The force translated to the constraint J marker is the same as computed above. If the I and J markers
are coincident, the torque translated to the constraint J marker is the same as computed above. But if
there is a finite separation between the I and J markers, the torque translated to the constraint J marker
is different from the one computed above (because of the moments contributed by the reaction
forces).
7. The MREQUEST statement is not scheduled to be supported in Adams Solver (C++). You are
encouraged to migrate away from this statement and use the REQUEST statement instead.
output_control modify request

Allows you to modify an existing request.
A REQUEST indicates a set of data you want Adams to output. Using a REQUEST, you can output a set
of displacements, velocities, forces, or accelerations, with respect to markers in your system; or you can use
the user-written subroutine REQSUB to define nonstandard output.
Adams calculates all data in the ground reference frame, although you can specify that the data be resolved in
another reference frame. This is of no importance in the case of force data, but it can be very important in
the case of displacements and time derivatives, i.e. velocities and accelerations.
Except for rotational displacements, all the information types are vectors. For example, joint velocities are
actually translational and rotational velocity difference vectors of the joint I marker with respect to the joint
J marker. Joint accelerations are actually translational and rotational acceleration difference vectors of the
joint I marker with respect to the joint J marker. In other words, if V is a translational vector quantity and W
is an rotational vector quantity,
Vij = Vi – Vj,
And Wij = Wi – Wj,
V’ij = V’i- V’j
And W’ij = W’I – W’j
Note that the units for rotational displacement data in the request output of the tabular file default to degrees.
The units for all other angular output data defaults to radians.
Format:
output_control modify
request_name = .model_name.request_name
new_request_name = .model.new_request_name
adams_id = geom._id
comment = string
component_names= string
component_units = string
component_labels = string
results_name = string
title = string
i_marker_name = marker_name
user_function = real number
f1 = run time function
output_control 53
output_control modify
variable_name = variable name
routine= string
Description:

request_name String Specifies the name of the request to be modified. You
may later identify a request by typing its name.
new_request_name String Specifies the name of the new request.
Adams data file.
output_type Displacement/velocity/ Specifies whether you want the request to output
acceleration/force/user displacement, velocity, acceleration, force, or user data.
i_marker_name An existing triad Specifies the marker for which you wish Adams to
generate data.
j_marker_name An existing triad Specifies the marker with respect to which you wish
Adams to generate the data.
r_marker_name An existing triad Specifies the marker with respect to which you want
Adams to resolve the data. Adams computes the data
identified by the I and J markers, then reports the data
as x, y, and z components in the reference frame of the
reference marker. Angular displacements, which are not
vectors, are not affected by reference marker. If you do
not supply this parameter, Adams will resolve the data
in the ground reference frame.

comment String Specifies a comment for the request. The comment can
contain up to 80 characters, and can be comprised of
letters of the alphabet (a-z, A-Z), numbers (0-9), and
underscores. You may also use spaces and special
characters (*&^%$#) if you enclose the comment in
quotation marks.
Examples:
comment="Displacement of wheel
center 1 wrt ground"
title String Specifies any of the eight alphanumeric headings for
columns of request output in the request file.
F1 Function Specifies the function expression that is the first
component of the request that is being created or
modified. The f1 parameter allows you to generate user-
defined output variables and have them reported by
Adams to the request file.
F2 Function Specifies the function expression that is the second
F3 Function Specifies the function expression that is the third
F4 Function Specifies the function expression that is the fourth
modified The f4 parameter allows you to generate user-
F5 Function Specifies the function expression that is the fifth
output_control 55

F6 Function Specifies the function expression that is the sixth
F7 Function Specifies the function expression that is the Seventh
F8 Function Specifies the function expression that is the eight
subroutine REQSUB.
Component_names String This option is available only for XML format. By
default, there are eight components per results set, and
they have generic names, such as X, Y, Z, and MAG..
You can specify more descriptive names for them or
specify a particular unit label or unit type associated
with each component.
Component_units String This option is available only for XML format. Specify
the unit dimension of the result set components. If you
do not specify units, then the units of the components
are predefined based upon standard request type (For
example displacement, velocity and acceleration)
Component_labels String This option is available only for XML format. Specify
the labels to be used when plotting the result set
components. Labels can be strings that include white
space. Quotes must be used to define the string if you
see special characters or white space.
Results_name String Specifies the name of the results set in which all result
set components are placed. If there is an existing result
set with this name, then the result set components are
placed in that result set.
Variable_name String Specifies one or more variables that represent the
components associated with a request. This option is
only available if the format of the results files is set to
XML.
1. Normally, request names are composed of alphabetic, numeric, or '_' (underscore) characters, and
be assigned to it.
3. You may choose one of the following values for the output_type.
A. DISPLACEMENT
Adams outputs the displacement of the I marker with respect to the J marker. This argument
generates eight headings and eight columns of output. The columns include the time (Time), the
translational magnitude (Mag), the x component (X), the y component (Y), the z component (Z),
the psi angle (Psi), the theta angle (Theta), and the phi angle (Phi).
The psi, theta, and phi angles are the Euler angle displacements of the I marker with respect to
the J marker. Adams calculates this displacement data in the global coordinate system. If you
specify R_MARKER_NAME, Adams resolves the translational x component, the translational y
component, and the translational z component in the coordinate system of the R marker. The R
marker does not affect psi, theta, and phi.
If you enter the 'OUTPUT_CONTROL SET OUTPUT YPR=ON' command, psi, theta, and
phi rotations become yaw, pitch, and roll rotations.
output_control 57
Rotational displacement information differs from all other standard output. Whether this
information is in psi, theta, and phi coordinates or in yaw, pitch, and roll coordinates, the rotation
sequence is not a vector. As a result, Adams outputs no magnitude column. In addition, the
sequence of coordinates is independent of any frame external to the I and the J markers.
Therefore, the R_MARKER_NAME parameter has no effect on the angular coordinates.
B. VELOCITY
Adams outputs the velocity of the I marker with respect to the J marker. This argument generates
nine headings and nine columns of data for velocity. The nine columns include the time (Time),
the translational magnitude (Vm), the translational x component (Vx), the translational y
component (Vy), the translational z component (Vz), the rotational magnitude (Wm), the
rotational x component (Wx), the rotational y component (Wy), and the rotational z component
(Wz).
Adams calculates this velocity data (the first derivative of the displacement of the I marker with
respect to the J marker) in the global coordinate system. If you specify R_MARKER_NAME,
Adams resolves the translational x component, the translational y component, the translational z
component, the rotational x component, the rotational y component, and the rotational z
component in the coordinate system of the R marker.
C. ACCELERATION
Adams outputs the acceleration of the I marker with respect to the J marker. This argument
generates nine headings and nine columns of output. The columns include the time (Time), the
magnitude of translational acceleration (Accm), the translational x component (Accx), the
translational y component (Accy), the translational z component (Accz), the magnitude of
rotational acceleration (Wmdot), the rotational x component (Wxdot), the rotational y
component (Wydot), and the rotational z component (Wzdot). Adams calculates this
acceleration data (the second derivative of the displacement of the I marker with respect to the J
marker) in the global coordinate system. If you specify R_MARKER_NAME, Adams resolves
the translational x component, the translational y component, the translational z component, the
rotational x component, the rotational y component, and the rotational z component in the
coordinate system of the R marker.
D. FORCE
Adams outputs the force associated with the I and the J markers or, if only the I marker is given,
outputs the action-only forces on the I marker. When both the I and the J markers are given,
Adams sums the forces on the I marker of those forces associated with the I and the J markers.
These forces can include both applied forces (such as SPRINGDAMPERs and BUSHINGs) and
reaction forces from constraint elements (such as JOINTs and MOTIONs). When only the I
marker is given, Adams sums all of the action-only forces that are applied to the I marker. Adams
reports the components of the resulting vectors in the reference frame of the R marker if you
specify R_MARKER_NAME.
If you do not specify R_MARKER_NAME, Adams reports the components in the ground
reference frame. This argument generates nine columns of output. The columns include the time,
the translational force magnitude, the three components of the translational force, the rotational
force (torque) magnitude, and the three components of the torque.
Applied forces and torques are those generated by beams, bushings, fields, single-component
forces, and spring-dampers. Adams outputs the applied forces and torques acting at the request I
marker (which may be either the applied force I marker or the applied force J marker). The
magnitude and point of force application on the part containing the applied force J marker varies
according to the type and source of the force. For spring-dampers and action-reaction single-
component forces, the forces and torques acting at the J marker are equal and opposite to the
forces and torques acting at the I marker. For action-only single-component forces, there is no
force or torque acting at the applied force J marker. For beams, fields, and bushings, the forces
acting at the applied force J marker are equal and opposite to the forces acting at the applied force
I marker. As long as the applied force I marker and the applied force J marker are coincident, the
torques acting at the applied force J marker are equal and opposite to the torques acting at the
applied force I marker. If there is a finite separation between the I and the J markers, the torques
acting at the applied force J marker are opposite, but not equal, to the torques acting at the applied
force I marker.
Reaction forces and torques are those generated by constraint-inducing elements. For revolute,
primitives, Adams outputs the reaction forces and torques acting at the request I marker (which
may be either the constraint I marker or the constraint J marker). The force and torque acting at
the request J marker are equal and opposite to the force and torque acting at the request I marker.
Depending on the type of constraint, some or all of the torques acting at the I marker are zero.
You must be careful when requesting a force with the I and the J markers reversed from those
specified in the force-producing element. Adams reports the force as if it were applied to the J
marker of the force-producing element. The translational force on the J marker of the force
element will be equal and opposite to the translational force on the I marker of the force element
if it is not action only. The force will be zero if it is action only. The torque on the J marker of
the force element has an extra component that may have significance. The torque is the sum of
two contributions. The first contribution is the opposite of the torque on the I marker. The
second contribution is due to the force acting across the separation between the I and the J
markers. If the force acts along the line of sight of the two markers, this extra torque will be zero.
To minimize misunderstandings, attach your REQUEST markers in the same order as the
markers on the force-producing element.
E. USER
Adams will output the values computed by the user-written subroutine REQSUB. If you choose
a USER request type, you must also supply the USER_FUNCTION parameter to define the
constants Adams will pass to the REQSUB.
4. If you are requesting displacement, velocity, or acceleration data, you must supply the J_marker.
Adams will measure the displacement, velocity, or acceleration of the I marker with respect to the J
marker.
output_control 59
If you are requesting force data for action-reaction forces, you must supply the J marker. Adams will
sum the forces on the I marker of those forces associated with the I and J markers.
If you are requesting force data for action-only forces, do not supply the parameter J_marker. Adams
will sum all of the action-only forces applied to the I marker.
5. Each title heading can have as many as eight alphanumeric characters, and underscores. No leading
or internal white-space characters are allowed. The first character in each heading must be alphabetic.
You can use all alphanumeric characters. You cannot use the comma (,), the semicolon (;), the
ampersand (&), or the exclamation point (!). These are limitations are dictated by the Adams data-
set parser. If you do not want to specify a title for a particular column, use two quotation marks with
no characters in between the quotations marks.
If you want to unset all of the titles, use only two quotation marks with no characters in between the
quotations marks ("").
Examples:
title = First, Second,"", DISP_X, Last, ANG_disp, AMAG, ""
verification.
Components Examples
Continuation commas FUNCTION = 1 + 1 + 1 + 1 + 1 + 1 , + 1 + 1 + 1 + 1 + 1 + 1 + 1
NUMBERS
OPERATORS
• In a FUNCTION expression, Adams allows any of the operators **, *, /, +, and -. Adams executes
SYSTEM CONSTANTS

BLANKS
as they do in an Adams statement. However, you should remember these two restrictions:
CONTINUATION COMMAS
FUNCTION BUILDER
output_control 61
SYSTEM VARIABLES
ARITHMETIC IFS
follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
Invoke the text edit window and pick the FUNCTIONS button to be a list of functions that can be
accessed.
Names Purposes
directions.
7. Result sets are helpful if you want to group the output from multiple requests into a single results set.
For example, you might have several different requests measuring driver input for a vehicle, and you
might want to place them all within a result set named Driver_Inputs for easier viewing in Adams
PostProcessor.
8. Units for component_labels may be:
MASS AREA
TIME VOLUME
FORCE TORQUE
LENGTH PRESSURE
VELOCITY DENSITY
ACCELERATION ENERGY
ANGLE TORSION_STIFFNESS
ANGULAR_VELOCITY TORSION_DAMPING
ANGULAR_ACCELERATION FREQUENCY
output_control 63
output_control set debug
INERTIA AREA_INERTIA
STIFFNESS FORCE_TIME
DAMPING TORQUE_TIME

Allows you to output data for debugging your data set. You can instruct Adams toprint out information using
the following parameters:
Format:
eprint = on/off
verbose = on/off
topology= on/off
dof = on/off
Example:
output_control set debug &
eprint = on &
verbose = off &
topology = on &
dof = on
Description:

model_name String Specifies the model to be modified. You use this parameter to
eprint On/Off Specifies that a block of information will be printed for each
kinematic, static, or dynamic step.
verbose On/Off Specifies that Adams will output additional information in the
diagnostic messages and send it to the screen during an analysis.
jmdump On/Off Specifies that the Jacobian matrix will be dumped after each
iteration. JMDUMP is useful only when you request a dynamic
analysis.

reqdump On/Off Specifies that data from the REQUEST and MREQUEST
statements is to be output at each iteration.
rhsdump On/Off Specifies that data from the YY array (state vector), the RHS array
(error terms), and the DELTA array (increment to state vector) is to
be dumped at each iteration.
dump On/Off Specifies that Adams will write the internal representation of your
data set in the tabular output file after Adams reads and checks the
input.
topology On/Off Specifies that Adams will print topological data in the message file.
dof On/Off Specifies that a degree-of-freedom table will be printed in the
tabular output file.
associated with it.
2. The “eprint” information helps you to monitor the simulation process and to locate the source of the
error if there is a problem.
Each step consists of two phases:
a. A forward step in time (dynamic predictor).
b. The solution of the equations of motion (dynamic corrector).
For the first phase, Adams prints three or four pieces of information. The information includes the
following:
• The step number. This is a running count of the number of steps taken and can be used as a
measure of how hard Adams is working.
• For dynamics, the order of the predictor. This corresponds to the order of the polynomial Adams
uses to predict the solution at the end of the integration step.
• The value of time at the beginning of the step.
• The size of the step.
For the second phase, Adams prints out the cumulative number of iterations and a table of
information about the iterations. The cumulative number of iterations is a running count of the
iterations needed to solve the equations of motion and can be used as a measure of how many
computations Adams is performing. The table contains information about the maximum equation
error and maximum variable change for each iteration. For each iteration, Adams prints out seven or
eight pieces of the following information:
output_control 65
output_control set madata
The iteration number. This will be the one at the beginning of each step and will increment by one
until Adams converges to a solution or exceeds the maximum allowable number of iterations.
The absolute value of the largest equation error. Each equation should have an error value close to
zero. This number is an indicator of how far Adams is from a solution. It should decrease after every
iteration.
The data set element associated with the largest equation error.
For the above data set element, the equation that has the largest equation error.
The absolute value of the largest change in a variable. The final iteration should not need to change
variables very much. This number is an indicator of how far Adams needs to change variables to
approach. The data set element associated with the absolute value of the largest change in a variable.
For the above data set element, the variable with the largest change.
If Adams has updated the Jacobian, YES appears under the new Jacobian header.
3. Information such as the name of the subroutine from which Adams sends each diagnostic,
explanations, and possible remedies (when available) will be output
4. Adams can generate topological data from the information in your data set about the relationship
between parts and constraints ( except for couplers and user-defined constraints), such as joints. An
understanding of this topological data will help you find constraint errors in you model, but it is not
essential to an understanding of Adams. You can use the topological data generated by Adams to chart
the connections between parts and constraints in the model.This alerts you to overconstrained loops
and immobile loops. A value of ON instructs Adams to print this data in the message file. The default
value is OFF.
5. The dof table tells whether or not each of the six components of motion (i.e. translation along the x-
axis, the y-axis, and the z-axis and rotation about the x-axis, the y-axis, and the z-axis) is constrained
for each part. These are the degrees of freedom as input, not the degrees of freedom after Adams
removes redundant constraints.
Cautions:
1. Adams always outputs VERBOSE information to the message file regardless of the setting of the
VERBOSE parameter.
2. The dump facility essentially maps the equations and variables in your system and provides their
numeric codes.
Tips:
1. If you do not include the VERBOSE argument, Adams outputs only severities and basic error
messages to the screen.

MADATA generates a modal file. This file serves as input to the Adams Modal program. Adams Modal is an
auxiliary program marketed and supported by Mechanical Dynamics, Inc.
Format:
statics = yes /no
time = real_number
comment= string
Example:
output_control set madata &
model_name= model_1 &
statics = yes &
time = 10 &
comment= "Displacement of wheel center 1 wrt ground"
Description:

model_name String Specifies the model to be modified. You use this parameter
command.
statistics Yes/No Specifies that the modal data is to be dumped from the first
static equilibrium analysis and writes it to the modal file.
time Real Number Dumps the modal data at up to thirty time steps
greater than 0 (r1[,...,r30]) from the next quasi-static equilibrium analysis
or from the next dynamic analysis and writes it to the modal
file.
Comment String Specifies a comment for request, mrequest, madata, and
results entities.
associated with it.
2. To record modal data for subsequent static equilibrium analyses, you must use an MADATA
command/statement with the STATICS argument just before each static equilibrium analysis.
output_control 67
output_control set output
3. The The REAL values for the tme parameter (r1[,...,r30]) should correspond to thetime steps for a
quasi-static equilibrium or a dynamic analysis. The values (r1[,...,r30]) must each be greater than zero.
4. The comment can contain up to 80 characters, and can be comprised of letters of the alphabet (a-z,
A-Z), numbers (0-9), and underscores. You may also use spaces and special characters (*&^%$#) if
Cautions:
1. Adams always outputs VERBOSE information to the message file regardless of the setting of the
VERBOSE parameter.
2. The dump facility essentially maps the equations and variables in your system and provides their
numeric codes.
Tips:
1. With Adams Modal, you can linearize a mechanical system about any appropriate point of interest
and calculate eigenvalues and eigenvectors for that point in time. You can then use this data to analyze
the linear system response. The Adams Modal program includes a comprehensive postprocessor for
easy graphic examination of the computed data.

OUTPUT controls the generation of request, graphics, and initial conditions files. In addition, it controls
the form, format, coordinates, filtering, and scaling of request data in the tabular output file. Specifically,
OUTPUT controls the following:
1. Forms of request data in the tabular output file:
 X-y charts of the request data for the tabular output file--The output is in the same order as the
requests are in the data set. The information about each request (including those created by an
MREQUEST) is in two parts. The left side of the first part contains a table of simulation time and
the translational information output by the request, and the right side contains a plot of the
translational information against time. The left side of the second part contains a table of simulation
time and the rotational information output by the request, and the right side contains a plot of the
rotational information against time.
These plots differ in two important ways from plots you create with the Adams PLOT command, or
the Adams View XY_PLOT command. First, time is along the vertical axis in the chart plots and
request data is along the horizontal axis. Second, the chart plots are normalized; i.e. each curve is
scaled independently of the others from the highest value to the lowest value for that curve.
Therefore, use care when comparing curves to one another. You can compare the shapes but not the
magnitudes of the curves.
• Time-response-request tables--A time-response-request table lists all values for a single request
from throughout the simulation. There is one line in the table for each output time step; the lines
are in ascending order of time.
• Output-step-request (OS) table--An output-step-request table lists the values of all requests at
each output time step. There is a line for each output time step, followed by one line for each
request.
2. Formats of request data in the tabular output file
• Columns per line - 72 columns per line or - 132 columns per line
• Numerical notation of request data in the tabular output file - Fixed-point--Fixed-point notation
expresses a decimal or an integer number without an exponent or
• Scientific--Scientific notation expresses a number as the appropriate power of 10 (the
exponent). Adams uses E between the mantissa and the exponent, and may use a decimal
number as the value.
3. Coordinates of rotational request data in the tabular output file
• Yaw, pitch, and roll or o Psi, theta, and phi
4. Scales for request data in the tabular output file
• Scale for displacements o Scale for velocities o Scale for accelerations o Scale for forces
5. Filters for request data in the tabular output file
• Zero filter for displacements
• Zero filter for velocities
• Zero filter for accelerations
• Zero filter for forces
Format:
model_name= String
chart = on/off
reqsave = on/off
dacsave = on/off
rpcsave = on/off
print = on/off
fixed = on/off
osformat = on/off
ypr = on/off
separator = on/off
icsave= on/off
teletype= on/off
grsave= on/off
output_control 69

dscale= real
dzero= real
vscale= real
vzero= real
ascale= real
azero = real
fscale= real
fzero = real
loads= none/ dac/ nastran/ generic/ rpc/ ansys/ abaqus/ marc
modal_deformation= none/ generic/ nastran/ dac/ punch/ rpc/ ansys/ femfat
nodal_deformation= none/ generic/ nastran/ ansys/ abaqus
stress== none/dac/generic
strain none/dac/generic
Description:

model_name String Specifies the model to be modified. You use this
parameter to identify the existing model to be affected
with this command.
chart On/off Specifies that Adams will produce x-y charts of the
request data in the tabular output file. If you do not
specify CHART=ON, Adams does not produce charts
of the request data for the tabular output file. A value
of ON for this parameter will produce a chart, and a
value of OFF will not produce a chart.
reqsave On/off Specifies that Adams will save request output in the
request file so that you can use Adams View to display
x-y plots. If you do not specify REQSAVE=ON,
Adams does not save the request output in the request
file. The default value for this parameter is OFF.
dacsave On/off
rpcsave On/off

print On/off Specifies whether or not Adams will print time-
response-request tables in the Adams Tabular Output
File. If you specify ON, Adams will write tables for
each request and mrequest in your model. If you specify
OFF, Adams will not write the tables.
fixed On/off Specifies numerical output in fixed-point notation
format. A value of FIXED=ON will force output to
fixed-point notation. Any values that are too small or
too large for fixed-point notation are output in
scientific notation. If you specify FIXED=OFF, Adams
formats numerical output in scientific notation.
osformat On/off Specifies that output-step-request (OS) tables will be
written to the tabular output file immediately after
completion of each output step for dynamic,
kinematic, or quasi-static equilibrium analysis. If you
specify OSFORMAT=ON, Adams outputs an output-
step-request (OS) table at each output time step during
simulation. If you specify OSFORMAT=OFF, Adams
does not output request data in this form for these
analysis types.
ypr On/off Specifies that rotational values are to be OUTPUT in
yaw, pitch, and roll coordinates, rather than in psi,
theta, and phi coordinates.
separator On/off Specifies whether or not Adams will write separators to
the Request, Graphics, Results, and Tabular Output
Files when you modify the model topology in the
middle of a simulation.
icsave On/off Specifies that the state vector at every output time step
will be saved.
teletype On/off Specifies Adams to format tabular output for printers
with 72 columns per line, rather than for printers with
132 columns per line (this is done with the value
TELETYPE=ON). A value of TELETYPE=OFF
instructs Adams to format tabular output in 132
columns.
grsave On/off Specifies that Adams is to save graphic output in a
graphics file. This file can then be read into Adams
View, and the graphics can be displayed. A value of
GRSAVE=ON will instruct Adams to write graphics
data to the graphics file. If GRSAVE=OFF is specified,
Adams does not save graphics output.
output_control 71

dscale Real Specifies the scale factor applied to translational and
rotational displacements Adams outputs. Dscale
accepts two REAL numbers( r1, r2). Define r1 to scale
the translational displacements. Define r2 to scale the
rotational displacements. Both r1 and r2 default to
1.0.
dzero Real Specifies that output displacements less than the value
of this parameter, in magnitude, are to be set equal to
zero. The value of DZERO must be greater than zero.
The value of DZERO defaults to 1.0E-07 in scientific
notation and to 0.001 in fixed-point notation.
vscale Real Specifies scale factors to apply to the translational and
rotational velocities Adams outputs. VSCALE accepts
two REAL numbers( r1, r2 ). Define r1 to scale the
translational velocities. Define r2 to scale the rotational
velocities. Both r1 and r2 default to 1.0.
vzero Real Specifies that output velocities less than the value of
this parameter, in magnitude, are to be set equal to zero.
The value of VZERO must be greater than zero. The
value of VZERO defaults to 1.0E-07 for output in
scientific notation and to 0.001 for output in fixed-
point notation.
ascale Real Specifies a scale factor which is applied to the
translational and the rotational accelerations that
Adams outputs.
Azero Real Specifies that output accelerations that have a
magnitude less than the value of this parameter are to
be set equal to zero. The value given must be greater
than zero. The value defaults to 1.0E-07 for output in
point notation.
fscale Real Specifies a scale factor which is applied to the
translational and the rotational forces Adams outputs.
FSCALE accepts two REAL numbers ( r1, r2 ). Define
r1 to scale the translational forces. Define r2 to scale the
rotational forces. Both r1 and r2 default to 1.0E+00 in
scientific notation and to 1.0 in fixed-point notation.

fzero Real Specifies that output forces less than the value of this
parameter, in magnitude, are to be set equal to zero.
The value of FZERO must be greater than zero. The
value of FZERO defaults to 1.0E-07 for output in
point notation.
loads none/ dac/ nastran/ generic/ rpc/ ansys/ abaqus/ marc
modal_deformation none/ generic/ nastran/ dac/ punch/ rpc/ ansys/ femfat
nodal_deformation none/ generic/ nastran/ ansys/ abaqus
stress none/dac/generic
strain none/dac/generic
associated with it.
2. When you request a static equilibrium analysis, Adams always outputs an output-step-request (OS)
table whether or not you specify OSFORMAT=ON. Use OSFORMAT to view the values of all
requests at a particular output time or to provide printed output in cases where the simulation might
not run to completion. A simulation may not run to completion because the model or user-written
subroutines are not fully debugged. OSFORMAT might provide information useful useful in
debugging the model or the user-written subroutines.
3. For ypr, first Adams rotates about the z-axis, then about the new negative y-axis (y'), and then about
the second new x-axis (x"). If you specify YPR=OFF, Adams outputs rotational values in psi, theta,
and phi coordinates.
4. You can change the model topology by adding Adams commands to your ACF file to activate an
element, deactivate an element, change a marker position, or change the type or point of application
of a force or constraint during a simulation.
If you specify SEPARATOR=ON (this is the default) the analysis information will be read into
Adams View, one analysis for each block of output between the separators.
If you specify SEPARATOR=OFF the analysis information will be read into Adams View as a single
analysis. This allows you to plot or animate the analysis from beginning to end.
output_control 73
output_control set results
5. Adams uses a special format to output this information to the the initial conditions file so that a
subsequent simulation can be restarted at any time in the current simulation. When a subsequent
simulation is performed using the same data set, the mid-simulation conditions from the previous
analysis can be accessed and used as the initial conditions for the current analysis. Adams prompts the
user for the name of the initial conditions file if the ICSAVE parameter is set to ON. When a
simulation is restarted, Adams searches the initial conditions file for the time closest to the time
specified in the EXECUTION command, and then replaces the state vector in the model with that
from the initial conditions file. If ICSAVE=OFF is specified, Adams does not save initial conditions
in the initial conditions file.
6. ASCALE accepts two REAL numbers( r1, r2 ). Define r1 to scale the translational accelerations.
Define r2 to scale the rotational accelerations. These numbers are multiplied by the accelerations in
Adams, therefore, a scale factor between 0.0 and 1.0 scales the accelerations down, a scale factor
greater than 1.0 scales the accelerations up. Negative scale factors change the sign of the accelerations.
Both r1 and r2 default to 1.0.
Tips:
1. If your simulation has many output steps, or you have many requests and mrequests, specifying OFF
for print parameter will result in a much smaller Tabular Output File and conserve disk space.

RESULTS is used to create the results file. This all-purpose file can contain all the simulation output from
Adams. You can use the results file as an input file to Adams View. The results file may contain any
combination of system displacements, velocities, accelerations, forces, variables defined through user-
written differential equations, and user-written requests.
The results file can contain any combination of the following information:
 Displacements--Displacements of the LPRF with respect to ground and resolved in the ground
reference frame.
 Velocities--Velocities of the LPRF with respect to ground and resolved in the ground reference
frame.
 Accelerations--Accelerations of the LPRF with respect to ground and resolved in the ground
reference frame.
 Reaction forces--Forces on the I marker required to enforce each constraint, resolved in the ground
reference frame.
 Applied forces--Forces on the I marker applied by Adams force elements, resolved in the ground
reference frame.
 Differential equations--Values of the variables defined by the user-written differential equations
and their first derivatives with respect to time.
 User results--Values computed in the evaluation user-written subroutine REQSUB.
Description:

model_name Existing model Specifies the model to be modified. You use this parameter to
create_results_file On/Off Specifies whether or not Adams is to create a results file which
contains all simulation output from Adams. For more
information about the contents and format of the results file, see
Appendix F in the Adams View Reference file.
formatted On/Off Specifies that the results file is to be a formatted file. The default
is an unformatted (or binary) file. The formatted file is a
sequential ASCII text file, and the unformatted file is a direct
access binary file. You can understand a formatted file if you
write it to the screen or print it. An unformatted binary file will
read into a postprocessing program faster.
applied_forces On/off Specifies whether the results file is to include output from
applied_forces. ON indicates that the results file will include the
desired output. OFF indicates that the results file will not include
the applied_forces output.
displacements On/off Specifies whether the results file is to include output from part
displacements. ON indicates that the results file will include the
the part displacements output.
reaction_forces On/off Specifies whether the results file is to include output of
reaction_forces. ON indicates that the results file will include the
the reaction_forces output.
velocities On/off Specifies whether the results file is to include output from part
velocities. ON indicates that the results file will include the
the part velocity output.
data_structures On/off Specifies whether the results file is to include output from
data_elements. These elements include: curves, splines,
variables, arrays, matrices, plants, and strings. ON indicates that
the results file will include the desired output. OFF indicates that
the results file will not include the data_elements output.
output_control 75

system_elements On/off Specifies whether the results file is to include output from
system_elements. These elements include
LINEAR_STATE_EQUATIONs,
GENERAL_STATE_EQUATIONs, and
TRANSFER_FUNCTIONs. ON indicates that the results file
will include the desired output. OFF indicates that the results file
will not include the system_element output.
linear On/off Specifies whether the results file is to include output from an
Adams linear analysis. ON indicates that the results file will
include the desired output. OFF indicates that the results file will
not include the linear analysis output.
floating_markers On/off Specifies whether the results file is to include output from
floating_markers. ON indicates that the results file will include
the desired output. OFF indicates that the results file will not
include the floating_markers output.
comment String Specifies a comment for request, mrequest, madata, and results
entities.
accelerations On/off Specifies whether the results file is to include part accelerations.
associated with it.
2. The comment can contain up to 80 characters, and can be comprised of letters of the alphabet (a-z,
A-Z), numbers (0-9), and underscores. You may also use spaces and special characters (*&^%$#) if
Examples:
comment="Displacement of wheel center 1 wrt ground"
panel 1
panel set acf_twindow activate
panel
Activates a statement that was previously turned off by the DEACTIVATE command.
An ACTIVATE command, used in conjunction with the DEACTIVATE command, switches Adams
elements on and off. All Adams elements are active by default in the input dataset, but may be deactivated
using the DEACTIVATE command. For simulation purposes, when ADAMS activates a statement, the
statement appears as though it were always in the dataset. When Adams deactivates a statement, the
statement effectively disappears from the model. Both ACTIVATE and DEACTIVATE commands take
effect when the user issues the next SIMULATE command.
After the activation of any element, Adams reprocesses the model at the next SIMULATE command, as if it
had just been read in from the dataset. During the reprocessing Adams checks the entire model for
consistency, reinitializes user subroutines, and recomputes initial conditions.
When checking, Adams verifys that the model is still valid when the newly activated elements are included.
If, for example, an activated JOINT overconstrains a model resulting in an immobile system, Adams issues
an error message.
Adams also reinitializes all user subroutines to re-establish functional dependencies. For each element that
refers to a user-written subroutine, Adams calls the user-written subroutine with IFLAG set to true.
If the user activates a constraint or force in the middle of a simulation, by default Adams will split the Tabular
Output, Request, Graphics and Results output into two separate set of output concatenated together. This
ensures that the output correctly reflects the new system topology.
The OUTPUT/NOSEPARATOR argument will prevent Adams from splitting the file. This allows the user
to plot or animate the output continuously from the beginning to end, but may result in misleading graphics
during postprocessing.
Format:
beam_name = existing beam
bushing_name = existing bushing
field_name = existing field
jprim_name = existing jprim
motion_name = existing motion
sensor_name = existing sensor
single_component_force_name = existing single_component_force

spring_damper_name = existing spring damper
Example:
panel set acf_twindow activate &
panel set acf_twindow activate joint_name = joint_1
Description:

beam_name Existing beam Specifies an existing beam.
bushing_name Existing bushing Specifies an existing bushing.
field_name Existing field Specifies an existing field
joint_name Existing joint Specifies an existing joint.
jprim_name, Existing jprim Specifies an existing jrpim.
motion_name Existing motion Specifies an existing motion generator.
sensor_name Existing sensor Specifies an existing sensor
single_component_force_name Existing Specifies an existing single_component
single_component_force force
spring_damper_name Existing spring damper Specifies an existing spring damper
group_name Existing group Specifies an existing group.
1. You may identify a motion generator by typing its name or by picking it from the screen.
If the motion generator is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the motion generator is displayed.
If you created the motion generator by reading an Adams data set file, its name is the letters MOT
followed by the Adams data set ID number. The name of Adams MOTION/101 is MOT101, for
example. If you created the motion generator during preprocessing, you gave it a name at that time.
If a motion generator is available by default, you may identify it by entering its name only. If it is
not, you must enter its full name. To identify a motion generator under a model, for instance, you
may need to enter the model name as well. For example, you may specify motion generator 'servo'
in model 'links' by entering ".links.servo". If you type a "?", Adams View will list the motion
generators available by default.
You must separate multiple motion-generator names by commas.
panel 3
panel set acf_twindow deactivate
If the motion generator is visible in one of your views, you may identify it by picking on any of the
You need not separate multiple motion-generator picks by commas.

Turns off a statement that was previously turned on by the ACTIVATE command or was active by default
Format:
beam_name = an existing beam.
bushing_name = an existing bushing
field_name = an existing field
jprim_name = an existing primative joint
sensor_name = an existing sensor
single_component_force_name = an existing single-component force
spring_damper_name = an existing spring-damper force
Example:
panel set acf_twindow deactivate &
panel set acf_twindow deactivate beam_name = beam_1 &
panel set acf_twindow deactivate bushing_name = bushing_1 &
panel set acf_twindow deactivate field_name = field_1 &
panel set acf_twindow deactivate joint_name = joint_1 &
panel set acf_twindow deactivate sensor_name = sensor_1 &
panel set acf_twindow deactivate sensor_name = sensor_1 &
panel set acf_twindow deactivate group_name = group_1
Description:

beam_name An Existing Beam Specifies an existing beam.
bushing_name An Existing Bushing Specifies an existing bushing.
field_name An Existing Field Specifies an existing field which you
want information on
joint_name An Existing Joint Specifies an existing joint
jprim_name An Existing Primative Joint Specifies an existing jprim
motion_name An Existing Motion Specifies an existing motion generator.
sensor_name An Existing Sensor Specifies an existing sensor
single_component_force_name An Existing Single- Specifies an existing
component Force single_component_force
spring_damper_name An Existing Spring-damper Specifies an existing spring-damper
Force force
group_name An Existing Group Specifies an existing group
1. A DEACTIVATE command, used in conjunction with the ACTIVATE command, switches Adams
elements off and on. All Adams elements are active by default in the input dataset, but may be
deactivated using the DEACTIVATE command. For simulation purposes, when ADASMS activates
a statement, the statement appears as though it were always in the dataset. When Adams deactivates
a statement, the statement effectively disappears from the model. Both ACTIVATE and
DEACTIVATE commands take effect when the user issues the next SIMULATE command. Once
deactivated, a statement remains inactive until it is activated using the ACTIVATE command.
After the deactivation of any element, Adams reprocesses the model at the next SIMULATE
command, as if it had just been read in from the dataset. During the reprocessing Adams checks the
entire model for consistency, reinitializes user subroutines, and recomputes initial conditions.
When checking, Adams examines all active-element function expressions and arguments for
references to inactive elements. If an active force, constraint or sensor refers to an inactive element,
Adams issues an error message just as if the inactive element did not exist. If a force REGUEST or a
force GRAPHIC refers to an inactive element, Adams reports zero forces for the inactive element.
Adams also reinitializes all user subroutines to re-establish functional dependencies. For each element
that refers to a user-written subroutine, Adams calls the user-written subroutine with IFLAG set to
true.
Adams reports zero values in all output files for any forces associated with inactive elements, including
both applied forces and joint reaction forces. This includes requests, force graphics, and forces in the
results file.
panel 5
AdamsAdams continues to report displacements, velocities, and accelerations for all JOINT and
JPRIM MREQUESTs, even for JOINTs and JPRIMs that have been deactivated. MREQUEST
create displacements, velocities and accelerations requests for the markers associated with the specified
JOINTs and JPRIMs. Adams continues to output the relative marker displacements velocities and
accelerations even if the user has deactivated the original JOINT or JPRIM.
If the user deactivates a constraint or force in the middle of a simulation, by default Adams will split
the Tabular Output, Request, Graphics and Results output into two separate set of output
concatenated together. This ensures that the output correctly reflects the new system topology.
The OUTPUT/NOSEPARATOR argument will prevent Adams from splitting the file. This allows
the user to plot or animate the output continuously from the beginning to end, but may result in
misleading graphics during postprocessing.
2. You may identify a beam by typing its name or by picking it from the screen.
If the beam is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the beam is displayed.
If you created the beam by reading an Adams data set or graphics file, the beam name is the letters
BEA followed by the Adams data set beam ID number. The name of AdamsAdams BEAM/101 is
BEA101, for example. If you created the beam during preprocessing, you gave it a name at that time.
If a beam is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a beam under a different model, for instance, you may need to enter
the model name as well. For example, you may specify beam 101 from the model named test by
entering ".test.bea101". If you type a "?", Adams View will list the beams available by default.
3. You may identify a bushing by typing its name or by picking it from the screen.
If the bushing is not visible on the screen, you must type the name. You may also find it convenient
to type the name even if the bushing is displayed.
If you created the bushing by reading an Adams data set or graphics file, the bushing name is the
letters BUS followed by the Adams data set bushing ID number. The name of Adams
BUSHING/101 is BUS101, for example. If you created the bushing during preprocessing, you gave
If a bushing is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a bushing under a different model, for instance, you may need
to enter the model name as well. For example, you may specify bushing 'lower_front' from model
'sla' by entering ".sla.lower_front". If you type a "?", Adams View will list the bushings available by
default.
4. You may identify a field by typing its name or by picking it from the screen.
If the field is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the field is displayed.
If you created the field by reading an Adams data set file, the field name is 'FIE'. If you created the
field during preprocessing, you gave it a name at that time.
If a field is available by default, you may identify it by entering its name only. If it is not, you must
".robot.fld1". If you type a "?", Adams View will list the fields available by default.
followed by the AdamsAdams data set joint ID number. The name of Adams JOINT/101 is JOI101,
for example. If you created the joint during preprocessing, you gave it a name at that time.
6. You may identify a jprim by typing its name or by picking it from the screen.
If the jprim is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the jprim is displayed.
If you created the jprim by reading an Adams data set or graphics file, the jprim name is the letters
JPR followed by the Adams data set jprim ID number. The name of Adams JPRIM/101 is JPR101,
for example. If you created the jprim during preprocessing, you gave it a name at that time.
If a jprim is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a jprim under an analysis, for instance, you may need to enter the
analysis name as well. For example, you may specify jprim 101 from the analysis named test by
entering ".test.jpr101". If you type a "?", Adams View will list the jprims available by default.
panel 7
by the Adams data set sensor ID number. The name of Adams SENSOR/101 is SEN101, for
example. If you created the sensor during preprocessing, you gave it a name at that time.
If a sensor is owned by the default model, you may identify it by entering its name only. If it is not,
a "?", AdamsAdams View will list the single-component forces available by default.
10. You may identify a spring-damper force by typing its name or by picking it from the screen.
If the spring-damper force is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the spring-damper is displayed.
If you created the spring-damper force by reading an AdamsAdams data set, the spring-damper name
is the letters SPR followed by the Adams data set spring-damper ID number. The name of Adams
SPRINGDAMPER/101 is SPR101, for example. If you created the spring-damper during
If a spring-damper is available by default, you may identify it by entering its name only. If it is not,
you must enter its full name. To identify a spring-damper under a different model, for instance, you
may need to enter the model name as well. For example, you may specify spring-damper 'left' from
model 'sla' by entering ".sla.left". If you type a "?", Adams View will list the spring-dampers available
by default.
Cautions:
1. You must separate multiple beam names by commas.
2. You must separate multiple single-component force names by commas.
3. You must separate multiple spring-damper names by commas.
panel set acf_twindow dynamic_simulation
4. You must separate multiple group names by commas.

5. You must separate multiple bushing names by commas.
6. You must separate multiple joint names by commas.
7. You must separate multiple field names by commas.
8. You must separate multiple jprim names by commas
9. You must separate multiple motion-generator names by commas.
10. You must separate multiple sensor names by commas.
Tips:
1. If the beam is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple beam picks by commas.
3. If the single-component force is visible in one of your views, you may identify it by picking on any of
the graphics associated with it
4. You need not separate multiple single-component force picks by commas
5. If the spring-damper is visible in one of your views, you may identify it by picking on any of the

Specifies the type of analysis you want Adams to perform is dynamic.
The DYNAMIC_SIMULATION command specifies that Adams is to integrate the dynamics equations. If
you request a dynamic analysis for a model with zero degrees of freedom, Adams issues a warning message
and integrates the equations instead of using kinematic analysis.
Kinematic analysis is faster.
You may use the 'MODEL VERIFY' command to display the number of degrees-of-freedom in your model.
Format:
number_of_steps = integer
step_size = real
end_time = real
duration = real
panel 9
panel set acf_twindow eigen_solution_calculation
Example:
panel set acf_twindow dynamic_simulation &
end_time = 5.0
Description:

number_of_steps Integer Specifies the number of values to be stored in each
component of a result set being read from a file.
step_size Real Specifies the size of the output step for a dynamic,
kinematic, or quasi-static equilibrium analysis in
model time units. STEP_SIZE must be greater than
zero.
end_time Real Specifies the end time for a dynamic, kinematic, or
quasi-static equilibrium analysis.
duration real Specifies the duration for a dynamic, kinematic, or
quasi-static equilibrium analysis in model time units.
The DURATION must be greater than zero.
If the parameter “number_of_steps” is not specified the size of the components will be inferred from
the format of the file. A component will be read from a file until a comment line is encountered.
This commented line marks the end of the component.
2. The parameter END_TIME must be greater than the begin time. Since the begin time must be
greater than zero, this means that the end time must also be greater that zero.

Specifies that you want Adams linearize the model about an operating point by performing an eigen solution
analysis.
To linearize and Adams model about an operating point, the Adams model should first be placed in the
configuration by performing and STATIC_SIMULATION or an TRANSIENT_SIMULATION. Then the
EIGEN_SOLUTION_CALCULATION can be performed to provide the eigen value and eigen vectors
associated to the linear system derived from the model at the operating point.
Specifying the DAMPING parameter as NO means that the velocity dependent terms in forces and
VARIABLEs are not included in the stiffness (K) and mass (M) matrices.
Specifying the VECTORS parameter as NO means that no eigenvectors (i.e. mode shapes) will be computed.
Only eigenvalues will be reported.
Format:
damping = yes/no
no_eigen_vectors = true_only
coordinates_of_modes = integer
energy_of_modes = integer
dissipative_energy = integer
kinetic_energy = integer
strain_energy = integer
Example:
panel set acf_twindow eigen_solution_calculation &
damping = yes &
no_eigen_vectors = true
Description:

Damping Yes/No Specifies if damping is to be included in the eigen
solution analysis
no_eigen_vectors True Specifying the NO_EIGEN_VECTORS parameter
indicates to Adams that the eigen solution analysis is
to be performed without computation of mode
shapes (eigenvectors). Only the eigenvalues will be
reported.
coordinates_of_modes Integer This parameter is used to specify the mode numbers
for which a table of mode shape coordinates will be
output to the Adams output file.
energy_of_modes Integer This parameter is used to specify the mode numbers
for which a table of modal energy distribution will be
panel 11
panel set acf_twindow generate_state_matrix

dissipative_energy Integer This parameter is used to specify the mode numbers
for which a table of disspative energy distribution will
be output to the Adams output file.
kinetic_energy Integer This parameter is used to specify the mode numbers
for which a table of kinetic energy distribution will be
strain_energy Integer This parameter is used to specify the mode numbers
for which a table of strain energy distribution will be
1. Specifying the DAMPING parameter as NO means that the velocity dependent terms in forces and
VARIABLEs are not included in the stiffness (K) and mass (M) matrices.
2. The “coordinates_of_modes”, ”dissipative_energy”,”strain_energy”,”kinetic_energy” and
“energy_of_modes” parameter accepts either one (1) value or two (2) values separated by a comma
(,). The values are mode shape numbers, and must be greater than zero. Two values are given to
specify a range of mode shape numbers. One value is given to specify a single mode shape number.

Specifies that you want linearize the model and generate a state matrix representation of the linearized
model.
To linearize and model about an operating point, the model should first be placed in the configuration by
performing and STATIC_SIMULATION or an TRANSIENT_SIMULATION. Then the
GENERATE_STATE_MATRIX command can provide the the state matrices. The representation of the
linear system is:
xdot = Ax + Bu
y = Cx + Dy
where x is the states of the plant model, u is the inputs to the plant model, y is the outputs from the plant
model, and A, B, C, and D are the state matrices representing the plant. These are the matrices that are
reported to the you.
You specify the plant inputs and outputs using the PLANT_INPUT_NAME and
PLANT_OUTPUT_NAME parameters. Plant state are automatically determined by and result in the best
numerical conditioning of the state matrices. Only one PLANT_INPUT_NAME and
PLANT_OUTPUT_NAME can be specified for each GENERATE_STATE_MATRIX command.
The state matrices can be output in either MATRIX_X format or MATLAB format through the use or the
MATRIX_FORMAT parameter.
The FILE_NAME parameter tells the name of the file the you want the state matrices written to. For
MatrixX all the matrices are written to the file named in this parameter. For the MATLAB format the
specified name is used as the base name and all matrices are written to separate files named with each matrix
name appended to the name specified in this parameter.
Format:
file_name = string
matrix_format = matrix_format
plant_input_name = existing pinput
plant_output_name = existing poutput
plant_state_name = existing pstate
Description:

File_name String Specifies the name of the file that the state matrices
are to be written to.
Matrix_format Matrix_x/matlab Specifies the state matrices will be output in either
MATRIX_X format or MATLAB format.
Plant_input_name Existing pinput Specifies an existing plant_input.
Plant_output_name Existing poutput Specifies an existing plant_output.
Plant_state_name Existing plant state Specifies an existing plant state.
Reference_marker Existing marker Specify a marker that will serve as the reference.
1. The state matrices can be output in either MATRIX_X format or MATLAB format through the use
or the MATRIX_FORMAT parameter.
2. The FILE_NAME parameter tells the name of the file the you want the state matrices written to.
For MatrixX all the matrices are written to the file named in this parameter. For the MATLAB format
the specified name is used as the base name and all matrices are written to separate files named with
each matrix name appended to the name specified in this parameter.
3. You may identify a plant_input by typing its name or by picking it from the screen.
Since plant_input do not have a geometric position, /View displays plant_input icons at or near the
model origin. If the plant_input icon is not visible on the screen, you must type the name. You may
also find it convenient to type the name even if the plant_input icon is displayed.
panel 13
panel set acf_twindow kinematic_simulation
If you created the plant_input by reading an data set or graphics file, the plant_input name is the
letters PIN followed by the data set plant_input ID number. The name of PINPUT/101 is PIN101,
for example. If you created the plant_input during preprocessing, you gave it a name at that time.
If a plant_input is owned by the default model, you may identify it by entering its name only. If it is
not, you must enter its full name. To identify a plant_input under a different model, for instance, you
may need to enter the model name as well. For example, you may specify plant_input
'velocity_set_point' from model 'motor' by entering ".motor.velocity_set_point'". If you type a "?",
/View will list the plant_input elements available by default.
You must separate multiple plant_input names by commas.
If the plant_input is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple plant_input picks by commas.
4. You may identify a plant_output by typing its name or by picking it from the screen.
Since plant_output do not have a geometric position, /View displays plant_output icons at or near
the model origin. If the plant_output icon is not visible on the screen, you must type the name. You
may also find it convenient to type the name even if the plant_output icon is displayed.
If you created the plant_output by reading an data set or graphics file, the plant_output name is the
letters "POU" followed by the data set plant_output ID number. The name of POUTPUT/101 is
POU101, for example. If you created the plant_output during preprocessing, you gave it a name at
that time.
If a plant_output is owned by the default model, you may identify it by entering its name only. If it
is not, you must enter its full name. To identify a plant_output under a different model, for instance,
you may need to enter the model name as well. For example, you may specify plant_output
'actual_velocity' from model 'motor' by entering ".motor.actual_velocity'". If you type a "?", /View
will list the plant_output available by default.
You must separate multiple plant_output names by commas.
If the plant_output is visible in one of your views, you may identify it by picking on any of the
You need not separate multiple plant_output picks by commas.
panel set acf_twindow kinematic_simulation

Specifies the type of analysis you want Adams to perform is kinematic.
The KINEMATIC_SIMULATION command specifies that Adams is to run a kinematic analysis. If you
request a kinematic analysis for a model with one or more degrees of freedom, Adams issues an error message
and ignores the entire command.
panel set acf_twindow output_file_separator
Format:
Panel set acf_twindow kinematic_simulation
step_size = real
end_time = real
duration = real
Example:
panel set acf_twindow kinematic_simulation &
end_time = 5.0
Description:

kinematic, or quasi-static equilibrium analysis in model
time units. STEP_SIZE must be greater than zero.
duration real Specifies the duration for a dynamic, kinematic, or quasi-
static equilibrium analysis in model time units. The
DURATION must be greater than zero.
the format of the file. A component will be read from a file until a comment line is encountered. This
commented line marks the end of the component.

Specifies if Adams is to write delimiting lines to the Request, Results, Graphics, and Tabular Output files
when the user modifies the model topology in the middle of of a simulation.
panel 15
panel set acf_twindow reload
Format:
separator = on_off
Example:
panel set acf_twindow output_file_separator &
panel set acf_twindow output_file_separator separator = on
Description:

separator ON_OFF Specifies whether or not Adams will write separators to the
Request, Graphics, Results, and Tabular Output Files when
you modify the model topology in the middle of a
simulation.
1. You can change the model topology by adding Adams commands to your ACF file to activate an
element, deactivate an element, change a marker position, or change the type or point of application
of a force or constraint during a simulation.
If you specify SEPARATOR=ON (this is the default) the analysis information will be read into
AdamsAdams View, one analysis for each block of output between the separators.
If you specify SEPARATOR=OFF the analysis information will be read into Adams View as a single
analysis. This allow you to plot or animate the analysis from beginning to end.
Tips:
1. The default is to write the separator.

Restart a simulation from a previously saved model or simulation state.
Format:
save_type = adams_save_type
file_name = string
output_prefix = string
title = string
Example:
panel set acf_twindow reload &
panel set acf_twindow save save_type = system &
panel set acf_twindow save file_name = "c:\users\save"
Description:

save_type ADAMS_SAVE_TYPE Specifies the type of file to be SAVEd or RELOADed
file_name STRING Specifies the name of the file that is to be read, written,
or executed.
output_prefix STRING Specifies a new base (root) name for the output files
(.REQ, .RES, .GRA, .OUT, etc.) from the simulation
which follows this RELOAD command.
title STRING This parameter allows the specification of the XY plot
title.
1. Using the reload command with the STATES argument allows the user to reload the saved simulation
time and state values, including displacements, velocities, force values and user-defined variable
values. Adams resets the simulation time to the saved values and uses the saved states as initial
conditions for the next simulation.
Using the RELOAD command with the SYSTEM argument allows the user to reload the entire saved
system, including the model definition (parts, markers, joints, etc.), simulation time and state values
(displacements, velocities, force values, user-defined variable values, etc.) and solver data (integrator
parameters, state derivatives, etc.). Adams completely resets all model, simulation and solver data to
that stored in the file.
SAVE_TYPE=STATES respecifies that the file contains simulation time and state values
(displacements, velocities, force values user-defined variable values, etc.).
2. SAVE_TYPE=SYSTEM respecifies that the file contains the entire Adams system, including the
model, simulation time, and state_values.
4. If the user does not specify the OUTPUT_PREFIX argument, Adams will append the output to the
currently open output files after writing a special delimiter line into the file.
panel 17
panel set acf_twindow save
5. This parameter allows the specification of the XY plot title. The title is a "quoted" character string
that will be displayed at the top of the XY plot. The title will be scaled and centered automatically.
Unlike plot names, titles need not be unique.
A title may be arbitrarily long and a combination of letters of the alphabet and numbers may be used.

A save command stores the current AdamsAdams model and simulation conditions or only the current
simulation states
Format:
save_type = adams_save_type
file_name = string
autosave = integer
Example:
panel set acf_twindow save &
panel set acf_twindow save save_type = system&
panel set acf_twindow save file_name = "c:\users\save"&
panel set acf_twindow save autosave = 2
Description:

save_type ADAMS_SAVE_TYPE Specifies the type of file to be SAVEd or RELOADed.
file_name STRING Specifies the name of the file that is to be read, written,
or executed.
autosave INTEGER Indicates that Adams is to save the simulation states
every i output steps.
1. A save command stores the current Adams model and simulation conditions or only the current
simulation states. This allows the user to return to the model or states at a later time using the
RELOAD command.
panel set acf_twindow static_simulation
The user may use the SAVE command with the STATES argument to save the current simulation
time and state values, including displacements, velocities, force values, and user-defined variable
values. The user can later restart a simulation from this point by reloading the states with the
RELOAD/STATES command. When the user reload this file, Adams resets the simulation time to
the saved value and use the saved states as initial conditions for the next simulation.
The user may use the SAVE command with the SYSTEM argument to save the entire current system,
including the model definition (parts, markers, joints, etc.), simulation time and state values
(displacements, velocities, force values, and user-defined variable values etc.), and solver data
(integrator parameters, state derivatives, etc.). SAVE/SYSTEM creats a complete record of the
current model and simulation conditions. The user can later return to this point by reloading the
conditions using the RELOAD/SYSTEM command. When the user reloads a system file, Adams
completely reset the model, simulation and solver data to that stored in the file.
2. SAVE_TYPE=STATES respecifies that the file contains simulation time and state values
(displacements, velocities, force values user-defined variable values, etc.).
SAVE_TYPE=SYSTEM respecifies that the file contains the entire Adams system, including the
model, simulation time, and state_values.
4. Each subsequent SAVE command overrides the previous case. Setting AUTOSAVE to zero turns
AUTOSAVE off.

Specifies the type of analysis you want Adams to perform is static.
The STATIC_SIMULATION command specifies that Adams is to run either a static equilibrium analysis or
a quasi-static equilibrium analysis. If you choose STATIC_SIMULATION and fail to specify an
END_TIME, or NUMBER_OF_STEPS, Adams performs a static equilibrium analysis at the current time.
If you use choose STATIC_SIMULATION and specify an end time and one or more steps, Adams performs
a quasi- static equilibrium analysis.
Format:
step_size = real
end_time = real
duration = real
panel 19
panel set acf_window transient_simulation
Example:
panel set acf_twindow static_simulation &
end_time = 5.0
Description:

panel set acf_window transient_simulation

Specifies the type of analysis you want Adams to perform is transient.
The TRANSIENT_SIMULATION command specifies that Adams is to run a kinematic analysis if the
model has zero degrees of freedom, or a dynamic analysis if the system has one or more degrees of freedom.
panel set twindow_function akima_spline
Format:
Panel set acf_window transient_simulation
step_size = real
end_time = real
duration = real
Example:
panel set acf_twindow transient_simulation &
end_time = 5.0
Description:


The AKIMA_SPLINE function uses the AKIMA method of interpolation to create a spline function across
a set of data points.
panel 21
Format:
x = function
z = function
derivative_order = integer
Example:
panel set twindow_function akima_spline &
panel set twindow_function cubic_spline spline_name = spline_1 &
panel set twindow_function cubic_spline derivative_order = 2
Description:

x FUNCTION Specifies the real variable that is the independent
variable value along the x-axis of the spline.
z FUNCTION Specifies a real variable that is the second independent
variable value along the z-axis of the surface being
interpolated
spline_name AN EXISTING Specifies an existing spline
SPLINE
derivative_order INTEGER An optional integer that specifies the order of the
derivative at the interpolate value to be returned by
CUBSPL.
Range: 0 < iord < 2
1. The data points to be interpolated are defined in the SPLINE element in your Adams model. The
SPLINE that you define may represent a curve ( x-y points) or a surface (x-y-z points). Interpolation
in the y direction is cubic, and interpolation in the z direction is linear.
The AKIMA_SPLINE function is very fast, since it uses local methods. It always produces good
results for the value of the function being approximated. The AKIMA_SPLINE returns good
estimates for the first derivative of the approximated function when the data points are evenly spaced.
In instances where the data points are unevenly spaced, the estimate of the first derivative may be in
error. In all cases, the second derivative of the function being approximated is unreliable.
2. This variable can be any value of interest that you can compute using a function expression.
To enter a function expression you enter a series of quoted strings.

verification.
summerized in the following table.
Components Examples
NUMBERS FUNCTION = 1E2 + 3.4 + 6
OPERATORS FUNCTION = 3*6/2 + 3 - 2**2
SYSTEM CONSTANTS FUNCTION = PI + 20
SYSTEM VARIABLES FUNCTION = AX(1040, 2010)
ARITHMETIC IFS FUNCTION = IF(DX(3, 5): -1, 0, 1)
FORTRAN-77 FUNCTIONS FUNCTION = ABS(NUM) - 6
BLANKS FUNCTION = 1 + 2
CONTINUATION COMMAS FUNCTION = 1 + 1 + 1 + 1 + 1 + 1 , + 1 + 1 + 1 + 1 + 1 + 1 + 1
Adams FUNCTIONS FUNCTION = POLY(0, 0, 6.28)
NUMBERS
FUNCTION expressions can include integers, real numbers, and exponents. In other words, all
OPERATORS
• From the greatest to the least, the operators have the following priorities. ** then * / then + -. In
other words, Adams executes exponentiation (**) before all other operators and executes
SYSTEM CONSTANTS
panel 23

BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
SYSTEM VARIABLES
ARITHMETIC IFS
follows:
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
be accessed.
Names Purposes
AKISPL Accesses the data in a SPLINE statement and uses the Akima cubic method to fit a
CUBSPL Accesses the data in a SPLINE statement and uses the traditional cubic method to fit
panel 25
Names Purposes
3. If the SPLINE defines only one curve, Adams ignores this parameter.
verification.
Components Examples
NUMBERS
OPERATORS
SYSTEM CONSTANTS
BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
panel 27
SYSTEM VARIABLES
ARITHMETIC IFS
follows:
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
be accessed.
panel set twindow_function ax
Names Purposes
spline name is the letters SPL followed by the Adams data set spline ID number. The name of Adams
SPLINE/101 is SPL101, for example. If you created the spline during preprocessing, you gave it a
name at that time.
If a spline is available by default, you may identify it by entering its name only. If it is not, you must
Cautions:
1. You must separate multiple spline names by commas.

The AX function returns the rotational displacement of the I_MARKER (i1) about the x-axis of the
J_MARKER (i2). This value is computed as follows: Assuming that rotations about the other two axes (y-,
z-axes) of marker i2 are zero, then, AX is the angle between the two y-axes (or the two z-axes).
Mathematically, AX is calculated as:
AX = ATAN2 ((dot_product_of yi1 zi2),(dot_product_of yi1 yi2))
where yi1 is the y-axis of marker i1, yi2 is the y-axis of marker i2, and zi2 is the z-axis of marker i2.
This type of measurement is also referred to as "shadow angles".
panel 29
Format:
Example:
panel set twindow_function ax &
Description:

I_marker_name Existing Marker Specifies an existing marker used as the I_MARKER
(i1) in the evaluation of the function.
J_marker_name Existing Marker Specifies an existing marker used as the J_MARKER
name at that time.
panel set twindow_function ay

The AY function returns the rotational displacement of the I_MARKER (i1) about the y-axis of the
J_MARKER (i2). This value is computed as follows: Assuming that rotations about the other two axes (x-,
z-axes) of marker i2 are zero. Then AY is the angle between the two x-axes (or the two z-axes).
Mathematically, AY is calculated as:
AY = ATAN2 ((dot_product_of zi1 xi2),(dot_product_of zi1 zi2))
where zi1 is the z-axis of marker i1, xi2 is the x-axis of marker i2, and zi2 is the z-axis of marker i2.
Format:
Example:
panel set twindow_function ay &
Description:

I_marker_name Existing marker Specifies an existing marker used as the I_MARKER
J_marker_name Existing marker Specifies an existing marker used as the J_MARKER
name at that time.
panel 31
panel set twindow_function az

The AZ function returns the rotational displacement of the I_MARKER (i1) about the z-axis of the
J_MARKER (i2). This value is computed as follows: Assume that rotations about the other two axes (x-, y-
axes) of marker i2 are zero. Then AZ is the angle between the two x-axes (or the two y-axes). Mathematically,
AZ is calculated as:
AZ = ATAN2 ((dot_product_of xi1 yi2),(dot_product_of xi1 xi2))
where xi1 is the x-axis of marker i1, xi2 is the x-axis of marker i2, and yi2 is the y-axis of marker i2.
Format:
Example:
panel set twindow_function az &
Description:

I_marker_name Existing Marker Specifies an existing marker used as the I_MARKER (i1)
in the evaluation of the function.
J_marker_name Existing Marker Specifies an existing marker used as the J_MARKER (i2)
in the evaluation of the function.
panel set twindow_function b_spline
name at that time.

Format:
alpha = function
component = curve_component
Example:
panel set twindow_function b_spline &
panel set twindow_function b_spline curve_name = curve_1 &
panel set twindow_function b_spline derivative_order = 2 &
panel set twindow_function b_spline component = x
panel 33
Description:

curve_name An Existing Acurve A curve name is string of characters that identifies a
curve
alpha Function A real variable that identifies the value of the
independent parameter, , at which the CURVE
function evaluates the curve.
derivative_order Integer Order of the derivative that you want returned from
the curve.
component Curve_component An integer variable that specifies the component that
the CURVE function returns
1. Curve names are assigned by the user when curves are created. After a curve has been created, it may
be referenced by its name until it is deleted. A curve may not have the same name as another curve
on the same plot. A curve is associated to a plot and may be referenced at any time with respect to
the plot. For example, a curve named "c1" on plot "p1" may be referenced by the full specification
of ".p1.c1". This type of full name specification avoids the need to force a given plot to be the
"current" or "default" to reference data (i.e. a curve) associated with it. This is very useful when
copying a curve from one plot to another, etc.
A curve_name may be arbitrarily long and a combination of letters of the alphabet and numbers may
2. If the curve is a B-spline computed by the CURVE statement, alpha must be in the domain -1 <
<1
3. The legal values are:
1 - returns the x coordinate or derivative
2 - returns the y coordinate or derivative
3 - returns the z coordinate or derivative
4. An integer variable that specifies the component that the CURVE function returns. The legal values
are:
1 - returns the x coordinate or derivative
2 - returns the y coordinate or derivative
3 - returns the z coordinate or derivative
Parameters iord and icomp together allow you to request any one of the following nine return values:
panel set twindow_function beam

The BEAM function returns the COMPONENT of a force due to BEAM you identify in the
BEAM_NAME parameter.
The force or torque is calculated in the coordinate system of the REFERENCE_MARKER. If the
RETURN_VALUE_ON_MARKER parameter is set to "i", the value returned is the force or torque acting
on the I_MARKER of the force/torque generating element. If the RETURN_VALUE_ON_MARKER
parameter is set to "j", the value returned is the one acting on the J_MARKER. If the
REFERENCE_MARKER is not specified, the results are with respect to the ground coordinate system.
Format:
beam_name = existing beam
return_value_on_marker = marker_type
component = all_components
Description:

beam_name Existing beam Specifies an existing beam.
panel 35

return_value_on_mar Marker_type Specifies for which marker on the force
ker element (i or j) the function will return force
values.
component FM, FX, FY, FZ, TM, TX, TY, Specifies the specific COMPONENT of force
TZ or torque that the function is to return for the
force element.
reference_marker Existing Marker Specifies a marker that provides a reference
coordinate system for the function.
1. You may identify a beam by typing its name or by picking it from the screen.
If the beam is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the beam is displayed.
If you created the beam by reading an ADAM data set or graphics file, the beam name is the letters
BEA followed by the Adams data set beam ID number. For example, the name of Adams BEAM/101
is BEA101. If you created the beam during preprocessing, you will have given it a name at that time.
If a beam is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a beam under a different model, for instance, you may need to enter
the model name as well. For example, you may specify beam 101 from the model named test by
entering ".test.bea101". If you type a "?", Adams View will list the beams available by default.
You must separate multiple beam names by commas.
If the beam is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple beam picks by commas.
2. The force or torque is calculated in the coordinate system of the REFERENCE_MARKER. If the
RETURN_VALUE_ON_MARKER parameter is set to "i", the value returned is the force or torque
acting on the I_MARKER of the force/torque generating element. If
RETURN_VALUE_ON_MARKER parameter is set to "j", the value returned is that acting on the
J_MARKER. If the REFERENCE_MARKER is not specified, the results are with respect to the
ground coordinate system.
3. The value for the COMPONENT parameter is one of fm, fx, fy, fz, tm, tx, ty, or tz.
acting on the I_MARKER of the force/torque generating element. If the
J_MARKER. If the REFERENCE_MARKER is not specified the results are with respect to the
panel set twindow_function bistop_slot

The BISTOP_SLOT function models a gap element.
Format:
x = function
dx = function
lower_bound = real
upper_bound = real
boundary_penetration = real
angular_lower_bound = angle
angular_upper_bound = angle
angular_boundary_penetration = angle
stiffness = real
force_exponent = real
max_damping_coefficient = real
Example:
panel set twindow_function bistop_slot &
panel set twindow_function bistop_slot lower_bound = 5 &
panel set twindow_function bistop_slot angular_lower_bound = 58 &
panel set twindow_function bistop_slot angular_boundary_penetration = 10 &
panel set twindow_function bistop_slot max_damping_coefficient = 3
Description:

x Function Specifies a real variable that is the
distance variable you want to use to
compute the force.
dx Function Specifies a real variable that
communicates the time derivative
of x to the function
lower_bound Real Specifies a real variable that is the
non-angular lower bound of x.
panel 37

upper_bound Real A real variable that specifies the
non-angular upper bound of the
independent variable x.
boundary_penetration Real Specifies a positive real variable
that is the non-angular boundary
penetration at which Adams
applies full damping.
angular_lower_bound Angle Specifies a real variable that is the
angular lower bound of x.
angular_upper_bound Angle A real variable that specifies the
angular upper bound of the
independent variable x
angular_boundary_penetration Angle Specifies a positive real variable that
is the angular boundary
penetration at which Adams
stiffness Real A non-negative real variable that
specifies the stiffness of boundary
surface interaction.
force_exponent Real Specifies a positive real variable that
is the exponent of the force
deformation characteristic.
max_damping_coefficient Real Specifies a non-negative real
variable that is the maximum
damping coefficient
1. The gap element essentially consists of a slot which defines the domain of motion of a Part located in
the slot. As long as the Part is located in the slot between the LOWER_BOUND (i.e. x1) and the
UPPER_BOUND (i.e. x2), and has no interference with the ends of the slot, it is free to move, and
no forces act on the Part. When the Part tries to move beyond the physical definition of the slot,
impact forces representing contact are created by the BISTOP_SLOT function. The force created
tends to move the floating Part back into the slot.
The BISTOP_SLOT force, which you define, has two components, a spring or STIFFNESS
component and a damping or viscous component. The STIFFNESS component (i.e. k) with the
FORCE_EXPONENT (i.e. e) is dependent on the penetration of the floating part beyond the gap
or slot into the restricting part, The damping or viscous component may be used to model energy loss.
To prevent a discontinuity in the damping force at zero penetration, the damping coefficient is
defined as a cubic step function of the penetration. Thus at zero penetration, the damping coefficient
is always zero. The damping coefficient achieves a maximum, MAX_DAMPING_COEFFICIENT
(i.e. cmax), at a user-defined penetration, BOUNDARY_PENETRATION (i.e. d). Even though the
points of contact between the floating part and the restricting part may change as the system moves,
Adams always exerts the force between the I and the J markers.
The equation for this function can be mathematically expressed as follows:
| k*(x1-x)**e - STEP(x,x1-d,cmax,x1,0)*x' when x < x1 |
BISTOP = < 0 when x1 <= x <= x2
>
|-k*(x-x2)**e - STEP(x,x2,0,x2+d,cmax)*x' when x > x2 |
2. You compute x value using a function expression. For example, if the user wants to use the x
displacement of marker MAR0201 with respect to MAR0301, then x is DX(MAR0201,MAR0301).
verification.
Components Examples
NUMBERS
panel 39
OPERATORS
From greatest to least, the operators have the following
• priorities. ** then * / then + -. In other words, Adams
• executes exponentiation (**) before all other operators and
• executes multiplication (*) and division (/) before addition
• (+) and subtraction (-).
You can use parentheses to alter the precedence of operators.
SYSTEM CONSTANTS
BLANKS
Adams does not accept a blank space between a function and its left bracket. (This is true for both
CONTINUATION COMMAS
FUNCTION BUILDER
SYSTEM VARIABLES
ARITHMETIC IFS
follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
a FORTRAN reference manual.
Invoke the text edit window and pick the FUNCTIONS button to ge a list of functions that can be
accessed.
panel 41
Adams FUNCTIONS
Invoke the text edit window and pick the FUNCTIONS button to get a list of functions that can be
accessed.
Names Purposes
AKISPL Accesses the data in a SPLINE statement and uses the Akima cubic
directions.
CHEBY Evaluates a Chebyshev polynomial.
FORCOS Evaluates a Fourier cosine series.
FORSIN Evaluates a Fourier sine series.
IMPACT | Evaluates a force restricting displacement of a part in one direction.
You compute this value using a function expression. For example, if x (the distance variable you use
to compute the force) is compute using the distance function DX(0201,0301) then, dx is computed
using the velocity function VX(0201,0301).
verification.
Components Examples
NUMBERS
OPERATORS
• priorities. ** then * / then + -. In other words, Adams
• executes exponentiation (**) before all other operators and
• executes multiplication (*) and division (/) before addition
• (+) and subtraction (-).
SYSTEM CONSTANTS
panel 43
BLANKS
Adams does not accept a blank space between a function and its left bracket. (This is true for both
CONTINUATION COMMAS
FUNCTION BUILDER
SYSTEM VARIABLES
ARITHMETIC IFS
follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
accessed.
Adams FUNCTIONS
accessed.
Names Purposes
AKISPL Accesses the data in a SPLINE statement and uses the Akima cubic
directions.
CHEBY Evaluates a Chebyshev polynomial.
method to fit acubic curve (a spline) to the data.
FORCOS Evaluates a Fourier cosine series.
FORSIN Evaluates a Fourier sine series.
IMPACT | Evaluates a force restricting displacement of a part in one direction.
panel 45
If x is less than LOWER_BOUND, Adams calculates a positive value for the force. The value of
LOWER_BOUND must be less than the value of UPPER_BOUND. The LOWER_BOUND
parameter is given as "x1" in the BISTOP_SLOT equation below.
3. If x is greater than UPPER_BOUND, Adams calculates a negative value for the force. The value of
UPPER_BOUND must be greater than the value of LOWER_BOUND. The UPPER_BOUND
parameter is given as "x2" in the BISTOP_SLOT equation below.
4. The BOUNDARY_PENETRATION parameter is given as "d" in the BISTOP_SLOT and
IMPACT equations below.
IMPACT = < >
| 0 when x >= x1 |
5. If x is less than ANGULAR_LOWER_BOUND, Adams calculates a positive value for the force. The
value of ANGULAR_LOWER_BOUND must be less than the value of
ANGULAR_UPPER_BOUND. The ANGULAR_LOWER_BOUND parameter is given as "x1"
in the BISTOP_SLOT equation below.
6. If x is greater than ANGULAR_UPPER_BOUND, Adams calculates a negative value for the force.
The value of ANGULAR_UPPER_BOUND must be greater than the value of
ANGULAR_LOWER_BOUND. The ANGULAR_UPPER_BOUND parameter is given as "x2"
in the BISTOP_SLOT equation below.
7. The ANGULAR_BOUNDARY_PENETRATION parameter is given as "d" in the BISTOP_SLOT
and IMPACT equations below.
>
IMPACT = < >
| 0 when x >= x1 |
8. For a stiffening spring characteristic, FORCE_EXPONENT (i.e. e in the equations below) is greater
than 1.0. For a softening spring characteristic, 0 < FORCE_EXPONENT < 1.0.
panel set twindow_function bushing
The FORCE_EXPONENT parameter is used in the BISTOP_SLOT and IMPACT equations

below:
IMPACT = < >
| 0 when x >= x1 |
9. The maximum damping is reached when the BOUNDARY_PENETRATION (i.e. d) value is
reached.
The MAX_DAMPING_COEFFICIENT (i.e. cmax) parameter is used in the BISTOP_SLOT and
IMPACT equations below:
IMPACT = < >
| 0 when x >= x1 |

The BUSHING function returns a force COMPONENT for the BUSHING you identify in the
BUSHING_NAME parameter.
parameter is set to "j", the value returned is that acting on the J_MARKER. If the REFERENCE_MARKER
is not specified, the results are with respect to the ground coordinate system.
Format:
bushing_name = existing bushing
panel 47
Description:

Bushing_name Existing Bushing Specifies an existing bushing.
return_value_on_marker Marker_type Specifies for which marker on the force
element (i or j) the function will return force
values.
component FM, FX, FY, FZ, TM, Specifies the specific COMPONENT of
TX, TY, TZ force or torque that the function is to return
for the force element.
reference_marker Existing Marker Specifies a marker that provides a reference
1. You may identify a bushing by typing its name or by picking it from the screen.
If the bushing is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the bushing is displayed.
If you created the bushing by reading an Adams data set or graphics file, the bushing name is the
letters BUS followed by the Adams data set bushing ID number. For example, the name of
AdamsAdams BUSHING/101 is BUS101. If you created the bushing during preprocessing, you will
If a bushing is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a bushing under a different model, for instance, you may need to enter
the model name as well. For example, you may specify bushing 'lower_front' from model 'sla' by
entering ".sla.lower_front". If you type a "?", Adams View will list the bushings available by default.
You must separate multiple bushing names by commas.
If the bushing is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple bushing picks by commas.
panel set twindow_function chebyshev_polynomial

The CHEBYSHEV_POLYNOMIAL function evaluates a Chebyshev polynomial at a user specified value x.
The SHIFT (that is, x0) and the COEFFICIENTS (that is, a0, a1,..., a30) parameters are used to define the
constants for the Chebyshev polynomial. The Chebyshev polynomial is defined as:
C(x) =\ aj * Tj(x-x0)
where the functions Tj are recursively defined as:
Tj(x-x0) = 2 * (x-x0) * Tj-1(x-x0) - Tj-2(x-x0)
where
T0(x-x0) = 1, and
T1(x-x0) = x-x0.
The index "j" has a range from zero (0) to n, where n is the number of terms in the series.
Note that:
T2(x-x0) = 2 * (x- x0)**2 - 1
T3(x-x0) = 4 * (x- x0)**3 - 3 * (x- x0)
Format:
x = run time function
shift = real
angular_shift = angle
coefficients = real
angular_coefficients = angle
panel 49
panel set twindow_function cosine_fourier_series
Description:

x Run Time Function Specifies a run time function.
shift Real Specifies a real variable that is a non-angular shift
in a Chebyshev polynomial, Fourier Cosine
series, Fourier Sine series, or polynomial
function. Or, a phase shift in the independent
variable x, for a simple_harmonic_function.
angular_shift Angle Specifies a real variable that is a non-angular shift
in a Chebyshev polynomial, Fourier Cosine
series, Fourier Sine series, or polynomial
function. Or, a phase shift in the independent
coefficients, Real Specifies the non-angular real variables that
define as many as thirty-one coefficients (a0,
a1,..., a30) for the series or polynomial.
angular_coefficients Angle Specifies the angular real variables that define as
many as thirty-one coefficients (a0, a1,..., a30)
for the series or polynomial.

The COSINE_FOURIER_SERIES function evaluates a Fourier Cosine series at a user specified value "x".
The SHIFT (i.e. x0) and the COEFFICIENTS (i.e. a0, a1,..., a30) parameters are used to define the
constants for the Fourier Cosine series. The FREQUENCY (i.e. w) parameter specifies the fundamental
frequency of the series. The Fourier Cosine series is defined :
F(x) =\ aj * Tj (x-x0)
where the functions Tj are defined as:
Tj (x-x0) = cos{j * w * (x-x0)}
The index j has a range from zero (0) to n, where n is the number of terms in the series.
Format:
x = run time function
shift = real
coefficients = real

frequency = angle
Description:

x Run time function Specifies a run time function.
shift Real Specifies a real variable that is a non-angular shift in
a Chebyshev polynomial, Fourier Cosine series,
Fourier Sine series, or polynomial function. Or, a
phase shift in the independent variable x, for a
simple_harmonic_function.
angular_shift Angle Specifies a real variable that is a non-angular shift in
a Chebyshev polynomial, Fourier Cosine series,
coefficients Real Specifies the non-angular real variables that define
as many as thirty-one coefficients (a0, a1,..., a30)
many as thirty-one coefficients (a0, a1,..., a30) for
the series or polynomial.
Frequency Angle Specifies the real variable that is the fundamental
FREQUENCY of the series or harmonic function.
1. Adams assumes FREQUENCY is in radians per unit of the independent variable unless you use a D
after the value.
The FREQUENCY parameter is represented in the following functions as "w".
The SIMPLE_HARMONIC_FUNCTION
SHF = a * sin(w * (x-x0) - phi) + b
The FOURIER_COSINE_SERIES is defined :
F(x) =aj*Tj(x-x0), where the Tj are: Tj(x-x0)=cos{j * w * (x-x0)}
The FOURIER_SINE_SERIES is defined as:
F(x) =aj*Tj(x-x0), where the Tj are: Tj(x-x0)=sin{j * w * (x-x0)}
panel 51
panel set twindow_function cubic_spline

The CUBIC_SPLINE function uses the standard cubic method of interpolation to create a spline function
across a set of data points
Format:
x = function
z = function
Example:
panel set twindow_function cubic_spline &
panel set twindow_function cubic_spline spline_name = spline_1 &
panel set twindow_function cubic_spline derivative_order = 2 &
Description:

x Function Specifies the real variable that is the independent
variable value along the x-axis of the spline.
z Function Specifies a real variable that is the second independent
variable value along the z-axis of the surface being
interpolated
spline_name An Existing Spline Specifies an existing spline
derivative_order Integer An optional integer that specifies the order of the
derivative at the interpolate value to be returned by
CUBSPL.
Range: 0 < iord < 2
1. The data points are defined in a SPLINE DATA_ELEMENT in your Adams View model. The
SPLINE that you define may represent a curve ( x-y points) or a surface (x-y-z points). Interpolation
in the y direction is cubic, and interpolation in the z direction is linear.
The CUBIC_SPLINE, though not as fast as AKIMA_SPLINE, always produces good results for the
value of the function being approximated, including its first and second derivatives. There is no
requirement on the data points being evenly spaced. This may be an important consideration when
you use splines to define functions in Adams. The solution process often requires estimates of
derivatives of the functions being defined. The smoother a derivative is, the easier it is for the solution
process to converge.
If the spline data incorporates sudden changes in value, the CUBIC_SPLINE function gives more
oscillatory results for the curve or surface than are given by the AKIMA_SPLINE function.tended
Definition:
2. This variable can be any value of interest that you can compute using a function expression.
verification.
Components Examples
NUMBERS
OPERATORS
panel 53
AdamsAdams subtracts TIME from one before it performs multiplication and division.
SYSTEM CONSTANTS
BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
SYSTEM VARIABLES
ARITHMETIC IFS
follows:
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
MAX, SIN, SQRT, and TAN in your expression. For more information about these functions, see a
FORTRAN reference manual. Invoke the text edit window and pick the FUNCTIONS button to
Adams FUNCTIONS
be accessed.
panel 55
Names Purposes
cubic curve(a spline) to the data.
3. If the SPLINE defines only one curve, Adams ignores this parameter.
verification.
Components Examples
Components Examples
NUMBERS
OPERATORS
SYSTEM CONSTANTS
BLANKS
CONTINUATION COMMAS
panel 57
FUNCTION BUILDER
SYSTEM VARIABLES
ARITHMETIC IFS
follows:
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
FUNCTION expression. The following table lists all the AdamsAdamsAdams functions and their
purposes. Invoke the text edit window and pick the FUNCTIONS button to make a list of functions
that can be accessed.
Names Purposes
spline name is the letters SPL followed by the Adams data set spline ID number. The name of Adams
SPLINE/101 is SPL101, for example. If you created the spline during preprocessing, you gave it a
name at that time.
panel 59
panel set twindow_function curve_curve

The curve_curve function returns the COMPONENT of a force due to curve_curve you identify in the
CURVE_CURVE_NAME parameter.
is not specified the results are with respect to the ground coordinate system.
Format:
curve_curve_name = existing curve_curve
Description:

Curve_curve_name Existing curve_curve Specifies an existing curve_curve
constraint.
return_value_on_marker Marker_type Specifies for which marker on the
force element (i or j) the function
will return force values.
component FM, FX, FY, FZ, TM, TX, TY, Specifies the specific
TZ COMPONENT of force or torque
that the function is to return for the
force element.
reference_marker Existing Marker Specifies a marker that provides a
reference coordinate system for the
function.
1. You may identify a curve_curve by typing its name or by picking it from the screen.
If the curve_curve is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the curve_curve is displayed.
panel set twindow_function differential_equation
If you created the curve_curve by reading an Adams data set or graphics file, the curve_curve name is
the letters CCU followed by the Adams data set curve_curve ID number. For example, the name of
Adams CVCV/101 is CCU101. If you created the curve_curve during preprocessing, you will have
If a curve_curve is available by default, you may identify it by entering only its name. If it is not, you
To identify a curve_curve under an model, for instance, you may need to enter the model name as
well. For example, you may specify CVCV101 from the model named test by entering
".test.CCU101". If you type a "?", Adams View will list the curve_curves available by default.
You must separate multiple curve_curve names by commas.
If the curve_curve is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple curve_curve picks by commas.

The DIFFERENTIAL_EQUATION function returns the value of the state variable associated with the
DIFFERENTIAL_EQUATION you identify in the DIFFERENTIAL_EQUATION_NAME parameter.
Format:
differential_equation_name = existing equation
Example:
panel set twindow_function differential_equation &
differential_equation_name = diff_1
panel 61
panel set twindow_function dm
Description:

differential_equation_name Existing Equation Specifies an existing
differential_equation.
1. You may identify a differential_equation by typing its name or by picking it from the screen.
Since differential_equation do not have a geometric position, Adams View displays
differential_equation icons at or near the model origin. If the differential_equation icon is not visible
differential_equation icon is displayed.
If you created the differential_equation by reading an Adams data set or graphics file, the
differential_equation name is the letters DIF followed by the Adams data set differential_equation ID
number. For example, the name of Adams DIFF/101 is DIF101. If you created the
differential_equation during preprocessing, you will have given it a name at that time.
If a differential_equation is owned by the default model, you may identify it by entering its name
only. If it is not, you must enter its full name. To identify a differential_equation under a different
model, for instance, you may need to enter the model name as well.
For example, you may specify differential_equation 'fluid_volume' from model 'hydro' by entering
".hydro.fluid_volume'". If you type a "?", Adams View will list the differential_equation available by
default.
You must separate multiple differential_equation names by commas.
If the differential_equation is visible in one of your views, you may identify it by picking on any of
You need not separate multiple differential_equation picks by commas.

The DM function returns the magnitude of the translational displacement vector from J_MARKER (i2) to
I_MARKER (i1).
Format:
Example:
panel set twindow_function dm &
panel set twindow_function dm i_marker_name = marker_71 &
panel set twindow_function dm j_marker_name = marker_82
Description:

i_marker_name AN EXISTING MARKER Specifies an existing marker used as the I_MARKER
j_marker_name AN EXISTING MARKER Specifies an existing marker used as the J_MARKER
1. The J_MARKER (i2) may not be specified, in which case it defaults to ground. DM is the distance
between markers i1 and i2 and by definition is always positive. Mathematically, DM is calculated as
follows:
DM = ( [ Ri1 - Ri2] [ Ri1 - Ri2] )**1/2
where Ri1 is the displacement of marker i1 in ground, and Ri2 is the displacement of marker i2 in
ground.
If you created the marker by reading an ADAMS data set or graphics file, the marker name is the
letters MAR followed by the ADAMS data set marker ID number. The name of ADAMS
MARKER/101 is MAR101, for example. If you created the marker during preprocessing, you gave
panel 63
panel set twindow_function dt_differential_equation
If you created the marker by reading an ADAMS data set or graphics file, the marker name is the
letters MAR followed by the ADAMS data set marker ID number. The name of ADAMS
MARKER/101 is MAR101, for example. If you created the marker during preprocessing, you gave
Tips:

The DT_DIFFERENTIAL_EQUATION function returns the value of the time derivative of the state
variable associated with the DIFFERENTIAL_EQUATION you specify in the
DIFFERENTIAL_EQUATION_NAME parameter.
Format:
differential_equation_name = an existing equation
Example:
panel set twindow_function dt_differential_equation &
differential_equation_name = diff_eq_1
Description:

differential_equation_name An Existing Specifies an existing differential_equation.
Equation
1. In instances, where a DIFFERENTIAL_EQUATION is used to define an implicit algebraic
equation, the DT_DIFFERENTIAL_EQUATION function returns an approximation of the time
derivative obtained by numerical differencing.
2. You may identify a differential_equation by typing its name or by picking it from the screen.
panel set twindow_function dx
Since differential_equation do not have a geometric position, Adams View displays

differential_equation icons at or near the model origin. If the differential_equation icon is not visible
differential_equation icon is displayed.
If you created the differential_equation by reading an Adams data set or graphics file, the
differential_equation name is the letters DIF followed by the Adams data set differential_equation ID
number. The name of Adams DIFF/101 is DIF101, for example. If you created the
differential_equation during preprocessing, you gave it a name at that time.
If a differential_equation is owned by the default model, you may identify it by entering its name
only. If it is not, you must enter its full name. To identify a differential_equation under a different
differential_equation 'fluid_volume' from model 'hydro' by entering ".hydro.fluid_volume'".
You must separate multiple differential_equation names by commas.
If the differential_equation is visible in one of your views, you may identify it by picking on any of
You need not separate multiple differential_equation picks by commas.
Tips:
1. If you type a "?", Adams View will list the differential_equation available by default.

The DX function returns the x-component of the translational displacement vector from J_MARKER (i2)
to I_MARKER (i1), as expressed in R_MARKER (i3) coordinate system.
Format:
r_marker_name = an existing marker
Example:
panel set twindow_function dx &
panel 65
Description:

i_marker_name An Existing Marker Specifies an existing marker used as the I_MARKER (i1) in
the evaluation of the function.
j_marker_name An Existing Marker Specifies an existing marker used as the J_MARKER (i2) in
r_marker_name An Existing Marker Specifies the marker used as the R_MARKER (i3) with
respect to which you want Adams to evaluate the function.
1. The J_MARKER (i2) may not be specified, in which case it defaults to ground. Similarly, the
R_MARKER (i3) may not be specified, in which case it defaults to ground. Mathematically, DX is
calculated as follows:
DX = [ Ri1 - Ri2] xi3
where Ri1 is the displacement of marker i1 in ground, Ri2 is the displacement of marker i2 in ground,
and xi3 is the unit vector along the x-axis of marker i3 .
time.
time.
panel set twindow_function dy
4. If you do not supply this parameter, Adams will evaluate the function in the ground reference frame.
Tips:

The DY function returns the y-component of the translational displacement vector from J_MARKER (i2)
to I_MARKER (i1), as expressed in the R_MARKER (i3) coordinate system. J_MARKER (i2) may not be
specified, in which case, it defaults to ground. Similarly, the R_MARKER (i3) may not be specified, in which
case it defaults to ground. Mathematically, DY is calculated as follows:
DY = [ Ri1 - Ri2] yi3
where, Ri1 is the displacement of marker i1 in ground, Ri2 is the displacement of marker i2 in ground, and
xi3 is the unit vector along the y-axis of marker i3 .
Format:
Example:
panel set twindow_function dy &
r_marker_name = cm
panel 67
panel set twindow_function field
Description:

R_marker_name Existing Marker Specifies the marker used as the R_MARKER (i3) with
respect to which you want Adams to evaluate the
function. If you do not supply this parameter, Adams
will evaluate the function in the ground reference
frame.
name at that time.

The FIELD function returns the force COMPONENT for the FIELD you identify in the FIELD_NAME
parameter.
Format:
field_name = existing field
Description:

field_name Existing Field Specifies an existing bushing.
return_value_on_marke Marker_type Specifies for which marker on the force
element (i or j) the function will return
force values.
component FM, FX, FY, FZ, TM, TX, TY, TZ Specifies the specific COMPONENT of
force or torque that the function is to
return for the force element.
function.
1. Specifies an existing field which you want information on.
You may identify a field by typing its name or by picking it from the screen.
If the field is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the field is displayed.
If you created the field by reading an Adams data set file, the field name is 'FIE'. If you created the
field during preprocessing, you will have given it a name at that time.
If a field is available by default, you may identify it by entering only its name. If it is not, you must
".robot.fld1". If you type a "?", Adams View will list the fields available by default.
You must separate multiple field names by commas.
If the field is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple field picks by commas.
panel 69
panel set twindow_function fm

The FM function returns the magnitude of the net translational force acting at the I_MARKER (i1). You
should omit specification of the J_MARKER (i2) when the user wants to find the magnitude of an action-
only force acting at I_MARKER (i1).
Format:
Example:
panel set twindow_function fm &
Description:

I_marker_name Existing marker Specifies an existing marker used as the I_MARKER (i1) in
J_marker_name Existing marker Specifies an existing marker used as the J_MARKER (i2) in
panel set twindow_function force_vector
MAR followed by the AdamsAdams data set marker ID number. The name of Adams MARKER/101
is MAR101, for example. If you created the marker during preprocessing, you gave it a name at that
time.

The FORCE_VECTOR function returns the force COMPONENT of a FORCE_VECTOR you identify
in the FORCE_VECTOR_NAME parameter.
Format:
force_vector_name = an existing vforce
Example:
panel set twindow_function force_vector &
panel set twindow_function single_component_force return_value_on_marker = i &
panel set twindow_function single_component_force component = fx &
panel set twindow_function single_component_force reference_marker = marker_84
panel 71
Description:

force_vector_name An Existing Vforce Specifies an existing force_vector.
return_value_on_marker Marker_type Specifies for which marker on the force element
(i or j) the function will return force values
component All_components Specifies the specific COMPONENT of force
or torque that the function is to return for the
force element.
reference_marker An Existing Marker Specifies a marker that provides a reference
2. You may identify a force vector by typing its name or by picking it from the screen.
If the force vector is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the force vector is displayed.
If you created the force vector by reading an Adams data set or graphics file, the force vector name is
the letters VFO followed by the Adams data set force vector ID number. The name of Adams
VFORCE/101 is VFO101, for example. If you created the force vector during preprocessing, you
If a force vector is available by default, you may identify it by entering its name only. If it is not, you
must enter its full name. To identify a force vector under another model, for instance, you may need
to enter the model name as well. For example, you may specify force vector 'spring' from the model
'suspension' by entering ".suspension.spring". If you type a "?", AdamsAdams View will list the force
J_MARKER. If the REFERENCE_MARKER is not specified the results are with respec to the
panel set twindow_function fx
REFERENCE_MARKER is not specified the results are with respect to the ground coordinate
system.
Tips:
1. You need not separate multiple force vector picks by commas.
2. If the force vector is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.

The FX function returns the x-component of the net translational force acting at the I_MARKER (i1) as
computed in the coordinate system of the R_MARKER (i3). All force elements acting between the I_ and
J_MARKERs (i1 and i2) are included in the calculation of the force, unless the force is an action-only type
force. You should omit specification of the J_MARKER (i2) and the R_MARKER (i3) to find the x-
component of an action-only force acting at the I_MARKER (i1).
Format:
Example:
panel set twindow_function fx &
r_marker_name = marker_4
panel 73
panel set twindow_function fy
Description:

I_marker_name Existing marker Specifies an existing marker used as the I_MARKER (i1) in
J_marker_name Existing marker Specifies an existing marker used as the J_MARKER (i2) in
R_marker_name Existing marker Specifies the marker used as the R_MARKER (i3) with
respect to which you want Adams to evaluate the function.
If you do not supply this parameter, Adams will evaluate the
function in the ground reference frame.
time.
part 'lower_arm' by entering ".links.lower_arm.pivot". If you type a "?", AdamsAdams View will list
the markers available by default.

The FY function returns the y-component of the net translational force acting at the I_MARKER (i1), as
computed in the coordinate system of the R_MARKER (i3). All force elements acting between the I_ and
J_MARKERs (i1 and i2) are included in the calculation of the force, unless the force is an action-only type
force. The user should omit specification of the J_MARKER (i2) and the R_MARKER (i3) or specify it as
zero to find the y-component of an action-only force acting at the I_MARKER (i1).
Format:
Example:
panel set twindow_function fy &
r_marker_name = marker_4
Description:

R_marker_name Existing marker Specifies the marker used as the R_MARKER (i3) with
respect to which you want Adams to evaluate the
function. If you do not supply this parameter, Adams
will evaluate the function in the ground reference frame.
time.
panel 75
panel set twindow_function general_force

The GENERAL_FORCE function returns the force COMPONENT for a GENERAL_FORCE you
identify in the GENERAL_FORCE_NAME parameter.
Format:
general_force_name = an existing genforce
Example:
panel set twindow_function general_force &
Description:

general_force_name An Existing Genforce Specifies an existing general force.
values
component All_components Specifies the specific COMPONENT of
force or torque that the function is to return
for the force element.
formed by the three component forces and the three component torques determines the direction of
The GENERAL_FORCE corresponds to the Adams GFORCE statement.
A GENERAL_FORCE creates a six component force element that applies the forces between two
As the system moves, Adams moves the "floating_marker" on its part to keep the "floating_marker"
the "floating_marker" marker at the instantaneous position of the I marker. The magnitude of the
force depends on expressions or subroutines that the user supplies. The value of the force is the
resultant (that is, the square root of the sum of the squares) of (up to) three mutually orthogonal force
components together with the resultant (that is, the square root of the sum of the squares) of (up to)
three mutually orthogonal torque components.
The resultant vector formed by the three user-defined component forces along the reference marker
action.
The resultant vector formed by the three component torques determines the direction of the
rotational torque action. The user defines these torques about the reference marker axes. The reaction
is equal and opposite to the action.
panel 77
panel set twindow_function impact
system.
Cautions:
1. If the REFERENCE_MARKER is not specified the results are with respect to the ground coordinate
system.

The IMPACT function models collisions. It evaluates a function that turns on when the distance between
the I and the J markers falls below a nominal FREE_LENGTH (i.e. x1), (i.e. when two parts collide). As long
as the distance between the I and the J markers is greater than the FREE_LENGTH, the force is zero. An
example of a system you can model with the IMPACT function is a ball impacting the ground.
The force has two components, a spring or STIFFNESS component and a damping or viscous component.
The STIFFNESS component (i.e. k) with the FORCE_EXPONENT (i.e. e) is a function of the penetration
of the I_MARKER within the free length distance from the J_MARKER. The stiffness component opposes
the penetration. The damping component of the force is a function of the speed of penetration. The
damping opposes the direction of relative motion. To prevent a discontinuity in the damping force at
contact, the damping coefficient is, by definition, a cubic step function of the penetration. Thus at zero
penetration, the damping coefficient is always zero. The damping coefficient achieves a
MAX_DAMPING_COEFFICIENT (i.e. cmax), at a user-defined penetration,
BOUNDARY_PENETRATION (that is, d).
The equation for this function can be mathematically expressed as follows:
Note that when:

 x > x1, no penetration occurs and the force is zero (penetration p = 0)
 x < x1, penetration occurs at the end closer to the J marker, and the force is > 0 (penetration p = x1 -
x).
Also note that when p < d, the instantaneous damping coefficient is a cubic step function of the
penetration p.
When p > d, the instantaneous damping coefficient is cmax.
Adams Solver (FORTRAN) never returns a negative force for IMPACT. If the above expression is
negative, Adams Solver (FORTRAN) returns a value of zero.
Figure 2, below, is a plot of damping coefficient versus penetration.
Figure 2. Damping Coefficient versus Penetration
Format:
x= run time function
dx= function
free_length= real
boundary_penetration= real
angular_free_length= angle
angular_boundary_penetration= angle
stiffness= real
force_exponent= real
max_damping_coefficient= real
panel 79
Description:

x Run Time Function Specifies the run time function.
dx Function Specifies a real variable that communicates the time
derivative of x to the function.
free_length Real Specifies the non-angular FREE_LENGTH of the
independent variable, x.
boundary_penetration Real Specifies a positive real variable that is the non-
angular boundary penetration at which Adams
angular_free_length Angle Specifies the ANGULAR_FREE_LENGTH of the
independent variable, x.
angular_boundary_penet Angle Specifies a positive real variable that is the angular
ration boundary penetration at which Adams applies full
damping.
stiffness Real A non-negative real variable that specifies the
stiffness of boundary surface interaction.
force_exponent Real Specifies a positive real variable that is the exponent
of the force deformation characteristic.
max_damping_coefficien Real Specifies a non-negative real variable that is the
t maximum damping coefficient.
1. IMPACT models collisions and contact. It evaluates a force that turns on when a distance falls below
a nominal free length (that is, when two parts collide).
The force has two components: a spring or stiffness component and a damping or viscous component.
The stiffness component opposes the penetration. The damping component of the force is a function
of the speed of penetration. The damping opposes the direction of relative motion. To prevent a
discontinuity in the damping force at contact, the damping coefficient is, by definition, a cubic step
function of the penetration. Thus, at zero penetration, the damping coefficient is always zero. The
damping coefficient achieves a maximum, cmax, at a user-defined penetration, d.
An object colliding with ground is an example of a system that can be modeled with the IMPACT
function.
Let x be the instantaneous distance, x1 be the free length (when x is less than x1, the force turns on),
x1 - x be the penetration, and d be the penetration at which Adams/Solver applies full damping
(cmax).
• When x x1, force = 0.
• When x < x1, force is positive.
• When (x1-d) < x < x1, force is positive; there is damping, but it is less than cmax.
• When x (x1-d), force is positive and damping = cmax.
The following equation defines IMPACT:
2. You compute the value of the dx parameter by using a function expression.

For example, if x (the distance variable you use to compute the force) is compute using the distance
function DX(0201,0301) then, dx is computed using the velocity function VX(0201,0301).
verification.
.
Components Examples
NUMBERS
panel 81
OPERATORS
• priorities. ** then * / then + -. In other words, Adams executes exponentiation (**) before all other
operators and executes multiplication (*) and division (/) before addition (+) and subtraction (-).
SYSTEM CONSTANTS
BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
The FUNCTIONS button on the right side of the Adams View text editor provides a means of
SYSTEM VARIABLES
ARITHMETIC IFS
follows.
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
accessed.
panel 83
Adams FUNCTIONS
accessed.
Names Purposes
AKISPL Accesses the data in a SPLINE statement and uses the Akima cubic method to
BISTOP Evaluates a force restricting displacement of a part in two opposite directions.
4. For an impact force, the free_length parameter specifies the distance above which there is no contact,
and therefore, no force is generated. Specifically, if x is less than the FREE_LENGTH (i.e. x1),
Adams calculates a positive value for the force. Otherwise, the force value is zero.
5. The BOUNDARY_PENETRATION parameter is given as "d" in the BISTOP_SLOT and
IMPACT equations below.
6. For an impact force, the angular_free_length is the distance above which there is no contact, and
therefore no force, is generated. Specifically, if x is less than the FREE_LENGTH (i.e. x1), Adams
calculates a positive value for the force. Otherwise, the force value is zero.
7. For a stiffening spring characteristic, FORCE_EXPONENT (i.e. e in the equations below) is greater
than 1.0. For a softening spring characteristic, 0 < FORCE_EXPONENT < 1.0.
panel set twindow_function input_value_for_plant
The FORCE_EXPONENT parameter is used in the BISTOP_SLOT and IMPACT equations

below:
8. The maximum damping is reached when the BOUNDARY_PENETRATION (i.e. d) value is

reached.
The MAX_DAMPING_COEFFICIENT (i.e. cmax) parameter is used in the BISTOP_SLOT and
IMPACT equations.
Cautions:
1. IMPACT is only used to determine force or torque magnitudes.
2. The force value and the distance measure must both be positive in the same direction.
3. When e is less than or equal to one, the rate of change of the force is discontinuous at contact. This
may cause convergence problems.
panel set twindow_function input_value_for_plant

The OUTPUT_VALUE_FOR_PLANT function returns the COMPONENT of a PLANT_OUTPUT you
identify in the PLANT_OUTPUT_NAME parameter.
A PLANT_OUTPUT is made up of a list of VARIABLES (algebraic expressions). The COMPONENT
parameter is an integer indicating the kth VARIABLE in the list. For example, if the PLANT_OUTPUT is
defined by a list of ten VARIABLEs, and you list the component as 7, the
OUTPUT_VALUE_FOR_PLANT function returns the value for the 7th VARIABLE in the list.
Format:
panel set twindow_function output_value_for_plant
plant_input_name = existing poutput
component = integer
Example:
panel set twindow_function output_value_for_plant &
plant_output_name = poutput_01 &
component = 2
panel 85
panel set twindow_function invpsd
The OUTPUT_VALUE_FOR_PLANT function returns the value for the 2nd VARIABLE in the list since
the component value specified is 2.
Description:

Plant_output_name Existing poutput Specifies an existing plant_output.
Component Integer Specifies which VARIABLE value should be returned for the
OUTPUT_VALUE_FOR_PLANT or
OUTPUT_VALUE_FOR_PLANT function.
1. You may identify a plant_output by typing its name or by picking it from the screen.
Since plant_output do not have a geometric position, Adams View displays plant_output icons at or
near the model origin. If the plant_output icon is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the plant_output icon is displayed.
If you created the plant_output by reading an Adams data set or graphics file, the plant_output name
is the letters "POU" followed by the Adams data set plant_output ID number. For example, the
name of Adams POUTPUT/101 is POU101. If you created the plant_output during preprocessing,
If a plant_output is owned by the default model, you may identify it by entering only its name. If it
is not, you must enter its full name. To identify a plant_output under a different model, for instance,
you may need to enter the model name as well. For example, you may specify plant_output
'actual_velocity' from model 'motor' by entering ".motor.actual_velocity'". If you type a "?", Adams
View will list the plant_output available by default.
You must separate multiple plant_output names by commas.
If the plant_output is visible in one of your views, you may identify it by picking on any of the
You need not separate multiple plant_output picks by commas.
2. The COMPONENT is an integer indicating the kth VARIABLE in the list.
For example, A PLANT_OUTPUT is made up of a list of VARIABLES (algebraic expressions). The
COMPONENT parameter for the OUTPUT_VALUE_FOR_PLANT function is an integer
indicating the kth VARIABLE in the list. Therefore, if the PLANT_OUTPUT is defined by a list of
ten VARIABLEs, and you request the 7th component to be returned, the

The INVPSD (Inverse Power Spectral Density) function regenerates a time signal from a power spectral
density description
Format:
x = function
min_frequency = real
max_frequency = real
num_frequencies = real
use_logarithmic = boolean
random_number_seed = real
Example:
panel set twindow_function invpsd &
panel set twindow_function invpsd spline_name = spline_1 &
panel set twindow_function invpsd min_frequency = 30 &
panel set twindow_function invpsd num_frequencies = 47 &
panel set twindow_function invpsd use_logarithmic = yes
Description:

x Function Specifies a real variable that is the independent
variable of the function
spline_name An Existing Spline You identify a spline by typing its name.
min_frequency Real A real variable that specifies the lowest frequency to
be regenerated.
max_frequency Real A real variable that specifies the highest frequency to
be regenerated
num_frequencies Real An integer that specifies the number of frequencies.
This number is supposed to be larger than 1 and less
than 200
use_logarithmic Boolean An integer variable that acts as a flag indicating
whether the PSD data points are interpolated in the
linear or logarithmic domain.
random_number_seed Real A real variable that specifies a seed for a random
number generator, used to calculate the phase shifts
panel 87
1. This variable can be any value of interest that you can compute using a function expression. For
example, if the independent variable in the function is time, x is the system variable TIME.
verification.
Components Examples
NUMBERS
OPERATORS
SYSTEM CONSTANTS
BLANKS
CONTINUATION COMMAS
FUNCTION BUILDER
SYSTEM VARIABLES
panel 89
ARITHMETIC IFS
follows:
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
FUNCTION expression. The following table lists all the Adams functions and their purposes. Invoke
the text edit window and pick the FUNCTIONS button to make a list of functions that can be
accessed.
Names Purposes
AKISPL Accesses the data in a SPLINE statement and uses the Akima cubic method to
panel set twindow_function joint
Names Purposes
2. If you created the spline by reading an Adams data set, the spline name is the letters SPL followed by
the Adams data set spline ID number. The name of Adams SPLINE/101 is SPL101, for example. If
you created the spline during preprocessing, you gave it a name at that time.
3. The legal values are:yes (0) - linear domain no (1) - logarithmic domain
4. During a simulation, PSD can be called with up to a maximum of 20 different seeds.
Cautions:
1. You must separate multiple spline names by commas.

The JOINT function returns the force COMPONENT for the JOINT you identify in the JOINT_NAME
parameter.
Format:
Example:
panel 91

Description:

joint_name An Existing Joint Specifies an existing joint
return_value_on_marker Marker_type Specifies for which marker on the force element (i or j)
the function will return force values
component All_components Specifies the specific COMPONENT of force or
torque that the function is to return for the force
element.
reference_marker An Existing Marker Specifies a marker that provides a reference coordinate
system for the function.
2. Specifies an existing joint.
You may identify a joint by typing its name or by picking it from the screen.
panel set twindow_function m_acc
system.
Cautions:
1. You must separate multiple joint names by commas.
Tips:
1. If the joint is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple joint picks by commas.

The M_ACC function calculates the magnitude of the difference of the translational acceleration vector of
the I_MARKER (i1) in ground and the J_MARKER (i2) in ground.
Format:
reference_frame_marker = an existing marker
Example:
panel set twindow_function m_acc &
panel 93
Description:

i_marker_name An Existing Marker Specifies an existing marker used as the I_MARKER
j_marker_name An Existing Marker Specifies an existing marker used as the J_MARKER
reference_frame_marker An Existing Marker The reference frame in which the second time
derivative of the displacement vector is taken
1. Mathematically, M_ACC is calculated as follows:
M_ACC = ([ai1-ai2] dot_product_with [ai1-ai2])**1/2
where ai1 is the acceleration of the I_MARKER (i1) in ground, and ai2 is the acceleration of the
J_MARKER (i2) in ground.
time.
time.
panel set twindow_function m_wdt
4. Set l = 0 or omit the argument if you want the time derivatives to be calculated in the ground

The M_WDT function returns the magnitude of the difference between the angular acceleration vector of
the I_MARKER (i1) in ground and the angular acceleration of the J_MARKER (i2) in ground.
Mathematically, M_WDT is calculated as follows:
M_WDT = ([i1-i2] dot_product_with [i1-i2])**1/2
where i1 is the angular acceleration vector of the I_MARKER (i1) in ground, and i2 is the angular
acceleration vector of the J_MARKER (i2) in ground.
Format:
Reference_frame_marker = an existing marker
Example:
panel set twindow_function m_wdt &
reference_frame_marker = marker_4
Description:

I_marker_name Existing marker Specifies an existing marker used as the
I_MARKER (i1) in the evaluation of the
function.
J_marker_name Existing marker Specifies an existing marker used as the
J_MARKER (i2) in the evaluation of the
function.
Reference_frame_marker Existign marker Specifies the reference frame marker.
panel 95
panel set twindow_function motion
time.

The MOTION function returns the force COMPONENT caused by the MOTION you identify in the
MOTION_NAME parameter.
Format:
Example:
Description:

motion_name An Existing Motion Specifies an existing motion generator.
return_value_on_marker Marker_type Specifies for which marker on the force element (i or j)
the function will return force values
component All_components Specifies the specific COMPONENT of force or
torque that the function is to return for the force
element.
reference_marker An Existing Marker Specifies a marker that provides a reference coordinate
system for the function.
panel 97
panel set twindow_function multi_point_force
system.
Cautions:
1. You must separate multiple motion-generator names by commas.
Tips:
1. If the motion generator is visible in one of your views, you may identify it by picking on any of the
2. You need not separate multiple motion-generator picks by commas.

Format:
multi_point_force_name = an existing nforce
Example:
panel set twindow_function multi_point_force marker_name = marker_1 &
panel set twindow_function multi_point_force reference_marker = marker_80
panel set twindow_function phi
Description:

multi_point_force_name An Existing Nforce Specifies an existing multi_point_force
marker_name An Existing Marker
force element.
1. You use multi_point_force_name parameter to identify the existing multi_point_force to affect with
this command.
You may identify a multiple point force by typing its name or by picking it from the screen.
If the multiple point force is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the multiple point force is displayed.
If you created the multiple point force by reading an Adams data set or graphics file, the multiple
point force name is the letters NFO followed by the Adams data set multiple point force ID number.
The name of Adams NFORCE/101 is NFO101, for example. If you created the multiple point force
during preprocessing, you gave it a name at that time.
If a multiple point force is available by default, you may identify it by entering its name only. If it is
not, you must enter its full name. To identify a multiple point force under another model, for
instance, you may need to enter the model name as well. For example, you may specify multiple point
force 'FEA_element' from the model 'suspension' by entering ".suspension.FEA_element". If you
type a "?", Adams View will list the multiple point forces available by default.
You must separate multiple multiple point force names by commas.
If the multiple point force is visible in one of your views, you may identify it by picking on any of the
Tips:
1. You need not separate multiple multiple point force picks by commas.

The PHI function calculates the third angle of a body-2 [3 1 3] Euler rotation sequence, which will orient
the J_MARKER (i2) the same as the I_MARKER (i1).
panel 99
panel set twindow_function pitch
Format:
Example:
panel set twindow_function phi &
Description:

name at that time.

The PITCH function calculates the second angle of a body-3 [3 -2 1]
Euler rotation sequence which will orient the J_MARKER (i2) the same as the I_MARKER (i1).
Format:
Example:
panel set twindow_function pitch &
Description:

I_marker_name An Existing Marker Specifies an existing marker used as the I_MARKER (i1) in the
evaluation of the function.
J_marker_name An Existing Marker Specifies an existing marker used as the J_MARKER (i2) in the
time.
panel 101
panel set twindow_function point_curve

The point_curve function returns the COMPONENT of a force due to point_curve you identify in the
POINT_CURVE_NAME parameter.
Format:
point_curve_name = existing point_curve
Description:

Point_curve_name Existing point_curve Specifies an existing point_curve
constraint.
force values.
component FM, FX, FY, FZ, TM, TX, TY, Specifies the specific COMPONENT of
TZ force or torque that the function is to
function.
1. You may identify a point_curve by typing its name or by picking it from the screen.
If the point_curve is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the point_curve is displayed.
If you created the point_curve by reading an Adams data set or graphics file, the point_curve name is
the letters PCU followed by the Adams data set point_curve ID number. For example, the name of
Adams CVCV/101 is PCU101. If you created the point_curve during preprocessing, you will have
panel set twindow_function polynomial
If a point_curve is available by default, you may identify it by entering only its name. If it is not, you
To identify a point_curve under an model, for instance, you may need to enter the model name as
well. For example, you may specify CVCV101 from the model named test by entering
".test.PCU101". If you type a "?", Adams View will list the point_curves available by default.
You must separate multiple point_curve names by commas.
If the point_curve is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple point_curve picks by commas.

The POLYNOMIAL function evaluates a standard polynomial at a user specified value x. The SHIFT (i.e.
x0) and the COEFFICIENTS (i.e. a0, a1,..., a30) parameters are used to define the constants for the
polynomial. The standard polynomial is defined as:
The index j has a range from zero to n, where n is the number of terms in the series.
Format:
x = run time functiom
shif = real
panel 103
panel set twindow_function primitive_joint

coefficients = real
Example:
panel set twindow_function polynomial &
x = time &
shift = 0 &
coefficients = 0
Description:

x Run Time Function Specifies the run time function.
shift Real Specifies a real variable that is a non-angular shift in a
Chebyshev polynomial, Fourier Cosine series, Fourier Sine
series, or polynomial function.Or, a phase shift in the
independent variable x, for a simple_harmonic_function.
angular_shift Angle Specifies a real variable that is a angular shift in a Chebyshev
polynomial, Fourier Cosine series,Fourier Sine series, or
polynomial function.Or, a phase shift in the independent
coefficients Real Specifies the non-angular real variables that define as many
as thirty-one coefficients (a0, a1,..., a30) for the series or
polynomial.
angular_coefficients Angle Specifies the angular real variables that define as many as
thirty-one coefficients (a0, a1,..., a30) for the series or
polynomial.

The PRIMITIVE_JOINT function returns the force COMPONENT caused by the PRIMITIVE_JOINT
you identify in the JPRIM_NAME parameter.
Format:
jprim_name = an existing primative joint
Example:
panel set twindow_function primitive_joint &
Description:

jprim_name An Existing Primative Joint Specifies an existing jprim
values
force element.
2. You may identify a jprim by typing its name or by picking it from the screen.
If the jprim is not visible on the screen, you must type the name. You may also find it convenient to
type the name even if the jprim is displayed.
panel 105
panel set twindow_function psi
If you created the jprim by reading an Adams data set or graphics file, the jprim name is the letters
JPR followed by the Adams data set jprim ID number. The name of AdamsAdams JPRIM/101 is
JPR101, for example. If you created the jprim during preprocessing, you gave it a name at that time.
If a jprim is available by default, you may identify it by entering its name only. If it is not, you must
enter its full name. To identify a jprim under an analysis, for instance, you may need to enter the
analysis name as well. For example, you may specify jprim 101 from the analysis named test by
entering ".test.jpr101". If you type a "?", Adams View will list the jprims available by default.
system.
Cautions:
1. You must separate multiple jprim names by commas.
Tips:
1. If the jprim is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
2. You need not separate multiple jprim picks by commas.

The PSI function calculates the first angle of a body-2 [3 1 3] Euler rotation sequence, which will orient the
J_MARKER (i2) the same as the I_MARKER (i1).
Format:
Example:
panel set twindow_function az &
Description:

I_marker_name Existing Marker Specifies an existing marker used as the I_MARKER (i1) in the
J_marker_name Existing Marker Specifies an existing marker used as the J_MARKER (i2) in the
panel 107
panel set twindow_function roll

The ROLL function calculates the third angle of a body-3 [3 -2 1] Euler rotation sequence which will orient
the J_MARKER (i2) the same as the I_MARKER (i1).
Format:
Example:
panel set twindow_function roll &
Description:

I_marker_name An Existing Marker Specifies an existing marker used as the I_MARKER (i1) in the
J_marker_name An Existing Marker Specifies an existing marker used as the J_MARKER (i2) in the
time.
part 'lower_arm' by entering ".links.lower_arm.pivot".
panel set twindow_function simple_harmonic_function
Tips:

The SIMPLE_HARMONIC_FUNCTION evaluates a simple harmonic function.
The following equation defines the function:
where:
x = independent variable expression

a = AMPLITUDE
w = fundmental FREQUENCY
x0 = phase SHIFT in the independent variable
phi = PHASE_SHIFT in the harmonic function
b = AVERAGE_VALUE_OF_DISPLACEMENT
Format:
shift= real
angular_shift= angle
amplitude= real
average_value_of_displacement= real
angular_amplitude= angle
angular_average_value_of_displacement= angle
frequency= angle
phase_shift= angle
Example:
panel set twindow_function simple_harmonic_function &
x = time &
shift = 5 &
amplitude = 200 &
average_value_of_displacement = 256.6 &
frequency = 245 &
phase_shift = 45
panel 109
Description:

X Run Time Function Specifies a run time function.
shift Real Specifies a real variable that is a non-angular shift in a
Chebyshev polynomial, Fourier Cosine series, Fourier
Sine series, or polynomial function. Or, a phase shift in
the independent variable x, for a
angular_shift Angle Specifies a real variable that is a angular shift in a
Chebyshev polynomial, Fourier Cosine series, Fourier
Sine series, or polynomial function. Or, a phase shift in
the independent variable x, for a
amplitude Real Specifies the non-angular AMPLITUDE of the
harmonic function.
average_value_of_displ Real Specifies the non-angular
acement AVERAGE_VALUE_OF_DISPLACEMENT of the
SIMPLE_HARMONIC_FUNCTION.
angular_amplitude Angle Specifies the ANGULAR_AMPLITUDE of the
harmonic function.
angular_average_value Angle Specifies the
_of_displacement ANGULAR_AVERAGE_VALUE_OF_DISPLACE
MENT of the
frequency Angle Specifies the real variable that is the fundamental
phase_shift Angle Specifies a PHASE_SHIFT in the
1. The “amplitude” and the “angular_amplitude” parameters are used in the following
SIMPLE_HARMONIC_ FUNCTION equation:
Where "a" is the AMPLITUDE parameter.
2. In the SIMPLE_HARMONIC_ FUNCTION, “b” represents the average_value_of_displacement.
where, b is the ANGULAR_AVERAGE_VALUE_OF_DISPLACEMENT parameter.
3. Adams assumes FREQUENCY is in radians per unit of the independent variable, unless you use a D
after the value.
panel set twindow_function sine_fourier_series

where:
Tj (x-x0) = cos{j * w * (x-x0)}

where the funtions Tj are defined as:

Tj (x-x0) = sin {j* *(x-x0)}
4. SHF = a * sin(w * (x-x0) - phi) + b
where, "phi" is the PHASE_SHIFT parameter.

The SINE_FOURIER_SERIES function evaluates a Fourier Sine series at a user specified value x. The
SHIFT (i.e. x0) and the COEFFICIENTS (i.e. a0, a1,..., a30) parameters are used to define the constants for
the Fourier Sine series. The FREQUENCY (i.e. w) parameter specifies the fundamental frequency of the
series. The Fourier Sine series is defined as:
F(x) = aj * Tj (x-x0),
where the functions Tj are defined as:
Tj (x-x0) = sin{j * w * (x-x0)}
The index j has a range from zero (0) to n, where n is the number of terms in the series.
Format:
shift= real
angular_shift= angle
panel 111

coefficients= real
angular_coefficients= angle
Frequency = angle
Description:

x Run Time Function Specifies a run time function.
shift Real Specifies a real variable that is a non-angular shift
in a Chebyshev polynomial, Fourier Cosine series,
angular_shift Angle Specifies a real variable that is a non-angular shift
in a Chebyshev polynomial, Fourier Cosine series,
coefficients Real Specifies the non-angular real variables that define
as many as thirty-one coefficients (a0, a1,..., a30)
many as thirty-one coefficients (a0, a1,..., a30) for
the series or polynomial.
Frequency Angle Specifies the real variable that is the fundamental
1. Adams assumes FREQUENCY is in radians per unit of the independent variable unless you use a D
after the value.
F(x) =\ aj*Tj(x-x0),
where the Tj are:
Tj(x-x0)=cos{j * w * (x-x0)}
panel set twindow_function single_component_force

F(x) =\ aj*Tj(x-x0),
where the Tj are:
Tj(x-x0)=sin{j * w * (x-x0)}

The SINGLE_COMPONENT_FORCE function returns the force COMPONENT for the
SINGLE_COMPONENT_FORCE you identify in the SINGLE_COMPONENT_FORCE_NAME
parameter.
Format:
single_component_force_name= an existing single-component force
return_value_on_marker= marker_type
component= all_components
reference_marker= an existing marker
Example:
panel set twindow_function single_component_force &
panel set twindow_function single_component_force single_component_force_name = sforce &
Description:

single_component_force_name An Existing Single- Specifies an existing
component Force single_component_force.
force values
component All_components Specifies the specific COMPONENT of
force or torque that the function is to
panel 113
a "?", Adams View will list the single-component forces available by default.
You must separate multiple single-component force names by commas.
If the single-component force is visible in one of your views, you may identify it by picking on any of
J_MARKER.
system.
Cautions:
1. If the REFERENCE_MARKER is not specified the results are with respect to the ground coordinate
system.
panel set twindow_function spring_damper
Tips:
1. You need not separate multiple single-component force picks by commas.

The SPRING_DAMPER function returns a force COMPONENT for the SPRING_DAMPER you
identify in the SPRING_DAMPER_NAME parameter.
Format:
spring_damper_name= existing spring_damper
reference_marker= existing marker
Description:

Spring_damper_name Existing Spring_damper Specifies an existing spring_damper.
force values.
component FM, FX, FY, FZ, TM, TX, TY, Specifies the specific COMPONENT of
TZ force or torque that the function is to
function.
1. You may identify a spring-damper force by typing its name or by picking it from the screen.
If the spring-damper force is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the spring-damper is displayed.
panel 115
panel set twindow_function state_value_for_plant
If you created the spring-damper force by reading an Adams data set, the spring-damper name is the
letters SPR followed by the Adams data set spring-damper ID number. For example, the name of
Adams SPRINGDAMPER/101 is SPR101. If you created the spring-damper during preprocessing,
If a spring-damper is available by default, you may identify it by entering only its name. If it is not,
To identify a spring-damper under a different model, for instance, you may need to enter the model
name as well. For example, you may specify spring-damper 'left' from model 'sla' by entering
".sla.left".
If you type a "?", Adams View will list the spring-dampers available by default.
You must separate multiple spring-damper names by commas.
If the spring-damper is visible in one of your views, you may identify it by picking on any of the
You need not separate multiple spring-damper picks by commas.

The STATE_VALUE function returns the COMPONENT of a STATE_VALUE you identify in the
PLANT_STATE_NAME parameter.
A PLANT_STATE is made up of a list of VARIABLES (algebraic expressions). The COMPONENT
parameter is an integer indicating the kth VARIABLE in the list. For example, if the PLANT_STATE is
defined by a list of ten VARIABLEs, and you list the component as 7, the STATE_VALUE_FOR_PLANT
function returns the value for the 7th VARIABLE in the list.
Format:
plant_state_name= existing plant state
component= integer
Example:
panel set twindow_function state_value_for_plant &
plant_state_name= pstate_01 &
component= 2
The STATE_VALUE_FOR_PLANT function returns the value for the 2nd VARIABLE in the list since the
component value specified is 2.
Description:

Plant_state_name Existing Plant State Specifies an existing plant_state.
Component Integer Specifies which VARIABLE value should be
returned for the STATE_VALUE_FOR_PLANT
or STATE_VALUE_FOR_PLANT function.
1. You may identify a plant_state by typing its name or by picking it from the screen.
Since plant_state do not have a geometric position, Adams View displays plant_state icons at or near
the model origin. If the plant_state icon is not visible on the screen, you must type the name. You
may also find it convenient to type the name even if the plant_state icon is displayed.
If a plant_state is owned by the default model, you may identify it by entering only its name. If it is
not, you must enter its full name. To identify a plant_state under a different model, for instance, you
may need to enter the model name as well. For example, you may specify plant_state 'actual_velocity'
from model 'motor' by entering ".motor.actual_velocity'". If you type a "?", Adams View will list the
plant_state available by default.
You must separate multiple plant_state names by commas.
If the plant_state is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple plant_state picks by commas.
2. The COMPONENT is an integer indicating the kth VARIABLE in the list.
panel 117
panel set twindow_function step
For example, A PLANT_STATE is made up of a list of VARIABLES (algebraic expressions). The

COMPONENT parameter for the OUTPUT_VALUE_FOR_PLANT function is an integer
indicating the kth VARIABLE in the list. Therefore, if the PLANT_STATE is defined by a list of
ten VARIABLEs, and you request the 7th component to be returned, the

The STEP function approximates the HEAVERSINE step function with a cubic polynomial. The figure
illustrates the STEP function.
Figure 1. Step Function
The value x is the independent variable, x0 and x1 define the variable values at which the step begins and
ends, h0 and h1 are the initial value and the final value of the step. The equation that defines STEP is as
follows.
Format:
x= runtime function
begin_at= real
end_at= real
angular_begin_at= angle
angular_end_at= angle
initial_function_value= real
final_function_value= real
angular_initial_function_value= angle
angular_final_function_value= angle
Step5 = boolean
Description:

x Run Time Function Specifies a run time function
begin_at Real Specifies the non-angular value of "x" (the
independent variable) where the haversine function
begins. The BEGIN_AT parameter is represented
below as "x0"
end_at Real Specifies the non-angular value of "x" (the
ends. The END_AT parameter is represented below
as "x1"
angular_begin_at Angle Specifies the angular value of "x" (the independent
variable) where the haversine function begins. The
ANGULAR_BEGIN_AT parameter is represented
below as "x0"
angular_end_at Angle Specifies the angular value of "x" (the independent
variable) where the haversine function ends. The
ANGULAR_END_AT parameter is represented
below as "x1"
initial_function_value Real Specifies the non-angular value of "x" (the
independent variable) where the haversine function is
at its initial value. The
INITIAL_FUNTION_VALUE parameter is
represented below as "h0"
panel 119
panel set twindow_function sweep

final_function_value Real Specifies the non-angular value of "x" (the
has its final value. The
FINAL_FUNCTION_VALUE parameter is
represented below as "h1"
angular_initial_function_v Angle Specifies the angular value of "x" (the independent
alue variable) where the haversine function is at its initial
value. The
ANGULAR_INITIAL_FUNTION_VALUE
parameter is represented below as "h0"
angular_final_function_val Angle Specifies the angular value of "x" (the independent
ue variable) where the haversine function has its final
value. The
ANGULAR_FINAL_FUNCTION_VALUE
parameter is represented below as "h1"
Step5 Yes/No Specifies a Boolean value
Cautions:
1. The value x1 must not equal x0. Equal values of x1 and x0 imply a discontinuous step, which STEP
cannot fit.

The SWEEP function returns a constant amplitude sinusoidal function with linearly increasing frequency.
Format:
x= function
amplitude= real
start_value= real
start_frequency= real
end_value= real
end_frequency= real
delta_x= real
Example:
panel set twindow_function sweep &
panel set twindow_function sweep amplitude = 10 &
panel set twindow_function sweep start_value= 2 &
panel set twindow_function sweep start_frequency = 4 &
panel set twindow_function sweep delta_x = .01
Description:

x Function Specifies a real variable that is the independent variable of the function
amplitude Real Specify the amplitude of the sinusoidal function.
start_value Real Specifies the initial value of the variable.
start_frequency Real The initial frequency of the sinusoidal function
end_value Real Specifies the when the loop is done.
end_frequency Real The final frequency.
delta_x Real The interval in which the SWEEP function becomes fully active.
1. This variable can be any value of interest that you can compute using a function expression. For
example, if the independent variable in the function is time, x is the system variable TIME.
verification.
panel 121
Components Examples
NUMBERS
OPERATORS
SYSTEM CONSTANTS
BLANKS
• Adams does not accept a blank space between a function and its left bracket. (This is true for both,
CONTINUATION COMMAS
FUNCTION BUILDER
window.
SYSTEM VARIABLES
ARITHMETIC IFS
follows:
panel 123
FUNCTION = 6 * IF(VR(10,31): 0 , 0 , 100)
Adams FUNCTIONS
be accessed.
Names Purposes
panel set twindow_function theta
2. For each iteration of the loop, including the first, Adams View checks the value of START_VALUE
+ INCREMENT_VALUE. If the result is less than or equal to END_VALUE (or greater than or
equal to if INCREMENT_VALUE is negative) the loop is executed

The THETA function calculates the second angle of a body-2 [3 1 3] Euler rotation sequence, which will
orient the J_MARKER (i2) the same as the I_MARKER (i1).
Format:
Example:
panel set twindow_function theta &
Description:

I_marker_name Existing Marker Specifies an existing marker used as the
function.
J_marker_name Existing Marker Specifies an existing marker used as the
function.
If you created the marker by reading an data set or graphics file, the marker name is the letters MAR
followed by the data set marker ID number. For example, the name of MARKER/101 is MAR101.
If you created the marker during preprocessing, you will have given it a name at that time.
panel 125
panel set twindow_function tm
part 'lower_arm' by entering ".links.lower_arm.pivot". If you type a "?", /View will list the markers

The TM function returns the magnitude of the net torque acting at the I_MARKER (i1). You should omit
specification of the J_MARKER (i2) and the R_MARKER (i3) to find the magnitude of an action-only
torque acting at the I_MARKER (i1).
Format:
Example:
panel set twindow_function theta &
Description:

function.
function.
panel set twindow_function torque_vector
name at that time.

The TORQUE_VECTOR function returns a force COMPONENT for the TORQUE_VECTOR you
identify in the TORQUE_VECTOR_NAME
Format:
torque_vector_name= an existing vtorque
reference_marker= an existing marker
Example:
panel set twindow_function torque_vector &
panel 127
Description:

torque_vector_name An Existing Vtorque Specifies an existing torque_vector.
values
force element.
2. You may identify a torque vector by typing its name or by picking it from the screen.
If the torque vector is not visible on the screen, you must type the name. You may also find it
convenient to type the name even if the torque vector is displayed.
If you created the torque vector by reading an Adams data set or graphics file, the torque vector name
is the letters VTO followed by the Adams data set torque vector ID number. The name of Adams
VTORQUE/101 is VTO101, for example. If you created the torque vector during preprocessing,
you gave it a name at that time.
If a torque vector is available by default, you may identify it by entering its name only. If it is not,
you must enter its full name. To identify a torque vector under another model, for instance, you may
need to enter the model name as well. For example, you may specify torque vector 'spring' from the
model 'suspension' by entering ".suspension.spring". If you type a "?", Adams View will list the torque
You must separate multiple torque vector names by commas.
panel set twindow_function tx
system.
Tips:
1. If the torque vector is visible in one of your views, you may identify it by picking on any of the
2. You need not separate multiple torque vector picks by commas.

The TX function returns the x-component of the net torque acting at the I_MARKER (i1), as computed in
the coordinate system of the R_MARKER (i3). All force elements acting between the I_ and J_MARKERs
(i1 and i2) are included in the calculation of the torque, unless the force element is an action-only type of
force. The user should omit specification of the J_MARKER (i2) and the R_MARKER (i3), or specify it as
zero to find the x-component of an action-only torque element acting at the I_MARKER (i1).
Format:
r_marker_name= existing marker
Example:
panel set twindow_function tx &
r_marker_name = cm
panel 129
panel set twindow_function ty
Description:

R_marker_name Existing Marker Specifies the marker used as the R_MARKER (i3)
with respect to which you want Adams to evaluate
the function. If you do not supply this parameter,
Adams will evaluate the function in the ground
reference frame.
name at that time.

The TY function returns the y-component of the net torque acting at the I_MARKER (i1), as computed in
force. You should omit specification of the J_MARKER (i2) and the R_MARKER (i3), to find the y-
component of an action-only torque element acting at the I_MARKER (i1).
Format:
Example:
panel set twindow_function ty &
r_marker_name = cm
Description:

function.
function.
R_marker_name Existing Marker Specifies the marker used as the
R_MARKER (i3) with respect to which you
want Adams to evaluate the function. If you
do not supply this parameter, Adams will
evaluate the function in the ground reference
frame.
panel 131
panel set twindow_function tz

The TZ function returns the z-component of the net torque acting at the I_MARKER (i1), as computed in
force. You should omit specification of the J_MARKER (i2) and the R_MARKER (i3), to find the z-
component of an action-only torque element acting at the I_MARKER (i1).
Format:
Example:
panel set twindow_function tz &
r_marker_name = cm
panel set twindow_function variable_value
Description:

I_marker_name Existing Marker Specifies an existing marker used as the I_MARKER (i1) in the
J_marker_name Existing Marker Specifies an existing marker used as the J_MARKER (i2) in the
R_marker_name Existing Marker Specifies the marker used as the R_MARKER (i3) with respect to
which you want Adams to evaluate the function. If you do not
supply this parameter, Adams will evaluate the function in the
ground reference frame.

The VARIABLE_VALUE function returns the value of a VARIABLE you identify in the
VARIABLE_NAME parameter.
This function evaluates the VARIABLE and returns its value. A VARIABLE is defined as a scalar algebraic
equations. A VARIABLE can be used independently, or as part of the PLANT INPUT, PLANT OUTPUT,
or ARRAY elements. The computed value of the VARIABLE may depend on almost any Adams system
variable.
panel 133
panel set twindow_function vm
Format:
variable_name= existing solver variable
Example:
panel set twindow_function variable_value &
Description:

Variable_name Existing Solver Variable Specifies an existing variable.
by the Adams data set variable ID number. For example, the name of Adams VARIABLE/101 is
VAR101. If you created the variable during preprocessing, you will have given it a name at that time.
If a variable is owned by the default model, you may identify it by entering only its name. If it is not,
If the variable is visible in one of your views, you may identify it by picking on any of the graphics
associated with it.
You need not separate multiple variable picks by commas.

The VM function calculates the magnitude of the translational velocity vector of the I_MARKER (i1) with
respect to the J_MARKER (i2).
Format:
Example:
panel set twindow_function vm &
i_marker_name marker_1 &
j_marker_name marker_2
Description:

I_marker_name An Existing Marker Specifies an existing marker used as the I_MARKER
J_marker_name An Existing Marker Specifies an existing marker used as the J_MARKER
Reference_frame_marker An Existing Marker
1. Mathematically, VM is calculated as follows:
VM = ( [ Vi1 - Vi2] dot_product_of [ Vi1 - Vi2] )**1/2
where Vi1 is the velocity of the I_MARKER (i1) in ground, and Vi2 is the velocity of the
J_MARKER (i2) in ground.
time.
panel 135
panel set twindow_function vr
Tips:

The VR function calculates the radial (relative) velocity of the I_MARKER (i1) with respect to the
J_MARKER (i2).
Format:
Example:
panel set twindow_function vr &
Description:

I_marker_name An Existing Specifies an existing marker used as the I_MARKER (i1)
Marker in the evaluation of the function.
J_marker_name An Existing Specifies an existing marker used as the J_MARKER (i2)
Reference_frame_marker An Existing
Marker
1. Mathematically, VR is calculated as follows:
VM = ( [ Vi1 - Vi2] dot_product_of [ Ri1 - Ri2] ) / DM(i1,i2)
panel set twindow_function vx
where Vi1 is the velocity of the I_MARKER (i1) in ground, Vi2 is the velocity of the J_MARKER
(i2) in ground, Ri1 is the displacement of the I_MARKER (i1) with respect to the global origin, Ri2
is the displacement of the J_MARKER (i2) with respect to the global origin, and DM(i1,i2) is the
distance between markers i1 and i2. When the I_MARKER (i1) and the J_MARKER (i2) are
separating from each other, VR is positive. VR is negative when the I_MARKER (i1) and the
J_MARKER (i2) are approaching each other.
time.
Tips:

The VX function returns the x-component of the difference between the global velocity vector of the
I_MARKER (i1) and the global velocity vector of the J_MARKER (i2) as computed in the coordinate system
of the R_MARKER (i3).
Format:
panel 137
Example:
panel set twindow_function vx &
Description:

I_marker_name An Existing Specifies an existing marker used as the I_MARKER (i1) in
Marker the evaluation of the function.
J_marker_name An Existing Specifies an existing marker used as the J_MARKER (i2) in
R_marker_name An Existing Specifies the marker used as the R_MARKER (i3) with
Marker respect to which you want Adams to evaluate the function.
Marker
1. Mathematically, VX is calculated as follows:
VX = [ Vi1 - Vi2] dot_product_with xi3
(i2) in ground, and xi3 is the unit vector along the x-axis of the R_MARKER (i3).
time.
panel set twindow_function vy
Tips:
2. If you do not supply the the r_marker_name parameter, Adams will evaluate the function in the

The VY function returns the y-component of the difference between the global velocity vector of the
Format:
Example:
panel set twindow_function vy &
Description:

Marker respect to which you want Adams to evaluate the
function.
Marker
1. Mathematically, VY is calculated as follows:
panel 139
panel set twindow_function vz
VY = [ Vi1 - Vi2] dot_product_with yi3

(i2) in ground, and yi3 is the unit vector along the y-axis of the R_MARKER (i3) .
time.
Tips:

The VZ function returns the z-component of the difference between the global velocity vector of the
Format:
Example:
panel set twindow_function vz &
Description:

Marker respect to which you want Adams to evaluate the
function.
Marker
1. Mathematically, VZ is calculated as follows:
VZ = [ Vi1 - Vi2] dot_product_with zi3
(i2) in ground, and zi3 is the unit vector along the z-axis of the R_MARKER (i3) .
time.
panel 141
panel set twindow_function wx
Tips:

The WX function returns the x-component of the difference between the angular velocity vector of the
I_MARKER (i1) in ground and the angular velocity vector of the J_MARKER (i2) in ground, as computed
in the coordinate system of the R_MARKER (i3)
Format:
r_marker_name= an existing marker
Example:
panel set twindow_function wx &
Description:

i_marker_name An Existing Marker Specifies an existing marker used as the
I_MARKER (i1) in the evaluation of the function.
j_marker_name An Existing Marker Specifies an existing marker used as the
J_MARKER (i2) in the evaluation of the function.
r_marker_name An Existing Marker Specifies the marker used as the R_MARKER (i3)
the function.
1. Mathematically, WX is calculated as follows:
WX = [wi1 - wi2] dot_product_with xi3
where wi1 is the angular velocity vector of the I_MARKER (i1) in ground, wi2 is the angular velocity
vector of the J_MARKER (i2) in ground, and xi3 is the unit vector along the x-axis of the
R_MARKER (i3) .
panel set twindow_function wy
time.
time.
Tips:

The WY function returns the y-component of the difference between the angular velocity vector of the
in the coordinate system of the R_MARKER (i3)
panel 143
Format:
Example:
panel set twindow_function wy &
Description:

i_marker_name An Existing Marker Specifies an existing marker used as the I_MARKER
j_marker_name An Existing Marker Specifies an existing marker used as the J_MARKER
r_marker_name An Existing Marker Specifies the marker used as the R_MARKER (i3)
the function.
1. Mathematically, WY is calculated as follows:
WY = [wi1 - wi2] dot_product_with yi3
vector of the J_MARKER (i2) in ground, and yi3 is the unit vector along the y-axis of the
R_MARKER (i3) .
time.
panel set twindow_function wz
time.

The WZ function returns the z-component of the difference between the angular velocity vector of the
in the coordinate system of the R_MARKER (i3).
Format:
Example:
panel set twindow_function wz &
panel 145
Description:

function.
function.
r_marker_name An Existing Marker Specifies the marker used as the R_MARKER
(i3) with respect to which you want Adams to
evaluate the function.
1. Mathematically, WZ is calculated as follows:
WZ = [wi1 - wi2] dot_product_with zi3
vector of the J_MARKER (i2) in ground, and zi3 is the unit vector along the z-axis of the
R_MARKER (i3) .
time.
time.
panel set twindow_function x_acc
Tips:

The X_ACC function returns the x-component of the difference between the global acceleration vector of
the I_MARKER (i1) and the global acceleration vector of the J_MARKER (i2) as computed in the
coordinate system of the R_MARKER (i3)
Format:
Example:
panel set twindow_function x_acc &
panel set twindow_function dm i_marker_name= marker_71 &
panel 147
Description:

function.
function.
1. Mathematically, X_ACC is calculated as follows:
X_ACC = [ ai1 - ai2] dot_product_with xi3
where ai1 is the velocity of the I_MARKER (i1) in ground, ai2 is the velocity of the J_MARKER (i2)
in ground, and xi3 is the unit vector along the x-axis of the R_MARKER (i3) .
time.
panel set twindow_function x_wdt
time.
Cautions:
1. You must separate multiple marker names by commas.
Tips:

The X_WDT function returns the x-component of the difference between the angular acceleration vector of
the I_MARKER (i1) in ground and the angular acceleration vector of the J_MARKER (i2) in ground, as
computed in the coordinate system of the R_MARKER (i3).
Mathematically, X_WDT is calculated as follows:
X_WDT = [i1 - i2] dot_product_with xi3
where wdoti1 is the angular acceleration vector of the I_MARKER (i1) in ground, wdoti2 is the angular
acceleration vector of the J_MARKER (i2) in ground, and xi3 is the unit vector along the x-axis of the
R_MARKER (i3) .
Format:
reference_frame_marker= an existing marker
panel 149
Example:
panel set twindow_function x_wdt &
Description:

Reference_frame_marker Existing marker Specifies the reference frame marker.
R_marker_name Existing marker Specifies the marker used as the R_MARKER (i3)
reference frame.
time.
panel set twindow_function y_acc

The Y_ACC function returns the y-component of the difference between the global acceleration vector of
Format:
Example:
panel set twindow_function y_acc &
panel set twindow_function dm j_marker_name = marker_82 &
panel set twindow_function x_acc reference_frame_marker = marker_74
Description:

function.
function.
1. Mathematically, Y_ACC is calculated as follows:
Y_ACC = [ ai1 - ai2] dot_product_with yi3
where ai1 is the acceleration of the I_MARKER (i1) in ground, ai2 is the acceleration of the
J_MARKER (i2) in ground, and yi3 is the unit vector along the y-axis of the R_MARKER (i3) .
panel 151
panel set twindow_function y_wdt
time.
time.
Cautions:
Tips:

The Y_WDT function returns the y-component of the difference between the angular acceleration vector of
computed in the coordinate system of the R_MARKER (i3). Mathematically, Y_WDT is calculated as
follows:
Y_WDT = [i1 - i2] dot_product_with yi3
where i1 is the angular acceleration vector of the I_MARKER (i1) in ground, i2 is the angular acceleration
vector of the J_MARKER (i2) in ground, and yi3 is the unit vector along the x-axis of the R_MARKER (i3) .
Format:
reference_frame_marker= an existing marker
Example:
panel set twindow_function y_wdt &
Description:

reference frame.
panel 153
panel set twindow_function yaw
time.

The YAW function calculates the first angle of a body-3 [3 -2 1] Euler rotation sequence which will orient
the J_MARKER (i2) the same as the I_MARKER (i1). Note that mathematically YAW is the same as AZ.
Format:
Example:
panel set twindow_function yaw &
i_marker_name = origin &
j_marker_name = cm
Description:

I_MARKER_NAME An Existing Specifies an existing marker used as the I_MARKER (i1) in
J_MARKER_NAME An Existing Specifies an existing marker used as the J_MARKER (i2) in
panel set twindow_function z_acc
time.

The Z_ACC function returns the z-component of the difference between the global acceleration vector of
Format:
Example:
panel set twindow_function z_acc &
panel set twindow_function dm j_marker_name = marker_82 &
panel set twindow_function x_acc reference_frame_marker = marker_74
panel 155
Description:

function.
function.
(i3) with respect to which you want adams to
1. Mathematically, Z_ACC is calculated as follows:
Z_ACC = [ ai1 - ai2] dot_product_with zi3
where ai1 is the acceleration of the I_MARKER (i1) in ground, ai2 is the acceleration of the
J_MARKER (i2) in ground, and zi3 is the unit vector along the z-axis of the R_MARKER (i3) .
If you created the marker by reading an adams data set or graphics file, the marker name is the letters
MAR followed by the adams data set marker ID number. The name of adams MARKER/101 is
time.
panel set twindow_function z_wdt
If you created the marker by reading an adams data set or graphics file, the marker name is the letters
MAR followed by the adams data set marker ID number. The name of adams MARKER/101 is
time.
4. If you do not supply this parameter, adams will evaluate the function in the ground reference frame.
Cautions:
Tips:

The Z_WDT function returns the z-component of the difference between the angular acceleration vector of
computed in the coordinate system of the R_MARKER (i3). Mathematically, Z_WDT is calculated as
follows:
Z_WDT = [i1 - i2] dot_product_with zi3
where i1 is the angular acceleration vector of the I_MARKER (i1) in ground, i2 is the angular acceleration
vector of the J_MARKER (i2) in ground, and zi3 is the unit vector along the x-axis of the R_MARKER (i3) .
Format:
R_marker_name = existing marker
Reference_frame_marker= an existing marker
panel 157
Example:
panel set twindow_function z_wdt &
Description:

with respect to which you want to evaluate the
function. If you do not supply this parameter, will
evaluate the function in the ground reference
frame.
If you created the marker by reading an data set or graphics file, the marker name is the letters MAR
followed by the data set marker ID number. The name of MARKER/101 is MAR101, for example.
If you created the marker during preprocessing, you gave it a name at that time.
f a marker is available by default, you may identify it by entering its name only. If it is not, you must
part 'lower_arm' by entering ".links.lower_arm.pivot". If you type a "?", /View will list the markers
part 1
part attributes
part
part attributes
Allows you to set attributes for a part:
 Size or scale of icons - You can set a size of the icon used to represent the part in modeling units, or
you can scale its size by a non-unit scale factor.
 Visibility - You can set a part's visibility to on or off, or toggle its current setting. When you set a
part's visibility off, the part will not be drawn and all markers and geometry belonging to the part are
turned off. When you set a part's visibility on, you allow the entire part to be drawn.
 Name Visibility - You can set the visibility of the part's name label to on or off, or toggle its the
current setting.
 Color - You can set the color of the part. You can also set the scope of the color using entity scope to
limit the application of the color. For example, you can set the scope of the color to only edges.
If an entity does not have a particular attribute setting, it can inherit that from another entity. Inheritance
can be either top down or bottom up. Top down refers to the natural hierarchy of an Adams model. The
hierarchy is a tree structure with the model at the apex. Parts exist beneath the model, and markers exist
beneath the parts
For example, if the icon size of the model is set to 0.1, and the default inheritance is set to top down, then all
icons displayed within the model are displayed at this size. However, if the icon size of a model is set to 0.1,
and the default inheritance is set to bottom up, then any icons set to a size other than the model's icon size
are displayed at their own size.
Format:
part attributes
flexible_body_name = existing flex body
external_system_name = existing external system
equation_name = existing equation
fe_node_name = existing FE_Node
part attributes
part attributes
Example:
part attributes &
size_of_icons = .125 &
color = red &
visibility = on &
entity_scope = fill_color
Description:

part_name Existing Part Specifies the rigid body to be modified
flexible_body_name Existing Flex Body Specifies the flexible body to be modified
external_system_name Existing external system Specifies an external system to be modified
point_mass_name Existing Point Mass Specifies the point mass to be modified
equation_name Existing Equation Specifies the equation to be modified
fe_node_name Existing FE_Node Specifies the FE_Node to be modified
scale_of_icons Real Specifies the amount by which you want to
scale the icons.
size_of_icons(Mutually Length Specifies the size, in modeling units, the
exclusive with scale_of_icons) Adams View icons will appear.
visibility On/off/toggle Specifies the visibility of the part in a view:
 on - The part is visible.

 off - The part is invisible.
 toggle - Reverses the current state of the
part's visibility.
name_visibility On/off/toggle Specifies whether or not you want the name
of the part displayed in the view
color Existing Color Specifies the color of the part.
part 3
part attributes

entity_scope Controls how a color modification is to
affect a particular graphic entity.
Active On/off/no_opinion Sets the activation status of the part during a
simulation.
dependents_active See explanation for active parameter.
1. The scale factor is relative to the current size set. If no initial size is specified for Adams View icons,
the default size is one modeling LENGTH unit. For example, if the modeling units are K/M/S, a part
axes icon has triad legs of one meter in length.
When you specify scale_of_icons, Adams View calculates a new size by multiplying the current size
by the scale, and storing the product as the new icon size.
2. For the size_of_icon parameter, if no initial size is specified for Adams View icons, the default size is
one modeling LENGTH unit. For example, if the modeling units are K/M/S, a part axes icon has
triad legs of one meter in length.
Example:
When you set size_of_icons at the model level, all Adams View icons used in creating a model use the
size specified. If the model has a size_of_icons set, and a part under that model has a different
size_of_icons, the model's size_of_icons takes precedence.
if the following: are set to:

.model size_of_icons = .125 meters
.part size_of_icons = .15 meters
the part's icon is .125 meters in size
Example:
If the model has size_of_icons of set to 0.0, and a part under that model has a size_of_icons set to
.125, the part's icon size is used.

.model size_of_icons = 0.0 meters
.part size_of_icons = .125 meters
the part's icon is .125 meters in size
part attributes
3. You can specify any color in the modeling database and no_color. If you specify no_color, Adams
View uses the default color for this entity if there is no color present in its parent modeling entity.
Example 1:
In the following example, the geometry (circle) will be red because its parent part is set to red and it
is set to no_color.

.model no_color
.part red
then the geometry is red.
Example 2:
In the following example, the circle will be red because if a parent modeling entity has a color
previously specified, that color takes precedence. Adams View issues a warning message about color
precedence.

.model no_color
.part red
.geometry(circle) blue
then the geometry is red.
Example 3:
In this example, the parents of the geometry (circle) have no colors set, so the color of the geometry
takes precedence.

.model no_color
.part no_color
.geometry(circle) blue
then the geometry is blue.
4. The values for the entity_scope parameter are:

• fill_color - Applies color to those areas of a graphic that can be shaded (including, sides of a
cylinders, frustums, boxes, and so on).
part 5
part copy
• edge_color - Applies color to lines making up the edges of the facets (or areas filled by the
fill_color) of a graphic that can be shaded.
• outline_color - Applies color to lines that define the outline of graphics, which cannot be shaded
or filled, such as two points defining an outline using the GRAPHICS statement or the coil of a
spring-damper.
• text_color - Applies color to the text associated with the part (its name).
• all - Applies all three entity types: fill_color, edge_color, and outline_color to the graphic entity.
entity_scope is optional and if you do not enter it, the default is set to fill_color.
5. The active parameter can take the following values: yes - The part is active. no - The part is written
to the dataset as a comment.
• no_opinion - The part inherits the activation status of its parent.
When you set the active attribute on an object, you are also setting it on the children of the object. If
you set active=no on a part, but want the marker on that part to be on, then you must explicitly set
active=yes on the marker, after setting activation on the part.
The dependents_active parameter acts in the same way, but sets the active attribute for the dependents,
all the way down the dependency chain. For example, if you execute the following command:
• where, PAR1 has a marker MAR1, which is the I marker of a joint JOI1 (which has a J marker
MAR2), then JOI1 will be deactivated.
• Also, if the joint JOI1 is referenced in a request function, or if the I marker is referenced by a
request, then the request will be deactivated.
changed individually.
• Group
• Part
• Differential equation
• Marker
• Geometry
• Constraints
• Forces
• Data elements
• Output control
part copy
Allows you to create a copy of an existing part (rigid body, equation, flexible body, point mass) within the
same model.
part copy
The copy is identical to the original with the exception of the part name. Parts must have unique names
relative to other parts in a given model. The replica is completely independent of the original, and you can
modify it without affecting the original.
All modeling entities under the original part will be copied to the replica, using the same names.
Because the parts have different names, markers under the two parts can have the same names.
Format:
part copy
part_name = existing part name
new_part_name = name of new rigid body
new_flexible_body_name = new flex body
point_mass_name = new point mass
new_point_mass_name = existing point mass
equation_name = new equation
new_equation_name = existing equation
Example:
part copy &
new_part_name = part_3_copy
Description:

part_name Existing Part Specifies the name of the rigid body to be copied
new_part_name New Part Specifies the name of the new rigid body. You can use
this name later to refer to this part.
view_name Existing View Specifies the view in which to display a part. You
must associate a view with each part you are copying.
flexible_body_name Existing Flex Body Specifies the name of the flexible body to be copied
new_flexible_body_name New Flex Body Specifies the name of the new flexible body. You can
use this name later to refer to this part.
point_mass_name Existing Point Mass Specifies the name of the point mass to be copied
part 7
part create equation differential_equation

new_point_mass_name New Point Mass Specifies the name of the new point mass. You can
use this name later to refer to this part.
equation_name Existing Equation Specifies the name of the equation to be copied
new_equation_name New Equation Specifies the name of the new equation. You can use
this name later to refer to this part.
1. Adams View does not allow you to have two parts with the same name, so you must provide a unique
name.
2. You can identify a view by typing its name or by picking it from the screen. In most cases, you can
enter the special view name all, which means all the views currently displayed.
commas.

Allows you to create or modify a user-defined differential equation.
A differential equation creates a user-defined state variable and defines a first-order differential equation that
describes it. The equation can be dependent on any Adams Solver state variable available in a function
expression except point-curve and 2D curve-curve constraints. You can create systems of differential
equations using more than one differential equation, linear state equation, or general state equation.
Both, Adams FUNCTION expressions and user-written subroutines, can access the user-defined state
variables and their derivatives.
FUNCTION expressions access the values by using the function DIF(i1) and the derivatives by using
DIF1(i1). In each case, i1 specifies the ADAMS_ID of the differential equation that defines the variable.
User-written subroutines access the values and derivatives by calling the subroutine, DEQINF.
You describe the variable in a differential equation either by writing a function expression or user-written
subroutine. Because it is easier to write function expressions than subroutines, you should use function
expressions whenever possible to describe user-defined differential variables.
The equation defined by a FUNCTION expression or by a user-written subroutine may be in either explicit
or implicit form. The following equation defines the explicit form of a differential equation:
y' = f (y, q, q', t)
In this equation, y' is the derivative of the user-defined state variable, y is the user-defined state variable itself,
and q is a vector of Adams-defined state variables. If you cannot solve for the first derivative of the state
variable, you need to use the implicit form. The following equation defines the implicit form of a differential
equation:
0 = F (y, y', q, q', t)
Format:
differential_equation_name= new equation
adams_id= integer
comments= string
initial_condition= real
no_initial_condition= true_only
function= function
user_function= real
static_hold= on/off
implicit= on/off
routine = string
Description:

differential_equation_name New Equation Specifies the name of the equation to be created or
modified
adams_id Integer Assigns a unique ID number to the equation.
Comments String Adds any comments about the equation to help you
initial_condition Real Specifies the initial value of the differential equation at the
start of the simulation.
no_initial_condition True_only Unsets the velocity initial condition for the specified
equation (true) so it no longer has a velocity initial
condition.
Function Function Specifies a function expression or defines and passes
constants to a user-written subroutine to define the
differential equation.
user_function Real Specifies up to 30 values for Adams Solver to pass to a
subroutine DIFSUB.
static_hold On/off Indicates that equation states are not permitted to change
during static and quasi-static simulations (on).
Implicit On/off Indicates that the function expression or subroutine
defines the implicit form of the equation (on).
part 9
when entering it.
be assigned to it.
3. Initial_condition parameter may also specify in case of definition of an implicit equation, an
approximate value of the initial time derivative of the differential equation at the start of the
simulation. (You do not need to supply a second value when you enter an explicit equation because
Adams Solver can compute the initial time derivative directly from the equation.)
Adams Solver might adjust the value of the time derivative when it performs an initial conditions
simulation. Entering an initial value for the time derivative helps Adams Solver converge to a desired
initial conditions solution.
4. Remember, leaving a velocity unset lets Adams View calculate the velocity of the part during an initial
conditions simulation, depending on the other forces and constraints acting on the part. It is not the
same as setting the initial velocity to zero.
5. Adams View treats the function parameter as a series of literal strings. When you write an Adams
Solver dataset, Adams View writes these strings, just as you enter them here, after the 'FUNCTION='
argument.
If you want to define the equation with an expression, enclose the expression in quotes and enter it
just as you would in the dataset.
If you want to define the equation with a user-written subroutine, enter the character string
"USER(r1[,...,r30])", where r1[,...,r30] are the values you want Adams Solver to pass to your user-
written subroutine DIFSUB. For example, if you enter "USER(1.,2.,3.)", Adams Solver calls your
DIFSUB with values 1, 2, and 3. For more information, see the Adams Solver Subroutines online
help
6. Many Adams Solver statements and commands feature the construct

FUNCTION=USER(r1,r2,...,r30), which specifies that Adams Solver is to obtain element
characteristics by loading and calling a specific user subroutine from a specific library of user
subroutines. For example, Adams Solver calls the SFOSUB subroutine for the SFORCE statement.
The ROUTINE argument allows you to optionally specify an alternative library and user subroutine
name for some or all elements.
The ROUTINE argument takes a string argument:
ROUTINE=libname::subname
The delimiter, ::, is required to separate the library name from the subroutine name. Both the libname
and the subname are optional, but the :: delimiter is required to distinguish the library name. For
example, to specify that a different subroutine name, mysfo, is to be loaded from the default
subroutine library (the library that was mentioned when Adams Solver was run in run-user mode),
you should write:
ROUTINE=mysfo
or
ROUTINE=::mysfo
If the default name (for example SFOSUB for SFORCE) is acceptable but the user subroutine is to
be loaded from a library 'mylib', you must write:
ROUTINE=mylib::
The table below lists the default names for user subroutines for Adams Solver statements and
commands.
Statement/Command Default User Subroutine

MOTION MOTSUB
FIELD FIESUB
SFORCE SFOSUB
STORQUE SFOSUB
MFORCE MFOSUB
GFORCE GFOSUB
VFORCE VFOSUB
VTORQUE VTOSUB
VARIABLE VARSUB
DIFF DIFSUB
SENSOR SENSUB
SENSOR SEVSUB
REQUEST REQSUB
part 11
Statement/Command Default User Subroutine

CURVE CURSUB
SURFACE SURSUB
CONTROL CONSUB
COUPLER See the COUPLER and GSE section below.
GSE See the COUPLER and GSE section below.
Note: The subroutine specified by the ROUTINE argument must have the same argument list
as the default subroutine. Only the name is changed. Failure to satisfy this requirement
results in unpredictable runtime failure.
Just like many elements of a particular type can share the default user subroutine, many elements may
share an alternative user subroutine. In other words, a group of your SFORCE elements may use the
SFOSUB in the default library while a different group of SFORCE elements is using mylib::mysfo.
You can either fully qualify the name and location of the library or rely on Adams Solver to search for
the library using predefined rules. For example, ROUTINE argument can specify absolute paths:
ROUTINE=/home/jdoe/mylibs/libsforces.so::sfo312
or relative paths with abbreviated library names:
ROUTINE=mylibs/sforces::sfo312
In the latter case, you would be relying on Adams Solver knowing to search in /home/jdoe (see the
PREFERENCES statement (C++ or FORTRAN) for details about the library search path) and built-
in search-rules that first look for the specified name, and failing that, try to prepend the lib prefix and
an architecture specific suffix (.dll on the Microsoft Windows platform, .sl on the HP-UX platform
and .so on other Linux platforms and Linux).
COUPLER and GSE
The COUPLER and GSE elements deserve special mention because they require more than one user
subroutine.
The COUPLER element requires that three subroutines be provided. This is handled by providing a
comma separated list of three libname::subname pairs, for example:
ROUTINE=lib1::cou1, lib2::cou2, lib3::cou3
where lib1, lib2, and lib3 can be three different libraries. The default names for these subroutines are
COUSUB,COUXX,COUXX2, in that order.
The GSE case is further complicated by the fact that the GSE subroutine interface has recently been
redesigned and the ROUTINE argument had been previously reserved to address the now deprecated
GSESUB interface. To specify the new GSE_DERIV, GSE_OUTPUT, GSE_UPDATE,
GSE_SAMP subroutines for GSE, use the INTERFACE argument:
INTERFACE=lib1::gse1,lib2::gse2,lib3::gse3,lib4::gse4
part create equation linear_state_equation
to specify the subroutines that default to GSE_DERIV, GSE_OUTPUT, GSE_UPDATE,

GSE_SAMP, in that order. You can specify deprecated GSE subroutine interface using:
ROUTINE=lib1::gse1,lib2::gse2,lib3::gse3,lib4::gse4,lib5::gse5
to specify the subroutines that default to GSESUB, GSEXX, GSEXU, GSEYX, GSEYU, in that
order.
1. The user-specified initial conditions are retained as the static equilibrium values. Note that this does
not guarantee that the time derivatives of the user-defined variable will be zero after static analysis.
2A0D0210000000

Allows you to create a linear_state_equation.
Format:
linear_state_equation_name = a new lse
adams_id = adams_id
comments = string
x_state_array_name = an existing array
u_input_array_name = an existing array
y_output_array_name = an existing array
ic_array_name = an existing array
a_state_matrix_name = an existing matrix
b_input_matrix_name = an existing matrix
c_output_matrix_name = an existing matrix
d_feedforward_matrix_name = an existing matrix
static_hold = on_off
Example:
part create equation linear_state_equation &
linear_state_equation_name = lse__1 &
adams_id = 10 &
comments = "a new lse" &
x_state_array_name = array__1 &
a_state_matrix_name = matrix__1
part 13
Description:

linear_state_equation_name A New Lse Specifies the name of the new
linear_state_equation.
adams_id Adama_Id Specifies an integer used to identify this element in
modified.
x_state_array_name An Existing Array Specifies the array in the model which will be used
as the state array for this linear system.
u_input_array_name An Existing Array Specifies the array name in the current model
which will be used as the input (or control) array
for this linear system
(LINEAR_STATE_EQUATION).
y_output_array_name An Existing Array Specifies the array name in your model which will
be used as the output array for this linear system
(LINEAR_STATE_EQUATION)
ic_array_name An Existing Array Specifies the array in the model which will be used
as the initial conditions array for this linear system
a_state_matrix_name An Existing Matrix Specifies the matrix in the model which is used as
the state matrix for this linear system
b_input_matrix_name An Existing Matrix Specifies the matrix in the model which is used as
the control matrix for this linear system
c_output_matrix_name An Existing Matrix Specifies the matrix in the model which is used as
the output matrix for this linear system
d_feedforward_matrix_name An Existing Matrix Specifies the matrix in your model which is used as
the feedforward matrix for this linear system
static_hold On_Off Indicates that equation states are not permitted to
change during static and quasi-static analysis.
1. The LINEAR_STATE_EQUATION is used, along with associated arrays and matrices statements,
to define a system of constant coefficient, explicit, differential, and algebraic equations in the classic
state-space format.
The Linear State Equation (LSE) is designed to model a linear, time-invariant control system defined
in the state space, especially to facilitate importing of controllers developed in with external software.
It can be used, however, to define any arbitrary set of coupled constant-coefficient differential and
algebraic equations which can be expressed in matrix notation as:
| dX/dt | | A | B | |X|
< ----- > = | ----- | < - >
| Y | | C | C | |U|
where, at least the A matrix must be non-zero. The LINEAR_STATE_EQUATION follows standard
control systems terminology, where X is the state vector, Y is the output vector, U is the input vector
and IC is the initial condition vector, X(t=0). In the Adams data set, each of these vectors is defined
using an ARRAY. Similarly, A is the state matrix, B is the control matrix, C is the output matrix, and
D is the feedforward matrix. Each of these matrices is defined using a MATRIX. All MATRIX and
ARRAY sizes must be conformable as required by the above equation. ARRAYs with zero-length and
zero-sized matrices should not be defined; Adams will correctly formulate the system equations based
on those ARRAYs and MATRIXs which do exist.
2. You may use this name later to refer to this linear_state_equation. Adams View will not allow you to
have two linear_state_equations with the same name, so you must provide a unique name.
be assigned to it.
yourself.
part 15
5. The user must have an array with the name specified by the x_array_name parameter, in their model
and it may not be used in any other LINEAR_STATE_EQUATION,
GENERAL_STATE_EQUATION or TRANSFER_FUNCTION.
6. When the Y_OUTPUT_ARRAY_NAME parameter is used, the user must have an array with this
name in the model and it may not be used in any other LINEAR_STATE_EQUATION,
GENERAL_STATE_EQUATION or TRANSFER_FUNCTION.
When the Y_OUTPUT_ARRAY_NAME parameter is used, the user must also include a
C_OUTPUT_MATRIX or D_FEEDFORWARD_MATRIX name, or both, in the
LINEAR_STATE_EQUATION definition, and these matrices must have the same number of rows
as there are elements in the Y_OUTPUT_ARRAY_NAME.
7. When the IC_ARRAY_NAME parameter is used, the user must have an array with this name in their
model and it must have the same number of elements as the X_STATE_ARRAY (equal to the
number of rows in the A_STATE_MATRIX). When no IC array is specified for a
LINEAR_STATE_EQUATION, all states are initialized to zero.
8. The user must have a MATRIX with this name in their model, it must be a square matrix (same
number of rows and columns) and it must have the same dimension as the X_STATE_ARRAY. If
the user has specified an inconsistent size for the X_STATE_ARRAY, Adams will issue a warning
message and automatically resizes the X_STATE_ARRAY to match the A_STATE_MATRIX.
9. When the B_INPUT_MATRIX_NAME parameter is used, the user must also include a
U_INPUT_ARRAY_NAME parameter in the LINEAR_STATE_EQUATION definition. You
must have a matrix with this name in your model. This matrix must have the same number of rows
as the A_STATE_MATRIX and the same number of columns as the number of elements in the
U_INPUT_ARRAY.
10. When the C_OUTPUT_MATRIX parameter is used, you must also include a
Y_OUTPUT_ARRAY parameter in the LINEAR_STATE_EQUATION definition. You must have
a matrix with this name in your model. This matrix must have the same number of columns as the
A_STATE_MATRIX and the same number of rows as the number of elements in the
Y_OUTPUT_ARRAY.
11. When the D_FEEDFORWARD_MATRIX_NAME parameter is used, you must also include both
Y_OUTPUT_ARRAY_NAME and U_INPUT_ARRAY_NAME parameters in the
LINEAR_STATE_EQUATION definition. You must have a matrix with this name in your model.
This matrix must have the same number of rows as the number of elements in the
Y_OUTPUT_ARRAY and the same number of columns as the number of elements in the
U_INPUT_ARRAY.
part create equation transfer_function
12. The user specified initial conditions are retained as the static equilibrium values. Note that this does
not guarantee that the time derivatives of the user-defined variable will be zero after static analysis.

Allows you to create or modify a user-defined transfer function.
You can use transfer functions to define an arbitrary set of constant-coefficient, differential and algebraic
equations that can be expressed in the Laplace domain as the following where m k:
Transfer functions are especially useful for describing elements from control-system block diagrams. The
characteristic equation for a single transfer function can be a polynomial of degree less than 30.
Internal to Adams Solver, there is an algorithm to automatically convert the list of fixed numerator and
denominator coefficients to the following elements:
 Canonical state-space form
 Set of coupled, linear, constant-coefficient differential equations
 Single algebraic equation
You define the arrays for a transfer function using array data elements. The arrays define the transfer function
input and let you reference the states and output of the transfer function. Initial conditions for a transfer
function are assumed to be identically zero.
Format:
transfer_function_name= new tfsiso
adams_id= integer
comments= string
x_state_array_name= existing array
u_input_array_name= existing array
y_output_array_name= existing array
ic_array_name= existing adams array
static_hold= on_off
numerator_coefficients= real
denominator_coefficients= real
part 17
Description:

transfer_function_name New TFSISO Specifies the name of the equation to be created or
modified
adams_id Integer Assigns a unique ID number to the equation.
comments String Adds comments about the equation to help you
x_state_array_name Existing Array Specifies the array that defines the state variable
array for the transfer function.
u_input_array_name Existing Array Specifies the array that defines the input (or
control) for the transfer function. The array must
be an inputs (U) array. If you specified the size of
the array when you created it, it must be one.
y_output_array_name Existing Array Specifies the array that defines the output for the
transfer function.
static_hold On/off Indicates that equation states are not permitted to
change during static and quasi-static simulations
(on).
numerator_coefficients Real Specifies the coefficients of the polynomial in the
numerator of the transfer function.
denominator_coefficients Real Specifies the coefficients of the polynomial in the
denominator of the transfer function.
Ic_array_name Existing Adams Array Specifies an existing Adams array.
when entering it.
part create external_system initial_velocity
be assigned to it.
Comments:
For comments, you can enter any alphanumeric characters. The comments that you create appear in the
Information window when you select to display information about the object, in the Adams View log file and
in a command or dataset file when you export your model to these types of files. (Note that design variables
are not output to datasets; therefore, neither are their comments.)
1. The array specified in the x_state_array_name must be a states (X) array, and it cannot be used in any
other linear state equation, general state equation, or transfer function. If you specified the size of the
array when you created it, it must be one less than the number of coefficients in the denominator.
2. The array specified in the y_state_array_name must be an outputs (Y) array, and it cannot be used in
any other linear state equation, general state equation, or transfer function. If you specify the size of
the array when you created it, its size must be one.
3. For the static_hold parameter, the user-specified initial conditions are retained as the static
equilibrium values. Note that this does not guarantee that the time derivatives of the user-defined
variable will be zero after static analysis.
During a static simulation, Adams Solver finds equilibrium values for user-defined differential
variables (differential equations, general state equations, linear state equations, and transfer
functions), as well as for the displacement and force variables. The equilibrium values it finds change
the initial conditions for subsequent simulations. To help you control the static simulation results,
Adams View provides an option that you can set to keep the values constant. This option is called
static hold. Static hold retains the user-specified initial conditions as the static equilibrium values.
If you do not set static hold, Adams Solver sets the time derivatives of the user-defined variables to
zero during a static simulation, and uses the user-supplied initial-condition values only as initial
guesses for the static solution. Generally, the final equilibrium values are not the same as the initial
condition values. Adams Solver then uses the equilibrium values of the user-defined variables as the
initial values for any subsequent simulation, just as with the equilibrium displacement and force
values.
If you do set static hold, Adams Solver retains the user-specified initial conditions as the static
equilibrium values. Therefore, the final equilibrium values are the same as the user-specified initial
conditions. Note that this does not guarantee that the time derivatives of the user-defined variable are
zero after a static simulation.
4. For the numerator_coefficients and the denominator_coefficients, list the coefficients in order of
ascending power of s, starting with s to the zero power, including any intermediate zero coefficients.
The number of coefficients for the denominator must be greater than or equal to the number of
coefficients for the numerator.

Allows you to create initial velocities on an existing external system part.
part 19
Format:
external_system_name = an existing part
vm = existing marker
wm = existing marker
vx = velocity
no_vx = true_only
vy = velocity
no_vy = true_only
vz = velocity
no_vz= true_only
wx = angular_vel
no_wx = true_only
wy = angular_vel
no_wy = true_only
wz = angular_vel
no_wz = true_only
Example:
part create external_system initial_velocity &
external_system_name= external_system_1 &
vm = cm &
wm = marker_1 &
vx = 1.02 &
vy = 1.01 &
vz = 1.05 &
no_wz = true
Description:

external_system_name Existing external system You use this parameter to identify the existing
external system part to affect with this command.
vm Existing marker Specifies the marker representing the translational
velocity.
wm Existing marker Specifies the marker representing the rotational
velocity about it.
vx Velocity Specifies the initial translational velocity of the
center-of-mass marker along the x-axis of the
no_vx True_only Specifies to "UNSET" the "vx" velocity initial
condition for the specified part, if set.
vy Velocity Specifies the initial translational velocity of the
center-of-mass marker along the y-axis of the
no_vy True_only Specifies to "UNSET" the "vy" velocity initial
condition for the specified part, if set.
vz Velocity Specifies the initial translational velocity of the
center-of-mass marker along the z-axis of the
no_vz True_only This is not the same as setting the value to zero. A
zero velocity is not the same as "no" velocity.
Therefore, by setting this parameter to true there is
no longer a velocity initial condition for this
element.
wx Angular_velocity Specifies the initial rotational velocity of the center-
of-mass marker about its x-axis.
no_wx True_only Specifies to "UNSET" the "wx" angular_velocity
initial condition for the specified part, if set.
wy Angular_velocity Specifies the initial rotational velocity of the center-
of-mass marker about its y-axis.
no_wy True_only Specifies to "UNSET" the "wy" angular_velocity
wz Angular_velocity Specifies the initial rotational velocity of the center-
of-mass marker about its z-axis.
no_wz True_only Specifies to "UNSET" the "wz" angular_velocity
part 21
part create external_system name_and_position
1. Translational velocities are specified by parameters VX, VY, and VZ.
Rotational velocities are specified by parameters WX, WY, and WZ.
Note: The initial translational velocities are with respect to the ground coordinate axes, while
the initial rotational velocities are with respect to the center-of-mass marker axes.
2. You may identify an external system by typing its name or by picking it from the screen.
a. If the external system part is not visible on the screen, you must type the name. You may also find
it convenient to type the name even if the part is displayed.
b. If you created the part by reading an Adams data set or graphics file, the part name is the letters
PAR followed by the Adams data set part ID number. For example, the name of Adams
PART/101 is PAR101.
c. If you created the part during preprocessing, you will have given it a name at that time.
d. If a part is available by default, you may identify it by entering only its name. If it is not, you must
enter its full name. To identify a part under another model, for instance, you may need to enter
the model name as well. For example, you may specify part 'arm' from model 'robot' by entering
e. You must separate multiple part names by commas. If the part is visible in one of your views, you
may identify it by picking on any of the graphics associated with it.
f. You need not separate multiple part picks by commas.
3. Note that the initial translational velocities are with respect to the ground coordinate axes, while the
initial rotational velocities are with respect to the center-of-mass marker axes.
4. Setting no_vx or no_vy or no_vz is not the same as setting the corresponding velocity value to zero.
A zero velocity is not the same as "no" velocity. Therefore, when this parameter is set to true, there is
no longer a velocity initial condition for this element.
5. Setting no_wx, no_wy, no_wz is not the same as setting the corresponding angular velocity value to
zero. A zero angular_velocity is not the same as "no" angular_velocity. Therefore, when this
parameter is set to true, there is no longer an angular_velocity initial condition for this element.

Allows you to create an external system part by specifying its name and position.
Format:
external_system_name = a new external system
type = boolean

adams_id = adams_id
comments = string
input_file_name = string
interface_routines = string
location = location
Example:
part create external_system name_and_position &
external_system_name = external_system_1 &
adams_id = 1 &
type = nastran &
planar = yes &
Description:

external_system_name New external system Specifies the name of the external system to
be created.
type Nastran, Marc, user The type of external system. Defaults to
'nastran' if not specified.
adams_id Integer Specifies an integer used to identify this
part 23

view_name Existing View Specifies the view in which to display this
part.
input_file_name String File containing the input source parameters
for the external system.
modal_neutral_file_name String An optional (rigid only) MNF, if a visual
representation of the external system is
required.
md_db_file_name String An optional MD DB, if a visual
representation of the external system is
required.
index_in_database Integer Index of the body in the specified MD DB.
Valid only if the parameter
md_db_file_name is specified.
user_function Real Specifies up to 30 values for Adams Solver
to pass to a user-written subroutine. Valid
only if the external system type is 'user'.
interface_routines Function Specifies an alternative library and
subroutine names for the user subroutines
EXTSYS_DERIV, EXTSYS_UPDATE,
EXTSYS_OUTPUT, EXTSYS_SAMP,
EXTSYS_SET_NS, EXTSYS_SET_ND,
EXTSYS_SENSUB,
EXTSYS_SET_STATIC_HOLD,
EXTSYS_SET_SAMPLE_OFFSET,
respectively.
location Location Specifies x, y, and z coordinates defining
the flexible body's location in a given
reference frame defined in the parameter
relative_to.
orientation Orientation Specifies the orientation method
along_axis_orientation Location Specifies the orientation method
in_plane_orientation Location Specifies the in_plane orientation method
relative_to Existing model, part or marker Specifies a reference frame relative to which
the location and orientation are defined.
Leave blank or enter model name to use the
global coordinate system.
1. The position of the external system part can be broken down into two parts:
a. LOCATION
It can be specified by supplying three coordinates corresponding to the current coordinate system
type. For example, if the current coordinate system type is 'cartesian', you would supply an X, Y,
and Z. You may also specify location by "clicking" on an existing part or marker, with the mouse
cursor, that has the same desired location.
b. ORIENTATION
It can be specified by three different methods in Adams View.
The first is by supplying three angles that correspond to the current orientation type. For example,
if the current orientation type is 'body313' you would supply Z,X',Z'' rotation angles. You may
also supply three angles by "clicking" on an existing part or marker, that has the same desired
orientation. The second method is called the ALONG_AXIS_ORIENTATION. This method
specifies the orientation by directing one of the axes. Adams View will assign an arbitrary rotation
about that axis. The third and final method is called IN_PLANE_ORIENTATION. This
method specifies orientation by directing one of the axes, and locating one of the coordinate
planes.
All location and orientation coordinates will be relative to the coordinate system specified in the
parameter RELATIVE_TO. RELATIVE_TO defaults to the global origin of the model.
2. Currently, there are three types supported for an external system: nastran, marc and user. If the
parameter is not specified, it defaults to 'nastran'.
3. The input file name defines the source for the external analysis component. Nominally, this is a string
defining a path and input file, but can potentially be interpreted by the external analysis component
in an arbitrary manner.
4. Note that the parameters user_function and 'interface_routines' are valid only for external systems
that are of type 'user'.
5. When a valid rigid only MNF or an MD-DB (with the optional index) parameters are specified, the
external system will have a visual representation. Interactive marker creation and swap operations (for
a rigid or a flex body) are supported for such systems. However, these parameters are optional. When
not specified, the external system will have no visual representation.
The default name that AdamsAdams View provides will specify the parentage that it has assumed.
part 25
be assigned to it.
yourself.
commas.
system.
By default, you supply Euler (body313, or body-fixed z, x, z) angles.You may change this convention
system.
part create fe_part
12. You may enter either one or two locations for the in_plane_orientation parameter to direct the axis.
will be parallel to, and pointing the same way as the vector from the first location to the second. Note
system.
14. The six coordinates are below.
• X - X coordinate
• Y - Y coordinate
• Z - Z coordinate
• PSI - Psi angle
• THETA - Theta angle
• PHI - Phi angle
You may enter these coordinates in any order. If Adams has to alter the part position to obtain
consistent initial conditions, it does not vary the coordinates you specify with this parameter unless
Adams must vary them to satisfy the initial conditions you specify for a joint or for a motion.
part create fe_part

Allows you to create a new entity of the type fe_part in the Adams session. An fe_part defines a geometrically
non-linear part.
Format:
part create fe_part name_position_section
fe_part_name = new fe_part name
ref_curve = refer existing gcurve
i_marker = select existing marker/point
j_marker = select existing marker/point
i_hard_point = refer existing point
part 27
part create fe_part

j_hard_point = refer existing point
adams_id = real
material_type = refer existing material
cratiok = stiffness matrix
cratiom = mass matrix
prestress_filename = file name
external = Boolean(yes/no)
fepart_type = option(BEAM_3D,BEAMXY_2D,BEAMYZ_2D,BEAMZX_2D)
nodes_at_curve_points = Boolean(yes/no)
Example:
fe_part_name = FE_Part_1
adams_id = 1
ref_curve = GCURVE_1
material_type = steel
cratiok = 0.5
cratiom = 0.5
fepart_type = beamxy_2d
nodes_at_curve_points = yes/no
This will create an fe_part with the name FE_Part_1 with provided parameters.
Description:

fe_part_name string Specifies the name of the fe part to be created.
ref_curve Existing GCURVE Specifies the already created bspline curve to be used as the
reference centerline for the fe_part.
i_marker Existing Along with j_marker, specifies the already created
marker/point marker/point as reference to define the centerline for the
fe_part.
j_marker Existing Along with i_marker, specifies the already created
marker/point marker/point as reference to define the centerline for the
fe_part.
part create flexible_body initial_velocity

i_hard_point Existing point Along with i_point, specifies already created point as
reference to define centerline for fe_part.
j_hard_point Existing point Along with j_point, specifies already created point as
reference to define centerline for fe_part.
material_type Existing Material Specifies the identifier of the existing MATERIAL
statement used by this fe_part.
cratiok real Specifies the fraction of the stiffness matrix that
contributes to the damping matrix for this element.
cratiom real Specifies the fraction of the mass matrix that contributes to
the damping matrix for this element.
fepart_type Option Specifies the formulation type of fe_part.
prestress_filename string Specifies the name of a file containing pre-stress
information for this fe_part.
external Option Specifies if external geometry need to be used for fe part. If
yes, then only external geometry will be rendered.
nodes_at_curve_points Option Support FE part's centerline and node locations
parameterization with curve control points.
See Nodes Parameterization for more information.

Allows you to create initial velocities on an existing part.
Translational velocities are specified by parameters VX, VY, and VZ.
Note that the initial translational velocities are with respect to the ground coordinate axes, while the initial
rotational velocities are with respect to the center-of-mass marker axes.
Format:
flexible_body_name= existing flexible body
vm= existing marker
wm= existing marker
vx= velocity
no_vx= true_only
vy= velocity
part 29

no_vy= true_only
vz= velocity
no_vz= true_only
wx= angular_vel
no_wx= true_only
wy= angular_vel
no_wy= true_only
wz= angular_vel
no_wz= true_only
Example:
part create flexible_body initial_velocity &
flexible_body_name = flex_body__2 &
vm = int_node_12001 &
vx = 200 &
no_vy = true &
no_vz = true
This will apply a translational velocity of 200 at the center-of-mass marker along the x-axis of the ground
reference frame.
Description:

flexible_body_name Existing flex body Specifies the name of the flexible body.
vm Existing marker Specifies a marker about whose axes the translational
velocity vector components will be specified.
wm Existing marker Specifies a marker about whose axes the angular velocity
vector components will be specified.
vx Velocity Specifies the initial translational velocity of the center-of-
mass marker along the x-axis of the ground reference
frame.
no_vx True_only Unsets the vx velocity initial condition for the specified
part (true) so it no longer has a velocity initial condition.
part create flexible_body modal_ics

vy Velocity Specifies the initial translational velocity of the center-of-
mass marker along the y-axis of the ground reference
frame.
no_vy True_only Unsets the vy velocity initial condition for the specified
part (true) so it no longer has an velocity initial
condition.
vz Velocity Specifies the initial translational velocity of the center-of-
mass marker along the z-axis of the ground reference
frame.
no_vz True_only Unsets the vz velocity initial condition for the specified
wx Angular_velocity Specifies the initial rotational velocity of the center-of-
mass marker about its x-axis.
no_wx True_only Unsets the wx velocity initial condition for the specified
wy Angular_velocity Specifies the initial rotational velocity of the center-of-
mass marker about its y-axis.
no_wy True_only Unsets the wy velocity initial condition for the specified
wz Angular_velocity Specifies the initial rotational velocity of the center-of-
mass marker about its z-axis.
no_wz True_only Unsets the wz velocity initial condition for the specified
part (true) so it no longer has an velocity initial
condition.
Tips:

Allows you to set the initial conditions parameters on a flexible body, including the selected modes, the initial
displacements and velocities and the modal exact coordinates for selected modes.
part 31
Format:
flexible_body_name = existing flex_body
selected_modes = real
initial_modal_displacements = real
initial_modal_velocities = real
modal_exact_coordinates = integer
set_ic_modes = integer
modal_ic_displacements = real
modal_ic_velocities = real
Description:

flexible_body_name Existing flex_body Specifies the name of the flexible body.
selected_modes Real Specifies which modes to include when computing
the modal integrals for use by Adams Solver.
initial_modal_displacements real Specifies the initial displacements for the selected
modes.
initial_modal_velocities Real Specifies the initial velocities for the selected
modes.
modal_exact_coordinates Integer Specifies integers that correspond to the modal
coordinates you want held exact during initial
conditions displacement analysis.
set_IC_modes Integer Specifies a list of modes to use when setting
modal_IC_displacement or modal_IC_velocities.
modal_IC_displacements Real Specifies a displacement IC to use for the modes
specified in set_IC_modes.
modal_IC_velocities Real Specifies a velocity to use for the modes specified in
set_IC_modes.
1. Note that when you change the selected modes, you should also modify any initial conditions that
you have set.
part create flexible_body name_and_position
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
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.

Allows you to create or modify a flexible body. You specify a modal neutral file (MNF) or a Nastran MD DB
file or a Nastran Bulk Data File (BDF), and Adams View creates the necessary Adams View geometry for
displaying the flexible body. It also creates a mesh on the flexible body representing the flexible body nodes.
By default, Adams Flex places the flexible body so the flexible body’s local body reference frame (LBRF) is at
the origin of the global coordinate system. The LBRF corresponds to the origin of the finite element (FE)
environment in which the body was originally modeled. You can also set the location and orientation.
Format:
flexible_body_name = new flex body
adams_id = adams_id
comments = string
bdf_file_name = string
unit_of_length = string
unit_of_mass = string
unit_of_force = string
unit_of_time = string
part 33
matrices = existing matrix
damping_ratio = function
damping_routine = string
generalized_damping = off/full/internal_only
dynamic_limit = real
location = location
relative_to = existing model part or marker
exact_coordinates = exact_coordinates
invariants = boolean
characteristic_length = real
representation = rigid/modal/nforce/none
stability_factor = real
Example:
part create flexible_body name_and_position &
flexible_body_name = flex_body__2 &
modal_neutral_file_name = "d:\mscsoftware\adams\con_rod.mnf" &
comments = "example of creating a flexible body"
Description:

flexible_body_name New Flex Body Specifies the name of the flexible body to be created
or modified
adams_id Integer Assigns a unique ID number to the part.
comments String Adds comments about the part to help you manage
and identify it.

view_name Existing View Specifies the view in which to display the part. You
may identify a view by typing its name or by picking
it from the screen. In most cases, you can enter the
special view name all, which means, all the views
currently displayed.
You must separate multiple view names by commas.

You need not separate multiple view picks by
commas.
modal_neutral_file_name String This parameter is mutually exclusive to the MD DB
and BDF file arguments. Specifies the name of the
MNF.
md_db_file_name String This parameter is mutually exclusive to the MNF
and BDF file arguments. Specifies the name of the
MD DB file to create one or more flex bodies.
bdf_file_name String This parameter is mutually exclusive to the MNF
and MD DB file arguments. Specifies the name of
the Nastran BDF.
unit_of_length String Specifies the length unit of data contained in the
BDF if not explicitly specified in the BDF. A valid
length unit option is km, m, cm, mm, mi, ft, in, um,
nm, ang, yd, mil, or uin.
unit_of_mass String Specifies the mass unit of data contained in the BDF
if not explicitly specified in the BDF. A valid mass
unit option is kg, lbm, slug, gram, ozm, klbm, mgg,
sinch, ug, ng, or uston.
unit_of_force String Specifies the force unit of data contained in the BDF
if not explicitly specified in the BDF. A valid force
unit option is n, lbf, kgf, ozf, dyne, kn, klbf, mn, un,
or nn.
unit_of_time String Specifies the time unit of data contained in the BDF
if not explicitly specified in the BDF. A valid time
unit option is h, min, s, ms, us, nanosec, or d.
index_in_database Integer The parameter applies only, when the user is creating
a flexible body out of the MD DB. The parameter
specifies the index of the flexible body in the
specified MD DB. The parameter is optional. If not
specified, it is assumed to have the value 1.
matrices Existing Matrix Specifies the names of seventeen matrices for the
modal representation of the flexible body.
part 35

damping_ratio Function Specifies the damping ratio to be used.
damping_routine String Specifies the path to user-written subroutine to be
used to define modal damping.
generalized_damping Off, full, internal_only Sets generalized damping:
 off - Disables the generalized damping.

 full - Enables the complete generalized damping
matrix, including the effects of a resultant
damping force.
 internal_only - Only enables the portion of the
generalized damping matrix corresponding to the
modal coordinates (that is, ignore the resultant
damping force).
dynamic_limit Real Specifies the threshold frequency for quasi-static
modes.
location Location Specifies x, y, and z coordinates defining the flexible
body's location in a given reference frame defined in
the parameter relative_to.
along_axis_orientation Location Specifies the orientation method.
relative_to Existing Model, Part or Specifies a reference frame relative to which the
Marker location and orientation are defined. Leave blank or
enter model name to use the global coordinate
system.
exact_coordinates X, Y, Z, PSI, THETA, Specifies as many as six part coordinates that Adams
PHI, NONE, ALL View is not to change as it solves for the initial
conditions.
invariants Yes, No Lists nine on/off values used to control the invariants

characteristic_length Real Specifies the characteristic length of the flexible
body for linear limit check. This should be in the
model length unit. The linear limit is defined as
10% of this length.
representation RIGID, MODAL, Specifies the representation of the flexible body and
NFORCE, NONE if it is eligible for runtime type switching between
MODAL (linear) and RIGID representation during
a simulation. If MODAL, the flex body will be
treated as a linear flex body initially and can be
switched to rigid body using the FLEX_BODY
Solver command. If RIGID, the flex body will be
treated as a rigid body initially and can be switched
to linear flexible formulation during the simulation.
These two options provide dual representation
capability of the flex body during the simulation.
If representation is NFORCE, NONE or not

specified, the flex body is not eligible for runtime
switching.
If NFORCE, the flex body's modal representation is

Simplified. Its modal representation is converted to
a semi-equivalent multi_point_force representation
with rigid_body. The stiffness and damping matrix
of the multi_point_force is derived from the modal
stiffness matrix and modal damping settings. The
properties of the rigid_body are derived from the
mass invariants of the flexible_body.
Note: 1. Setting the representation to RIGID or

NFORCE can speed up the simulation
without a model change, but may result in
loss of fidelity.
2. Dual-representation or NFORCE
flexible bodies do not directly support
contact with any other bodies. One would
have to use dummy part geometry fixed to
the flexible body for contact modeling.
stability_factor Real Specifies the amount of damping needed to add to
the quasi-static modes to stabilize the simulation.
part 37
when entering it.
be assigned to it.
If an entity is available by default, you can identify it by entering only its name. If it is not, you must
name of the graphics file without the .gra extension.
 The matrices compose the modal integrals used by Adams Solver during simulation. In
general, if you enter the MNF, you do not need to specify names for the matrices.
 For the damping_ratio parameter, do one of the following:
 Do not specify to accept the default nonzero damping as follows:
 1% damping for all modes with frequency lower than 100.
 10% damping for modes with frequency in the 100-1000 range.
 100% critical damping for modes with frequency above 1000.
 Enter the scalar damping ratio that you want applied to all modes.
 For example if you would like to apply 1% damping enter 0.01. For more examples you
can see FLEX_BODY statement documentation
 Enter Adams run-time function expressions to create complex damping phenomena in
your flexible body. In addition, function expressions, such as FXFREQ and FXMODE,
allow you to apply different levels of damping to individual modes.
Several types of damping are inherently present in mechanical systems. Understanding the
source and level of damping are important in the simulation and testing of dynamic
systems. For example, a mechanism having low natural frequencies and relatively low
damping, could produce damaging motions under resonant conditions.
Applying damping judiciously can also improve simulation performance for models
containing flexible bodies. For example, consider a flexible body with a 10 kHz mode
whose shape is considered essential to allowing the body to assume a particular
deformation. Any response in this mode at its resonant frequency dictates integration steps
on the order of 1E-5 seconds, which can be unacceptable for long duration simulations. If
the damping for this mode is set at 100% of critical damping, however, any resonant
response is immediately suppressed. The mode's compliance is retained but its dynamics
are eliminated and the simulation performance is improved.
Damping Dissipation and Damping Matrix

The damping force on a flexible body is proportional to its generalized velocities and is assumed to
be derivable from the quadratic form:
part 39
where:
• D is a symmetric matrix of damping coefficients
·
• q is a vector of generalized velocities:
x·
y·
z·
wx
·
q = wy
wz
·
q1
…
q· 2
 x·, y·, z· are the absolute time derivatives of the position vector coordinates of the local part reference
frame with respect to the local part reference frame.
 w x, w y, w z are the angular velocity vector coordinates with respect to the local part reference
frame.
·
 q 1, …, q· 2 are the time derivatives of the modal coordinates.
The matrix D is composed of two parts, Dm and Dg:
D = Dm + Dg
Dm represents the contribution of proportional modal damping, and Dg represents the contribution
of a generalized damping matrix. Both are explained in the next section.
Specifying Modal Damping

The modal damping matrix Dm is diagonal and defined using critical damping ratios ζ i for each
mode i= 1,n.
0 3x3 0 3x3 0 3x1 0 3x1 … 0 3x1 0 3x1

0 3x3 0 3x3 0 3x1 0 3x1 … 0 3x1 0 3x1
0 1x3 0 1x3 2ζ 1 k 1 m 1 0 … 0 0
Dm = 0 2ζ 2 k 2 m 2 …
1x3 0 1x3 0 0 0
… … … … … … …
0 1x3 0 1x3 0 0 … 2ζ n – 1 k n – 1 m n – 1 0
0 1x3 0 1x3 0 0 … 0 2ζ n k n m n
where k i and m i are the generalized stiffness and mass for mode i.
Note: The damping ratio ζ i does not need to be constant. It can be a function of time or
system state.
If you do not specify modal damping when you create the flexible body, Adams Flex applies a default,
non-zero critical damping ratio as follows:
• 1% damping for all modes with frequency lower than 100.
• 10% damping for modes with frequency in the 100 to 1000 range.
• 100% critical damping for modes with frequency above 1000.
You can change the default modal damping in three ways:
• Assign a single scalar critical damping ratio that Adams Flex applies uniformly to all modes.
• Enter Adams run-time function expressions to create complex damping phenomena in your
flexible body. In addition, function expressions, such as FXFREQ and FXMODE, allow you to
apply different levels of damping to individual modes.
• Control the damping using the DMPSUB user-written subroutine. DMPSUB lets you set
different levels of damping for different modes and the damping can vary over time. For more on
writing subroutines, see the Subroutines section of the Adams Solver online help.
To assign modal damping when creating or modifying a flexible body:
1. In either the Create a Flexible Body dialog box or Flexible Body Modify dialog box, clear the selection
of default (use default in the Create a Flexible Body dialog box).
2. In the Damping Ratio text box, either:
part 41
• Enter the critical damping ratio.

• Enter a function. To get help building the function, next to the Damping Ratio text box, select
the More button . The Adams View Function Builder appears. For information on using the
Function Builder, see the Adams View Function Builder online help.
3. Continue creating or modifying the body, and then select OK.
Specifying Generalized Damping
The generalized damping matrix Dg is a constant symmetric matrix of the form:
D gTT D gTR D gTM

T
Dg = D gTR D gRR D gRM
T T
D gTM D gRM D g MM
To better understand how the generalized damping matrix is handled in Adams Flex, it is helpful to
start with the discrete finite element equations of motion
Mx·· + Bx·· + Kx·· = F
where:
 M, B, and K are the finite element mass, stiffness, and damping matrices, respectively.
 ··
x is the nodal coordinate vector.
 is the applied force vector.
The damping matrix B is derived from damping elements and parameters defined in the finite
element model. The previous equation can be transformed into modal coordinates:
T T T T
P MPq·· + P BPq· + P KPq = P F
where P is the matrix of mode shapes stored column-wise and q is the vector of modal coordinates
PTBP represents the generalized damping matrix. However, before Adams Flex can use the
generalized damping matrix, the portion PTBP of that projects onto the rigid body modes must be
transformed to the nonlinear, large motion, generalized coordinates: X, Y, Z, ψ , θ , and Φ used to
represent the flexible bodys large overall motion in Adams Solver (C++). To this end, a m x 6
transformation matrix, A, is constructed and transforms m rigid body modes to the six coordinates X
,Y, Z, ψ , θ , and Φ , and the final generalized matrix Dg is computed:
T A 0
D g = A 0 P BP
T
0 I nxn 0 I nxn
If the damping description in the finite element model results in a resultant damping force, there will
be nonzero entries in the sub-matrices D g
TT
, D g TR, D gTM, D gRR, D g RM . Because the resultant
damping force was derived from a linear finite element model governed by small strain
approximations and infinitesimal rotations, a resultant damping force may yield unexpected results
in the context of large overall motion supported in Adams. Therefore, Adams Flex provides the option
to ignore the resultant damping force. Ignoring a resultant damping force is referred to as internal-
only generalized damping.
Because the generalized matrix Dg is derived from the component finite element model, you can
leverage the damping elements and features in the finite element program. This is particularly useful
for defining non-proportional and spatially-dependent damping. Furthermore, the generalized
damping matrix is stored in the MNF to be optionally applied to the flexible body. That is, because
you defined damping in the finite element model, it is not necessary to employ it in Adams. To enable
generalized damping, however, you must have a generalized damping matrix stored in your MNF.
To specify generalized damping when creating or modifying a flexible body:
1. In either the Create a Flexible Body dialog box or Flexible Body Modify dialog box, set Generalized
Damping to:
• Off - Disables the generalized damping.
• Full - Enables the complete generalized damping matrix, including the effects of a resultant
damping force.
• Internal Only - Only enables the portion of the generalized damping matrix corresponding to the
modal coordinates (that is, ignore the resultant damping force).
2. Continue creating or modifying the body, and then select OK.
3. Orientation of rigid or flexible body using three rotation angles. Adams View orients the body starting
from the initial coordinate system and applying three successive rotations. Depending on the
convention you select, the rotations occur about space-fixed or body-fixed axes in any combination
of the x, y, and z axes. By default, you supply body 313 (body-fixed z, x, z) angles.
Adams View applies your orientation angles with respect to the coordinate system in the Orientation
Relative To or Relative To text box.
Along Axis Orientation
Orientation of a rigid or flexible body by directing one of its axes. Adams View assigns an arbitrary
rotation about the axis. Two points are needed to define an axis but you can enter either one or two
points to direct the axis. If you enter two points, the axis points from the first location to the second.
If you enter one point, Adams View uses the location you specified in the Location text box as the
first point and the new location as the second point.
Along Axis Orientation
part 43
Adams View applies the location coordinates in the coordinate system you identify in the Location
Relative To or Relative To text box.
Note that this does not completely dictate the orientation of the coordinate system. Adams View
positions the coordinate system with an arbitrary rotation about the axis. If you must completely
control the coordinate system orientation, select Orientation or In Plane Orientation.
By default, you direct the z-axis of the coordinate system. You can use the DEFAULTS
ORIENT_AXIS_AND_PLANE AXIS_AND_PLANE_SETTING command to change this
convention. For example, selecting either X_AXIS_XY_PLANE or X_AXIS_XZ_PLANE directs the
x-axis. The plane-convention setting does not affect this parameter.
You can also direct the axis graphically using the marker’s position handle. Simply point the
appropriate axis on the marker in the desired direction.
In Plane Orientation
Orientation of the rigid or flexible body by directing one of the axes and locating one of the
coordinate planes.
In Plane Orientation
To define an axis and a plane, you need three points. You can enter either two or three locations, however. If
you enter three locations, the axis points from the first location to the second and the plane is parallel to the
plane defined by the three locations. If you enter only two locations, Adams View uses the location you
specified in the Location text box as the first point and the other two locations as the second and third points.
Adams View applies the location coordinates in the coordinate system in the Relative To text box.
By default, you direct the z-axis of the coordinate system marker and locate the zx plane. You can use
the DEFAULTS ORIENT_AXIS_AND_PLANE AXIS_AND_PLANE_SETTING command to
change this convention. For example, selecting X_AXIS_XY_PLANE directs the x-axis and orients
the xy plane.
4. The six coordinates for the exact_coordinates parameter are:
• PSI - Psi angle
• PHI - Phi angle
You can enter these coordinates in any order. If Adams View has to alter the part position to
obtain consistent initial conditions, it does not vary the coordinates you specify with this
parameter unless Adams View must vary them to satisfy the initial conditions you specify for a
joint or for a motion.
5. Adams Flex computes the time varying mass matrix of the flexible body using nine inertia invariants.
(For details, see Theory of Flexible Bodies.) Four combinations of invariants have special significance
and they are provided with Adams Flex. In most cases, the modal basis in the MNF is an orthogonal
set including six rigid body modes. Theoretically, invariant 3 and 4 are zero in this situation even
though you may see some small non-zero entries due to numerical errors. So, invariants 3 and 4 are
disabled in all the four combinations by default. If you want to enable them, you can choose to
customize the invariant formulation. The standard formulations are:
• Rigid body - In this formulation, Adams Flex disables invariant 6, the modal mass, and the
flexible body is considered rigid. Adams View ignores all modes, even those you enable, during
the simulation. The results of the flexible body simulation closely resemble those for an Adams
rigid part although formulation differences can cause subtle result variations.
• Constant - In this formulation, Adams Flex disables invariants 3, 4, 5, 8 and 9. The flexible body's
inertial properties are unaffected by deformation (that is, deformation and rigid body motion are
uncoupled).
The Constant option may only have academic value because computational savings will be
modest while potentially having a dramatic effect on results. When you select Constant, Adams
View does not account for changes in the moment of inertia due to deformation.
• Partial coupling - In this formulation, which is the default, Adams Flex disables invariants 3, 4,
5 and 9. Invariants 5 and 9 provide a second-order correction to the flexible body inertia tensor.
These invariants impose the greatest computational overhead on the evaluation of the flexible
body equations of motion. Disabling these invariants can reduce CPU time significantly while
having minor impact on results in most cases.
• Full coupling - In this formulation, Adams Flex enables all of the invariants except for invariants
3 and 4. Use this method to achieve full accuracy.
When Adams Flex creates a flexible body, it uses the Partial Coupling formulation by default
because Partial Coupling has significant computational efficiency over the more accurate Full
Coupling formulation. You should verify, however, that your model does not require Full
Coupling.
You should always be careful when using the Constant formulation even when you expect
deformations to be small. Use it only after careful experimentation.
The Rigid Body formulation removes all flexibility effects, and you should only use it as a
debugging tool.
To set a modal formulation:
part 45
part create new_ground
1. In the Inertia modeling area of the Flexible Body Modify dialog box, select a formulation option or
select Custom.
When you select Custom, Adams Adams Flex displays a Custom Inertial Modeling dialog box that
lets you set up the invariants that you want selected.
2. Use the dialog box to select the inertia invariants, and then select OK.
You can also use this dialog box to view the effects of the different options. For example, select Partial
Coupling to view the invariants that option disables and enables.

Allows you to create a new part and makes it the ground part. This feature is useful when incrementally
designing a model.
Format:
part_name = a new part
Example:
part create new_ground &
part_name = part_1
Description:

part_name A New Part Specifies the name of the new part. You may use this name later to refer to
this part.
part create point_mass initial_velocity
be assigned to it.
Cautions:
1. Adams View will not allow you to have two parts with the same name, so you must provide a unique
name.

Allows you to create initial velocities on an existing point mass.
Translational velocities are specified by parameters VX, VY, and VZ.
Note that the initial translational velocities are with respect to the ground coordinate axes.
Format:
point_mass_name= existing point_mass
vm= existing marker
vx= velocity
no_vx= true_only
vy= velocity
no_vy= true_only
vz= velocity
no_vz= true_only
Example:
part create point_mass initial_velocity &
point_mass_name = point_mass__2 &
vm = int_node_12001 &
vx = 200 &
no_vy = true &
no_vz = true
This will apply a translational velocity of 200 at the center-of-mass marker along the x-axis of the ground
reference frame.
part 47
Description:

Point_mass_name Existing point_mass Specifies the name of an existing point mass.
vm Existing marker Specifies a marker about whose axes the translational velocity
vector components will be specified.
vx Velocity Specifies the initial translational velocity of the center-of-mass
marker along the x-axis of the ground reference frame.
no_vx True_only Unsets the vx velocity initial condition for the specified part
(true) so it no longer has a velocity initial condition.
vy Velocity Specifies the initial translational velocity of the center-of-mass
marker along the y-axis of the ground reference frame.
no_vy True_only Unsets the vy velocity initial condition for the specified part
vz Velocity Specifies the initial translational velocity of the center-of-mass
marker along the z-axis of the ground reference frame.
no_vz True_only Unsets the vz velocity initial condition for the specified part
1. You can specify initial velocities for parts. AdamsAdams View uses the initial velocity during the
initial conditions simulation, which it runs before it runs a simulation of your model.
You can specify translational and angular velocities for rigid bodies and only translational velocity for
point masses.
 Translational velocity defines the time rate of change of a part’s center of mass with respect to
ground or another marker in your model. You can specify translational velocity for each vector
component of the marker.
 Angular velocity defines the time rate of change of a part’s rotational position with respect to the
CM marker of the part or another marker in your model. You can specify angular velocity for each
vector component of the marker.
If you specify initial velocities, Adams View uses them as the initial velocity of the part during
assemble model operations, regardless of any other forces acting on the part. You can also leave some
or all of the velocities unset. Leaving a velocity unset lets Adams View calculate the velocity of the
part during an assemble operation depending on the other forces and constraints acting on the part.
Note that it is not the same as setting the initial velocity to zero. Setting an initial velocity to zero
means that the part will not be moving in the specified direction when the simulation starts,
regardless of any forces and constraints acting upon it.
part create point_mass mass_properties
Tips:
2. Note that the initial translational velocities are with respect to the ground coordinate axes.

Creates the mass properties on an existing point mass.
The mass properties of a point_mass include the mass and the center-of-mass marker. You may assign zero
mass to a point_mass whose three degrees of motion you constrain with respect to bodies that do have mass.
However, due to the number of changes that you may make to the dataset in the course of defining a model,
the probability of a later change requiring that the point mass have mass is high. Therefore, we recommend
that you assign finite (although insignificant) masses and inertias to point masses that you would otherwise
assign zero mass properties.
If you specify the mass for a point_mass, you must also specify the center-of-mass marker for the point_mass.
Format:
point_mass_name= existing point_mass
mass= mass
center_of_mass_marker= existing marker
density= density
material_type= existing material
Description:

point_mass_name Existing point mass Specifies the name of the part to create or modify.
Mass Mass Specifies the mass of the point mass.
center_of_mass_marker Existing marker Enter the marker that is to be used to define the center-
of-mass (CM) for the part.
density Density Specifies the part density and that the mass properties
of the part are to be automatically calculated.
material_type Existing material Specifies the material type of the part and that the mass
properties of the part are to be automatically calculated.
part 49
1. If the point mass has no mass, Adams View uses the point mass local part reference frame (LPRF) to
represent the position of the point mass internally. If the point mass has mass, Adams View uses the
position of the center-of-mass marker to represent the translational position of the point mass
internally.
The orientation of the point_mass and the center-of-mass marker have no effect on the simulation.
2. If the point mass has mass, Adams View uses the position of the CM marker to represent the
translational position of the point mass internally.
3. Adams View uses the part’s density and the volume of the geometry to calculate its mass and inertia.
Standard Material Properties
The following table shows the material properties for the standard material types in Adams View. All
material types in Adams View are assumed to be linearly elastic. Adams View automatically calculates
the material’s Shear Modulus (G) from the Young’s Modulus (E) and Poisson’s Ratio (ν) according
to the equation:
E
G = ---------------------
2(1 + υ)
Young’s Modulus value Density

The material: (Newton/meter2): Poisson’s Ratio: (kg/meter3):
Aluminum 7.1705E+ 10 0.33 2740.0
Cast iron 1.0E+11 0.211 7080.0
Steel 2.07E+11 0.29 7801.0
Stainless steel 1.9E+11 0.305 7750.0
Magnesium 4.48E+10 0.35 1795.0
Nickel 2.07E+11 0.291 7750.0
Glass 4.62E+10 0.245 2595.0
Brass 1.06E+11 0.324 8545.0
Copper 1.19E+11 0.326 8906.0
Lead 3.65E+10 0.425 11370
Titanium 1.0204E+11 0.3 4850.0
Tungsten 3.447E+11 0.28 19222
Wood 1.1E+10 0.33 438.0
'_' (underscore) characters, and start with an alphabetic or '_' character. They may be any length.
part create point_mass name_and_position
when entering it.
name that Adams View provides specifies the parentage that it has assumed. You can, or course, delete
be assigned to it.

Allows you to create a point mass by specifying its name and position. You must supply a unique name for
the new part, or accept the name that Adams View generates for you.
You define the position of the point mass by:
 Location - You can specify the location by supplying three coordinates corresponding to the current
coordinate system type. For example, if the current coordinate system type is Cartesian, you would
supply an x, y, and z. You can also specify location by clicking on an existing part or marker that has
the same desired location.
 Orientation - You can use the three different methods in Adams View:
• Orientation
• Along-axis orientation
• In_plane_orientation
All location and orientation coordinates are relative to the coordinate system specified in the parameter
relative_to.
relative_to defaults to the global origin of the model.
Format:
point_mass_name= new point mass
adams_id= adams_id
comments= string
view_name= existing view
location= location
part 51

relative_to= existing model part or marker
exact_coordinates= exact_coordinates
Description:

Point_mass_name New Point Mass Specifies the name of the point mass to create or modify.
adams_id Integer Assigns a unique ID number to the part.
comments String Adds comments about the part to help you manage and
identify it.
view_name Existing view Specifies the view in which to display the part.
location Location Specifies x, y, and z coordinates defining the flexible
body's location in a given reference frame defined in the
parameter relative_to.
along_axis_orientation Location Specifies the orientation method
relative_to Existing Model, Part Specifies a reference frame relative to which the location
or Marker and orientation are defined. Leave blank or enter model
name to use the global coordinate system.
exact_coordinates X, Y, Z, PSI, Specifies as many as six part coordinates that Adams
THETA, PHI, View is not to change as it solves for the initial
NONE, ALL conditions.
when entering it.
be assigned to it.
enter its full name. To identify an entity under a different part, you may need to enter the model and
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.
name of the graphics file without the .gra extension.
4. You may identify a view by typing its name or by picking it from the screen. In most cases, you can
commas.
part 53
5. The along_axis_orientation parameter specifies the orientation of a rigid or flexible body by directing
one of its axes. Adams View assigns an arbitrary rotation about the axis. Two points are needed to
define an axis but you can enter either one or two points to direct the axis. If you enter two points,
the axis points from the first location to the second. If you enter one point, Adams View uses the
location you specified in the Location text box as the first point and the new location as the second
point.
Adams View applies the location coordinates in the coordinate system you identify in the Location
Relative To or Relative To text box. Note that this does not completely dictate the orientation of the
coordinate system. Adams View positions the coordinate system with an arbitrary rotation about the
axis. If you must completely control the coordinate system orientation, select Orientation or In Plane
Orientation.
By default, you direct the z-axis of the coordinate system. You can use the DEFAULTS
convention. For example, selecting either X_AXIS_XY_PLANE or X_AXIS_XZ_PLANE directs the
x-axis. The plane-convention setting does not affect this parameter.
You can also direct the axis graphically using the marker’s position handle. Simply point the
appropriate axis on the marker in the desired direction.
6. IThe in_plane_orientation parameter specifies the orientation of the rigid or flexible body by
directing one of the axes and locating one of the coordinate planes.
To define an axis and a plane, you need three points. You can enter either two or three locations,
however. If you enter three locations, the axis points from the first location to the second and the
plane is parallel to the plane defined by the three locations. If you enter only two locations, Adams
View uses the location you specified in the Location text box as the first point and the other two
locations as the second and third points. Adams View applies the location coordinates in the
part create rigid_body initial_velocity
coordinate system in the Relative To text box. By default, you direct the z-axis of the coordinate
system marker and locate the zx plane. You can use the DEFAULTS
convention. For example, selecting X_AXIS_XY_PLANE directs the x-axis and orients the xy plane.
7. The six coordinates for the exact_coordinates parameter are:
 X - X coordinate
 Y - Y coordinate
 Z - Z coordinate
 PSI - Psi angle
 THETA - Theta angle
 PHI - Phi angle
You can enter these coordinates in any order. If Adams View has to alter the part position to obtain
Adams View must vary them to satisfy the initial conditions you specify for a joint or for a motion.

Allows you to create initial velocities on an existing part
Format:
vm = an existing marker
wm = an existing marker
vx = velocity
no_vx = true_only
vy = velocity
no_vy = true_only
vz = velocity
no_vz = true_only
wx = angular_vel
no_wx = true_only
wy = angular_vel
no_wy = true_only
wz = angular_vel
part 55
Example:
part create rigid_body initial_velocity &
vm = cm &
wm = marker_1 &
vx = 1.02 &
vy = 1.01 &
vz = 1.05 &
no_wz = true
Description:

part_name An Existing Part Specifies the part to be modified. You use this parameter to identify
the existing part to affect with this command.
vm An Existing Marker
wm An Existing Marker
vx Velocity Specifies the initial translational velocity of the center-of-mass
marker along the x-axis of the ground reference frame.
no_vx True_Only Specifies to "UNSET" the "vx" velocity initial condition for the
specified part, if set.
vy Velocity Specifies the initial translational velocity of the center-of-mass
marker along the y-axis of the ground reference frame.
no_vy True_Only Specifies to "UNSET" the "vy" velocity initial condition for the
specified part, if set.
vz Velocity Specifies the initial translational velocity of the center-of-mass
marker along the z-axis of the ground reference frame.
no_vz True_Only This is not the same as setting the value to zero. A zero velocity is
not the same as "no" velocity. Therefore, by setting this parameter
to true there is no longer a velocity initial condition for this element.
wx Angular_Vel Specifies the initial rotational velocity of the center-of-mass marker
about its x-axis.
no_wx True_Only Specifies to "UNSET" the "wx" angular_velocity initial ondition for
the specified part, if set.
wy Angular_Vel Specifies the initial rotational velocity of the center-of-mass marker
about its y-axis.

no_wy True_only Specifies to "UNSET" the "wy" angular_velocity initial condition
for the specified part, if set.
wz Angular_vel Specifies the initial rotational velocity of the center-of-mass marker
about its z-axis.
no_wz True_only Specifies to "UNSET" the "wz" angular_velocity initial condition
for the specified part, if set.
1. Translational velocities are specified by parameters VX, VY, and VZ.
Note: The initial translational velocities are with respect to the ground coordinate axes, while
the initial rotational velocities are with respect to the center-of-mass marker axes.
associated with it.
4. Setting no_vx or no_vy or no_vz is not the same as setting the corresponding velocity value to zero.
A zero velocity is not the same as "no" velocity. Therefore, when this parameter is set to true, there is
no longer a velocity initial condition for this element.
5. Setting no_wx, no_wy, no_wz is not the same as setting the corresponding angular velocity value to
zero. A zero angular_velocity is not the same as "no" angular_velocity. Therefore, when this
parameter is set to true, there is no longer a angular_velocity initial condition for this element.
part 57
part create rigid_body mass_properties

Allows you to create mass properties on an existing part.
Format:
mass = mass
center_of_mass_marker = an existing marker
inertia_marker = an existing marker
ixx = inertia
iyy = inertia
izz = inertia
ixy = inertia
iyz = inertia
izx = inertia
material_type = an existing material
density = density
Example:
part create rigid_body mass_properties &
mass = 1.85 &
center_of_mass_marker = marker__1 &
material_type = steel
Description:

parameter to identify the existing part to be affected
with this command.
mass Mass Specifies the part mass
center_of_mass_marker An Existing Marker Specifies the marker that defines the part center of
mass and, in the absence of the inertia marker, the axes
for the inertia properties.

inertia_marker An Existing Marker Specifies the marker that defines the axes for the inertia
properties. If you do not supply an inertia marker, it
defaults to the part center-of-mass marker.
ixx Inertia Specifies the xx component of the mass-inertia tensor
as computed about the origin of the inertia marker,
and expressed in the coordinates of the inertia marker
reference frame.
iyy Inertia Specifies the yy component of the mass-inertia tensor
reference frame.
izz Inertia Specifies the zz component of the mass-inertia tensor
reference frame.
ixy Inertia Specifies the xy component of the mass-inertia tensor
reference frame.
iyz Inertia Specifies the yz component of the mass-inertia tensor
reference frame.
izx Inertia Specifies the zx component of the mass-inertia tensor
reference frame.
material_type An Existing Material Specifies the part material_type and that the mass
properties of the part are to be automatically calculated
density Density Specifies the part density and that the mass properties
of the part are to be automatically calculated.
1. The mass properties of a part include the mass, mass-inertia tensor, center-of-mass marker, and inertia
marker.
You may assign zero mass to a part whose six degrees of motion you constrain with respect to parts
that do have mass. However, due to the number of changes that you may make to the data set in the
course of defining a model, the probability of a later change requiring that the part have mass is high.
Consequently, you are encouraged to assign finite (although insignificant) masses and inertias to parts
you would otherwise give zero inertial properties.
part 59
A part without mass cannot have moments of inertia. If you specify the mass and moments of inertia
for a part, you must also specify the center-of-mass marker for the part.
associated with it.
3. If the part has no mass, Adams uses the part LPRF to represent the position and orientation of the
part internally.
If the part has mass, Adams uses the position of the center-of-mass marker to represent the
translational position of the part internally and uses the principal axes of the inertia tensor about the
center-of-mass marker to represent the orientation of the part internally. This internal frame of
reference is referred to as the part principal axes frame.
4. If the part has mass, Adams uses the position of the center-of-mass (CM) marker to represent the
translational position of the part internally and uses the principal axes of the inertia tensor about the
CM marker to represent the orientation of the part internally. This internal frame of reference is
referred to as the part principal axes frame.
5. The inertia matrix is defined as follows:
[ Ixx -Ixy -Ixz]
[ ]
J = [-Ixy Iyy -Iyz]
[ ]
[-Ixz -Iyz Izz]
It is a symmetrical, positive definite matrix. Compute the individual terms as follows:
Ixx = Integral (y**2 + z**2) dm
Iyy = Integral (x**2 + z**2) dm
Izz = Integral (x**2 + y**2) dm
Ixy = Integral xy dm
Ixz = Integral xz dm
Iyz = Integral yz dm
part create rigid_body name_and_position
In the above formulae, x, y, and z are the components of displacement of an infinitesimal mass particle
of mass dm, measured from the origin of the inertia marker in the reference frame of the inertia
marker. The integral is performed over the entire mass of the body. If you do not specify the inertia
marker, then it defaults to the center-of-mass marker. In that case, you compute these quantities
about the origin of the center-of-mass marker in the reference frame of the center-of-mass marker.
Tips:
1. The calculated mass properties are based upon the solid geometry that belongs to the part.

Allows you to create a rigid body part by specifying its name and position.
Format:
part_name = a new part
ground_part = boolean
adams_id = adams_id
comments = string
location = location
exact_coordinates = exact_coordinates
Example:
ground_part = yes &
adams_id = 1 &
comments = " a new ground part" &
planar = yes &
part 61
Description:

part_name A New Part Specifies the name of the new part. You
part.
ground_part Boolean
adams_id Adams_Id Specifies an integer used to identify this
view_name An Existing View Specifies the view in which to display this
part.
location Location Specifies the location of the origin of a
coordinate system (e.g. marker or part).
orientation Orientation Specifies the orientation of a coordinate
system (e.g. marker or part) using three
rotation angles.
along_axis_orientation Location Specifies the orientation of a coordinate
system (e.g. marker or part) by directing
one of the axes. Adams View will assign
an arbitrary rotation about the axis.
in_plane_orientation Location Specifies the orientation of a coordinate
system (e.g. marker or part) by directing
one of the axes and locating one of the
coordinate planes.
relative_to An Existing Model, Part Or Marker Specifies the coordinate system that
location coordinates and orientation
angles correspond to.
exact_coordinates Exact_Coordinates Specifies as many as six part coordinates
that Adams is not to change as it solves
for the initial conditions.
1. You must supply a unique name for the new part, or accept the name that Adams View has generated
for you.
The position of the rigid body part can be broken down into two parts:
location, and orientation.
LOCATION can be specified by supplying three coordinates corresponding to the current coordinate
system type. For example, if the current coordinate system type is 'cartesian', you would supply an X,
Y, and Z. You may also specify location by "clicking" on an existing part or marker, with the mouse
cursor, that has the same desired location.
ORIENTATION can be specified by three different methods in Adams View.
The first is by supplying three angles that correspond to the current orientation type. For example, if
the current orientation type is 'body313' you would supply Z,X',Z'' rotation angles. You may also
supply three angles by "clicking" on an existing part or marker, that has the same desired orientation.
The second method is called the ALONG_AXIS_ORIENTATION. This method specifies the
orientation by directing one of the axes. Adams View will assign an arbitrary rotation about that axis.
The third and final method is called IN_PLANE_ORIENTATION. This method specifies
orientation by directing one of the axes, and locating one of the coordinate planes.
All location and orientation coordinates will be relative to the coordinate system specified in the
parameter RELATIVE_TO. RELATIVE_TO defaults to the global origin of the model.
be assigned to it.
yourself.
part 63
commas.
system.
x, y, and z angles.
system.
8. You may enter either one or two locations for the in_plane_orientation parameter to direct the axis.
system.
part delete
10. The six coordinates are below.
• PSI - Psi angle
• PHI - Phi angle
You may enter these coordinates in any order. If Adams has to alter the part position to obtain
Adams must vary them to satisfy the initial conditions you specify for a joint or for a motion.
part delete
Allows you to delete an existing part (rigid body, equation, flexible body, point mass, or rigid stress object).
You must enter the name of the part you want to delete by either picking it from the screen or specifying the
full name.
You can reverse this deletion using an undo command.
Format:
part delete
equation_name = existing equation
external_system_name = existing external system
rigid_stress_name = existing rigid stress
fe_part_name = existing FE_Part
fe_node_name = existing FE_Node
Example:
part delete &
part_name = part_2
part 65
part delete
Description:

part_name Existing Part Specifies the name of the rigid body to be deleted
equation_name Existing Equation Specifies the name of the equation to be deleted
flexible_body_name Existing Flex Body Specifies the name of the flexible body to be deleted
external_system_name Existing External Specifies the name of an existing external system to be
System deleted
point_mass_name Existing Point Mass Specifies the name of the point mass to be deleted
rigid_stress_name Existing Rigid Stress Specifies the name of the rigid stress object to be deleted
fe_part_name Existing FE_Part Specifies the name of FE Part to be deleted
fe_node_name Existing FE_Node Specifies the name of FE Node to be deleted
enter its full name. To identify an entity under a different part, you may need to enter the model and
Notes:  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 will have given 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
part display
part display
Allows you to display the part (rigid body, flexible body, or point mass) in the specified view. If you do not
specify a view, Adams View displays the model in the active view. This command can be useful when the
entire part is no longer visible in the current view space because it fits the model into the current view.
Format:
part display
part_name= existing part
flexible_body_name= existing flex body
point_mass_name= existing point mass
fe_part_name= existing fe part name
view_name= existing view
fit_to_view= boolean
Example:
part display &
part_name = part_1
Description:

part_name Existing part Specifies the name of the rigid body to be displayed
flexible_body_name Existing flex body Specifies the name of the flexible body to be displayed
point_mass_name Existing point mass Specifies the name of the point mass to be displayed
fe_part_name Existing FE part Specifies the name of the FE part to be displayed
view_name Existing view Specifies the view in which to display this model.
fit_to_view Yes/No Controls whether or not to compute the extents of the
model or part before displaying the model or part in a
view. This parameter is optional and has a default value of
on.
1. You may identify a view by typing its name or by picking it from the screen. In most cases, you can
commas.
part 67
part merge rigid_body

Allows you to merge one part into another part. The part identified in part name is the part being merged
and the model identified in into_part_name is the destination model into which part_name will be merged.
The source part will not be changed after the merge operation.
Notes on merging:
Notes:  If the parts differ in mass properties, the destination part's properties are used. If they
differ in density, the destination part's material will be used.
 Children of the two parts that have the same names will be renamed after the merge with
an integer appended (for example, marker_1 would become marker_1_1).
Format:
into_part_name= existing part
Example:
part merge rigid_body &
into_part_name = part_3
Description:

Part_name Existing part Specifies the part to be merged into the destination part.
Into_part_name Existing part Specifies the name of the new part into which the part listed in part
name will be merged.
when entering it.
part modify equation differential_equation
be assigned to it.

Allows you to modify an existing user defined differential equation.
Format:
differential_equation_name = an existing equation
new_differential_equation_name = a new equation
adams_id = integer
comments = string
no_initial_condition = true_only
function = function
static_hold = on_off
implicit = on_off
Example:
part modify equation differential_equation &

Adams 2020 Adams View Command User Guide

Uploaded by

Copyright:

Available Formats

Adams 2020 Adams View Command User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Adams 2020 Adams View Command User Guide

Uploaded by

Copyright:

Available Formats

Adams 2020

Adams View Command User's Guide

About Adams View Commands

Syntax Rules for Entering Commands

Syntax Rules for Entering Values

Data type: Use:

The rules for entering values are that they:

Miscellaneous Command Information

Mixing Comments and Commands

Verifying Command Input

Getting Help Completing Command Parameters

To get assistance with keywords:

To view all parameter names associated with a keyword:

To get assistance with values for a parameter:

Grouping Operations into an Undo Block

To create an undo block:

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

animation add_simulation &

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value type Description

Parameter Value type Description

Parameter Value Type Description

Parameter Value Type Description

animation record start

Parameter Value Type Description

Parameter Value Type Description

Caution: AVI format is only available on Windows.

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

animation record stop

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Note: Clearances between parts is allowed only for post-processing clearances.

Note: Clearances between parts is allowed only for post-processing clearances.

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description

Parameter Value Type Description