- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
CODA proposes a concept-based interface for time-series forecasting. Five softly anchored concepts and an explicit observed anchor feed a horizon-specific affine decoder. It produces H forecasts from one past-only history and concept vector. The effects of concept edits are exactly inspectable within the fitted model. The paper evaluates predictive performance and the interface through analytic-statistic controls, concept removal and extension, residual alternatives, and alignment and coefficient analyses. It limits this interpretation to model behavior rather than causal interventions on the underlying physical system.
Critical strengths
-
The concept interface is coherent. The affine decoder makes the fitted model's response to concept edits mathematically explicit. The manuscript acknowledges the limits of soft alignment and the absence of harmonic phase. It also treats compatibility terms as priors rather than physical identities. These qualifications give the interpretation a clear scope.
-
The analytic-statistic control, concept-removal and extension experiments, residual alternatives, and alignment/coefficient analyses examine relevant aspects of the interface. These experiments provide positive evidence for the intended method, even though its correspondence with the empirical artifact remains unresolved.
Critical weaknesses
The main unresolved issue is the correspondence between the reported forecasting task and the empirical artifact. The manuscript specifies fixed-origin direct H-step forecasting: all H outputs use one initial history and one concept vector. The supplied reassessment's preserved source excerpts instead describe a scalar prediction head. For consecutive one-step predictions, this pipeline updates the history with newly observed values. Those observations were unavailable at the initial origin. Rolling one-step forecasting is legitimate at each new origin, but its task and information set differ from the stated fixed-origin comparison. The encoder, previous-window reference, and channel-sharing definitions also differ. These discrepancies make it necessary to identify the version used for the reported results.
An older supplementary version could explain the discrepancy. The README also identifies its results as debug-scale experiments rather than the full benchmark. The current material, however, gives neither a version chronology nor a connection between an existing direct-H implementation and the main tables or ablations. The excerpts do not show which pipeline generated those results. A general old-version explanation or newly corrected code would not establish that connection. Identifiable records are needed before this concern can be resolved.
Questions for authors
-
Please identify the already-existing fixed-origin direct-H version used for the reported results and provide its version timeline. How does it relate to the supplied scalar, moving-observed-history implementation?
-
Please provide saved H-step predictions, the configuration, and metric records for one or two identifiable main-table or ablation entries. These records should link the model version and initial forecast origins to the reported values. Existing records may resolve the concern without rerunning the full benchmark. If those entries used rolling-observed history, the affected comparisons would need fixed-origin evaluation with matched baselines.