<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">One more thing about +/-t options. The name(s)/code(s) are not case sensitive.<div><br><div>For more short cut "+tpar" is the same as "+t*PAR:"<div>
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Arial; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class="Apple-interchange-newline"><br></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Arial; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;">Leonid.</div>
</div>
<div><br><blockquote type="cite"><div>On Jul 7, 2025, at 16:40, Leonid Spektor <spektor@andrew.cmu.edu> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=us-ascii"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Mingyu,<div><br></div><div>The +/-t options convention is following:</div><div><br></div><div>+/-t%mor<span class="Apple-tab-span" style="white-space:pre"> </span>- include or exclude all %mor utterances.</div><div><br></div><div>The * (star) right after "+/-t" is a literal star. All speaker tiers start with a star character, i.e. *PAR: text.</div><div><br id="lineBreakAtBeginningOfMessage"><div>
<div style="caret-color: rgb(0, 0, 0); font-family: Arial; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div>+/-tPAR - is a short cut, if the star is missing after the "t", then it is assumed you want speaker tiers.</div><div><br></div><div>+/-t*PAR - no short cuts, just explicit way to specify specific speaker tier.</div><div><br></div><div><div>+/-tPAR* - star at the end means wild character that matches anything there is.</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Some corpuses have speakers *PAR-one: and *PAR-two: and so on.</div><div><br></div><div>+/-t*PAR* - the same a above, just more explicit.</div></div><div><br></div><div>Hope this helps,</div><div><br></div></div><div style="caret-color: rgb(0, 0, 0); font-family: Arial; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">Leonid.</div>
</div>
<div><br><blockquote type="cite"><div>On Jul 7, 2025, at 15:58, 'Mingyu Yuan' via chibolts <chibolts@googlegroups.com> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);">Hi everyone, <br><br>I have a question about extracting participants' utterances using CLAN commands and was wondering if I'm thinking along the right lines. I'd appreciate it if you could take a look. Thanks!<br><br>I'm working with DementiaBank, specifically the ADReSS dataset, a subset of the Pitt corpus. I used the following command to extract the 'flow' tier of participants' utterances: `flo +cr +tPAR*`. Here, I have the asterisk * placed after the PAR identifier. But I noticed that in the CLAN manual, the asterisk typically precedes it, as in `t*PAR`. <br><br>I got the following output after running `t*PAR`</div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><br></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);">flo (13-Apr-2023) is conducting analyses on:<br> ONLY speaker main tiers matching: *PAR;<br></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><br></div><div style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);">And here's the output after running `tPAR*`</div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><br></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);">flo (13-Apr-2023) is conducting analyses on:<br> ONLY speaker main tiers matching: *PAR*;<br></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><br></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);">It looks like the asterisk is used to search for tier ID patterns. Since all my files contain only INV and PAR tiers, I assume tier matching would only affect the selection of the PAR tier. I also used a Python function to verify that the utterances extracted by these two commands were identical (attached below, in case it's helpful). </div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><br></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);">Both commands appear to work, but I don't fully understand why. Please let me know your thoughts. Thank you very much!</div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><br></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);">Best,</div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);">Mingyu</div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><br></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><div>def check_clan_command(id, file_old, file_new):</div><div> # Read the .cex file created by the old command (i.e. with tPAR*)<br> with open(PATH_TO_OLD_FILE, 'r') as file_old_cmd:<br> file_o = file_old_cmd.read().splitlines()</div><div> # Read the .cex file created by the new command (i.e. with t*PAR)<br> with open(PATH_TO_NEW_FILE, 'r') as file_new_cmd:<br> file_n = file_new_cmd.read().splitlines()</div><div> print(id, file_o == file_n)</div></div><div dir="ltr" style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34);"><div><div><br></div></div></div><div><br class="webkit-block-placeholder"></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="mailto:chibolts+unsubscribe@googlegroups.com">chibolts+unsubscribe@googlegroups.com</a>.<br>
To view this discussion visit <a href="https://groups.google.com/d/msgid/chibolts/d2459e0d-41c6-4707-9e00-e75f5e755c47n%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/chibolts/d2459e0d-41c6-4707-9e00-e75f5e755c47n%40googlegroups.com</a>.<br>
</div></blockquote></div><br></div></div></div></blockquote></div><br></div></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 visit <a href="https://groups.google.com/d/msgid/chibolts/A31960C6-965F-4F60-BAEB-F06E7B339E41%40andrew.cmu.edu?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/chibolts/A31960C6-965F-4F60-BAEB-F06E7B339E41%40andrew.cmu.edu</a>.<br />