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

Add normalization to HessianDiagonalAggregator #184

Open
ashelkovnykov opened this issue Oct 19, 2016 · 6 comments
Open

Add normalization to HessianDiagonalAggregator #184

ashelkovnykov opened this issue Oct 19, 2016 · 6 comments
Assignees

Comments

@ashelkovnykov
Copy link
Contributor

From a comment by @XianXing on PR #131:

"The computation and approximation for Hessian diagonal was designed and implemented independent of Photon's normalization, because previously we didn't enable normalization for GLMix.

But it will be helpful if we take the normalization into account as well here for Hessian diagonal, in order to make it consistent with the rest of code."

@fastier-li fastier-li self-assigned this Mar 16, 2017
@fastier-li
Copy link
Member

fastier-li commented Mar 16, 2017

Assigning to myself as I am working on normalization right now.

@XianXing - can you review this PR, and let me know if it is actually incorrect from an algorithm point of view, if we don't normalize the Hessian diagonal when normalization is turned on?

@XianXing
Copy link
Contributor

The PR looks good to me in general, but I haven't got a chance to look at it carefully.

Can you have other folks to take a look at the PR as well, for example @ankans or Ajith, so that you guys get the help needed and won't get blocked?

@fastier-li
Copy link
Member

Yes, we are having it reviewed by Ankan too. What it does is only setup normalization contexts in GAME and then call the same machinery as photon. If it was correct in photon after the normalization contexts were set, it should be correct in GAME, that hasn't changed at all. What happens to the Hessian diagonal in photon, in case of normalization?

@fastier-li
Copy link
Member

@XianXing - what is the real impact of not having this? Is it correctness? Is it performance? Is it required to compute variances correctly?

@XianXing
Copy link
Contributor

Correctness. The impact would be downstream applications. For example, I don't know if we are using the estimated variance for multi-armed bandit and explore-exploit tradeoffs at LNKD or not, but based on our experience the quality of estimated variance would have direct impact on those applications (can't be more specific than this without getting into trouble :) ).

Having said that, if there are no such use cases at LNKD, please feel free to de-prioritize it.

@pogil @beechung

@fastier-li
Copy link
Member

fastier-li commented Mar 16, 2017

So, it is correctness of variances, only. The correctness of coefficient means themselves does not depend on that, right?

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

3 participants