Documentation: https://luca-penasa.github.io/quick-spice-manager
Source Code: https://github.com/luca-penasa/quick-spice-manager
PyPI: https://pypi.org/project/quick-spice-manager/
quick-spice-manager provides a straightforward way to download, cache, and load ESA SPICE kernels. The core of the library is an FTP-based download engine that fetches kernels directly from the ESA public FTP server (spiftp.esac.esa.int) with parallel transfers and progress reporting. QuickSpiceManager handles metakernel resolution, local caching, pool management, and environment-based overrides — so you can get a loaded kernel set with minimal boilerplate. Optional integration with planetary-coverage is available as an extras install.
Supported missions include JUICE, SOLAR-ORBITER, BEPICOLOMBO, MARS-EXPRESS, ROSETTA, and many more.
pip install quick-spice-managerNote: The
SpiceManagername is a deprecated alias forQuickSpiceManagerand will be removed in a future release. UseQuickSpiceManagerin new code.
from quick_spice_manager import QuickSpiceManager
# Downloads kernels automatically from the ESA FTP server and loads them.
# Kernels are cached in the platform user-cache directory and reused on
# subsequent calls — no re-download unless the cache is cleared.
sm = QuickSpiceManager(spacecraft="JUICE", mk="plan")
sm.load_kernels()
# ... use spiceypy directly ...
sm.unload_kernels()resolved_mk triggers FTP download and PATH_VALUES rewriting without loading
anything into the SPICE pool, giving you a ready-to-use metakernel path:
sm = QuickSpiceManager(spacecraft="JUICE", mk="plan")
import spiceypy
spiceypy.furnsh(str(sm.resolved_mk)) # pool management is yoursThe result is cached — repeated access to sm.resolved_mk does not re-download
or recreate the temp file.
The preferred approach — kernels are loaded on entry and the original kernel pool is automatically restored on exit:
with QuickSpiceManager(spacecraft="JUICE", mk="plan") as sm:
# kernels are loaded here; original pool is restored on exit
...By default exclusive=True, which clears the entire SPICE pool before loading
so that only the kernels from the chosen metakernel are active. Set
exclusive=False to keep any previously loaded kernels alongside the new ones:
with QuickSpiceManager(spacecraft="JUICE", mk="plan", exclusive=False) as sm:
...sm = QuickSpiceManager(spacecraft="JUICE")
print(sm.metakernels) # e.g. ['juice_plan', 'juice_plan_v462_20260223_001', ...]By default version="latest" fetches the current unversioned metakernel and
re-downloads it on each fresh resolution so you always get the latest kernel
list. To pin a reproducible snapshot, pass the exact version tag from the FTP
server:
sm = QuickSpiceManager(spacecraft="JUICE", mk="plan", version="v462_20260223_001")
sm.load_kernels()The version tag is the suffix that appears in the versioned filenames listed by
sm.metakernels (e.g. juice_plan_v462_20260223_001 → tag is
v462_20260223_001). Pinned versions are looked up in kernels/mk/ first,
then in kernels/mk/former_versions/. A FileNotFoundError is raised if the
tag is not found, rather than silently falling back to a different version.
Kernels furnished via add_kernel() are registered as intentional — is_dirty
stays False and the pool can be snapshotted including them:
sm = QuickSpiceManager(spacecraft="JUICE", mk="plan")
sm.load_kernels()
sm.add_kernel("/path/to/extra.bc") # single file
sm.add_kernel(["/path/to/a.tls", "/path/to/b.bsp"]) # multiple filesWrite the live SPICE pool to a portable metakernel file that can be re-furnished later to reproduce the exact same set of loaded kernels:
sm.snapshot_pool("/tmp/pool_snapshot.tm")print(sm.is_active) # True if this manager currently owns the SPICE pool
print(sm.is_dirty) # True if kernels were added/removed since load_kernels()
sm.clean_pool() # unload extras and re-furnish missing kernelsprint(sm.cache_size) # human-readable size of the kernel cache
sm.clear_cache() # delete cached kernels (will re-download on next use)Pass an absolute path to an existing .tm file to skip FTP resolution:
sm = QuickSpiceManager(
spacecraft="JUICE",
mk="/path/to/my_local.tm",
kernels_dir="/path/to/kernels",
)
sm.load_kernels()The tour_config and config properties require the optional
planetary-coverage extra:
pip install quick-spice-manager[planetary-coverage]sm = QuickSpiceManager(spacecraft="JUICE", mk="plan")
# Returns a planetary_coverage.TourConfig loaded with locally cached kernels.
tc = sm.tour_config
print(tc.coverage)
# Returns a pandas DataFrame — renders as a table in Jupyter
print(sm.config)Two environment variables (readable from a .env file in the working directory) let you override the FTP-based workflow without changing code:
| Variable | Effect |
|---|---|
SPICE_METAKERNEL |
Path to a local metakernel file. Disables automatic FTP download. |
SPICE_DIRECTORY |
Directory containing the kernel files referenced by the metakernel. |
# .env
SPICE_METAKERNEL=/data/kernels/juice_ops.tm
SPICE_DIRECTORY=/data/kernelsThe FTP downloader supports the following ESA missions (case-insensitive, common aliases accepted):
| Mission | Accepted names |
|---|---|
| BepiColombo | BEPICOLOMBO, MPO, MTM, MMO |
| Comet Interceptor | COMET-INTERCEPTOR |
| EnVision | ENVISION |
| ExoMars 2016 | EXOMARS2016, TGO, EDM |
| ExoMars RSP | EXOMARSRSP |
| Gaia | GAIA |
| Hera | HERA |
| Huygens | HUYGENS, CASP |
| INTEGRAL | INTEGRAL |
| JUICE | JUICE |
| JWST | JWST |
| Mars Express | MARS-EXPRESS, MEX, BEAGLE2 |
| Rosetta | ROSETTA |
| SMART-1 | SMART-1 |
| Solar Orbiter | SOLAR-ORBITER, SOLO |
| Venus Express | VENUS-EXPRESS, VEX |
Logging is disabled by default. Enable it for debugging:
from quick_spice_manager import log_enable, log_enable_debug
log_enable() # INFO level
log_enable_debug() # DEBUG level- Clone this repository
- Requirements:
- uv
- Python 3.10+
- Create a virtual environment and install the dependencies
uv syncuv run pytestThe documentation is automatically generated from the content of the docs directory and from the docstrings of the public signatures of the source code. The documentation is updated and published as a Github Pages page automatically as part each release.
Releases are done with the command, e.g. incrementing patch:
uv run just bump patch
# also push, of course:
git push origin main --tagsthis will update the changelog, commit it, and make a corresponding tag.
as the CI is not yet configured for publish on pypi it can be done by hand:
uv build
uv publish --build path/to/wheelTrigger the Draft release workflow (press Run workflow). This will update the changelog & version and create a GitHub release which is in Draft state.
Find the draft release from the GitHub releases and publish it. When a release is published, it'll trigger release workflow which creates PyPI release and deploys updated documentation.
To update the skeleton of the project using copier:
uvx copier update --defaultsPre-commit hooks run all the auto-formatting (ruff format), linters (e.g. ruff and mypy), and other quality
checks to make sure the changeset is in good shape before a commit/push happens.
You can install the hooks with (runs for each commit):
pre-commit installOr if you want them to run only for each push:
pre-commit install -t pre-pushOr if you want e.g. want to run all checks manually for all files:
pre-commit run --all-filesThis project was generated using a fork of the wolt-python-package-cookiecutter template.