You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a rare but unforgiving problem. Sometimes ARCADE finishes a trial and then stops. No new trial is started. None of the buttons are responsive. The only solution is the run kill_arcade.bat. It makes me nervous because this will certainly happen during a real experiment, some day.
I am pretty certain that this freeze occurs between trials because I get my cleanUp state's onExit function to print "Finished", which is always printed. The cause is somehow a non-deterministic. It's rare and I do not know the exact conditions that lead up to it.
It could be that it is connected to pressing the "Pause/Quite Session" button in the Control Screen. At least, this was the case in the most recent freeze that I saw. Perhaps there are cases where the pause window fails to appear, for some reason.
I guess that the only way forward is to pop some logmessage( ) commands into SGLSessionArc.mRunSession to see how far it gets before the next freeze.
The text was updated successfully, but these errors were encountered:
jsdpag
added a commit
to jsdpag/ARCADE
that referenced
this issue
Jun 17, 2022
…CADE issue esi-neuroscience#31. Suspected freeze on account of failure to show pause window. Error messages will indicate whether freeze occurs during a trial or afterwards in the pause block.
This is a rare but unforgiving problem. Sometimes ARCADE finishes a trial and then stops. No new trial is started. None of the buttons are responsive. The only solution is the run kill_arcade.bat. It makes me nervous because this will certainly happen during a real experiment, some day.
I am pretty certain that this freeze occurs between trials because I get my cleanUp state's onExit function to print "Finished", which is always printed. The cause is somehow a non-deterministic. It's rare and I do not know the exact conditions that lead up to it.
It could be that it is connected to pressing the "Pause/Quite Session" button in the Control Screen. At least, this was the case in the most recent freeze that I saw. Perhaps there are cases where the pause window fails to appear, for some reason.
I guess that the only way forward is to pop some logmessage( ) commands into SGLSessionArc.mRunSession to see how far it gets before the next freeze.
The text was updated successfully, but these errors were encountered: