Closed hunse closed 3 years ago
Ok, I think I've addressed all of the comments. I ended up making a ChipProcess
class; any nodes with a process subclassed from this will be put on the chip. This keeps things cleaner in the builder (we care about this in the connection builder, in addition to in the splitter). It also makes it possible for users to add their own chip processes, and makes it easier for us in the future if we want to add more.
I got rid of DVSFileChipNode
entirely, and renamed the process to DVSFileChipProcess
so it should be clear that it's sending spikes directly to the chip (I also made a note about this in the example).
This allows loading DVS input from either
.aedat
or.events
files and sending it to the chip.