Many thanks to everybody for your feedback. I'm glad I now have an explanation
for the reported behaviour.
James
___
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
> Sent: Friday, June 19, 2015 8:25 PM
> To: moses-support@mit.edu
> Subject: Re: [Moses-support] Major bug found in Moses
>
> [sorry for the garbled message before]
>
> you are right. The idea is pretty obvious. It roughly corresponds to
> 'Histogram pruning' in thi
ng, as I think it does for everyone else on the list. It also
includes language modeling, by the way.
- John Burger
MITRE
> James
>
>
> From: John D. Burger
> Sent: Wednesday, June 24, 2015 6:03 PM
> To: Read, James C
> Cc: m
tz
> Sent: Wednesday, June 24, 2015 5:56 PM
> To: Read, James C
> Cc: Rico Sennrich; moses-support@mit.edu
> Subject: Re: [Moses-support] Major bug found in Moses
>
>
> On Wed, Jun 24, 2015 at 9:05 AM, Read, James C wrote:
> As the title of this thread makes clear the
Original Message-
From: on behalf of "Read, James C"
Date: Wednesday 24 June 2015 17:29
To: "John D. Burger"
Cc: "moses-support@mit.edu"
Subject: Re: [Moses-support] Major bug found in Moses
>Please allow me to give a synthesis of my understanding of your respon
d appreciate it.
Thanks.
-Original Message-
From: moses-support-boun...@mit.edu [mailto:moses-support-boun...@mit.edu] On
Behalf Of Read, James C
Sent: Wednesday, June 24, 2015 10:29 AM
To: John D. Burger
Cc: moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
try really hard to design a system that
> performed so poorly.
>
> James
>
>
> From: amittai axelrod
> Sent: Wednesday, June 24, 2015 5:36 PM
> To: Read, James C; Lane Schwartz
> Cc: moses-support@mit.edu; Philipp Koehn
> Subject: Re:
Sent: Wednesday, June 24, 2015 5:56 PM
To: Read, James C
Cc: Rico Sennrich; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
On Wed, Jun 24, 2015 at 9:05 AM, Read, James C
mailto:jcr...@essex.ac.uk>> wrote:
As the title of this thread makes clear the purp
em that
> performed so poorly.
>
> James
>
>
> From: amittai axelrod
> Sent: Wednesday, June 24, 2015 5:36 PM
> To: Read, James C; Lane Schwartz
> Cc: moses-support@mit.edu; Philipp Koehn
> Subject: Re: [Moses-support] Major
On Wed, Jun 24, 2015 at 9:05 AM, Read, James C wrote:
> As the title of this thread makes clear the purpose of reporting the bug
> was not to invite a discussion about conclusions made in my draft paper.
> Clearly a community that builds its career around research in SMT is
> unlikely to agree w
From: amittai axelrod
Sent: Wednesday, June 24, 2015 5:36 PM
To: Read, James C; Lane Schwartz
Cc: moses-support@mit.edu; Philipp Koehn
Subject: Re: [Moses-support] Major bug found in Moses
what *i* would do is tune my systems.
~amittai
On 6/24/15 09:15, Read, James C wrote:
> Thank you for
> James
>
>
> From: amittai axelrod
> Sent: Friday, June 19, 2015 7:52 PM
> To: Read, James C; Lane Schwartz
> Cc: moses-support@mit.edu; Philipp Koehn
> Subject: Re: [Moses-support] Major bug found in Moses
>
> if we don't
: Lane Schwartz
Sent: Wednesday, June 24, 2015 4:43 PM
To: Read, James C
Cc: Rico Sennrich; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
On Wed, Jun 24, 2015 at 8:11 AM, Read, James C
mailto:jcr...@essex.ac.uk>> wrote:
Other than that it seems painfully clea
On Wed, Jun 24, 2015 at 8:11 AM, Read, James C wrote:
>
>
> Other than that it seems painfully clear that the point I meant to make
> has not been understood entirely. If the default behaviour produces BLEU
> scores considerably lower than merely selecting the most likely translation
> of each phr
support@mit.edu; Philipp Koehn
Subject: Re: [Moses-support] Major bug found in Moses
if we don't understand the problem, how can we possibly fix it?
all the relevant code is open source. go for it!
~amittai
On 6/19/15 12:49, Read, James C wrote:
> So, all I did was filter out the less likely ph
2015 8:25 PM
To: moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
[sorry for the garbled message before]
you are right. The idea is pretty obvious. It roughly corresponds to
'Histogram pruning' in this paper:
Zens, R., Stanton, D., Xu, P. (2012). A Syst
support@mit.edu; Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
Hi James,
Well, it's pretty straightforward: The decoder's job is to find the
hypothesis with the maximum model score. That's why everybody builds
models which assign high model score to high-quali
all we need to do to get a best paper at ACL?
James
From: Lane Schwartz
Sent: Friday, June 19, 2015 7:40 PM
To: Read, James C
Cc: Philipp Koehn; Burger, John D.; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
On Fri, Jun 19, 2015
/watch?v=CHDDNnRm-g8
>
> O.
>
> - Original Message -
>> From: "Marcin Junczys-Dowmunt"
>> To: moses-support@mit.edu
>> Sent: Friday, 19 June, 2015 19:21:45
>> Subject: Re: [Moses-support] Major bug found in Moses
>> On that interesting id
45
> Subject: Re: [Moses-support] Major bug found in Moses
> On that interesting idea that moses should be naturally good at
> translating things, just for general considerations.
>
> Since some said this thread has educational value I would like to share
> something that might
to get a best paper at ACL?
>
>
> James
>
>
> --
> *From:* Lane Schwartz >
> *Sent:* Friday, June 19, 2015 7:40 PM
> *To:* Read, James C
> *Cc:* Philipp Koehn; Burger, John D.; moses-support@mit.edu
>
> *Subject:* Re: [Moses-support] Majo
I like the idea very much. I would need to discuss this with my
collegues, but I guess we can publish recipes for the MT engines we use
in production at WIPO and the UN. They are modelled after some of your
WMT systems, but tuned for speed and small size.
On 20.06.2015 15:42, Adam Lopez wrote:
>
> Can and
> should we make a wider effort to facilitate the reproduction of systems
> by disseminating settings or configuration files? This dissemination is
> partially done by system description papers, but they cannot cover all
> settings [this would make for a very boring paper]. I put some e
On 19/06/15 19:21, Marcin Junczys-Dowmunt wrote:
> So, if anything, Moses is just a very flexible text-rewriting tool.
> Tuning (and data) turns into a translator, GEC tool, POS-tagger,
> Chunker, Semantic Tagger etc.
that's a good point, and the basis of some criticism that can be
levelled at the
design a system which searches for HIGH QUALITY
> TRANSLATION.
>
> James
>
>
> From: Matthias Huck
> Sent: Friday, June 19, 2015 5:08 PM
> To: Read, James C
> Cc: Hieu Hoang; moses-support@mit.edu; Arnold, Doug
> Subject: Re: [Moses-
Ah OK, I misunderstood, I thought you were talking about more advanced
pruning techniques compared to the significance method from Johnson et
al. while you only referred to the 30-best variant.
Cheers,
Marcin
On 19.06.2015 19:35, Rico Sennrich wrote:
> Marcin Junczys-Dowmunt writes:
>
>> Hi Ric
Marcin Junczys-Dowmunt writes:
>
> Hi Rico,
> since you are at it, some pointers to the more advanced pruning
> techniques that do perform better, please :)
>
> On 19.06.2015 19:25, Rico Sennrich wrote:
> > [sorry for the garbled message before]
> >
> > you are right. The idea is pretty obviou
Hi Rico,
since you are at it, some pointers to the more advanced pruning
techniques that do perform better, please :)
On 19.06.2015 19:25, Rico Sennrich wrote:
> [sorry for the garbled message before]
>
> you are right. The idea is pretty obvious. It roughly corresponds to
> 'Histogram pruning' i
[sorry for the garbled message before]
you are right. The idea is pretty obvious. It roughly corresponds to
'Histogram pruning' in this paper:
Zens, R., Stanton, D., Xu, P. (2012). A Systematic Comparison of Phrase
Table Pruning Technique. In Proceedings of the 2012 Joint Conference on
Empiric
Read, James C writes:
> So, all I did was filter out the less likely phrase pairs and the BLEU
score shot up. Was that such a stroke of genius? Was that not blindingly
obvious?
you are right. The idea is pretty obvious. It roughly corresponds to
'Histogram pruning' in this paper:
Zens, R., Sta
On that interesting idea that moses should be naturally good at
translating things, just for general considerations.
Since some said this thread has educational value I would like to share
something that might not be obvious due to the SMT-biased posts here.
Moses is also the _leading_ tool for
--
> *From:* Lane Schwartz
> *Sent:* Friday, June 19, 2015 7:40 PM
> *To:* Read, James C
> *Cc:* Philipp Koehn; Burger, John D.; moses-support@mit.edu
> *Subject:* Re: [Moses-support] Major bug found in Moses
> On Fri, Jun 19, 2015 at 11:28 AM, Read, James C <mailto:
P.S. Have a good weekend everybody. Be back in action in a couple of days.
James
From: Read, James C
Sent: Friday, June 19, 2015 7:49 PM
To: Lane Schwartz
Cc: Philipp Koehn; Burger, John D.; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in
?
James
From: Lane Schwartz
Sent: Friday, June 19, 2015 7:40 PM
To: Read, James C
Cc: Philipp Koehn; Burger, John D.; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
On Fri, Jun 19, 2015 at 11:28 AM, Read, James C
mailto:jcr
On Fri, Jun 19, 2015 at 11:28 AM, Read, James C wrote:
What I take issue with is the en-masse denial that there is a problem with
> the system if it behaves in such a way with no LM + no pruning and/or
> tuning.
>
There is no mass denial taking place.
Regardless of whether or not you tune, the
, June 19, 2015 6:10 PM
To: Read, James C
Cc: Philipp Koehn; Burger, John D.; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
James,
1) Acknowledging that the search algorithm performs poorly with no LM, tuning
or pruning despite the fact the search space clearly contains
deal with this level of denial.
James
From: amittai axelrod
Sent: Friday, June 19, 2015 5:33 PM
To: Read, James C; Lane Schwartz
Cc: moses-support@mit.edu; Philipp Koehn
Subject: Re: [Moses-support] Major bug found in Moses
* "[i'm] the guy that s
James,
> 1) Acknowledging that the search algorithm performs poorly with no LM,
> tuning or pruning despite the fact the search space clearly contains high
> quality translations
>
Yes. We all acknowledge this. If you have a better technique, that's great.
Show that it's better. Your paper does no
That's actually presentation-worthy material :) I have to note that down
somewhere.
W dniu 2015-06-19 16:23, amittai axelrod napisał(a):
> speaking of cobbling together a good translation from imperfect parts:
>
> google:
>
> A motorist heard on the radio the announcement: "Caution Caution
> *Sent:* Friday, June 19, 2015 5:04 PM
> *To:* Read, James C
> *Cc:* Philipp Koehn; Burger, John D.; moses-support@mit.edu
> *Subject:* Re: [Moses-support] Major bug found in Moses
> James,
>
> You may see the techniques that exist as outdated, wrong-headed, and
> inefficient
;>
>>
>>
>> ------------------------
>> *From:* Lane Schwartz
>> *Sent:* Friday, June 19, 2015 5:04 PM
>> *To:* Read, James C
>> *Cc:* Philipp Koehn; Burger, John D.; moses-support@mit.edu
>> *Subject:*
4 PM
> TO: Read, James C
> CC: Philipp Koehn; Burger, John D.; moses-support@mit.edu
> SUBJECT: Re: [Moses-support] Major bug found in Moses
>
> James,
>
> You may see the techniques that exist as outdated, wrong-headed, and
> inefficient. You have the right to hold th
Huck
Sent: Friday, June 19, 2015 5:08 PM
To: Read, James C
Cc: Hieu Hoang; moses-support@mit.edu; Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
Hi James,
Yes, he just said that.
The decoder's job is to find the hypothesis with the maximum model
score. That's one
nging my head against a brick wall. I have no other preferred past times.
James
From: Lane Schwartz
Sent: Friday, June 19, 2015 5:04 PM
To: Read, James C
Cc: Philipp Koehn; Burger, John D.; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in
___
> From: Hieu Hoang
> Sent: Wednesday, June 17, 2015 9:00 PM
> To: Read, James C
> Cc: Kenneth Heafield; moses-support@mit.edu; Arnold, Doug
> Subject: Re: [Moses-support] Major bug found in Moses
>
> the decoder's job is NOT to find the high quality translation
o the answer with
> simple logic and low computational requirements?
>
>
> BE HONEST!
>
>
> James
>
>
> --
> *From:* moses-support-boun...@mit.edu on
> behalf of Philipp Koehn
> *Sent:* Thursday, June 18, 2015 9:39 PM
> *T
putational requirements?
BE HONEST!
James
From: moses-support-boun...@mit.edu on behalf
of Philipp Koehn
Sent: Thursday, June 18, 2015 9:39 PM
To: Burger, John D.
Cc: moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
Hi,
I am great f
half
of Burger, John D.
Sent: Thursday, June 18, 2015 6:32 PM
To: moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
On Jun 17, 2015, at 11:54, Read, James C wrote:
> The question remains why isn't the system capable of finding the most likely
> translations w
: [Moses-support] Major bug found in Moses
James,
The underlying questions that you appear to be posing are these: When the
search space is simplified by decoding without a language model, to what extent
is the decoder able to identify hypotheses that have the best model score?
Second, does
oug
Subject: Re: [Moses-support] Major bug found in Moses
the decoder's job is NOT to find the high quality translation (as measured by
bleu). It's job is to find translations with high model score.
you need the tuning to make sure high quality translation correlates with high
model score
James
From: amittai axelrod
Sent: Wednesday, June 17, 2015 9:03 PM
To: Read, James C; Hieu Hoang; Kenneth Heafield; moses-support@mit.edu
Cc: Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
this is a little hard to follow. "naturally
if (scalar @columns < 4)
> > {
> > die "ERROR: input file is not a well formatted phrase
> table. A phrase table must have at least four colums each column separated
> by |||\n";
> > }
> >
> > # get the probability and check it is less tha
s each column separated by |||\n";
> }
>
> # get the probability and check it is less than the threshold
> my @scores = split /\s+/, $columns[2];
> if ($scores[3] > $min)
> {
> print FILTEREDTABLE $line."\n&q
courage you to
> advance your new system without trying to fix one that's not broken.
>
> Tom
>
>
> > Date: Wed, 17 Jun 2015 15:48:14 +
> > From: "Read, James C"
> > Subject: Re: [Moses-support] Major bug found in Moses
> > To: Marcin Junczys-D
Seconding the message from Tom Hoar - this is the most educational
exchange I have seen on the list in years (and a nice change from the
'Moses won't compile' messages!) Thank you for the detailed responses.
Julian
---
Julian Myerscough
Quality Assurance Manager - L
I just wanted to chip in a couple of cents from my side.
First, I agree with Tom: my most sincere admiration for the patience you
all have evidenced when answering in this thread. It is certainly not easy
to keep calm when someone is saying that all your work in the last 10
years is wrong.
S
e of both the challenge and the status quo.
So, although I can not "admit the system is broke," I encourage you to
advance your new system without trying to fix one that's not broken.
Tom
> Date: Wed, 17 Jun 2015 15:48:14 +
> From: "Read, James C"
> Sub
t the system is broke and get around to fixing it?
>
> James
>
> --
> *From:* Marcin Junczys-Dowmunt
> *Sent:* Wednesday, June 17, 2015 5:29 PM
>
> *To:* Read, James C
> *Cc:* Arnold, Doug; moses-support@mit.edu
> *Subject:* Re: [Moses-support] Major
n convinced that this is undersirable behaviour and therefore a bug.
>
> James
>
>
> From: Marcin Junczys-Dowmunt
> Sent: Wednesday, June 17, 2015 5:12 PM
> To: Read, James C
> Cc: Arnold, Doug; moses-support@mit.edu
> Subject: Re: [Moses-support] Major bug found in Mo
June 17, 2015 8:34 PM
> To: Read, James C; Kenneth Heafield; moses-support@mit.edu
> Cc: Arnold, Doug
> Subject: Re: [Moses-support] Major bug found in Moses
>
> 4 BLEU is nothing to sniff at :) I was answering Ken's tangent aspersion
> that LM are needed for tuning.
>
&
s-support-boun...@mit.edu on
> behalf of Kenneth Heafield
> Sent: Wednesday, June 17, 2015 7:13 PM
> To: moses-support@mit.edu
> Subject: Re: [Moses-support] Major bug found in Moses
>
> I'll bite.
>
> The moses.ini files ship with bogus feature weights. One is requi
nold, Doug; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
To paint you a picture:
Imagine you have a rat in a labyrinth (the labyrinth is the TM and the search
space). That rat is quite good at finding the center of that labyrinth. Now you
somehow disable that rat&
__
> From: Hieu Hoang
> Sent: Wednesday, June 17, 2015 8:34 PM
> To: Read, James C; Kenneth Heafield; moses-support@mit.edu
> Cc: Arnold, Doug
> Subject: Re: [Moses-support] Major bug found in Moses
>
> 4 BLEU is nothing to sniff at :) I was answering Ken&
y would that rank
> on your desirable qualities of a TM list?
>
> James
>
>
> From: amittai axelrod
> Sent: Wednesday, June 17, 2015 8:20 PM
> To: Read, James C; Hieu Hoang; Kenneth Heafield; moses-support@mit.edu
> Cc: Arnold, Doug
>
Wednesday, June 17, 2015 8:34 PM
To: Read, James C; Kenneth Heafield; moses-support@mit.edu
Cc: Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
4 BLEU is nothing to sniff at :) I was answering Ken's tangent aspersion
that LM are needed for tuning.
I have some sympathy
Heafield; moses-support@mit.edu
Cc: Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
hi --
you might not be aware, but your emails sound almost belligerently
confrontational. i can see how you would be frustrated, but starting a
conversation with "i have found a major bug
eth Heafield; moses-support@mit.edu
> Subject: Re: [Moses-support] Major bug found in Moses
>
> On 17/06/2015 20:13, Kenneth Heafield wrote:
>> I'll bite.
>>
>> The moses.ini files ship with bogus feature weights. One is required to
>> tune the system to disc
ntributing all that much then does it?
>
> James
>
>
> From: moses-support-boun...@mit.edu on behalf
> of Hieu Hoang
> Sent: Wednesday, June 17, 2015 7:35 PM
> To: Kenneth Heafield; moses-support@mit.edu
> Subject: Re: [Moses-support] Major bug found in Mos
PM
To: moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
I'll bite.
The moses.ini files ship with bogus feature weights. One is required to
tune the system to discover good weights for their system. You did not
tune. The results of an untuned system are meaningles
No.
James
From: Lane Schwartz
Sent: Wednesday, June 17, 2015 7:58 PM
To: Read, James C
Cc: Hieu Hoang; Kenneth Heafield; moses-support@mit.edu; Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
James,
Did you run any optimizer? MERT, MIRA
You would expect an improvement of 37 BLEU points?
James
From: Marcin Junczys-Dowmunt
Sent: Wednesday, June 17, 2015 4:32 PM
To: Read, James C
Cc: Moses-support@mit.edu; Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
Hi James,
there are
..@mit.edu on
> behalf of Hieu Hoang
> Sent: Wednesday, June 17, 2015 7:35 PM
> To: Kenneth Heafield; moses-support@mit.edu
> Subject: Re: [Moses-support] Major bug found in Moses
>
> On 17/06/2015 20:13, Kenneth Heafield wrote:
> > I'll bite.
> >
> > The m
expect this to give poor results if the TM is well trained?
>> Surely the results of my filtering experiments provve otherwise.
>>
>> James
>>
>> ________
>> From: moses-support-boun...@mit.edu on
>> behalf of Rico Sennrich
>> Sent: Wednesday, June
t this to give poor results if the TM is well trained?
>> Surely the results of my filtering experiments provve otherwise.
>>
>> James
>>
>>
>> From: moses-support-boun...@mit.edu on
>> behalf of Rico Sennrich
>> Sent: Wednesday, June 17, 2015 5:32
heck it is less than the threshold
my @scores = split /\s+/, $columns[2];
if ($scores[3] > $min)
{
print FILTEREDTABLE $line."\n";;
}
}
____
From: moses-support-boun...@mit.edu on behalf
of Rico Sennrich
Sen
Read, James C writes:
>
> Actually the approximation I expect to be:
>
> p(e|f)=p(f|e)
>
> Why would you expect this to give poor results if the TM is well trained?
Surely the results of my filtering
> experiments provve otherwise.
>
> James
I recommend you read the following:
https://en.wik
d?
> Surely the results of my filtering experiments provve otherwise.
>
> James
>
>
> From: moses-support-boun...@mit.edu on behalf
> of Rico Sennrich
> Sent: Wednesday, June 17, 2015 5:32 PM
> To: moses-support@mit.edu
> Subject:
Rico Sennrich
Sent: Wednesday, June 17, 2015 5:32 PM
To: moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
Read, James C writes:
> I have been unable to find a logical explanation for this behaviour other
than to conclude that there must be some kind of bug in Mo
e threshold
my @scores = split /\s+/, $columns[2];
if ($scores[3] > $min)
{
print FILTEREDTABLE $line."\n";;
}
}
________
From: Matt Post
Sent: Wednesday, June 17, 2015 5:25 PM
To: Read, James C
Cc: Marc
17, 2015 5:23 PM
To: Read, James C; Marcin Junczys-Dowmunt
Cc: Moses-support@mit.edu; Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
Hi,
BLEU scores don't mean much, unless you know what the translations look like.
Marcin's explanation sounds very plausible.
How d
Read, James C writes:
> I have been unable to find a logical explanation for this behaviour other
than to conclude that there must be some kind of bug in Moses which causes a
TM only run of Moses to perform poorly in finding the most likely
translations according to the TM when
> there are less
---
>
> FROM: Marcin Junczys-Dowmunt
> SENT: Wednesday, June 17, 2015 5:12 PM
> TO: Read, James C
> CC: Arnold, Doug; moses-support@mit.edu
> SUBJECT: Re: [Moses-support] Major bug found in Moses
>
> Hi James
>
> No, not at all. I would say that is
_
>From: Read, James C
>Sent: Wednesday, June 17, 2015 4:56 PM
>To: Marcin Junczys-Dowmunt
>Cc: Moses-support@mit.edu; Arnold, Doug
>Subject: Re: [Moses-support] Major bug found in Moses
>
>
>You would expect an improvement of 37 BLEU points?
>
>
>James
>
>
>
From: Marcin Junczys-Dowmunt
Sent: Wednesday, June 17, 2015 5:12 PM
To: Read, James C
Cc: Arnold, Doug; moses-support@mit.edu
Subject: Re: [Moses-support] Major bug found in Moses
Hi James
No, not at all. I would say that is expected behaviour. It's how search spaces
and optimization
pisał(a):
>
> You would expect an improvement of 37 BLEU points?
>
> James
>
> -
>
> FROM: Marcin Junczys-Dowmunt
> SENT: Wednesday, June 17, 2015 4:32 PM
> TO: Read, James C
> CC: Moses-support@mit.edu; Arnold, Doug
> SUBJECT:
Hi James,
there are many more factors involved than just probability, for instance
word penalties, phrase penalities etc. To be able to validate your own
claim you would need to set weights for all those non-probabilities to
zero. Otherwise there is no hope that moses will produce anything
sim
Junczys-Dowmunt
Cc: Moses-support@mit.edu; Arnold, Doug
Subject: Re: [Moses-support] Major bug found in Moses
You would expect an improvement of 37 BLEU points?
James
From: Marcin Junczys-Dowmunt
Sent: Wednesday, June 17, 2015 4:32 PM
To: Read, James C
Cc: Moses
Hi all,
I tried unsuccessfully to publish experiments showing this bug in Moses
behaviour. As a result I have lost interest in attempting to have my work
published. Nonetheless I think you all should be aware of an anomaly in Moses'
behaviour which I have thoroughly exposed and should be easy
88 matches
Mail list logo
