This page provides lightweight Python tools to allow users to query and access I-ALiRT data.
It also serves as a central location for I-ALiRT data feature requests or bug reports, through the "Issues" pages.
The I-ALiRT team welcomes any and all discussions or contributions! If you have any questions, comments, requests, or anything else, please do open an issue. If you have thoughts on an existing issue or pull request, we welcome comments and discussion everywhere.
If you are interested in contributing to the project, welcome! Please start here.
If you have any questions about using I-ALiRT that are not covered by the existing documentation, you can open a question-type Issue. Before you open a new issue, please search through the existing answered questions and documentation to see if your question has already been answered.
For new feature requests, you can open a "feature request" ticket for I-ALiRT. Please fill out with as much detail as you can. Please also do a search through existing tickets to see if an existing ticket already
This lightweight Python package allows users to query the I-ALiRT database and list/download files from S3.
The I-ALiRT project welcomes contributions! To contribute, please consult the IMAP Contribution guide. All IMAP repositories follow these standards.
pip install ialirt-data-access
ialirt-data-access -hFind all files from a given year, day of year, and instance
$ ialirt-data-access --url <url> ialirt-log-query --year <year> --doy <doy> --instance <instance>Two mutually exclusive query modes are supported.
Individual params mode — query by partial datetime (year and doy required):
$ ialirt-data-access --url <url> ialirt-packet-query --year <year> --doy <doy> [--hh <hour>] [--mm <minute>] [--ss <second>]UTC range mode — query by ISO 8601 time range (time_utc_start required):
$ ialirt-data-access --url <url> ialirt-packet-query --time_utc_start <YYYY-MM-DDTHH:MM:SS> [--time_utc_end <YYYY-MM-DDTHH:MM:SS>]Find all archive CDF files, optionally filtered by year, month, and day. All parameters are optional; version defaults to 1.
$ ialirt-data-access --url <url> ialirt-archive-query [--year <year>] [--month <month>] [--day <day>] [--version <version>]Or use --since to get all files on or after a given date (format: YYYYMMDD). Cannot be combined with --year, --month, or --day.
$ ialirt-data-access --url <url> ialirt-archive-query --since <yyyymmdd> [--version <version>]An equivalent curl command is shown.
$ curl "https://ialirt.imap-mission.com/ialirt-archive-query?year=2024&month=05&day=21&version=1"$ curl "https://ialirt.imap-mission.com/ialirt-archive-query?since=20240521&version=1"Download a file and place it in the Downloads/ directory by default, or optionally specify another location using --downloads_dir. Valid filetype options include: logs, packets, archive.
$ ialirt-data-access --url <url> ialirt-download --filetype <filetype> --filename <filename>An example of how to download a cdf file from the archive directory is shown.
$ ialirt-data-access --url https://ialirt.imap-mission.com ialirt-download --filetype archive --filename imap_ialirt_l1_realtime_<yyyymmdd>_v<NNN>.cdfAn equivalent curl command is shown.
$ curl -L -O "https://ialirt.imap-mission.com/ialirt-download/archive/imap_ialirt_l1_realtime_<yyyymmdd>_v<NNN>.cdf"Query the database for a given time. Examples shown below. Valid --instrument values include:
- hit
- mag
- codice_lo
- codice_hi
- swapi
- swe
- spice (metadata about kernels)
- spacecraft (IMAP ephemeris state vectors)
- _hk (housekeeping telemetry)
If omitted, the query returns science instruments for the selected time range.
$ ialirt-data-access --url <url> space-weather --met_in_utc_start <met_in_utc_start> --met_in_utc_end <met_in_utc_end>or to query 1 hr from a start time
$ ialirt-data-access --url <url> space-weather --time_utc_start <time_utc_start>or to query the past 1 hr from an end time
$ ialirt-data-access --url <url> space-weather --time_utc_end <time_utc_end>or to query a specific instrument within the past hour
$ ialirt-data-access --url <url> space-weather --instrument <instrument>or to query spice metadata
$ ialirt-data-access --url <url> space-weather --instrument spiceor to query housekeeping for a specific instrument
$ ialirt-data-access --url <url> space-weather --instrument <instrument>_hkor to query imap spacecraft position and velocity
$ ialirt-data-access --url <url> space-weather --instrument spacecraftan equivalent curl command would be
$ curl "https://ialirt.imap-mission.com/space-weather?instrument=mag&time_utc_start=2025-11-22T05:30:00&time_utc_end=2025-11-22T08:30:00"import ialirt_data_access
# Search for files
results = ialirt_data_access.log_query(year="2024", doy="045", instance="1")To change the default URL that the package accesses, you can set
the environment variable IALIRT_DATA_ACCESS_URL or within the
package ialirt_data_access.config["DATA_ACCESS_URL"]. The default
is the production server https://ialirt.imap-mission.com.
The default for the CLI is to use the public endpoints. To access some unreleased data products and quicklooks, you may need elevated permissions. To programmatically get that, you need an API Key, which can be requested from the SDC team.
To use the API Key you can set environment variables and then use
the tool as usual. Note that the api endpoints are prefixed with /api-key
to request unreleased data. This will also require an update to the
data access url. So the following should be used when programatically
accessing the data.
IMAP_API_KEY=<your-api-key> IALIRT_DATA_ACCESS_URL=https://ialirt.imap-mission.com/api-key ialirt-data-access ...or with CLI flags
ialirt-data-access --api-key <your-api-key> --url https://ialirt.imap-mission.com/api-key ...Example:
ialirt-data-access --api-key <api_key> --url https://ialirt.imap-mission.com/api-key space-weather --instrument <instrument>An equivalent curl command would be:
$ curl -H "x-api-key: $IALIRT_API_KEY" "https://ialirt.imap-mission.com/api-key/space-weather?instrument=mag"For troubleshooting support, go to this page.