Preventing the matching of Infinitives

[Liam Considine]

Hello Chibolts,

Is there a way to indicate in a +t%mor Combo command, a certain
constituent that I do not want to occur in a particular location?

For example, what could i do so that the verb in this command is NOT
preceded by an inf|to? I don't really want to indicate EVERYTHING that
is alright there... just the few things i don't want...

combo +t*MOT +t%mor +s"v|*^prep|*^((n|*+pro|*+det|*)+((det|*+qn|*)^(n|*
+pro|*+det|*))+((det|*+qn|*)^adj|*^(n|*+pro|*+det|*))) +k +r2 +u *.cha

Thanks for the thoughts,
Liam

[Leonid Spektor]

Liam,

NOT marker is indicated by '!' character. In your example you would specify:

+s"!inf|to^v|*^prep|*^((n|*+pro|*+det|*)+((det|*+qn|*)^(n|*+pro|*+det|*))+((det|*+qn|*)^adj|*^(n|*+pro|*+det|*)))"

I would like to point out that as soon as search locates "v| prep| det|" it will stop. COMBO will not try to find all possible matches specified by search patter. So, "v| prep| det| n|" or "v| prep| det| adj| n|" will never be found by COMBO.

But, I just tested COMBO and it doesn't work as well as it should. I would recommend to you to use some other regular expression search application for searches that are this complicated. You can use KWAL command to extract only specific speakers and their associated "%mor" tiers from your data, if you are only interested in searching just some specific speakers' data. And then use "LONGTIER *.cha" command to make each "%mor" tier fit on just one line, in case your search application can not search across multiple lines such as the case when "%mor" tier wraps around. Meanwhile, I will try for fix COMBO.

Leonid.

> --
> You received this message because you are subscribed to the Google Groups "chibolts" group.
> To post to this group, send email to chib...@googlegroups.com.
> To unsubscribe from this group, send email to chibolts+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/chibolts?hl=en.
>
>

[Liam Considine]

Leonid,

Thanks for the quick reply about the NOT market '!'
It is also good to know that COMBO behaves differently than I had
assumed (i.e. not try to find all possible matches.)

If i were to make a combo.cut file where I disentangled this search
into a set of individual +t%mor regular expressions,
would it then be more likely to return the

"v| prep| det| n|" or "v| prep| det| adj| n|" ?

I appreciate your energy,
Liam

[Leonid Spektor]

Liam,

If you remove all 'OR' options and list all explicit final search conditions, then combo will do wht you expect it to. But, in this case your original search will be broken up into 15 following searches:

+s"v|*^prep|*^n|*"
+s"v|*^prep|*^pro|*"
+s"v|*^prep|*^det|*"

+s"v|*^prep|*^det|*^n|*"
+s"v|*^prep|*^det|*pro|*"
+s"v|*^prep|*^det|*det|*"

+s"v|*^prep|*^qn|*^n|*"
+s"v|*^prep|*^qn|*pro|*"
+s"v|*^prep|*^qn|*det|*"

+s"v|*^prep|*^det|*^adj|*^n|*"
+s"v|*^prep|*^det|*^adj|*^pro|*"
+s"v|*^prep|*^det|*^adj|*^det|*"

+s"v|*^prep|*^qn|*^adj|*^n|*"
+s"v|*^prep|*^qn|*^adj|*^pro|*"
+s"v|*^prep|*^qn|*^adj|*^det|*"

You can put those search commands into a batch file like the one I am attaching here and run them with command:

bat combo_search.cut

Leonid.