Adams Basic Package > Adams View > View Command Language > numeric_results > numeric_results create filter

numeric_results create filter

Allows you to test each value of the component; if the value is above the specified maximum value, or below the specified minimum value, set it to zero. For example: If the component is a discrete sampling of a sinusoidal wave with an amplitude of one (1), and filter is requested with a maximum value of .9 (above_value=.9), all the values corresponding to 'sin (x) > .9' will be set to 0.

Format:

numeric_results create filter
result_set_component_name =	an existing component
new_result_set_component_name =	a new component
below_value =	real
above_value =	real
units =	units_type_with_calc

Example:

numeric_results create filter &
result_set_component_name =	time &
new_result_set_component_name =	rsc__1 &
units =	time

Description:

Parameter	Value Type	Description
result_set_component_name	An Existing Component	Identifies the component of an existing result set.
new_result_set_component_name	A New Component	This parameter allows you to identify where the new data components are to be stored.
below_value	Real	The BELOW_VALUE parameter is used as a critical value evaluator in the operation to be performed.
above_value	Real	The ABOVE_VALUE parameter is used as a critical value evaluator in the operation to be performed.
units	Units_Type_With_Calc	Allows you to specify the type of units to be used for the new result set component.

Extended Definition:

1. The component must be in an existing result set and reference to the component must include the result set name. 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 refer to the X component in the result set REQ1, enter .SHIFT.REQ1.X (the .SHIFT. may be omitted if shift is the current analysis_name). SHIFT refers to the analysis name that result set came from (or is stored under).

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)

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. The below_value parameter is a critical value which determines the threshold below which a particular numeric value will be modified, printed, etc. (depending on the operation to be performed).

This parameter is optional and if not entered, no value will be passed to the application, and therefore, no action will be taken based on the BELOW_VALUE parameter. If entered, the BELOW_VALUE parameter must be a real number.

4. The above_value parameter is a critical value which determines the threshold above which a particular numeric value will be modified, printed, etc. (depending on the operation to be performed).

This parameter is optional and if not entered, no value will be passed to the application, and therefore, no action will be taken based on the ABOVE_VALUE parameter. If entered, the ABOVE_VALUE parameter must be a real number.

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