Papers › Metallicity estimation of RR Lyrae stars from their I-band light curves

Metallicity estimation of RR Lyrae stars from their I-band light curves

13 Jul 2021arXiv:2107.05983links table onlyarchive 2025-07-28

István Dékány, Eva K. Grebel, Grzegorz Pojmański

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.

We have revisited the problem of metallicity prediction of RR Lyrae stars from their near-infrared light curves in the Cousins I waveband. Our study is based on high-quality time-series photometry and state-of-the-art high-resolution spectroscopic abundance measurements of 80 fundamental-mode (RRab) and 24 first-overtone (RRc) stars, spanning ∼[-2.7,+0.18] dex and ∼[-3,-0.5] dex ranges, respectively. Employing machine-learning methods, we investigated various light-curve representations and regression models to identify their optimal form for our objective. Accurate new empirical relations between the [Fe/H] iron abundance and the light-curve parameters have been obtained using Bayesian regression for both RRab and RRc stars with mean absolute prediction errors of 0.16 and 0.18 dex, respectively. We found that earlier I-band [Fe/H] estimates had a systematic positive bias of up to ∼0.4 dex in the metal-poor regime. Our new predictive models were deployed on large ensembles of RR Lyrae stars to obtain photometric metallicity distribution functions (MDFs) for various old stellar populations in and around the Milky Way. We find that the mode of the old bulge component's MDF is approximately -1.4 dex, in remarkable agreement with the latest spectroscopic result. Furthermore, we derive MDF modes of -1.83, -2.13, and -1.77 dex for the Large and Small Magellanic Clouds, and the Sagittarius dwarf galaxy, respectively.

Code

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; 6 ran; 0 honoured the contract we drafted; 2 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 8 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; each sample names its own and says which. “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.

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