MRO CK files. =========================================================================== This ``aareadme.txt'' file describes contents of the kernels/ck directory of the MRO SPICE data server. It was last modified on April 1, 2009. 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 MRO spacecraft, its solar arrays, and high gain antenna. 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") Reconstructed CK files mro_sc_psp_YYMMDD_YYMMDD Regular weekly reconstructed MRO spacecraft orientation CK files produced by NAIF/JPL. Each of these files covers seven days identified in the file name. The files are delivered weekly, two days after the end date of the file coverage. mro_sc_psp_YYYY-MM-DD Regular daily reconstructed MRO 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 a two day delay. mro_sc_YYYY-MM-DD[_zzz] Special reconstructed MRO spacecraft orientation CK files produced by NAIF/JPL. These special CK files are created and delivered sooner than regular daily files to support quick look activities. The names of such files contain additional identifier ``_zzz'' following the date. mro_sa_psp_YYMMDD_YYMMDD Regular weekly reconstructed MRO solar array orientation CK files produced by NAIF/JPL. Each of these files covers seven days identified in the file name. The files are delivered weekly, two days after the end date of the file coverage. mro_sa_YYYY-MM-DD Regular daily reconstructed MRO 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 a two day delay. mro_hga_psp_YYMMDD_YYMMDD Regular weekly reconstructed MRO high gain antenna orientation CK files produced by NAIF/JPL. Each of these files covers seven days identified in the file name. The files are delivered weekly, two days after the end date of the file coverage. mro_hga_YYYY-MM-DD Regular daily reconstructed MRO 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 a two day delay. Some of the regular reconstructed CKs may be re-created and re-delivered at a later time if TLM outages resulted in the originally delivered file being incomplete. Predicted CK files ATARPSNAME_sc_YYYYMMDDHRMNSC Predicted MRO spacecraft orientation CK files produced by NAIF/JPL from the AtArPS data released by the s/c team. Each of these files covers the same period as the AtArPS file named ``ATARPSNAME'' from which it was made. The files are delivered within minutes of the AtArPS delivery to the project database. The YYYYMMDDHRMNSC is the date/time when AtArPS to CK conversion took place. ATARPSNAME_sa_YYYYMMDDHRMNSC Predicted MRO solar array orientation CK files produced by NAIF/JPL from the AtArPS data released by the s/c team. Each of these files covers the same period as the AtArPS file named ``ATARPSNAME'' from which it was made. The files are delivered within minutes of the AtArPS delivery to the project database. The YYYYMMDDHRMNSC is the date/time when AtArPS to CK conversion took place. ATARPSNAME_hga_YYYYMMDDHRMNSC Predicted MRO high gain antenna orientation CK files produced by NAIF/JPL from the AtArPS data released by the s/c team. Each of these files covers the same period as the AtArPS file named ``ATARPSNAME'' from which it was made. The files are delivered within minutes of the AtArPS delivery to the project database. The YYYYMMDDHRMNSC is the date/time when AtArPS to CK conversion took place. Some of the regularly delivered predicted CKs can be re-created and re-delivered at a later time if the AtArPS file the CKs were made from was redelivered. Such re-created CK will have different YYYYMMDDHRMNSC -- the file generation date/time -- in the name. The naming scheme of the AtArPS files is described in the ``Regular Predicted CK Files created by NAIF'' subsection below. At the MRO SPICE PDS archive release preparation times (approximately every three months) selected predicted CK files get renamed to have have names compliant with the PDS 28.3 requirement. The new PDS compliant names have the following structure: mro_sc_psp_YYMMDD_YYMMDDp Predicted MRO spacecraft orientation CK files for PSP with the dates in the name indicating the file coverage and the last letter ``p'' indicating that this CK contains predicted data. mro_sa_psp_YYMMDD_YYMMDDp Predicted MRO Solar Array orientation CK files for PSP with the dates in the name indicating the file coverage and the last letter ``p'' indicating that this CK contains predicted data. mro_hga_psp_YYMMDD_YYMMDDp Predicted MRO High Gain Antenna orientation CK files for PSP with the dates in the name indicating the file coverage and the last letter ``p'' indicating that this CK contains predicted data. Each of the renamed files contains a note indicating its original name at the top of the comment area. Test CK Files mro_sc_tds_tt_YYMMDDHRMN_yymmddhrmn Test MRO spacecraft orientation CK files produced by NAIF/JPL. These files are produced only in special cases, in support of some tests, when requested by the science teams. They provide attitude data from TDS identified by file name token ``tds'' for the ERT or SCET (identified by file name token ``tt'') time range from YYMMDDHRMN to yymmddhrmn. Special CK files mro_sa_ab_fixed Special CK file providing nominal solar array orientation for the whole aerobraking phase of the mission. mro_hga_ab_fixed Special CK file providing nominal high gain antenna orientation for the whole aerobraking phase of the mission. CK File Naming Schema. -------------------------------------------------------- The subsections below describe CK file naming schemes. Regular Reconstructed Weekly CK Files. The reconstructed spacecraft, solar array and high gain antenna orientation weekly CK files are automatically created by NAIF from the spacecraft engineering telemetry (orientation quaternions, spacecraft angular rates and solar array and antenna gimbal angles) on a weekly basis. These files are automatically transferred to the server right after creation. These files are intended for OPS use and for archiving in PDS. The file names for these CKs have the following format: mro_XXX_ZZZ_YYMMDD_yymmdd where XXX is the structure id: ``sc'' for spacecraft, ``sa'' for sa, ``hga'' for HGA; ZZZ is full or abbreviated mission phase; YYMMDD is the first day covered by the file; yymmdd is the last day covered by the file; Regular Reconstructed Daily CK Files. The reconstructed spacecraft, solar array and high gain antenna orientation daily CK files are automatically created by NAIF 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 the regular reconstructed spacecraft, SA and HGA CKs have the following format: mro_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; Regular Predicted CK Files created by NAIF. The predicted spacecraft, solar array and high gain antenna orientation CK files are automatically created from an AtArPS file containing predicted orientation quaternions, spacecraft angular rates and solar array and antenna gimbal angles is delivered to the project database by the s/c team. These files are automatically transferred to the server right after creation. The file names for the regular predicted spacecraft, SA and HGA CKs have the following format: ATARPSNAME_XXX_YYYYMMDDHRMNSC where ATARPSNAME is the name of the source AtArPS file; XXX is the structure id: ``sc'' for spacecraft, ``sa'' for sa, ``hga'' for HGA; YYYYMMDDHRMNSC is the date/time when the CK file was created; The names of the AtArPS files regularly delivered during PSP follow this schema (per Dave Eckart, GN&C Ops, LMA, 01/29/07): TYPE_yydoy_YYDOY[_RMXXX] where TYPE data type. One of the following: CK_Pred -> attitude data for Predicted C-Kernel (Uses Navigation predict SPK files, and some non-flight Ephemeris, ITL and special event files.) CK_RPred -> attitude data for Reconstructed-Predicted C-Kernel (Uses reconstructed Navigation SPKs, and only flight versions of Ephemeris, ITL files, and special event (calibration, OTM, etc) products. As the name implies it is an after-the-fact run for science to fill in gaps in the C-Kernels generated from flight telemetry.) The PEF modeling is the only limitation to accuracy of this delivery. DESAT_ATT_PREDICT -> Attitude and desat data for Navigation for upcoming sequence. Generally, these deliveries do not include ITL or special events (calibrations, OTMs, etc). Name also contains sequence ID (PEF -> e.g. RM008) used in predict. These are coarse predictions, since sequences and products change often prior to uplink. ATT_PREDICT_[ACTIVITY] -> Attitude data for special activities. For example, ATT_PREDICT_SHARAD, etc. yydoy approximate start time of file (nearest DOY, i.e. 07/021-23:30 --> 07022) YYDOY approximate end time of file (nearest DOY); may be omitted for ATT_PREDICT_ files. RMXXX sequence number; used for DESAT_ATT_PREDICT files only. Note that while AtAtPS files delivered prior to PSP did not follow this naming scheme, the sets and meanings of the tokens in the names were similar to those described above. Renamed Predicted CK Files. At the MRO SPICE PDS archive release preparation times (approximately every three months) selected predicted AtArPS CK files get renamed to have have names compliant with the PDS 28.3 requirement. The file names for these CKs have the following format: mro_XXX_ZZZ_YYMMDD_yymmddp where XXX is the structure id: ``sc'' for spacecraft, ``sa'' for sa, ``hga'' for HGA; ZZZ is full or abbreviated mission phase; YYMMDD is the first day covered by the file; yymmdd is the last day covered by the file; p indicates that the CK file contains predicted data. Each of the renamed files contains a note indicating its original name at the top of the comment area. Test CK Files. The test CKs files are created by NAIF on as needed basis. The file names for the test CKs have the following format: mro_XXX_TDS_TT_YYMMDDHRMN_yymmddhrmn where XXX is the structure id: ``sc'' for spacecraft, ``sa'' for sa, ``hga'' for HGA; TDS is the name of the test TDS from which the data was obtained. TT is the data query time type (``ert'' or ``scet''). YYMMDDHRMN is the data query begin time. yymmddhrmn is the data query end time. Special CK Files. The special CKs files are created by NAIF on as needed basis. The file names for the special CKs have the following format: mro_XXX_ZZZZZZZZZ where XXX is the structure id: ``sc'' for spacecraft, ``sa'' for sa, ``hga'' for HGA; ZZZZZZZZZ is the string identifying the type of data in the file and/or purpose of the file.