numeric_results create scale

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.

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.

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).

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.