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. How long does tuning step take? (renubalyan)
2. Re: How long does tuning step take? (Philipp Koehn)
3. Max Number of Mert iterations (Maryam Aminian)
4. Re: Max Number of Mert iterations (Philipp Koehn)
5. Re: Error while compiling Moses (nakul sharma)
----------------------------------------------------------------------
Message: 1
Date: Sat, 21 Dec 2013 01:37:40 +0530 (IST)
From: renubalyan <renubalyan@cdac.in>
Subject: [Moses-support] How long does tuning step take?
To: moses-support@mit.edu
Message-ID:
<884459095.28881.1387570060581.JavaMail.open-xchange@webmail.cdac.in>
Content-Type: text/plain; charset="utf-8"
Hi,
How long should the tuning step say for a small set of 200 sentences take?
or is there a way know that whether the tuning step is moving correctly or not
or what is the maximum possible number of iterations the tuning step takes?
Thanks
Renu
-------------------------------------------------------------------------------------------------------------------------------
This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20131221/f3041146/attachment-0001.htm
------------------------------
Message: 2
Date: Fri, 20 Dec 2013 15:53:39 -0500
From: Philipp Koehn <pkoehn@inf.ed.ac.uk>
Subject: Re: [Moses-support] How long does tuning step take?
To: renubalyan <renubalyan@cdac.in>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAAFADDDLCNcgpUjFCjR_gRsQJTmXenGHEaedYxCisnv6FvMefw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
the biggest cost in tuning is the repeated decoding of the tuning
set with different weights. You can track the progress by checking
the files generated in the temporary directory.
Tuning runs by deafult for a maximum of 25 iterations, or when
convergence is reached.
-phi
On Fri, Dec 20, 2013 at 3:07 PM, renubalyan <renubalyan@cdac.in> wrote:
> Hi,
>
> How long should the tuning step say for a small set of 200 sentences take?
> or is there a way know that whether the tuning step is moving correctly or
> not or what is the maximum possible number of iterations the tuning step
> takes?
>
>
> Thanks
> Renu
>
> -------------------------------------------------------------------------------------------------------------------------------
> This e-mail is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies and the original message. Any unauthorized review, use,
> disclosure, dissemination, forwarding, printing or copying of this email
> is strictly prohibited and appropriate legal action will be taken.
> -------------------------------------------------------------------------------------------------------------------------------
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
------------------------------
Message: 3
Date: Fri, 20 Dec 2013 16:21:33 -0500
From: Maryam Aminian <aminian.mary@gmail.com>
Subject: [Moses-support] Max Number of Mert iterations
To: moses-support <moses-support@mit.edu>
Message-ID:
<CAHhcigEHdwYM+xohNUzXq-1sAA9q=wjCoNRN052HJ10ax55PrQ@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello everyone,
I have a problem with the max number of iterations of Mert that appreciate
it if you can help me.
I have run mert-moses.pl and can see that the tuning process has
interrupted after 25th run. How can I change the maximum number of
iterations of mert step so that I can make sure that it has converged?
Best Regards,
Maryam
--
-- Maryam Aminian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20131220/8ae9bc9f/attachment-0001.htm
------------------------------
Message: 4
Date: Fri, 20 Dec 2013 18:35:08 -0500
From: Philipp Koehn <pkoehn@inf.ed.ac.uk>
Subject: Re: [Moses-support] Max Number of Mert iterations
To: Maryam Aminian <aminian.mary@gmail.com>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAAFADDCF-UT2-FAciDQA19GYkazO5ZD6B52eTqkePVVLB+9KAg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
add the switch "-maximum-iterations 50" to the call to mert-moses.pl
(or any other number).
-phi
On Fri, Dec 20, 2013 at 4:21 PM, Maryam Aminian <aminian.mary@gmail.com> wrote:
> Hello everyone,
>
> I have a problem with the max number of iterations of Mert that appreciate
> it if you can help me.
> I have run mert-moses.pl and can see that the tuning process has interrupted
> after 25th run. How can I change the maximum number of iterations of mert
> step so that I can make sure that it has converged?
>
> Best Regards,
> Maryam
>
> --
> -- Maryam Aminian
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
------------------------------
Message: 5
Date: Sat, 21 Dec 2013 11:01:05 +0530
From: nakul sharma <nakul777@gmail.com>
Subject: Re: [Moses-support] Error while compiling Moses
To: Christophe Servan <christophe.servan@gmail.com>
Cc: moses-support@mit.edu
Message-ID:
<CAHGfYnoAR48qgEJ_G5u34GMSv1P1SXAWu_omjWPpTrrWT8Ux5w@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Christophe,
Thank you for help and guidance. My system configuration is as under:-
OS: Ubuntu 12.04.2 LTS(updated some 100 days ago)
RAM: 3 GB
HDD: 40 GB (for linux)
I have already installed the bzip2 library. When I execute on terminal
following command:-
whereis bzip2
is get following result:-
nakul@nakul-Inspiron-1545:~$ whereis bzip2
bzip2: /bin/bzip2 /usr/share/man/man1/bzip2.1.gz
nakul@nakul-Inspiron-1545:~$
This indicates that bzip2 is installed. Please tell what can be possible
solution ?
On Fri, Dec 20, 2013 at 2:51 PM, Christophe Servan <
christophe.servan@gmail.com> wrote:
> Dear Nakul,
> did you install the bzip2 library (i.e. the package bzip2-dev) ?
>
> Best,
>
> Christophe
>
>
> 2013/12/20 nakul sharma <nakul777@gmail.com>
>
>> Hi,
>>
>> I am trying to compile moses. But I am getting following error messages.
>> Please help in this regard.
>>
>> notice: found boost-build.jam at /usr/share/boost-build/boost-build.jam
>> notice: loading Boost.Build from /usr/share/boost-build/kernel
>> notice: Searching /etc /home/nakul /usr/share/boost-build/kernel
>> /usr/share/boost-build /usr/share/boost-build/kernel
>> /usr/share/boost-build/util /usr/share/boost-build/build
>> /usr/share/boost-build/tools /usr/share/boost-build/contrib
>> /usr/share/boost-build/. for site-config configuration file site-config.jam
>> .
>> notice: Configuration file site-config.jam not found in /etc /home/nakul
>> /usr/share/boost-build/kernel /usr/share/boost-build
>> /usr/share/boost-build/kernel /usr/share/boost-build/util
>> /usr/share/boost-build/build /usr/share/boost-build/tools
>> /usr/share/boost-build/contrib /usr/share/boost-build/. .
>> notice: Searching /home/nakul /usr/share/boost-build/kernel
>> /usr/share/boost-build /usr/share/boost-build/kernel
>> /usr/share/boost-build/util /usr/share/boost-build/build
>> /usr/share/boost-build/tools /usr/share/boost-build/contrib
>> /usr/share/boost-build/. for user-config configuration file user-config.jam
>> .
>> notice: Configuration file user-config.jam not found in /home/nakul
>> /usr/share/boost-build/kernel /usr/share/boost-build
>> /usr/share/boost-build/kernel /usr/share/boost-build/util
>> /usr/share/boost-build/build /usr/share/boost-build/tools
>> /usr/share/boost-build/contrib /usr/share/boost-build/. .
>>
>> file /home/nakul/mosesdecoder-master/previous.sh
>> #!/bin/sh
>> /usr/bin/bjam -j2 --debug-configuration -d2
>>
>>
>> bash -c "g++ -lSegFault -x c++ - <<<'int main() {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -static -lSegFault -x c++ - <<<'int main() {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 1
>> bash -c "g++ -lboost_program_options-1_46_1 -x c++ - <<<'int main() {}'
>> -o /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 1
>> bash -c "g++ -static -lboost_program_options -x c++ - <<<'int main() {}'
>> -o /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -lboost_system-mt -static -x c++ - <<<'int main() {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -lboost_thread-mt -static -x c++ - <<<'int main() {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -lboost_program_options-mt -static -x c++ - <<<'int main()
>> {}' -o /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -lboost_unit_test_framework-mt
>> -DBOOST_TEST_MODULE=CompileTest -include boost/test/unit_test.hpp -static
>> -x c++ - <<<'BOOST_AUTO_TEST_CASE(foo) {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -lboost_iostreams-mt -static -x c++ - <<<'int main() {}'
>> -o /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -lboost_filesystem-mt -static -x c++ - <<<'int main() {}'
>> -o /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -static -lz -x c++ - <<<'int main() {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 0
>> bash -c "g++ -ltcmalloc_minimal -x c++ - <<<'int main() {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 1
>> Tip: install tcmalloc for faster threading. See BUILD-INSTRUCTIONS.txt
>> for more information.
>> warning: No toolsets are configured.
>> warning: Configuring default toolset "gcc".
>> warning: If the default is wrong, your build may not work correctly.
>> warning: Use the "toolset=xxxxx" option to override our guess.
>> warning: For more configuration options, please consult
>> warning:
>> http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
>> notice: will use 'g++' for gcc, condition <toolset>gcc-4.6
>> notice: using gcc libraries :: <toolset>gcc-4.6 :: /usr/bin /usr/lib
>> /usr/lib32 /usr/lib64
>> notice: using gcc archiver :: <toolset>gcc-4.6 :: /usr/bin/ar
>> notice: using gcc ranlib :: <toolset>gcc-4.6 :: /usr/bin/ranlib
>> warning: toolset gcc initialization: can not find tool windres
>> warning: initialized from
>> notice: using rc compiler :: <toolset>gcc-4.6 :: /usr/bin/as
>> bash -c "g++ -lbz2 -x c++ - <<<'int main() {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 1
>> bash -c "g++ -llzma -x c++ - <<<'int main() {}' -o
>> /home/nakul/mosesdecoder-master/dummy >/dev/null 2>/dev/null && rm
>> /home/nakul/mosesdecoder-master/dummy 2>/dev/null"
>> 1
>> ...patience...
>> ...found 3439 targets...
>> ...updating 4 targets...
>> gcc.link
>> moses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/moses
>>
>> "g++" -o
>> "moses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/moses"
>> -Wl,--start-group
>> "moses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/Main.o"
>> "moses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/IOWrapper.o"
>> "moses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/mbr.o"
>> "moses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/LatticeMBR.o"
>> "moses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/TranslationAnalysis.o"
>> "moses/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/libmoses.a"
>> -Wl,-Bstatic -lz -lboost_filesystem-mt -lboost_iostreams-mt
>> -lboost_thread-mt -lboost_system-mt -lz -Wl,-Bdynamic -lrt -ldl -lSegFault
>> -lrt -Wl,--end-group -g -pthread
>>
>>
>> /usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib/libboost_iostreams-mt.a(bzip2.o):
>> In function `boost::iostreams::detail::bzip2_base::do_init(bool, void*
>> (*)(void*, int, int), void (*)(void*, void*), void*)':
>> (.text+0x2e9): undefined reference to `BZ2_bzDecompressInit'
>> /usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib/libboost_iostreams-mt.a(bzip2.o):
>> In function `boost::iostreams::detail::bzip2_base::do_init(bool, void*
>> (*)(void*, int, int), void (*)(void*, void*), void*)':
>> (.text+0x391): undefined reference to `BZ2_bzCompressInit'
>> /usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib/libboost_iostreams-mt.a(bzip2.o):
>> In function `boost::iostreams::detail::bzip2_base::end(bool)':
>> (.text+0x455): undefined reference to `BZ2_bzDecompressEnd'
>> /usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib/libboost_iostreams-mt.a(bzip2.o):
>> In function `boost::iostreams::detail::bzip2_base::end(bool)':
>> (.text+0x4d1): undefined reference to `BZ2_bzCompressEnd'
>> /usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib/libboost_iostreams-mt.a(bzip2.o):
>> In function `boost::iostreams::detail::bzip2_base::compress(int)':
>> (.text+0x18c): undefined reference to `BZ2_bzCompress'
>> /usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib/libboost_iostreams-mt.a(bzip2.o):
>> In function `boost::iostreams::detail::bzip2_base::decompress()':
>> (.text+0x19c): undefined reference to `BZ2_bzDecompress'
>> collect2: ld returned 1 exit status
>> ...failed gcc.link
>> moses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/moses...
>> ...skipped <p/home/nakul/mosesdecoder-master/bin>moses for lack of
>> <pmoses-cmd/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>moses...
>> testing.capture-output
>> moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest.run
>>
>>
>> LD_LIBRARY_PATH="/usr/bin:/usr/lib:/usr/lib32:/usr/lib64:$LD_LIBRARY_PATH"
>> export LD_LIBRARY_PATH
>>
>>
>> "moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest"
>> "moses/LM/backward.arpa" >
>> "moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest.output"
>> 2>&1
>> status=$?
>> echo >>
>> "moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest.output"
>> echo EXIT STATUS: $status >>
>> "moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest.output"
>> if test $status -eq 0 ; then
>> cp
>> "moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest.output"
>> "moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest.run"
>> fi
>> verbose=0
>> if test $status -ne 0 ; then
>> verbose=1
>> fi
>> if test $verbose -eq 1 ; then
>> echo ====== BEGIN OUTPUT ======
>> cat
>> "moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest.output"
>> echo ====== END OUTPUT ======
>> fi
>> exit $status
>>
>> ====== BEGIN OUTPUT ======
>> Running 1 test case...
>> moses/LM/BackwardTest.cpp(162): error in "ProbingAll": difference{100%}
>> between static_cast<double>(TransformLMScore( 0.0 )){0} and
>> static_cast<double>(ngramScore){1.3724476843890443e-07} exceeds 0.01%
>>
>> *** 1 failure detected in test suite "BackwardTest"
>>
>> EXIT STATUS: 201
>> ====== END OUTPUT ======
>> ...failed testing.capture-output
>> moses/LM/bin/BackwardTest.test/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/BackwardTest.run...
>> ...failed updating 2 targets...
>> ...skipped 2 targets...
>> The build failed with command line:
>> /usr/bin/bjam -j2 --debug-configuration -d2
>> If you need support, attach the full output to your e-mail.
>> ERROR
>>
>> --
>> Thanks & Regards,
>> Nakul Sharma
>>
>>
>>
>> _______________________________________________
>> Moses-support mailing list
>> Moses-support@mit.edu
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>>
>
--
Thanks & Regards,
Nakul Sharma
Assistant Professor (IT)
Sinhgad Academy of Engineering (SAE)
Pune
India.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20131221/e2403251/attachment.htm
------------------------------
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
End of Moses-support Digest, Vol 86, Issue 60
*********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 86, Issue 60"
Post a Comment