Sir,
As you mentioned adding "-tt" while running decoder for input gives us
feature score for each pair, also a non-zero value for a translation model
(given that there are multiple phrase-table) gives us indication from which
phrase-table translation candidate was used. Sir I'm making a system
Hi,
yes, that is correct. If there are non-zero valued scores listed with a
translation model feature, then this translation model was used for the
phrase pair.
-phi
On Wed, Jul 29, 2015 at 7:57 PM, Saumitra Yadav yadav.saumitr...@gmail.com
wrote:
Sir,
Thank you for that option , it really
Hi,
when you call the decoder with the option -tt then you get for
each phrase pairs a list of all feature scores. You can use this
to track down which phrase table was used for each phrase
translation.
-phi
On Wed, Jul 29, 2015 at 10:59 AM, Hieu Hoang hieuho...@gmail.com wrote:
good
Sir,
Thank you for that option , it really helped. I just wanted to know if I'm
analysing it correctly
For initial analysis m just finding how many times which phrase tables were
called , so in attached file (formatted just for easy readability ) please
find the output of one sentence , is it
Sir,
Is there a command or argument which can tell, which phrase in output is
taken from which phrase-table (incase we have multiple phrase-tables )?
Regards,
Saumitra Yadav
M.Tech.
Department Of Computer Science And Technology
Goa University
On Sun, Jul 26, 2015 at 11:49 AM, Hieu Hoang
good question. no. You can try write it yourself.
in the TargetPhrase class, there is a method
GetContainer()
which points to the phrase-table that a particular rule comes from. You
can use this.
On 29/07/2015 18:51, Saumitra Yadav wrote:
Sir,
Is there a command or argument which can
since you have 3 phrase-tables, you may have to have 3 entries in the
[decoding-graph-backoff] section, eg
[decoding-graph-backoff]
0
3
3
Hieu Hoang
Researcher
New York University, Abu Dhabi
http://www.hoang.co.uk/hieu
On 25 July 2015 at 20:23, Saumitra Yadav yadav.saumitr...@gmail.com
Sir,
Please find attached , moses.ini file i used and command used
was ~/Decoder/mosesdecoder/bin/moses -f moses.ini
Regards,
Saumitra Yadav
M.Tech.
Department Of Computer Science And Technology
Goa University
On Sat, Jul 25, 2015 at 9:21 PM, Hieu Hoang hieuho...@gmail.com wrote:
can you
can you please send me the moses.ini file that you used, that cause the
segfault. And send me the exact command you typed
On 24/07/2015 14:40, Saumitra Yadav wrote:
But sir when i did that there was *segmentation fault* while loading
first phrase-table, one walk around i got was giving
But sir when i did that there was * segmentation fault* while loading first
phrase-table, one walk around i got was giving phrase-table uncompressed to
decoder.
Regards,
Saumitra Yadav
M.Tech.
Department Of Computer Science And Technology
Goa University
On Thu, Jul 23, 2015 at 8:06 PM, Hieu
i think you have to swap the phrase tables around. The decoder always
looks at the 1st phrase-table, then backoff to the 2nd if nothing is found
On 22/07/2015 16:59, Saumitra Yadav wrote:
Sir/Ma'am,
I'm trying to use multiple phrase tables for translation in Moses
decoder, with preference to
Sir/Ma'am,
I'm trying to use multiple phrase tables for translation in Moses decoder,
with preference to 1st phrase-table, but was getting a segmentation fault
while loading 1st phrase table, so just switched the positions of
phrase-tables in moses configuration file and it was working , now the
Okay fine. So the backoff apparently works even though the code seemed
to suggest something different to me. Got it wrong I guess.
Maybe there's some other problem in my setup, for instance with factored
generation steps.
Thanks anyway for looking into this.
On Sun, 2015-04-19 at 12:52 +0400,
Hi Hieu,
It seems that [decoding-graph-backoff] doesn't quite behave like last
year any more. Can you briefly explain how its behaviour has changed,
i.e. what it did before and what it does now? Can you please also let me
know whether there's a way to reproduce the old behaviour via
configuration
Didn't know it has changed. How should it behave and how does it actually
behave?
On 16 Apr 2015 21:04, Matthias Huck mh...@inf.ed.ac.uk wrote:
Hi Hieu,
It seems that [decoding-graph-backoff] doesn't quite behave like last
year any more. Can you briefly explain how its behaviour has changed,
ah yes, I thought the backoff was doing the opposite to what it's
supposed to do so I changed the comparison around. I checked that it
backed off, but i didn't run it through tuning.
it may still be wrong, or there may be strange interaction with the tuning.
On 16/04/2015 22:16, Matthias Huck
Well, what's that business mentioned in your mail from January (quoted
below), with the backoff being broken, then being broken more, then
possibly been fixed - or not?
https://github.com/moses-smt/mosesdecoder/commit/44fec57c535db2df73ccbb1628d8143a9c728c19
I set up a system that was supposed
Hey,
I have used the multiple decoding paths with and without the backoff
procedures.
I once experimented with using a French-English phrase table as a backoff
table when translating from Creole (Mauritian) to English (I had a small
Creole-English corpus).
I found that I got a decent improvement
Hm, we have been using it at WIPO, but I have to admit I never checked
it _actually_ does anything useful. We sorta believe it does.
W dniu 09.01.2015 o 16:08, Hieu Hoang pisze:
Hi All
Does anyone use this functionality in Moses when you have multiple
phrase-tables?
From the code, it
From the git history, I think it was slightly broken, then I broke it even
more in May 2014.
https://github.com/moses-smt/mosesdecoder/commit/44fec57c535db2df73ccbb1628d8143a9c728c19
It was
endPos-startPos+1 = backoff
then
endPos-startPos+1 = backoff
I think it should be
endPos-startPos+1
Hi All
Does anyone use this functionality in Moses when you have multiple
phrase-tables?
From the code, it doesn't look like it works as described in
http://www.statmt.org/moses/?n=Moses.AdvancedFeatures
Maybe I'm missing something
--
Hieu Hoang
Research Associate
University of Edinburgh
21 matches
Mail list logo
