Papers › Likelihood-Based Jump Detection and Cosmic Ray Rejection for Detectors Read Out Up-the-Ramp
Likelihood-Based Jump Detection and Cosmic Ray Rejection for Detectors Read Out Up-the-Ramp
Timothy D. Brandt
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.
This paper implements likelihood-based jump detection for detectors read out up-the-ramp, using the entire set of reads to compute likelihoods. The approach compares the χ² value of a fit with and without a jump for every possible jump location. I show that this approach can be substantially more sensitive than one that only uses the difference between sequential groups of reads, especially for long ramps and for jumps that occur in the middle of a group of reads. It can also be implemented for a computational cost that is linear in the number of resultants. I provide and describe a pure Python implementation that can process a 10-resultant ramp on a 4096 ×4096 detector in ≈20 seconds, including iterative cosmic ray detection and removal, on a single core of a 2020 Macbook Air. This Python implementation, together with tests and a tutorial notebook, are available at \url{https://github.com/t-brandt/fitramp}. I also provide tests and demonstrations of the full ramp fitting and cosmic ray rejection approach on data from JWST.
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
Not run by Syntology. Nothing on this page verifies that the listed code works.
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