Combing two different tasks into one program

liwenna liwenna at gmail.com
Fri Sep 3 10:32:01 UTC 2010


I can imagine a whole bunch of different errors that could occur when
combining tasks in the way you did now...

make sure that all inlines that concern a procedure are nested on the
same procedure. I couldnt'tell you the exact mechanics top of my head
but I remember errors occurring from variables being declared (the dim
lines) on a different level of the total task then where they are
used.

Also: variables can be declared only once... if both your tasks that
have been merged now share a variable (or actually have two variables
that have the same name but shouldn't be shared between the tasks) and
both have inlines that declare this variables, this gives an error
too.

Just two possible errors that come to mind... carefully 'walk' trough
your experiment to check all your inlines on discrepanties.

Additionally you could post an error here to see if we can 'make
anything of it'

best,

liw

On Sep 3, 2:37 am, dkmcf <mcfar... at msu.edu> wrote:
> You need to sign up for a course in Introduction to Computer
> Programming.
>
> -- David McFarlane, Professional Faultfinder
>
> On Sep 2, 6:41 pm, cogneuroisfun <neuropsyc... at gmail.com> wrote:
>
> > Thank you for the reply. I did follow your advice and I understand how
> > the nested list works. (i forgot i could do that for tasks) however, i
> > keep on getting error messages about my inline script for one of my
> > tasks. i keep on getting error messages about my script saying it
> > cannot find certain things. however, everything for the task is
> > there.
>
> > does in line script often have problems when copying a procedure into
> > another e-prime program?
>
> > i cannot figure out how to stop getting error messages because it
> > appears as everything should be there and working
> > On Aug 9, 4:54 am, liwenna <liwe... at gmail.com> wrote:
>
> > > hmmz how about....
>
> > > make a 'masterlist' with two levels. Into level 1 nest the 'main list'
> > > for task A, into level 2 nest the main list for task B, set both main
> > > lists to exit after 1 trial. Tell the master list to repeat (in fixed
> > > order) as many times as your total number of trials.
>
> > > I think something like that should do the trick :)
>
> > > best,
>
> > > liw
>
> > > On Aug 8, 5:09 pm, cogneuroisfun <neuropsyc... at gmail.com> wrote:
>
> > > > Okay, so for my experiment, I have condition 1 (task A trials), and
> > > > condition 2 with task A alternating with task B. So, it would be like
> > > > one trial of A, one trial of B, one trial of A, one trial of B ect.
> > > > Both task A and B work great by themselves but I'm unsure how to make
> > > > them alternate without butchering either task. Is there any option
> > > > where I could only have the tasks alternate on a trial by trial basis?
> > > > Right now I just can have task A do 50 trials and then task B do 50.
> > > > I've been trying to play around with having new procedure making the
> > > > tasks alternate but I don't know how to only have each task do one
> > > > trial at a time.
>
> > > > Hopefully that made some sense, any help or guidance is greatly
> > > > appreciated!
>
> > > > Thanks!

-- 
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.



More information about the Eprime mailing list