Skip to content

B612-Asteroid-Institute/precovery

Repository files navigation

precovery: fast asteroid precovery at scale

A Python package by the Asteroid Institute, a program of the B612 Foundation

Python 3.7+ License DOI
Python Package with conda Publish Python Package to conda
Anaconda-Server Badge Anaconda-Server Badge Anaconda-Server Badge

Installation

Docker

You can build and use precovery using the Dockerfile and docker-compose.yml docker compose build docker compose run -it precovery bash

Conda

To get the latest released version and install it into a conda environment:
conda install -c asteroid-institute precovery

Source

To install the bleeding edge source code, clone this repository and then:

pip install .

openorb

Note that, openorb is not available on the Python Package Index and so you wil need to install it via source or conda. See the Dockerfile for example of how to build on Ubuntu linux.

healpy

healpy is available on PyPI, but as of version 1.16.2, only x86_64 wheels are published. For developers using Apple M1 Macbooks, these wheels won't be runnable.

Alternative wheels are therefore currently available on a B612 fork. aarch64 linux wheels can be found here: https://github.com/B612-Asteroid-Institute/healpy/releases/tag/1.16.2

Those wheels can be downloaded and directly pip-installed for developers using Docker containers on M1 Macbooks. See the Dockerfile for example.

Developer Setup

This project uses pre-commit to run linters and code formatters.

pre-commit sets the versions of these code analysis tools, and serves as an entrypoint for running them.

pre-commit installation

pre-commit is installed automatically inside the Docker container.

If you're developing on your local machine without Docker, install it using either pip install pre-commit or conda install -c conda-forge pre-commit. Then, install the hooks with pre-commit install-hooks, run from the root of this repository. This will install all the linters and tools in an isolated environment.

Running pre-commit

There are two ways you may choose to run pre-commit. You can run it manually, or you can run it automatically before every commit.

pre-commit generally only checks files that you have changed. It does this by comparing against git. This means that pre-commit will only check files you have staged (ones you have git add-ed). It will check the staged versions of those files.

Running pre-commit manually

Run pre-commit run to run linters against any files that you have changed.

Run pre-commit run --all-files to run linters against all files in the entire repository.

If you use a docker container for all development, you can use docker-compose run precovery pre-commit run [--all-files] to run within the container.

Running pre-commit automatically before every commit

Run pre-commit install to set up git hooks. These will block any commits if your changes don't pass the lint tests.

Sometimes, you might not pass lint but need to commit anyway. If you have automatic pre-commit enabled, this can get in the way.

You can disable all checks by using git commit --no-verify. You can disable a single check by using a SKIP environment variable. For example, to disable the mypy checks, use SKIP=mypy git commit.

You can skip multiple linters by passing a comma-separated list. For example, SKIP=mypy,black,flake8 git commit.

The values you pass to SKIP are the pre-commit hook IDs. These can be found in .pre-commit-config.yaml.

Observation Schema

Input CSV

precovery expects a specific set of columns to be able to index observations into a search efficient format. Input files should be sorted by ascending time.

Name Unit Type Description
obs_id None str Unique observation ID for the observation
exposure_id None str Exposure or Image ID from which observation was measured
mjd days float MJD of the observation in UTC1
ra degree float Right Ascension (J2000)
dec degree float Declination (J2000)
ra_sigma degree float 1-sigma uncertainty in Right Ascension (Optional)2
dec_sigma degree float 1-sigma uncertainty in Declination (Optional)2
mag None float Photometric magnitude measured for observation
mag_sigma None float 1-sigma uncertainty in photometric magnitude (Optional)2
filter None str Filter/bandpass in which the observation was made
exposure_mjd_start days float Start MJD of the exposure in UTC
exposure_mjd_mid days float Midpoint MJD of the exposure in UTC
exposure_duration seconds float The length of the exposure
observatory_code None str MPC observatory code for the observatory/observing program

Precovery Results

Precovery returns observations that lie within the angular tolerance of the predicted location of an input orbit propagated and mapped to the indexed observations. These observations are termed PrecoveryCandidates. Optionally, precovery can also return FrameCandidates which are frames where the orbit intersected the Healpix-mapped exposure for a specific dataset but no observations were found within the angular tolerance. In this case, quantities specific to individual observations will be returned as NaNs (mjd, ra_deg, dec_sigma_arcsec, ra_sigma_arcsec, mag, mag_sigma, observation_id, delta_ra_arcsec, delta_dec_arcsec, distance_arcsec), with the remaining quantities that define the Healpix-mapped exposure returned as normal.

Name Unit Type Description NaN When?
mjd days float MJD of the observation in UTC1 FrameCandidates
ra_deg degree float Right Ascension (J2000) FrameCandidates
dec_deg degree float Declination (J2000) FrameCandidates
ra_sigma_arcsec arcsecond float 1-sigma uncertainty in Right Ascension FrameCandidates, Missing In Source Observations3
dec_sigma_arcsec arcsecond float 1-sigma uncertainty in Declination FrameCandidates, Missing In Source Observations3
mag None float Photometric magnitude measured for observation FrameCandidates
mag_sigma None float 1-sigma uncertainty in photometric magnitude FrameCandidates, Missing In Source Observations3
filter None str Filter/bandpass in which the observation was made No
obscode None str MPC observatory code for the observatory/observing program No
exposure_id None str Exposure or Image ID from which observation was measured No
exposure_mjd_start days float Start MJD of the exposure in UTC No
exposure_mjd_mid days float Midpoint MJD of the exposure in UTC No
exposure_duration seconds float The length of the exposure No
observation_id None str Unique observation ID for the observation FrameCandidates
healpix_id None int ID of the HEALPixel onto which the exposure was mapped No
pred_ra_deg degree float Predicted Right Ascension (J2000) of the object at the time of the observation No
pred_dec_deg degree float Predicted Declination (J2000) of the object at the time of the observation No
pred_vra_degpday degree / day float Predicted velocity in Right Ascension (J2000) of the object at the time of the observation No
pred_vdec_degpday degree /day float Predicted velocity in Declination (J2000) of the object at the time of the observation No
delta_ra_arcsec arcsecond float Difference between predicted and observed Right Ascension (predicted - observed) FrameCandidates
delta_dec_arcsec arcsecond float Difference between predicted and observed Declination (predicted - observed) FrameCandidates
distance_arcsec arcsecond float Angular offset between the predicted location of the object and the obervation FrameCandidates
dataset_id None str Dataset ID from where the observation was precovered No

Footnotes:

Footnotes

  1. The time at which the observation is reported may be different than the exposure midpoint time to account for effects such as shutter motion. 2

  2. Quantities that are optional should be serialized as empty strings with the columns still defined in the input CSVs.
    When using pandas to serialize dataframes, NaN values are automatically stored as empty strings. 2 3

  3. May be NaN if they were undefined in the source observations. 2 3