Open ranr01 opened 6 years ago
Bump, it just took me a bit to figure this out. It seems that @dfm answered this already in #57 and the intended result is indeed nominal/ndim
.
This behavior doesn't appear to be documented (I'm happy to contribute a few lines of explanation if the maintainers would like), but more importantly, I'm unsure why george
behaves this way. Shouldn't a ConstantKernel
always be considered a scalar, even if ndim != 1
, since kernels always output a scalar? What's the motivation for varying the hyperparameter according to ndim
?
@apsabelhaus: This was chosen as an implementation detail really, but I understand that it is a bit strange! I don't have much time these days to commit, but I'd love to have a note in the docs if you have the time!
Thanks! Good to know. I'll figure out some documentation suggestions when I've got a few minutes. Until then, hopefully this issue points folks in the right direction.
Hi,
When you multiply a kernel with a constant, $A$, you get an additional parameter to the kernel, $k_1$. However, I've noticed that this parameter is given by $k_1 = log(A/d)$ where d is the kernel's ndim (and not simply by $k_1=log(A))$).
Is this intentional? If so it might be a good idea to document it in the kernels section of the docs.
Below is a simple example.
Thanks, Ran
A simple example:
outputs something like:
which is OK since we expect the diagonal to be 1.0.
However, if you look at the parameters:
you get:
Where naively I would expect 'kernel:k1:log_constant' to be 0.0 and not log(1/2).