AEDAT 3.0
This section explains how version 3.0 differed from version 3.1.
Header Lines
The version header line reads as follows:
#!AER-DAT3.0\r\nThere is no end of header line required. Therefore, the only way to check where the header ends is to check that a line starts with the ‘#’ character and then read the line up to the new-line marker, but this can fail if the very first byte of the first event also has a value of 35 (decimal), corresponding to the ‘#’ character.
Polarity Event
The origin point is in the lower left of the screen rather than the upper left, meaning that it is not compatible with the standard computer graphics way of doing things, e.g. libraries such as OpenCV.
Frame Event
The origin point is in the lower left of the screen rather than the upper left, meaning that it is not compatible with the standard computer graphics way of doing things, e.g. libraries such as OpenCV.
The color filter enumeration values are different due in part to a smaller available range; the ROI identifier is thus positioned differently. Both features were never in active use for AEDAT 3.0:
Bytes |
Meaning |
Description |
|---|---|---|
0-3 |
32 bit info |
Holds information on the frame event. |
Bytes 0-1 are divided in the following way:
Bits |
Description |
|---|---|
0 |
… |
1-3 |
… |
4-6 |
Color filter information used for interpolating color images (demosaicing). Valid values are: MONO(0), RGBG(1), RGBW(2). |
7-13 |
ROI (Region of Interest) identifier (up to 128). |
New Event Types
The following event types were not implemented in version 3.0:
Spike