Repository navigation
HeatOps v2: multi-crew scheduling and reproducible evaluation - #3
Merged
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.
Why
The hackathon scheduler selects only one crew and depends on a small historical demo. This branch adds workforce assignment and explicit experimental evidence while preserving the Phoenix regression.
Changes
Validation
162 local tests passed; Ruff lint/format and compileall passed. The original Phoenix result remains 2.971485%, with an unchanged snapshot checksum. Streamlit HTTP health and a real Open-Meteo request were verified.
The complete fixed benchmark rerun and final documentation are being attached before handoff. This PR remains a draft. No main-branch merge or public deployment change is requested.