<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi all,<o:p></o:p></p><p class=MsoNormal>Today, I was particularly pleased about how far one can take the whole nested list approach to attributes. The following is rather difficult to manage in other ways (though that’s always uncertain given the many strange possible ways to reach the same goal), and is something that is quite often asked in the mailinglist. <o:p></o:p></p><p class=MsoNormal>The goal is to take 2 items from a list of N items, assign target status to one of them and order them randomly.<o:p></o:p></p><p class=MsoNormal>We take:<o:p></o:p></p><p class=MsoNormal>1 ItemList, nested inside a high level (say, “sessionlist”). It contains 6 items (“topics”): cat, wife, wine, society, painting and atom (randomized), in the attribute “Tops”.<o:p></o:p></p><p class=MsoNormal>In the TrialList, I have as a Nested list: “TargetTopic”, with a single attribute “TTopic”, 2 levels.<o:p></o:p></p><p class=MsoNormal>In the TrialList, I have 5 attributes: “Topic1”, “Topic2”, Topic”, “T1N”, “T2N”<o:p></o:p></p><p class=MsoNormal>T1N and T2N have the following levels<o:p></o:p></p><p class=MsoNormal style='margin-left:18.0pt'>0,1<o:p></o:p></p><p class=MsoNormal style='margin-left:18.0pt'>2,3<o:p></o:p></p><p class=MsoNormal style='margin-left:18.0pt'>4,5<o:p></o:p></p><p class=MsoNormal>And denote the topic to take (if the ItemList were unsorted, 0 would be cat, 5 atom)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Now, Topic1 has, at each of the 3 levels, but each says: [Tops:[T1N]] while Topic2 has 3 level and each says: [Tops:[T2N]]<o:p></o:p></p><p class=MsoNormal>They could, of course, just have stated [Tops:1] [Tops:2] and so on, but this makes recoding much easier (for instance, if more topics are added). <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Finally, the Topic attribute denotes a target topic with the single [Topic[TTopic]]<o:p></o:p></p><p class=MsoNormal>Which thus uses the nested list (with TTopic being either 1 or 2) to indicate the “target”, such that this item is either [Topic1] or [Topic2].<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thus, with this arrangement, it is particularly easy to then show the two paired words in the experiment, with textdisplay1 and 2, sequentially calling [Topic1][Topic2].<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As one can see, and as has been pointed out before by David McFarlane on this list, one can be extremely creative with the whole square brackets thing. I was surprised, however, to learn just how very adaptive this can make the randomization, as in the following samples of a single (literal) cell in a list:<o:p></o:p></p><p class=MsoNormal>[Topic1][Topic2] concatenates by drawing from Topic1 and Topic2<o:p></o:p></p><p class=MsoNormal>[Tops:[T1N]] draws row obtained from nested attribute T1N from Tops<o:p></o:p></p><p class=MsoNormal>[Topic[TTopic]] concatenates Topic with attribute TTopic, and thus draws either from Topic1 or Topic2.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I suppose one has to be a bit of an e-prime geek to get a thrill from doing this, but I hope this account may inspire some people anyway.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best,<o:p></o:p></p><p class=MsoNormal>Michiel<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "E-Prime" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:e-prime+unsubscribe@googlegroups.com">e-prime+unsubscribe@googlegroups.com</a>.<br />
To post to this group, send email to <a href="mailto:e-prime@googlegroups.com">e-prime@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/e-prime/01cd01cf53fe%242b8ea140%2482abe3c0%24%40eu?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/e-prime/01cd01cf53fe%242b8ea140%2482abe3c0%24%40eu</a>.<br />
For more options, visit <a href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br />