Add events handling: trace/map + new view for aliggned/rasters + PSTHs

[alejoe91]

Events can be passed to the run_mainwindow either as a dict:

{
    "event_key": {
         "samples": [.....], # or time
    }
}

In case of multi segment, the events must be list of lists/arrays.

Alternatively, one can use a spikeinterface.BaseEvent object.

The Trace/TraceMap views allow to go to previous/next event (and select event type in case of multiple).
A new EventView shows aligned rasters or PSTHs.
Here's how it looks:

event-sigui.webm

• panel Trace/TraceMap

[chrishalcrow]

Woah - one of the postdocs in my lab will love this!

[chrishalcrow]

@alejoe91 I don't think you've commited the eventview

[alejoe91]

done!

[alejoe91]

@chrishalcrow ready to test for real! :)

[samuelgarcia]

Lets move this events handling in a separate function no ?

[samuelgarcia]

I think we need to discuss the behavior we want.
If I understand correctly this is a psth segment by segment only.
Maybe we should also have a cumulate across segmetn psth no ?

Also the name eventview is to explore event I would call this veiw spikeonevent no ?

[samuelgarcia]

Cool.
TODO:

• psth and raster should gather acrros segments
• we should have an event_tools.py
• we should have lines and rates for the psth

[chrishalcrow]

Hello, our behavior often has a different time support than our ephys (e.g. we start recording events before we start recording ephys). Would be good to cleanly handle event times that are outside of the ephys time interval.

[alejoe91]

Hello, our behavior often has a different time support than our ephys (e.g. we start recording events before we start recording ephys). Would be good to cleanly handle event times that are outside of the ephys time interval.

Ok, basically just filtering the events (if given in time) based on the recording start/end times?