Skip to main content

Raw FITS database management tool

Project description

fitsdb

fitsdb is a command-line interface and Python package for indexing FITS files into an SQL database. It extracts metadata from FITS headers and organizes it for easy querying.

For example, the command

fitsdb index fits_folder

makes a SQLite database with metadata from FITS files and their corresponding observations. A python package then provides convenience functions. For example

from fitsdb import db

con = db.connect("db.sqlite")

db.observations_files(
    con, 
    "flat", 
    "2020-04-01", 
    filter="a", 
    exposure=120.0, 
    tolerance=50, 
    past=3,
)

returns a list of flat calibration files:

  • taken with filter a
  • with exposure times of 120 seconds +/- 50 seconds.
  • taken at most 3 days prior to the science frames on a specific date.

Installation

fitsdb is available on PyPI. It is recommended to install it in a fresh Python virtual environment. You can use uv for fast and reproducible environment management, or use venv/pip as you prefer.

Using PyPI (recommended)

uv venv
source .venv/bin/activate
uv pip install fitsdb

From source

git clone https://github.com/lgrcia/fitsdb.git
cd fitsdb
uv venv
source .venv/bin/activate
uv sync
uv pip install -e .

This will install the fitsdb CLI and all dependencies.

Instrument YAML Configuration

The instrument configuration YAML file defines how FITS header keywords are mapped to database fields and how instrument names are recognized. This file is required for the index command and is specified using the -i or --instruments option in the CLI. The CLI uses this configuration to correctly interpret FITS headers for different instruments and to standardize the metadata stored in the database.

Example Structure

default:
    instrument_names:
        default: ["default",]
    definition:
        keyword_instrument: "TELESCOP"
        keyword_object: "OBJECT"
        keyword_image_type: "IMAGETYP"
        keyword_light_images: "light"
        keyword_dark_images: "dark"
        keyword_flat_images: "flat"
        keyword_bias_images: "bias"
        keyword_observation_date: "DATE-OBS"
        keyword_exposure_time: "EXPTIME"
        keyword_filter: "FILTER"
        keyword_ra: "RA"
        keyword_dec: "DEC"
        keyword_jd: "JD"
        unit_ra : "deg"
        unit_dec : "deg"
        scale_jd : "utc"

speculoos:
    instrument_names:
        # these are all the possible names under the 'keyword_image_type' that
        # correspond to the Callisto instrument
        Callisto: ["speculoos-Callisto", "callisto"]
        Europa: ["speculoos-Europa",]
        Io: ["speculoos-Io",]
        Ganymede: ["speculoos-Ganymede",]
        Artemis: ["speculoos-Artemis", "artemis", "sno"]
    definition:
        keyword_light_images: "Light Frame"

Other:
    instrument_names:
        Trius-SX694: ["Trius-SX694",]
    definition:
        keyword_instrument: "INSTRUME"
        keyword_light_images: "Light_Frame"

Sections

  • instrument_names: Maps instrument aliases to canonical names.
  • definition: Maps FITS header keywords to logical fields used by the parser.

You can add more sections for different instruments as needed. The default section is used as a fallback.

CLI Usage

Index FITS Files

To index FITS files into a database, use:

fitsdb index <folder> -i instruments.yaml [-o output.sqlite]

Arguments:

  • <folder>: Path to the folder containing FITS files.
  • -i, --instruments: Path to the instruments.yaml file defining instrument configurations. If not provided, a built-in default is used.
  • -o, --output: (Optional) Path to the output database file. Defaults to db.sqlite in the folder.
  • -p, --processes: (Optional) Number of processes to use for indexing (default: number of CPU cores).
  • --duplicate/--no-duplicate: (Optional) Parse files even if they already exist in the database (default: --no-duplicate).

Show Observations

Show observations from the database (supports regex, case-insensitive):

fitsdb observations <db.sqlite> [-i INSTRUMENT] [-d DATE] [-f FILTER] [-o OBJECT] [--exposure/--no-exposure]

Arguments:

  • <db.sqlite>: Path to the SQLite database file.
  • -i, --instrument: Filter by instrument name (regex).
  • -d, --date: Filter by observation date (YYYY-MM-DD).
  • -f, --filter: Filter by filter name (regex).
  • -o, --object: Filter by object name (regex).
  • --exposure/--no-exposure: Do exposure times (False by default).

All regex filters are case-insensitive.

API

fitsdb includes a FastAPI-based REST API for querying the database over HTTP. The API provides endpoints to retrieve observations and file metadata.

Running the API Server

To start the API server, you need to set the FITSDB environment variable to point to your database file and run uvicorn:

export FITSDB=/path/to/your/db.sqlite
uvicorn fitsdb.api:app --reload

The API will be available at http://localhost:8000 by default. You can view the interactive API documentation at http://localhost:8000/docs.

Endpoints

Root Endpoint

Get Observations

GET /observations/ - Retrieve observations with optional filtering

Query parameters (all optional):

  • instrument: Filter by instrument name (string)
  • filter: Filter by filter name (string)
  • date: Filter by observation date in YYYY-MM-DD format (string)
  • object: Filter by object name (string)
# Get all observations
curl http://localhost:8000/observations/

# Filter by instrument
curl "http://localhost:8000/observations/?instrument=Callisto"

# Filter by multiple parameters
curl "http://localhost:8000/observations/?instrument=Callisto&filter=a&date=2020-04-01"

Returns: JSON array of observation records with metadata.

Get Files by ID

GET /files/{index} - Retrieve file details by observation index

Path parameters:

  • index: observation index (integer)
# Get file with ID 123
curl http://localhost:8000/files/123

Returns: JSON array containing the file record, sorted by date.

Example Response

The /observations/ endpoint returns data in this format:

[
  {
    "path": "/path/to/file1.fits",
    "date": "2020-04-01 20:30:00",
    "instrument": "Callisto",
    ...
  }
]

Environment Variables

  • FITSDB: Required. Path to the SQLite database file created by the fitsdb index command.

Development

Requirements

  • Python 3.11+
  • Dependencies listed in pyproject.toml.

Testing

Run unit tests using:

pytest

License

MIT License

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

fitsdb-0.0.2.tar.gz (5.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

fitsdb-0.0.2-py3-none-any.whl (4.2 kB view details)

Uploaded Python 3

File details

Details for the file fitsdb-0.0.2.tar.gz.

File metadata

  • Download URL: fitsdb-0.0.2.tar.gz
  • Upload date:
  • Size: 5.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for fitsdb-0.0.2.tar.gz
Algorithm Hash digest
SHA256 24f79762edd2aa155631ba1ae24c54ed86e9c15db9fa8401a1ec75bb088d2f72
MD5 fea4a68ede0b0bf8238a287b59ba0405
BLAKE2b-256 6f597e707d48798897be1650955cd95c54c1f8513cdfabd1c4a687a5d723198f

See more details on using hashes here.

Provenance

The following attestation bundles were made for fitsdb-0.0.2.tar.gz:

Publisher: ci.yml on lgrcia/fitsdb

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file fitsdb-0.0.2-py3-none-any.whl.

File metadata

  • Download URL: fitsdb-0.0.2-py3-none-any.whl
  • Upload date:
  • Size: 4.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for fitsdb-0.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 d0117b75761c158d161e2752570036d536fce14e93bdcb0f791231ccf6e7772e
MD5 ba7047335ae851672256c6bd07f97c9e
BLAKE2b-256 a3c0f66804cf71f56a5f4f5538d0e2a0f1a4c79516d8f3d3aefe2b7ef68f4225

See more details on using hashes here.

Provenance

The following attestation bundles were made for fitsdb-0.0.2-py3-none-any.whl:

Publisher: ci.yml on lgrcia/fitsdb

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page