Jiande Wu

Multi-source transformer forecasting

A transformer that fuses case, death, and social media sentiment data for county-level COVID-19 forecasting, evaluated retrospectively across 46 South Carolina counties and three Omicron waves.

Paper · Code · PyTorch · 2025

Wu J, Tanim S, Woo M, Ahammed T, Bleichrodt AM, Rennert L. Epidemics 53 (2025) 100865. Open access (CC BY 4.0).

Problem

Epidemic forecasts often depend only on delayed indicators such as confirmed cases. Prior work using social media signals focused on detecting outbreaks early, and often only in counties of more than a million people, which can miss outbreaks in less populous areas. The study asked whether a transformer that fuses epidemiological records with county-level social media sentiment could forecast cases and deaths for all 46 counties of one state.

Data

Model

Evaluation design

Results

Median county agreement across the three waves:

Target1 week ahead5 weeks ahead
Cases74.0–82.6%68.7–79.6%
Deaths83.2–86.3%84.3–87.2%

Against the baselines, as reported in the paper's comparison of longer- and shorter-term forecasts:

Horizon, metricThis modelPersistenceARIMA
5 weeks, agreement81.9%61.2%59.9%
5 weeks, RMSE35.198.4106.9
5 weeks, MAE23.072.177.6
7 days, agreement74.5%71.6%55.9%

The advantage over persistence is large at five weeks and small at seven days, where carrying the last value forward is a strong baseline. Accuracy falls as the horizon grows, and predicted peaks consistently lag the observed ones.

What social media data added

Change in median case agreement from adding sentiment data, by wave (range over horizons):

Wave1–7 days ahead1–5 weeks ahead
1 (B.1.1.529)+4.94 to +10.50%+9.04 to +14.82%
2 (BA.4/BA.5)−4.22 to +4.06%−2.69 to +10.09%
3 (BQ.1/XBB.1.5)−3.57 to +3.53%−0.49 to +7.52%

The gain was clear in the first Omicron wave, a period of rapid change and heavy public discussion, and mixed afterwards. Overall the paper describes it as a mild to moderate improvement.

Limitations

What carried forward

Later work addresses the first two limitations. Evaluating on data as it was published at the time, rather than on later revised values, is the basis of ObsAwareData, which keeps every release and a reliability flag on each value, and of the planned real-time benchmark in resplens, which is to report probabilistic scores.