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

write function that translates from hubverse format to scoringutils-ready format #11

Open
3 tasks
nickreich opened this issue Jan 30, 2024 · 1 comment
Open
3 tasks

Comments

@nickreich
Copy link
Contributor

nickreich commented Jan 30, 2024

Create a user-accessible function to handle transforming model-output data to a scoringutil forecast object: https://epiforecasts.io/scoringutils/dev/reference/as_forecast.html

Essentially, the goal of this function is to ensure that model output data is converted to the corresponding scoringutil format by calling the appropriate internal transformation function (these functions are defined in #22, #23, #24, #25, #26).

For example, model output data of output_type median would be passed to the internal hubEvals transform_point_model_output function.

This function should be exported for a user who wants more direct, custom access to scoringutils functionality, but also will be called in hubEvals::score_mdl_output() (#13)

migrated from epiforecasts/scoringutils#605

Definition of done:

  • Create function
  • Unit test(s)
  • Update documentation (vignettes, news, etc.)
@nickreich
Copy link
Contributor Author

To clarify what distinguishes this issue from #12, I think the idea is that this function would be exported and accessible by users where the functions specified in #12 would not be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants