psychopy_monitor : (deprecated) The path to a Monitor Center config file Examples: A. : str Add an ioHub Device by using the device class path as the key, and the device's configuration in a dict value. the 'device_list' section of the yaml file. iohub_config_name : str Specifies the name of the iohub_config.yaml file that contains the ioHub Device list to be used by the ioHub Server.
#Mouse status iohub psychopy update
Information like display size, viewing distance, coord / color type is used to update the ioHub Display device. window : :class:`` The psychoPy experiment window being used. experiment_info : dict Can be used to save the following experiment metadata fields: code (<=256 chars), title (<=256 chars), description (<=4096 chars), version (<=32 chars) session_info : dict Can be used to save the following session metadata fields: code (<=256 chars), name (<=256 chars), comments (<=4096 chars), user_variables (dict) datastore_name : str Used to provide an ioHub HDF5 file name different than the session_code. session_code : str, <= 256 char When specified, used as the name of the ioHub HDF5 file created for the session. To customize how the ioHub Server is initialized when started, use one or more of the following keyword arguments when calling the function: Parameters - experiment_code : str, <= 256 char If experiment_code is provided, an ioHub HDF5 file will be created for the session. Mouse: named 'mouse', with runtime event reporting enabled. The following Devices are enabled by default: - Keyboard: named 'keyboard', with runtime event reporting enabled.
By default (no kwargs specified), the ioHub server does not create an ioHub HDF5 file, events are available to the experiment program at runtime. Def launchHubServer ( ** kwargs ): """ Starts the ioHub Server subprocess, and return a :class:`` object that is used to access enabled iohub device's events, get events, and control the ioHub process during the experiment.
0 kommentar(er)
