Metraipolis › archive › dc_406708593c68

GPUPHOT: A Python Framework for High-Performance GPU-Accelerated Photometry and Distributed Astronomical Data Reduction — arXiv:2609.32375

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.32375
License (as archived)
CC0-1.0
Archived
2026-10-07T22:12:19.139Z
SHA-256 of the archived text
9859e83c8abf717c6c448f5b659c65881b355cb7c5a29a1265fc73932c7c70ac
Stable URL of this page
https://metraipolis.com/documento/dc_406708593c68

How to cite

GPUPHOT: A Python Framework for High-Performance GPU-Accelerated Photometry and Distributed Astronomical Data Reduction — arXiv:2609.32375 — arXiv (en), https://arxiv.org/abs/2609.32375 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_406708593c68 (Metraipolis archive dc_406708593c68, sha256 9859e83c8abf717c6c448f5b659c65881b355cb7c5a29a1265fc73932c7c70ac)
BibTeX
@misc{dc406708593c68,
  title = {GPUPHOT: A Python Framework for High-Performance GPU-Accelerated Photometry and Distributed Astronomical Data Reduction — arXiv:2609.32375},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.32375},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_406708593c68; sha256 9859e83c8abf717c6c448f5b659c65881b355cb7c5a29a1265fc73932c7c70ac},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.32375. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

We present GPUPHOT, an open-source Python framework for GPU-accelerated real-time photometry and astrometry of astronomical CCD and scientific CMOS images. Four of its seven stages run entirely on the GPU through CuPy (background estimation, source detection, PSF modeling and aperture photometry); the catalog crossmatch selects a CPU or GPU backend by problem size, and the zero-point and astrometric calibrations run on the CPU, within a containerized distributed system. Checkpoint-based GPU memory monitoring and an opt-in spatial-binning fallback let a single container image run on GPUs from a 4 GB laptop card to 80 GB datacenter accelerators. We benchmark the framework on nineteen observations from two robotic facilities, the Two-meter Twin Telescope and the Transient Survey Telescope, spanning 4.2 to 151.2 megapixels and 228 to 134,206 cataloged sources, on eight NVIDIA GPU platforms with one process per image. The H100 completes the densest 151.2-megapixel field end-to-end in 31.9 s, and GPU source detection on the A100 is 6-15x faster than the CPU library sep on the same frames. Once three sources of non-determinism are pinned, catalogs and zero points agree to the fourth decimal across GPU models and host CPUs. In this one-process-per-image regime the CuPy 14 / cuML stack showed a 7% lower peak memory and a median 38% higher per-image latency than CuPy 12, both due to the RAPIDS allocator displacing the CuPy memory pool at import; restoring the pool removes the memory difference and cuts the median overhead on datacenter GPUs to 11%, with identical output. Long-lived workers, the production mode, run the two stacks near parity. We recommend the CuPy 14 stack for its reproducibility and maintained libraries, not for memory or speed. GPUPHOT and its benchmark scripts are released for autonomous facilities that require end-to-end photometric reduction at survey cadence.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-29 in cs.DC).
Categorie arXiv: Instrumentation and Methods for Astrophysics (astro-ph.IM) ; Distributed, Parallel, and Cluster Computing (cs.DC).
Pagina del lavoro: https://arxiv.org/abs/2609.32375 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-07T21:53:13.745Z dalla pagina https://arxiv.org/catchup/cs.DC/2026-09-29?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).