Hi Arefeh, On Fri, 2015-01-23 at 12:03 +0000, Arefeh Kazemi wrote: > > >>Can you try to run the setup from the cluster on your local desktop > system? With the same input, a Moses binary compiled from the same > sources, and the same command to produce the n-best lists? Normally it > should give you the same output. > > > you mean I run the binary file which is produced on the cluster, on my > local pc, without compiling moses again?
If you can use the binary from the cluster, yes, copy it to your desktop system and run that. Your previous mail seemed to indicate that you observe the issue on the cluster only, not on your local machine. Make sure you did not use a different Moses code base first. See if the output is the same on some toy setup. Then try to reproduce the setup from the cluster on your desktop (if the memory requirements allow for that). > > > >>Why would the feature never produce an overall score larger than > 60? > > > > my feature calculate multiply of some probabilities for dependency > structures of a sentence. a sentence with limited max size has limited > number of such dependencies, so I can estimate the maximum value of my > feature. Okay, that makes sense. > > > > >>Also note that you should not use Assign() in your feature functions > any > more (since two weeks ago). > > > I've already seen your post. I just use PlusEquals in my code, as I > understand its not affected by your change, right? No, if you used Assign() before, you've been setting the overall score for the complete derivation so far. With PlusEquals() you're adding deltas. They get accumulated. You need to rewrite your code to compute a delta score just for the current hypothesis expansion. (Typical feature functions compute that kind of score anyway, but maybe yours didn't.) If you used PlusEquals() before already, then you don't have to modify anything. Cheers, Matthias > > > Regards > > > On Friday, January 23, 2015 12:11 AM, Matthias Huck > <mh...@inf.ed.ac.uk> wrote: > > > > Hi Arefeh, > > Can you try to run the setup from the cluster on your local desktop > system? With the same input, a Moses binary compiled from the same > sources, and the same command to produce the n-best lists? Normally it > should give you the same output. > > Why would the feature never produce an overall score larger than 60? > > Also note that you should not use Assign() in your feature functions > any > more (since two weeks ago). > http://comments.gmane.org/gmane.comp.nlp.moses.user/12146 > If you use Assign rather than PlusEquals and you merged with the > recent > master from GitHub on the cluster but not on your desktop machine, > then > something like what you described can have happened. > > Cheers, > Matthias > > > > On Thu, 2015-01-22 at 21:00 +0000, Arefeh Kazemi wrote: > > Hi > > > > > > I've implemented a feature with 4 scores in moses-chart. when I > debug > > the code on my system, every thing is OK and the scores are > calculated > > right, but when I run mert to tune the weights (on a cluster), I get > > wrong scores for my feature in run*.best.100 files. for example my > > feature could have the maximum value of 60 but for some instances I > > get values more than 300. > > > > does anyone know why this happens? > > > > > > Regards > > > > > > > _______________________________________________ > > Moses-support mailing list > > Moses-support@mit.edu > > http://mailman.mit.edu/mailman/listinfo/moses-support > > > > -- > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > > > > > > > > > > _______________________________________________ > Moses-support mailing list > Moses-support@mit.edu > http://mailman.mit.edu/mailman/listinfo/moses-support > -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support
