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

Guaranteed latent model functionality #525

Open
SamuelBrand1 opened this issue Nov 15, 2024 · 2 comments
Open

Guaranteed latent model functionality #525

SamuelBrand1 opened this issue Nov 15, 2024 · 2 comments
Labels
enhancement New feature or request EpiAware

Comments

@SamuelBrand1
Copy link
Collaborator

          The implicit promise of this being a latent model is that it will work with the library of latent model functionality. Does this implementation do so? If no do we need to rethink the idea of making this a latent model

Originally posted by @seabbs in #510 (comment)

As @seabbs mentions above the latent model type (setting ODE model and parameter priors) offered by #510 might not make sense with the whole latent model stack. E.g. What does broadcasting a sample from this kind of latent model mean?

This opens up a conversation about what we want for the fundamental capabilities of latent model.

@seabbs
Copy link
Collaborator

seabbs commented Nov 19, 2024

Yes agree. As discussede f2f we likely need some kind of latent model type tree that dispatches between vectors, matrices and other

@SamuelBrand1
Copy link
Collaborator Author

SamuelBrand1 commented Nov 19, 2024

Agreed: latent random variable (processes) we expect to be indexable should be one branch and others on the other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request EpiAware
Projects
None yet
Development

No branches or pull requests

2 participants