PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2000-09-27 NOTE = "MGS RST Instrument Health Report HEA0271A.TXT" END_OBJECT = TEXT END Engineering Data ================ Engineering Data Statistical Summary from CSV2STAT: First SCET: 2000-09-25T00:09:19.194 Last SCET: 2000-09-25T23:59:59.182 CHANNL CHANNEL TITLE DN-LO DN-HI EU-LO EU-HI EU-AVG/STDEV RECDS ------ ------------- ----- ----- --------- --------- ---------/-------- ----- F-0190 HGA_AZ_ANG 6424 12149 1.57E+00 2.97E+00 2.76E+00/8.78E-03 2617 F-0195 HGA_EL_ANG -11233 11091 -2.74E+00 2.71E+00 -6.53E-01/3.41E-02 2617 L-0034 MOT1_RANGING 0 0 5237 L-0036 MOT1_TLM_MOD 0 0 5231 L-0037 MOT1_USO_ENA 0 0 5237 L-0044 MOT2_RANGING 1 1 5237 L-0046 MOT2_TLM_MOD 0 1 5231 L-0047 MOT2_USO_ENA 1 1 5237 L-0053 RF_SW_OSC 2 2 5231 L-0060 TWTA1_FILMNT 0 0 5237 L-0061 TWTA1_HV 0 0 5236 L-0070 TWTA2_FILMNT 1 1 5236 L-0071 TWTA2_HV 0 1 5237 L-0080 USO_PWR 0 0 5237 L-0090 KaBLE_STAT 0 0 5237 L-0091 KaBLE_ENABLE 1 1 5236 L-0111 MOT1_RCV_AGC 255 255 -1.53E+02 -1.53E+02 -1.53E+02/7.93E-07 5237 L-0121 MOT2_RCV_AGC 162 255 -1.53E+02 -1.27E+02 -1.50E+02/1.09E-01 5237 L-0131 TWTA1_HLX_I 0 1 -3.84E-02 -1.85E-02 -3.82E-02/2.14E-05 5237 L-0132 TWTA1_ANOD_V 0 1 -1.00E+03 -1.00E+03 -1.00E+03/1.31E-02 656 L-0141 TWTA2_HLX_I 17 42 2.86E-01 7.85E-01 4.94E-01/2.71E-03 5237 L-0142 TWTA2_ANOD_V 61 229 -8.66E+02 -5.30E+02 -6.56E+02/6.21E+00 656 L-0200 USO_REG_V 203 205 4.06E+00 4.10E+00 4.08E+00/2.46E-04 655 L-0201 USO_OVEN_V 128 130 2.56E+00 2.60E+00 2.57E+00/3.73E-04 655 T-0302 EPC1_T 188 196 -4.19E+00 -7.38E-01 -2.73E+00/3.01E-02 657 T-0303 EPC2_T 182 192 -2.43E+00 1.71E+00 -6.74E-01/4.77E-02 657 T-0310 RF_ISOLTR1_T 229 233 -6.05E+00 -1.15E+00 -3.37E+00/8.45E-03 5231 T-0311 RF_ISOLTR2_T 225 233 -6.05E+00 3.13E+00 -1.09E+00/2.50E-02 5231 T-0312 TWT1_T 227 233 -6.05E+00 1.06E+00 -2.66E+00/3.59E-02 655 T-0313 TWT2_T 219 233 -6.05E+00 8.56E+00 9.13E-02/1.76E-01 655 T-0315 USO_T 146 149 1.91E+01 2.00E+01 1.97E+01/8.23E-03 657 T-0316 KA_AMP_T 215 220 7.73E+00 1.16E+01 9.88E+00/2.47E-02 654 L-0200, L-0201, and T-0315 are nominal. Open Loop Data ============== Data Collection --------------- We have transferred the following open loop data to Stanford: YYYY/DDD DSS DSP SAMP BW DSP BIT REC RECS RECS MAX START STOP RATE MODE RESN LEN MSSG SNR -------- --- -------- -------- ---- ---- ---- ---- ---- ----- ---- ----- 2000/270 25 12:28:00 12:35:00 5000 2000 2 12 1666 2101 0 44.7 2000/270 25 14:26:00 14:33:00 5000 2000 2 12 1666 2101 0 45.8 2000/270 25 16:23:00 16:30:00 5000 2000 2 12 1666 2101 0 46.0 2000/270 25 18:21:00 18:28:00 5000 2000 2 12 1666 2101 0 45.7 2000/270 25 20:19:00 20:26:00 5000 2000 2 12 1666 2101 0 45.7 2000/270 25 22:16:00 22:23:00 5000 2000 2 12 1666 2101 0 46.6 2000/271 45 00:14:00 00:21:00 5000 2000 2 12 1666 2101 0 49.1 2000/271 45 02:12:00 02:19:00 5000 2000 2 12 1666 2101 0 48.4 2000/271 65 06:07:00 06:14:00 5000 2000 2 12 1666 2101 0 -0.0 2000/271 65 08:05:00 08:12:00 5000 2000 2 12 1666 2101 0 45.5 2000/271 65 10:02:00 10:09:00 5000 2000 2 12 1666 2101 0 45.5 2000/271 65 12:00:00 12:07:00 5000 2000 2 12 1666 2101 0 44.6 2000/271 65 13:58:00 14:05:00 5000 2000 2 12 1666 2101 0 44.9 2000/271 65 15:55:00 16:02:00 5000 2000 2 12 1666 2101 0 43.5 Anomalies --------- Data from occultation 6953i (DSS 45, start time 2000/271-04:09:00) have not been found. Data from occultation 6954i (DSS 65, start time 2000/271-06:07:00) have no signal. The noise level is also well below what is usually expected. Closed Loop Data ================ Data Collection --------------- We have obtained the following files from OSCAR and EPIC: Original File Name Name on SOPC -------------------------------- ------------ ODF: 00269O270_10S.SJO_v1 0269270A.ODF ODF: 00270O271_10S.SJO_v1 0270271A.ODF EOP: 000926-eop.long 20200353.EOP EOP: 000926-eop.short 93520353.EOP Anomalies --------- Sami Asmar relayed the following report/query from Eric Graat of the MGS Navigation Team: We here on the MGS NAV team have encountered some trouble fitting the one-way doppler (F1) tracking data collected by DSS 15, 45 and 65 from 9/8/00 15:40:00 UTC to 9/9/00 10:40:00 UTC. This F1 data was collected during the latest radio-science campaign. Attempting to include this F1 data in our orbit solutions which used two-way coherent doppler (F2) tracking data corrupted the orbit deter- mined by the F2 data. Several estimation methods were attempted in order to fit the F1, but no method worked. This problem did not seem to be caused by mismodeled spacecraft dynamics or obvious "blunder" points in the data. We regularly use the MGS F1 tracking data in our orbit solutions, so our inability to fit this data was surprising. Do you know of anything that would make this F1 unsuitable for our orbit determination process? Analyses -------- At Frank Lemoine's request, Pat Esposito asked Darren Baird to review tracking and AMD data from 2000-08-13. Frank had noted that there were only three angular momentum desaturation events on 08-13 and had been having difficulty with trajectory reconstructions. He suspected that an AMD event had been omitted from the AMD file. Darren's report: Here are the start times of the 3 AMDs that occurred on 13 Aug 2000. 07:21:44 SCET 14:42:18 SCET 21:40:34 SCET I went back and took a good look at the reconstructed solution that included data from August 13. The SOLVE page showed that the AMDs were all between 15-19 mm/s. Also, the fit did not have the signature that we would have expected had an AMD been missing during that time period. For the sake of completeness, I looked closely at some corrupted data that occurred on August 13 to ensure that it was not caused by a missing AMD. This data had to be removed from our solution, and Eric reminded me that an ISA was written on this data, and a solar flare was identified as the root cause. Since the fit for this batch of orbits appears normal (i.e. no signature) and since the AMDs are spaced at the usual 7-hour intervals, it is clear to me that we are NOT missing any AMDs on August 13. Dah-Ning Yuan also noted problems with the F1 data about a week later. His report: We also reported the anomalous behavior of F1 data over 9/15/00- 9/16/00 to the RMDC team. Based on their response, it might be caused by the solar flare since other projects also experienced similar anomalies during the same time frames. Ancillary Data ============== Data Collection --------------- We have obtained the following files from the FIS: Original File Name Name on SOPC -------------------------------- ------------ AMD: amdgen.00-270.out 0268269A.AMD AMD: amdgen.00-271.out 0269270A.AMD OPT: optg_m_000916_OD6824-6930_rec_V1 0260269A.OPT SAK: mgs_solar_array_2000-269.ck 0269269A.SAK SOE: mm075b.03.tsoe 0275279D.SOE SOE: mm076a.01.tsoe 0279282A.SOE SPK: spk_m_000916_OD6824-6930_rec_V1 0260269A.SPK TCK: mgs_spice_c_kernel_2000-269.ck 0269269A.TCK We have obtained the following files from NAIF and/or IPNG: Original File Name Name on SOPC -------------------------------- ------------ AGK: mgs_hga_ck_2000-09-17.bc 0261261A.AGK MOLA POD Team Orbit Solutions ============================= Data Collection --------------- We have obtained the following files from GEODESY: Original File Name Name on SOPC -------------------------------- ------------ GDN: gdn_ql17_008080250_008151630.tsp 0221228A.GDN GDN: gdn_ql17_008131420_008201030.tsp 0226233A.GDN