Contents

Troubleshooting

Troubleshooting

If you encounter any problem, create a JIRA Issue:

  • Project: SPICE Problem and Change Requests (SPICEPCR)

  • Issue Type: Software Problem Report

  • Component: GEOGEN

Warnings

GEOGEN CLI

  • Could not retrieve `{}` property using {} path

  • No instrument data product definition found for (instrument_host_id={}, instrument_id={}, product_type={})

  • Could not retrieve `{}` property using {} path

Config

  • Undefined or null input product_type: default {}/{}/{} product type definition used instead

  • Unable to derive mission SKD kernels/ path

  • Could not retrieve applicable_targets in config file {}

  • No primary_target defined for {} mission

Product

  • Invalid input product props for {} product: no {} product type definition for {} instrument host and {} instrument (can add new product type definition in configuration file)

  • Missing {} required product property for {} product

Coverage

  • SPICE(DSKDATANOTFOUND) for {} target

  • Unable to retrieve SPICE instrument code for detector name {} (this detector is assumed to be of IN-SITU type)

  • Unable to derive AOV corresponding to a product detector mode for {} detector

  • Input target name {} not applicable

  • Input SPICE body {} is not a natural Solar System body that can be used as reference target

  • stop_time < start_time

  • Invalid {} target name related to {} product, for {} mission

Errors

GEOGEN CLI

  • Could not find any SPICE kernels to load for {} input PLF file

  • Unknown Mission ID {}

  • {} configuration file could not be opened

Product

  • SPICE-unknown input {} instrument host ID for {} product

Coverage

  • Observation {} could not be computed

  • Unable to derive footprint for observation {}

  • Unable to retrieve SPICE instrument code for detector name {} (use –force-detector option to force computation for this detector, assuming it is of IN-SITU type.)

previous

Release Notes

next

Installation