geometry modify shape shell
Allows you to modify an existing shell object.
Format:
geometry modify shape shell |
|---|
shell_name = | an existing shell |
new_shell_name= | a new shell |
comments = | string |
reference_marker = | an existing marker |
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:
Parameter | Value Type | 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. |
comments | String | Specifies comments for the object being created or 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 |
Extended Definition:
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. For more information, see
Using Extended Names.
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:
"...._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.
3. 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.
4. 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.
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:
8 6 1.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
-1.0 -1.0 -1.0
-1.0 1.0 -1.0
1.0 1.0 -1.0
1.0 -1.0 -1.0
4 1 2 3 4
4 5 6 2 1
3 2 6 7
4 3 7 8 4
4 1 4 8 5
4 8 7 6 5