Closed tymees closed 2 years ago
I was thinking about incorporating stopIfExperimentClosed
in session.start
, because we probably always want to run it? and right now most templates don't call it at all
I was thinking about incorporating
stopIfExperimentClosed
insession.start
, because we probably always want to run it? and right now most templates don't call it at all
Probably all of the lexical decisions don't use it. I like the idea that we check whether the experiment is fit to handle new sessions in session.start Than we have one obvious place to check whether a session can start.
For now I moved the call to the start of main(): https://github.com/UiL-OTS-labs/jspsych-spr-mw/commit/bed42140f58f66a8ac8481f9def0e1a37b7dd2e7
We can plan a better solution later
Right now, the
setAccessKey
andstopIfExperimentClosed
are called early on inkickOffExperiment()
. However, this clashes with the newsession API
for list balancing in themain()
function.As that will make an API call before
stopIfExperimentClosed
is called, an API error will crash the experiment.Thus, the lines
on line 57 should be moved to be the first two lines of
main()