There are certain times when you will want to import with an external header file. Examples when you would use a separate header file include:
Import of all or multiple channels of a multi-column or multi-channel file in one step
Import of sequential multi-channel files
Import of data with byte swapping enabled
Import of data which requires x- and/or y-axis modification (e.g. scaling)
Use of Import Keywords which are not available in the default header
To create a separate DADiSP header file, select Header File, New Header from the Data pull-down menu. This header file will describe what is contained in your data file, and how you want DADiSP to import and store each channel. There are many DADiSP keywords which can be used to describe your file; see the section below on Import Keywords for keyword definitions. Make sure that the file ends with a blank line (i.e., a carriage return and line feed), and save the file as an ASCII text file.
DADiSP Import Keywords can appear in any order in the file. Each keyword must appear on a separate line. The syntax for the keywords is as follows: keyword, space(s), argument(s) separated by commas or spaces. Multiple lines for each keyword are allowed. That is, if there is not enough room on a line for all the arguments to the keyword, you can create another line with the same keyword, and continue with the argument list. DADiSP will append the arguments on duplicate keyword lines to the previous values. When using multiple lines for keywords, the subsequent lines do not have to be adjacent (although it is easier to read if they are adjacent). Finally, keywords are case insensitive. Arguments are case insensitive except for the following, which are case sensitive: Dataset Names, Series Names, and Labbook Names.
A DADiSP header, Test2.hed, might look like this:
SERIES Accel_1, Accel_2