Repository navigation
feat(evolve-kernel): per-iteration progress table in detail page - #35
Merged
Merged
Conversation
The metric cards only surface the *last* iteration's speedup and the library's current best, so a run that is stuck — or that regressed after a good iteration — looks identical to one that is climbing, and the per-iteration "goal" (what the optimizer set out to do) was not visible anywhere. Add an "Iteration Progress" panel rendered from the already-fetched `/iterations` payload: one row per iteration with status, exec time, speedup, library size, duration and goal. Rows that set a new best exec time are marked green with a "▲" tag — the "is it actually improving?" signal. - export `formatMs` from ok-kernel-library.js so both tables share one formatter instead of duplicating it - coerce `perf.speedup` with Number() before toFixed: the value is stored straight from an LLM-generated perf harness report with no numeric validation, so a malformed row now degrades to "—" instead of throwing - add tests/test_iteration_progress.py pinning the reader fields the table renders, plus that a partially written iteration record does not take the whole list down
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.
The metric cards only surface the last iteration's speedup and the library's current best, so a run that is stuck — or that regressed after a good iteration — looks identical to one that is climbing, and the per-iteration "goal" (what the optimizer set out to do) was not visible anywhere.
Add an "Iteration Progress" panel rendered from the already-fetched
/iterationspayload: one row per iteration with status, exec time, speedup, library size, duration and goal. Rows that set a new best exec time are marked green with a "▲" tag — the "is it actually improving?" signal.formatMsfrom ok-kernel-library.js so both tables share one formatter instead of duplicating itperf.speedupwith Number() before toFixed: the value is stored straight from an LLM-generated perf harness report with no numeric validation, so a malformed row now degrades to "—" instead of throwing