Join GitHub today
Add scoring of date-based targets #102
Currently we only score 'step-ahead' targets such as '1 wk ahead'. More generally we can score any continuous ones (e.g., 'Season peak percentage'). However, we should also score non-continuous ones like 'Season onset' or 'Season peak week'. @nick explained to me that this can get complicated. We think the solution is to add support for a fixed set of Zoltar-standard time representations, and use existing libraries like pymmwr to implement them. We'd probably use
This came up b/c these date-based targets - Season onset and Season peak week - currently have truth values (which were generated by abhinav's script) that have been converted from EWs to timezero dates. However, the predicted values are still EWs.