- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper studies a class of irregular multivariate time-series forecasting architectures that (1) represent each observed event independently and (2) integrate information across events through a relational mechanisms. The authors argue that this computation order overlooks context already available among measurements sharing the same recorded timestamp. Although the relational structure may connect co-timestamp events, their initial states do not yet depend on one another when the first relational transformation is applied. The authors call this mismatch pre-propagation synchronicity loss. To address this issue, the paper introduces pre-propagation synchronicity modeling, an architecture-agnostic representation interface that reconstructs the available co-timestamp context and incorporates it into each event state before relational propagation. The resulting information path is: (1) event representation, (2) synchronicity restoration, and (3) relational reasoning. Its hypergraph realization, built on HyperIMTS, is called MissHyper. Experiments on three clinical datasets report improved mean forecasting errors across the evaluated architectures, with MissHyper obtaining the lowest mean errors among the tested configurations.
Critical strengths
- The paper identifies an underexamined design choice in irregular time-series models using relational forecasters: not only how observations interact, but when shared context enters their representations. This is particularly relevant for clinical data, where co-recorded measurements can be jointly informative.
- The proposed interface can be applied to different relational forecasters rather than being tied to a single backbone, increasing its potential relevance.
- The experimental section follows a clear progression: it tests the interface across four architectures and three clinical datasets, compares MissHyper with existing forecasters, and examines the contributions of snapshot context, gating, and event-layout support through ablations. Overall, the experiments are reasonable and aligned with the paper’s main claims.
Critical weaknesses
Weakness 1
Proposition 1 provides limited support for the architectural diagnosis. Proposition 1 correctly shows that averaging and nonlinear transformation need not commute, but this is an elementary observation. More importantly, the proposition neither establishes that the proposed ordering is preferable nor that a relational network cannot recover the relevant context.
Weakness 2
Variable identity is not explicitly represented in the snapshot context. Equation 5 constructs each event embedding from its value, query flag, and support, but not from its variable identity. Therefore, measurements from different variables may be treated identically when these inputs coincide, even though their meanings differ. This design may remove variable-specific information before snapshot aggregation. The paper should justify this choice and discuss it as a limitation.
Weakness 3
Clarity and organization. Several central concepts and pieces of notation are introduced either too late or without sufficient definition, making the proposed method unnecessarily difficult to follow.
-
3.1 The problem statement is not presented in the clearest order. The opening paragraph introduces the main architectural issue and defines pre-propagation synchronicity loss before clearly delimiting and referencing the relevant family of “event-centric” models supplied with relational forecasters. The necessary context appears only later in the Introduction, in the discussion of event/set representations and relational forecasters. Defining the affected model class and citing representative methods at its first mention would make the motivation easier to understand and prevent the initial claim from appearing broader than intended.
-
3.2 Some basic concepts and notation in Section 4.1 are insufficiently defined. In particular, the paper does not explicitly define what constitutes an episode or an event. Moreover, in the event-layout matrix , the dimensions (L) and (C) are not clearly introduced. The clipped local window should also be formally defined. The role of the window size (w) is explained only at the end of the section, whereas it should be introduced when first appears.
-
3.3 Minor: The organization of the Related Work and hypergraph presentation could be improved. Related Work repeatedly restates the contribution, while some of its clearest scope statements would be more effective in the Introduction. It could instead focus on positioning the method and introducing the HyperIMTS backbone. Since MissHyper is the main realization, the methodological section should then clearly define its hypergraph construction—specifically, the event nodes, timestamp hyperedges, and variable hyperedges—before presenting the propagation operator in Section 4.4.
-
3.4 Minor: Figure 1 and 2 are never referenced in the main text.
Altogether, these things strongly indicate that the text was heavily generated by an LLM and the text not checked/reviewed thoroghly enough by a human.
Weakness 4
The proposed “pre-propagation” module is itself a form of relational aggregation. The operator pools co-timestamp event states into a shared summary and then broadcasts that summary back to update each event. This is effectively a timestamp-local message-passing step placed before the existing backbone. Keeping the original propagation machinery unchanged therefore does not mean that the full model has the same amount of relational computation as the baseline. As a result, the gains may come from adding an extra local interaction stage, rather than from repairing a distinct architectural failure. The paper would be clearer if it framed the contribution as an early timestamp-context layer and compared it against a matched additional message-passing baseline.
Weakness 5
Novelty relative to prior set- and context-pooling designs is limited and under-discussed. Pooling a shared summary and returning it to individual elements is an established pattern in Deep Sets and PointNet. Related ideas also appear in irregular time-series work such as SeFT, which combines set-level summaries with individual observations. Hypergraph aggregation frameworks such as AllSet already cover the general form of node-to-group-to-node updates. The gated interpolation likewise resembles familiar transform/carry mechanisms. The potentially novel part is the specific combination of timestamp-local pooling, event-layout support, and placement before several irregular forecasting backbones. That contribution is narrower than identifying a previously overlooked general principle, and the related-work discussion should make this positioning more precise.
Weakness 6
The ablations do not fully isolate why the method improves. The design adds several ingredients at once: an observed/query flag, a local layout feature, a context projection, a gate, and additional nonlinear computation. Support also appears in multiple places. A comparison against the original model therefore tests a bundle of changes rather than synchronicity restoration alone. In addition, the variant without snapshot restoration still retains a substantial fraction of the improvement over HyperIMTS on all three datasets. This does not invalidate the full model, but it weakens the claim that synchronous context is the main driver. A useful control would keep the module active while replacing the shared summary with a self-only summary, since a singleton timestamp still receives an extra gated nonlinear transformation even when no co-timestamp neighbor exists.
Questions for authors
-
Q1 - W1 : Can you provide a controlled ablation that places the same snapshot-context module before versus after the first relational block, while keeping the remaining architecture fixed? This would more directly test whether the reported gains arise from operation ordering rather than from the additional context module or model capacity.
-
Q2 - W2 : What limitations does excluding variable identity impose on the proposed notion of snapshot context?
-
Q3 - W4 : Can you compare the proposed module against an ordinary additional timestamp message-passing layer with matched features, parameter count, and computational budget?
-
Q4 - W6 : Can you report a self-only control in which the snapshot summary is replaced by each event’s own transformed state, so that the extra nonlinear capacity is kept but co-timestamp sharing is removed?