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
Frequently, the policy environment changes throughout the year. Currently, we can call it with an integer for a year, a month, or a precise date. The former two may create ambiguity (we probably default to 1 Jan if a year is provided, but I would actually have to look that up).
Just as for data, we should require precision from the user instead of making assumptions.
Change parser
Check docs
Fix tutorials
The text was updated successfully, but these errors were encountered:
hmgaudecker
changed the title
Require precise data for setting up a policy environment
Require precise date for setting up a policy environment
Oct 2, 2024
Frequently, the policy environment changes throughout the year. Currently, we can call it with an integer for a year, a month, or a precise date. The former two may create ambiguity (we probably default to 1 Jan if a year is provided, but I would actually have to look that up).
Just as for data, we should require precision from the user instead of making assumptions.
The text was updated successfully, but these errors were encountered: