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.

Sign up for GitHub

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

Jump to bottom

Figure out a better way of handling calculation of num_latent_gps #1343

Open
st-- opened this issue Mar 18, 2020 · 0 comments
Open

Figure out a better way of handling calculation of num_latent_gps #1343

st-- opened this issue Mar 18, 2020 · 0 comments

Comments

@st--
Copy link
Member

st-- commented Mar 18, 2020

It's not nice for GPModel to need to be aware of specific likelihoods as introduced by #1316. However, num_latent_gps is a bit more broken in general, we should fix this in the future. There are also some slightly problematic assumptions re the output dimensions of mean_function.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@st--