Automate the full open-dataset smoke workflow behind one command
Constraint: Real FMA or MTG-Jamendo onboarding should require only an input directory change, not a long manual command chain Rejected: Keep the smoke steps separate only | Slows repeated validation and increases operator error risk Confidence: high Scope-risk: moderate Directive: Use smoke-local as the default first-pass validation path for every new local open-music corpus Tested: /usr/local/miniconda3/bin/python src/data/external_adapters.py smoke-local fma data/synthetic_v2/songs --output-root data/external_smoke --eval-ratio 0.2 --query-duration 5.0 --train-epochs 1 --batch-size 2; /usr/local/miniconda3/bin/python -m py_compile src/data/external_adapters.py src/data/manifest_tools.py train.py run_demo.py evaluate.py scripts/generate_artifacts.py Not-tested: Real downloaded FMA or MTG-Jamendo directories on larger-scale smoke runs
Showing
42 changed files
with
1050 additions
and
0 deletions
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
No preview for this file type
This file is too large to display.
-
Please register or sign in to post a comment