Timing out Experiment after specified time.

Comments

• Fab

  November 2021

  Hi @Artabanos,

  This is happening because at the time you define trialTime (trialTime = self.get("time_trialSequence")), the trialSequence object has not started, hence it's time of onset has not been defined.

  You could try is the following:

  (1) define the maxtime as you currently, remove everything else from your timer script.

  (2) at the beginning of your expSequence, define blockTime

  (3) at the beginning of your trialSequence, define your trialTime

  (4) in the settings of your expLoop, use the "break if" option and set it to ([trialTime]-[blockTime] >= [maxtime]. Now, whenever that condition is met, the expLoop will be interrupted and the task will move to whether comes after that loop. If the Break if condition can't include operations, go back to step 3 and add a variable measuring the difference between trialTime and blockTime (let's say you call it timeElapsed), and set the break if condition to [timeElapsed] >= [maxTime].

  Haven't tried implementing this myself but I think it should work.

  Good luck!

  Fabrice.

  
• Artabanos

  November 2021

  Hi Fabrice,

  Thank you for your extensive and helpful reply! I didn't actually manage to get your solution to work, but your suggestions did lead me to a solution that ended up doing what I wanted it to do.

  1) Before any loops began, I defined maxTime as 30000 ms well as elapsedTime as an empty integer (using the int() function). This allows the trial loop later to call elapsedTime even though there is no value to this yet. I also allowed both of these values to be called by OpenSesame using the self.experiment.set() function.

  2) Then, I added another inline script as the final step in my trialSequence. This script defines: timeStart = self.get("time_trialBlock") as well as timeOut = self.get("time_LCTstring"). timeStart, in this case, is the time at which the trial block started, and timeOut calls the time at which the last stimulus was presented. timeStart is a static value, whereas timeOut updates every time a stimulus appears on screen.

  3) In the same script, I defined another variable as the difference between these two points in time: elapsedTime = timeOut - timeStart (and, again, set this variable to be used with self.experiment.set())

  4) Finally, in my trialBlock loop, I used the 'break if' function and set this to [elapsedTime]>=[maxTime].

  In this way, trialBlock calls only values already initialised and therefore won't terminate the experiment, and it neatly times out 30000ms (30 seconds) after the start of the trial block.

  Thanks again for your help @Fab , much appreciated!

  Willem
• Fab

  November 2021

  Hi Willem @Artabanos,

  Great stuff! Glad you got it to work and solved the problem! 👍️

  Good luck with your experiment!

  Fabrice.

  
• ChrisSw

  September 9

  Hello everyone,

  
  

  i´m trying to do the same thing but i´m not able to see my mistake here. I want to implement different block times so i guessed that i needed more scripts, since i was trying to set either one minute or like 52000ms or so. (2 scripts for each block varying in its maxTime)

  
  

  After trying to trouble shoot i came across this thread. Maybe you can help me out by giving me either some further instruction or showing me the script that seems to have worked out in the end.

  
  

  Here are my scripts so far.

  

  

  Since i´m new to OpenSesame, please try explaining step-by-step.

  
  

  Thank you in advance.

  
  

  Kind regards, Chris😊
• eduard

  September 15 edited September 15

  Hi Chris,

  This example demonstrates the principle. You can adapt it to your needs.

  Since i´m new to OpenSesame, please try explaining step-by-step.

  As I see, you are not only new to Opensesame but also to Python. Understanding both is quite useful when using the software and building your experiments. I recommend you try some of the tutorials, and maybe also a Python course. If you have a basic understanding of those things, your coding experience will be much nice ;)

  timer.osexp

  Eduard

  
• ChrisSw

  September 15 edited September 15

  Yea,

  i‘m quite new to all of this. The Experiment is required for my bachelor thesis. I‘ll try this out First thing in the Morning, thank you so far, Eduard.
• mhilliard2

  November 7

  @Artabanos

  Do you mind sharing your LC task? I am making a pattern comparison task, but I am experiencing difficulties implementing the 30000 ms timeout. Specifically, I am receiving the feedback that my in-line script is missing the required positional argument 'val'. I followed your steps, stating: self.experiment.set(maxTime).

  Did you run into this error while creating your successful task?

  @eduard I attempted implementing the language used in the timer task you shared, however, when using this, the entire task times-out at 30000 ms, rather than the trial block. Additionally, the trial does not run for a complete 30000 ms, it is variable but always ends before the full duration. Does this have something to do with the block_dur and clock_time variables?

  Thank you
