[2024.2.2 compatibility+] Error Messages I can't make sense of

Hi,

I am trying to make a new experiment with version 2024.2.2. compatibility+, but when trying to execute the experiment it aborts and I get a bunch of error messages in the Runner’ stdout that don’t seem to have anything to do with my experiments custom code or elements. stdout at the end.

Could it be, that the issue is that I have two versions of PsychoPy installed (2024.2.2 compatbility+ and 2021.1.4) which conflict with one another when trying to execute an experiment? It wasn’t an issue for other experiments so far.

My timeline only contains 2 routines

The loop calls on a .xslx sheet, which contains the values for the inst_base_sheets

I don’t know what the issue is…

Generating PsychoPy script...

## Running: C:\Users\Mitarbeiter\Desktop\LESON 7 Performance\Experiment Vorlage\LESON 7 Performance Vorlage_lastrun.py ##
47.9340     INFO     Loaded monitor calibration from ['2024_04_09 16:45']
47.9744     INFO     Loaded monitor calibration from ['2024_04_09 16:45']
pygame 2.1.0 (SDL 2.0.16, Python 3.8.10)
Hello from the pygame community. https://www.pygame.org/contribute.html
8.3421     WARNING     launchHubServer: If using the iohub mouse or eyetracker devices, fullScr should be True.
Traceback (most recent call last):
  File "C:\Users\Mitarbeiter\Desktop\LESON 7 Performance\Experiment Vorlage\LESON 7 Performance Vorlage_lastrun.py", line 769, in <module>
    run(
  File "C:\Users\Mitarbeiter\Desktop\LESON 7 Performance\Experiment Vorlage\LESON 7 Performance Vorlage_lastrun.py", line 457, in run
    if defaultKeyboard.getKeys(keyList=["escape"]):
  File "C:\Program Files\PsychoPy\lib\site-packages\psychopy\hardware\keyboard.py", line 494, in getKeys
    self.dispatchMessages()
  File "C:\Program Files\PsychoPy\lib\site-packages\psychopy\hardware\keyboard.py", line 607, in dispatchMessages
    key_events = KeyboardDevice._iohubKeyboard.getKeys(clear=True)
  File "C:\Program Files\PsychoPy\lib\site-packages\psychopy\iohub\client\keyboard.py", line 329, in getKeys
    self._syncDeviceState()
  File "C:\Program Files\PsychoPy\lib\site-packages\psychopy\iohub\client\keyboard.py", line 232, in _syncDeviceState
    events = {int(k): v for k, v in list(kb_state.get('events').items())}
AttributeError: 'str' object has no attribute 'get'
  File "C:\Program Files\PsychoPy\lib\site-packages\psutil\_pswindows.py", line 679, in wrapper
    return fun(self, *args, **kwargs)
  File "C:\Program Files\PsychoPy\lib\site-packages\psutil\_pswindows.py", line 933, in create_time
    user, system, created = cext.proc_times(self.pid)
ProcessLookupError: [Errno 3] assume no such process (originated from GetExitCodeProcess != STILL_ACTIVE)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\PsychoPy\lib\site-packages\psutil\__init__.py", line 354, in _init
    self.create_time()
  File "C:\Program Files\PsychoPy\lib\site-packages\psutil\__init__.py", line 710, in create_time
    self._create_time = self._proc.create_time()
  File "C:\Program Files\PsychoPy\lib\site-packages\psutil\_pswindows.py", line 681, in wrapper
    raise convert_oserror(err, pid=self.pid, name=self._name)
psutil.NoSuchProcess: psutil.NoSuchProcess process no longer exists (pid=7024)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\PsychoPy\lib\site-packages\psychopy\iohub\start_iohub_process.py", line 118, in <module>
    Computer.psychopy_process = psutil.Process(psychopy_pid)
  File "C:\Program Files\PsychoPy\lib\site-packages\psutil\__init__.py", line 326, in __init__
    self._init(pid)
  File "C:\Program Files\PsychoPy\lib\site-packages\psutil\__init__.py", line 367, in _init
    raise NoSuchProcess(pid, None, msg)
psutil.NoSuchProcess: psutil.NoSuchProcess no process found with pid 7024
################# Experiment ended with exit code 1 [pid:7024] #################

I’m getting this sometimes at the moment. The fix for me is to switch to PsychToolbox Input

I wanted to try that, but today the experiment worked without any problem at all…
But I’ll keep your idea in mind, in case it happens again.