Closed MSRudolph closed 1 year ago
@MSRudolph Is there a test case you could add to catch this issue in future if someone makes a change which will break it again?
Hi @anilagca, thanks for your release. However this PR contains a fix that we should release ASAP. @mstechly We could write a test where we know the Hessian analytically. I can work on that soon.
Hey @MSRudolph ! I added some preliminary function for testing.
Hey @MSRudolph ! I added some preliminary function for testing.
- If you could see if this makes sense as a test case and if not, edit it so it does, that would be great. I understand that calculating things at (0,0) might be too much of a trivial/special case.
- I noticed that the approximate Hessian calculation has terrible precision. Did you know about it / is it something that we should be concerned about?
Thanks for picking this back up, @mstechly.
@MSRudolph I've update the tests and added a cost function and an analytical Hessian. I made the function a bit more non-trivial. If you say this looks good, I think we can merge. @max-radin – something seems to be wrong with CICD, or perhaps you need to trigger it manually? I don't know, but please take a look.
This looks great, thanks :)
Reworking a change from this PR. After comparing with automatic differentiation hessians, the SPSA hessian implementation was correct, but the full hessian implementation had a doubled diagonal.