• eduard

  November 7

  Hi,

  when using this, the entire task times-out at 30000 ms, rather than the trial block

  There is only one block in the experiment. Sop ending the block means ending the experiment.

  the trial does not run for a complete 30000 ms

  I suppose you mean 3000 ms? How do you know it doesn't do it? In the example there is no logger, so that you can't see how long exactly the block ran. When I add a logger I consistently see durations larger than 3000 which is expected.

  
• mhilliard2

  November 7

  @eduard

  I am hoping to run each trial block for 30000 ms, or in other words, 30 seconds. Meaning that the two trial blocks will run for separate 30000 ms durations. I personally timed each trial to see how long the trial block duration lasted, and both lasted less than the full duration by a matter of a couple thousand ms.

  I am hoping to run two separate blocks with different stimuli, for 30000 ms each. Is it possible to change the language in the timer OS task you shared, so that I may run each task block separately for a full 30000 ms each?
• eduard

  November 8

  I am quite sure the code works. Can you share your experiment, I shall try to see what is going on

  
• mhilliard2

  November 10

  LetterComparison.osexp

  Hello,

  My pattern comparison task is too large of a file to attach within this forum, so I have shared my letter comparison task that uses the in-line script you have shared in your timer task. I am hoping to make each of the two trial blocks last for 30000 ms total. Currently, the run time for the first trial block is variable and the second trial block is not running (I am guessing as a result of the maxTime variable). Regardless, I am looking for advice on how to get each trial block to run for a smooth set 30000 ms.

  Thank you!
• eduard

  November 11

  Hi,

  the second trial block is not running

  You need to reset block_dur . Otherwise it will already be at the start larger than 30s

  the run time for the first trial block is variable

  Because the duration of the items inside the actual loop is not in your control, you won't be able to guarantee that the loop will last exactly 30 seconds. The problem is that you depend on the time a participant is taking for their response. Suppose the participants is falling asleep during the first trial, the experiment will never stop, because inside the loop you will wait for an infinite duration until the participants responds. Nevertheless, provided that the participant replies rather quickly, the problem so far was that the timer started in the prepare phase of the experiment. The attached example should be reasonably accurate (I print out the current time to the debug window to show the current duration)

  Eduard

  LetterComparison.osexp

  
  

  
• mhilliard2

  November 11

  @eduard

  Thank you for identifying the error, the task is running exactly as I would like it to be now.

  However, when I attempt to run the task in an external browser, I recieve a notification stating: " Uncaught TypeError: Cannot set properties of undefined (setting 'imports')." Is the language you implemented into the in-line script not compatible with Jatos/external browsers? I am not sure what the setting imports error could be a result of, as this task does not use any outside stimuli.

  Thanks again
• eduard

  November 11

  Indeed, I wrote Python code which is not compatible with Online experimenting. You would need to translate the code to Javascript (and use the javascript inline_script item). Most of the code should be easily copied without any changes, but I am not sure how to take a time sample in javascript. This might help. and maybe, @Fab can you help out once again?

  
• Fab

  November 17 edited November 18

  Hi @mhilliard2, (cc @eduard)

  I had a quick look (am pressed for time) but I think I've cracked it.

  Your code can easily adapted to Javascript for most parts (for example, in Javascript, you just need to use vars.somevariable to define a variable you'd define with var somevariable in Python), but I've had trouble accessing the clock function (clock.time()). I'm not sure whether it is actually accessible from Javascript or not, so I implemented an alternative using Javascript language :

  var currentDateTime = new Date()
  vars.block_start_time = currentDateTime.getTime() / 1000
  

  It's not as direct as in Python but this does get you the clock's current time in seconds. Because it gets it in seconds and not milliseconds, I've also changed the maximum interval to 30 instead of 30000:

  vars.max_dur = 30 //in seconds
  

  The rest is a basic adaptation of the Python code to Javascript. Had a quick go and it seems to be working as supposed to but, as I said, I'm in a rush and did this quickly, so I recommend you doublecheck it.

  I tried it from both from OS in a window and through a browser and it seems to work. In your browser, I recommend checking what's going on in the console to keep track of things, which you can do by opening the console through the browser's menu or using CTRL+SHIFT+i in most browsers in Windows:

  

  
  

  Here's my version:

  LetterComparison Fab2.osexp

  Hope this helps,

  Fabrice.

  PS: please be aware that in order to run in a browser and through JATOS, the compatibility check must not detect any problem. This means that the "log all variables" of the logger must be disabled and that you must indicate manually which variables you want to log. For the task to run, I disabled the logging of all variables. You'll need to set the logger up based on what you want to register.