Moses-support Digest, Vol 124, Issue 19

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. ReportingOptions and mosesserver XML (Lane Schwartz)
2. Error: died with signal 11, with coredump (Arpita Dutta)


----------------------------------------------------------------------

Message: 1
Date: Mon, 20 Feb 2017 11:39:32 -0600
From: Lane Schwartz <dowobeha@gmail.com>
Subject: [Moses-support] ReportingOptions and mosesserver XML
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CABv3vZnnnV=Lfe-SDXSHKTosTKxBjk-d9S7tSLhTo7wUDkJ+oA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

In moses/parameters/ReportingOptions.cpp, the following code was added by
Uli in commit 69e5a1cc152de40 about a year ago:


m = param.find("align");
if (m != param.end() && Scan<bool>(xmlrpc_c::value_string(m->second)))
ReportSegmentation = 1;


This is relevant when using XML-RPC requests via mosesserver, and it turns
on ReportSegmentation if the XML response includes segmentation. Most of
the time this would be superfluous, since the reason that the XML response
contains segmentation is typically because ReportSegmentation was already
set to 1 in the moses server config file.

I'm interested in re-enabling the moses server code that allows this to
alternatively be set via XML-RPC request, but I don't want
ReportSegmentation turned on in this case. The reason is that I want the
segmentation information, but I don't want the returned hypothesis to
include the segmentation in the reported hypothesis string. If
ReportSegmentation is set to 1, then that will happen.

My question is, is it OK to delete or comment out this block of code?

If someone has a good reason why it's there, that's fine. But I can't seem
to find one.

Thanks,
Lane
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20170220/9df6f889/attachment-0001.html

------------------------------

Message: 2
Date: Mon, 20 Feb 2017 12:07:12 +0530
From: Arpita Dutta <duttaarpi@gmail.com>
Subject: [Moses-support] Error: died with signal 11, with coredump
To: Moses-support@mit.edu
Message-ID:
<CAKKUE23qZwyqKNRUdzkfi7-iZxhtsMW691FY9KQVXoDUyCRVbg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello everyone'

Hmm: Iteration 1
ERROR: Execution of: /home/nits/Desktop/ad/mosesdecoder/tools/GIZA++
-CoocurrenceFile /home/nits/Desktop/ad/demo1/giza.ben-en/ben-en.cooc -c
/home/nits/Desktop/ad/demo1/corpus/ben-en-int-train.snt -m1 5 -m2 0
-m3 3 -m4 3 -model1dumpfrequency 1
model4smoothfactor 0.4 -nodumps 1 -nsmooth 4 -o
/home/nits/Desktop/ad/demo1/giza.ben-en/ben-en
-onlyaldumps 1 -p0 0.999 -s /home/nits/Desktop/ad/demo1/corpus/en.vcb
-t /home/nits/Desktop/ad/demo1/corpus/ben.vcb
died with signal 11, with coredump

Can anyone please explain to me why this error is coming?I am using a
parallel corpora of 5000 sentences for training,3500 sentences for
tuning and 4GB RAM.

I have tried this command once to remove segmentation fault -S 50%.I
have got result that time but now this command is not working.

Is there any other command to remove this error?

Please help me.

Arpita Dutta

PhD Scholar

Nit Silchar

Assam-788010

India
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20170220/24d3df6f/attachment-0001.html

------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 124, Issue 19
**********************************************

Tweet