PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2003-05-08 NOTE = "MGS RST Instrument Health Report HEA3128A.TXT" END_OBJECT = TEXT END Errata ====== 3121142A.SPK was incorrectly written to CD MORS_0829 with its original (SFDU) label; the incorrect version was also saved to magellan:/users/z00/SPK. The correct version will be designated 3121142B.SPK, saved to magellan, and written to MORS_0831. There is no entry below (Ancillary Data) because the error occurred at Stanford, and the original file did not need to be redelivered. Miscellaneous ============= Jesse Glance reports successful MGS recovery from a Payload Data System anomaly that was causing us to lose spacecraft engineering data. His report (slightly edited): This afternoon (2003-05-07), after SCT R/T commanding to force a PDS reset and Mode Change that returned PDS to S&E_2(TST) mode, the S/C engineering packet corruption problem vanished. Best explanation of the problem's root cause is that during the most recent (autonomous) PDS software reset (Sunday), the PDS-S/C_Eng interface failed to re-synchronize properly. The PDS (per an obscure 1996 LMA Tech Memo, and JPL's PDS hardware designer and holder of said memo, Carl Steiner) is [sometimes/always?] incapable of self-diagnosing this problem. Manually forcing a re-initialization of PDS interfaces, via PDS External Reset command, did the trick. It is expected that instrument teams will shortly report that their interfaces and data continue to be good following the corrective External Reset and Mode Change Commands (MOC and TES have already confirmed). Frank Lemoine announces a new series of reconstructed orbits based on the latest GSFC Mars gravity model. The first of these orbit files is listed below (MOLA POD Team Orbit Solutions). The new gravity model has been delivered to Stanford but not yet reformatted and forwarded to the Planetary Data System. Additional information from Frank (slightly edited): As of May 7, 2003 we have started to export orbits with our new 90x90 gravity model, MGM1041c. MGM1041c contains about twice the tracking data contained in MGM1004d (GMM2B) and is to 90x90 rather than 80x80. MGM1041C uses the IAU2000 coordinate system. Some other changes were also introduced into the processing. Greg Neumann has verified that the geodesy campaign gdn_ql41c* files are are close to the original set of exported orbits (0.5 - 1.0 m), so we presume at this stage the rotation matrices in our export software from Mars/IAU2000 to J2000 are all in order. Over the coming weeks, all orbits in mapping and the extended mission will be redone with mgm1041c. Engineering Data ================ No new data. The PDS anomaly has been cleared (see message from Jesse Glance under Miscellaneous), but it will take another 1-2 days for us to see the uncorrupted data since we typically run about two days behind real time on these queries. Open Loop Data ============== Data Collection --------------- We have transferred the following RSR open loop data to Stanford: YYYY/DDD DSS RSR RSR CH KSPS BT REC RECS RSR MAX START STOP ID RS LEN FILE NAME SNR -------- --- -------- -------- --- -- ---- -- ----- ----- ------------ ----- 2003/126 34 18:11:00 18:21:00 3 1 2 16 8260 601 31261811.RSR 55.6 2003/126 34 20:09:00 20:18:00 3 1 2 16 8260 541 31262009.RSR 55.5 2003/127 54 03:59:00 04:09:00 3 1 2 16 8260 601 31270359.RSR 55.5 2003/127 54 05:57:00 06:07:00 3 1 2 16 8260 601 31270557.RSR 55.6 2003/127 54 07:55:00 08:04:00 3 1 2 16 8260 541 31270755.RSR 55.3 2003/127 25 09:52:00 10:02:00 3 1 2 16 8260 601 31270952.RSR 54.9 2003/127 25 11:50:00 12:00:00 3 1 2 16 8260 601 31271150.RSR 55.3 2003/127 25 13:48:00 13:57:00 3 1 2 16 8260 541 31271348.RSR 56.0 2003/127 25 15:45:00 15:55:00 3 1 2 16 8260 601 31271545.RSR 56.1 2003/127 25 17:43:00 17:53:00 3 1 2 16 8260 601 31271743.RSR 51.6 2003/127 45 17:43:00 17:53:00 3 1 2 16 8260 601 3127174D.RSR 56.3 2003/127 45 19:41:00 19:51:00 3 1 2 16 8260 601 31271941.RSR 56.4 2003/127 45 21:38:00 21:48:00 3 1 2 16 8260 601 31272138.RSR 56.1 2003/127 45 23:36:00 23:46:00 3 1 2 16 8260 601 31272336.RSR 55.8 Anomalies --------- The following occultations had small random fluctuations in the free-space carrier amplitude: Occultation Start Date/Time DSS Comments ----------- ----------------- ----- -------------------------- 18599i 2003/127-05:57:00 54 +/-0.5 dB fluct 18600i 2003/127-07:55:00 54 +/-0.5 dB fluct 18601i 2003/127-09:52:00 25 +/-0.5 dB fluct 18604i 2003/127-15:45:00 25 +/-0.5 dB fluct The following occultations had frequency spurs around the carrier frequency: Occultation Start Date/Time DSS Comments ----------- ----------------- ----- -------------------------- 18601i 2003/127-09:52:00 25 slight +/-60 Hz spurs 18605i 2003/127-17:43:00 25 multiple spurs The following occultations had low SNR: Occultation Start Date/Time DSS Comments ----------- ----------------- ----- -------------------------- 18605i 2003/127-17:43:00 25 SNR -4.5 dB The dual anomalies on occultation 18605i at DSS 25 are puzzling because input to the A/D converter was within the normal range; maximum SNR dropped 5 dB and spurs appeared, suggesting a sudden loss in receiver stability on the last of five occultations. We will watch for future problems. The same occultation was also captured at DSS 45 with no apparent anomalies. The following occultation was captured at two different antennas: Occultation Start Date/Time DSS #1 DSS #2 ----------- ----------------- ------ ------ 18605i 2003/127-17:43:00 25 45 Closed Loop Data ================ Data Collection --------------- We have obtained the following files from OSCAR: Original File Name Name on SOPC ------------------------------------ ------------ ODF: 03126O127.DAT;1 3126127A.ODF ODF: 03127O128.DAT;1 3127128A.ODF Ancillary Data ============== Data Collection --------------- We have obtained the following files from the DOM: Original File Name Name on SOPC ------------------------------------ ------------ DKF: mm279a.01.dkf 3134138A.DKF DKF: mm279a.03.dkf 3134138B.DKF DKF: mm280a.01.dkf 3137142A.DKF DKF: mm280a.01a.dkf 3137142B.DKF OPT: optg_m_030507_OD18606-18607_18863_V1 3127148A.OPT SAK: mgs_solar_array_2003-124.ck 3124124A.SAK SOE: mm279a.01.tsoe 3134138A.SOE SOE: mm279a.03.tsoe 3134138B.SOE SOE: mm280a.01.tsoe 3137142A.SOE SPK: spk_m_030507_OD18606-18607_18863_V1 3127148A.SPK TCK: mgs_spice_c_kernel_2003-124.ck 3124124A.TCK See note above (ERRATA) regarding 3121142B.SPK. We have obtained the following files from NAIF: Original File Name Name on SOPC ------------------------------------ ------------ AGK: mgs_hga_ck_2003-04-28.bc 3118118A.AGK MOLA POD Team Orbit Solutions ============================= Data Collection --------------- We have obtained the following files from GEODESY: Original File Name Name on SOPC ------------------------------------ ------------ GDN: gdn_ql41c_212011945_212080810.tsp 2335342B.GDN GDN: gdn_ql41c_905071433_905110000.tsp 9127130D.GDN GDN: gdn_ql41c_905100000_905170000.tsp 9130136D.GDN GDN: gdn_ql41c_905160000_905220000.tsp 9136141D.GDN GDN: gdn_ql41c_905210000_905270000.tsp 9141146E.GDN GDN: gdn_ql41c_905260000_906010000.tsp 9146151D.GDN This 2335342B.GDN file is a redelivery. The processing for the original file (see HEA3127A.TXT) was apparently not set up correctly.