- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This papers proposes DC-XPIFM, a physics-informed foundation model framework for short-term AI data-center power forecasting. The work focuses on two dataset MIT and NLR, and proposes two energy models and fine-tunes three time-series foundation models (TimesFM-2.5, Chronos-2, Moirai). Among the physics-informed versions of the foundation models and non-physics-informed baselines, PI-TimesFM has the lowest averaged MAE/MAPE. A separate Bayesian inverse PINN fits RC parameters and reports identifiability diagnostics.
Critical strengths
- This paper addresses a very timely and practical problem on AI data center. With fast increasing AI workloads and associated power swings, it is important to be able to forecast the load accurately and understand the impact of increased load and dynamics involved.
- The proposed physics model is simple and seems applicable to different foundation model without needing to alter the models' architectures.
- The paper has very thorough baseline sweep.
Critical weaknesses
- The improvements from the physics-informed versions of FM are overstated from the MAE/MAPE perspective. Looking at Figure 1, other than (d) and (e) where PI-FM follows the dynamics of the true time series, PI-FM is not able to follow the dynamics, especially in (f) where FM and PI-FM are mostly flat. Dynamics are very important feature in planning the power grid load. This suggests that PI-FM is likely not usable in practice.
- Two separate physics models are proposed, one for MIT and one for NLR separately. This design undermines the generalization claim. Do the physics models work for an unseen dataset? Does a new model have to be proposed for AI data centers with different hardware structure?
- The discussions of the two dataset are scattered in a few places, and are introduced in the "method" section. Structure of the paper could be improved.
Questions for authors
I think the first two points in the weakness section are important to address, as they are foundational on this paper's contribution.
4 comments
Question 2: Two separate physics models are proposed, one for MIT and one for NLR separately. This design undermines the generalization claim. Do the physics models work for an unseen dataset? Does a new model have to be proposed for AI data centers with different hardware structure?
We thank the reviewer for the feedback provided, which has improved the quality of the submitted manuscript. It is worth noting that the MIT Supercloud dataset and the NLR dataset do not include cooling system data, and to the best of our knowledge, these are the only two publicly available datasets showing the impact of AI workloads on power consumption. However, it is important to note that cooling loads vary slowly (minutes-to-hours). The rapid transients motivating our work (exceeding 132 kW/s at rack level) primarily originate from GPU workloads, not cooling, which is why we focus on short-term forecasting (order of minutes). This is the first work to address this challenge using our XPIFM architecture. If facility-level data were available, cooling parameters can be incorporated as an additional slow-dynamics thermal node in the RC network. Nevertheless, our RC model operates at the GPU-board level, not at the facility level.
How is DC-XPiFM instantiated at an unseen data center, and does it transfer?
MIT provides GPU and memory signals, whereas NLR provides per-GPU power and temperature plus CPU power, with no memory channel. The procedure therefore uses only what every site has: GPU temperature, power, and the GPU datasheet. However, in practice, nvidia-smi reports the same exact GPU and memory fields at every facility. To the best of our knowledge, these are the only two public datasets that show how different AI workloads affect power. The physics adapts to this, because the heat balance is modular so other parameters can be incorporated as additional nodes in the RC network, increasing the number of RC parameters. We will include this analysis and the new equations incorporating cooling in the appendix. Nevertheless, for transfer, we use the data available everywhere: GPU temperature, power, and the GPU datasheet.
Therefore,
1. The procedure is DC-XPiFM's own constraint, calibrated without a meter. That constraint is the heat balance , and setting it up at a new site means fixing its constants and . With a power meter, our inverse PINN identifies them, as in the paper. Without one, we use the same equation once the temperature has settled (), which is accurate because a GPU responds thermally within about a second. It then becomes a straight line:
A new site therefore follows:
- Read two numbers from the GPU datasheet: the idle power and the maximum power .
- Record GPU temperature, with no power meter, and take its 1st and 99th percentiles as the idle and full-load temperatures.
- Check that the recording covers both idle and full load. Otherwise, the procedure reports failure.
- Convert temperature into power with the line through the two points,
\frac{P-P_{\mathrm{idle}}}{P_{\mathrm{max}}-P_{\mathrm{idle}}}=\frac{T-T_{1\\%}}{T_{99\\%}-T_{1\\%}}
and fine-tune the forecasting model on this estimated power.
The two points fix the same constants that the inverse PINN identifies with a meter: on the NLR training workloads, they give = 0.045 and 0.052 K/W with = 37.8 and 36.4 °C, against 0.040 and 0.047 K/W with 36–39 °C (on online inference, differs by 34%). Moreover, the training is the same, where the physics-informed loss equals training on a blend of metered and physics-implied power, and step 4 is the case in which no meter exists, so only the physics-implied power remains.
2. Does it transfer, or is it tuned to one dataset? Here, we hid the NLR power meter (H100 GPUs), set up DC-XPiFM from the datasheet and the temperature log alone, and used the hidden meter only to score the forecasts. Hence, no constant is fitted to power data. The error falls by 18.6% (TimesFM), 21.4% (Chronos-2), and 31.5% (Moirai) relative to the same forecasting model without fine-tuning. Two further results rule out dataset-specific tuning. First, constants fitted on MIT and carried over to NLR are 12.2% worse than the datasheet calibration. Second, we applied the same four steps unchanged to two more sites.
3. Each source of heterogeneity:
- GPU hardware: on the older V100 GPUs at MIT Supercloud and OLCF Summit, the unchanged calibration is weaker ( 0.60 and 0.63). On Summit, we found the cause in step 2: the 1st percentile is about 3 K colder than the temperature at which the GPUs idle. Taking the most frequent temperature as the idle point raises to 0.81 and lowers the forecast error by 42–44%. This correction needs no meter, but we chose it among three candidates using metered Summit data.
- Sampling frequency: NLR and MIT (0.1–0.2 s, as released) were resampled to one step per second (by averaging) to ensure consistency.
We have considered these aspects in the revised version of the paper and made sure that the generalization claim is not overstated.
I thank the authors for providing this detailed rebuttal. I think the authors have addressed my concern in the "Question 2", but for "Question 1", the main weakness is that the model is not able to follow the dynamics and I don't think it has been addressed. As a result, I will maintain my original assessment, as dynamics is a crucial aspect in the power system.
We thank the reviewer for their comment and for acknowledging that our response addressed Question 2. We agree that capturing power dynamics is essential. We have expanded the analysis of Figure 1, added trajectory comparisons, and evaluated ramp errors specifically to address Question 1.
We respectfully disagree with the general conclusion that the model is unable to follow dynamics. Your original review acknowledged that PI-FM follows the true dynamics in Figures 1(d) and 1(e). The expanded analysis provides further evidence across MIT Supercloud and NLR workloads:
- Figure 1(a): Power-slope changes under high-load operation; 37.73% lower MAE than the unconstrained FM.
- Figure 1(b): Abrupt power reduction and subsequent recovery; 57.85% lower MAE.
- Figure 1(c): Post-event behavior with reduced forecast drift; 31.34% lower MAE.
- Figure 1(d): Repeated oscillations during Stable Diffusion training; 30.81% lower MAE.
- Figure 1(e): A major low-power excursion and rebound during Llama-2 LoRA fine-tuning; 29.54% lower MAE.
- Figure 1(f): An abrupt load transition during online inference; 3.28% lower MAE.
These percentages concern the illustrated windows. The overall MIT improvements are 1.85% in MAE and 3.80% in MAPE, which we distinguish from these window-specific gains. The trajectory comparisons directly demonstrate tracking of repeated rises and falls, recovery, and workload-driven excursions.
We acknowledge your specific observation about Figure 1(f): both forecasts smooth repeated short-duration fluctuations. PI-FM captures the principal operating-level transition but does not reproduce every subsequent dip. This is a limitation, but it does not negate the dynamic tracking demonstrated in the other panels. Our claim is improved tracking of the evaluated dynamics, without guaranteeing exact reconstruction of every fluctuation, especially that this is a forecasting problem and not an estimation problem. We are forecasting several steps in the future. If it was an estimation problem (1 step in the future), we would be able to reconstruct the trajectory fully even better than the vanilla baseline FM. This analysis is also added in the revised version of the paper.
More directly, we introduced ramp MAE to quantify errors in power changes:
| Ramp MAE per node (W) | Without fine-tuning | With Physics | Change |
|---|---|---|---|
| TimesFM | 459 | 399 | −13.1% [−15.8, −10.7] |
| Chronos-2 | 461 | 376 | −15.4% [−21.1, −9.9] |
| Moirai | 572 | 402 | −29.3% [−31.5, −26.9] |
Ramp MAE decreases in all 18 paired runs for each model and on every evaluated workload: Stable Diffusion improves by 9–31%, LoRA by 4–30%, and online inference by 19–32%. On windows containing a power jump, errors decrease by 17%, 19%, and 31% for TimesFM, Chronos-2, and Moirai, respectively. These results directly address dynamic tracking beyond aggregate power-level MAE/MAPE and selected visual examples.
The method explicitly incorporates dynamic relationships during adaptation. As detailed in Section 3.3 and Appendix B, the objective includes energy-balance residuals, their step-to-step variation, and disagreement between forecast power rates and those implied by the RC equations. We also provided the analytical ODE solution and discussed its relationship to oscillation-like workloads and step-load responses.
Our previous response additionally reported that physics-informed adaptation reduces drift from pretrained weights by approximately 51%, improves NLR workload balanced accuracy from 0.821 to 0.893, and increases power-event AUROC from 0.879 to 0.894 on NLR and 0.523 to 0.568 on MIT. These representation-level results complement the direct trajectory and ramp-error evidence.
We have also added more forecast windows and comparisons among physics alone, XPIFM, and vanilla FM to make their trajectory differences explicit. The inverse-PINN analysis provides complementary physical verification through parameter identification and comparison with recursive least squares, as elaborated in the revised manuscript.
Practical deployment must be assessed against a specific operational task and timescale. However, the smoothing observed in Figure 1(f) does not establish general practical unusability. The expanded trajectories, consistent ramp-MAE reductions, and improvements on power-jump windows support our conclusion that physics-informed adaptation improves tracking of the evaluated power dynamics.
We respectfully ask that Question 1 be reassessed in light of this evidence. We also welcome any feedback that would improve the quality of the revised version of the paper.
Question 1: improvements from the physics-informed versions of FM
We thank the reviewer for this comment. Incorporating the physics component was found to be valid and useful for modeling the hardware. As an extra loss term when a power meter is available, however, its gain is not specific to the physics. We address each part of the question in turn.
1. Controlled ablation of each term: We removed each of the four loss terms in turn, and we also used each one alone. The table gives the change in forecast error (MAE) relative to ordinary fine-tuning without physics:
The full loss gives −1.74% [−2.21, −1.27] lower error (better than the baseline).
2. Further tests to prove the improvement of incorporating Physics, especially when the power data is missing:
Without a meter, it was observed that the physics gain is even more prominent, where the physics-implied power is then the only training signal, and it lowers the error by 19–32%. The physics therefore helps most where measurements are missing.
3. The physics helps where it is used as a model of the hardware.
T(t)=Ta+RPˉ+1+ω2τ2RP^sin(ωt−arctanωτ)+Ke−t/τ,τ=RC,
which states how strongly and how late temperature follows power. With the inverse-PINN constants (τ about 1 min), it reproduces 72–107% of the response measured on MIT at periods from 5 min to 1 h, against 1–5% with the constants obtained using recursive least squares (τ about 3 h). The oscillatory term in the ODE solution also explains why XPIFM captures the transients better than the vanilla model. This is further substantiated by the new metric introduced: ramp MAE, which is the error on points within 2 min of a true power ramp, where a step is a one-second change larger than twice the usual change. The results obtained are as follows:
The ramp MAE falls in 18 of 18 paired runs for each model and on every workload (Stable Diffusion −9% to −31%, LoRA −4% to −30%, online inference −19% to −32%). On windows that contain a power jump, the error falls by 17%, 19%, and 31%.
4. Which errors can fine-tuning and added telemetry not address? The unannounced workload change: on NLR, ordinary fine-tuning has 95 W error on steady windows but 456 W on windows with a power jump. More telemetry does not help, because temperature follows power (by about 0.2 s on NLR) and never leads it. In fact, forecasting power and temperature jointly under the physics loss worsens the power error by 4.4% and 6.4%. Moreover, the paper proved that physics influences what the model learns. As mentioned in the paper, XPIFM stays 51% closer to its pretrained weights than ordinary fine-tuning. Also, a fixed classifier on its embeddings identifies the five NLR workloads with balanced accuracy 0.893, against 0.821, and detects power events with AUROC 0.894 against 0.879 on NLR (0.568 against 0.523 on MIT).
5. Robustness: Without a meter, the physics gain is consistent, where the error falls in every workload, on every model:
Hence, without a meter, the gain holds at every horizon, workload, and model.