confusing MOR behavior

[Leonid Spektor]

Melissa,

    I just tried "mor +xl" command in Mac Unix on few of our data files and
it worked fine. As you stated in your email, there must be something in your
clean files that as a result of cumulative effect crashes mor program.
Because this is a specific situation, possibly limited to your unique data
set, I would need your whole 302 file data set to test and fix mor program.
Please zip it and email it to me directly, instead of chibolts address. My
email spektor at andrew.cmu.edu.

Thanks,
Leonid.


On 19-12-08 09:34, "Melissa Sherman" <melissa.c.sherman at gmail.com> wrote:

> Brian,
> 
> This is not an urgent matter for me, as I can run each file individually
> through MOR. I appreciate you taking time out of your vacation to reply to my
> email.
> 
> I wish you and Leonid a happy holidays!
> 
> mesh
> 
> 
> 
> On Fri, Dec 19, 2008 at 5:37 AM, Brian MacWhinney <macw at cmu.edu> wrote:
>> 
>> Dear Melissa,
>>      We have changed the format of CHAT in a couple of ways recently
>> that are sure to mess up the use of SALTIN.  Right now, I am on
>> vacation in Borneo and Leonid is also on vacation until just after
>> Christmas.  So,  I am afraid that we will not be able to fix SALTIN for
>> a week or two.  If this is urgent, you could send me the files and
>> perhaps I could work on them.
>> 
>> --Brian
>> 
>> On Dec 16, 2008, at 11:16 PM, Melissa Sherman wrote:
>> 
>>> >
>>> > Hi-
>>> >
>>> > I am working with a group of children's transcripts and using MOR and
>>> > POST from the CLAN toolkit. Everything was working wonderfully until
>>> > MOR decided to give me a segmentation fault during batch processing
>>> > one day. Here is what I try to accomplish:
>>> >
>>> > I first have transcripts in the SALT format. I convert these to UTF8
>>> > and then use SALTIN to change them to CHAT format. This step has
>>> > always worked fine for me with a batch processing. (saltin *.slt)
>>> >
>>> > At this point, I can run MOR on all the files (mor +l"lex" *.cha) and
>>> > all files will process. However, if I run CHECK on the .cha files, I
>>> > find errors.
>>> >
>>> > My next step is to clean the files using my own script. After they are
>>> > cleaned, they pass through CHECK without any errors.
>>> >
>>> > Now comes the strange part. When I run MOR on all the cleaned files, I
>>> > get a segmentation fault 258 files through, out of 302. If I run each
>>> > cleaned file through MOR individually, though, they all process
>>> > without any errors.
>>> >
>>> > This puzzles me because it appears that the fault lies within my
>>> > cleaning script, but I am not sure what types of things I could
>>> > correct because CHECK is not returning any errors. I also have a
>>> > couple hundred (I like batch processing) other transcripts in a few
>>> > corpora that are still batch processing completely, while using the
>>> > same scripts.
>>> >
>>> > We use the linux version of CLAN. The segmentation fault error that I
>>> > recieve follows. This example is trying to compile an unknown word
>>> > list using the +xl flag.
>>> > (after 258 files)
>>> > From file <h10633.cln> to file <b10135.ul2.cex>
>>> > Using sf-rule: /users/mesh/lang_imp/lex/english/sf.cut.
>>> > Using ex-rule: /users/mesh/lang_imp/lex/english/ex.cut.
>>> > Using a-rules: /users/mesh/lang_imp/lex/english/ar.cut.
>>> > Segmentation fault
>>> >
>>> > Any help or ideas would be greatly appreciated.
>>> >
>>> > Melissa Sherman
>>>> > >
>>> >
>> 
>> 
>> 
> 
> 
> > 
> 


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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.linguistlist.org/pipermail/chibolts/attachments/20081222/32025d8f/attachment.htm>