Skip to content


Repository files navigation

GitHub release; latest by date GitHub Release Date Test Status Code coverage
PyPI - Version PyPI - Format PyPI - Downloads PyPI - Python Version
GitHub commits since latest release GitHub commit activity GitHub last commit
Number of GitHub open issues Number of GitHub closed issues Number of GitHub open pull requests Number of GitHub closed pull requests
GitHub License Number of GitHub stars GitHub forks


Version 2.x, originally released March, 2022 (see above for current installable version)

PDS Ring-Moon Systems Node, SETI Institute

cspyce is a Python module that provides an interface to the C-language CSPICE library produced by the Navigation and Ancillary Information Facility (NAIF) of NASA's Planetary Data System (PDS). It implements most functions of CSPICE in a Python-like way, while also supporting numerous enhancements, including support for Python exceptions, array inputs, and aliases.

cspyce may be installed by running pip install cspyce.

Python versions 3.8 thru 3.12 are currently supported, with pre-built wheels available for Linux, MacOS, and Windows.

If you are looking for information on running or distributing this code from the GitHub sources, look at the file in this directory.


cspyce has been designed to replicate the core features of CSPICE for users who wish to translate a program that already exists. Function names in cspyce match their CSPICE names.

However, it is also designed to behave as much as possible like a normal Python module. To that end, it has the following features.

  • The C language requires buffers to be allocated for output and it requires array sizes to be included for both input and output. The cspyce module, instead, eliminates all extraneous inputs, and all output arguments are returned as a list (or as a single object if the function only returns one item).

  • cspyce has been fully integrated with Python's exception handling; programmers can still opt to use CSPICE's error handling mechanism if they wish to.

  • All cspyce functions can handle positional arguments as well as arguments passed by name.

  • All cspyce functions have informative docstrings, so typing help(function) provides useful information.

  • Many cspyce functions take sensible default values if input arguments are omitted.

  • All cspyce functions that take filename arguments now support path-like-arguments. A path-like argument could be a strings, a byte string, or a pathlib.Path. The pathlib.Path class provides an object-oriented class for manipulating file-system paths and performing common operations on files.


In addition, the cspyce module takes advantage of features of the Python language to provide numerous options about how the functions perform their work. These options include:

  • Whether to return a CSPICE-style error condition or to raise a Python exception.

  • How to handle CSPICE functions that return a status flag, e.g., "found" or "ok", instead of using the CSPICE toolkit's error handling mechanism.

  • Whether to allow cspyce functions to accept arrays of inputs all at once, rather than looping through inputs in Python.

  • Whether to automate the translation between SPICE body and frame IDs and their associated names.

  • Whether to allow cspyce to support aliases, in which the same body or frame is associated with alternative names or IDs.


In CSPICE, the user can designate what to do in the event of an error condition using the function erract(). In CSPICE, the available options are "RETURN", "REPORT", "IGNORE", "ABORT", and "DEFAULT". The cspyce version of this function adds new options "EXCEPTION" and "RUNTIME" to the suite of error handling options supported by CSPICE.

  • As usual, the user can select the exception handling mechanism to use by calling the function erract(). In cspyce, the default is "EXCEPTION".

  • When using the "EXCEPTION" option, each CSPICE error condition raises a Python exception rather than setting the failed() flag. The exception contains the text of the CSPICE error, in the form (short message + " -- " + long message). The CSPICE error conditions are mapped to standard Python exception types in a sensible way:

    • KeyError indicates that a SPICE ID or name is unrecognized.
    • ValueError indicates that one of the inputs to a function had an invalid value.
    • TypeError indicates that one of the inputs to a function had an invalid type.
    • IndexError indicates that an integer index is out of range.
    • IOError indicates errors with reading and writing files, including SPICE kernels. IOError can also indicate that needed information was not in one of the furnished kernels.
    • MemoryError indicates that adequate memory could not be allocated, or that the defined size of a memory buffer in C is too small.
    • ZeroDivisionError indicates that a divide-by-zero has occurred.
    • RuntimeError indicates that an action is incompatible with some aspect of the CSPICE module's internal configuration.
  • When using one of CSPICE's intrinsic error handling methods, no exception will be raised, but a call to failed() will reveal whether an error has occurred. A call to reset() is needed to clear the error.

  • Care has been taken to reduce the chances that the "dangerous" options "IGNORE" and "REPORT" will cause a segmentation fault. However, this possibility cannot be entirely ruled out, so caution is advised.

  • Because it would be a highly questionable thing to do, the "ABORT" and "DEFAULT" options are overridden by "EXCEPTION" when the user is running cspyce from an interactive shell. However, they resume their standard effects during non-interactive runs.

  • When using the "RUNTIME" option, each CSPICE error condition raises a Python RuntimeError exception rather than setting the failed() flag. This is similar to the "EXCEPTION" option except the type of exception is always the same.

  • Certain out-of-memory conditions are beyond the control of the CSPICE library. These will always raise a MemoryError exception, regardless of the exception handling method chosen.


