Papers › The population of galaxy-galaxy strong lenses in forthcoming optical imaging surveys
The population of galaxy-galaxy strong lenses in forthcoming optical imaging surveys
Thomas E Collett
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 and future imaging surveys represent significant improvements in depth, area and seeing compared to current data-sets. These improvements offer the opportunity to discover up to three orders of magnitude more galaxy-galaxy strong lenses than are currently known. In this work we forecast the number of lenses discoverable in forthcoming surveys and simulate their properties. We generate a population of statistically realistic strong lenses and simulate observations of this population for the Dark Energy Survey (DES), Large Synoptic Survey Telescope (LSST) and Euclid surveys. We verify our model against the galaxy-scale lens search of the Canada-France-Hawaii Telescope Legacy Survey (CFHTLS), predicting 250 discoverable lenses compared to 220 found by Gavazzi et al (2014). The predicted Einstein radius distribution is also remarkably similar to that found by Sonnenfeld et al (2013). For future surveys we find that, assuming Poisson limited lens galaxy subtraction, searches in DES, LSST and Euclid datasets should discover 2400, 120000, and 170000 galaxy-galaxy strong lenses respectively. Finders using blue minus red (g-i) difference imaging for lens subtraction can discover 1300 and 62000 lenses in DES and LSST. The uncertainties on the model are dominated by the high redshift source population which typically gives fractional errors on the discoverable lens number at the tens of percent level. We find that doubling the signal-to-noise ratio required for a lens to be detectable, approximately halves the number of detectable lenses in each survey, indicating the importance of understanding the selection function and sensitivity of future lens finders in interpreting strong lens statistics. We make our population forecasting and simulated observation codes publicly available so that the selection function of strong lens finders can easily be calibrated.
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="1507.02657")
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.
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 caoxiaoyue/sim_csst_lens. “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.
6aaa6b21ded8fb06 · report
0dd874a994e04fec · report
318d6ca3afd8cc13 · 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