List counterbalancing by sujbect

Rachel rachel.ostrand at gmail.com
Wed Mar 14 02:10:23 UTC 2012


Hi everyone,

Thanks so much for your suggestions. I went with David Vinson's idea
of creating a separate procedure for each GroupList, and it worked
perfectly. Admittedly, this solution is somewhat undesirable for two
reasons: first, if I had 100 different conditions, instead of just 8,
not only would I have to make up 100 different counterbalancing lists
but also 100 different procedures to nest these lists in. Second, as
the other David pointed out, it's rather inelegant of a solution to
have redundancy in the code. However, it doesn't require building a
new TrialProc for each list, which is the major procedure that you
want to keep the same across all versions, so if something gets
changed, it gets changed in all versions. Given then that neither of
these hurdles was too major, it was a great suggestion, worked for my
purposes, and thanks again for all of your responses.

-Rachel

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