Replies: 1 comment
-
@m-julian as of the 1.7.0 release, the gpytorch periodic kernel supports ARD. See #1919. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I tried implementing a periodic kernel that supports ARD, where every input dimension can have its own period length and lengthscale. Everything seems to be working fine and the tests produce the same results (see below). I was wondering if something like this would be useful to have in gpytorch, as the current
PeriodicKernel
does not fully support multi-dimensional input (does not support different lengthscale for each dimension). I do have a couple of questions below, and would appreciate any comments/feedback on the implementation. Let me know if I should make a separate post for the questions because this post did get quite long.Questions:
PeriodicKernel
instances and change the active dimension for each one, but then it becomes a bit tedious to set parameters for separate dimensions (I didn't really find an easy way to set hyperparameter values for a more complex kernel composition).RuntimeError: The expected shape of the kernel was torch.Size([3, 2, 5, 5]), but got torch.Size([3, 5, 5]). This is likely a bug in GPyTorch.
ingpytorch/lazy/lazy_evaluated_kernel_tensor.py
. Obviously caused by my implementation, but I can remove this by usinggpytroch.settings.debug(False)
. Could I change my implementation to go around this without having to turn off debugging?n_dim x n_data_x1, n_data_x2
tensor because I cannot divide by the lengthscales before calculating the distance. Could KeOps be used here to not have to store the whole tensor at once?ARD-Periodic Kernel:
Here are the tests I have ran so far to check if the covariance matrices match.
Any feedback is much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions