-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: <lambda>() got an unexpected keyword argument 'time_out' #10
Comments
Difficult to tell without more context. At which stage during the test did this happen? |
Did the test otherwise work correctly? |
Sorry for the delay. The experiment saved the data correctly, I think! It threw the exception between trials 11 and 12. I am not sure what happened then. Could I have accidentally pressed an invalid key? -Cyrus
|
I have a vague idea about what might go wrong but in order to test it we need recipe for replicating this exception. |
OK. I will try to make a minimal example. |
It doesn't need to be minimal. Just find a way to reliably replicate the problem with your English test. Thanks! |
It looks like it happens when I press any key other than the two keys I set up in the config file (in my case, "c" and "i". In the the events below I was pressing the wrong keys a lot.... Does this happen to you too?
|
There are two different kinds of exceptions:
I think the first only occurs during the practice phase and the second only during the main test. The underlying cause is probably similar but I still haven't figured out when exactly I have to press the wrong keys in order to generate these exceptions. Either way, the exceptions are likely harmless because nothing is supposed to happen anyway when a wrong key is pressed. So the exceptions do not interfere with the test. But of course it's better to fix this anyway. |
The first error doesn't occur when a wrong key is pressed. It happens when a correct key is pressed while the feedback is shown ("oops" or "very good"). In fact, wrong keys can't trigger anything because no event handlers are bound to keys other than those needed for responses or aborting the program (esc). |
The second error occurs when a correct key is pressed while a memory item (a letter) is displayed. Both errors are completely harmless. I'll think about a fix. |
Glad it was nothing serious. :-) |
Thanks for reporting this, Cyrus! |
Any idea why this happened? (This was with the English Operation Span version)
The text was updated successfully, but these errors were encountered: