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

Light refactor of models based on experience with Predictive, forecasting, and plans for time handling. #249

Closed
3 tasks done
damonbayer opened this issue Jul 8, 2024 · 3 comments · Fixed by #305
Closed
3 tasks done
Assignees
Labels
clean up Good code that could be better good first issue Good for newcomers

Comments

@damonbayer
Copy link
Collaborator

damonbayer commented Jul 8, 2024

  • n_timepoints_to_simulate should be renamed. Maybe just n_datapoints
  • We should not pad data inside or outside of the model. Right now we pad and then slice when we could just do neither. Addressed in Forecasting Interface #241
  • There should not be a separate fork if observed_data is None in either model Addressed in Forecasting Interface #241
@gvegayon
Copy link
Member

In the context of #304, I realized we have the arguments n_timepoints and duration for seeding processes and processes in general. Shouldn't all be named duration, @damonbayer @dylanhmorris?

@damonbayer
Copy link
Collaborator Author

Shouldn't all be named duration, @damonbayer @dylanhmorris?

In #156, we standardized on n_timepoints, but I think we should do something with time units for these arguments.

@dylanhmorris
Copy link
Collaborator

New issue to discuss/decide this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clean up Good code that could be better good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants