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

Demonstration Primarily For NNH At PyRenew Meeting #31

Closed
AFg6K7h4fhy2 opened this issue Oct 23, 2024 · 6 comments · May be fixed by #40
Closed

Demonstration Primarily For NNH At PyRenew Meeting #31

AFg6K7h4fhy2 opened this issue Oct 23, 2024 · 6 comments · May be fixed by #40
Assignees
Labels
High Priority user-feedback Pertaining to user feedback for certain items in the code-base.

Comments

@AFg6K7h4fhy2
Copy link
Collaborator

AFg6K7h4fhy2 commented Oct 23, 2024

A demonstration at the November 5th community meeting might consist of the following

  • A utilities diagram discussion (utilities which are current or in progress).
  • The sequence of steps from model → idata → dateframe (from idata w/ dates) → hub submission.
  • The sequence of steps from model → idata → dateframe (from idata w/ dates) → ScoringUtils ready object.
@AFg6K7h4fhy2 AFg6K7h4fhy2 added the user-feedback Pertaining to user feedback for certain items in the code-base. label Oct 23, 2024
@AFg6K7h4fhy2 AFg6K7h4fhy2 self-assigned this Oct 23, 2024
@AFg6K7h4fhy2 AFg6K7h4fhy2 added this to the [October 28, November 8] milestone Oct 23, 2024
@AFg6K7h4fhy2
Copy link
Collaborator Author

This will take the form of a Quarto notebook, likely following from the FluSight vignette.

@AFg6K7h4fhy2
Copy link
Collaborator Author

AFg6K7h4fhy2 commented Nov 4, 2024

Considerations for this issue:

  1. Is the Nov. 5 community meeting occurring?
  2. Conditional on (1) "yes", is forecasttools-py still expected to be demo'd?
  3. Conditional on (1, 2) "yes", what should the demo consist of?

For (3), in addition to #31 (comment), I can imagine, with respect to forecasttools-py

  • Discussing the addition of dates to az.InferenceData.
  • Pondering the future of forecasttools-py (with reference to the utilities diagram, see here).

Re: #31 (comment)

The Nov. 5th meeting is not occurring but a future forecasttools-py demo. might occur.

@AFg6K7h4fhy2
Copy link
Collaborator Author

Following STF Daily Standup 2024-11-04:

  • pyrenew-hew ED visits forecasts will be discussed at 2024-11-05 community meeting.
  • forecasttools-py can be demo'd at some future data, depending on maturity and extent of the utilities it provides.

As such, I am changing the priority of this issue from Medium to Low and the milestone. Comments from colleagues would be appreciated.

#31 (comment) has been updated to reflect the meeting.

@AFg6K7h4fhy2
Copy link
Collaborator Author

Following the MSR Meeting for 2024-11-15:

  • forecasttools-py will be demo'd.
    • Idea: Part, Discussion on idata (groups, vars, dims).
    • Idea: Part, Walkthrough of hubverse submission from idata.
    • Idea: Part, Walkthrough of adding time to idata+ utility.
    • Idea: Part, Discussion on future work.
  • forecasttools-R might be demo'd.

@AFg6K7h4fhy2
Copy link
Collaborator Author

Some brief notes:

  • A render Quarto notebook will be the medium.
  • The author ought to send DHM a copy before 10AM EST 2024-11-19.

@AFg6K7h4fhy2
Copy link
Collaborator Author

The author closes this issue, since the community meeting occurred. The PR associated with this issue remains to be merged, as it depends on the merging of the "time representations" PR, i.e. PR 35.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority user-feedback Pertaining to user feedback for certain items in the code-base.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant