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 current setting with this parameter.
■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 |
color = | existing color |
active = | on/off/no_opinion |
dependents_active = | on/off/no_opinion |
Example:
force attributes & |
|---|
Force_name = | FORCE_1 & |
Color = | RED & |
Name_visibility = | OFF & |
Active = | On & |
Dependents_active = | OFF |
Description:
Parameter | Value Type | Description |
|---|
force_name | 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 | Real | Specifies the size, in modeling units, the Adams View icons will appear in. |
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 | 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. |
dependents_active | On/OFF/NO_OPINION | When you set ACTIVE=NO, that element is written to the data set as a comment. |
Extended Definition:
1. You may identify a 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 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.
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.
3. 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 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 a SIZE_OF_ICONS set, and a part under that model has a different 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.
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 visibility of an entity and reverse it.
5. 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.
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
.geometry(circle) ------- BLUE
The circle will be BLUE.
7. 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.
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