document output folder structure - #498
Open
anandhu-eng wants to merge 2 commits into
Open
Conversation
Add docs/OUTPUT_STRUCTURE.md describing what a run writes to its report directory: where the directory comes from, the layout of a combined perf + accuracy run, the scorer-specific and compliance-audit files that can appear alongside it, and which tools read which artifact. Link it from the README documentation table and from the CLI quick reference, and correct the CLI quick reference note that said `benchmark from-config` has no `--report-dir` override — it does. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
github-actions
Bot
added
the
size/normal
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
1 participant
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.
Nothing so far explained what a benchmark run leaves behind in its report directory, so this adds a short guide.
It covers:
The guide is linked from the README documentation table and from the CLI quick reference.
While writing it I also found a wrong note in the CLI quick reference: it said
benchmark from-configcannot set the report directory from the command line. It can, so that note is corrected.Documentation only — no code changes.
🤖 Generated with Claude Code