SEP: Source Extractor as a library

Kyle Barbary

doi:10.21105/joss.00058

Abstract

SEP: Source Extractor as a library

Highlights

Authors of JOSS papers retain files, performs a configurable series of tasks, including background estimation, source copyright and release the work un- detection, deblending and a wide array of source measurements, and outputs a der a Creative Commons Attri- FITS format catalog file
– reading input files, producing output files and controlled by a limited set of configuration options specified in another file – can limit its applicability or lead to awkward workflows
The code is derived from the Source Extractor code base and aims to produce results compatible with Source Extractor whenever possible

Summary

Introduction

Authors of JOSS papers retain files, performs a configurable series of tasks, including background estimation, source copyright and release the work un- detection, deblending and a wide array of source measurements, and outputs a der a Creative Commons Attri- FITS format catalog file. While Source Extractor is highly useful, the fact that it can only be used as an executable – reading input files, producing output files and controlled by a limited set of configuration options specified in another file – can limit its applicability or lead to awkward workflows. There is often a desire to have programmatic access to perform one or more of the above tasks on in-memory images as part of a larger custom analysis.

Results

Conclusion