Consider improving nowcaster/forecaster epi_slide
sample in advanced.Rmd
#288
Labels
bug
Something isn't working
documentation
Improvements or additions to documentation
P2
low priority
Problem described here. Allowing negative
after
values would not completely resolve the issue above, as the test-time prediction would still need to be made. We're just missing the train/test split. E.g., this version should perform the split (and expands the window to get two time steps (max) worth of training data). However, it runs into issues with a missing training split when there is no training data available (previously not a problem because there was always the test data to train on):This gives a mysterious message
due to the carefree coding (because we are trying to pull
y
out of aNULL
training set). We can likely get more appropriate error messages via:group_split
,nest_by
,nest(....., .by=.....)
, etc. + a bunch of awkward indexing (filter
pull
unwrap)This improves the error message
but regardless of whether we get an intelligible error message or not, we still have to have manual code to deal with skipping/completing instances with no training data (see #256).
For now, I plan to just explain the additional problem noted in the linked issue, and hold off on any improvements. A solution to #256 may give us more options. Another approach would be to change to using
epipredict
in this example.The text was updated successfully, but these errors were encountered: