Reference desk / inputs, arithmetic, evidence
Three datacenter power-continuity cases you can calculate by hand, run in the browser and reproduce in Python.
307.8 seconds in this charging-disabled example. Stored energy × discharge efficiency × distribution efficiency gives delivered energy: 100 × 0.90 × 0.95 = 85.5 kWh. Divide by 1,000 kW and multiply by 3,600 to convert hours to seconds. With 50 kWh, the same assumptions give 153.9 seconds.
These are durations after the utility outage. With the outage beginning at 300 s, depletion occurs at 607.8 s or 453.9 s elapsed. An event timestamp and a ride-through duration describe different quantities.
The battery cases use 1,000 kW IT demand, 100 or 50 kWh opening energy, charging disabled, utility and generator failure at 300 s and recovery at 900 s, 90% discharge efficiency and 95% distribution efficiency. For path maintenance, one 700 kW gross path remains for 600 s: it delivers 665 kW and leaves a 335 kW deficit.
307.8 seconds of battery ride-through
100 × 0.90 × 0.95 ÷ 1,000 × 3,600
Link to this result · Readable full report
Scenario JSON · Complete result JSON
Input SHA-256: a11b0d4078daef9a79e07f7969940203c23ccaa800c0a2c60cc5853b0acacfd0
Run: 598f3279493596e75400. Result at the cited source revision.
153.9 seconds of battery ride-through
50 × 0.90 × 0.95 ÷ 1,000 × 3,600
Link to this result · Readable full report
Scenario JSON · Complete result JSON
Input SHA-256: 0db72b981fa59c8a566e5610fd8627f4c623baeb8bb2662d22c5cae246a2b8b9
Run: b27bf2eb3e3f3a603202. Result at the cited source revision.
55.833 kWh unserved over ten minutes
700 × 0.95 = 665 kW served; 1,000 − 665 = 335 kW unserved
Link to this result · Readable full report
Scenario JSON · Complete result JSON
Input SHA-256: 6b446789e2f755b9ac1ac81896c7f0d85827a9a03b6ceedfd8fbdc6cb3b775dd
Run: bdbd07fc183ea54c6cba. Result at the cited source revision.
| Case | Requested IT | Served IT | Unserved IT |
|---|---|---|---|
| 100 kWh at 1 MW | 500 | 418.833333 | 81.166667 |
| 50 kWh at 1 MW | 500 | 376.083333 | 123.916667 |
| One 700 kW surviving path | 500 | 444.166667 | 55.833333 |
The energy table rounds to six decimal places; the case summaries may be shorter. JSON records retain the complete decimal strings and interval ledger. Input-hash filenames identify each configuration; retain the source revision and manifest when citing a result.
python scripts/build_evidence.py --output outputs/reproduction-1.0.0
python scripts/build_evidence.py --verify outputs/reproduction-1.0.0Reconstruct the ledger from its terms, independently of the reported residual: source energy equals served IT energy plus the change in stored battery energy and the conversion losses. Requested IT energy equals served plus unserved IT energy.
Mohammad Rezwan Khan. Datacenter Twin Lab, version 1.0.0. Synthetic continuity reference cases. https://khanlab.co.technology/evidence/
For numerical reuse, include the case name, input SHA-256, engine version, result file and exact source revision. Documentation for this build: 5584954af4c82e5313fe1043306c1d82924c968f. Use the software citation record for author and repository details.
This is a software reproduction record, not a peer-reviewed paper or a calibrated facility dataset. No DOI or independent external reproduction is asserted. Original code and inputs are Apache-2.0; source notices describe the material included.
They support learning about finite reserve, losses, outage timing and path capacity for the stated synthetic inputs. They do not establish equipment suitability, facility uptime, grid adequacy, GPU job performance or physical safety. See the model scope and authorship and external reproduction protocol.