Open brookslogan opened 2 weeks ago
I think that the intention here is to use a combination of arx_forecast_workflow()
and the various functions that modify the workflow (adjust_*()
, update()
, etc).
Do you have a use case where you tried to do this and couldn't? Or can we try to do it? It would make a good vignette or precipitate the creation of additional functions to allow the flexibility you need.
Suppose we want to tweak
arx_forecaster()
. We probably can't just preprocess the inputs or postprocess the outputs; we want to modify theepi_workflow
involved. It seems natural to want to copy-paste its implementation, maybe thearx_fcast_workflow()
implementation, and maybe maybe thearx_args_list()
implementation. One could potentially do without the latter two with theepi_workflow
modification functions, but we don't use those much / at all in our own code/examples, so it might actually feel easier / more natural to do even more copy-pasting rather than use them.One problem/friction with the above:
Created on 2024-06-18 with reprex v2.0.2
is_regression
is a internal (non-exported) function fromepipredict
. There may be other internal functions involved, or imported, non-exported functions from other packages, that can cause similar issues. It may be helpful to:::
or re-export external functions used by canned forecaster/workflows/argslists.