numeric_results create empty
Allows you to create an empty result set.
Format:
numeric_results create empty |
|---|
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:
Parameter | Value Type | Description |
|---|
new_result_set_name | A New Component | This parameter allows you to identify where the new data components are to be stored. |
comments | String | Specifies comments for the object being created or modified. |
Extended Definition:
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.
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.
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 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 request (.REQ) and results (.RES) files.
Result set type | Result set name | Component names | File that result is from |
|---|
part | PARxxx... | x y z e1 e2 e3 e4 mag vx vy vz wx wy wz accx accy accz wdx wdy wdz | results file |
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 fmag1 tmag1 fx2 fy2 fz2 tx2 ty2 tz2 fmag2 tmag2 fx3 fy3 fz3 tx3 ty3 tz3 fmag3 tmag3 | results file |
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) | | |
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.