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

Handle hierarchical smoothness for Matern #239

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

igoumiri
Copy link
Contributor

@igoumiri igoumiri commented Sep 4, 2024

work in progress. Tests are still failing.

_backend_05_fn: Callable = _matern_05_fn,
_backend_15_fn: Callable = _matern_15_fn,
_backend_25_fn: Callable = _matern_25_fn,
_backend_inf_fn: Callable = _matern_inf_fn,
_backend_gen_fn: Callable = _matern_gen_fn,
):
if smoothness.fixed() is True:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was crazy. Numpy functions return np.bool_ so comparisons with == work but is fail. That took me a while to debug.

from MuyGPyS.gp.hyperparameter.experimental import (
HierarchicalParam,
NamedHierarchicalParam,
)
from MuyGPyS.gp.kernels import KernelFn


def _set_matern_fn(
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Part of the problem is that hierarchical parameters require batch_features to be evaluated, and we don't have them at init time. I'm not sure if we should just default to _backend_gen_fn or if we need to evaluate and map _set_matern_fn to each smoothness value.

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

Successfully merging this pull request may close these issues.

1 participant