You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: