Papers › Cosmology-informed neural networks to solve the background dynamics of the Universe
Cosmology-informed neural networks to solve the background dynamics of the Universe
Augusto T. Chantada, Susana J. Landau, Pavlos Protopapas, Claudia G. Scóccola, Cecilia Garraffo
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
The field of machine learning has drawn increasing interest from various other fields due to the success of its methods at solving a plethora of different problems. An application of these has been to train artificial neural networks to solve differential equations without the need of a numerical solver. This particular application offers an alternative to conventional numerical methods, with advantages such as lower memory required to store solutions, parallelization, and, in some cases, a lower overall computational cost than its numerical counterparts. In this work, we train artificial neural networks to represent a bundle of solutions of the differential equations that govern the background dynamics of the Universe for four different models. The models we have chosen are ΛCDM, the Chevallier-Polarski-Linder parametric dark energy model, a quintessence model with an exponential potential, and the Hu-Sawicki f(R) model. We use the solutions that the networks provide to perform statistical analyses to estimate the values of each model's parameters with observational data; namely, estimates of the Hubble parameter from cosmic chronometers, type Ia supernovae data from the Pantheon compilation, and measurements from baryon acoustic oscillations. The results we obtain for all models match similar estimations done in the literature using numerical solvers. In addition, we estimate the error of the solutions that the trained networks provide by comparing them with the analytical solution when there is one, or to a high-precision numerical solution when there is not. Through these estimations we find that the error of the solutions is at most ∼1% in the region of the parameter space that concerns the 95% confidence regions that we find using the data, for all models and all statistical analyses performed in this work.
In Syntology View this paper on Syntology: its repositories, every harvested function with whether it ran, its licence and the call to fetch it.
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="2205.02945")
Code
Syntology Ran 1 of 1 code samples harvested from 1 repository linked to this paper; 0 have no recorded run. Of those that ran: 1 ran · our draft was wrong.
By repository: official repository: 1 sample from 1 repository, 1 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
1 sample harvested; 1 ran; 0 honoured the contract we drafted; 0 have no recorded run. Read from Syntology's graph 2026-09-25; that is when this build read the record, not when the samples ran.
Licence: 0 of the 1 sample 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 at-chantada/cosmo-nets. “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.
45efd6d6b157e7c7 · 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