feat: run the same prompt multiple times into separate numbered output directories#65
Open
floo-dck wants to merge 1 commit into
Open
feat: run the same prompt multiple times into separate numbered output directories#65floo-dck wants to merge 1 commit into
floo-dck wants to merge 1 commit into
Conversation
…arate output directories
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.
Summary
Adds a new
--runsCLI flag that executes AutoRecLab multiple times with thesame prompt in a single command. Each run is written to its own numbered
subfolder inside the configured
out_dir, so multiple experiment runs no longeroverwrite each other.
Motivation: To analyze the stability/variance of results, we need to run the
exact same prompt several times (e.g. 10x) and compare the outputs.
Changes
--runs Nargument (default1) inmain.py. The prompt is read once andreused for every run.
out/run_01,out/run_02, … The numbering continues from the highestexisting
run_*folder, so previous results are never overwritten. Thezero-padding adapts to the total run count (e.g.
run_01…run_10).run_once()helper and theprompt input into
get_user_request()for readability.reset()methods toCostsTrackerandStatisticsTrackerso costs and statistics start clean for every run.attach_file_handler()now removes previously attachedfile handlers, so each run logs to its own
debug.login its own folder.--runsoption.Backwards compatibility
With
--runs 1(the default) the behavior is unchanged — output is writtendirectly to
out/as before.How to test
uv run main.py --prompt "Build a recommender..." --runs 10