Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Placing pygaze_log after pygaze_stop_recording

I'm using PyGaze with a Tobii eye tracker. In the Visual world tutorial the pygaze_log item is placed just before the pygaze_stop_recording item. The eye tracker is thus still recording during logging and this makes for a messy part in the data as eye tracking data is still saved in between the vars, see image. Also, previously we encountered some issues with the formatting of the data where the rows of the vars and eye tracking data would get mixed up, although we have not seen this happen recently.

Is there any harm in placing pygaze_log after pygaze_stop_recording?


Comments

  • Hi,

    I am not entirely sure whether I remember right, but I think if you have the logger after the stop, you won't log your variables/messages. To be sure, why not just trying it?

    Messy data files are rather normal in eye tracking, as you often don't even need all the samples, but rather more meaningful things like saccades, blinks, etc. So, it is common practice to parse the raw eye tracking log file and extract information you need. I am not aware of a "common" parser that is standard in the field (they are commonly taylored to ones experimental structure), but if you google, you will find some examples.

    Hope this helps,

    Eduard

    Buy Me A Coffee

  • Thanks for your reply! I tried it and it does seem to log the variables correctly. But I just wanted to make sure.

    Thanks,

    Iris

Sign In or Register to comment.