Papers › Detecting gravitational lenses using machine learning: exploring interpretability and...
Detecting gravitational lenses using machine learning: exploring interpretability and sensitivity to rare lensing configurations
Joshua Wilde, Stephen Serjeant, Jane M. Bromley, Hugh Dickinson, Leon V. E. Koopmans, R. Benton Metcalf
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.
Forthcoming large imaging surveys such as Euclid and the Vera Rubin Observatory Legacy Survey of Space and Time are expected to find more than 10⁵ strong gravitational lens systems, including many rare and exotic populations such as compound lenses, but these 10⁵ systems will be interspersed among much larger catalogues of ∼10⁹ galaxies. This volume of data is too much for visual inspection by volunteers alone to be feasible and gravitational lenses will only appear in a small fraction of these data which could cause a large amount of false positives. Machine learning is the obvious alternative but the algorithms' internal workings are not obviously interpretable, so their selection functions are opaque and it is not clear whether they would select against important rare populations. We design, build, and train several Convolutional Neural Networks (CNNs) to identify strong gravitational lenses using VIS, Y, J, and H bands of simulated data, with F1 scores between 0.83 and 0.91 on 100,000 test set images. We demonstrate for the first time that such CNNs do not select against compound lenses, obtaining recall scores as high as 76\% for compound arcs and 52\% for double rings. We verify this performance using Hubble Space Telescope (HST) and Hyper Suprime-Cam (HSC) data of all known compound lens systems. Finally, we explore for the first time the interpretability of these CNNs using Deep Dream, Guided Grad-CAM, and by exploring the kernels of the convolutional layers, to illuminate why CNNs succeed in compound lens selection.
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="2202.12776")
Code
Syntology Ran 0 of 2 code samples harvested from 1 repository linked to this paper; 2 have no recorded run.
By repository: official repository: 2 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
2 samples harvested; 0 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 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 JoshWilde/LensFindery-McLensFinderFace. “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.
1500e97d7f954935 · report
74d27d19736fe2e0 · 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