Moses-support Digest, Vol 101, Issue 34

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. Re: Couldn't use --working-dir of mert-moses.pl (Tom Hoar)
2. Re: Error while compiling Moses v3.0 on Cygwin
(Muhammad Danial Raza)
3. Moses segmentation fault under multi-thread (Liangyou Li)


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

Message: 1
Date: Wed, 11 Mar 2015 10:52:36 +0700
From: Tom Hoar <tahoar@precisiontranslationtools.com>
Subject: Re: [Moses-support] Couldn't use --working-dir of
mert-moses.pl
To: moses-support@mit.edu
Message-ID: <54FFBC04.4090505@precisiontranslationtools.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

The several arguments are positional arguments OR named arguments, which
can be confusing. Full paths often solve problems. Also, not sure if the
equal sign causes problems. So, try this:

nohup nice mosesdecoder/scripts/training/mert-moses.pl \
--decoder-flags "-threads 8" \
--working-dir /home/fubin/moses/work/mert-work5 \
--input <full-path>/data/fr-en2006/dev/dev2006.true.fr \
--refs <full-path>/data/fr-en2006/dev/dev2006.true.en \
--decoder <full-path>/mosesdecoder/bin/moses \
--config <full-path>/work/train/model/moses.ini \
--mertdir <full-path>/mosesdecoder/bin/ &> work/outfile/mertstart.out



On 03/11/2015 10:38 AM, ?? wrote:
> nohup nice mosesdecoder/scripts/training/mert-moses.pl
> --decoder-flags="-threads 8"
> --working-dir=/home/fubin/moses/work/mert-work5
> data/fr-en2006/dev/dev2006.true.fr data/fr-en2006/dev/dev2006.true.en
> mosesdecoder/bin/moses work/train/model/moses.ini
> --mertdir=mosesdecoder/bin/ &> work/outfile/mertstart.out



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

Message: 2
Date: Wed, 11 Mar 2015 15:44:48 +0500
From: Muhammad Danial Raza <muhammad.danial.raza@gmail.com>
Subject: Re: [Moses-support] Error while compiling Moses v3.0 on
Cygwin
To: Hieu Hoang <hieuhoang@gmail.com>
Cc: moses-support@mit.edu
Message-ID:
<CAEQzcOe7OajgGRPBtx_XUphxic_9hqwikDc9fZuAvw5vbam6rQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Thank you Hieu, the second point did the trick for me.

On Tue, Mar 10, 2015 at 8:43 PM, Hieu Hoang <hieuhoang@gmail.com> wrote:

