|
|
|
The current position of the cursor relative to date and time is displayed at the top of the screen as
Cursor date and time = date time
The EVENT # column indicates a unique number applied to the event marker at the time it was enabled during data acquisition. Event marker numbers are always assigned sequentially (i.e., starting with 1 and incrementing until the last event marker enabled is reached, or until the maximum number of event markers is achieved. Refer to Event Mark Editing for details related to event marker memory consumption). Event marker numbers followed by a star (*) indicate those automatically created by data acquisition at the start of a storage-to-disk cycle.
The TBF column indicates the event marker's position in time relative to the beginning of the data acquisition file. All values are annotated in seconds.
The TM column displays the event marker's position in seconds relative to the time marker if the time marker is enabled.
The %EOF column indicates the position of the event marker relative to the end of the data file as a percentage.
The DATE column displays the date on which the event marker was enabled.
The TIME column indicates the time at which the event marker was enabled to the nearest second.
The COMMENT column displays the comment that was provided (if any) at the time the event marker was enabled during data acquisition. Assuming a full 39-character comment was provided for the event marker when it was enabled, the comment will appear truncated if the time marker function is enabled. Characters consumed by the time marker column are freed for comment display when the time marker is disabled.
When you scroll the event list to an event number greater than the total enabled during acquisition, all columns (except EVENT #) will display **.
The TM column is active only if the time marker was enabled when the search-for-event function was invoked. If the time marker was not enabled, ** will be displayed in the TM column.
If no event markers were enabled during data acquisition, the data file will be padded with 256 equally spaced event markers to allow the SEARCH-FOR-EVENT function to be used to quickly vector to any area of the data file.
