Adams Basic Package > Adams View > View Command Language > file > file dac write

file dac write

Allows you to export DAC-format request files from Adams View after a simulation completes. This technique does not require you to set up requests before running the simulation.

nCode International created the DAC file format. This DAC format supports single-parameter (time series), two-parameter (x-y), and three-parameter (histogram) files. Adams Durability supports the time series format. With this DAC format, you can input data from durability test machines and output data to nSoft and other DAC-compatible programs. This topic contains an overview of the DAC format. For a detailed description of the DAC format, see the nSoft data File Formats document from nCode International.

DAC files are binary, sequential, and fixed-length with 512-byte records. The data represent a fixed sample rate or time step. Real numbers are single-precision (4-byte) values. Each file has header, data, and footer regions. Adams Durability supports both old (pre version 5.0) and new (version 5.0+) DAC formats with a single channel of time series data.

In general, DAC files are not portable from platform to platform. For example, files created by Adams Durability on a Windows platform are not readable by Adams Durability or other programs on Linux platforms. nCode provides an nSoft utility to convert DAC files from one platform to another. However, this utility does not have a specification for the Linux platform. When using Adams Durability or Adams View on a Linux platform, use DAC files that have been converted to Windows or INTEL (Windows DAC files are compatible with Linux). Note that Linux-generated DAC files can be processed on Windows and vice versa.

Format:

file dac write
file_name =	file_name
result_set_component =	existing result_set

Example:

file dac write &
file_name =	c:\data\dac_format &
result_set_component =	my_result_set

Description:

Parameter	Value Type	Description
File_name	String	Specifies the name of the file that is to be read, written, or executed.
Result_set_component	Existing Result Set	Identifies the components of an existing result set. The components must be in an existing result set and reference to the component must include the result set name.

Extended Definition:

1. The proper extension in the file_name parameter is the default, but you can override it by supplying a different extension.

It is not necessary to enclose the file name in quotes if it only contains alphanumeric characters and starts with a letter. If you want to include other characters, such as a '.' for an extension or '/' or '[]' for directory paths, you must enclose the file name in quotes.

2. For example, assume you read a request file named shift.req, and this request file contains the result set REQ1. If you want to refer to the X component in the result set REQ1, enter .SHIFT.REQ1.X (you can omit .SHIFT. if SHIFT is the current analysis_name). SHIFT refers to the analysis name from which the result set came (or is stored under).

Result sets are associated with an analysis and can be identified as such. A result set associated with request 101 from an analysis named test can be referred to as .test.req101.

The table illustrates the default names assigned to result sets and result set components read from request (.req) and results (.res) files.

Result set naming

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)