We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think this is worth a separate discussion-- I think we might want separate fitting and prediction keys
Like, I think it's fair for us to fit the model a small number of times (1? 3?) but then we'll want to draw a number of trajectories (100? 1000?).
I want the same fitted model to produce the same trajectory when given the same input key.
There are some nice ways to generate child keys from a parent key.
Originally posted by @swo in #102 (comment)
The text was updated successfully, but these errors were encountered:
cc @afmagee42 if you have any deep thoughts here
Sorry, something went wrong.
eschrom
No branches or pull requests
Like, I think it's fair for us to fit the model a small number of times (1? 3?) but then we'll want to draw a number of trajectories (100? 1000?).
I want the same fitted model to produce the same trajectory when given the same input key.
There are some nice ways to generate child keys from a parent key.
Originally posted by @swo in #102 (comment)
The text was updated successfully, but these errors were encountered: