search

edeno / Jadhav-2016-Data-Analysis

Code for analysis on data from Jadhav et al. 2016
GNU General Public License v3.0
2 stars 5 forks source link

DIO pulses are corrupted for a couple of animals #7

Open edeno opened 8 years ago

edeno commented 8 years ago

The DIO file has six channels corresponding to motion detection (the animal is near the reward well) or reward delivery for each of the three reward wells located at the end of each arm. So the animals' position (as marked by infrared diodes on top of the microdrive preamp) when these channels are active should correspond to the end of the arms where the reward well is located. However, this is not always the case:

Blue lines indicate the rat's position in the W-track. Red dots correspond to the rat's position when either motion detection or reward delivery is triggered

Blue lines indicate the rat's position in the W-track. Red dots correspond to the rat's position when either motion detection or reward delivery is triggered. Data is from rat 'HPa', day 8, epoch 2. See python notebook UnderstandingDIO for more plots and code.

I emailed Demetris and he confirmed there might be an issue:

Unfortunately you will have to ask shantanu about the other issues as I seem to remember him saying something about his dio pules being corrupted for a couple of the animals leading to the displaced position/time issue that you're seeing (so don't worry you're not crazy :)). By now, he may have manually corrected these pulses or reconstructed the dio-like info from the position or something.

I will email Shantanu and see if he has any solutions

edeno commented 8 years ago

Update from Shantanu:

The DIOs were unfortunately corrupted for this data set, so for some fraction of them, the DIO times are incorrect. I don't think there is any way of correcting this. I did run a cross-check to find DIOs that were in the correct location, but did not use this for any analysis.

edeno commented 8 years ago

Yes, I had to use the position data for the reward behavior, which of course does not have the temporal resolution of the DIOs. The DIO timing corruption was an unfortunate thing, a hardware logging error that only came to light later.