Hi Christine,
The ~5 s ISI comes from total ISI = 150 = 675 - 21 - 32*15.75
where 675 = total per run, 32*15.75 = 32 event times, and
21 = pre/post rest time, all in seconds per run.
So 150 s ISI time divided by 31 (32-1 ISI periods) is 4.839 s,
the average ISI (assuming none at the start or end of a run).
To put it another way, that 150 s was for your pseudo-rest
events: 50*3 s events.
There is no current way to force one condition not to occur
first or last in a run, not when creating an output timing
file (i.e. it might be possible to make ISIs a multiple of
3s, but that has its own difficulty since the other task
events are not - still, it would be doable).
Maybe it would not be too difficult to add this (though it
would have to apply to both the basic and advanced cases,
and maybe I would not try to do it with the max consec or
ordered stim cases). We'll see...
- rick
