Repository navigation
Wrap EyeTracker events with Pythonic EyeEvent objects - #49
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Description
This PR updates the klibs EyeTracker API to return standardized eye event objects (e.g.
FixationStart,SaccadeEnd, etc.) when retrieving the tracker's event queue. This makes it easier to share code across tracker types as well as provides a much nicer and friendlier API for getting information about the attributes of different events (e.g. the start and end positions for a series of saccades, the duration of blinks).The documentation for the KLEyeTracker module has also been overhauled extensively.
Merge Checklist
closes #<issue-number>to automatically close an issue