Many CSPICE functions bypass the library's own error handling mechanism; instead they return a status flag, sometimes called "found" or "ok", or perhaps an empty response to indicate failure. The cspyce module provides alternative options for these functions.

Within cspyce, functions that return error flags have an alternative implementation with a suffix of "_error", which uses the CSPICE/cspyce error handling mechanism detailed above instead.

Note that most _error versions of functions have fewer return values than the associated non-error versions. The user should be certain which version is being used before interpreting the returned value(s).

The cspyce module provides several ways to control which version of the function to use:

  • The function use_flags() takes a function name or list of names and designates the original version of each function as the default. If the input argument is missing, original versions are selected universally.

  • The function use_errors() takes a function name or list of names and designates the _error version of each function as the default. If the input argument is missing, _error versions are selected universally.

To provide a more consistent Python interface, the _error versions of all cspyce functions are selected by default. You can also choose between the "flag" and "error" versions of a function using cspyce function attributes, as discussed below.



Nearly every function that takes floating-point input (be it a scalar, 1-D array, or 2-D array) has a vectorized version that allows you to pass a vector of these items in place of a single value. The CSPICE function is called for each of the provided inputs, the results are collected, and the cspyce function returns a vector of results.

  • Vectorized versions have the same name but with _vector appended.

  • In a vectorized function, you can replace any or all floating-point input parameters with an array having one extra leading dimension. Integer, boolean, and string inputs cannot be replaced by arrays.

  • If no inputs have an extra dimension, then the result is the same as calling the original, un-vectorized function.

  • Otherwise, all returned quantities are replaced by arrays having the size of the largest leading axis.

  • Note that it is permissible to pass arrays with different leading axis sizes to the function. The vectorized function cycles through the elements of each array repeatedly if necessary. It may make sense to do this if each leading axis is an integer fraction of the largest axis size. For example, if the first input array has size 100 and the second has size 25, then the returned arrays(s) will have 100 elements and the values of the second will each be used four times. However, caution is advised when using this capability.

  • Some functions are not vectorized. These include:

    • Functions that have no floating-point inputs.
    • Functions that include strings among the returned quantities.
    • Functions that already return arrays where the leading axis could be variable in size.
  • In the two cases (ckgp and ckgpav) where a function can be both vectorized and either raise an error or return a flag, the _vector suffix comes before _error.


An optional import allows the cspyce module to support multidimensional arrays:

import cspyce
import cspyce.arrays

The latter import creates a new function in which the suffix _array replaces _vector for every vectorized function. Whereas _vector functions support only a single extra dimension, _array functions follow all the standard rules of shape broadcasting as defined in NumPy. For example, if one input has leading dimension (10,4) and another has dimension (4,), then the two shapes will be broadcasted together and returned quantities will be arrays with shape (10,4).

You can choose between the scalar, vector, and array versions of a function by using their explicit names, or by using cspyce function attributes, as discussed below.


Aliases allow the user to associate multiple names or SPICE codes with the same CSPICE body or frame. Aliases can be used for a variety of purposes.

  • You can use names and codes interchangeably as input arguments to any cspyce function.
  • You can use a body name or code in place of a frame name or code, and the primary frame associated with that identified body will be used.
  • Strings that represent integers are equivalent to the integers themselves.

Most importantly, you can allow multiple names or codes to refer to the same CSPICE body or frame. For bodies and frames that have multiple names or codes, calls to a cspyce function will try each option in sequence until it finds one that works. Options are always tried in the order in which they were defined, so higher-priority names and codes are tried first.

Example 1: Jupiter's moon Dia uses code 553, but it previously used code 55076. With 55076 defined as an alias for 553, a cspyce call will return information about Dia under either of its codes.

Example 2: The Earth's rotation is, by default, modeled by frame "IAU_EARTH". However, "ITRF93" is the name of a much more precise description of Earth's rotation. If you define "IAU_EARTH" as an alias for "ITRF93", then the cspyce toolkit will use ITRF93 if it is available, and otherwise IAU_EARTH.

Immediately after a cspyce call involving aliases, you can find out what value or values were actually used by looking at attributes of the function. For example, the first input to the cspyce function spkez is called targ and it identifies the code of a target being observed. After a call to

cspyce.spkez(553, ...)

the value of cspyce.spkez.targ will be the code actually used, in this case either 553 or 55076.

To enable aliases, you must import an additional module

import cspyce
import cspyce.aliases

(Note that cspyce.aliases and cspyce.arrays can both be imported, and in either order. Note also that these are unconventional modules, in that they introduce new functionality into the cspyce namespace rather than creating new namespaces called cspyce.aliases and cspyce.arrays.)

With this import, a new function is defined for every cspyce function that takes a frame or body as input. The new function has the same name as the pre-existing cspyce function, but with _alias inserted immediately after the original cspyce name (and before any other suffix such as _vector or _error).

You can make alias support the default for individual cspyce functions or for the entire cspyce module by calling cspyce.use_aliases(). These versions can subsequently be disabled as the default by calling cspyce.use_noaliases() (see more detailed discussion below).

To define a body alias or frame alias, call

cspyce.define_body_aliases(name_or_code, name_or_code, ...)
cspyce.define_frame_aliases(name_or_code, name_or_code, ...)

where the arguments are an arbitrary list of codes and names.

To determine the aliases associated with a name or code, call


where the argument is either a name or a code.

You can also select between the alias-supporting and alias-nonsupporting versions of a function using function attributes as discussed below.


A cspyce function can accumulate several suffixes, based on the particular behavior, as so:


Only functions that are truly distinct are defined. For example, if a function does not have a vector option, then no function will exist containing the _vector suffix.

You can use these functions to set defaults:


Each function can take one or more arguments referencing specific cspyce functions, in which case the defaults only apply to those functions. If no arguments are specified, the default applies to all functions. For example, to use "flags" as the default for all functions except ckgp, you could use:



Function attributes provide a simpler mechanism for choosing the needed version of a function, without needing to remember the suffix rules. Every cspyce function has these attributes, each of which identifies another (or possibly the same) cspyce function:

Attribute Meaning
func.flag the equivalent function without the _error suffix, if any.
func.error the equivalent function with the _error suffix, if any.
func.scalar the equivalent function without _array or _vector suffixes.
func.vector the equivalent function with the _vector suffix, if any.
func.array the equivalent function with the _array suffix, if any.
func.alias the equivalent function with the _alias suffix, if any.
func.noalias the equivalent function without the _alias suffix, if any.

These attributes are always defined, even if the particular option is not supported by that function. This saves the programmer the effort of remembering, for example, which functions support aliases or which functions support flags.

Thus, if the programmer wishes to be sure they are using the error version of function bodn2c, and wants the vector version if it exists (but it doesn't!), they can call

cspyce.bodn2c.error.vector(args, ...)



cspyce provides an enhanced version of SpiceCell to make it simpler to use for both CSPICE and in Python.

In the documentation that follows, active elements refer to those elements in the SpiceCell whose index is such that 0 ≤ index < spice_cell.card.


To create a SpiceCell:

from cspyce import SpiceCell, SPICE_CELL_INT, SPICE_CELL_DOUBLE
spice_cell = SpiceCell(typeno=SPICE_CELL_INT, size=20)
spice_cell = SpiceCell(typeno=SPICE_CELL_DOUBLE, size=10)

With these constructors, spice_cell.card will be set to 0 and there will initially be no active elements.

If you already have data that you want to convert to a spice cell, you can use a simpler interface:

spice_cell = SpiceCell([1, 2, 3, 4, 5])
spice_cell = SpiceCell(np.arange(1.0, 10.0))
spice_cell = SpiceCell(np.arange(1.0, 10.0), size=40)  # set size explicitly

If you use these constructions, Python will create a SpiceCell whose size is a little bigger than the length of the given data. The passed first argument will be the active elements.

Any CSPICE function that expects a SpiceCell as an input can also be passed an array, a tuple, or anything that can reasonably be converted into an appropriately typed SpiceCell:

Any CSPICE function that returns a SpiceCell as a result takes an optional final argument.

  • If this argument is omitted, a SpiceCell with a function-specific default capacity will be created, and the output will be placed into it.
  • If this argument is a SpiceCell, it will be used as the output argument.
  • If this argument is an integer, a SpiceCell with that capacity will be created and used as the output.

In all cases, the SpiceCell output will also be a return value.

>>> import cspyce
>>> cspyce.wninsd(2.0, 4.9, (1.0, 3.0, 5.0, 7.0, 9.0, 11.0))
<SpiceCell double 6/12 [ 1.   4.9  5.   7.   9.  11. ]>

Sequence-like operations

SpiceCell offers the following methods so that they behave like Python sequences.

spice_cell[index], spice_cell[index] = value

: Gets or sets the index-th element of the SpiceCell. Must have -len(spice_cell) ≤ index < spice_cell.size. As in Python, we allow negative indices, but -1, -2, etc count backwards from the last active elements.

len(spice_cell) : Returns the number of active elements of spice_cell.

spice_cell.append(value) : If value is a float or integer, it is added to the SpiceCell's active cells. If value is an array, all of its elements are added to the SpiceCell's active cells. The cell's maximum size is grown if necessary.

spice_cell.extend(values) : Appends each value in values to the end of the SpiceCell's active cells. Each element of values can be a float, an integer, or an array. The SpiceCell's maximum size is grown if necessary.

spice_cell += values : Synonym for spice_cell.extend(values)

spice_cell.clear() : Make all elements inactive. Same as spice_cell.card = 0.

iter(spice_cell) : Iterates through the active elements of spice_cell. Because of this iterator, list(spice_cell), set(spice_cell), and tuple(spice_cell) work as expected. You can also write a for loop for item in spice_cell: ... to iterate through the active elements.

bool(spice_cell) : If a spice_cell is used in a boolean context, its value is False if all elements are inactive (spice.cell.card == 0), and True otherwise.

SpiceCell-specific operations

SpiceCell also has the following methods and properties specific to a SpiceCell.

spice_cell.size : Gets the current maximum size of the SpiceCell.

spice_cell.size = value : Grows or shrinks the maximum size of the SpiceCell. If the number of active elements is greater than value, it is reduced to value. This operation is a cspyce enhancement that does not exist in CSPICE.

spice_cell.card : Same as len(spice_cell). (Also known as the "cardinality", hence the name).

spice_cell.card = value : Changes the number of active elements in the SpiceCell. Must have 0 ≤ value < spice_cell.size.

spice_cell.as_array() : Returns a view of the active contents of the array as a numpy array

spice_cell.as_intervals() : Returns a view of the active contents of the array as a 2-dimensional card/2x 2 array. Many SpiceCells are used to represent intervals in which each pair of numbers represents the lower and upper bounds.

Although cspyce's SpiceCells can grow and shrink, CSPICE is not aware of this capability. Its functions will still raise a WINDOWOVERFLOW if SpiceCell.size is not large enough to hold the results. The user must increase SpiceCell.size and try again.

Handling intervals and other structures

Although internally, a SpiceCell is a flat array of integers or floats, some CSPICE routines treat the contents of a SpiceCell as if it were a 2-dimensional array. For example, some CSPICE routines expect the SpiceCell to contain pairs of values where each pair represents the limits of an interval.

To simplify dealing with this use case, the methods append and extend have been enhanced. You can pass an array or an array-like object to append, and all elements of the array will be added to the SpiceCell. Likewise you can pass extend a sequence of array-like objects, and all of them will be added to the SpiceCell.

So, for example, you could write:

spice_cell.append([10, 20])
spice_cell.extend([[35, 50], [90, 100], [120, 140]])

to add intervals to your SpiceCell.

To view a SpiceCell containing intervals, you can use spice_cell.as_intervals() as described above. This is just a shortcut for spice_cell.as_array().reshape(-1, 2), where -1 is a special marker to reshape saying "figure out this value from the size of the array and the other dimensions". The expression spice_cell.as_array().reshape(-1, 3) would give an array of triples. self.as_array().reshape(-1, 4, 4) gives an array of 4x4 matrices.