Skip to content

feat: expose ML retraining interval as a config entity - #5236

Closed
WhatIsThisAllAboutSilly wants to merge 1 commit into
springfall2008:mainfrom
WhatIsThisAllAboutSilly:feature/configurable-ml-interval
Closed

WhatIsThisAllAboutSilly wants to merge 1 commit into
springfall2008:mainfrom
WhatIsThisAllAboutSilly:feature/configurable-ml-interval

Conversation

@WhatIsThisAllAboutSilly

Copy link
Copy Markdown

Add ml_retrain_interval_hours with a two-hour default and a 1–48 hour range. Read the setting each ML cycle and report the configured interval in training logs.

Cover interval boundaries, live changes, initial training and prediction cadence. Document daily retraining configuration.

Refs #5072

Add ml_retrain_interval_hours with a two-hour default and a 1–48 hour range. Read the setting each ML cycle and report the configured interval in training logs.

Cover interval boundaries, live changes, initial training and prediction cadence. Document daily retraining configuration.

Refs springfall2008#5072
@springfall2008

Copy link
Copy Markdown
Owner

Wouldn't apps.yaml setting be enough?

@WhatIsThisAllAboutSilly

Copy link
Copy Markdown
Author

Certainly could be, although input_number.predbat_forecast_plan_hours exists and doesn't seem to override apps.yaml so why does that exist?

@springfall2008

Copy link
Copy Markdown
Owner

Certainly could be, although input_number.predbat_forecast_plan_hours exists and doesn't seem to override apps.yaml so why does that exist?

It's just a question of how many config entities you add...

@WhatIsThisAllAboutSilly

Copy link
Copy Markdown
Author

Maybe apps.yaml is cleaner, when I get 5 mins I'll do that instead I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants