Closed caiw closed 2 months ago
I added some of these to visual-input-stream.
For tactile, these are set to as none
as they are not relevant for the current datasets
Note that audio_delivery_shift_correction
is correctly 0.0
for dataset 3 - we have the MISC channel and have confirmed there was no drift (luckily, as I don't think I would have noticed this if there was.).
Interestingly, the config for dataset 3 was incorrect anyway, and had the audio and delivery delays from 4, so good job you put this issue here Cai.
Completed as part of #290, tested and confirmed to mimic previous results.
As mentioned in #290, these fields have been added to config files but aren't yet correct:
audio_delivery_latency
visual_delivery_latency
tactile_delivery_latency
audio_delivery_shift_correction
tactile_delivery_shift_correction
audio_delivery_latency
visual_delivery_latency
tactile_delivery_latency
audio_delivery_shift_correction
visual_delivery_shift_correction
tactile_delivery_shift_correction
audio_delivery_latency
visual_delivery_latency
tactile_delivery_latency
audio_delivery_shift_correction
visual_delivery_shift_correction
tactile_delivery_shift_correction
Note to people doing this
stimulus drift can be done using (
trigger == 2
)