Expose smoke device control before scaling real-data runs
Constraint: Real FMA smoke is already running on CPU, but future smoke runs must be able to target GPU without manually splitting the pipeline
Rejected: Pass through raw 'auto' everywhere | run_demo/evaluate embedder paths cannot consume torch.device('auto') safely
Confidence: high
Scope-risk: narrow
Directive: Keep smoke orchestration device handling normalized at the adapter boundary unless all downstream CLIs gain native auto-device support
Tested: smoke-local --help shows --device; resolve_device('auto') returns cpu on this host; smoke-local synthetic run prints Device: cpu; manual build-index and evaluate succeed on smoke artifacts with top1=1.0 topk=1.0
Not-tested: End-to-end smoke-local completion on the long-running real FMA job and a live CUDA host path
Showing
4 changed files
with
60 additions
and
10 deletions
-
Please register or sign in to post a comment