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

Reconsider note about redundant fields #96

Open
elray1 opened this issue Mar 8, 2024 · 0 comments
Open

Reconsider note about redundant fields #96

elray1 opened this issue Mar 8, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@elray1
Copy link
Contributor

elray1 commented Mar 8, 2024

Looking at this page: https://hubdocs.readthedocs.io/en/latest/user-guide/tasks.html#usage-of-task-id-variables

We write "We encourage Hubs to avoid redundancy in the model task IDs. For example, Hubs should not include all three of target_date, origin_date, and horizon as task IDs because if any two are specified, the third can be calculated directly. Similarly, if a variable is constant, it should not be included. For example, if a Hub does not include multiple targets, target could be omitted from the task IDs."

However, since we wrote that, we've had discussions around the idea that including redundant fields (in the case of FluSight, reference_date, horizon, and target_date) might be helpful as a check to ensure that teams did their setup correctly. Should we remove this note?

@nickreich nickreich added the documentation Improvements or additions to documentation label May 17, 2024
@mmkerr mmkerr self-assigned this Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: Todo
Development

No branches or pull requests

3 participants