How does the Pivoted Cholesky Decomposition implementation differ from Harbrecht et.al. 2012 ? #2067
Replies: 1 comment
-
You could fix this by setting
I don't think that's true?
Most of our numerical methods in GPyTorch use relative errors, not absolute errors. It sounds like the only difference between your implementation and ours is the stopping conditions. If you need strict stopping conditions based on absolute error, then our implementation probably isn't suitable for your needs. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi GPyTorch devs, I am trying to implement the
mBCG
algorithm from the original GPyTorch paper for PyMC. I am currently working on implementing Pivoted Cholesky decomposition and have implemented the one from the Original Harbrecht et.al 2012 paperTo me it seems like the implementation in GPyTorch differs from the original in three places,
max_iter
orrank
instead ofn
max(diag)
instead ofl1_norm(diag)
Are there any other differences ?
I wrote a simple test (with my Pivoted Cholesky implementation in NumPy) and the results differ from GPyTorch. link to the notebook
Any help / pointers would be very helpful. (tagging @gpleiss since he implemented the algorithm on GPyTorch)
Beta Was this translation helpful? Give feedback.
All reactions