-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop H2O Regression Algorithms #2
Comments
If we want to extract other models from the leaderboard. We can do as
|
@AlbertoAlmuinha I'm not super concerned about the reproducibility. We can solve this down the road. A couple of reasons for the differences - Each time your run AutoML in a session for a given project, the results get added to the leaderboard. This could be why we are getting different results. Also, we can always ask Erin LeDell (she's available in our Slack Channel). |
@AlbertoAlmuinha please feel free to submit a pull request once you have your codes ready for review. |
@mdancho84 Sure, count on a PR by the end of this week (possibly sooner but I don't want to get my fingers caught). |
@AlbertoAlmuinha I think you are getting different results because you could not run the XGBoost model. H2O XGBoost does not run on windows. Web-based H2O Cluster (http://localhost:54321/flow) should be running when we use h2o.init(). |
H2O AutoML WorkflowHere's an example that I've adapted from @AlbertoAlmuinha's work and @Shafi2016's MVP examples. Take a look and let me know what you think. Notes:
We can likely do better than this if we train longer but good for a quick example. |
@AlbertoAlmuinha Regarding reproducibility -- H2O AutoML will only be reproducible if the following criteria are met (your code is doing 1 & 2 but not 3):
|
Objective is to forecast using additional predictors including date-related predictors. recipe_spec <- recipe(Weekly_Sales ~ ., data = training(splits)) %>% The code above has predictors related to Date. I’m assuming that there is another predictor say X. FUTURE FORECAST -----If one needs to forecast 1-year ahead after refitting model(s) using full data set (training + testing), then one needs also future 1-year X values as well as predictors related to Date. It is needed to collect/prepare future 1-year X values as well. Any idea please or any implementation in modeltime to simulate/predict 1-year X values. |
Here's a minimal example based on Shafi's code. We can convert this into
tidymodels
format once we agree on the process being shown.Created on 2021-03-08 by the reprex package (v1.0.0)
The text was updated successfully, but these errors were encountered: