Make forecast boosting rounds configurable - #14
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
--estimatorsto the production forecast CLIWhy
The evaluator and demo already allowed the number of boosting rounds to be
configured, and the README said this setting was configurable. The production
aep-forecastcommand nevertheless always used the hard-coded default of 800.User impact
Users can now trade training time against model capacity consistently across
evaluation, demo, and production forecast commands.
Validation
python -m pytest -q(66 passed)python -m ruff check src tests streamlit_app.pypython -m compileall -q src tests streamlit_app.pypython -m buildaep-forecast --helpexposes--estimators