commas and COMBO

Wed Oct 5 01:33:56 UTC 2022

This was a bug in COMBO that had to do with speaker tier immediately following @ID tier. I have fixed it and update all versions of CLAN on the web.

This command will ignore words separated by commas:

combo +svení^vení @

This command will match words with or without commas in between them:

combo +svení^vení +g4 @

Leonid.

> On Oct 4, 2022, at 12:38, Leonid Spektor <spektor at andrew.cmu.edu> wrote:
> 
> Cynthia,
> 
> 	Please email to me both files you used for testing. The one with commas that is not suppose to produce any output and the one without commas that works correctly. I can't replicate the problem you are having, so need the actual files you are running COMBO on for testing. Please email those files as attachments to me directly at spektor at andrew.cmu.edu <mailto:spektor at andrew.cmu.edu>.
> 
> Also, please let me know what MacOS version do you have on your Mac.
> 
> Leonid.
> 
>> On Oct 4, 2022, at 11:01, Cynthia Audisio <cpaudisio at gmail.com <mailto:cpaudisio at gmail.com>> wrote:
>> 
>> Dear Leonid,
>> 
>> I've updated my version on Mac but I get the same result as before.
>> 
>> ---The command matches one occurrence on the following transcript.
>> 
>> @Begin
>> @Languages:    spa
>> @Participants:    PA1 Participant
>> @ID:    spa|change_corpus_later|PA1|||||Participant|||
>> *PA1:    vení, vení.
>> *PA1:    ahí voy.
>> *PA1:    vení, vení.
>> @End
>> 
>> > combo +svení^vení @
>> vení^vení
>> combo +svení^vení @
>> Tue Oct  4 11:56:54 2022
>> combo (12-Sep-2022) is conducting analyses on:
>>   ALL speaker tiers
>> ****************************************
>> From file </Applications/CLANc/work/combo/Untitled 2.cha>
>> ----------------------------------------
>> *** File "/Applications/CLANc/work/combo/Untitled 2.cha": line 5.
>> *PA1:    (1)vení , (1)vení .
>> 
>>     Strings matched 1 times
>> 
>> 
>> ---Whenever commas are excluded, it matches the actual amount of occurrences:
>> 
>> @Begin
>> @Languages:    spa
>> @Participants:    PA1 Participant
>> @ID:    spa|change_corpus_later|PA1|||||Participant|||
>> *PA1:    vení vení.
>> *PA1:    ahí voy.
>> *PA1:    vení vení.
>> @End
>> 
>> > combo +svení^vení @
>> vení^vení
>> combo +svení^vení @
>> Tue Oct  4 11:59:09 2022
>> combo (12-Sep-2022) is conducting analyses on:
>>   ALL speaker tiers
>> ****************************************
>> From file </Applications/CLANc/work/combo/Untitled 2.cha>
>> ----------------------------------------
>> *** File "/Applications/CLANc/work/combo/Untitled 2.cha": line 5.
>> *PA1:    (1)vení (1)vení .
>> ----------------------------------------
>> *** File "/Applications/CLANc/work/combo/Untitled 2.cha": line 7.
>> *PA1:    (1)vení (1)vení .
>> 
>>     Strings matched 2 times
>> El lunes, 3 de octubre de 2022 a las 23:49:28 UTC-3, Leonid Spektor escribió:
>> Cynthia,
>> 
>> 	You might be using an older version of CLAN. Your command "combo +svení^vení", in latest version of CLAN, when run on the following data:
>> 
>> *PA1:	vení, vení.
>> *PA2:	ahí voy.
>> *PA1:	vení, vení.
>> *PA2:	vení vení.
>> 
>> Will produce the following output:
>> 
>> > combo +svení^vení combo.cha
>> vení^vení
>> combo +svení^vení combo.cha
>> Mon Oct  3 22:42:14 2022
>> combo (12-Sep-2022) is conducting analyses on:
>>   ALL speaker tiers
>> ****************************************
>> From file <combo.cha>
>> ----------------------------------------
>> *** File "combo.cha": line 4.
>> *PA2:	(1)vení (1)vení .
>> 
>>     Strings matched 1 times
>> 
>> The words separated by commas will not match.
>> 
>> Leonid.
>> 
>> 
>>> On Oct 3, 2022, at 21:50, Cynthia Audisio <cpau... at gmail.com <applewebdata://63FE510C-C296-4319-8E63-D8842BE503CC>> wrote:
>>> 
>> 
>>> Dear chibolts,
>>> 
>>> Why is it that whenever I use COMBO with words separated by commas, the command only matches the first co-occurence?
>>> 
>>> For instance, on the following fragment
>>> 
>>> *PA1: vení, vení.
>>> *PA2: ahí voy.
>>> *PA1: vení, vení.
>>> 
>>> combo +svení^vení returns:
>>> 
>>> *PA1:    (1)vení, (1)vení .
>>>     Strings matched 1 times
>>> 
>>> without the comma, it works just fine.
>>> 
>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups "chibolts" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an email to chibolts+u... at googlegroups.com <applewebdata://63FE510C-C296-4319-8E63-D8842BE503CC>.
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/d2bf52c5-c0a1-4d57-885f-4f6916025959n%40googlegroups.com <https://groups.google.com/d/msgid/chibolts/d2bf52c5-c0a1-4d57-885f-4f6916025959n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups "chibolts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to chibolts+unsubscribe at googlegroups.com <mailto:chibolts+unsubscribe at googlegroups.com>.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/9c541f91-a4dd-4509-8b85-e7af01b12984n%40googlegroups.com <https://groups.google.com/d/msgid/chibolts/9c541f91-a4dd-4509-8b85-e7af01b12984n%40googlegroups.com?utm_medium=email&utm_source=footer>.
> 

-- 
You received this message because you are subscribed to the Google Groups "chibolts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chibolts+unsubscribe at googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/286464D7-7FF1-4E38-AAB5-739D2B5CB45C%40andrew.cmu.edu.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.linguistlist.org/pipermail/chibolts/attachments/20221004/68d1f62f/attachment.htm>