M01 Odyssey SPK files. =========================================================================== This ``aareadme.txt'' file describes contents of the kernels/spk directory of the M01 SPICE data server. It was last modified on July 26, 2013. Contact Chuck Acton (818-354-3869, Chuck.Acton@jpl.nasa.gov) or Boris Semenov (818-354-8136, Boris.Semenov@jpl.nasa.gov) if you have any questions regarding this data. Brief summary -------------------------------------------------------- This directory contains the SPICE SP-Kernel files for the M01 spacecraft. All files are in IEEE binary format and suitable for ftp binary transfer to use on UNIX workstations and MACs. The following files are present in this directory. (Only file names are shown; the file name extensions of the binary SPK files are always ".bsp"): Merged SPK files: m01_map_rec Ever-growing "up-to-date" reconstructed mapping orbit SPK file regularly updated by append-merging reconstructed OD solution SPK files from M01 NAV; the coverage of this file starts at the end of the latest ``m01_map[1-9]'' SPK and extends through the end of the coverage the last delivered reconstructed OD solution; m01_map Ever-growing "up-to-date" mapping SPK file regularly updated by append-merging regular mapping OD solution SPK files from M01 NAV; the coverage of this file starts at the end of the latest ``m01_map[1-9]'' SPK and extends through the end of the coverage the last delivered regular OD solution; m01_map[1-11] Final merged mapping SPKs, each covering a part of the mapping phase of the mission. These files were made by merging reconstructed OD SPK files produced by M01 NAV. The digit(s) following ``map'' indicates the portion of the mapping phase covered by the file and maps to the actual coverage dates as follows: Part of Map Start UTC Stop UTC ----------- ---------- ---------- map1 (*) 2002-02-19 2002-03-31 map2 2002-04-01 2002-06-30 map3 2002-07-01 2002-09-30 map4 2002-10-01 2002-12-31 map5 2003-01-01 2003-03-31 map6 2003-04-01 2003-06-30 map7 2003-07-01 2003-09-30 map8 2003-10-01 2003-12-31 map9 2004-01-01 2004-03-31 map10 2004-04-01 2004-06-30 map11 (**) 2004-07-01 2004-09-30 (*) the first portion is shorter than three months to align the file coverage boundaries with the project-wide archive period cut-off dates. (**) the last portion covers beyond the end of the Mapping mission into the Extended mission. Note that ``m01_map1'' released in June 2002 and covering through 2002-05-31 has been replaced with two files containing exactly same data -- ``m01_map1_v2'' covering through 2002-03-31 and ``m01_map2'' covering from 2002-04-01. This was done to align the file coverage boundaries with the project-wide archive period cut-off dates, as requested by the project's DAWG. m01_ext[1-N] Final merged extended mission SPKs, each covering a part of the extended phase of the mission. These files were made by merging reconstructed OD SPK files produced by M01 NAV. The digit(s) following ``ext'' indicates the portion of the extended phase covered by the file and maps to the actual coverage dates as follows: Part of Map Start UTC Stop UTC ----------- ---------- ---------- ext1 2004-10-01 2004-12-31 ext2 2005-01-01 2005-03-31 ext3 2005-04-01 2005-06-30 ext4 2005-07-01 2005-09-30 ext5 2005-10-01 2005-12-31 ext6 2006-01-01 2006-03-31 ext7 2006-04-01 2006-06-30 ext8 2006-07-01 2006-09-30 ext9 2006-10-01 2006-12-31 ext10 2007-01-01 2007-03-31 ext11 2007-04-01 2007-06-30 ext12 2007-07-01 2007-09-30 ext13 2007-10-01 2007-12-31 ext14 2008-01-01 2008-03-31 ext15 2008-04-01 2008-06-30 ext16 2008-07-01 2008-09-30 ext17 2008-10-01 2008-12-31 ext18 2009-01-01 2009-03-31 ext19 2009-04-01 2009-06-30 ext20 2009-07-01 2009-09-30 ext21 2009-10-01 2009-12-31 ext22 2010-01-01 2010-03-31 ext23 2010-04-01 2010-06-30 ext24 2010-07-01 2010-09-30 ext25 2010-10-01 2010-12-31 ext26 2011-01-01 2011-03-31 ext27 2011-04-01 2011-06-30 ext28 2011-07-01 2011-09-30 ext29 2011-10-01 2011-12-31 ext30 2012-01-01 2012-03-31 ext31 2012-04-01 2012-06-30 ext32 2012-07-01 2012-09-30 ext33 2012-10-01 2012-12-31 ext34 2013-01-01 2013-03-31 ext35 2013-04-01 2013-06-30 ext36 2013-07-01 2013-09-30 ext37 2013-10-01 2013-12-31 ext38 2014-01-01 2014-03-31 ext39 2014-04-01 2014-06-30 ext40 2014-07-01 2014-09-30 ext41 2014-10-01 2014-12-31 ext42 2015-01-01 2015-03-31 ext43 2015-04-01 2015-06-30 ext44 2015-07-01 2015-09-30 ext45 2015-10-01 2015-12-31 (*) the first portion does not start at the beginning of the extended mission but at the first archive cut-off boundary following it. m01_ab_v2 Version 2 of merged aerobraking SPK covering the whole aerobraking and transition-to-mapping phases of the mission; this file was made by merging regular Aerobraking OD and reconstructed transition OD SPK files produced by M01 NAV; this file supersedes version 1 AB SPK, m01_ab.bsp; m01_ab Version 1 of merged aerobraking SPK covering the whole aerobraking and transition-to-mapping phases of the mission; this file was made by merging regular OD SPK files produced by M01 NAV; m01_cruise Final merged cruise SPK covering the whole cruise phase of the mission and MOI period; this file was made by merging regular OD SPK files produced by M01 NAV; Regularly delivered SPK files: spk_m_od*-*_rec_v* Reconstructed mapping OD solution SPK files produced by M01 NAV. These files are delivered once a week. Each of these files contains reconstructed trajectory for the period identified by the two orbit numbers in the file name (*-*). spk_m_od*-*_*_v* Regular mapping OD solution SPK files produced by M01 NAV. These files are delivered once a week. Each of these files contains reconstructed trajectory for the period identified by the first two orbit numbers in the file name (*-*) and predicted trajectory for the period identified by the second and third orbit numbers in the file name (*_*). spk_m_reftraj_*_*_v* Reference mapping orbit SPK files produced by M01 NAV for mapping phase of the mission. These files are delivered occasionally on as needed basis. Each of these files contains predicted trajectory for the period identified by the dates the file name (*_*). spk_em_reftraj_*_*_v* Reference extended mapping orbit SPK files produced by M01 NAV. These files are delivered occasionally on as needed basis. Each of these files contains predicted trajectory for the period identified by the dates the file name (*_*). spk_m_*_*_*_v* Reference long-term planning orbit SPK files produced by M01 NAV. These files are delivered occasionally on as needed basis. Each of these files contains predicted trajectory for the period identified by the dates the file name (*_*). M01 spacecraft structures SPK file: m01_struct_v10 SPK file containing relative locations of M01 solar array and HGA structures. Planetary and satellite ephemeris SPK files: mar* SPK files containing Martian satellite ephemeris data. de* SPK files containing Planetary ephemeris data. SPK File Naming Schema. -------------------------------------------------------- The subsections below describe SPK files naming schemes. OD Solution SPK Files created by M01 NAV. These files are automatically transferred to the archive from the M01 Project Data Base (PDB) within one hour after M01 NAV delivers them to the PDB. The file names for regular aerobraking, mapping and extended mission OD solution SPKs have the format: spk_[P][_YYMMDD]_od[XXXXX]-[XXXXX]_[YYYYY]_v[Z] where spk_ indicates SPK files delivered by M01 NAV; P is a letter(s) identifying mission phase: ``moi'' -- Mars orbit insertion, ``ab'' -- Aerobraking, ``tm'' -- transition to Mapping, ``m'' -- Mapping, and ``em'' Extended Mapping; _YYMMDD is the file creation date, optional; XXXXX are the orbit numbers of the first and last reconstructed orbit in the file (examples: _od002-007, _od00808-00808); YYYYY is the orbit number of last predicted orbit in the file or letters "_rec" if the file doesn't contain predicted data (examples: _01122 _rec); Z is file version number (examples: _V1, _V2); The file names for reference trajectory SPKs have the format: spk_[P]_reftraj_[YYMMDD]_[yymmdd]_vZ spk_[P]_[YYMMDD]_[yymmdd]_[extra]_vZ where spk_ indicates SPK files delivered by M01 NAV; P is a letter identifying mission phase: "m" -- Mapping, etc; _reftraj indicates reference trajectory SPK; YYMMDD is the coverage begin date; yymmdd is the coverage begin date; extra is the additional qualifiers; Z is the version number; The file names for regular cruise OD solution SPKs have the format: spk_[P]_[YYMMDD]-[yymmdd]_[XXXX] where spk_ indicates SPK files delivered by M01 NAV; P is a letter identifying mission phase: "c" -- cruise; YYMMDD is the epoch of the NAV solution two characters each for year, month, day; yymmdd is the data end time of the NAV solution two characters each for year, month, day (this date is usually the file delivery date); XXXX is any additional identification data (for example: tcm1_final); Merged SPK File created by NAIF These files are created are created manually (for Cruise at the end of the Cruise phase of the mission) or automatically (for Aerobraking, Mapping, and Extended phases of the mission) from the M01 NAV regular OD solution SPKs or manually from SPK files sets coming from other data providers. The file names have the format: m01_XXXX[_YYYYY][_PPPPPP][_VVV][_TTT] where XXXX is full or abbreviated mission phase name (examples: _crus, _ab, _map1, _map2, ext1); due to the file size constraint the mapping and extended phases will be broken into sub-intervals, each covering TBD time span; _YYYYY is an optional string referring to a particular part of a mission phase; _PPPPPP is an optional string identifying team, if not M01 NAV, produced OD solution contained in the file _VVV is an optional string referring to OD solution version number (examples: _v1, _v4); _TTT is an optional string referring to type of the OD solution if multiple type are generated by the same team (examples: _rec); Supplementary/Meta Information Files. -------------------------------------------------------- There are two types of supplementary/meta information files provided with the SPK files: detached label files and orbit number files. SPK Label Files. Detached label files have the same names as the corresponding SPK files with the additional extension ".lbl" appended at the end. For all files except the merged products created by NAIF, the labels do NOT have any specific structure and they contain rather ``raw'' information combined from the following sources: file SFDU label (if such was present), contents of the comment area and file summary output by the BRIEF utility program. Most of these labels are created automatically "on the fly" and are planned to be re-processed before final data archiving with the PDS. For the merged products created by NAIF, the label contains more structured and organized information including PDS-like label, detailed description of the data sources, the way the file was created, etc. Orbit Number Files. Orbit number files are present for the corresponding merged products created by NAIF for the orbital phases of the mission (aerobraking, mapping, etc.) Orbit number files have the same names as the corresponding SPK file but with the extension ".bsp" replaced by ".orb" or ".norb". The orbit number files with the ".orb" extension contain data that follow the "periapsis-to-periapsis" orbit numbering scheme -- with the orbit number changing at periapsis. The orbit number files with the ".norb" extension contain data that follow the "node-to-node" orbit numbering scheme -- with the orbit number changing at the descending node. The information contained in the orbit number files includes the orbit number, periapsis or descending node UTC and SCLK time, apoapsis or ascending UTC time and additional information for periapsis or descending node such as subsolar and subspacecraft longitude/latitude. Details Regarding Merged SPK File for Current Phase -------------------------------------------------------- During orbital phases of the mission, the merged SPK file for the current phase of the mission is updated (appended) automatically every time M01 NAV delivers a new regular OD solution SPK file. It contains a prediction for the next few orbits along with reconstructed data up to the date of its creation. Normally these is no label available for this file. The corresponding orbit number file is also updated automatically once updating of its "parent" SPK file is finished. Merged SPK files for all completed mission phases stay unmodified and have detached labels of good quality. Archived Files -------------------------------------------------------- Original M01 NAV regular OD solution SPK files, original SPK files created by other NAV data producers and merged files created at NAIF are archived on CD-ROM and not present in this directory. Refer to the ``archived.txt'' file in this directory for a complete list of these files. Though NAIF recommends to use merged SPKs located in this directory which were made by merging data from the original products, someone can obtain archived files by submitting an e-mail request to NAIF using contact information given above.