During the course of an experiment, condition codes are altered while digitization is paused; whenever a pause occurs, a pause mark is placed in the log file. Whenever makelog encounters a pause or delete mark in the raw file, it increments the condition code in logfile. These "pseudo-condition codes" start at 64 (decimal) at the beginning of the raw file, and proceed upward. After makelog is done, one will have the logfile with "pseudo-condition codes" which need to be mapped by the experimenter into the appropriate values. The programs logpoke(1) or remapccs(1) can be used for this purpose; consult their man pages for details on how this is accomplished.
It should be noted that logfile may not contain events that occurred very near the end of the raw file, most noteably the final pause mark if the dig program was paused just before exiting. This is due to the fact that makelog uses the same low-level routines to read the raw file as other programs such as garv(1) and avg(1) : these programs purposefully ignore events in the last few records of the raw file to ensure that all events are followed by at least an epoch’s worth of raw data; the side-effect to makelog is that any events very near the end of the raw file will not be read and thus will not be present in the regenerated logfile.
Table of Contents