Papers › Core-collapse supernova equations of state based on neutron star observations

Core-collapse supernova equations of state based on neutron star observations

9 Jul 2012arXiv:1207.2184links table onlyarchive 2025-07-28

Andrew W. Steiner, Matthias Hempel, Tobias Fischer

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.

Many of the currently available equations of state for core-collapse supernova simulations give large neutron star radii and do not provide large enough neutron star masses, both of which are inconsistent with some recent neutron star observations. In addition, one of the critical uncertainties in the nucleon-nucleon interaction, the nuclear symmetry energy, is not fully explored by the currently available equations of state. In this article, we construct two new equations of state which match recent neutron star observations and provide more flexibility in studying the dependence on nuclear matter properties. The equations of state are also provided in tabular form, covering a wide range in density, temperature and asymmetry, suitable for astrophysical simulations. These new equations of state are implemented into our spherically symmetric core-collapse supernova model, which is based on general relativistic radiation hydrodynamics with three-flavor Boltzmann neutrino transport. The results are compared with commonly used equations of state in supernova simulations of 15 and 40 solar mass progenitors. We do not find any simple correlations between individual nuclear matter properties at saturation and the outcome of these simulations. However, the new equations of state lead to the most compact neutron stars among the relativistic mean-field models which we considered. The new models also obey the previously observed correlation between the time to black hole formation and the maximum mass of an s=4 neutron star.

PaperPDFCodeCode Syntology ran

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="1207.2184")

Code

Syntology Ran 0 of 3 code samples harvested from 1 repository linked to this paper; 3 have no recorded run.

By repository: community (archive-listed): 3 samples from 1 repository, 0 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

3 samples harvested; 0 ran; 0 honoured the contract we drafted; 3 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.

3unverified

Licence: 0 of the 3 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 aarondjohnson/bns_source_confusion. “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.

Mceta_from_m1m2 aarondjohnson/bns_source_confusion/python/events.py community (archive-listed) unverified MIT (permissive) · 873db42dc8f539f0 · report
md_sfr_td aarondjohnson/bns_source_confusion/python/events.py community (archive-listed) unverified MIT (permissive) · 2ecdda3fb9094f9f · report
redshift_Mc aarondjohnson/bns_source_confusion/python/events.py community (archive-listed) unverified MIT (permissive) · 273ee36161b7fd9d · 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