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 |
|---|
entity_name = | an existing entity |
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:
Parameter | Value Type | Description |
|---|
entity_name | An Existing Entity | Specifies the name of an existing entity |
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 |
Extended Definition:
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 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 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 separate multiple database entity picks by commas.
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 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. 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.