<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> Janet,<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>RELY program has some peculiarities in the way it gives feedback. The "Done with file ..." messages give more information than is necessary and this causes the confusion. RELY creates only one output file. The message "Done ..." means that the file has been read, unlike in other CLAN programs where it means that the file by that name has been created. I have refined the messages that RELY displayed and in the new version it will be much more clear. I will install the new version by Monday.</div><div><br></div><div>The message 'CURRENT OUTPUT FILE "sample2.rely.cex" IS INCOMPLETE' is erroneously displays wrong file name. In your example it should say 'CURRENT OUTPUT FILE "sample.rely.cex" IS INCOMPLETE' instead. I have fixed this error as well. This message indicates that whatever file CLAN program has created is corrupted and therefor should be ignored. RELY has one limitation that would produce this kind of error message. If the tier names at a particular location in both input files do not match, then RELY displays this message and quits. RELY assumes that at least all speaker tier names will be the same and in the same order within both input files. The text on those tiers can differ and they can have different number of dependent tiers, but if the speakers themselves do not match, then there is a really big problem there and it needs to be fixed before RELY can continue. </div><div><br></div><div>If you still have problems or questions about RELY please write to me directly and please attach all the input files that you use in your RELY program examples.</div><div><div>
<span class="Apple-style-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; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-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; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-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; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br class="Apple-interchange-newline">Leonid.</div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Jan 22, 2011, at 12:04, Janet Bang wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Dr. MacWhinney,<br><br>Thank you for your suggestion. For reliability, we were specifically wanting to look at the level of the words per utterance. Actually, the RELY program was able to give us an output of comparisons on the main line, which is a big help in having much of the data ready, to then do the statistical calculations by hand. Therefore, my question now has to do with automating this process, rather than automating computation. <br>
<br>What we mean about the RELY program giving us an output of comparisons, is that the program was able to recognize the following situation:<br>- if the file sample.cha had an utterance "mommy goes home" on line 16<br>
- and sample2.cha had the utterance "mommy goes back home" on line 18<br>- the RELY program was able to recognize that these two utterances contained the same information and compared them appropriately in the output as being different. <br>
<br>However, after testing out the RELY program on the main lines (I used the command: rely +t*MOT -t*CHI -t*%), I realized that the program was not be able to produce an output comparing these lines past line 60 on the original file. <br>
<br>I've tested out the .cha files at various lengths, and this seems to be where the output stops, although I've set the limit of lines in the output as "no limit".<br><br>Furthermore, in the output window when I am running the RELY program on sample.cha and sample2.cha, this information shown:<br>
<br>CURRENT OUTPUT FILE "sample2.rely.cex" IS INCOMPLETE<br><br>This is a bit confusing to us because even with the shorter files where this program does not produce this note, it will say:<br><br>Done with file <sample.rely.cex> with errors reported in <sample.rely.cex><br>
Done with file <sample2.rely.cex><br><br>But, there is no file called <sample2.rely.cex> on the computer, even when it seems the program was able to run to completion.<br><br>Is there something that we are not considering in the command when we run this program? Or, is it that the RELY program was just not meant to compare the main lines, and this is why this may be happening?<br>
<br><br>Thank you for your help,<br><br>Janet Bang<br><br><br><br><br><br><br><br><br><br><br><br><br><div class="gmail_quote">On Fri, Jan 7, 2011 at 10:39 AM, Brian MacWhinney <span dir="ltr"><<a href="mailto:macw@cmu.edu">macw@cmu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Dear Janet,<br>
Yes, we discussed this earlier. If I remember correctly, we concluded that the shape of the main line is so complex that there was no well-defined way of computing reliability. Would it be on the level of the word, or the phoneme, or the code or the overall sentence, or exactly what? Perhaps you could create a small sample file in which you demonstrate how you think reliability should be computed and we could then take a look at that to see whether the procedure could be automated.<br>
<font color="#888888"><br>
-- Brian MacWhinney<br>
</font><div><div></div><div class="h5"><br>
On Jan 7, 2011, at 1:01 AM, Janet wrote:<br>
<br>
> Dear users of CHAT and CLAN,<br>
><br>
> I am a graduate student at McGill University using CHAT and CLAN to<br>
> transcribe and analyze parent-child interactions. I would like to<br>
> establish reliability of these transcriptions with other transcribers,<br>
> and was wondering if anyone has been able to use the RELY program to<br>
> do so? I noticed there was a posting to this question a couple of<br>
> years ago, and there wasn't a way for RELY to do so on the main<br>
> lines. Any help would be much appreciated.<br>
><br>
> Thank you,<br>
><br>
> Janet Bang<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><div><br class="webkit-block-placeholder"></div>
-- <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+unsubscribe@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">http://groups.google.com/group/chibolts?hl=en</a>.<br>
</blockquote></div><br></div></body></html>
<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 />