Astropy: A Community Python Package for Astronomy

We present the first public version (v0.2) of the open-source and community-developed Python package, Astropy. This package provides core astronomy-related functionality to the community, including support for domain-specific file formats such as Flexible Image Transport System (FITS) files, Virtual Observatory (VO) tables, and common ASCII table formats, unit and physical quantity conversions, physical constants specific to astronomy, celestial coordinate and time transformations, world coordinate system (WCS) support, generalized containers for representing gridded as well as tabular data, and a framework for cosmological transformations and conversions. Significant functionality is under active development, such as a model fitting framework, VO client and server tools, and aperture and point spread function (PSF) photometry tools. The core development team is actively making additions and enhancements to the current code base, and we encourage anyone interested to participate in the development of future Astropy versions

The Redshift Completeness of Local Galaxy Catalogs

There is considerable interest in understanding the demographics of galaxies within the local universe (defined, for our purposes, as the volume within a radius of 200 Mpc or z ≤ 0.05). In this pilot paper, using supernovae (SNe) as signposts to galaxies, we investigate the redshift completeness of catalogs of nearby galaxies. In particular, type Ia SNe are bright and are good tracers of the bulk of the galaxy population, as they arise in both old and young stellar populations. Our input sample consists of SNe with redshift ≤0.05, discovered by the flux-limited ASAS-SN survey. We define the redshift completeness fraction (RCF) as the number of SN host galaxies with known redshift prior to SN discovery, determined, in this case, via the NASA Extragalactic Database, divided by the total number of newly discovered SNe. Using SNe Ia, we find $\mathrm{RCF}=78{\pm }_{7}^{6}$% (90% confidence interval) for z < 0.03. We examine the distribution of host galaxies with and without cataloged redshifts as a function of absolute magnitude and redshift, and, unsurprisingly, find that higher-z and fainter hosts are less likely to have a known redshift prior to the detection of the SN. However, surprisingly, some ${L}_{* }$ galaxies are also missing. We conclude with thoughts on the future improvement of RCF measurements that will be made possible from large SN samples resulting from ongoing and especially upcoming time-domain surveys

The Astropy Project: Building an inclusive, open-science project and status of the v2.0 core package

The Astropy project supports and fosters the development of open-source and openly-developed Python packages that provide commonly-needed functionality to the astronomical community. A key element of the Astropy project is the core package Astropy, which serves as the foundation for more specialized projects and packages. In this article, we provide an overview of the organization of the Astropy project and summarize key features in the core package as of the recent major release, version 2.0. We then describe the project infrastructure designed to facilitate and support development for a broader ecosystem of inter-operable packages. We conclude with a future outlook of planned new features and directions for the broader Astropy project

Astropy: A community Python package for astronomy

We present the first public version (v0.2) of the open-source and community-developed Python package, Astropy. This package provides core astronomy-related functionality to the community, including support for domain-specific file formats such as flexibl

Learning from FITS: Limitations in use in modern astronomical research

The Flexible Image Transport System (FITS) standard has been a great boon to astronomy, allowing observatories, scientists and the public to exchange astronomical information easily. The FITS standard, however, is showing its age. Developed in the late 1970s, the FITS authors made a number of implementation choices that, while common at the time, are now seen to limit its utility with modern data. The authors of the FITS standard could not anticipate the challenges which we are facing today in astronomical computing. Difficulties we now face include, but are not limited to, addressing the need to handle an expanded range of specialized data product types (data models), being more conducive to the networked exchange and storage of data, handling very large datasets, and capturing significantly more complex metadata and data relationships. There are members of the community today who find some or all of these limitations unworkable, and have decided to move ahead with storing data in other formats. If this fragmentation continues, we risk abandoning the advantages of broad interoperability, and ready archivability, that the FITS format provides for astronomy. In this paper we detail some selected important problems which exist within the FITS standard today. These problems may provide insight into deeper underlying issues which reside in the format and we provide a discussion of some lessons learned. It is not our intention here to prescribe specific remedies to these issues; rather, it is to call attention of the FITS and greater astronomical computing communities to these problems in the hope that it will spur action to address them