Generate release artifacts for the open-dataset smoke path
Constraint: Open-dataset workflow needed the same reporting/release outputs as the synthetic baseline to be operationally useful Rejected: Treat open-data smoke as a one-off test only | Leaves no reusable benchmark or release documentation trail Confidence: high Scope-risk: narrow Directive: Every future real-dataset smoke run should emit eval JSON plus artifact bundle in the same directory Tested: /usr/local/miniconda3/bin/python scripts/generate_artifacts.py --eval-json reports/open-smoke-fixed/fma/eval.json --config-json reports/open-smoke-fixed/fma/config.json --output-dir reports/open-smoke-fixed/fma --model-version open-smoke-fixed --data-version synthetic_as_open_fixed_fma Not-tested: Artifact generation on a larger real downloaded corpus with multiple hard-case buckets
Showing
7 changed files
with
166 additions
and
0 deletions
-
Please register or sign in to post a comment