You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebGazer no longer initializes automatically when the page loads. Instead, the webgazer-init-camera plugin will initialize WebGazer and ask for camera access permissions. Added an auto_initialize parameter to the WebGazer extension to allow users to initialize on page load if desired.
The sampling interval can be set in the WebGazer extension. By default the extension aims for 30Hz. Faster intervals are probably not possible until browsers provide better interfaces to synchronize processing with video feeds.
Improved the timing measurements reported by WebGazer by ~30 milliseconds. Timing is now based on an estimate of when the video frame was recorded, instead of when WebGazer finished computational work on the video frame.
jsPsych.pluginAPI.compareKeys can now handle null values: it will return true if both key arguments are null, and return false if one key is null and the other is a key code or key character. This means that this function can be used to check for a correct non-response. (jsPsych.pluginAPI.compareKeys handling null keys #1577)
Changes
Minor formatting and text updates to the webgazer-init-camera plugin to center the camera view.
The webgazer-validate plugin now records the coordinates of the validation points.
The webgazer-init-camera plugin now records the load time for WebGazer to initialize.
Added a point_size parameter to calibration and validation plugins, and set the default to a larger value.
Bug Fixes
Fixed an issue where webgazer_targets did not record the bounding box of content on the screen if the content was loaded after the trial began.
Fixed problem with the minimum_valid_rt parameter in jsPsych.init not working when the WebAudio clock is used to measure keyboard RTs (i.e. rt_method: 'audio' in jsPsych.pluginAPI.getKeyboardResponse). Thanks @kinleyid! (RT unit inconsistency and minimum_valid_rt #1675)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This minor release is focused on improvements to the eye tracking features added in version 6.3.0.
New Features
webgazer-init-camera
plugin will initialize WebGazer and ask for camera access permissions. Added anauto_initialize
parameter to the WebGazer extension to allow users to initialize on page load if desired.jsPsych.pluginAPI.compareKeys
can now handlenull
values: it will returntrue
if both key arguments arenull
, and returnfalse
if one key isnull
and the other is a key code or key character. This means that this function can be used to check for a correct non-response. (jsPsych.pluginAPI.compareKeys handling null keys #1577)Changes
webgazer-init-camera
plugin to center the camera view.webgazer-validate
plugin now records the coordinates of the validation points.webgazer-init-camera
plugin now records the load time for WebGazer to initialize.point_size
parameter to calibration and validation plugins, and set the default to a larger value.Bug Fixes
webgazer_targets
did not record the bounding box of content on the screen if the content was loaded after the trial began.minimum_valid_rt
parameter injsPsych.init
not working when the WebAudio clock is used to measure keyboard RTs (i.e.rt_method: 'audio'
injsPsych.pluginAPI.getKeyboardResponse
). Thanks @kinleyid! (RT unit inconsistency and minimum_valid_rt #1675)This discussion was created from the release v6.3.1.
Beta Was this translation helpful? Give feedback.
All reactions