Hi,
I can confirm it's not working, if I am not wrong it does not collect
the sparse features. I fixed that in a branch of mine, but the script
has diverged a lot between both branches, so I did not commit.
W dniu 27.04.2015 o 17:07, Hieu Hoang pisze:
i know -continue works ok with dense features. I can't tell you about
sparse features
Hieu Hoang
Researcher
New York University, Abu Dhabi
http://www.hoang.co.uk/hieu
On 27 April 2015 at 19:03, Matthias Huck <[email protected]
<mailto:[email protected]>> wrote:
Hi,
Is there possibly a problem when continuing interrupted tuning
runs with
sparse features?
It seems to me that mert-moses.pl <http://mert-moses.pl> doesn't
add the [weight-file] section
to the run*.moses.ini it creates right after resuming the tuning. That
would imply that no sparse weights are used in the next decoding
iteration.
Am I doing something wrong, or does anyone know a workaround?
Cheers,
Matthias
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
_______________________________________________
Moses-support mailing list
[email protected] <mailto:[email protected]>
http://mailman.mit.edu/mailman/listinfo/moses-support
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support
