Make smoke metadata explicit before more real-data comparisons
Constraint: Real-data smoke reports must distinguish manifest query duration from training segment duration to avoid 5s-vs-8s confusion across runs Rejected: Keep a single ambiguous query_duration field | Makes cross-run analysis and handoff error-prone Confidence: high Scope-risk: narrow Directive: Preserve explicit duration semantics in future smoke/report artifacts and keep legacy aliases only for compatibility Tested: build_smoke_config_summary() emits manifest_query_duration=8.0 and train_segment_duration=5.0 using configs/default.yaml Not-tested: End-to-end regeneration of the still-running real FMA smoke report bundle with the new config schema
Showing
3 changed files
with
87 additions
and
11 deletions
-
Please register or sign in to post a comment