Papers › Extending the SAGA Survey (xSAGA) I: Satellite Radial Profiles as a Function of Host...
Extending the SAGA Survey (xSAGA) I: Satellite Radial Profiles as a Function of Host Galaxy Properties
John F. Wu, J. E. G. Peek, Erik J. Tollerud, Yao-Yuan Mao, Ethan O. Nadler, Marla Geha, Risa H. Wechsler, Nitya Kallivayalil, Benjamin J. Weiner
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 present "Extending the Satellites Around Galactic Analogs Survey" (xSAGA), a method for identifying low-z galaxies on the basis of optical imaging, and results on the spatial distributions of xSAGA satellites around host galaxies. Using spectroscopic redshift catalogs from the SAGA Survey as a training data set, we have optimized a convolutional neural network (CNN) to identify z < 0.03 galaxies from more distant objects using image cutouts from the DESI Legacy Imaging Surveys. From the sample of > 100,000 CNN-selected low-z galaxies, we identify >20,000 probable satellites located between 36-300 projected kpc from NASA-Sloan Atlas central galaxies in the stellar mass range 9.5 < log(M_⋆/M_⊙) < 11. We characterize the incompleteness and contamination for CNN-selected samples, and apply corrections in order to estimate the true number of satellites as a function of projected radial distance from their hosts. Satellite richness depends strongly on host stellar mass, such that more massive host galaxies have more satellites, and on host morphology, such that elliptical hosts have more satellites than disky hosts with comparable stellar masses. We also find a strong inverse correlation between satellite richness and the magnitude gap between a host and its brightest satellite. The normalized satellite radial distribution between 36-300 kpc does not depend strongly on host stellar mass, morphology, or magnitude gap. The satellite abundances and radial distributions we measure are in reasonable agreement with predictions from hydrodynamic simulations. Our results deliver unprecedented statistical power for studying satellite galaxy populations, and highlight the promise of using machine learning for extending galaxy samples of wide-area surveys.
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="2112.01542")
Code
Syntology Ran 2 of 2 code samples harvested from 1 repository linked to this paper; 0 have no recorded run. Of those that ran: 2 ran · our draft was wrong.
By repository: official repository: 2 samples from 1 repository, 2 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
2 samples harvested; 2 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: 2 of the 2 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 jwuphysics/xsaga. “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.
4f4be33e01dd6c71 · report
a7c715170cecdc4f · 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