www.kxcad.net Home > CAE Index > MSC Software Index > Adams MD R2 Index

numeric_results list_info all

Allows you to use the ALL keyword to control what information about a particular result set component should be included as it is written to the terminal or file using the NUMERICAL_RESULTS LIST_INFO command.

Format:

 

numeric_results list_info all
result_set_component_name =	an existing component
write_to_terminal =	on_off
file_name =	string

Example:

 

numeric_results list_info all
result_set_component_name =	time
write_to_terminal =	on
file_name =	"c:\info.txt"

Description:

 

Parameter	Value Type	Description
result_set_component_name	An Existing Component	Identifies the component of an existing result set.
write_to_terminal	On_Off	Specifies whether the information requested is to be sent to the informational window or not.
file_name	String	Specifies that the information requested is to be sent to a file with the name specified with the parameter.

Extended Definition:

1.	If selected, the ALL keyword will cause the MAXIMUM_VALUE, MINIMUM_VALUE, TIME_RANGE, (or frequency, if appropriate) and NO_OF_TIME_STEPS to be output in the form of an informational message.

If there is no time/frequency range, the value listed is zero (0).

List all the information about the specified component.

2.

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

3.	This parameter is most likely to be used in conjunction with the FILE_NAME parameter to get the information to be put into a file.