- 02 Jun, 2026 40 commits
-
-
Constraint: While the dataset gate is still byte-bound, the user expects continued verifiable milestone tracking rather than idle waiting. Rejected: Deferring updates until completion | That would lose evidence about guard durability and long-transfer behavior. Confidence: high Scope-risk: narrow Directive: Continue capturing substantial percentage gains and guard-runtime evidence until the readiness gate finally opens. Tested: Verified the detached guard remained alive for more than five minutes, confirmed log growth through eleven polling cycles, re-ran archive inspect, and confirmed readiness is still blocked only by incomplete bytes. Not-tested: Extraction and real-data smoke remain pending until the archive is complete.
cnb.bofCdSsphPA authored -
Constraint: The active Ralph loop still needs concrete, incremental verification while the real-data gate remains download-bound. Rejected: Compressing multiple progress milestones into silence | The user explicitly asked for continuous staged progress with commits. Confidence: high Scope-risk: narrow Directive: Keep checkpointing only material byte-progress and guard-liveness milestones until the archive completes. Tested: Verified the detached guard remained alive for more than four minutes, confirmed log growth through nine polling cycles, re-ran archive inspect, and confirmed readiness is still blocked only by incomplete bytes. Not-tested: Extraction and real-data smoke remain pending until the archive is complete.
cnb.bofCdSsphPA authored -
Constraint: Long-running progress evidence should keep proving both transfer health and guard durability until the gate opens. Rejected: Waiting silently for completion | The user asked for continuous optimization and verifiable staged updates. Confidence: high Scope-risk: narrow Directive: Keep recording material progress jumps and guard liveness rather than emitting redundant no-change updates. Tested: Verified the detached guard was still alive after more than three minutes, confirmed log growth through seven polling cycles, re-ran archive inspect, and confirmed readiness remains blocked only by incomplete bytes. Not-tested: Extraction and real-data smoke still await full archive completion.
cnb.bofCdSsphPA authored -
Constraint: The real-data lane depends on confidence that the unattended guard will survive for the rest of the download, not just a short sample window. Rejected: Declaring the guard fully solved after the prior check | More elapsed time and more cycles give stronger operational proof. Confidence: high Scope-risk: narrow Directive: Continue pairing guard-runtime evidence with readiness checks until the archive completes and phase transition occurs. Tested: Verified the detached guard was still alive after more than two minutes, observed log growth through five polling cycles, re-ran archive inspect, and confirmed readiness is still blocked only by incomplete bytes. Not-tested: The completed handoff through extraction and smoke is still pending archive completion.
cnb.bofCdSsphPA authored -
Constraint: We need evidence that the new guard launcher solved the earlier drop behavior before trusting it for the rest of the transfer. Rejected: Assuming success from one or two polls alone | A longer runtime and multiple cycles provide stronger evidence. Confidence: high Scope-risk: narrow Directive: Keep verifying guard liveness alongside archive progress until readiness opens and the pipeline can switch phases. Tested: Checked the detached guard's pid/runtime, confirmed three logged polling cycles, re-ran archive inspect, and confirmed the readiness gate is still blocked only by incomplete bytes. Not-tested: Extraction and real-data smoke remain pending until the archive reaches full size.
cnb.bofCdSsphPA authored -
Constraint: A multi-hour download needs a background guard that survives shell teardown, not just a logically correct polling loop. Rejected: More ad-hoc nohup restarts | They obscured whether the issue was loop logic or process detachment. Confidence: high Scope-risk: narrow Directive: Use the guard launcher for future unattended waits and keep pid/log artifacts so later sessions can verify liveness quickly. Tested: Ran a foreground three-cycle control experiment, launched the new setsid-based guard, then verified the detached process survived with PPID 1 and emitted at least two polling cycles in the log. Not-tested: Full handoff through completed download, extraction, and smoke still awaits archive completion.
cnb.bofCdSsphPA authored -
Constraint: The real-data lane still needs a reliable unattended handoff process, and fresh evidence now shows the first durability fix was incomplete. Rejected: Treating the restarted waiter as fully solved | The second drop proves more diagnosis is required. Confidence: medium Scope-risk: narrow Directive: Investigate why the waiter exits after the first logged poll instead of assuming the infinite-loop change alone solved stability. Tested: Re-checked archive progress, confirmed the waiter process was absent, inspected the single-entry log file, and restarted the waiter successfully. Not-tested: Root-cause isolation for the second waiter drop remains pending.
cnb.bofCdSsphPA authored -
Constraint: The real dataset download lasts far longer than the waiter's original three-cycle lifetime, so the handoff process must survive unattended. Rejected: Repeatedly restarting a short-lived waiter by hand | That is fragile and defeats the point of automation. Confidence: high Scope-risk: narrow Directive: Keep the waiter long-lived by default and preserve progress logs so future sessions can see active polling immediately. Tested: Diagnosed the original max-cycles behavior, ran a short two-cycle verification showing archive growth, then relaunched the long-lived waiter and confirmed live process plus log output. Not-tested: The completed handoff path from full archive to extraction has not fired yet because the download is still in progress.
cnb.bofCdSsphPA authored -
Constraint: The real-data lane should not rely on a dead background handoff process while a long download is still in flight. Rejected: Assuming the prior waiter was still alive | A direct process check showed it was gone. Confidence: high Scope-risk: narrow Directive: Re-check waiter liveness during subsequent progress audits and restart it whenever it drops before archive completion. Tested: Re-ran archive inspect, verified the waiter was absent, confirmed the empty log file, restarted the waiter, and validated the new live process. Not-tested: The restarted waiter has not yet handed off to extraction because the archive remains incomplete.
cnb.bofCdSsphPA authored -
Constraint: The dataset gate is long-running, so progress should continue without manual babysitting once the archive finishes. Rejected: Pure polling without a handoff process | That would still require manual intervention at completion time. Confidence: high Scope-risk: narrow Directive: Leave the waiter in place until it hands off to post-download preparation, then capture the resulting extraction evidence. Tested: Re-ran archive inspect, confirmed no prior waiter, started wait_for_fma_and_prepare in the background, and verified the live process plus log file. Not-tested: The waiter has not yet reached extraction because the archive is still incomplete.
cnb.bofCdSsphPA authored -
Constraint: The active Ralph loop needs current operational evidence while the dataset gate is still waiting on download completion. Rejected: Relying on byte growth alone | We also need process-level proof that the transfer path is still alive. Confidence: high Scope-risk: narrow Directive: Keep validating both archive growth and transfer liveness until readiness opens, then switch to extraction immediately. Tested: Re-ran inspect, watchdog, and process checks; all confirmed higher byte counts, a live curl process, and no restart needed. Not-tested: Real-data extraction and smoke remain blocked by the incomplete archive.
cnb.bofCdSsphPA authored -
Constraint: We need script-backed evidence for whether the pipeline can advance beyond download waiting. Rejected: Assuming the next phase is ready from percentage alone | Readiness must be validated by the post-download gate script. Confidence: high Scope-risk: narrow Directive: Use the readiness script, not only byte counts, before switching to extraction and smoke. Tested: Re-ran archive inspect and the post-download readiness check, which confirmed progress growth but a still-blocked archive_not_complete gate. Not-tested: Extraction and smoke remain deferred until the readiness script reports completion.
cnb.bofCdSsphPA authored -
Constraint: Ralph requires new verification evidence while the real-data gate remains unresolved. Rejected: Repeating the prior status without a fresh measurement | It would not prove continued forward progress. Confidence: high Scope-risk: narrow Directive: Keep recording byte-level progress until the archive completes, then switch immediately to extraction and smoke validation. Tested: Re-ran inspect and watchdog checks, confirming higher byte counts and a live curl process without restart. Not-tested: Extraction and real-data smoke remain blocked on archive completion.
cnb.bofCdSsphPA authored -
Constraint: Real-data smoke cannot be claimed before the user-provided archive is fully downloaded and locally inspectable. Rejected: Pretending readiness from partial bytes | That would create false verification evidence for the dataset lane. Confidence: high Scope-risk: narrow Directive: Do not run real FMA extraction or smoke until inspect reports the full expected archive size. Tested: Re-ran the archive inspect command and confirmed the active background curl process plus current local file size. Not-tested: Extraction, local preparation, and real FMA smoke remain pending until the archive completes.
cnb.bofCdSsphPA authored -
Constraint: The guidance had to align with the repo's existing manifest and pgvector templates while staying usable for later industrial ingestion. Rejected: A purely conceptual note | It would not be actionable for future sessions or data engineering work. Confidence: high Scope-risk: narrow Directive: Keep future dataset onboarding and pgvector ingestion changes anchored on manifest-first contracts and stable song identifiers. Tested: Relative markdown links for the updated docs were validated locally and repository anchor files were confirmed present. Not-tested: No model retraining or database ingestion was run in this documentation-only stage.
cnb.bofCdSsphPA authored -
Constraint: The real FMA archive still needs time, but once it finishes the workflow should transition into extraction and readiness with minimal operator attention Rejected: Keep completion detection as an entirely manual loop | Wastes attention and slows handoff at the exact moment the archive becomes useful Confidence: high Scope-risk: narrow Directive: Use wait_for_fma_and_prepare.py as the passive bridge from long-running download to active dataset onboarding whenever unattended waiting is acceptable Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/wait_for_fma_and_prepare.py; /usr/local/miniconda3/bin/python acr-engine/scripts/wait_for_fma_and_prepare.py --interval 2 --max-cycles 2 Not-tested: The completed-path handoff into extraction remains pending full archive completion
cnb.bofCdSsphPA authored -
Constraint: Once the large FMA archive finishes, future sessions should not need to manually stitch extraction and readiness checks together Rejected: Leave post-download steps as manual shell sequences | Increases delay and error risk at the most valuable transition point Confidence: high Scope-risk: narrow Directive: Keep fma_postdownload_ready.py as the canonical first command after archive completion before attempting real-data smoke runs Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/fma_postdownload_ready.py; /usr/local/miniconda3/bin/python acr-engine/scripts/fma_postdownload_ready.py Not-tested: Successful extract and readiness on the full archive remain pending completion of the download
cnb.bofCdSsphPA authored -
Constraint: Schema and manifest-export templates are useful, but practical adoption still needs an explicit handoff into database load order and SQL shapes Rejected: Stop at export JSON only | Leaves later sessions to redesign the bulk-ingest bridge from scratch Confidence: high Scope-risk: narrow Directive: Keep bulk-load templates declarative until a real database target is available, then add a live loader without changing manifest semantics Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/pgvector_bulk_load_template.py; /usr/local/miniconda3/bin/python acr-engine/scripts/pgvector_bulk_load_template.py --input acr-engine/reports/pgvector_manifest_export_test.json --output acr-engine/reports/pgvector_bulk_load_plan_test.json Not-tested: Live PostgreSQL execution remains pending a database environment
cnb.bofCdSsphPA authored -
Constraint: The user needs concrete downstream data handling guidance now, and future vector retrieval work should not start from abstract docs alone Rejected: Leave pgvector support at prose-only guidance | Delays integration by forcing later sessions to reinvent schema and export bridges Confidence: high Scope-risk: narrow Directive: Keep schema/export templates aligned with actual manifest semantics before adding live database loaders Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/export_manifest_to_pgvector_json.py; /usr/local/miniconda3/bin/python acr-engine/scripts/export_manifest_to_pgvector_json.py --data acr-engine/data/synthetic_v2 --split test --source-dataset synthetic_v2 --output acr-engine/reports/pgvector_manifest_export_test.json Not-tested: Live PostgreSQL/pgvector ingestion remains pending a real database target
cnb.bofCdSsphPA authored -
Constraint: The user needs detailed data-format guidance now, while the real FMA archive transfer still requires durable hands-off supervision across long sessions Rejected: Treat documentation and download-watch work as separate later tasks | Would leave either user guidance or transfer resilience lagging behind active development Confidence: high Scope-risk: narrow Directive: Keep the new training-data/pgvector guide aligned with actual manifest fields and use watch_fma_download.py as the first-line long-transfer watchdog Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/watch_fma_download.py; /usr/local/miniconda3/bin/python acr-engine/scripts/watch_fma_download.py --cycles 2 --interval 2; /usr/local/miniconda3/bin/python acr-engine/scripts/prepare_fma_archive.py inspect Not-tested: Full archive completion, extraction, and real-data smoke remain pending
cnb.bofCdSsphPA authored -
Constraint: Long FMA archive downloads cannot rely on fragile foreground execution if Ralph-style work must continue across sessions Rejected: Keep manually reissuing foreground download commands after stalls | Increases interruption risk and weakens resumability evidence Confidence: high Scope-risk: narrow Directive: Prefer prepare_fma_archive.py bg-download for future large archive recovery so PID and log evidence remain standardized Tested: /usr/local/miniconda3/bin/python acr-engine/scripts/prepare_fma_archive.py bg-download; /usr/local/miniconda3/bin/python acr-engine/scripts/prepare_fma_archive.py inspect; tail -n 40 /tmp/fma_modelscope_download.log Not-tested: Full archive completion, extraction, and real-data smoke remain pending
cnb.bofCdSsphPA authored -
Constraint: Multi-session continuation gets brittle when large real-data downloads require manual byte math to estimate progress Rejected: Leave inspect output as raw archive size only | Forces every future session to recalculate completion state by hand Confidence: high Scope-risk: narrow Directive: Keep progress fields stable so handoff tooling and humans can rely on them during long archive transfers Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/prepare_fma_archive.py; /usr/local/miniconda3/bin/python acr-engine/scripts/prepare_fma_archive.py inspect Not-tested: Completion of the full archive and downstream extraction remain pending
cnb.bofCdSsphPA authored -
Constraint: The user supplied a verified archive URL that is a better current source of truth than the previously tested mirror path Rejected: Keep the older archive URL as the default control surface | Would ignore fresher user evidence and split operational guidance across sources Confidence: high Scope-risk: narrow Directive: Treat the ModelScope FMA archive URL as the primary default until a newer verified source supersedes it Tested: curl -I -L --max-time 60 https://modelscope.cn/datasets/pengzhendong/fma/resolve/master/fma_small.zip; curl -L --range 0-1023 --max-time 60 -o /tmp/fma_modelscope_probe.bin https://modelscope.cn/datasets/pengzhendong/fma/resolve/master/fma_small.zip; /usr/local/miniconda3/bin/python acr-engine/scripts/prepare_fma_archive.py inspect Not-tested: Full archive completion, extraction, and downstream real-data smoke remain pending
cnb.bofCdSsphPA authored -
Constraint: A service intended for industrialization needs a real process-level smoke test, not only direct function imports Rejected: Rely on unit-style handler calls alone | Misses uvicorn startup and actual HTTP surface regressions Confidence: high Scope-risk: narrow Directive: Keep service_smoke.py lightweight and dependency-free so it remains the fastest operational gate before broader API expansion Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/service_smoke.py; /usr/local/miniconda3/bin/python acr-engine/scripts/service_smoke.py Not-tested: /recognize and /index/build over HTTP remain pending dedicated API smoke inputs
cnb.bofCdSsphPA authored -
Constraint: Industrializing the service path requires visibility into model/index availability and repeated-load behavior before adding heavier production features Rejected: Keep stateless per-request loading until later | Hides readiness problems and wastes time on repeated engine initialization Confidence: high Scope-risk: narrow Directive: Preserve /ready and /cache as low-cost operational probes even if the serving stack evolves behind them Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/src/service/app.py; /usr/local/miniconda3/bin/python /tmp/test_service_readiness.py; /usr/local/miniconda3/bin/python /tmp/test_service_cache.py Not-tested: Live FastAPI HTTP serving and concurrent request behavior remain pending
cnb.bofCdSsphPA authored -
Constraint: The verified FMA archive is multi-gigabyte and downloads slowly, so the workflow must remain inspectable and resumable before extraction can happen Rejected: Depend on ad hoc curl and unzip commands only | Makes long-running handoff and recovery brittle during Ralph-style continuous execution Confidence: high Scope-risk: narrow Directive: Keep official FMA archive acquisition centered on prepare_fma_archive.py so future sessions share one resumable control surface Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/prepare_fma_archive.py; /usr/local/miniconda3/bin/python acr-engine/scripts/prepare_fma_archive.py inspect; unzip -v | head -n 2 Not-tested: Archive extraction and real-data smoke remain pending completion of the full fma_small.zip download
cnb.bofCdSsphPA authored -
Constraint: Real-data progress was blocked until we could prove an upstream archive path that still works today Rejected: Continue iterating on historical per-track URLs | Those paths already proved unstable via 403 and 404 evidence Confidence: high Scope-risk: narrow Directive: Prefer the verified fma_small.zip archive route over legacy page or single-track scraping paths unless upstream changes again Tested: curl -I -L --max-time 60 https://os.unil.cloud.switch.ch/fma/fma_small.zip; curl -L --range 0-1023 --max-time 60 -o /tmp/fma_small_probe.bin https://os.unil.cloud.switch.ch/fma/fma_small.zip Not-tested: Full 7.68 GB archive download, extraction, and smoke execution remain pending
cnb.bofCdSsphPA authored -
Constraint: Real-data progress requires proving whether failures come from our environment or from changed upstream access paths Rejected: Keep treating the fetch blocker as a missing-tool problem | Would misdirect future debugging after yt-dlp module support was verified Confidence: high Scope-risk: narrow Directive: Do not retry historical FMA page URLs again unless a fresh source confirms their return; pivot to official archives or stable mirrors instead Tested: which yt-dlp || true; /usr/local/miniconda3/bin/python -m yt_dlp --version; /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/fetch_fma_subset.py; /usr/local/miniconda3/bin/python acr-engine/scripts/fetch_fma_subset.py --report acr-engine/reports/fma_fetch_subset_report.json Not-tested: Successful real FMA download still pending a valid upstream archive or mirror URL
cnb.bofCdSsphPA authored -
Constraint: Continuous dataset landing work needs concrete failed-path evidence so future sessions do not restart from outdated assumptions Rejected: Omit the failed download automation because it did not complete | Loses reproducible evidence about the current 403 and missing-tool barriers Confidence: high Scope-risk: narrow Directive: Replace this bounded fetch path only after verifying a stable official archive or mirror-based download route Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/fetch_fma_subset.py; /usr/local/miniconda3/bin/python acr-engine/scripts/fetch_fma_subset.py --report acr-engine/reports/fma_fetch_subset_report.json Not-tested: Successful real FMA audio download remains blocked by current upstream/tooling availability
cnb.bofCdSsphPA authored -
Constraint: The user wants real datasets added locally and potentially pushed, which would make ordinary git history fragile without LFS guardrails Rejected: Download first and retrofit tracking later | Risks oversized commits and inconsistent reproducibility rules Confidence: high Scope-risk: narrow Directive: Route all future raw corpus archives and audio under acr-engine/data/raw through LFS unless a smaller manifest-only alternative is explicitly chosen Tested: git lfs version; git check-attr filter -- acr-engine/data/raw/fma_small_audio/example.wav; git check-attr filter -- acr-engine/data/raw/archive.zip Not-tested: Actual large-file add/push against remote LFS storage remains pending until real dataset files are downloaded
cnb.bofCdSsphPA authored -
Constraint: Real-data validation now depends on user-requested local corpus drop zones that may exist before they contain any audio Rejected: Let smoke-local fail deep inside training | Produces slower and less actionable feedback for continuous sessions Confidence: high Scope-risk: narrow Directive: Keep readiness thresholds aligned with the minimum viable query split assumptions before expanding real-data automation Tested: /usr/local/miniconda3/bin/python -m py_compile src/data/external_adapters.py scripts/status_snapshot.py; /usr/local/miniconda3/bin/python src/data/external_adapters.py check-local-ready fma data/raw/fma_small_audio --eval-ratio 0.2 --query-duration 8.0; /usr/local/miniconda3/bin/python src/data/external_adapters.py check-local-ready mtg_jamendo data/raw/mtg_jamendo_audio --eval-ratio 0.2 --query-duration 8.0; /usr/local/miniconda3/bin/python scripts/status_snapshot.py --output .omx/latest_status_snapshot.json Not-tested: Full smoke-local on real FMA or MTG-Jamendo remains blocked until audio is actually downloaded
cnb.bofCdSsphPA authored -
Constraint: Ongoing Ralph-style handoff requires new sessions to distinguish finished capability from smoke-only scaffolding quickly Rejected: Leave capability status implicit in scattered docs | Increases onboarding ambiguity and status misreads Confidence: high Scope-risk: narrow Directive: Update this map whenever a smoke path becomes real-data validated or a regression invalidates a claimed capability Tested: Verified docs/current-capability-map.md exists and is linked from docs/README.md and docs/session-handoff.md Not-tested: Semantic accuracy against future real-dataset runs remains pending
cnb.bofCdSsphPA authored -
Constraint: Future sessions benefit from a saved machine-readable snapshot, not just on-demand script output Rejected: Keep snapshot stdout-only | Makes handoff less durable and harder to automate across sessions Confidence: high Scope-risk: narrow Directive: Refresh .omx/latest_status_snapshot.json whenever the default docs, smoke paths, or next-step commands materially change Tested: /usr/local/miniconda3/bin/python scripts/status_snapshot.py --output .omx/latest_status_snapshot.json; JSON parse check for latest_commit and next_commands Not-tested: External automation consuming the saved snapshot over multiple sessions
cnb.bofCdSsphPA authored -
Constraint: Future sessions need a quick machine-readable summary of the verified repo state and next commands Rejected: Depend on manual reconstruction from docs and git history alone | Slower and more error-prone during handoff Confidence: high Scope-risk: narrow Directive: Keep the snapshot script aligned with the real default docs, drop zones, smoke outputs, and next-step commands Tested: /usr/local/miniconda3/bin/python scripts/status_snapshot.py Not-tested: Consumption of the snapshot by external automation beyond manual review
cnb.bofCdSsphPA authored -
Constraint: New sessions need a minimal startup checklist so they can verify repo health and resume development quickly Rejected: Keep startup knowledge implicit in long docs only | Increases ramp-up time and the chance of missing key checks Confidence: high Scope-risk: narrow Directive: Update this checklist whenever the default startup workflow or open-dataset commands materially change Tested: existence checks for acr-engine/FIRST_RUN_CHECKLIST.md, docs/README.md, docs/session-handoff.md, plus docs link-presence checks Not-tested: Human walkthrough of the full checklist from a fresh shell
cnb.bofCdSsphPA authored -
Constraint: New sessions need a fast, durable understanding of the project state, open-dataset workflow, verified evidence, and next steps Rejected: Rely on scattered docs and git history alone | Too slow for session handoff and easy to miss critical workflow context Confidence: high Scope-risk: narrow Directive: Keep this handoff doc updated whenever a major workflow milestone or verified capability changes Tested: existence checks for docs/session-handoff.md and docs/README.md, plus docs index link presence Not-tested: Manual human review across multiple markdown renderers
cnb.bofCdSsphPA authored -
Constraint: Replacing the synthetic stand-in with real FMA or MTG-Jamendo data should not require users to infer directory structure Rejected: Leave only generic workflow text | Still forces users to guess where local audio should live before smoke runs Confidence: high Scope-risk: narrow Directive: Keep future real-corpus onboarding anchored to data/raw drop zones and smoke-local commands Tested: filesystem existence checks for acr-engine/data/raw/fma_small_audio, acr-engine/data/raw/mtg_jamendo_audio, acr-engine/data/raw/README.md, docs/README.md, docs/open-dataset-workflow.md, acr-engine/data/external_ingested/README.md Not-tested: Real downloaded audio placed into the new drop zones
cnb.bofCdSsphPA authored -
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
cnb.bofCdSsphPA authored -
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
cnb.bofCdSsphPA authored -
Constraint: Open-dataset support was not complete until imported corpora could train, build indexes, and produce eval outputs without manual path surgery Rejected: Stop at train.py dry-run | Does not prove the retrieval/evaluation half of the workflow actually works Confidence: high Scope-risk: moderate Directive: Keep future external dataset layouts self-contained and manifests-root aware across training, indexing, and evaluation paths Tested: /usr/local/miniconda3/bin/python train.py --data data/external_ingested/synthetic_as_open_fixed/fma/manifests --output data/models_open_smoke_fixed --device cpu --epochs 1 --batch-size 2; /usr/local/miniconda3/bin/python run_demo.py build-index --data data/external_ingested/synthetic_as_open_fixed/fma/manifests --model data/models_open_smoke_fixed/best_model.pt --output data/index_open_smoke_fixed --device cpu; /usr/local/miniconda3/bin/python evaluate.py --data data/external_ingested/synthetic_as_open_fixed/fma/manifests --model data/models_open_smoke_fixed/best_model.pt --index-prefix data/index_open_smoke_fixed/reference --split test --device cpu --fast-eval --output-json reports/open-smoke-fixed/fma/eval.json; /usr/local/miniconda3/bin/python -m py_compile evaluate.py run_demo.py src/engines/ecapa_embedder.py src/engines/chromaprint_matcher.py src/data/dataset.py src/data/manifest_tools.py src/data/external_adapters.py train.py Not-tested: Real downloaded FMA or MTG-Jamendo corpora at larger scale
cnb.bofCdSsphPA authored
-