> there seems to be a problem with the unit tests, similar to
> https://www.mail-archive.com/moses-support%40mit.edu/msg11603.html
> Either
> 1. Ignore it, if the executables compiled ok
> 2. Use the current source code from the github master branch. The issue
> should have be fixed already
>
>
> On 10/03/2015 12:37, Muhammad Danial Raza wrote:
>
> Hello,
>
> I have a 32-bit Cygwin on a 64-bit windows machine. I have followed the
> following steps to compile moses:
>
> - Compiled boost using the following commands:
> - "*cd ~/mosesdecoder/boost_1_55_0/*"
> -
> - *"./b2 -j8 -q --prefix=$PWD --libdir=$PWD/lib64
> --without-context --layout=system link=static install || echo FAILURE"*
> - *"--without-context" *because "Boost.Context" is not supported on
> cygwin and also it is not required by moses. (Reference
> <http://comments.gmane.org/gmane.comp.nlp.moses.user/10701>)
> - Secondly, I used the following command to compile moses:
> -
> - *./bjam --with-boost=~/mosesdecoder/boost_1_55_0 -j8*
> - Attached is the output and the build log
>
> Any help in this regard would be appreciable.
>
> Regards,
> Muhammad Danial Raza
>
>
> _______________________________________________
> Moses-support mailing listMoses-support@mit.eduhttp://mailman.mit.edu/mailman/listinfo/moses-support
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150311/a251ad59/attachment-0001.htm

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

Message: 3
Date: Wed, 11 Mar 2015 12:12:29 +0000
From: Liangyou Li <llysuda@gmail.com>
Subject: [Moses-support] Moses segmentation fault under multi-thread
To: moses-support@mit.edu
Message-ID:
<CAHeunNU-deR3izpULULKVWF9oe2iiOJwP20cKDoLRhhh=jCz=g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

When I run moses with sparse features in multi-threads ( parameter -threads
all), I got segmentation fault.

The three sparse features are:
*SourceWordDeletionFeature factor=0*
* TargetWordInsertionFeature factor=0*
* WordTranslationFeature input-factor=0 output-factor=0*

The exact command I used is:
*moses_chart -threads all -f moses.ini -i input -n-best-list nbest 100
distinct*

This error happens kind of randomly?. But it only happens when sparse
features and multi-threads are used.

I've tried several times to use gdb to trace the error. Fortunately, I just
get the back-trace info, as listed:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdae77700 (LWP 32390)]
0x00007ffff711f5e3 in std::basic_ostream<char, std::char_traits<char> >&
std::operator<< <char, std::char_traits<char>, std::allocator<char>
>(std::basic_ostream<char, std::char_traits<char> >&,
std::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&) () from /usr/lib64/libstdc++.so.6
Missing separate debuginfos, use: zypper install
glibc-debuginfo-2.15-22.17.1.x86_64
libgcc47-debuginfo-4.7.1_20120723-1.1.1.x86_64
liblzma5-debuginfo-5.0.3-12.2.2.x86_64
libstdc++47-debuginfo-4.7.1_20120723-1.1.1.x86_64
zlib-debuginfo-1.2.7-2.1.2.x86_64
(gdb) backtrace
#0 0x00007ffff711f5e3 in std::basic_ostream<char, std::char_traits<char>
>& std::operator<< <char, std::char_traits<char>, std::allocator<char>
>(std::basic_ostream<char, std::char_traits<char> >&,
std::basic_string<char, std::char_traits<char>, std::allocator<char> >
const&) () from /usr/lib64/libstdc++.so.6
#1 0x0000000000584711 in Moses::operator<< (out=..., name=...) at
moses/FeatureVector.cpp:141
#2 0x0000000000440232 in
Moses::ScoreComponentCollection::GetVectorForProducer (this=0x7fffad0e9380,
sp=0xe2aab0) at moses/ScoreComponentCollection.cpp:293
#3 0x00000000004407da in
Moses::ScoreComponentCollection::OutputFeatureScores (this=0x7fffad0e9380,
out=..., ff=0xe2aab0, lastName="LM0") at
moses/ScoreComponentCollection.cpp:351
#4 0x000000000044055a in
Moses::ScoreComponentCollection::OutputAllFeatureScores
(this=0x7fffad0e9380, out=...) at moses/ScoreComponentCollection.cpp:319
#5 0x0000000000561ce4 in Moses::ChartManager::OutputNBestList
(this=0x7fffacbe0010, collector=0x9320d210, nBestList=std::vector of length
100, capacity 128 = {...}, translationId=569)
at moses/ChartManager.cpp:381
#6 0x00000000005619d6 in Moses::ChartManager::OutputNBest
(this=0x7fffacbe0010, collector=0x9320d210) at moses/ChartManager.cpp:335
#7 0x0000000000467cd6 in Moses::TranslationTask::Run (this=0x214d90b0) at
moses/TranslationTask.cpp:111
#8 0x0000000000530b69 in Moses::ThreadPool::Execute (this=0x7fffffffd710)
at moses/ThreadPool.cpp:61
#9 0x0000000000534ecd in boost::_mfi::mf0<void,
Moses::ThreadPool>::operator() (this=0xf263088, p=0x7fffffffd710) at
/home/lly/plateform/boost_1_55_0/include/boost/bind/mem_fn_template.hpp:49
#10 0x0000000000534e30 in
boost::_bi::list1<boost::_bi::value<Moses::ThreadPool*>
>::operator()<boost::_mfi::mf0<void, Moses::ThreadPool>, boost::_bi::list0>
(this=0xf263098, f=..., a=...)
at /home/lly/plateform/boost_1_55_0/include/boost/bind/bind.hpp:253
#11 0x0000000000534dd5 in boost::_bi::bind_t<void, boost::_mfi::mf0<void,
Moses::ThreadPool>, boost::_bi::list1<boost::_bi::value<Moses::ThreadPool*>
> >::operator() (this=0xf263088)
at
/home/lly/plateform/boost_1_55_0/include/boost/bind/bind_template.hpp:20
#12 0x0000000000534d9a in
boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void,
Moses::ThreadPool>, boost::_bi::list1<boost::_bi::value<Moses::ThreadPool*>
> > >::run (this=0xf262ed0)
at
/home/lly/plateform/boost_1_55_0/include/boost/thread/detail/thread.hpp:117
#13 0x00000000008b4752 in thread_proxy ()
#14 0x00007ffff6965e0e in start_thread () from /lib64/libpthread.so.0
#15 0x00007ffff669d2cd in clone () from /lib64/libc.so.6

?Has anyone ?had the problem before ? Any ideas on solving this ?
Many Thanks ?


PS: In my experiment, I found the function " void
CompletedRuleCollection::Add(const TargetPhraseCollection &tpc, const
StackVec &stackVec, const std::vector<float> &stackScores, const
ChartParserCallback &outColl) " does not consider " m_ruleLimit " . So
after adding parameter " -rule-limit 0 ", the decoder can only collect one
translation option.


Cheers
Liangyou



--

Liangyou Li
CNGL
School of Computing
Dublin City University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20150311/cdc531f4/attachment.htm

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

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


End of Moses-support Digest, Vol 101, Issue 34
**********************************************

Tweet