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. error: ?intrusive_ptr_release? was not declared in this scope
(Nicholas Ruiz)
2. Re: use placeholder with mosesserver (Ulrich Germann)
3. Re: problem in generating phrase table after tuning
(Philipp Koehn)
----------------------------------------------------------------------
Message: 1
Date: Tue, 17 Nov 2015 14:48:39 -0500
From: Nicholas Ruiz <nicruiz@fbk.eu>
Subject: [Moses-support] error: ?intrusive_ptr_release? was not
declared in this scope
To: moses-support@mit.edu
Message-ID:
<CAKa+0YO2YX=5gmD7JbD+f06a0bJMNXH=-ZgEH9FT=06A+QUcUg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
I'm following the steps on this website to install the HEAD version of
moses on a CentOS
http://www.statmt.org/moses/?n=Development.GetStarted
$ cat /etc/issue
CentOS release 6.7 (Final)
Kernel \r on an \m
$ gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada
--enable-java-awt=gtk --disable-dssi
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib
--with-ppl --with-cloog --with-tune=generic --with-arch_32=i686
--build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC)
When attempting to compile using compile.sh, I get the following error:
"g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall
-pthread -I/n/w10-nruiz/mosesdecoder/opt/include
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK
-DBOOST_THREAD_DYN_DLL -DHAVE_CMPH -DHAVE_PROBINGPT -DHAVE_XMLRPC_C
-DKENLM_MAX_ORDER=6 -DLM_IRST -DMAX_NUM_FACTORS=4 -DNDEBUG -DPT_UG
-DTRACE_ENABLE=1 -DWITH_THREADS -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES
-I"." -I"moses/TranslationModel/CompactPT/opt/include" -I"opt/include"
-I"util/double-conversion" -c -o
"moses/TranslationModel/UG/bin/gcc-4.4.7/release/link-static/threading-multi/count-ptable-features.o"
"moses/TranslationModel/UG/count-ptable-features.cc"
...failed gcc.compile.c++
moses/TranslationModel/UG/bin/gcc-4.4.7/release/link-static/threading-multi/count-ptable-features.o...
gcc.compile.c++
moses/TranslationModel/UG/bin/gcc-4.4.7/release/link-static/threading-multi/ptable-describe-features.o
In file included from
/n/w10-nruiz/mosesdecoder/opt/include/boost/intrusive_ptr.hpp:16,
from moses/TranslationModel/UG/mmsapt.h:9,
from
moses/TranslationModel/UG/ptable-describe-features.cc:2:
/n/w10-nruiz/mosesdecoder/opt/include/boost/smart_ptr/intrusive_ptr.hpp: In
destructor ?boost::intrusive_ptr<T>::~intrusive_ptr() [with T =
sapt::mmBitext<sapt::L2R_Token<sapt::SimpleWordId> >]?:
moses/TranslationModel/UG/mmsapt.h:56: instantiated from here
/n/w10-nruiz/mosesdecoder/opt/include/boost/smart_ptr/intrusive_ptr.hpp:97:
error: ?intrusive_ptr_release? was not declared in this scope
I installed boost to ./opt using the instructions listed on the above site.
I'm able to compile just fine following the instructions on my MacBook Pro
(obviously different architecture). Any ideas why this might be happening?
Thanks,
Nick Ruiz
z?n? ???u
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151117/1cb5a8d5/attachment-0001.html
------------------------------
Message: 2
Date: Tue, 17 Nov 2015 21:34:15 +0000
From: Ulrich Germann <ulrich.germann@gmail.com>
Subject: Re: [Moses-support] use placeholder with mosesserver
To: Evgeny Matusov <ematusov@apptek.com>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAHQSRUqc9UjYTm_oTCx2VfeEYgCMKiv=Me17BkQNcU0Biet-9Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Evgeny,
"passing n-best size is commented out" because m_bestSize is deprecated.
Instead m_options.nbest.nbest_size is used, which is updated via the call
to m_options.update(params) at nor near line 277 in TranslationRequest.cpp.
So TranslationRequest is actually paying attention to the "nbest"
parameter, just not through the deprecated variable m_nbestSize.
My long-term strategy is to have one Class
(moses/parameters/)AllOptions(.h) that stores all the options for a
particular translation request, bundled roughly thematically (e.g., nbest
lists, OOV handling, etc.) The defaults are copied from StaticData when a
TranslationRequest is instantiated, and then updated via the aforementioned
call to m_options.update(params).
If you want to set any additional parameters through the server interface
that aren't set yet, do it through m_options.update(). I'm gradually moving
all the variables from StaticData into the Options classes, but I'm doing
it one variable at a time, because there are so many of them and calls to
StaticData::Instance().GetSomeVariableThatShouldntBeGlobalButIs() have
metastasised throughout the code base. If there's a variable that's still
in StaticData that you need to update dynamically, let me know and I'll
prioritize the transition.
The placeholder factor, by the way (since that is relevant for what you are
trying to do), is stored in
TraslationRequest.m_options.input.placeholder_factor.
Cheers - Uli
On Tue, Nov 17, 2015 at 2:43 PM, Evgeny Matusov <ematusov@apptek.com> wrote:
> Hi active Moses developers,
>
>
> As promised, I am working on adding the correct placeholder output to
> Moses in the server mode. Currently, passing the n-best size through xmlrpc
> is commented out. Any reason why this is the case? It might be convenient
> to run server queries with/without N-best output and with different N-best
> sizes without having to restart the server (currently, this is the only way
> to do it).
>
>
> If there are no objections, I will put this parameter back into the code.
>
>
> Best,
>
> Evgeny.
>
>
> ------------------------------
> *From:* Evgeny Matusov
> *Sent:* Wednesday, November 11, 2015 10:30 AM
> *To:* ugermann@inf.ed.ac.uk
>
> *Cc:* moses-support@mit.edu
> *Subject:* Re: [Moses-support] use placeholder with mosesserver
>
>
> Hi Uli,
>
>
> thanks a lot! We will try to add some test cases for Mosesserver,
> including XML input with/without placeholders.
>
>
> Best,
>
> Evgeny.
>
>
> ------------------------------
> *From:* Ulrich Germann <ulrich.germann@gmail.com>
> *Sent:* Wednesday, November 11, 2015 2:58 AM
> *To:* Evgeny Matusov
> *Cc:* moses-support@mit.edu
> *Subject:* Re: [Moses-support] use placeholder with mosesserver
>
> Hi all,
>
> I've just pushed what I believe might address a few of the issues in this
> thread:
>
> - the more fine-grained configuration options for request handling and
> queuing, server timeouts etc. (added in August due to threading issue) have
> been transferred to the main moses executable.
>
> - the server now pays attention to the xml-input option specified via
> json; the range of accepted values is the same as when specified on the
> command line. I have not written the xml-input handling and do not actively
> use it, so it may or may not work. I don't think there are any regression
> tests that test this right now. Reports from the trenches are welcome.
>
> - mosesserver.cpp is deprecated. It is now merely a shell around the
> regular moses call with --server. I did not remove it from the code base
> entirely, as I assume that there's a plethora of setups out there that rely
> on the existence of mosesserver. What the wrapper does is add --server to
> the options and then call run regular moses.
>
> - anyone adding stuff to mosesserver.cpp from now on owes me a lifetime
> supply of the finest Laphroaig. Just send me a quarter cask every year for
> Burns Nicht for the rest of my life if you do. If I haven't pushed anything
> for two years, you may assume I'm dead.
>
>
> - Uli
>
> On Tue, Nov 10, 2015 at 2:58 PM, Ulrich Germann <ulrich.germann@gmail.com>
> wrote:
>
>> Hi all,
>>
>> mosesserver is deprecated and should not be used any more. I'll transfer
>> the threading-related changes to the server implementation in the regular
>> moses executable and let you know once I'm done so that other things (like
>> passthrough) can be added. By the looks of it, the changes are fairly
>> straightforward, so it shouldn't take long. However, I can't guarantee that
>> the new server will do everything the old server did, (or do it the same
>> way).
>>
>> It would be fantastic if a few people could design and contribute test
>> cases so that we can do some regression testing for the server. Ideally a
>> test case should provide:
>>
>> - tiny models to work with (or we may be able to recycle some that
>> already exist)
>> - sample input (json)
>> - expected output (json)
>>
>> Cheers - Uli
>>
>>
>>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
--
Ulrich Germann
Senior Researcher
School of Informatics
University of Edinburgh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151117/3b5f12ea/attachment-0001.html
------------------------------
Message: 3
Date: Tue, 17 Nov 2015 16:43:57 -0500
From: Philipp Koehn <phi@jhu.edu>
Subject: Re: [Moses-support] problem in generating phrase table after
tuning
To: Apurva Joshi <apurvajoshi1992@gmail.com>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CAAFADDCuUN_uD+Gj9Mypgc31azUOTtcXUw2ugeKFeg=2pMv1DQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
the standard pipeline filters the phrase translation table
for tuning and evaluation.
The result of tuning, however, is just the feature weights.
None of the model files should be changed.
Specifically, you should not just use the moses.ini file
in the tuning directory, since this is uses a phrase table
filtered for the tuning set.
In the standard experiment.perl pipeline, the script
$MOSES/scripts/ems/support/substitute-weights.perl
substitutes weights in the original moses.ini with
the tuned weights.
-phi
On Tue, Nov 17, 2015 at 2:17 AM, Apurva Joshi <apurvajoshi1992@gmail.com>
wrote:
> hello ,
>
> initially i trained with corpora containing 7 lac sentnses...i trained
> it..and its giving good translation...
>
> then for tuning i took new small size corpora containing 2k lines ....
>
> now i run tuning with this new processed corpora as input along with my
> moses.ini (generated after training) as input ....then mert-work folder is
> generated with run6.moses.ini ....
>
> along with this ,phrase table.gz and reordering table is also generated in
> mert-work folder...
>
> now problem is ....
>
> 1st problem :
>
> before tuning , size of phrase table is 2.5Gb
>
> after tuning , size of phrase table is 256.5Mb
>
> 2nd problem:
>
> now while running moses, should i use moses.ini(in mert-work/filtered
> folder) OR moses.ini(run6.moses.ini) ...?
>
> i ran moses using both above mentioned moses.ini....
> from both m not getting proper o/p...
> eg
>
> ip = hello
>
> op =
>
> *BEST TRANSLATION: hello|UNK|UNK|UNK *
> before tuning , it was giving me correct translation of hello i.e
>
> op= ?????? (hindi translation of hello)....
>
>
> so whether is it taking memory problem or what ?? plzz help...
>
>
>
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20151117/7ca04e14/attachment.html
------------------------------
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
End of Moses-support Digest, Vol 109, Issue 37
**********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 109, Issue 37"
Post a Comment