Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting non optimized errors in the take_step function #2

Open
NnannaOmoke opened this issue Jul 10, 2024 · 0 comments
Open

Setting non optimized errors in the take_step function #2

NnannaOmoke opened this issue Jul 10, 2024 · 0 comments

Comments

@NnannaOmoke
Copy link

Hello there, Mr. John! I'm sorry this is coming so long after you've published your work, but I noticed some things I'm having problems understanding. In Mr. Platt's paper, in the take_step function, he gives a line to updating the error cache, which I assume is usually done by reapplying the decision function to the two support vectors at those indices and getting the error. Instead, you do none of that and actually update the error cache of every support vector excepting the ones that have just taken steps. Is there some reasoning for this? I would really appreciate your input, as I'm trying to write a translation of Mr. Platt's paper in Rust, and I have used your notebook for some guidance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant