Papers › Biophysically grounded mean-field models of neural populations under electrical stimulation
Biophysically grounded mean-field models of neural populations under electrical stimulation
Caglar Cakan, Klaus Obermayer
Electrical stimulation of neural systems is a key tool for understanding neural dynamics and ultimately for developing clinical treatments. Many applications of electrical stimulation affect large populations of neurons. However, computational models of large networks of spiking neurons are inherently hard to simulate and analyze. We evaluate a reduced mean-field model of excitatory and inhibitory adaptive exponential integrate-and-fire (AdEx) neurons which can be used to efficiently study the effects of electrical stimulation on large neural populations. The rich dynamical properties of this basic cortical model are described in detail and validated using large network simulations. Bifurcation diagrams reflecting the network's state reveal asynchronous up- and down-states, bistable regimes, and oscillatory regions corresponding to fast excitation-inhibition and slow excitation-adaptation feedback loops. The biophysical parameters of the AdEx neuron can be coupled to an electric field with realistic field strengths which then can be propagated up to the population description.We show how on the edge of bifurcation, direct electrical inputs cause network state transitions, such as turning on and off oscillations of the population rate. Oscillatory input can frequency-entrain and phase-lock endogenous oscillations. Relatively weak electric field strengths on the order of 1 V/m are able to produce these effects, indicating that field effects are strongly amplified in the network. The effects of time-varying external stimulation are well-predicted by the mean-field model, further underpinning the utility of low-dimensional neural mass models.
In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="1906.00676")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="1906.00676", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="1906.00676")
Code
Syntology 22 code samples harvested from 2 repositories linked to this paper: 13 ran (of which 0 constructed an object rather than computing a result; 13 with no instrument failure: 0 honoured, 0 violated, 13 with no contract checked; 0 where Syntology's instrument failed) · 9 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: official repository: 9 samples from 1 repository, 4 ran (4 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 13 samples from 1 repository, 9 ran (9 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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
22 samples harvested: 13 ran (of which 0 constructed an object rather than computing a result; 13 with no instrument failure: 0 honoured, 0 violated, 13 with no contract checked; 0 where Syntology's instrument failed) · 9 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 0 of the 22 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.
Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (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 are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. 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 six 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; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. 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.
300e3bef7215b2da · report
fixture: signature lengthMat:Tensor/2/float, signalV:float/0/float, segmentLength:float/0/float · returned Tensor · level recorded 2026-09-25 f57cc8f2ce5a29df · report
fixture: signature N:int/0/int, seed:int/0/int · returned tuple · level recorded 2026-09-25 6b4da69eae403d37 · report
fixture: signature fName:str/0/str · returned KeysViewHDF5 · level recorded 2026-09-25 c0b62e8217717154 · report
fixture: signature table:ndarray/2/float, xid1:int64/0/int, yid1:int64/0/int, dxid:float/0/float, dyid:float/0/float · returned float · level recorded 2026-09-25 7e8bf6e80c3d758e · report
46f56cd0bc02669f · report
e0b7fc10694d1349 · report
b014d12b457be069 · report
fc76b7c559c08b5c · report
fixture: signature original:float/0/float, target:ndarray/2/float · returned ndarray · level recorded 2026-09-24 d9308e8c6fa62ed5 · report
fixture: signature lengthMat:Tensor/2/float, signalV:float/0/float, segmentLength:float/0/float · returned Tensor · level recorded 2026-09-24 c468bd2caba6ea6d · report
fixture: signature a:ndarray/2/float, axis:str/0/str · returned ndarray · level recorded 2026-09-24 7b33507ea7cdb6c7 · report
fixture: signature nested_dict:dict/0/?, parent_key:str/0/str, sep:str/0/str · returned dict · level recorded 2026-09-24 76b5f97d544101bd · report
fixture: signature filename:str/0/str · returned list · level recorded 2026-09-25 119c7524954dc07a · report
fixture: signature traces:ndarray/2/float, smoothing:float/0/float, distance:int/0/int, prominence:float/0/float · returned ndarray · level recorded 2026-09-24 1a4bb8f2e387db71 · report
fixture: signature M1:ndarray/2/float, M2:ndarray/2/float · returned float64 · level recorded 2026-09-24 68c2b2ecd6f94d27 · report
fixture: signature dct:dict/0/?, replace_dict:dict/0/? · returned dict · level recorded 2026-09-24 8c4b676da76c291c · report
fixture: signature x:ndarray/1/float, y:ndarray/1/float, w:ndarray/1/float · returned float64 · level recorded 2026-09-24 c9fd8edcc38454b1 · report
95c1521c9281311c · report
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
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