M01 CK files. =========================================================================== This ``aareadme.txt'' file describes contents of the kernels/ck 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 C-Kernel files for the M01 spacecraft, its solar arrays and high gain antenna. 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 CK files are always ".bc"): Merged CK files: m01_sc_map* M01 Spacecraft Orientation CK files for Mapping. 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_sc_map1'' released in June 2002 and covering through 2002-05-31 has been replaced with two files containing exactly same data -- ``m01_sc_map1_v2'' covering through 2002-03-31 and ``m01_sc_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. The same was done with ``map1'' SA and HGA CKs. m01_sc_ext* M01 Spacecraft Orientation CK files for Extended Mission. 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 Ext 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_sa_map* M01 Solar Array Orientation CK files for Mapping. The digit(s) following ``map'' indicates the portion of the mapping phase covered by the file and maps to the actual coverage dates as defined by the table above. m01_sa_ext* M01 Solar Array Orientation CK files for Extended Mission. The digit(s) following ``ext'' indicates the portion of the extended phase covered by the file and maps to the actual coverage dates as defined by the table above. m01_hga_map* M01 High Gain Antenna Orientation CK files for Mapping. The digit(s) following ``map'' indicates the portion of the mapping phase covered by the file and maps to the actual coverage dates as defined by the table above. m01_hga_ext* M01 High Gain Antenna Orientation CK files for Extended Mission. The digit(s) following ``ext'' indicates the portion of the extended phase covered by the file and maps to the actual coverage dates as defined by the table above. m01_sc_ab* M01 Spacecraft Orientation CK files for Aerobraking. Four digits following ``ab'' indicate the month covered by the file; for example ``ab0201'' covers January 2002. m01_sa_ab* M01 Solar Array Orientation CK files for Aerobraking. Four digits following ``ab'' indicate the month covered by the file; for example ``ab0201'' covers January 2002. m01_hga_ab* M01 High Gain Antenna Orientation CK files for Aerobraking. Four digits following ``ab'' indicate the month covered by the file; for example ``ab0201'' covers January 2002. m01_sc_cru* M01 Spacecraft Orientation CK files for Cruise. The coverage of the individual files is as follows: ``cru1'' -- April-June 2001, ``cru2'' -- July-August 2001, ``cru3'' -- September-October 2001, till the MOI. m01_sa_cru* M01 Solar Array Orientation CK files for Cruise. The coverage of the individual files is as follows: ``cru1'' -- April-June 2001, ``cru2'' -- July-August 2001, ``cru3'' -- September-October 2001, till the MOI. Regular daily CK files: m01_sc_YYYY-MM-DD Individual regular daily M01 Spacecraft Orientation CK files produced by NAIF/JPL. Each of these files covers one day identified in the file name. The files are delivered daily with two-three day delay. m01_sa_YYYY-MM-DD Individual regular M01 Solar Array Orientation CK files produced by NAIF/JPL. Each of these files covers one day identified in the file name. The files are delivered daily with two-three day delay. m01_hga_YYYY-MM-DD Individual regular M01 High Gain Antenna orientation CK files produced by NAIF/JPL. Each of these files covers one day identified in the file name. The files are delivered daily with two-three day delay. Some of the regularly delivered CKs can be re-created and re-delivered at a later time if TLM outages resulted in the originally delivered file being incomplete. CK File Naming Schema. -------------------------------------------------------- The subsections below describe CK file naming schemes. Regular Daily CK Files created by NAIF. The spacecraft, solar array and high gain antenna CK files are automatically created from the spacecraft engineering telemetry (orientation quaternions, spacecraft angular rates and solar array and antenna gimbal angles) on a daily basis. These files are automatically transferred to the server right after creation. The file names for regular spacecraft, SA and HGA CKs have the format: m01_XXX_YYYY-MM-DD[_yyyy-mm-dd][_zzz] where XXX is the structure id: ``sc'' for spacecraft, ``sa'' for sa, ``hga'' for HGA; YYYY-MM-DD is the (first) day covered by the file; yyyy-dd-dd is the last day covered by the file (usually omitted because nominally each file covers only one day); zzz is an optional identifier for CKs generated for special purposes (example: _emcal); Merged CK Files created by NAIF/JPL. The file names for special CKs created by NAV teams have the format: These files are created manually for all phases of the mission (usually after a mission phase or a part if it is over.) The file names have the format: m01_XXX_YYYYY[_PPPPPP][_VVV][_TTT] where XXX is the structure id: ``sc'' for spacecraft, ``sa'' for sa, ``hga'' for HGA; YYYYY is full or abbreviated mission phase name followed by a single digit mission phase sub-part identifier or four digit year-month identifier. For example a ``crus1'' file covers the first part of cruise while a ``ab0201'' file covers the the whole or a portion of January 2002 that falls during Aerobraking phase; PPPPPP is an optional string identifying team, if not NAIF, produced orientation contained in the file; VVV is an optional string specifying version number (examples: _v1, _v4); TTT is an optional string referring to type of the type of file if multiple types are generated by the same team (examples: _rec);