Clause Delimiter [^c]
If you wish to conduct analyses such as MLU and MLT based on clauses rather than utterances as the basic unit of analysis, you should mark the end of each clause with this symbol. It is not necessary to mark the scope of this symbol, since it is assumed to apply to all the material before it up to the beginning of the utterance or up to the preceding [^c] marker. It is possible to create additonal user-defined single-letter codes using this format, such as [^d] which could be defined as a marker of a clause that includes an error. Then, inside the MLU and MLT programs, you need to add the +c switch to specify exactly which codes of this type should be recognized.
--
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...@googlegroups.com.
To post to this group, send email to chib...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/CA%2B3CKJ5mRuFy4MWXiAZP6G89UJE59hFSZSdPH5a4M6_k9EReEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Nicole,We gave this idea more consideration and using our existing conventions we decided to handle clauses differently. You can still have symbol [^c] for clauses without errors. But, for clauses with errors you can have a generic code [^c *], or a more specific codes [^c error type 1], [^c error type 2] and so on [^c error ...]. This convention will make it easier for FREQ to search for all clauses using this command: freq +s"[^c*]". Or for only clauses without errors with this command:freq +s"[^c]". Or for specific error/type clause with this command: freq +s"[^c error type 1]".
Leonid.
To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/8D1A96C5-C7F6-4FAE-AA4B-99E5825122DD%40cmu.edu.