<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial">Hello
ChiBolts</span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial"> </span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial">We have
run into some interesting issues in my lab today, so this discussion is
particularly timely.<span style="mso-spacerun:yes"> </span>We have transcripts
from bilingual children (SPA and ENG) that we need to run multiple analyses on,
including MLT and MOR and POST.<span style="mso-spacerun:yes"> </span>Of
course, even though transcripts are supposed to be ENG or SPA, there is a lot
of code switching going on throughout.<span style="mso-spacerun:yes">
</span>Our issues are outlined below. </span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial"> </span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial">First,
compound words (french_fry) do not check.<span style="mso-spacerun:yes">
</span>They end up in the output file.<span style="mso-spacerun:yes">
</span>Does this mean that they would not be included in subsequent MOR
analyses?<span style="mso-spacerun:yes"> </span>If we want them to be part of
the MOR analyses, how do we get it to check?<span style="mso-spacerun:yes">
</span>We checked the depfile, and *_* was there under the %syn
line. We are hesitant to change the depfile unless we need to; can
someone tell us how to get compound words into the MOR analyses?</span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial"> </span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial">Second,
non-words such as ‘mmhm’ also do not pass check.<span style="mso-spacerun:yes"> </span>We attempted to run MOR even with these in
the main tier, and the %MOR tiers were not created. Any idea why not?</span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial"> </span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial">Third,
our collaborator needs to run MLT and TTR in both English, Spanish, and ‘mixed’
(utterances that include code switches) utterances.<span style="mso-spacerun:yes"> </span>She has been using pre-codes to identify the
language used in the utterance, and post-codes to identify utterances that she
wants omitted from the MLT analyses.<span style="mso-spacerun:yes">
</span>However, we cannot get transcripts with pre-codes to run in MOR.<span style="mso-spacerun:yes"> </span>Is there a way to calculate MLT that does not
involve the use of precodes?</span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial"> </span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial">Fourth,
more generally, does CLAN treat pre-codes and post-codes similarly?<span style="mso-spacerun:yes"> </span>Or are they unique in how they influence subsequent
analyses?<span style="mso-spacerun:yes"> </span></span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial"> </span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial">Finally,
we have been able, with Leonid and Brian’s wonderful assistance, to get MOR to
run in both SPA and ENG when precodes are deleted from the transcripts.<span style="mso-spacerun:yes"> </span>I have a set of directions for this, and can
share if folks want them.<span style="mso-spacerun:yes"> </span></span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial"> </span></p>
<p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial"> Shelley Brundage, </span></p><p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none;
text-autospace:none"><span style="font-size:13.0pt;font-family:Arial">George Washington University</span></p>
<br><div class="gmail_quote">On Thu, Jun 23, 2011 at 11:46 AM, Leonid Spektor <span dir="ltr"><<a href="mailto:spektor@andrew.cmu.edu">spektor@andrew.cmu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Rasmus,<br>
<br>
<br>
1. The form "bird+house-s" is incorrect. If the manual says otherwise, then it needs to be changed. The correct form is "bird+houses".<br>
<br>
2. We don't support this feature at this time. We are in a process of implementing a generic "@x:" tag which will allow users to specify anything they want to. Your example below, then will look like "Toronto@x:geo". This should be implemented in a day or so.<br>
<br>
3. We discourage people from editing the "depfile.cut". Adding anything to that file without additional changes to other supporting files and/or programs will cause problems with other programs like mor and post. We also no longer support the "depadd.cut" file. Check just simply ignores it.<br>
<br>
We no longer distribute the "depadd.cut" file. You must have a very old installation of CLAN and new updates do not delete any old files present there.<br>
<font color="#888888"><br>
Leonid.<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
On Jun 23, 2011, at 09:20, RSteinkrauss wrote:<br>
<br>
> Hi,<br>
><br>
> I have some questions regarding checking files in CLAN and would be<br>
> very happy if someone could help me. I am using the Win version from<br>
> 30-Apr-2011.<br>
><br>
> 1. If understood the manual correctly, English compounds should be<br>
> transcribed with a + sign. Also, plurals in compounds should be marked<br>
> with a dash-s. However, when i run CHECK on my transcript, a form such<br>
> as bird+house-s gives me an "undeclared suffix" error. Same with bird<br>
> +house-s@s if it is a codeswitch in an otherwise German text.<br>
><br>
> 2. We would like to use some @-tags in our transcripts that are not<br>
> specified in the manual (such as @geo for place names, e.g.<br>
> Toronto@geo). I understand that this is not longer possible using a<br>
> depadd-file, so I wondered if the way to go is to change the<br>
> depfile.cut-file.<br>
><br>
> 3. Assuming that this was indeed what should be done, I changed the<br>
> depfile.cut so that it would include the tags we need. After that,<br>
> CHECK worked fine (with the exception of the errors described in<br>
> question 1). However, if I now change the depadd.cut file again, CLAN<br>
> will not react to the changes. E.g., if I remove a previously allowed<br>
> @-tag such as @geo from my depadd.cut, CHECK will not complain when it<br>
> encounters that tag in a transcipt. Strangely, that behaviour persists<br>
> even after de- and reinstalling CLAN. I have set the lib path<br>
> correctly, to a folder containing my changed depadd.cut. Also after<br>
> changing the lib path back to the original depadd.cut that came /<br>
> installed with CLAN, CHECK still allows my own @-tags.<br>
><br>
> Does anyone have an idea how to go about this? Any feedback would be<br>
> greatly appreciated!<br>
><br>
> Thank you in advance,<br>
> Rasmus<br>
><br>
> --<br>
> You received this message because you are subscribed to the Google Groups "chibolts" group.<br>
> To post to this group, send email to <a href="mailto:chibolts@googlegroups.com">chibolts@googlegroups.com</a>.<br>
> To unsubscribe from this group, send email to <a href="mailto:chibolts%2Bunsubscribe@googlegroups.com">chibolts+unsubscribe@googlegroups.com</a>.<br>
> For more options, visit this group at <a href="http://groups.google.com/group/chibolts?hl=en" target="_blank">http://groups.google.com/group/chibolts?hl=en</a>.<br>
><br>
><br>
<br>
--<br>
You received this message because you are subscribed to the Google Groups "chibolts" group.<br>
To post to this group, send email to <a href="mailto:chibolts@googlegroups.com">chibolts@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href="mailto:chibolts%2Bunsubscribe@googlegroups.com">chibolts+unsubscribe@googlegroups.com</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/chibolts?hl=en" target="_blank">http://groups.google.com/group/chibolts?hl=en</a>.<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Shelley B. Brundage, Ph.D., CCC-S<br>Associate Professor and Graduate Program Director<br>Board Recognized Specialist and Mentor-Fluency Disorders<br>Speech and Hearing Science department<br>
George Washington University<br>2115 G St NW Suite 201<br>Washington, D.C. 20052<br>(202) 994-5008 office<br>(202 994-2205 lab<br>(202) 994-2589 fax<br>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "chibolts" group.<br />
To post to this group, send email to chibolts@googlegroups.com.<br />
To unsubscribe from this group, send email to chibolts+unsubscribe@googlegroups.com.<br />
For more options, visit this group at http://groups.google.com/group/chibolts?hl=en.<br />