Dear all,
I am pretty much new in terms of Nengo usage, hopefully somebody in this forum have had the experiences with various DVS (Dynamic Vision Sensor) file formats.
Namely, I have tried to to read the MNIST-DVS events by usage of “nengo_loihi.dvs.DVSFileChipProcess” as it has been shown in the example.
However, the events read by the “DVSFileChipProcess” always missing y-axis which is set to zero which should not be the case:
Event: 15247
x: 4
y: 0
t: 1240570
p: 0
v: 0
Event: 15248
x: 4
y: 0
t: 1240581
p: 1
v: 0
Event: 15249
x: 4
y: 0
t: 1240590
p: 0
v: 0
Since DVS-MNIST is in aedat2.0 format and Nengo implementation supports the same format where is the mismatch?
a) The Nengo aedat2.0 implementation
b) Here is another implementation of the dataloader which provides
which provides good output, for example:
Evnt: 15000
x: 66
y: 69
t: 1214176
p: 1.0
Evnt: 16500
x: 75
y: 55
t: 1307373
p: -1.0
It seems to me that in current Nengo impelmentation for aedat2.0 DVS format
contains additional fields apart of (y-axis,x-axis,p-polarity,t-time stamp) which are not present in
aedat2.0 format, am I right? And what would be the remedy for such situation?
fields = [
(“type”, ctypes.c_uint64, 1),
(“y”, ctypes.c_uint64, 9),
(“x”, ctypes.c_uint64, 10),
(“polarity”, ctypes.c_uint64, 1),
(“trigger”, ctypes.c_uint64, 1),
(“adc_sample”, ctypes.c_uint64, 10),
(“t”, ctypes.c_uint64, 32),
]
def etuple(e):
return (e.y, e.x, e.polarity, e.trigger, e.t)
Thank you,
With best ragards,
GK.