Make long CPU index builds resumable and root-path tolerant
Constraint: Real FMA smoke indexing can run for a long time on CPU and synthetic/root-layout datasets must still use the same build-index entrypoint Rejected: Treat build-index as all-or-nothing and require full reruns after interruption | wastes hours on CPU and obscures whether work was already completed Confidence: high Scope-risk: moderate Directive: Preserve checkpoint file compatibility; future smoke-local automation should prefer resume before rebuilding from scratch Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/src/engines/ecapa_embedder.py acr-engine/src/engines/chromaprint_matcher.py acr-engine/run_demo.py; synthetic_v2 partial-checkpoint resume vs fresh rebuild equality check (shape/ids/embeddings/progress) Not-tested: In-place resumption of the currently running real FMA process after an actual external kill/restart
Showing
5 changed files
with
181 additions
and
9 deletions
-
Please register or sign in to post a comment