|
|
|
Junior Member
      
Group: Forum Members
Last Login: 2/29/2008 11:43:41 AM
Posts: 18,
Visits: 68
|
|
| Hello, I am creating an experiment that has 600 trials, and I would like to allow the participant to have a break every 200 trials (so a break after 200, then another break after 400 trials). How can I do this? Initially I created 3 separate trial lists, each with 200 trials. But this is messy and makes the data output harder to work with. Is there some clever script I can use that can tell E-prime to allow the user to go to a break screen after 200 trials? And then after they press the spacebar, the trials will continue from where they left off? Cheers!
|
|
|
|
|
Forum MVP
      
Group: Administrators
Last Login: Today @ 5:00:06 PM
Posts: 569,
Visits: 1,238
|
|
|
|
|
|
Junior Member
      
Group: Forum Members
Last Login: 10/17/2007 12:04:54 PM
Posts: 10,
Visits: 15
|
|
I've attached an E-Prime program that implements the procedure that I use for having periodic breaks. The program presents a letter on each trial. The correct response is simply to press the key for that letter on the keyboard. A break occurs after every 10 trials.
To implement the breaks, I followed this procedure:
- Define an integer variable called counter (click on View, then Script, to see it)
- Initialize it to 0 (see the first occurrence of the CounterReset inline script)
- Add 1 to the counter. If the counter equals 10, then goto a flag called StartBreak, else goto a flag called EndBreak (see the CounterUpdate inline script). The "else goto" part makes the program skip the break if the number of elapsed trials is not 10.
- Insert flags called StartBreak and EndBreak at the end of the trial procedure. Between the flags, insert the desired screens to appear during the break.
- Before the EndBreak flag, insert a copy of the CounterReset inline script to reset the counter to 0 for the next run of 10 trials.
Note that with this procedure, you can also easily specify breaks after different numbers of trials by adding extra goto commands and having an additional cumulative counter (i.e., one that is never reset).
|
|
|
|