+-----------------------------------------------------------------------------+
| __ __ __ __ __ __ ___ __ ___ __ __ ___ |
| /__\ /__` '__\ /__` |__) | / ` |__ /__` |__ |__) \ / | / ` |__ |
| \__, .__/ \__/ .__/ | | \__, |___ .__/ |___ | \ \/ | \__, |___ |
| |
+-----------------------------------------------------------------------------+
The BepiColombo Mission Archived SPICE Kernel Data Set
Last update: 2024-11-06T17:30:00
Introduction
============
This document describes the BepiColombo SPICE kernel data set (SKD)
containing observation geometry and other ancillary data in the form of
SPICE System kernel files for the Mercury Planetary Orbiter (MPO),
Mercury Magnetospheric Orbiter (MMO or MIO), and Mercury Transfer
Module (MTM) spacecrafts their instruments, and targets. It describes the
data set directory structure, kernels included in the data set, their
naming conventions, and provides pointers to the SPICE software and
documentation.
Table of Contents
=================
Introduction
Table of Contents
Overview
Errata
Archive Contents
Kernel Types
Archived Kernel Details
SPK Files
PCK Files
IK Files
CK Files
LSK Files
SCLK Files
FK Files
DSK Files
MK Files
Miscellaneous Files
Checksum Files
File Formats
SPICE Software and Documentation
Contact Information
Cognisant Persons
Overview
========
This archive includes the complete set of BepiColombo SPICE data files
(kernel files), which can be accessed using SPICE software. The
SPICE data contain geometric and other ancillary information needed
to recover the full value of science instrument data. In particular
SPICE kernels provide spacecraft and planetary ephemerides,
spacecraft and instrument orientation, instrument mounting
alignments, and data needed for relevant time conversions. Data in
the SPICE kernel files must be accessed using the software called
the SPICE Toolkit produced and distributed by the Navigation and
Ancillary Information Facility (NAIF) Node of the Planetary Data
System.
This archive includes data covering from BepiColombo launch,
through the end time of the latest spacecraft orientation file
supplied in the archive. Until the end of the spacecraft lifespan
this archive will be accumulating with new data added according to
the project archiving plan.
Back to Table of Contents
Errata
======
1. This document is a simple HTML document. Providing documents in a
simple mark-up format was allowed by earlier versions of the PDS4
Standards but became prohibited in later versions starting summer
2015. Since the document was compliant at the time when the first
SPICE Bundle was released and for the sake of cross agency
consistency of SPICE bundles, it will exist in the archive
as an HTML document.
2. C-Matrix Kernels generated from housekeeping telemetry contain several
gaps for different known reasons. Some of the gaps might be restored in
future versions of the bundle. Note that for S/C attitude those gaps
are covered by predicted CK files.
3. C-Matrix Kernels generated from housekeeping telemetry measured
quaternions included periods with fake identity quaternions until
release 04, therefore, the corresponding CKs below from release 05
have coverage gaps at the periods where the fake identity quaternions
occurred:
- bc_mpo_sc_scm_20181020_20190101_s20240615_v01.bc
- bc_mpo_sc_scm_20190101_20200101_s20240615_v01.bc
- bc_mpo_sc_scm_20200101_20210101_s20240615_v01.bc
- bc_mpo_sc_scm_20210101_20220101_s20240615_v01.bc
- bc_mpo_sc_scm_20220101_20230101_s20240615_v01.bc
4. C-Matrix Kernels from MGA housekeeping telemetry measured angles were
generated using a wrong convention in their component's signs until
release 05, therefore, the corresponding CKs below, previous to release
06, have this generation problem:
- bc_mpo_mga_scm_20181020_20190101_s20200109_v02.bc
- bc_mpo_mga_scm_20190101_20200101_s20200109_v02.bc
- bc_mpo_mga_scm_20190101_20200101_s20230309_v01.bc
- bc_mpo_mga_scm_20200101_20210101_s20210618_v02.bc
- bc_mpo_mga_scm_20200101_20210101_s20230309_v01.bc
- bc_mpo_mga_scm_20210101_20220101_s20220106_v01.bc
- bc_mpo_mga_scm_20210101_20220101_s20230309_v01.bc
- bc_mpo_mga_scm_20220101_20230101_s20221229_v01.bc
- bc_mpo_mga_scm_20230101_20230621_s20230617_v01.bc
- bc_mpo_mga_scm_20230101_20240101_s20240104_v01.bc
- bc_mpo_mga_scm_20240101_20240617_s20240615_v01.bc
Back to Table of Contents
Archive Contents
================
Files in this archive are organized into a set of subdirectories
below the top-level directory. The following diagram shows the
structure and content of these directories. The directory names are
enclosed in square brackets ([]).
[top-level-directory]
|
|- bundle_bc_spice_v*.xml Bundle PDS4 label, one or more versions.
|- readme.txt Bundle top-level readme file.
|
|-[spice_kernels] Directory containing SPICE kernels.
| |
| |- collection_spice_kernels_v*.xml PDS4 labels for Spice Kernels collections.
| |- collection_spice_kernels_inventory_v*.tab
| | Spice Kernels collections' inventories.
| |
| |-[ck] Directory containing CK files.
| | |
| | |-- *.bc Binary CK files.
| | +-- *.xml PDS4 labels for CK files.
| |
| |-[dsk] Directory containing DSK files.
| | |
| | |-- *.bds Binary DSK files.
| | +-- *.xml PDS4 labels for DSK files.
| |
| |-[fk] Directory containing FK files.
| | |
| | |-- *.tf Text FK files.
| | +-- *.xml PDS4 labels for FK files.
| |
| |-[ik] Directory containing IK files.
| | |
| | |-- *.ti Text IK files.
| | +-- *.xml PDS4 labels for IK files.
| |
| |-[lsk] Directory containing LSK files.
| | |
| | |-- *.tls Text LSK files.
| | +-- *.xml PDS4 labels for LSK files.
| |
| |--[mk] Directory containing MK files.
| | |
| | |-- *.tm Text Meta-kernel files.
| | +-- *.xml PDS4 labels for MK files.
| |
| |-[pck] Directory containing PCK files.
| | |
| | |-- *.tpc Text PCK files.
| | |-- *.bpc Binary PCK files.
| | +-- *.xml PDS4 labels for PCK files.
| |
| |-[sclk] Directory containing SCLK files.
| | |
| | |-- *.tsc Text SCLK files.
| | +-- *.xml PDS4 labels for SCLK files.
| |
| +-[spk] Directory containing SPK files.
| |
| |-- *.bsp Binary SPK files.
| +-- *.xml PDS4 labels for SPK files.
|
|-+-[miscellaneous] Directory miscellaneous files.
| |
| |- collection_miscellaneous_v*.xml PDS4 labels for miscellaneous collections.
| |- collection_miscellaneous_inventory_v*.tab
| | Miscellaneous collections' inventories.
| |
| +-[checksum] Directory containing checksum files.
| |
| |-- *.tab Text checksum files.
| +-- *.xml PDS4 labels for checksum files.
|
+-[document] Directory containing documents.
|
|- collection_document_v*.xml PDS4 labels for document collections.
|- collection_document_inventory_v*.tab
| Document collections' inventories.
|
|- spiceds_v*.html This file and its earlier versions.
+- spiceds_v*.xml PDS4 labels for this file and its earlier versions.
Back to Table of Contents
Kernel Types
============
Different SPICE kernel types are used to store different kinds of
ancillary data.
SPK (Spacecraft Planet Kernel) files contain ephemerides (position
and velocity) for spacecraft, planets, satellites, comets and
asteroids as well as for moving or fixed spacecraft and instrument
structures. SPK files are located under the spice_kernels/spk
directory of this archive.
PCK (Planetary Constants Kernel) files contain certain physical,
dynamical and cartographic constants for target bodies, such as size
and shape specifications, and orientation of the spin axis and prime
meridian. PCK files are located under the spice_kernels/pck
directory of this archive.
IK (Instrument Kernel) files contain instrument parameters relevant
for computing an instrument's geometry such as field-of-view
definitions, CCD and optical distortion characteristics, and internal
timing parameters. IK files are located under the spice_kernels/ik
directory of this archive.
CK (C-matrix Kernel) files contain time varying orientations for
spacecraft, spacecraft structures, and articulating science
instruments. CK files are located under the spice_kernels/ck
directory of this archive.
LSK (Leapseconds Kernel) files contain the leapseconds and the
values of other constants required to perform a transformation
between Universal Time Coordinated (UTC) and Ephemeris time (ET),
which is also known as Barycentric Dynamical Time (TDB). LSK
files are located under the spice_kernels/lsk directory of
this archive.
SCLK (Spacecraft Clock Kernel) files contain on-board clock
calibration data required to perform a transformation between
Ephemeris time (ET) and spacecraft on-board time (SCLK). SCLK files
are located under the spice_kernels/sclk directory of this
archive.
FK (Frame definitions Kernel) files contain information required to
define reference frames, sources of frame orientation data and
connections between these frames and other frames supported within
the SPICE system. The science instrument frame definitions provided
in the FK files include mounting alignment information for the
instruments. FK files are located under the spice_kernels/fk
directory of this archive.
DSK (Digital Shape Kernel) files contain detailed shape models for
extended objects. These objects typically are solar system bodies such as
planets, dwarf planets, natural satellites, asteroids, and comet nuclei.
DSK data also can represent shapes of artificial objects such as spacecraft
components or represent abstractions such as a magnetic field model.
DSK files are located under the spice_kernels/dsk
directory of this archive.
MK (Meta-Kernel) files list sets of related SPICE kernels that
should be used together, providing an easy way to make data from
these kernel sets available to a SPICE-based application by loading
meta-kernels into the program using the high level SPICE data loader
routine FURNSH. MK files are located the spice_kernels/mk
directory of this archive.
Back to Table of Contents
Archived Kernel Details
=======================
The subsections below provide details, such as file naming
conventions and specific details, for each of the kernel types
included in this archive.
Please note that the most detailed description of the data in each file is
provided in metadata included inside the file or the comment area of the
file. For binary files this information can be viewed using the utility
program COMMNT included in the NAIF Toolkit.
Back to Table of Contents
SPK Files
This directory contains the SPICE SP-Kernel files for the BepiColombo
mission, including mission analysis, nominal and operational spacecraft
trajectory SPKs, generic planetary and satellite ephemeris SPKs.
Naming Scheme for BepiColombo spacecraft SPKs:
The naming scheme for the BepiColombo spacecraft trajectory SPKs is:
bc_SC_TYPE[_ID][_DESC]_YYYYMMDD_YYYYMMDD_vNN.bsp
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft;
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
TYPE Data type, where a reference to the originator of the
data, the type of data and the and the reference period
is provided. This is a three letter acronym. The first
letter defines the file originator:
s: Science Operations Center;
m: Mission Analysis;
f: Flight Dynamics;
the second letter defines the reference period of the
data:
c: Cruise phase;
l: Science phase Long term;
m: Science phase Medium term;
s: Science phase Short term;
o: Undefined;
the third letter indicates the type of data
p: Predicted data;
r: Reconstructed data;
t: Test data;
ID mapping to the original file product IDs as defined
per an ICD document (optional);
DESC description of the original reference file of any
particular of the original file (optional);
YYYYMMDD coverage start and stop times in TDB (required);
NN version number, starting from 01 (required; e.g. 01);
The naming scheme for the BepiColombo spacecraft center-of-gravity
SPKs is:
bc_SC_cog[_ID][_YYYYMMDD_YYYYMMDD]_vNN.bsp
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft;
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
ID mapping to the original file product IDs as defined
per an ICD document (optional);
YYYYMMDD coverage start and stop times in TDB (optional);
NN version number, starting from 01 (required; e.g. 01);
The naming scheme for the BepiColombo spacecraft structures SPKs is:
bc_SC_struct_vNN.bsp
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft;
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
NN version number, starting from 01 (required; e.g. 01);
The naming scheme for the BepiColombo spacecraft cruise SPKs is:
bc_SC_cruise_vNN.bsp
where
SC acronym of the spacecraft:
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
NN version number, starting from 01 (required; e.g. 01);
The naming scheme for the BepiColombo spacecraft prelaunch SPKs is:
bc_SC_prelaunch_vNN.bsp
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft
NN version number, starting from 01 (required; e.g. 01);
Naming Scheme for Generic Planetary Ephemeris SPKs
The naming scheme for generic planetary SPKs is:
deNNN.bsp
where
NNN DE version (required; e.g. 421);
Naming Scheme for ESA ESTRACK ground stations SPKs
The naming scheme for ESA ESTRACK ground stations SPKs is:
estrack_vNN.bsp
where
NN version (required; e.g. 01);
Naming Scheme for NASA DSN ground stations SPKs
The naming scheme for NASA DSN ground stations SPKs is:
earthstns_itrf93_YYMMDD.bsp
where
YYMMDD product creation time (required);
Naming Scheme for JAXA ground stations SPKs
The naming scheme for JAXA ground stations SPKs is:
earthstns_jaxa_YYYYMMDD.bsp
where
YYYYMMDD product creation time (required);
Naming Scheme for BepiColombo science frames origins SPKs
The naming scheme for BepiColombo science frames origins SPKs is:
bc_sci_vNN.bsp
where
NN version (required; e.g. 01);
Back to Table of Contents
PCK Files
This directory contains generic and mission-specific SPICE Planetary
Constants Kernel files for the BepiColombo mission. The data in these
kernels correspond to the best knowledge of the orientation, size and
shape of Mercury, Venus and the Earth.
Naming Scheme for Generic PCKs
The naming scheme for generic PCKs is:
pckNNNNN.tpc
where
NNNNN version number (required)(e.g. 00010);
If multiple versions of a generic PCK Kernel file are
provided, always use the latest version (unless an
earlier version is needed for some special reasons.)
The naming scheme for mission-specific PCKs is:
pckNNNNN_bc_vNN.tpc
where
NNNNN PCK version number (required)(e.g. 00011);
NN version number, starting from 01 (required; e.g. 01);
If multiple versions of a generic PCK Kernel file are
provided, always use the latest version (unless an
earlier version is needed for some special reasons.)
The naming scheme for generic PCK containing masses for Solar System
bodies is:
gm_deNNN.tpc
where
NNN planetary ephemeris version number (required; e.g. 403);
If multiple versions of a generic PCK Kernel file are
provided, always use the latest version (unless an
earlier version is needed for some special reasons).
Naming Scheme for Earth high-precision PCKs
The naming scheme for the Earth high-precision PCKs is:
earth_SDAT_EDAT_PDAT.bpc
where
SDAT is the file's coverage start time in YYMMDD format;
EDAT is the file's coverage end time in YYMMDD format;
PDAT is the date from which the information contained
in the file corresponds to predicted data. Any data
prior to this date corresponds to actual measurements.
Back to Table of Contents
IK Files
This directory contains the SPICE Instrument Kernel files for the
BepiColombo remote sensing and in-situ measurement/plasma science
instruments.
The naming scheme for BepiColombo IKs is:
bc_SC_INST_vNN.ti
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft;
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
INST instrument identifier (required):
mppe for MPPE
msasi for MSASI
ssas for SSAS
aux for Auxiliary
bela for BELA
mertis for MERTIS
mgns for MGNS
mixs for MIXS
phebus for PHEBUS
serena for SERENA
simbio-sys for SIMBIO-SYS
sixs for SIXS
str for STRs
mcam for MCAMs
NN version number (required);
If multiple versions of an IK file are provided for an
instrument, always use the latest version (unless
earlier version is needed for some special reasons.)
Back to Table of Contents
CK Files
This directory contains the SPICE C-Kernel files for the BepiColombo
(MPO, MMO, MTM) spacecrafts, their structures, and science instruments.
BepiColombo spacecraft CK:
The naming scheme for the BepiColombo spacecrafts CKs is:
bc_SC_INST_TYPE[_ID][_DESC]_YYYYMMDD_YYYYMMDD_SCLK_vNN.bc
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft;
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
INST instrument/structure/sensor identifier (required):
sc: for the MPO/MMO/MTM spacecraft frame;
hga: for the MPO High Gain Antenna frames;
mga: for the MPO Medium Gain Antenna frames;
sa: for the MPO/MTM Solar Arrays frames;
magboom: for the Magnetometer Boom frames;
mertis: for the MERTIS flip mirror frame;
phebus: for the PHEBUS scanner frames;
serena: for the SERENA Strofio flip mirror frame;
sep: for the MTM Solar Electric Propulsion frames.
TYPE Data type, where a reference to the originator of the
data, the type of data and the and the reference period
is provided. This is a three letter acronym. The first
letter defines the file originator:
s: Science Operations Center;
m: Mission Analysis;
f: Flight Dynamics;
the second letter defines the reference period of the
data:
c: Cruise phase reference;
l: Science phase Long term reference;
m: Science phase Medium term reference;
s: Science phase Short term reference;
o: Undefined reference;
the third letter indicates the type of data
p: Predicted data;
r: Reconstructed data;
t: Test data;
c: Commanded data (from Housekeeping Telemetry)
m: Measured data (from Housekeeping Telemetry)
ID mapping to the original file product IDs as defined per
an ICD document (optional);
DESC description of the original reference file of any
particular of the original file (optional);
YYYYMMDD coverage start and stop times in TDB (required);
SCLK reference to SCLK used to created the CK (required):
sYYMMDD: SCLK version YYMMDD for type ``step''
tYYMMDD: SCLK version YYMMDD for type ``stretch''
fYYMMDD: SCLK version YYMMDD for type ``fictional''
NN CK version number -- 2 digits (required).
The naming scheme for the BepiColombo spacecraft cruise CKs is:
bc_SC_INST_cruise_vNN.bc
where
SC acronym of the spacecraft:
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
INST instrument/structure/sensor identifier (required):
sc: for the MMO/MTM spacecraft frame
NN version number, starting from 01 (required; e.g. 01);
The naming scheme for the BepiColombo spacecraft prelaunch CKs is:
bc_SC_INST_prelaunch_vNN.bsp
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft
INST instrument/structure/sensor identifier (required):
sc: for the MPO spacecraft frame
NN version number, starting from 01 (required; e.g. 01);
If multiple versions of a C-Kernel file are provided, always use the latest
version (unless earlier version is needed for some special reasons.)
Back to Table of Contents
LSK Files
This directory contains the generic SPICE Leapseconds Kernel files for
the BepiColombo mission.
The naming scheme for generic LSKs is:
naifNNNN.tls
where
NNNN version number (required)(e.g. 0011);
If multiple versions of a generic LSK Kernel file are
provided, always use the latest version (unless earlier
version is needed for some special reasons.)
Back to Table of Contents
SCLK Files
This directory contains the SPICE Spacecraft Clock-Kernel files for the
BepiColombo spacecraft on-board clock.
The naming scheme for BepiColombo SCLKs is:
bc_SC_TYPE[_DESC]_YYYYMMDD.tsc
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft;
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
TYPE SCLK data type contained within the file:
fict: ``fictional'' data;
stre: SCLK created using a 'stretch' strategy, i.e. TCPs
are considered only the time they start to be
applicable, and then the correlation is made by
linking these points, i.e. not taking into
consideration the gradient and offsets provided
within the TCPs;
step: SCLK created using a 'step' strategy, i.e.
additional TCPs are created between real ones in
order to match the time correlation provided by a
TCP packet N at 60 seconds before TCP packet N+1,
so that continuity is forced.
DESC description of the applicability of the kernel. This
field might be used for spacecraft clocks with fictional
data which are not used for science planning purposes,
i.e. real telemetry data from a test campaign (optional);
YYYYMMDD start time of applicability, i.e. either release date for
fictional SCLKs or date of the last TCP used to generate
the SCLK in stretch/step mode.
Back to Table of Contents
FK Files
This directory contains the SPICE Frames Definition Kernel files for the
BepiColombo spacecraft, its structures, and science instruments, as well
as for the Ground Earth Stations. Moreover, it contains frame definitions
for science operations and for data analysis and scientific
investigations.
The following table provides information on which file contains which
frames, their file naming conventions and some particular details:
File Contents
--------------------------- -----------------------------------------
estrack_vNN.tf ESA Ground Stations topocentric frames.
bc_sci_vNN.tf BepiColombo science support frames.
bc_SC_vNN.tf BepiColombo spacecraft, structures,
instruments and sensors frames.
bc_dsk_surfaces_vNN.tf BepiColombo spacecraft Surface definitions
for Digital Shape Kernels.
earth_topo_YYMMDD.tf NASA DSN Ground Stations topocentric
frames.
earthstns_jaxa_YYYYMMDD.tf JAXA Ground Stations topocentric frames.
rssd0002.tf Cross-mission frames kernel that defines
frames of interest not ``built'' in the
SPICE toolkit.
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft;
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
YYMMDD product creation time (required);
NN version number -- two digits (required)
If multiple versions of a Frames Kernel file are
provided, always use the latest version (unless
earlier version is needed for some special reasons).
Back to Table of Contents
DSK Files
This directory contains the SPICE DS-Kernel files for the MPO, MMO and
MTM spacecrafts, its structures, and science instruments.
BepiColombo spacecraft DSK:
The naming scheme for the BepiColombo spacecraft DSK is:
bc_SC_BODY_[STRUC]_vNN.bds
where
SC acronym of the spacecraft:
mpo: for the Mercury Planetary Orbiter (MPO)
spacecraft;
mmo: for the Mercury Magnetospheric Orbiter (MMO)
spacecraft;
mtm: for the Mercury Transfer Module (MTM)
spacecraft
BODY type of body:
sc: for satellite
STRUC instrument/structure/sensor identifier (optional):
bus: for the spacecraft bus;
sa: for the MPO solar array;
sapx: for the MTM +X Solar Array;
samx: for the MTM -X Solar Array;
hga: for the high gain antenna;
mga: for the medium gain antenna;
mosif: for the MMO sunshield
NN DSK version number -- 2 digits (required).
If multiple versions of a DS-Kernel file are provided, always use the latest
version (unless earlier version is needed for some special reasons.)
Back to Table of Contents
MK Files
Meta-kernel (MK) files (a.k.a 'furnsh' files) provide lists of the
archived kernels included in this archive suitable for loading into
a SPICE-based application via the high level SPICE data loader
routine FURNSH. Using meta-kernels makes it easy to load with
one call a comprehensive SPICE data collection for a given period.
The text MK files are provided under the spice_kernels/mk
directory and are named according to the following scheme:
- BepiColombo MK files
bc_vVVV.tm
where
VVV is the version; the file with the latest
version supersedes all similarly named
files with earlier versions.
The reasons for adding new kernels include (but are not limited to)
adding new kinds of kernels, adding new versions of existing kernels
containing more complete or more accurate data, and adding new
versions of existing kernels superseding the existing kernels that
had errors. The file with the latest version number supersedes all
earlier versions.
Although the meta-kernels were created such that on a UNIX
workstation they can be loaded into a SPICE-based application
directly from the directory in which they reside -- because the
PATH_VALUES keyword is set to '..' and '/' is used as the path
delimiter -- it is recommended that users make local copies of these
files and update the PATH_VALUES keyword in each of them to point to
the actual location of the archive's 'spice_kernels' directory on
their system. Additional changes including replacing '/' and '\' in
all path specifications and converting UNIX line terminators to
terminators native to the user's system may be required to use these
meta-kernels on non-UNIX workstation.
The following guidelines were followed to pick and set priority --
determined by the order in which the kernel files are listed, with
the latest one taking precedence -- for the kernel files included in
these meta-kernels:
- the latest archived versions of LSK, PCK, SCLK, IK, FK, generic
SPKs, fixed offset SPKs, and fixed orientation CKs were included
- the latest reconstructed SPKs were included
- the latest predicted and reconstructed CKs were included
Additional description of the kernels sets listed in a text MK file is
provided in metadata included inside the description area of the
file. This information can be viewed using any text editor program.
Back to Table of Contents
Miscellaneous Files
===================
Miscellaneous files provide value added elements that are outside the
scope of the PDS archive requirements. Miscellaneous files included in
this archive are currently limited to checksum files.
The subsection below provides details for these files.
Back to Table of Contents
Checksum Files
A checksum file provides a table of MD5 checksums for all files in the
archive as of a particular archive (bundle) version, including
checksums for all previous checksums files and their labels but
excluding the checksum for the checksum file itself and its label.
The checksum files are provided under the miscellaneous/checksum
directory and are named according to the following scheme:
- BepiColombo checksum files
checksum_vVVV.tab
where
VVV is the version; the file with the latest
version supersedes all similarly named
files with earlier versions and can be
used to validate the archive in its
entirety.
Back to Table of Contents
File Formats
============
All text documents, checksum files, and other meta information files
such as descriptions, detached PDS4 labels, and inventory tables are
stream format files, with a carriage return (ASCII 13) and a line feed
character (ASCII 10) at the end of the records. This allows the
files to be read by most operating systems.
The text kernel files in this archive -- LSKs, PCKs, SCLKs, IKs, FKs,
and MKs -- are UNIX text files, with a line feed character (ASCII 10) at
the end of the line, and binary kernels files -- SPKs, CKs and DSKs --
are IEEE LSB binary files. While data files in this archive can be used
'as is' with SPICE toolkits for the majority of supported
environments, converting the files to the binary or text format
native to the user's computer may be required for use of the data
with FORTRAN toolkits on incompatible environments. Refer to the
documentation provided with the SPICE Toolkit to find out whether
conversion is needed in each specific case.
NAIF provides a tool (BINGO) that can convert either binary or text
kernels from one format to another. This means that text files can
have their line terminator changed and binary files can be converted
to the native format of the platform of interest. BINGO is available
from the utilities page at the NAIF Node of the PDS:
https://naif.jpl.nasa.gov/naif/utilities.html
Back to Table of Contents
SPICE Software and Documentation
================================
The latest SPICE Toolkit for a variety of computer platforms,
additional utility programs, documentation, tutorials, and hands-on
lessons are available at the NAIF Node of the PDS:
https://naif.jpl.nasa.gov
specifically:
Toolkit: https://naif.jpl.nasa.gov/naif/toolkit.html
Utilities: https://naif.jpl.nasa.gov/naif/utilities.html
Tutorials: https://naif.jpl.nasa.gov/naif/tutorials.html
Lessons: https://naif.jpl.nasa.gov/naif/lessons.html
Back to Table of Contents
Contact Information
===============================
If you have any questions regarding this directory or its
contents, please contact the ESA SPICE Service at ESAC:
Alfredo Escalante Lopez
(+34) 91 813 14 29
spice@cosmos.esa.int
or NAIF at JPL:
Boris Semenov
+1 (818) 354-8136
Boris.Semenov@jpl.nasa.gov
Back to Table of Contents
Cognisant Persons
===============================
This archive was produced by Alfredo Escalante, Ricardo Valles, and
Marc Costa Sitja, Archives and SPICE Software Development and Operations
Work Area, Data and Engineering Division (SCI-OP), Directorate of Science
(D/SCI), European Space Astronomy Centre (ESAC), European Space Agency
(ESA), Villanueva de la Canada, Spain.
End of BepiColombo SPICE archive description.
Back to Table of Contents