load opto pulses

[neuromusic]

currently, optogenetic stimulation is only recorded as a boolean in the trials dataframe

we should be able to load a list of events (like licks or rewards) with durations that indicate optogenetic stimulation, along with whatever parameters are needed to describe the opto stimulus.

@dougollerenshaw & @mtv2101 what would such a dataframe look like? and what would the session-level parameters look like?

I'm specifically thinking of a way to support both our coarse stimulation from the pilot and @mtv2101's more focused manipulations that are planned.

session opto parameters

• power
• light source
• other things?

columns for individual opto presentations

• time (float)
• duration (float)
• coordinates?

[mtv2101]

Currently I only log optogenetic onset timestamps in my optogenetics branch. This most-simple logging was chosen because we have opted to control duration, amplitude envelope, power and other opto stim characteristics using an external device (PulsePal). This is also future proof given that production hardware will not have the ability to output analog waveforms (is this correct?).

Ideally we would log all opto parameters in the dataframe. This would probably be a waveform, an x/y centroid location, and a global scale-factor (to translate the waveform into real values like mW/mm^2). If I wish to log this info from my non-productions optogenetic rigs i'll have to re-introduce these data in some hacky way.

[nickponvert]

@dougollerenshaw I'm closing this. We will have to think again about opto stimulation for the potential np/opto recordings, but that is pretty far away.