-
Notifications
You must be signed in to change notification settings - Fork 33
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
interface revision #297
Comments
The purpose of the package is to serve as a computational sandbox. Some features of the current interface make this harder than it probably should be. However, I might just miss the proper workflow at this point, so any clarification welcome (@tobiasraabe ).
|
I think for a bootstrap it does not really matter because the setup cost is really small compared to the cost of running a bootstrap. But in general it is true, that we should save setup costs. The reason we implemented it like this is that it reduces complexity by a lot when you always re-create everything instead taking some old model instance, determining which parts have to change and re-creating them. Therefore, I suggest the following:
|
Points for our discussion on Thursday:
|
The multiindex is already implemented in #277 and will be merged into master at some point. |
Description
We are considering to revise the
respy
interface and this issue serves to collect thought and use cases. At the moment, we initialize asimulate()
and acrit_func()
and do a host of setup operations. In particular, we create the time-consumingStateSpace
class instance.For simulation:
For estimation:
The text was updated successfully, but these errors were encountered: