The history files are introduced according to the SEP (Stanford Exploration Project) history files, although there are some differences, especially in running the programs.
The history files are designed to contain both the data and the information how to execute the programs. The following items are recognized in the history files:
No other items are interpreted in this version. All text containing neither equals nor colons has thus the effect of comments.
If the DATA for a program (i.e., string right to the colon) contain a substring identical to the name of the history file, the program is assumed to read the history file. In such a case, only the PARAMETER=VALUE couples between the beginning of the history file and the "colon" instruction to execute the program are assumed to apply to the program. This convention enables to modify the data for the program by entering additional PARAMETER=VALUE couples and additional "colon" instructions to execute the programs within the same history file.
When executing the history file, it is copied line by line to the output history file. When a "colon" instruction to execute the program is encountered, the program is executed with the name of the output history file substituted for the name of the input history file in order to hide the PARAMETER=VALUE couples between the "colon" instruction and end of file to the program.
The history files may be executed by Perl script
go.pl. For example, history file
'file.h' may be executed by command
perl go.pl file.h
generating the output history file named 'file.out'. If you wish to name the output history file, e.g., 'new.out', the history file may be executed by command perl go.pl file.h new.out
Perl interpreter should be available at www.perl.org
Example of the history file: corfun.h.
Alphabetical list of input parameters of all programs.