A DADiSP command file is an ASCII text file containing a list of DADiSP commands and keystrokes. Command files are designed to run a DADiSP session (or part of a DADiSP session) in an automated fashion. Your command file can load existing Worksheets, build a Worksheet on the fly, use built-in functions as well as your own custom functions and macros, format Worksheet Windows and layout, and use menus and messages to interact with the user. As you write a command file, keep in mind the purpose of your command file. Are you writing it to:
Automate repetitive commands?
Create a custom interface, so that the user can make simple choices to perform complex analysis?
Perform batch processing of multiple Series or Datasets and print out results?
Create a demonstration program?
No matter what your goals, DADiSP’s features and functions allow you to write simple or complex command files.
To create a command file, select Command Files, New from the Tools pull-down menu. Although command files can be named with any legal operating system filename, the DADiSP convention for command file names is to use a ".dsp" extension.
When typing commands into a command file, you can put multiple commands on one line, or spread them out so that the command file is easier to read. Case is not important except when referencing names of Labbooks, Worksheets, Datasets, and Series. DADiSP Labbook, Worksheet, Dataset and Series names are case sensitive, e.g., the Series RUN1.1.ANALOG1 is different from Run1.1.Analog1. Make sure you end the text file with a carriage return / line feed (so that there is a blank line at the end of the file).
Note: You can write command files using any text editor such as Notepad or emacs and vi (under UNIX/LINUX).