<HTML>
<HEAD>
<TITLE>Re: confusing MOR behavior</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Melissa,<BR>
<BR>
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 <a href="spektor@andrew.cmu.edu">spektor@andrew.cmu.edu</a>.<BR>
<BR>
Thanks,<BR>
Leonid.<BR>
<BR>
<BR>
On 19-12-08 09:34, "Melissa Sherman" <<a href="melissa.c.sherman@gmail.com">melissa.c.sherman@gmail.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Brian,<BR>
<BR>
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.<BR>
<BR>
I wish you and Leonid a happy holidays!<BR>
<BR>
mesh<BR>
<BR>
<BR>
<BR>
On Fri, Dec 19, 2008 at 5:37 AM, Brian MacWhinney <<a href="macw@cmu.edu">macw@cmu.edu</a>> wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Dear Melissa,<BR>
We have changed the format of CHAT in a couple of ways recently<BR>
that are sure to mess up the use of SALTIN. Right now, I am on<BR>
vacation in Borneo and Leonid is also on vacation until just after<BR>
Christmas. So, I am afraid that we will not be able to fix SALTIN for<BR>
a week or two. If this is urgent, you could send me the files and<BR>
perhaps I could work on them.<BR>
<BR>
--Brian<BR>
<BR>
On Dec 16, 2008, at 11:16 PM, Melissa Sherman wrote:<BR>
<BR>
><BR>
> Hi-<BR>
><BR>
> I am working with a group of children's transcripts and using MOR and<BR>
> POST from the CLAN toolkit. Everything was working wonderfully until<BR>
> MOR decided to give me a segmentation fault during batch processing<BR>
> one day. Here is what I try to accomplish:<BR>
><BR>
> I first have transcripts in the SALT format. I convert these to UTF8<BR>
> and then use SALTIN to change them to CHAT format. This step has<BR>
> always worked fine for me with a batch processing. (saltin *.slt)<BR>
><BR>
> At this point, I can run MOR on all the files (mor +l"lex" *.cha) and<BR>
> all files will process. However, if I run CHECK on the .cha files, I<BR>
> find errors.<BR>
><BR>
> My next step is to clean the files using my own script. After they are<BR>
> cleaned, they pass through CHECK without any errors.<BR>
><BR>
> Now comes the strange part. When I run MOR on all the cleaned files, I<BR>
> get a segmentation fault 258 files through, out of 302. If I run each<BR>
> cleaned file through MOR individually, though, they all process<BR>
> without any errors.<BR>
><BR>
> This puzzles me because it appears that the fault lies within my<BR>
> cleaning script, but I am not sure what types of things I could<BR>
> correct because CHECK is not returning any errors. I also have a<BR>
> couple hundred (I like batch processing) other transcripts in a few<BR>
> corpora that are still batch processing completely, while using the<BR>
> same scripts.<BR>
><BR>
> We use the linux version of CLAN. The segmentation fault error that I<BR>
> recieve follows. This example is trying to compile an unknown word<BR>
> list using the +xl flag.<BR>
> (after 258 files)<BR>
> From file <h10633.cln> to file <b10135.ul2.cex><BR>
> Using sf-rule: /users/mesh/lang_imp/lex/english/sf.cut.<BR>
> Using ex-rule: /users/mesh/lang_imp/lex/english/ex.cut.<BR>
> Using a-rules: /users/mesh/lang_imp/lex/english/ar.cut.<BR>
> Segmentation fault<BR>
><BR>
> Any help or ideas would be greatly appreciated.<BR>
><BR>
> Melissa Sherman<BR>
> ><BR>
><BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
<br>
--~--~---------~--~----~------------~-------~--~----~<br>
You received this message because you are subscribed to the Google Groups "chibolts" group. <br> To post to this group, send email to chibolts@googlegroups.com <br> To unsubscribe from this group, send email to chibolts+unsubscribe@googlegroups.com <br> For more options, visit this group at http://groups.google.com/group/chibolts?hl=en<br>
-~----------~----~----~----~------~----~------~--~---<br>
</BODY>
</HTML>
<br>