Skip to content
Snippets Groups Projects
Commit 7298a9aa authored by Marc Costa's avatar Marc Costa
Browse files

Initial Commit

parents
No related branches found
No related tags found
No related merge requests found
Showing
with 1224 additions and 0 deletions
*.BSP filter=lfs diff=lfs merge=lfs -text
*.BC filter=lfs diff=lfs merge=lfs -text
*.bsp filter=lfs diff=lfs merge=lfs -text
*.bc filter=lfs diff=lfs merge=lfs -text
include ExoMars2016.html
include MANIFEST.in
include README.md
recursive-include kernels *
recursive-include misc *
\ No newline at end of file
README.md 0 → 100644
ExoMarsRSP SPICE Kernel Dataset
===============================
SPICE is an essential tool for scientists and engineers alike in the
planetary science field for Solar System Geometry. Please visit the
[ESA SPICE Service (ESS) web site](https://spice.esac.esa.int).
The ExoMarsRSP SPICE Kernel Dataset (SKD) consists on a complete set of SPICE
Kernels that cover the whole mission lifespan including reconstructed and long
term predicted trajectory and orientation. The SKD has the following directory
structure:
* root directory (named after the mission: ExoMarsRSP)
* kernels
* ck: Kernels that contain orientation for the rover and some of its structures, (solar arrays, for instance).
* fk: Kernels that define reference frames needed for the Mission.
* ik: Kernels for the instruments on board the spacecraft.
* lsk: Leapseconds kernel.
* mk: Meta-kernel files (a.k.a "furnsh" files) that provide lists of kernels suitable for a given mission period.
* pck: Kernels that define planetary constants.
* sclk: Spacecraft clock coefficients kernels.
* spk: Orbit kernels, for the spacecraft and other solar system bodies.
* misc
* release notes: Includes the Release Notes of the SKD.
* other: different directories of interest.
The SKD also include text files that help to understand the contents of every directory. Those files are named aareadme.txt.
Please note that this Git repository provides a subset of the full SKD which is available in the [ESA SPICE FTP](ftp://spiftp.esac.esa.int/data/SPICE/ExoMarsRSP).
Installation
------------
In order to use Git to obtain the operational subset of the SKD, the user needs
to have Git installed. In addition, Git large file system (Git LFS) needs to be
installed it as well. Git LFS can be obtained [here](https://git-lfs.github.com/).
After activating Git LFS clone the repository with
git clone
In order to run the SKD in SPICE outside of the mk directory of the Git
repository the user needs to modify the following the PATH_VALUE variable
of the meta-kernel:
PATH_VALUES = ( '..' )
It is recommended for users to make a local copy of this file and
modify the value of the PATH_VALUES keyword to point to the actual
location of the ExoMars2016 SPICE data set's 'data' directory on
their system. Replacing '/' with '\' and converting line
terminators to the format native to the user's system may also be
required if this meta-kernel is to be used on a non-UNIX workstation.
Finally please note that in order to use the SPICE kernels you need to install
your prefered SPICE Library. You can find instructions on how to install
SPICE [here](https://naif.jpl.nasa.gov/naif/toolkit.html)
Function and Purpose
--------------------
ESA has a number of science missions under development and in operation that are dedicated to the study of our Solar System (i.e. MEX, Rosetta, ExoMars, BepiColombo, Solar Orbiter and JUICE). The Science Operations Centres for these missions, located at the European Space Astronomy Centre (ESAC) in Spain, are responsible for all science operations planning, data processing and archiving tasks, being the essential interface between the science instruments and the spacecraft, and with the scientific community.
From the concept study phase to the day-to-day science operations, these missions produce and use auxiliary data (spacecraft orbital state information, attitude, event information and relevant spacecraft housekeeping data) to assist science planning, data processing, analysis and archiving.
Within the Solar System scientific community, the SPICE information system is the 'de facto' standard for auxiliary data handling and geometry computations, and has been adopted and is extensively used in ESA missions. SPICE is developed and maintained by the Navigation and Ancillary Information Facility (NAIF) of the Jet Propulsion Laboratory (JPL).
The SPICE format includes definitions for orbit, attitude and event information, and the data files describing these categories are called ‘SPICE kernels’. These kernels contain sufficient information to compute derived geometrical or positional values using the existing NAIF SPICE toolkit.
For ESA missions, there are three different sources of SPICE kernels:
* The spacecraft orbit (SPK), attitude (CK) and clock correlation (SCLK) kernels, produced regularly for each mission from Mission Analysis and Flight Dynamics products and spacecraft telemetry.
* Generic kernels, such as planetary constants (PCK), leap seconds (LSK) and ephemerides (SPK), mostly provided by NAIF
* Instrument kernels (IK) and the frames specification kernel (FK), created in collaboration with the Instruments Teams
The ExoMars2016 SKD is operational and therefore it is updated with kernels generated from the periodical trajectory and orientation updates and from the relevant information obtained from housekeeping telemetry. Some updates on Instrument and S/C models might occur responding to operational demands.
The SKD contain two different types of kernels:
* Setup kernels (STK) FK, IK, PCK, LSK: they are typically text files and they are developed by ESS and are reviewed and iterated with the SGS and with the Instrument Teams when need be during the whole duration of the mission. The STKs include the following information:
* Set of Reference Frames of interest for geometry computations.
* FoV and boresight modeling for science payload.
* Study trajectory default orientation for S/C.
* Physical models for natural bodies of the mission.
* Time-varying kernels (TVK) SPK, CK, SCLK, MK: are either text or binary files and are generated with the Auxiliary Data Conversion System (ADCSng) and the source data is provided by the Flight Dynamics in terms of OEMs, AEMs and Housekeeping TM data. The TVKs incude the following information:
* Predicted attitude and predicted/reconstructed trajectory.
* OBT to UTC/CAL time conversion.
* Reconstructed trajectory and measured orientation for S/C.
* Orientation of Solar Arrays and HGA (if applicable).
* Position of scans or turn-tables or articulations of payload.
Meta-kernel management
----------------------
Meta-kernel (MK) file management is a critical element of any SPICE dataset.
For ESA Planetary Missions the MKs of the operational SKDs
are also used to control the version of the SPICE dataset in the
ESA SPICE FTP server. In general missions in operations will have an
"operational" MK. This MK will contain the latest SPICE
kernels available for the mission including those kernels generated
by ADCSng in a periodical basis. Since the periodicity of this
updates ranges from hours to weeks, the MK in the Meta-Kernel
directory does not have a version number and is regularly
overwritten. Nevertheless in order to keep traceability and
backwards compatibility with former MKs, a duplicate of every
generated operational MK is stored. This duplicated MK filename is
appended with a time tag and a version that corresponds to the
extended version of the SKD.
Note that this duplicated MK is not available
in the Git repository.
Environmental Considerations
----------------------------
At least a basic knowledge of the SPICE system is needed in order to
use these kernels. The SPICE toolkit provides versions in Fortran
(SPICELIB), C (CSPICE), IDL (icy), Matlab (mice) and Python (SpiceyPy),
and the user can choose any one that suits him/her.
The SPICELIB routine FURNSH, CSPICE function furnsh_c, icy routine
cspice_furnsh and SpiceyPy routine furnsh load a kernel file into the
kernel pool as shown below.
CALL FURNSH ( 'kernel_name' )
furnsh_c ( "kernel_name" );
cspice_furnsh, 'kernel_name'
cspice_funsh( 'kernel_name' );
spiceypy.furnsh( 'kernel_name' )
Documentation
-------------
The HTML documentation for the ExoMars2016 SKD is available [here](misc/ExoMars2016.html).
How to Help
-----------
Please note that the ExoMars2016 SKD might contain bugs and is being constantly updated.
Feedback is always welcome. If you discover a blug please do not hesitate to contact the [ESA SPICE Service](marc.costa@esa.int).
+-----------------------------------------------------------------------------+
| |
| __ __ __ __ __ __ ___ __ ___ __ __ ___ |
| /__\ /__` '__\ /__` |__) | / ` |__ /__` |__ |__) \ / | / ` |__ |
| \__, .__/ \__/ .__/ | | \__, |___ .__/ |___ | \ \/ | \__, |___ |
| |
| |
+-----------------------------------------------------------------------------+
Welcome to the operational ExoMars 2016 SPICE Kernel Dataset
============================================================
This directory contains the SPICE kernels Dataset generated for the
ExoMars 2016 mission.
See more details in:
http://www.cosmos.esa.int/web/spice/spice-for-em16
For more information on SPICE for ESA Planetary Missions, please go to
http://www.cosmos.esa.int/web/spice
For information on SPICE, please go to
http://naif.jpl.nasa.gov
For any question or suggestion on this site, please contact:
Marc Costa Sitja, mcosta@sciops.esa.int
ESA SPICE Service, esa_spice@sciops.esa.int
Content of this directory
--------------------------------------------------------
Each subdirectory within this directory contains all the kernels of
the same type that have been generated for the ExoMars2016 Mission.
ck: Kernels that contain orientation for the spacecraft and
some of its structures, (solar arrays, for instance).
fk: Kernels that define reference frames needed for the
Mission.
ik: Kernels for the instruments on board the spacecraft.
lsk: Leapseconds kernel.
mk: Meta-kernel files (a.k.a "furnsh" files) that provide
lists of kernels suitable for a given mission period.
pck: Kernels that define planetary constants.
sclk: Spacecraft clock coefficients kernels.
spk: Orbit kernels, for the spacecraft and other solar system
bodies.
Please refer to the aareadme.txt in each of the subdirectories for
information on the contents for the specific type of kernels and the
corresponding naming conventions.
Usage of the SPICE Kernels for ExoMars2016
--------------------------------------------------------
At least a basic knowledge of the SPICE system is needed in order to
use these kernels. The SPICE toolkit provides versions in Fortran
(SPICELIB), C (CSPICE), IDL (icy), Matlab (mice) and Python (SpiceyPy),
and the user can choose any one that suits him/her.
The SPICELIB routine FURNSH, CSPICE function furnsh_c, icy routine
cspice_furnsh and SpiceyPy routine furnsh load a kernel file into the
kernel pool as shown below.
CALL FURNSH ( 'kernel_name' )
furnsh_c ( "kernel_name" );
cspice_furnsh, 'kernel_name'
cspice_funsh( 'kernel_name' );
spiceypy.furnsh( 'kernel_name' )
In the case when two or more files contain data overlapping in time
for a given object, for binary kernels, the file loaded last takes
precedence.
If two (or more) text kernels assign value(s) using the '=' operator
to identical keywords, the data value(s) associated with the last
loaded occurrence of the keyword are used -all earlier values have
been replaced with the last loaded value(s).
-------------------
This file was last modified on January 21, 2018 by Marc Costa Sitja.
This file was created on January 20, 2016 by Marc Costa Sitja.
End of aareadme file.
\ No newline at end of file
ExoMars2016 CK files
===========================================================================
This ``aareadme.txt'' file describes the contents of the kernels/ck
directory of the ExoMars2016 SPICE data server.
It was last modified on January 21, 2018 by Marc Costa Sitja, ESAC/ESA.
Brief Summary
--------------------------------------------------------
This directory contains the SPICE C-Kernel files for the ExoMars2016
TGO spacecraft, its structures, and science instruments. Particularly,
it contains data for the following ExoMars 2016 TGO frames:
Frame Name Relative to NAIF ID
------------------- ------------------- ---------
TGO_SPACECRAFT J2000 -143000
TGO_CASSIS_TEL TGO_CASSIS_CRU -143410
TGO_NOMAD_LNO_SCAN TGO_NOMAD_LNO_BASE -143305
File naming conventions
--------------------------------------------------------
ExoMars 2016 spacecraft CK:
The naming scheme for the ExoMars2016 spacecraft CKs is:
em16_SC_INST_TYPE[_ID][_DESC]_YYYYMMDD_YYYYMMDD_SCLK_vNN.bc
where
SC accronym of the spacecraft (required):
tgo: for the Trace Gas Orbiter (TGO) spacecraft;
edm: for the for the Schiaparelli (EDM) lander;
INST instrument/structure/sensor identifier (required):
sc: for the TGO/EDM spacecraft frame;
cassis: for the CaSSIS Telescope frame;
nomad: for the NOMAD LNO Scanning mirror frame;
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;
i: Instrument Team;
the second letter defines the reference period of the
data:
c: Cruise phase reference;
p: Pre-aerobraking phase reference;
a: Aerobraking 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;
m: Measured 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) e.g:
npo: Nadir Power-optimised s/c attitude;
noa: Nadir Orbit-aligned s/c attitude;
axis: Orientation of the spin axis of EDM;
spin: Angular velocity od the spin axis of EDM;
YYYYMMDD coverage start and stop times in TDB (required);
SCLK reference to SCLK used to created the CK (required):
sYYYYMMDD: SCLK version YYMMDD for type ``step''
tYYYYMMDD: SCLK version YYMMDD for type ``stretch''
fYYYYMMDD: SCLK version YYMMDD for type ``fictional''
NN CK version number -- 2 digits (required).
See [5] for further details on the SCLK types available to ExoMars2016.
If multiple versions of a C-Kernel file are provided, always use the latest
version (unless earlier version is needed for some special reasons.)
Other directory contents
--------------------------------------------------------
aareadme.txt This file.
Particulars
--------------------------------------------------------
Nothing to report.
Kernel File Details
--------------------------------------------------------
The most detailed description of the data in a binary CK file is
provided in metadata included inside the comment area of the file.
This information can be viewed using the utility programs COMMNT and
SPACIT included in the NAIF Toolkit.
Contact Information
--------------------------------------------------------
If you have any questions regarding this directory or its
contents, please contact SPICE support at ESAC:
Marc Costa Sitja
(+34) 91-8131-457
mcosta@sciops.esa.int, esa_spice@sciops.esa.int
or SPICE support at IKI:
Alexander Abbakumov
+7 (495) 333-40-13
aabbakumov@romance.iki.rssi.ru
or NAIF at JPL:
Boris Semenov
(818) 354-8136
Boris.Semenov@jpl.nasa.gov
References and required readings
--------------------------------------------------------
1. ``Frames Required Reading'', NAIF Document
2. ``C-Kernel Required Reading'', NAIF Document
3. ``SCLK Required Reading'', NAIF Document
4. ``TIME Required Reading'', NAIF Document
5. ``ExoMars2016 SCLK file naming conventions,'' aareadme.txt file in
kernels/sclk directory.
End of aareadme file.
\ No newline at end of file
ExoMars2016 FK files
===========================================================================
This ``aareadme.txt'' file describes the contents of the kernels/fk
directory of the ExoMars2016 SPICE data server.
It was last modified on January 21, 2018 by Marc Costa Sitja, ESAC/ESA.
Brief Summary
--------------------------------------------------------
This directory contains the SPICE Frames Definition Kernel files for the
EXOMARS 16 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.
File naming conventions
--------------------------------------------------------
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.
em16_tgo_ops_vNN.tf ExoMars2016 TGO science operations frames.
em16_tgo_sc_mars_noa_vNN.tf Mapping/overwrite of TGO_SPACECRAFT to
TGO Mars Nadir-Orbit-Aligned frame.
em16_tgo_sc_mars_npo_vNN.tf Mapping/overwrite of TGO_SPACECRAFT to
TGO Mars Nadir-Power-Optimized frame.
em16_tgo_vNN.tf ExoMars2016 TGO spacecraft, structures,
instruments and sensors frames.
em16_edm_vNN.tf ExoMars2016 EDM lander, structures,
instruments and sensors frames.
where
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.)
Other directory contents
--------------------------------------------------------
aareadme.txt This file.
Particulars
--------------------------------------------------------
Important information about the Mapping/overwrite frame definition
kernels (em16_tgo_sc_mars_noa_vNN.tf and em16_tgo_sc_mars_npo_vNN.tf):
These frames have been implemented to overwrite the TGO_SPACECRAFT
frame definition provided in the ExoMars2016 Frames Definitions
kernel (em16_tgo_vNN.tf) and map it to the TGO_MARS_NOA/TGO_MARS_NPO
frames defined in the ExoMars 2016 Science Operations Frames
Definitions kernel (em16_tgo_ops_vNN.tf).
In order to make use of these frames' kernel, ONLY ONE of these files
MUST BE LOADED AFTER the ExoMars2016 frames definition kernel and
the ExoMars 2016 Science Operations Frames Definition kernel.
NOTE THAT BY USING ANY OF THESE KERNEL, THE TGO_SPACECRAFT FRAME
WILL BE MAPPED TO THE CORRESPONDING SCIENCE OPERATIONS FRAME, AND
ANY CK PROVIDING ORIENTATION FOR THE TGO_SPACECRAFT FRAME WILL
NOT BE USED BY THE APPLICATION SOFTWARE, EVEN IF IT IS LOADED IN
THE KERNEL POOL.
Kernel File Details
--------------------------------------------------------
The most detailed description of the data in an FK file is provided in
metadata included inside the descriptive text areas of the file. This
information can be viewed using any text editor.
Contact Information
--------------------------------------------------------
If you have any questions regarding this directory or its
contents, please contact SPICE support at ESAC:
Marc Costa Sitja
(+34) 91-8131-457
mcosta@sciops.esa.int, esa_spice@sciops.esa.int
or SPICE support at IKI:
Alexander Abbakumov
+7 (495) 333-40-13
aabbakumov@romance.iki.rssi.ru
or NAIF at JPL:
Boris Semenov
(818) 354-8136
Boris.Semenov@jpl.nasa.gov
References and required readings
--------------------------------------------------------
1. ``Frames Required Reading'', NAIF Document
2. ``Kernel Pool Required Reading'', NAIF
3. ``C-Kernel Required Reading'', NAIF
End of aareadme file.
\ No newline at end of file
This diff is collapsed.
This diff is collapsed.
ExoMars2016 IK files
===========================================================================
This ``aareadme.txt'' file describes the contents of the kernels/ik
directory of the ExoMars2016 SPICE data server.
It was last modified on January 21, 2018 by Marc Costa Sitja, ESAC/ESA.
Brief Summary
--------------------------------------------------------
This directory contains the SPICE Instrument Kernel files for the
ExoMars2016 Trace Gas Orbiter (TGO) remote sensing instruments.
File naming conventions
--------------------------------------------------------
The naming scheme for ExoMars2016 IKs is:
em16_SC_INST_vNN.ti
where
SC accronym of the spacecraft (required):
tgo: for the Trace Gas Orbiter (TGO) spacecraft;
edm: for the for the Schiaparelli (EDM) lander;
INST instrument identifier (required):
acs for ACS
cassis for CaSSIS
frend for FREND
nomad for NOMAD
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.)
Other directory contents
--------------------------------------------------------
aareadme.txt This file.
Particulars
--------------------------------------------------------
Nothing to report.
Kernel File Details
--------------------------------------------------------
The most detailed description of the data in an IK file is provided in
metadata included inside the descriptive text areas of the file. This
information can be viewed using any text editor.
Contact Information
--------------------------------------------------------
If you have any questions regarding this directory or its
contents, please contact SPICE support at ESAC:
Marc Costa Sitja
(+34) 91-8131-457
mcosta@sciops.esa.int, esa_spice@sciops.esa.int
or SPICE support at IKI:
Alexander Abbakumov
+7 (495) 333-40-13
aabbakumov@romance.iki.rssi.ru
or NAIF at JPL:
Boris Semenov
(818) 354-8136
Boris.Semenov@jpl.nasa.gov
References and required readings
--------------------------------------------------------
1. ``Kernel Pool Required Reading'', NAIF
2. Header of GETFOV SPICE API, latest version
End of aareadme file.
\ No newline at end of file
This diff is collapsed.
ExoMars2016 LSK files
===========================================================================
This ``aareadme.txt'' file describes the contents of the kernels/lsk
directory of the ExoMars2016 SPICE data server.
It was last modified on January 21, 2018 by Marc Costa Sitja, ESAC/ESA.
Brief Summary
--------------------------------------------------------
This directory contains the generic SPICE Leapseconds Kernel files for
the ExoMars 2016 mission.
File naming conventions
--------------------------------------------------------
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.)
Other directory contents
--------------------------------------------------------
aareadme.txt This file.
Particulars
--------------------------------------------------------
Nothing to report.
Kernel File Details
--------------------------------------------------------
The most detailed description of the data in an LSK file is provided
in metadata included inside the descriptive text areas of the file.
This information can be viewed using any text editor.
Contact Information
--------------------------------------------------------
If you have any questions regarding this directory or its
contents, please contact SPICE support at ESAC:
Marc Costa Sitja
(+34) 91-8131-457
mcosta@sciops.esa.int, esa_spice@sciops.esa.int
or SPICE support at IKI:
Alexander Abbakumov
+7 (495) 333-40-13
aabbakumov@romance.iki.rssi.ru
or NAIF at JPL:
Boris Semenov
(818) 354-8136
Boris.Semenov@jpl.nasa.gov
References and required readings
--------------------------------------------------------
1. ``TIME Required Reading'', NAIF Document
End of aareadme file.
\ No newline at end of file
KPL/LSK
LEAPSECONDS KERNEL FILE
===========================================================================
Modifications:
--------------
2016, Jul. 14 NJB Modified file to account for the leapsecond that
will occur on December 31, 2016.
2015, Jan. 5 NJB Modified file to account for the leapsecond that
will occur on June 30, 2015.
2012, Jan. 5 NJB Modified file to account for the leapsecond that
will occur on June 30, 2012.
2008, Jul. 7 NJB Modified file to account for the leapsecond that
will occur on December 31, 2008.
2005, Aug. 3 NJB Modified file to account for the leapsecond that
will occur on December 31, 2005.
1998, Jul 17 WLT Modified file to account for the leapsecond that
will occur on December 31, 1998.
1997, Feb 22 WLT Modified file to account for the leapsecond that
will occur on June 30, 1997.
1995, Dec 14 KSZ Corrected date of last leapsecond from 1-1-95
to 1-1-96.
1995, Oct 25 WLT Modified file to account for the leapsecond that
will occur on Dec 31, 1995.
1994, Jun 16 WLT Modified file to account for the leapsecond on
June 30, 1994.
1993, Feb. 22 CHA Modified file to account for the leapsecond on
June 30, 1993.
1992, Mar. 6 HAN Modified file to account for the leapsecond on
June 30, 1992.
1990, Oct. 8 HAN Modified file to account for the leapsecond on
Dec. 31, 1990.
Explanation:
------------
The contents of this file are used by the routine DELTET to compute the
time difference
[1] DELTA_ET = ET - UTC
the increment to be applied to UTC to give ET.
The difference between UTC and TAI,
[2] DELTA_AT = TAI - UTC
is always an integral number of seconds. The value of DELTA_AT was 10
seconds in January 1972, and increases by one each time a leap second
is declared. Combining [1] and [2] gives
[3] DELTA_ET = ET - (TAI - DELTA_AT)
= (ET - TAI) + DELTA_AT
The difference (ET - TAI) is periodic, and is given by
[4] ET - TAI = DELTA_T_A + K sin E
where DELTA_T_A and K are constant, and E is the eccentric anomaly of the
heliocentric orbit of the Earth-Moon barycenter. Equation [4], which ignores
small-period fluctuations, is accurate to about 0.000030 seconds.
The eccentric anomaly E is given by
[5] E = M + EB sin M
where M is the mean anomaly, which in turn is given by
[6] M = M + M t
0 1
where t is the number of ephemeris seconds past J2000.
Thus, in order to compute DELTA_ET, the following items are necessary.
DELTA_TA
K
EB
M0
M1
DELTA_AT after each leap second.
The numbers, and the formulation, are taken from the following sources.
1) Moyer, T.D., Transformation from Proper Time on Earth to
Coordinate Time in Solar System Barycentric Space-Time Frame
of Reference, Parts 1 and 2, Celestial Mechanics 23 (1981),
33-56 and 57-68.
2) Moyer, T.D., Effects of Conversion to the J2000 Astronomical
Reference System on Algorithms for Computing Time Differences
and Clock Rates, JPL IOM 314.5--942, 1 October 1985.
The variable names used above are consistent with those used in the
Astronomical Almanac.
\begindata
DELTET/DELTA_T_A = 32.184
DELTET/K = 1.657D-3
DELTET/EB = 1.671D-2
DELTET/M = ( 6.239996D0 1.99096871D-7 )
DELTET/DELTA_AT = ( 10, @1972-JAN-1
11, @1972-JUL-1
12, @1973-JAN-1
13, @1974-JAN-1
14, @1975-JAN-1
15, @1976-JAN-1
16, @1977-JAN-1
17, @1978-JAN-1
18, @1979-JAN-1
19, @1980-JAN-1
20, @1981-JUL-1
21, @1982-JUL-1
22, @1983-JUL-1
23, @1985-JUL-1
24, @1988-JAN-1
25, @1990-JAN-1
26, @1991-JAN-1
27, @1992-JUL-1
28, @1993-JUL-1
29, @1994-JUL-1
30, @1996-JAN-1
31, @1997-JUL-1
32, @1999-JAN-1
33, @2006-JAN-1
34, @2009-JAN-1
35, @2012-JUL-1
36, @2015-JUL-1
37, @2017-JAN-1 )
\begintext
ExoMars2016 MK files
===========================================================================
This ``aareadme.txt'' file describes the contents of the kernels/mk
directory of the ExoMars2016 SPICE data server.
It was last modified on January 21, 2018 by Marc Costa Sitja,
ESAC/ESA.
Brief Summary
--------------------------------------------------------
This directory contains the SPICE Meta-Kernel files for the ExoMars
2016 mission. Meta-kernels (also known as ``FURNSH kernel'') are used
to name a collection of kernels that are to be loaded into a user's
application at run-time. Meta-kernels are appropiate to group kernels
that correspond to a certain study group, phase or kernel state of the
mission.
File naming conventions
--------------------------------------------------------
Naming Scheme for ExoMars2016 spacecraft MKs:
The naming scheme for the ExoMars2016 spacecraft MKs is:
em16[_DESC][_vNNN][_TAG][_NNN].tm
where
DESC a brief description of the scope of study of the
trajectory (optional);
vNNN version number that corresponds to the version of the
meta-kernel or the SPICE Kernel Dataset release number
(optional; e.g. r121 for Release 1.2.1)
TAG a time tag of the MK generation time (optional;
e.g. 20160928);
NNN a count of the MK version generated for a given TAG
(mandatory if TAG is included; e.g 001)
Other directory contents
--------------------------------------------------------
aareadme.txt This file.
former_versions Directory where versions no longer valid are
stored for archive purposes.
Particulars
--------------------------------------------------------
Meta-Kernel file management is a critical element of any SPICE dataset.
For ESA Planetary Missions the Meta-Kernels of the operational SPICE
repositories are also used to control the version of the SPICE dataset.
In general missions in operations will have an "operational" Meta-Kernel.
This MK will contain the latest SPICE kernels available for the mission
including those kernels generated by the operational pipeline in a
periodical basis (namely SPK, CK and SCKL files). Since the periodicity
of this updates ranges from hours to weeks, the MK in the Meta-Kernel
directory does not have a version number and is regularly overwritten.
Nevertheless in order to keep traceability and backwards compatibility
with former MKs, a duplicate of every generated operational MK is
stored. This duplicated MK filename is appended with a time tag and a
version; if the original MK looks like:
ftp/data/SPICE/ExoMars2016/kernels/mk/em16_ops.tm
the following duplicate is generated:
ftp/data/SPICE/ExoMars2016/kernels/mk/em16_ops_v111_20160928_001.tm
For what concerns dataset version kernels, they are generated when a new
version of the kernel dataset is released. In parallel a new operational
version is made available.
New kernel datasets are typically released when new text kernels are
added, updateed or modified, when there is a change in the directory
structure, etc. Superseded version kernels are moved to the
'former_versions' directory.
Kernel File Details
--------------------------------------------------------
Name Comments
---------------------------------------------------------------------
em16_ops.tm Contains the latest available operational
kernels generated by the SPICE operational
pipeline.
em16_ops_vNNN_YYYYMMDD_NNN.tm Is a duplicate of the operational MK that
derived from release vNNN. If multiple
operational MK files are generated on the
same date the version NNN is increased
starting from 001. Read the ``Particulars''
section for more information.
Contact Information
--------------------------------------------------------
If you have any questions regarding this directory or its
contents, please contact SPICE support at ESAC:
Marc Costa Sitja
(+34) 91-8131-457
mcosta@sciops.esa.int, esa_spice@sciops.esa.int
or SPICE support at IKI:
Alexander Abbakumov
+7 (495) 333-40-13
aabbakumov@romance.iki.rssi.ru
or NAIF at JPL:
Boris Semenov
(818) 354-8136
Boris.Semenov@jpl.nasa.gov
References and required readings
--------------------------------------------------------
1. ``Kernel Required Reading'', NAIF Document
End of aareadme file.
\ No newline at end of file
KPL/MK
Meta-kernel for ExoMarsRSP Dataset v200 -- Operational 20180107_001
==========================================================================
This meta-kernel lists the ExoMarsRSP Operational SPICE kernels
providing information for the full mission based on predicted, test
and/or measured data.
Usage of the Meta-kernel
-------------------------------------------------------------------------
The set of kernels listed in this meta-kernel and the order in which
they are listed are picked to provide the best available data and
the most complete coverage based on the information about the
kernels available at the time this meta-kernel was made for the
ExoMarsRSP Operational scenario.
This file is used by the SPICE system as follows: programs that make use
of this frame kernel must "load" the kernel normally during program
initialization. Loading the kernel associates the data items with
their names in a data structure called the "kernel pool". The SPICELIB
routine FURNSH loads a kernel into the pool.
Reading the comments of the binary SPK and C-Kernels is very helpful to
understand the implemented S/C position and orientation. You can use the
following NAIF command line utility to extract that information from the
kernels:
> commnt -r em16_*
The kernels listed below can be obtained from the ESA SPICE FTP server:
ftp://spiftp.esac.esa.int/data/SPICE/ExoMarsRSP/kernels/
Implementation Notes
-------------------------------------------------------------------------
It is recommended that users make a local copy of this file and
modify the value of the PATH_VALUES keyword to point to the actual
location of the ExoMarsRSP SPICE data set's ``data'' directory on
their system. Replacing ``/'' with ``\'' and converting line
terminators to the format native to the user's system may also be
required if this meta-kernel is to be used on a non-UNIX workstation.
-------------------
This file was created on January 7, 2018 by Marc Costa Sitja ESA/ESAC.
\begindata
PATH_VALUES = ( '..' )
PATH_SYMBOLS = ( 'KERNELS' )
KERNELS_TO_LOAD = (
'$KERNELS/ck/em16_tgo_sc_slt_npo_20180101_20181231_s20170201_v01.bc'
'$KERNELS/ck/em16_tgo_sc_fpp_015_01_20160314_20170315_s20170201_v01.bc'
'$KERNELS/ck/em16_tgo_sc_fpp_d170207_pointing_20170305_20170309_s20170201_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20170301_20170331_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20170401_20170430_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20170501_20170531_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20170601_20170630_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20170701_20170731_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20170801_20170831_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20170901_20170930_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171001_20171008_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171009_20171013_s20171007_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171014_20171022_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171023_20171028_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171030_20171105_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171106_20171112_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171113_20171119_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171120_20171125_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171127_20171203_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171204_20171210_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171210_20171216_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_sc_sam_20171217_20171231_s20171024_v01.bc'
'$KERNELS/ck/em16_tgo_acs_sop_default_20160314_21000101_s20160719_v01.bc'
'$KERNELS/ck/em16_tgo_cassis_scp_tel_20160314_20161019_s20160414_v01.bc'
'$KERNELS/ck/em16_tgo_cassis_ipp_tel_20160407_20170309_s20170116_v02.bc'
'$KERNELS/ck/em16_tgo_nomad_sop_default_20160404_21000101_s20160719_v01.bc'
'$KERNELS/ck/em16_tgo_nomad_scp_20160404_20161019_s20160414_v01.bc'
'$KERNELS/ck/em16_edm_sop_axis_20161016_20161019_f20160921_v01.bc'
'$KERNELS/ck/em16_edm_sop_spin_20161016_20161019_f20160921_v01.bc'
'$KERNELS/fk/em16_tgo_v12.tf'
'$KERNELS/fk/em16_edm_v01.tf'
'$KERNELS/fk/em16_tgo_ops_v02.tf'
'$KERNELS/fk/rssd0002.tf'
'$KERNELS/ik/em16_tgo_acs_v05.ti'
'$KERNELS/ik/em16_tgo_cassis_v06.ti'
'$KERNELS/ik/em16_tgo_frend_v05.ti'
'$KERNELS/ik/em16_tgo_nomad_v04.ti'
'$KERNELS/ik/em16_edm_deca_v00.ti'
'$KERNELS/lsk/naif0012.tls'
'$KERNELS/pck/pck00010.tpc'
'$KERNELS/pck/de-403-masses.tpc'
'$KERNELS/sclk/em16_tgo_step_20171024.tsc'
'$KERNELS/sclk/em16_edm_fict_20160921.tsc'
'$KERNELS/spk/em16_tgo_flp_006_01_20160314_20210329_v01.bsp'
'$KERNELS/spk/em16_tgo_fap_148_01_20160314_20180116_v01.bsp'
'$KERNELS/spk/em16_edm_sot_landing_site_20161020_21000101_v01.bsp'
'$KERNELS/spk/em16_edm_fpd_028_01_20161016_20161020_v01.bsp'
'$KERNELS/spk/em16_edm_fpd_d161018_postsep_20161016_20161019_v01.bsp'
'$KERNELS/spk/de432s.bsp'
'$KERNELS/spk/mar097.bsp'
)
\begintext
Contact Information
------------------------------------------------------------------------
If you have any questions regarding this file contact SPICE support at
ESAC:
Marc Costa Sitja
(+34) 91-8131-457
mcosta@sciops.esa.int, esa_spice@sciops.esa.int
or NAIF at JPL:
Boris Semenov
+1 (818) 354-8136
Boris.Semenov@jpl.nasa.gov
End of MK file.
\ No newline at end of file
This diff is collapsed.
This file was produced by Bill Taber on October 3, 1997.
The values in this file are taken from the JPL Interoffice Memorandum
(IOM 314.10-127 May 22, 1995) "JPL Planetary and Lunar Ephemerides,
DE403/LE403" by Myles Standish, et al.
The masses for the sun and planetary barycenters given in this file are
derived from the masses used for the integration of the planetary
ephemeris DE-403. In the ephemeris the values of the masses are given
as ratios to of Solar GM to barycenter GM. These values are given here.
BODY1_GMSUN/GM = 6023600.0
BODY2_GMSUN/GM = 408523.71
BODY3_GMSUN/GM = 332946.048134
BODY4_GMSUN/GM = 3098708.0
BODY5_GMSUN/GM = 1047.3486
BODY6_GMSUN/GM = 3497.898
BODY7_GMSUN/GM = 22902.98
BODY8_GMSUN/GM = 19412.24
BODY9_GMSUN/GM = 135200000.0
These values are used by other products that use DE-403 to provide
gravitational force models for integration of trajectories.
Given the mass ratios and the mass of the sun, you can compute the mass
of any barycenter. These values are supplied in the text data given
below. Note that the values provided are rounded to three decimal
places.
\begindata
AU = 149597870.691
BODY1_GM = 22032.080
BODY2_GM = 324858.599
BODY3_GM = 403503.235
BODY4_GM = 42828.314
BODY5_GM = 126712767.863
BODY6_GM = 37940626.063
BODY7_GM = 5794549.007
BODY8_GM = 6836534.064
BODY9_GM = 981.601
BODY10_GM = 132712440023.310
\begintext
The masses of bodies other than the earth and moon are simply taken to
be the masses of the barycenters given above. The masses of the earth
and moon are taken from the referenced IOM.
\begindata
BODY199_GM = 22032.080
BODY299_GM = 324858.599
BODY301_GM = 4902.799
BODY399_GM = 398600.436
BODY499_GM = 42828.314
BODY599_GM = 126712767.863
BODY699_GM = 37940626.063
BODY799_GM = 5794549.007
BODY899_GM = 6836534.064
BODY999_GM = 981.601
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment