Closed sdevlin3001 closed 4 years ago
Hey Shannon. Just to be clear, you want me to take times from gazepoint data from the 'Time' column (doing so would make the code identical for FOVIO and gazepoint).
On Sun, Aug 9, 2020 at 1:50 PM sdevlin3001 notifications@github.com wrote:
Assigned #23 https://github.com/Clemson-Riggs-Lab/Eye_Tracking_S20/issues/23 to @samsmith0704 https://github.com/samsmith0704.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/Clemson-Riggs-Lab/Eye_Tracking_S20/issues/23#event-3636650272, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOITXKZVE6TWJDQOPPG2QD3R73OV5ANCNFSM4PZJNRBA .
Hi Sam. It technically won't be identical to FOVIO because FOVIO's Time column is in units of ms and Gazepoint's time units are in seconds. Angular velocity values should not be impacted since they should already be in units of degrees/second but I imagine start and end times of the saccade will be. Does that make sense?
This is a random issue I am just realizing could be problematic when analyzing all eye tracking files at once. For data collected with Gazepoint, make sure all scripts (except DataQuality.py), is using "Time" column (column AW) and NOT MissionTime. This is because MissionTime is only established once running DataQuality.py, which I will most likely run for all/most files at some point, BUT on the chance I don't, I want to make sure event detection scripts can be executed smoothly. From what I can tell, ED_with_pandas.py is the only file using MissionTime for Gazepoint eye trackers, all other files are, correctly, using the "Time" column (column AW), so this is currently only a minor issue, but I wanted to post it to general issues for awareness. @samsmith0704 if you could confirm that it is only an issue for ED_with_pandas.py, that would be great.