- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes ETDGN, an Event-Triggered Disentangled Graph Network for traffic forecasting. The main idea is to move dynamic graph adaptation from a purely time-driven or correlation-driven mechanism to an event-triggered mechanism. ETDGN first builds a routine traffic reference by decomposing traffic observations into trend, seasonal, and event-residual components. It then estimates event evidence from explicit context, traffic residuals, and spatially coherent abnormalities. When event evidence is sufficiently strong, the model constructs an event-conditioned graph, propagates event influence over this graph, and uses a gated residual branch to correct the routine forecast.
Overall, the paper addresses an important and practical problem in traffic forecasting: spatial dependencies may change abruptly due to accidents, weather, holidays, or other external events. The proposed framework is coherent, well motivated, and supported by extensive experiments.
Critical strengths
-
The motivation is clear and compelling. The paper convincingly argues that dynamic graph updates should not be driven only by time progression or historical correlations, since real traffic dependencies are often reshaped by external or latent events.
-
The model design is coherent and well aligned with the stated challenges. The event trigger, event-conditioned graph, propagation module, memory retrieval, and gated residual correction each serve a clear role in the overall architecture.
-
The separation between routine dynamics and event-induced deviations is a strong design choice. Modeling event effects as residual corrections over a routine forecast is intuitive and helps avoid contaminating stable trend and periodic patterns.
-
The experimental results are strong across multiple datasets, metrics, and forecasting horizons. The ablation study also supports the usefulness of event-triggered graph updating, event-conditioned graph construction, propagation, and disentanglement.
-
The qualitative analyses are useful. The event-pattern case study and propagation visualizations provide intuition about how the model responds to event-related conditions and how event influence evolves over space and time.
Critical weaknesses
-
For datasets without explicit event annotations, the notion of “event” could be more clearly grounded. The paper appears to derive event supervision from routine forecasting residuals in such cases. This is a reasonable practical strategy, but it makes the event trigger closer to a residual-abnormality trigger than a directly verified external-event trigger. The paper would benefit from a clearer discussion of this distinction.
-
The ablation study shows that the event branch and propagation module improve forecasting accuracy, but it does not report how often the event branch is activated. Since the central claim is event-triggered computation, activation statistics would be important for interpretation. I suggest reporting the event-branch activation rate on each dataset, ideally broken down by normal vs. event-related periods when external contexts are available. It would also be useful to correlate trigger intensity or activation rate with forecasting improvement, to show whether the event branch mainly helps during event-affected intervals rather than simply acting as additional model capacity.
-
The qualitative propagation analysis is compelling, but stronger quantitative validation would further support the interpretability claim. For example, if real incident locations, weather-affected regions, or event windows are available, it would be helpful to evaluate whether the learned event propagation aligns with these external signals.
Questions for authors
- What are the event-branch activation rates on PEMS-Stream, CA-Stream, PEMS08, and TaxiBJ?
- On datasets without explicit event annotations, how sensitive is the method to the residual-based pseudo-event threshold?
- Can the authors report activation rates separately for normal periods and event-related periods on TaxiBJ?
- Does the event branch contribute most of the performance improvement during high-trigger-intensity intervals?
- Can the learned event propagation be quantitatively compared with real incident, weather, or holiday-event signals when such information is available?