ioHub
ioHub copied to clipboard
isolver
A Python program, running as an independent process, that provides a 'proxy like' service for experiment runtimes ( psychopy ) and devices ( keyboard, mouse, parallel port, eye tracker, ... ).
Both in terms of mapping to modifier values and key field when modifier is pressed. Seems to be influenced by caplocks key state; different keysyms are being given based on...
The first run of a new experiment (i.e., no PATHS have been saved) first initializes a .hdf5 in the current working directory, then makes an additional .hdf5 after the PATHs...
Directories generated for each session should contain native device data and the trial list (only if using ConditionVariableProvider class?). Currently the native device data is stored in only the most...
On multimonitor setups, there have been two computers where the screen id determined for each monitor by ioHub is reverse to what it should be based on native Windows calls....
Currently, paths to experiment resources and results are relative to the experiment directory. It would be nice if we could specify absolute paths if someone wanted to store data or...
For example, it seems like it would be totally redundant to still have pyglet message handlers for keyboard and mouse events for the window when ioHub was providing these events....
Add support for a Display having a non full screen window being used for stim presentation; so the bounding rect of the 'display' therefore will depend on the window location...
Will give physical settings and calibration settings