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
I already wrote an epi_recipe wrapper around recipe. This performs 2 functions specific to our use case. First, the template is always a single row to avoid copies. Second, it handles time_value and geo_value (and other keys) properly.
Do we implement a epi_workflow around workflow. Current workflow does not support post processing of any type. And it doesn't have many useful S3 methods (residuals, fitted, etc).
Do we implement wrappers around predict to keep the keys.
epi_recipe doesn't currently add a class (it has class recipe). Do we add one?
We need to do something to solve 2.
The text was updated successfully, but these errors were encountered:
I already wrote an
epi_recipe
wrapper aroundrecipe
. This performs 2 functions specific to our use case. First, thetemplate
is always a single row to avoid copies. Second, it handlestime_value
andgeo_value
(and other keys) properly.epi_workflow
aroundworkflow
. Current workflow does not support post processing of any type. And it doesn't have many useful S3 methods (residuals, fitted, etc).predict
to keep the keys.epi_recipe
doesn't currently add a class (it has classrecipe
). Do we add one?We need to do something to solve 2.
The text was updated successfully, but these errors were encountered: