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. Problem in web based SMT System using MOSES
(Vishal Goyal (????? ????))
2. EAMT 2014: Call for Papers, deadline March 28 (Philipp Koehn)
3. Problems with moses compilation (Yun Chung)
----------------------------------------------------------------------
Message: 1
Date: Mon, 10 Mar 2014 22:24:05 +0530
From: Vishal Goyal(????? ????) <vishal.pup@gmail.com>
Subject: [Moses-support] Problem in web based SMT System using MOSES
To: moses-support <moses-support@mit.edu>
Message-ID:
<CADAAq5xcSD1XrZb0Ea5sav7cxxuLMwu5LKWUEaYRUBEMtNPQKw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello All,
Greetings.
We have developed SMT Approach based Hindi to Punjabi MT System using
Moses. Now We have hosted on the Linux server and hosted required tool
kits including MOSES etc.
We are facing a problem that When small text is given as input for
translation, it will translate but when it get number of requests for
translations in one go, It gets busy and Only starts doing transliteration
rather than translation...
It has been developed using CGI-Perl and has been installed at
http://tdil-dc.in/hi2pu
Please help us in solving our problem.
Thanks in anticipation...
Ajit- Please remain in contact with replies from the researchers of this
group...
--
*Regards,*
Vishal Goyal,
Ph.D., M.Tech., MCA, M.C.S.D.
Assistant Professor(Stage III) and Placement Coordinator,
Department of Computer Science,
Punjabi University Patiala-147002
[*Online Hindi to Punjabi Machine Translation Tool -*
http://h2p.learnpunjabi.org ]
*[Research Cell: An International Journal of Engineering Sciences,
http://ijoes.vidyapublications.com <http://ijoes.vidyapublications.com>]*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20140310/7a95a05c/attachment-0001.htm
------------------------------
Message: 2
Date: Mon, 10 Mar 2014 16:47:47 -0400
From: Philipp Koehn <pkoehn@inf.ed.ac.uk>
Subject: [Moses-support] EAMT 2014: Call for Papers, deadline March 28
To: "corpora@uib.no" <CORPORA@uib.no>, "moses-support@mit.edu"
<moses-support@MIT.EDU>, mt-list@eamt.org
Message-ID:
<CAAFADDDoVCPHXfYAeywGQ8d4PCASJ60f46ZJu1RLzDqds-xG1g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
EAMT 2014 Call for Papers
Annual Conference of the European Association for Machine Translation
(EAMT2014)
Dubrovnik, Croatia
16-18 June 2014
http://hnk.ffzg.hr/eamt2014/home.html
The European Association for Machine Translation (EAMT) invites
everyone interested in machine translation and translation-related
tools and resources to participate in this conference -- developers,
researchers, users (including professional translators and
translation/localisation managers): anyone who has a stake in the
vision of an information world in which language issues become less
visible to the information consumer. We especially invite researchers
to describe the state of the art and demonstrate their cutting-edge
results and avid MT users to share their experiences.
We expect to receive manuscripts in these three categories:
===========================================================================
(R) Research papers: Long-paper submissions (8 pages) are invited for
reports of significant research results in any aspect of machine
translation and related areas. Such reports should include a
substantial evaluation component. Contributions are welcome on all
topics in the area of Machine Translation or translation-related
technologies, including:
MT methodologies and techniques
Speech translation: speech to text, speech to speech
Translation aids (translation memory, terminology databases, etc.)
Translation environments (workflow, support tools, conversion
tools for lexica, etc.)
Practical MT systems (MT for professionals, MT for multilingual
eCommerce, MT for localization, etc.)
MT in multilingual public service (eGovernment etc.)
MT for the web
MT embedded in other services
MT evaluation techniques and evaluation results
Dictionaries and lexica for MT
Text and speech corpora for MT
Standards in text and lexicon encoding for MT
Human factors in MT and user interfaces
Related multilingual technologies (natural language generation,
information retrieval, text categorization, text summarization,
information extraction, etc.)
Papers should describe original work. They should emphasize completed
work rather than intended work, and should indicate clearly the state
of completion of the reported results. Where appropriate, concrete
evaluation results should be included.
===========================================================================
(U) User studies: Short-paper submissions (2-4 pages) are invited for
reports on users' experiences with MT, be it in small or medium size
business (SMB), enterprise, government, or NGOs. Contributions are
welcome on:
Integrating MT and computer-assisted translation into a
translation production workflow (e.g. transforming terminology
glossaries into MT resources, optimizing TM/MT thresholds, mixing
online and offline tools, using interactive MT, dealing with MT
confidence scores)
Use of MT to improve translation or localization workflows (e.g.
reducing turnaround times, improving translation consistency,
increasing the scope of globalization projects)
Managing change when implementing and using MT (e.g. switching
between multiple MT systems, limiting degradations when updating or
upgrading an MT system)
Implementing open-source MT in the SMB or enterprise (e.g.
strategies to get support, reports on taking pilot results into full
deployment, examples of advance customisation sought and obtained
thanks to the open-source paradigm)
Evaluation of MT in a real-world setting (e.g. error detection
strategies employed, metrics used, productivity or translation quality
gains achieved)
Post-editing strategies and tools (e.g. limitations of traditional
translation quality assurance tools, challenges associated with
post-editing guidelines)
Legal issues associated with MT, especially MT in the cloud (e.g.
copyright, privacy)
Use of MT in social networking or real-time communication (e.g.
enterprise support chat)
Use of MT to process multilingual content for assimilation
purposes (e.g. cross-lingual information retrieval, MT for
e-discovery, MT for spam detection)
Use of standards for MT
Papers should highlight problems and solutions and not merely describe
MT integration process or project settings. Where solutions do not
seem to exist, suggestions for MT researchers and developers should be
clearly emphasized. For user papers produced by academics, we require
co-authorship with the actual users.
(P) Project/Product description: Abstract submissions (1 page) are
invited to report new, interesting:
Tools for machine translation, computer aided translation, and the
like (including commercial products and open source software). The
authors should be ready to present the tools in the form of demos or
posters during the conference.
Research projects related to machine translation. The authors
should be ready to present the projects in the form of posters during
the conference. This follows on from the successful 'project villages'
held at the last two EAMT conferences.
The important dates are:
* Paper submission: March 28, 2014
* Notification to authors: April 18, 2014
* Camera-ready deadline: May 9, 2014
* Conference: June 16-18, 2014
Johann Roturier and Philipp Koehn
on behalf of the EAMT 2014 Organising Committee
http://eamt2014.ffzg.hr/
------------------------------
Message: 3
Date: Tue, 11 Mar 2014 09:25:20 +0100
From: Yun Chung <yunchungtuan@gmail.com>
Subject: [Moses-support] Problems with moses compilation
To: moses-support@mit.edu
Message-ID:
<CAPF6yLGrUxHEhBvkRWLo=YH55VEkR-+1Qw7UszziRokBcNwcmw@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Dear Moses supports,
I am running into an error when compiling Moses (
https://github.com/moses-smt/mosesdecoder/commit/23556697c4e6831bfd0574351717f5a7b79dff77)
with the options "threading=single" and "--static". (x86_64-redhat-linux)
The command I used is:
./bjam threading=single --static --prefix=$MOSES_INSTALLDIR
--install-scripts=$MOSES_SCRIPTS --with-srilm=$SRILM
--with-irstlm=$IRSTLMDIR --with-boost=$BOOSTDIR --with-xmlrpc-c=$XMLRPCDIR
--with-cmph=$CMPHDIR --with-giza=$MOSES_INSTALLDIR/bin --max-kenlm-order=5
--with-tcmalloc --without-libsegfault -j8 -a -q
It was a linking error with "pcqueue_test". The partial error message is
attached. If I remove "threading=single", the compilation finishes without
problems. It seems "-lpthread" could help with this step, but I don't know
how to add such an option to the bjam command. (Adding
"linkflags=-lpthread" alone seems to cause the compilation to freeze.) It
would be great if someone could tell me how to deal with it.
Thank you very much for the help in advance!
Best regards,
Yun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20140311/81db2797/attachment.htm
-------------- next part --------------
gcc.link util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test
"g++" -L"lib" -L"lib64" -Wl,-R -Wl,"lib" -Wl,-R -Wl,"lib64" -Wl,-rpath-link -Wl,"lib" -Wl,-rpath-link -Wl,"lib64" -o "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test" -Wl,--start-group "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/read_compressed.o" "util/double-conversion/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/bignum-dtoa.o" "util/double-conversion/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/bignum.o" "util/double-conversion/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/cached-powers.o" "util/double-conversion/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/diy-fp.o" "util/double-conversion/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/double-conversion.o" "util/double-conversio!
n/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/fast-dtoa.o" "util/double-conversion/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/fixed-dtoa.o" "util/double-conversion/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/strtod.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/bit_packing.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/ersatz_progress.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/exception.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/file.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/file_piece.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/mmap.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/murmur_hash.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/!
runtime-link-static/pool.o" "util/bin/gcc-4.1.2/release/debug-symbols-
on/link-static/runtime-link-static/scoped.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/string_piece.o" "util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/usage.o" -lboost_system -lboost_unit_test_framework -lbz2 -lz -lrt -ldl -lboost_system -Wl,--end-group -g -static
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `semaphore_init': include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:115: undefined reference to `sem_init'
include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:115: undefined reference to `sem_init'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `mutex':
include/boost/thread/pthread/mutex.hpp:39: undefined reference to `pthread_mutex_init'
include/boost/thread/pthread/mutex.hpp:39: undefined reference to `pthread_mutex_init'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `semaphore_wait':
include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:142: undefined reference to `sem_wait'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `~mutex':
include/boost/thread/pthread/mutex.hpp:47: undefined reference to `pthread_mutex_destroy'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `semaphore_destroy':
include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:126: undefined reference to `sem_destroy'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `semaphore_destroy':
util/pcqueue_test.cc:16: undefined reference to `sem_destroy'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `boost::mutex::lock()':
include/boost/thread/pthread/mutex.hpp:52: undefined reference to `pthread_mutex_lock'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `boost::mutex::unlock()':
include/boost/thread/pthread/mutex.hpp:61: undefined reference to `pthread_mutex_unlock'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `semaphore_post':
include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:134: undefined reference to `sem_post'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `semaphore_wait':
include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:142: undefined reference to `sem_wait'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `boost::mutex::lock()':
include/boost/thread/pthread/mutex.hpp:52: undefined reference to `pthread_mutex_lock'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `boost::mutex::unlock()':
include/boost/thread/pthread/mutex.hpp:61: undefined reference to `pthread_mutex_unlock'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `semaphore_post':
include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:134: undefined reference to `sem_post'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `~mutex':
include/boost/thread/pthread/mutex.hpp:47: undefined reference to `pthread_mutex_destroy'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `~mutex':
include/boost/smart_ptr/scoped_array.hpp:68: undefined reference to `pthread_mutex_destroy'
util/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static/pcqueue_test.o: In function `semaphore_destroy':
include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:126: undefined reference to `sem_destroy'
include/boost/interprocess/sync/posix/semaphore_wrapper.hpp:126: undefined reference to `sem_destroy'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale.o): In function `std::locale::_Impl::_M_install_cache(std::locale::facet const*, unsigned long)':
(.text._ZNSt6locale5_Impl16_M_install_cacheEPKNS_5facetEm+0x98): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale.o): In function `std::locale::_Impl::_M_install_cache(std::locale::facet const*, unsigned long)':
(.text._ZNSt6locale5_Impl16_M_install_cacheEPKNS_5facetEm+0xd5): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale.o): In function `std::locale::_Impl::_M_install_cache(std::locale::facet const*, unsigned long)':
(.text._ZNSt6locale5_Impl16_M_install_cacheEPKNS_5facetEm+0x8e): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale_init.o): In function `std::locale::global(std::locale const&)':
(.text._ZNSt6locale6globalERKS_+0x93): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale_init.o): In function `std::locale::global(std::locale const&)':
(.text._ZNSt6locale6globalERKS_+0xd9): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale_init.o): In function `std::locale::global(std::locale const&)':
(.text._ZNSt6locale6globalERKS_+0x125): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale_init.o): In function `std::locale::locale()':
(.text._ZNSt6localeC1Ev+0x7e): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale_init.o): In function `std::locale::locale()':
(.text._ZNSt6localeC1Ev+0x74): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale_init.o): In function `std::locale::locale()':
(.text._ZNSt6localeC2Ev+0x7e): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(locale_init.o): In function `std::locale::locale()':
(.text._ZNSt6localeC2Ev+0x74): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(guard.o): In function `(anonymous namespace)::static_mutex::lock()':
(.text._ZN72_GLOBAL__N_.._.._.._.._libstdc___v3_libsupc___guard.cc_00000000_7CD8311B12static_mutex4lockEv+0x18): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(guard.o): In function `(anonymous namespace)::static_mutex::unlock()':
(.text._ZN72_GLOBAL__N_.._.._.._.._libstdc___v3_libsupc___guard.cc_00000000_7CD8311B12static_mutex6unlockEv+0x18): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(eh_alloc.o): In function `__cxa_allocate_exception':
(.text.__cxa_allocate_exception+0xb6): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(eh_alloc.o): In function `__cxa_allocate_exception':
(.text.__cxa_allocate_exception+0xc7): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(eh_alloc.o): In function `__cxa_free_exception':
(.text.__cxa_free_exception+0x58): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libstdc++.a(eh_alloc.o): In function `__cxa_free_exception':
(.text.__cxa_free_exception+0x78): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libgcc_eh.a(unwind-dw2-fde-glibc.o): In function `__deregister_frame_info_bases':
(.text+0x10bc): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libgcc_eh.a(unwind-dw2-fde-glibc.o): In function `__deregister_frame_info_bases':
(.text+0x10cd): undefined reference to `pthread_mutex_unlock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libgcc_eh.a(unwind-dw2-fde-glibc.o): In function `__register_frame_info_table_bases':
(.text+0x117f): undefined reference to `pthread_mutex_lock'
/usr/lib/gcc/x86_64-redhat-linux/4.1.2/libgcc_eh.a(unwind-dw2-fde-glibc.o): In function `__register_frame_info_bases':
(.text+0x1257): undefined reference to `pthread_mutex_unlock'
collect2: ld returned 1 exit status
...skipped <putil/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static>pcqueue_test.passed for lack of <putil/bin/gcc-4.1.2/release/debug-symbols-on/link-static/runtime-link-static>pcqueue_test...
...failed updating 1 target...
------------------------------
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
End of Moses-support Digest, Vol 89, Issue 21
*********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 89, Issue 21"
Post a Comment