Papers › DiffCharge: Generating EV Charging Scenarios via a Denoising Diffusion Model
DiffCharge: Generating EV Charging Scenarios via a Denoising Diffusion Model
Siyang Li, Hui Xiong, Yize Chen
Recent proliferation of electric vehicle (EV) charging events has brought prominent stress over power grid operation. Due to the stochastic and volatile EV charging behaviors, the induced charging loads are extremely uncertain, posing modeling and control challenges for grid operators and charging management. Generating EV charging scenarios would aid via synthesizing a myriad of realistic charging scenarios. To this end, we propose a novel denoising Diffusion-based Charging scenario generation model DiffCharge, which is capable of generating a broad variety of realistic EV charging profiles with distinctive temporal properties. It is able to progressively convert the simply known Gaussian noise to genuine charging time-series data, by learning a parameterized reversal of a forward diffusion process. Besides, we leverage the multi-head self-attention and prior conditions to capture the temporal correlations and unique information associated with EV or charging station types in real charging profiles. Moreover, We demonstrate the superiority of DiffCharge on extensive real-world charging datasets, as well as the efficacy on EV integration in power distribution grids.
In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2308.09857")
Code
Syntology Ran 8 of 10 code samples harvested from 1 repository linked to this paper; 2 have no recorded run. Of those that ran: 8 ran with no contract checked.
By repository: official repository: 10 samples from 1 repository, 8 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
10 samples harvested; 8 ran; 0 honoured the contract we drafted; 2 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.
Licence: 10 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from lsy-cython/diffcharge. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.
Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
264fc915e9cd432a · report
f22d8d83e14938f4 · report
6a26c8f6a509c954 · report
b5cf8a26b931c7ab · report
aeead62832c56cfc · report
66a2bd5f1f573cca · report
9f53f2f802548aa4 · report
153d8a50757d7351 · report
23fb7a848ebd1181 · report
b0e79049b15ba425 · report
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections