Thank you so much for replying!
Is there a way to tell whether the error is a result of values supplied by the yaml file?
I couldn’t upload a yaml file, so I’ll just copy the content of the file here:
# specifies what devices to monitor
monitor_devices:
- Display:
name: display
reporting_unit_type: pix
device_number: 1
physical_dimensions:
width: 403
height: 304
unit_type: mm
default_eye_distance:
surface_center: 650
unit_type: mm
psychopy_monitor_name: default
- Experiment:
name: vrms
# SMI iView Config (cf. http://www.isolver-solutions.com/iohubdocs/iohub/api_and_manual/device_details/eyetracker_interface/SMI_Implementation_Notes.html)
- eyetracker.hw.smi.iviewx.EyeTracker:
name: tracker
enable: True
# *If* the ioHubDataStore is enabled for the experiment, then
# indicate if events for this device should be saved to the
# data_collection/keyboard event group in the hdf5 event file.
save_events: False
# streamEvents: Indicate if events from this device should be made available
# during experiment runtime to the PsychoPy Process.
# True = Send events for this device to the PsychoPy Process in real-time.
# False = Do *not* send events for this device to the PsychoPy Process in real-time.
stream_events: False
event_buffer_length: 1024
monitor_event_types: [BinocularEyeSampleEvent,]
network_settings:
send_ip_address: 192.168.1.2
# Port being used by iView X SDK for sending data to iView X
send_port: 4444
# IP address of local computer
# For Win10: Systemsteuerung\Netzwerk und Internet\Netzwerk- und Freigabecenter
# Set IPv4 of the ethernet connection to the ip specified here
receive_ip_address: 192.168.1.1
# port being used by iView X SDK for receiving data from iView X
receive_port: 5555
runtime_settings:
sampling_rate: 250
track_eyes: BINOCULAR_AVERAGED
sample_filtering:
FILTER_ALL: FILTER_OFF
vog_settings:
pupil_measure_types: PUPIL_DIAMETER
calibration:
# type: How many points should be used for the calibration sequence.
# Valid inputs are THREE_POINTS, FIVE_POINTS, NINE_POINTS
type: NINE_POINTS
# pacing_speed: How long a calibration point should
# be displayed before moving onto the next point when auto_pace
# is set to true. iViewX supports two values for this field: FAST and SLOW
# If auto_pace is False, pacing_speed is ignored.
auto_pace: Yes
pacing_speed: FAST
screen_background_color: 20
target_type: CIRCLE_TARGET
target_attributes:
target_size: 30
target_color: 239
target_inner_color: RED
show_validation_accuracy_window: True
# model_name: The model_name setting allows the definition of the eye tracker model being used.
# For the iViewX implementation, valid values are:
# RED, REDm, HiSpeed, MRI, HED, ETG, or Custom
model_name: REDm
data_store:
enable: False
experiment_info:
code: ystart
session_info:
code: S0001