-
Notifications
You must be signed in to change notification settings - Fork 324
Forecast Checks
Jarad Niemi edited this page Jul 1, 2020
·
18 revisions
-
header must only include
location
,target
,type
,quantile
,value
(required for zoltpy) andforecast_date
,target_end_date
-
each row must have the same number of columns as header
-
location
must be in "locations" column of locations.csv -
target
must be inpaste(1:20, "wk ahead inc death") paste(1:20, "wk ahead cum death") paste(0:130, "day ahead inc hosp") paste(1:8, "wk ahead inc case")
-
forecast_date
andtarget_end_date
must be in YYYY-MM-DD format -
quantile
must be inc(0.01, 0.025, seq(0.05, 0.95, by = 0.05), 0.975, 0.99)
-
quantile
for county locations must be inc(0.025, 0.100, 0.250, 0.500, 0.750, 0.900, 0.975)
-
checks
quantile
must be an int or float in [0, 1] -
checks
value
must be an int or float and non-negative -
validates date alignment as documented in the issue add additional validations
-
validates quantiles and values (i.e,. at the prediction level):
- checks that entries in
value
must be non-decreasing as quantiles increase - checks that elements in the
quantile
are unique
- checks that entries in
-
validates quantiles as a group:
- there must be exactly one point prediction for each
location/target
pair
- there must be exactly one point prediction for each
- Home
- Submitting Forecasts
- Data Validation
- Truth Data
- Baseline model
- Weekly ensemble release
- Developer