Collecting data continuously for 2 objects

[David McFarlane]

Sarah,

Glad you got it to work.  Not that you need this now, but here is 
another trick that I have used in a situation somewhat like 
yours.  Suppose we have a StimSlide followed by a MaskText to erase 
the stimulus, where StimSlide lasts for 500 ms or until a response 
(whichever comes first), and we want the whole trial to last 1500 ms 
regardless of response time (i.e., MaskText should last the remainder 
of the 1500 ms after the termination of StimSlide).  We still need a 
bit of inline code between StimSlide and MaskText, but instead of 
doing the calculation directly (which can get tricky to take account 
of onset delays, etc.), we set both objects to Cumulative timing 
mode, set the Duration of MaskText to a constant 1500 ms, and use the 
following single line of code:

SetNextTargetOnsetTime StimSlide.TargetOnsetTime

E-Prime then automatically takes care of the rest.  Just think about 
it (and maybe look at SetNextTargetOnsetTime in the online E-Basic 
Help).  Even though MaskText starts well into the 1500 ms, that 
doesn't matter, because E-Prime still takes MaskText.TargetOnsetTime 
to be the same as StimSlide.TargetOnsetTime, and as a result 
MaskText.TargetOffsetTime becomes StimSlide.TargetOnsetTime + 1500, 
which is all that we want.  Whew!

Now, I am still a bit puzzled about exactly what your Wait1 does, 
since unless you have ClearAfter = Yes on your ImageDisplay then the 
ImageDisplay would remain during the Wait1.  Usually when we want to 
erase a display we follow it with a blank TextDisplay instead of 
using ClearAfter with a Wait object, but I suppose that is a matter 
of personal programming style.

Regards,
-- David McFarlane, Professional Faultfinder


>Thanks David,
>
>It was a little more complicated than the appendix explanation.
>Instead of having the ImageDisplay1 = 500ms and the Wait1 = 1000ms, I
>changed the ImageDisplay to terminate but made it 1500ms, and kept the
>duration to 500ms, and then took out response collection for Wait1. I
>also had to adjust my inline to have the total trial time always
>equaling 1500ms despite the response time.
>
>But the appendix helped!
>Thank you,
>Sarah
>
>On Feb 24, 11:07 pm, David McFarlane <mcfar... at msu.edu> wrote:
> > Sarah,
> >
> > Please work through the Extended Input tutorial in Appendix C of the
> > User's Guide that came with E-Prime and see if that helps.
> >
> > Also, think through the difference between End Action = Terminate vs.
> > (none).
> >
> > -- David McFarlane, Professional Faultfinder
> >
> > > Hello all,
> >
> > > I have a TrialProc with five objects, two of them being ImageDisplay1
> > > and Wait1, in that order.
> >
> > > It is a go/nogo task, where ImageDisplay1 is the "Go" target, but it
> > > is only shown for 500ms regardless of the subject's response time,
> > > then the Wait1 in there which lasts for 1000ms - ImageDisplay1 RT.
> > > This keeps the ImageDisplay1 duration at a constant 500ms, but if the
> > > subject takes longer than 500ms to respond, the Wait1 still collects
> > > the response. When I analyze the data it is difficult to get an RT for
> > > each trial because I have to do some math in order to find the one RT
> > > from both objects.
> >
> > > I am wondering if there is a way to continuously collect the data for
> > > ImageDisplay1 and Wait1, so that my data output will give one RT
> > > instead of two for both objects.
> >
> > > Is there any way for this to be done?
> >
> > > Thank you,
> > > Sarah

-- 
You received this message because you are subscribed to the Google Groups "E-Prime" group.
To post to this group, send email to e-prime at googlegroups.com.
To unsubscribe from this group, send email to e-prime+unsubscribe at googlegroups.com.
For more options, visit this group at http://groups.google.com/group/e-prime?hl=en.