<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear Karin,<div class=""> It should be pretty easy to change your tier names using the CHSTRING command or just the REPLACE dialog in CLAN. I guess you only need to change one of the two files.</div><div class=""><br class=""></div><div class="">-- Brian<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 17, 2020, at 10:52 AM, Karin Edlund <<a href="mailto:karin.eva.edlund@gmail.com" class="">karin.eva.edlund@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div dir="auto" class="">Hi Brian,</div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Thank you for your quick answer.</div><div dir="auto" class="">I can understand that this is the case. We need to keep the participants blinded to the second coder and this is why we chose to work with separate coding systems for the participants. </div><div dir="auto" class="">We are mostly interested in overall match on actual word and utterance level, thus the tier names seem not to be so interesting to include for that calculation?</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Best Regards,</div><div dir="auto" class="">Karin Edlund</div><div class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">ons 17 juni 2020 kl. 16:39 skrev Brian MacWhinney <<a href="mailto:macw@andrew.cmu.edu" class="">macw@andrew.cmu.edu</a>>:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space" class="">Dear Karin,<div class=""><br class=""><div class=""> I don't think that RELY should try to get around this problem. Instead, I would recommend making sure that your transcribers use the same set of tier names.</div><div class=""><br class=""></div><div class="">--Brian MacWhinney<br class=""><div class=""><br class=""><blockquote type="cite" class=""></blockquote></div></div></div></div><div style="word-wrap:break-word;line-break:after-white-space" class=""><div class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 17, 2020, at 9:25 AM, Karin Edlund <<a href="mailto:karin.eva.edlund@gmail.com" target="_blank" class="">karin.eva.edlund@gmail.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">When accounting the overall percentage of agreement for overall match between two transcripts on the main line (function 3 of RELY), are Tier names included in that? When running the RELY function (3) in CLAN I got many "Tier names do not match" due to the fact that the transcribers use one set each of names of the participants. </div><div class="">If Tier names are included in the accounting of overall agreement of the transcription, is there a way of coming around this (provided we can keep our own sets of names for the participants)?</div><div class=""><br class=""></div><div class="">Best Regards,</div><div class="">Karin Edlund</div></div><div class=""><br class=""></div>
-- <br class="">
You received this message because you are subscribed to the Google Groups "chibolts" group.<br class="">
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:chibolts+unsubscribe@googlegroups.com" target="_blank" class="">chibolts+unsubscribe@googlegroups.com</a>.<br class="">
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/CANkUE2zECn_n3DWDUv20P38HYCfzufK6onPhbdPwf9PuJvhVHg%40mail.gmail.com?utm_medium=email&utm_source=footer" target="_blank" class="">https://groups.google.com/d/msgid/chibolts/CANkUE2zECn_n3DWDUv20P38HYCfzufK6onPhbdPwf9PuJvhVHg%40mail.gmail.com</a>.<br class="">
</div></blockquote></div><br class=""></div></div></div><div class=""><br class="webkit-block-placeholder"></div>
-- <br class="">
You received this message because you are subscribed to the Google Groups "chibolts" group.<br class="">
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:chibolts+unsubscribe@googlegroups.com" target="_blank" class="">chibolts+unsubscribe@googlegroups.com</a>.<br class="">
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/9EE985BB-D778-4BDE-A0CE-C4581D19E5F4%40andrew.cmu.edu?utm_medium=email&utm_source=footer" target="_blank" class="">https://groups.google.com/d/msgid/chibolts/9EE985BB-D778-4BDE-A0CE-C4581D19E5F4%40andrew.cmu.edu</a>.<br class="">
</blockquote></div></div><div class=""><br class="webkit-block-placeholder"></div>
-- <br class="">
You received this message because you are subscribed to the Google Groups "chibolts" group.<br class="">
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:chibolts+unsubscribe@googlegroups.com" class="">chibolts+unsubscribe@googlegroups.com</a>.<br class="">
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/CANkUE2xEGX-uAou19zrpX0K_bS-L_8BFP%2B9hxWFR9KG%2BZqrLFw%40mail.gmail.com?utm_medium=email&utm_source=footer" class="">https://groups.google.com/d/msgid/chibolts/CANkUE2xEGX-uAou19zrpX0K_bS-L_8BFP%2B9hxWFR9KG%2BZqrLFw%40mail.gmail.com</a>.<br class="">
</div></blockquote></div><br class=""></div></body></html>
<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 <a href="mailto:chibolts+unsubscribe@googlegroups.com">chibolts+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/F1DB467F-5630-4C69-AD40-F2924ABD93AB%40andrew.cmu.edu?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/chibolts/F1DB467F-5630-4C69-AD40-F2924ABD93AB%40andrew.cmu.edu</a>.<br />