Repository navigation
scoreboard: timed OpenEMR arms 3-6, arm 5 API step, agent/screen/API comparison - #1365
Merged
Merged
Conversation
…y: triggers and a poller) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…down in the tables Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ngine and throughput lines Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ff runs, Amendment 6 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e labels per run, claims runs shown only when complete Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n the fixture database), Amendment 7 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e every median, Amendment 8 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… on rebuilt state (5/5 caught, 0 false alarms); claims scripts never read a stale receipt; Amendment 9 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er in a file (CodeQL py/clear-text-storage-sensitive-data); label the re-judge block 'rebuilt state, judged by fixed verify-run' The claims scripts wrote each item's (made-up, patient-shaped) values to a params.json beside the baseline. verify-run now reads them from /dev/stdin, so no file holds them; the run record keeps only the executor and its claim (claims.py no longer copies the agent's final text into it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # packages/flow/public-artifacts.json
Member
Author
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.
Follow-up to #1303, which was merged at 05dd032. These are the scoreboard rows and changes made after that commit. Every figure comes from
python -m scoreboard.buildover rows committed underpackages/flow/benchmark/scoreboard/raw/.What's in it
SCOREBOARD.mdsection, "OpenEMR: agent, screen program and API step". It is the comparison the README quotes, with each run's profile label, engine, n and load gate.claims_openemr.py): faults are injected only in the fixture database, with triggers and a poller. Its data lands in a later commit, once the run is complete. The build shows a claims run only after its meta is marked complete.Checks
ruff checkandruff format --checkonbenchmark/scoreboard.refresh_inventory.sh).🤖 Generated with Claude Code