Papers › Validating full-spectrum fitting with a synthetic integral-field spectroscopic...
Validating full-spectrum fitting with a synthetic integral-field spectroscopic observation of the Milky Way
Zixian Wang, Michael R. Hayden, Sanjib Sharma, Jesse van de Sande, Joss Bland-Hawthorn, Sam Vaughan, Marie Martig, Francesca Pinna
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.
Ongoing deep IFS observations of disk galaxies provide opportunities for comparison with the Milky Way (MW) to understand galaxy evolution. However, such comparisons are marred by many challenges such as selection effects, differences in observations and methodology, and proper validation of full-spectrum fitting methods. In this study, we present a novel code GalCraft to address these challenges by generating mock IFS data cubes of the MW using simple stellar population models and a mock MW stellar catalog derived from E-Galaxia. We use the widely adopted full-spectrum fitting code pPXF to investigate the ability to recover kinematics and stellar populations for an edge-on mock MW IFS observation. We confirm that differences in kinematics, mean age, [M/H], and [α/Fe] between thin and thick disks can be distinguished. However, the age distribution is overestimated in the ranges between 2 - 4 and 12 - 14 Gyr compared to the expected values. This is likely due to the age spacing and degeneracy of SSP templates. We find systematic offsets in the recovered kinematics due to insufficient spectral resolution and the variation of line-of-sight velocity distribution with age and [M/H]. With future higher resolution and multi-[α/Fe] SSP templates, GalCraft will be useful to validate key signatures such as [α/Fe]-[M/H] distribution at different R and |z| and potentially infer radial migration and kinematic heating efficiency to study detailed chemodynamical evolution of MW-like galaxies.
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="2310.18258")
Code
Syntology Ran 7 of 9 code samples harvested from 1 repository linked to this paper; 2 have no recorded run. Of those that ran: 7 ran with no contract checked.
By repository: official repository: 9 samples from 1 repository, 7 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
9 samples harvested; 7 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: 0 of the 9 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 purmortal/galcraft. “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.
93acb5df56ef8231 · report
3ec84add278df4fc · report
66acd156f11bf57f · report
c1b7e6282c9d181b · report
ec04e5b69f44d566 · report
ce8f7e303c8c8a20 · report
e63cc92982955367 · report
b2edc7d50a0b4220 · report
6d54f80f09fbc2e0 · 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