{"id":"50e249b7-d930-402c-bc50-47295c0ad51b","arxiv_id":"2607.28833","paper_version":1,"verdict":"CONDITIONAL","confidence":"MODERATE","novelty_score":5.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":4,"one_line_summary":"With ten-minute ramping constraints in a 5,000-bus grid simulation, datacenter loads make slow, expensive generators 'must run', raising average off-peak marginal costs by roughly 8% in load-pocket regions.","lead":"Simulating a 5,000-bus grid, this paper finds that fast-ramping datacenter loads force slow, expensive generators to run even off-peak, raising average marginal costs by about 8%. The finding suggests common hourly, time-decoupled grid studies may understate the economic impact of datacenter connections.","discovery_kind":"new_application","skeptic_critique":{"model":"deepseek-v4-flash","headline":"Coupled vs decoupled comparison conflates temporal resolution with ramping constraints; missing control experiment undermines 'must-run' attribution.","rationale":"The reader's weakest assumption (South-area exclusion) does not directly threaten the West-area numbers that support the central claim. A more fundamental issue is the confounded experimental design: OPFLOW uses hourly averages while TCOPFLOW uses 10-minute profiles. The difference between the two includes both the effect of intra-hour load variability and the effect of ramping constraints. The paper attributes all of it to ramping constraints, but without a control (e.g., unlimited ramping), the observed 3-4 percentage point loading increase and 6-7 $/MWh marginal cost increase could be driven simply by the higher peak load seen in the 10-minute data. This is a clean, testable flaw: relaxing ramp limits would show whether the effect persists. If it persists, the 'must-run' mechanism is not the cause; if it disappears, the claim is supported. The paper's current evidence is therefore incomplete, and the verdict should remain conditional pending this additional experiment. My disagreement with the reader is on which issue is most load-bearing, not on the overall verdict.","tokens_in":6684,"tokens_out":10420,"duration_ms":115589,"concrete_test":"Re-run the West-area simulations with TCOPFLOW but set all generator ramp limits to a very large value (e.g., 1000 MW/min) so ramping never binds, keeping the same 10-minute datacenter profiles. Compare the resulting average loading and marginal cost to Table I. If the increase over OPFLOW persists, the effect is due to temporal resolution/peak load, not ramping constraints, and the central claim is unsupported. If the increase disappears, the 'must-run' attribution is confirmed. A supplementary test: run OPFLOW independently at 10-minute resolution to measure the resolution-only effect.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim attributes higher West-area generator loading and marginal cost in TCOPFLOW to ramping constraints forcing slow units to run. However, the decoupled OPFLOW baseline uses hourly average load, while TCOPFLOW uses the actual 10-minute datacenter profile with peaks up to 500 MW. The observed increase in Table I could simply reflect that the coupled simulation sees a higher peak load, not that ramp constraints bind. No control case isolates ramp limits: e.g., TCOPFLOW with effectively infinite ramping, or OPFLOW at 10-minute resolution. Without such a control, the 'must-run' mechanism and the headline 8% cost increase are not uniquely supported. The paper's exclusion of South-area cases (Section III, first paragraph) is not the most load-bearing concern because the West-area results, which carry the central claim, are unaffected by that exclusion.","agreement_with_reader":"disagree"},"referee_report":{"model":"deepseek-v4-flash","summary":"The paper compares temporally decoupled hourly ACOPF (OPFLOW) with time-coupled 10-minute ACOPF including generator ramping constraints (TCOPFLOW) on a modified, scaled 5000-bus IEEE 118-type system. It places large, fast-ramping datacenter loads at 350 candidate buses and reports that, in the West area, time coupling increases average generator loading by roughly 3.3–4.0 percentage points and average marginal cost by 5.6–6.9 $/MWh, an ~8% increase, which the authors attribute to slow, expensive generators becoming 'must run' to support datacenter ramps. The North area shows no difference, and all South-area coupled cases are excluded because they did not converge. The paper concludes that time-coupled analysis reveals hidden off-peak economic costs of datacenter ramping.","tokens_in":6915,"tokens_out":4318,"duration_ms":48736,"significance":"If the central result holds, the paper would provide a useful caution that standard hourly, temporally decoupled optimal power flow analyses may understate the system-cost and dispatch consequences of fast-ramping datacenter loads in congested, high-cost load pockets. The study covers many candidate locations (350) and presents a transparent scaling methodology with code availability, which are strengths. However, the current comparison conflates temporal resolution and load-profile representation with the presence of ramping constraints, and one results section directly contradicts the dispatch table for the steep window. These issues must be resolved before the economic-conclusion can be considered supported. The paper is a plausible contribution to the datacenter-grid-integration literature, but its headline quantitative claims are not yet uniquely established.","major_comments":[{"comment":"The central attribution of the West effect to ramping constraints is confounded. OPFLOW uses hourly average demand while TCOPFLOW uses the actual 10-minute datacenter profile with peaks up to 500 MW. The observed loading and marginal-cost increases could simply reflect the higher peak load seen by the coupled simulation. A control with effectively infinite ramping limits in TCOPFLOW, or an OPFLOW run at 10-minute resolution with the same load profile, is needed to isolate the ramp-constraint mechanism. Without such a control, the 'must-run' interpretation and the headline 8% cost increase are not uniquely supported.","section":"§II.A and Table I (comparison protocol)"},{"comment":"The steep/ramp-stress window results are internally inconsistent. Table I reports a 3.32 percentage-point loading increase and a 5.56 $/MWh marginal-cost increase for West in the steep window, yet §III.B states 'there is no difference between coupled and decoupled simulations, indicating that datacenters do not affect dispatch.' If this sentence refers only to the import difference, it should say so explicitly; as written it directly contradicts the dispatch results in Table I and undercuts the claim that both windows show the effect.","section":"§III.B vs Table I and Fig. 5"},{"comment":"The statement that 'loading of the most expensive West unit doubled' is not supported by any table, figure, or statistic in the manuscript. Since the abstract's 'up to 100% loading' depends on this unit-level claim, please provide unit-level dispatch results or remove the unsupported claim. The current Table I reports only area averages, which are a lower bound and do not justify the 'most expensive unit doubled' assertion.","section":"§III.A and abstract"},{"comment":"All 100 South-area time-coupled cases are excluded because they 'did not converge on ramping scenarios due to the local weak grid.' Non-convergence is attributed to physical infeasibility without supporting evidence. The paper should justify this attribution, for example by reporting solver exit status, attempting a feasibility restoration, or showing that relaxed formulations also fail. The exclusion removes roughly 29% of candidate placements and should be stated as a limitation in the abstract and conclusions. The West-area central result is not directly affected, but the scope of the study's claims is.","section":"§III, first paragraph (South exclusion)"},{"comment":"The paper claims 'economic consequences' and 'unexpectedly high system costs' but never reports total system production cost. Average marginal cost across generators is a proxy and does not directly yield system cost. Please report aggregate production cost for OPFLOW versus TCOPFLOW for each window and datacenter placement, or revise the economic-consequence language to match the proxy metrics actually computed.","section":"Title, abstract, and §III.A"}],"minor_comments":[{"comment":"The terminology 'module' versus 'area' is inconsistent, and the definition of D_m in Eq. (5) does not state units or explicitly clarify that the max is over hourly aggregated values. Please add units and define terms precisely.","section":"§II.A, Eqs. (3)–(5)"},{"comment":"The phrase 'up to four-digit precision' is unclear; it should say 'to four decimal places' or similar.","section":"§III.A"},{"comment":"The r values are reported without a clear description of what is being correlated (import values? deviations from the diagonal?) and with no formal definition. Add axis labels, a legend, and define r in the text.","section":"Fig. 5"},{"comment":"The 'average total cost per MW at Pmax' used as a cost indicator is not defined. Please specify the formula and whether it is the same as total cost divided by Pmax.","section":"Fig. 3"},{"comment":"The manuscript states that the full scaling code is in an online appendix, but no URL or repository identifier is given beyond the ExaGO software DOI. Please provide a direct link or DOI for the scaling code.","section":"References and code availability"}],"recommendation":"major_revision","confidential_remarks":"The main barrier is the missing control experiment: the current design cannot separate the effect of ramping constraints from the effect of using a higher-resolution, higher-peak load profile. The contradiction between Table I and §III.B for the steep window also suggests the authors may have misinterpreted one of their own results. These are fixable with additional simulations and careful rewriting, so I recommend major revision rather than rejection. The South exclusion, while disclosed, further limits the generality and should be presented more cautiously."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"Quick take: this paper builds a 5000-bus synthetic grid and runs time-coupled ACOPF for 350 datacenter placements, which is real work and a legitimate new application. The finding that West-area slow expensive units run more under coupled dispatch is plausible, and Table I shows a consistent direction for the peak window. But the paper does not actually isolate the effect of ramping constraints, and it contains an internal contradiction that needs fixing.\n\nThe thing the paper does well: the scale is appropriate for RTO-level interconnection studies, the datacenter load profiles come from Frontier observations, and the results are disaggregated by area in a way that exposes load-pocket effects. The West effect in the peak window (loading +3.97 points, marginal cost +6.87 $/MWh) is a concrete, falsifiable result. The authors also disclose the South non-convergence, which is honest.\n\nNow the soft spots, in order of severity.\n\nFirst, and load-bearing: the comparison conflates temporal resolution with ramping constraints. The decoupled baseline is OPFLOW on hourly average load; the coupled case is TCOPFLOW on the 10-minute profile. That changes both the time resolution and the presence of ramp limits. Without a control — say, TCOPFLOW with effectively infinite ramping, or OPFLOW at 10-minute resolution without coupling — you cannot tell whether the higher loading and marginal cost come from the ramp limits forcing slow units to run, or simply from the coupled simulation seeing a higher peak load (500 MW) and therefore dispatching more expensive generation. The paper's mechanism language ('must run') overreaches what this comparison can show.\n\nSecond, Section III.B explicitly says that for the ramp-stress window 'there is no difference between coupled and decoupled simulations,' which directly contradicts Table I's steep-window rows (West loading 79.74 vs 83.06, MC 89.75 vs 95.31). That is not a minor typo; it changes the paper's conclusion about which load profile matters.\n\nThird, smaller issues: the 'most expensive West unit doubled' claim is not backed by a figure or table, and the paper never reports total system cost despite the title and abstract promising 'economic consequences.'\n\nThe South exclusion is disclosed, and given the paper's West focus it's not the main problem.\n\nBottom line: a serious referee should see this. The question is policy-relevant, the modeling effort is substantial, and the missing control and the contradiction are fixable with additional simulations. As it stands, the central attribution is not yet established, so I would not cite the headline number until the control exists. I'd bring it to reading group as a case study on what counts as evidence in simulation studies.","headline":"Useful modeling study, but the headline 8% cost increase isn't uniquely attributable to ramp constraints without a proper control.","tokens_in":7377,"tokens_out":2415,"would_cite":false,"duration_ms":26290,"reading_group":"yes","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"This paper claims that when grid dispatch is simulated with ten-minute, time-coupled optimal power flow, fast-ramping datacenter loads in a congestible load pocket force slow, expensive generators to become effectively must-run, raising ave","keywords":["datacenter load ramping","ACOPF","time-coupled optimization","ramp constraints","must-run generators","load pockets","marginal cost","5000-bus test system"],"falsifier":"Rerun the time-coupled ACOPF for the 100 excluded South-area datacenter placements with a tighter solver tolerance, a different optimal-power-flow algorithm, or a small grid modification, and check whether they converge; if they converge without showing must-run loading of expensive slow units, the claim that weak load pockets produce this effect loses support. Alternatively, look at wholesale market data in a real load pocket before and after a large fast-ramping datacenter connects: if off-peak locational marginal prices show no uplift beyond the peak window, the modeled effect is not visibl","tokens_in":6611,"feed_emoji":"⚡","tokens_out":4279,"duration_ms":47604,"temperature":0.7,"pith_summary":"The paper tests how a 500 MW datacenter that can ramp at up to 5%/min affects dispatch on a congestible 5000-bus system, comparing hourly decoupled simulations with ten-minute time-coupled simulations that enforce ramping limits. The central claim is that the coupled simulations make slow, expensive generators in the West region behave as though they are must-run: they must be kept at higher output in early intervals to be ready for the datacenter's later ramp. As a result, average generator loading in the West rises by 3.3–4.0 percentage points and average marginal cost by 5.6–6.9 $/MWh, a 7–8% increase, concentrated in the peak-demand window. The paper also reports that all 100 South-area placements failed to converge in coupled runs, which it reads as evidence of a locally weak grid, and excludes them. The stakes are whether off-peak prices, not just peak prices, hide the true cost of firm datacenter connections.","feed_headline":"Datacenter ramps can make slow units 'must run', lifting costs 8%","feed_subtitle":"Time-coupled grid simulations show off-peak costs rise ~8% where fast-ramping datacenter loads force slow units to stay on.","key_machinery":"The organizing object is the time-coupled ACOPF (called TCOPFLOW in the paper) with a ten-minute discretization and generator ramping limits, contrasted with an hourly decoupled ACOPF (OPFLOW). The coupling is what does the work: it forces slow units to pre-ramp and stay at elevated output because feasibility in later intervals depends on earlier dispatch. Two metrics carry the comparison: percent generator loading (P_g/P_max) and marginal cost (b+2aP_g) at the dispatched point, plus an area import difference computed from line flows.","core_discovery":"When nodal, transmission-constrained ACOPF must remain feasible over a sequence of ten-minute intervals, ramping constraints couple dispatch decisions across time. Under that coupling, a slow-ramping generator that is needed for a future datacenter ramp cannot wait until the ramp begins; it must be pre-positioned at higher output, and once ramped it often cannot come down quickly. In the West-area simulations, this 'must run' effect raises average loading from about 79% to about 83% and average marginal cost from about 88–90 $/MWh to about 95 $/MWh, a 7–8% increase, while the North shows no difference. The paper concludes that time-decoupled or relaxed optimization misses these costs and tha","pith_inferences":["If the 100 non-convergent South cases are a solver or numerical artifact rather than physical infeasibility, excluding them could bias the area-level results; rerunning with a different solver, tolerance, or small grid modification is a direct test.","The must-run mechanism likely generalizes beyond datacenters to any large fast-ramping load, such as electrolyzers or electric-vehicle charging, in similarly constrained pockets.","In a real market, if the locational marginal price is set by the most expensive loaded unit, the price uplift could exceed the reported average marginal-cost increase, since the paper notes that loading of the most expensive West unit doubled.","The paper's suggested mitigation, battery storage in the load pocket, could be tested by adding a 100–500 MW storage resource next to the datacenter and measuring whether the must-run effect and cost increase shrink."],"forward_implications":["In load pockets with slow, expensive generation, firm datacenter connections can raise off-peak production costs by about 8%, a cost not captured in peak-only or hourly-decoupled studies.","The must-run effect appears only in the peak-demand window; the steep ramp-stress window shows no dispatch difference, so the shape of the datacenter load profile determines whether the effect materializes.","Time-coupled, ten-minute ACOPF fails to converge for all 100 South-area placements, indicating that a weak local grid may make some candidate datacenter sites infeasible before economic analysis begins.","Because North shows no difference, well-connected low-cost areas can absorb fast ramps without changing dispatch, so interconnection quality is decisive for mitigating the effect."],"fun_headline_variants":["Datacenter ramps make slow units must-run, adding 8% off-peak cost","Time-coupled ramping from datacenters hikes off-peak grid costs 8%","Datacenter bursts force slow generators to run, raising costs 8% off-peak","Hidden 8% cost rise: datacenter ramping makes slow units must-run"],"cache_read_input_tokens":2304,"weakest_assumption_plain":"The paper's load-bearing premise is that the non-convergence of all 100 South-area time-coupled cases is caused by local weak-grid infeasibility, not by numerical or modeling limits; if those cases were excluded for the wrong reason, the area-level dispatch and cost results could change.","fun_headline_variants_meta":{"raw":{"variants":["Datacenter ramps make slow units must-run, adding 8% off-peak cost","Time-coupled ramping from datacenters hikes off-peak grid costs 8%","Datacenter bursts force slow generators to run, raising costs 8% off-peak","Hidden 8% cost rise: datacenter ramping makes slow units must-run"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000509,"raw_usage":{"total_tokens":2308,"prompt_tokens":726,"completion_tokens":1582,"prompt_tokens_details":{"cached_tokens":256},"prompt_cache_hit_tokens":256,"prompt_cache_miss_tokens":470,"completion_tokens_details":{"reasoning_tokens":1488}},"tokens_in":470,"tokens_out":1582,"duration_ms":13309,"temperature":1.0,"reasoning_tokens":1488,"cache_read_input_tokens":256,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-03T01:32:17.560939+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"Rerun the time-coupled ACOPF for the 100 excluded South-area datacenter placements with a tighter solver tolerance, a different optimal-power-flow algorithm, or a small grid modification, and check whether they converge; if they converge without showing must-run loading of expensive slow units, the claim that weak load pockets produce this effect loses support. Alternatively, look at wholesale market data in a real load pocket before and after a large fast-ramping datacenter connects: if off-peak locational marginal prices show no uplift beyond the peak window, the modeled effect is not visibl","supporting_citations":[],"review_version":1}