Hi Leonid,<div><br></div><div>Thanks for your reply. I just downloaded the latest version of clan (<span style="color: rgb(0, 0, 0); font-size: medium; text-align: -webkit-center;">V 08-Feb-2013 11:00</span>), as well as the mor grammar (from <a href="http://childes.psy.cmu.edu/morgrams/">http://childes.psy.cmu.edu/morgrams/</a>), and recompiled. Unfortunately I got the same result as before:</div><div><br></div><div><div>*PAR:<span style="white-space: pre;"> </span>(a)bout (un)til (th)em .</div><div>%mor:<span style="white-space: pre;"> </span>?|abutt conj|until^prep|until ?|theem .</div></div><div><br></div><div>I am using clan on Ubuntu 10.04. I compile with:</div><div>CC = g++</div><div>and</div><div>CFLAGS = -DUNX -Wno-deprecated -Wno-deprecated-declarations</div><div><br></div><div>The first line of the make file mentions using the -m32 option, but that gives an error, so I don't do that.</div><div><br></div><div>Could you please let me know if you're able to replicate the strange behavior on unix clan, or if I might be doing something wrong when compiling or anything else?</div><div><br></div><div>Thanks a lot,</div><div><br></div><div>best,</div><div>Stephen</div><div><br></div><br>On Wednesday, February 6, 2013 3:20:03 PM UTC-7, Spektor, Leonid: CMU wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div style="word-wrap:break-word">Stephen,<div><br></div><div><span style="white-space:pre"> </span>I just tested the latest version of CLAN on both Mac and Windows PC and after running MOR on your sample tier below I get the following correct result:</div><div><br></div><div><div>*PAR:<span style="white-space:pre"> </span>(a)bout (un)til (th)em .</div><div>%mor:<span style="white-space:pre"> </span>prep|about^adv|about prep|until^conj|until pro:obj|them .</div><div><br></div><div>Please, make sure that you have the latest version of CLAN and MOR grammar. If you do have the latest versions, then please try to quit CLAN and restart it. Maybe CLAN got into bad state. If after using the latest CLAN/grammar and restarting CLAN, you still get this problem, then please email to me the data file and command line that produced bad result.</div><div><br></div><div>
<div style="word-wrap:break-word"><div style="word-wrap:break-word"><span style="border-collapse:separate;color:rgb(0,0,0);font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;color:rgb(0,0,0);font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word"><span style="border-collapse:separate;color:rgb(0,0,0);font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word"><div><br>Leonid.</div><div><br></div></div></span></div></span></span></div></div><br>
</div>
<br><div><div>On Feb 6, 2013, at 16:45 , Stephen Wilson wrote:</div><br><blockquote type="cite"><div><div>MOR does not seem to handle "noncompletion" of words as expected, e.g. (un)til, (be)cause.</div><div><br></div><div>According to the CHAT manual: "CLAN will treat items that are coded in this way as full words. For programs such as FREQ, the parentheses will essentially be ignored and (be)cause will be treated as if it were because."</div></div><div><br></div><div>But does this not apply to MOR? I get this as my parse:</div><div><br></div><div>*PAR:<span style="white-space:pre"> </span>(a)bout (un)til (th)em .</div><div>%mor:<span style="white-space:pre"> </span>?|abutt conj|until^prep|until ?|theem .</div><div><br></div><div>thanks,</div><div>Stephen</div><div><br></div>
-- <br>
You received this message because you are subscribed to the Google Groups "chibolts" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="MbjVZOqHH6QJ">chibolts+u...@<wbr>googlegroups.com</a>.<br>
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="MbjVZOqHH6QJ">chib...@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msg/chibolts/-/_z9nvzG6BMwJ" target="_blank">https://groups.google.com/d/<wbr>msg/chibolts/-/_z9nvzG6BMwJ</a>.<br>
For more options, visit <a href="https://groups.google.com/groups/opt_out" target="_blank">https://groups.google.com/<wbr>groups/opt_out</a>.<br>
<br>
<br>
</blockquote></div><br></div></div></blockquote>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "chibolts" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to chibolts+unsubscribe@googlegroups.com.<br />
To post to this group, send email to chibolts@googlegroups.com.<br />
To view this discussion on the web visit <a href="https://groups.google.com/d/msg/chibolts/-/dQhsYnhK6hcJ">https://groups.google.com/d/msg/chibolts/-/dQhsYnhK6hcJ</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
<br />
<br />