Should AutoReclab also have a Termination mechanism for budget overruns #74
dylanfandio
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Should AutoRecLab also have a termination mechanism for budget overruns?
Context
AutoRecLab currently focuses on iterative experimentation, debugging, and improvement. That is useful for exploration, but it can also lead to long-running runs when the task is difficult, the search space is large, or model/tool calls become expensive. It is already in some parts included in config.toml but there is still a lot which can be expanded.
This raises a practical question: should AutoRecLab be able to stop itself when a predefined budget is exceeded?
Motivation
A expansion of the termination mechanism could help in several situations:
Possible budget types
A termination rule could be based on one or more of the following:
Open design questions
Potential implementation idea
A simple first version could be:
Discussion
We think this would be a useful safety feature, especially for autonomous runs that can otherwise keep going without a strong stopping condition.
What would be the best budget signal for AutoRecLab:
Beta Was this translation helpful? Give feedback.
All reactions