File Options

The options on this page allow control over the generation and storage of files.

Base Directory

Specifies the root directory for data files to be saved in. Files for each stream are stored in sub-directories off this root. The sub-directory structure depends on the filename format.

Filename format

Allows the user to specify a different filename structure using a format specifier. If compatibility with MS-DOS or MS-DOS applications is required, then “A\X” should be used, to ensure an 8.3 naming convention.

Data Format

Selects the format of the recorded data files. Options are GCF, SAC, MiniSEED, P-SEGy, PEPP, SUDs, GSE, UFF (ufa, ufb), CSS.

Byte Order

For SAC, SEG-y, UFB and CSS files, the byte order of the files can be specified. This can be used to match the byte order with the native order of the hardware platform where the analysis is being performed. GCF and MiniSEED are defined to be in Motorola, or SPARC byte order. PEPP and SUDs data is defined to be in Intel byte order. GSE files are cm6 ASCII-encoded, so byte order is not applicable. UFA files are ASCII encoded, so byte order is not applicable.

Granularity

Select the method of file fragmentation required.
Specifies the amount of data that each file contains. See Recording for more information on generated files. Three different file durations can be set, for high sample rates, low sample rates and status streams. The distinction between high and low sample rates is set by the ‘Sample Rates >=“ option. If recording of files by their size is required instead of by duration, set the units selection box to Kilobytes, and set as appropriate.

Post-Processor

This option allows the user to specify a program which scream will run every time it closes a file. The name of the file is passed as a parameter. This feature provides great flexibility for interfacing with other analysis or archival systems. Typical uses might be:

• FTP or email files to remote data centres
• Format conversion using a third party utility
• Post-processing of file data headers to add site-specific information
• Automated printout of data or status information
• Automated transfer into analysis systems (e.g. PC-SUDS)

The command specified in the Post-Processor box can include any additional parameters necessary for the called program (e.g. GCFinfo needs the ‘view’ command to display the file). Because of this, the command line should not have any spaces in it, so the short pathname should be used (i.e. instead of “c:\program files\program”, use “c:\progra~1\program”).

See Also: Recording, Program Files, Setup