On 5/24/11 10:57 PM, Jason Baldridge wrote:
I think there are actually some problems to fix with the Perceptron that I
will get to on Thursday or so after I get a few major things off my plate.
Will explain then.
Thanks, we should also perform the fixes/refactoring to eliminate the
duplicate
code in the perceptron sequence trainer like you did in the non-sequence
perceptron
trainer.
It seems also that the stop criteria in the non-sequence perceptron trainer
does not really work, I did a few test with a very high iteration count,
and the accuracy
just started jumping back and forth between two values.
Beside that I already fixed a performance bug in the sequence perceptron
trainer, see OPENNLP-185.
Jörn
