Papers › Expressive architectures enhance interpretability of dynamics-based neural population models

Expressive architectures enhance interpretability of dynamics-based neural population models

7 Dec 2022arXiv:2212.03771archive 2025-07-28

Andrew R. Sedler, Christopher Versteeg, Chethan Pandarinath

Artificial neural networks that can recover latent dynamics from recorded neural activity may provide a powerful avenue for identifying and interpreting the dynamical motifs underlying biological computation. Given that neural variance alone does not uniquely determine a latent dynamical system, interpretable architectures should prioritize accurate and low-dimensional latent dynamics. In this work, we evaluated the performance of sequential autoencoders (SAEs) in recovering latent chaotic attractors from simulated neural datasets. We found that SAEs with widely-used recurrent neural network (RNN)-based dynamics were unable to infer accurate firing rates at the true latent state dimensionality, and that larger RNNs relied upon dynamical features not present in the data. On the other hand, SAEs with neural ordinary differential equation (NODE)-based dynamics inferred accurate rates at the true latent state dimensionality, while also recovering latent trajectories and fixed point structure. Ablations reveal that this is mainly because NODEs (1) allow use of higher-capacity multi-layer perceptrons (MLPs) to model the vector field and (2) predict the derivative rather than the next state. Decoupling the capacity of the dynamics model from its latent dimensionality enables NODEs to learn the requisite low-D dynamics where RNN cells fail. Additionally, the fact that the NODE predicts derivatives imposes a useful autoregressive prior on the latent states. The suboptimal interpretability of widely-used RNN-based dynamics may motivate substitution for alternative architectures, such as NODE, that enable learning of accurate dynamics in low-dimensional latent spaces.

PaperPDFCodeCode Syntology ran

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):

Code

Syntology 8 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 2 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 8 samples from 1 repository, 7 ran (7 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 on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

snel-repo/expressive-latent-dynamics-paper officialmentioned in paperpytorchApache-2.0Syntology: 8 samples, 7 ran (0 instrument-failed) · 1 unverified report

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

8 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 2 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · violated contract
5ran
1unverified

Licence: 2 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from snel-repo/expressive-latent-dynamics-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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

snel-repo/expressive-latent-dynamics-paper official repository 8 samples, 7 ran (0 instrument-failed) · 1 unverified
flatten in 178 papers
census: 4 implementations from 7 papers, 4 distinct outputs across 4 buckets, one shared input per bucket
paper_src/utils.py ran Apache-2.0 (permissive) · 50f9661f1274f758 · report fixture: signature dictionary:dict/0/?, level:list/1/empty · returned dict · level recorded 2026-09-25
get_sys_fps paper_src/fixedpoints.py ran Apache-2.0 (permissive) · 879de007fd614c22 · report fixture: signature system:System/0/? · returned tuple · level recorded 2026-09-25
has_image_loggers paper_src/callbacks.py ran · violated contract Apache-2.0 (permissive) here; the stored copy is pointer only · df9f400e259f725e · report fixture: signature loggers:list/1/callable · returned bool · level recorded 2026-09-25
linear_regression in 8 papers paper_src/metrics.py ran fingerprinted Apache-2.0 (permissive) · c71322c7a67019c6 · report fixture: signature preds:Tensor/2/float, targets:Tensor/2/float · returned Tensor · level recorded 2026-09-25
r2_score in 7 papers paper_src/metrics.py ran fingerprinted Apache-2.0 (permissive) · 93a4ed3809fa0894 · report fixture: signature preds:Tensor/2/float, targets:Tensor/2/float · returned Tensor · level recorded 2026-09-25
regression_r2_score paper_src/metrics.py ran fingerprinted Apache-2.0 (permissive) · dc9659beeedb385b · report fixture: signature preds:Tensor/2/float, targets:Tensor/2/float · returned Tensor · level recorded 2026-09-25
to_tensor in 92 papers
census: 8 implementations from 8 papers, 3 distinct outputs across 3 buckets, one shared input per bucket
paper_src/data.py ran · violated contract fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 99ba6555f6cb1bc6 · report fixture: signature array:list/1/float · returned Tensor · level recorded 2026-09-25
find_fixed_points paper_src/fixedpoints.py unverified Apache-2.0 (permissive) · b12edf20f511f76a · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

NODEfail

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