It should be noted that inlogfile 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(1) 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(1) 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 inlogfile.
A file containing the table in the following format is then created using an editor :
where each "pseudo-code" is listed sequentially starting with 64 followed by the number of the condition code into which it should be mapped, one per line. When all is ready, remapccs is run thus:
where mapfile is the name of the ASCII mapping file, inlogfile is the recontructed logfile containing the"pseudo-condition codes" generated by makelog, and outlogfile is the name of a logfile which will be created and will contain the mapped condition codes. Two separate log files are used to allow multiple attempts at remapping without destroying the "pseudo-code" logfile.
Table of Contents