PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM DATA_SET_ID = "MEX-M-MRS-1/2/3-MCO-0026-V1.0" STANDARD_DATA_PRODUCT_ID = ENB PRODUCER_ID = "SUE" PRODUCT_ID = "M00SUE0L1A_ENB_041001755_00.TXT" PRODUCT_CREATION_TIME = 2005-07-26T17:17:15.000 INSTRUMENT_HOST_ID = "MEX" OBJECT = TEXT PUBLICATION_DATE = 2005-06-10 NOTE = "MEX SUE Experimenter Notes" END_OBJECT = TEXT END From gene.goltz@jpl.nasa.gov Fri Apr 9 11:53:15 2004 Return-Path: Received: from smtp.jpl.nasa.gov (eis-msg-012.jpl.nasa.gov [137.78.160.40]) by magellan.Stanford.EDU (8.11.7p1+Sun/8.11.7) with ESMTP id i39IrFU01871 for ; Fri, 9 Apr 2004 11:53:15 -0700 (PDT) Received: from GGOLTZ-2K.jpl.nasa.gov (ggoltz-2k.jpl.nasa.gov [137.78.78.47]) by smtp.jpl.nasa.gov (8.12.10/8.12.10) with ESMTP id i39IrFMG004629; Fri, 9 Apr 2004 11:53:15 -0700 (PDT) Message-Id: <5.1.0.14.2.20040409114247.017b4c48@pop.jpl.nasa.gov> X-Sender: ggoltz@pop.jpl.nasa.gov X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 09 Apr 2004 11:52:48 -0700 To: Dick Simpson 650-723-3525 From: Gene Goltz Subject: MEX DOY 100 Occultation Data Cc: sami Asmar Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Content-Length: 530 Status: RO Dick, The MEX Occultation on DOY 100 (pass 0313) was performed over DSS-65. I recorded and played back RSR open-loop data as follows: - X-band, 2-way - RSR1B1 - 2 kHz, 16 bits - start = 17:30:00 - LOS = 18:04:45 (approximately) - stop = 18:10:00 - SFDUs = 2,401 You should be able to query these data from the TDS at your leisure. Also, a question about the frequency residuals: do you have any idea as to why we are seeing small (~2 Hz) steps every few minutes? Regards, Gene From rsimpson Fri Apr 9 19:47:39 2004 Return-Path: Received: (from rsimpson@localhost) by magellan.Stanford.EDU (8.11.7p1+Sun/8.11.7) id i3A2laY05714; Fri, 9 Apr 2004 19:47:36 -0700 (PDT) Date: Fri, 9 Apr 2004 19:47:36 -0700 (PDT) From: Dick Simpson 650-723-3525 Message-Id: <200404100247.i3A2laY05714@magellan.Stanford.EDU> To: gene.goltz@jpl.nasa.gov, hinson@rocc.Stanford.EDU, joe@neptune.Stanford.EDU, len.tyler@stanford.Stanford.EDU, paetzold@geo.uni-koeln.de, rsimpson, sami.asmar@jpl.nasa.gov Subject: DSN MEX OCI days 098-100 Content-Length: 4753 Status: R Gene, Sami, Martin, et al: Summary comments from the MEX occultations captured at Madrid on days 098-100. In each case, I queried for only 10-15 minutes based on when Gene Goltz said the occultation happened. About two-thirds of the samples are before occultation, and one-third after. If anyone wants more, we can get it; but we should decide that soon. The RSR/DSN issues noted in the summary report on the 093/095 observations seem to have been resolved. These data look good: the signal is centered, the analog-to-digital converters are not saturated, and spurious signals seem to be at a minimum. If we compare the SOE, DKF, and actual signal behavior over the three days, there are few solid correlations. I have heard from Dwight Holmes that the DSN is complaining because the instructions they receive in SOE/DKF files are being overridden by late-arriving briefing messages and voice commands during the track. This suggests that the SOE and DKF may not be useful in reconstructing spacecraft activity or state. On all three days, the spacecraft appears to be set up for 1-way if we believe the SOE/DKF. There are 60-120 second differences between predicted occultation and observed loss-of-signal. On day 098 the SOE tells us ranging and telemetry go off AFTER the predicted occultation while on the other two days they go off well before. But we see the same carrier levels (including a very brief amplitude spike just before occultation) on days 098 and 099; on day 100, the levels are very different and there is no spike. Over the three days, the best correlation between SOE/DKF and actual signal behavior is the SOE entry "SET DOWNLINK BAND: NONE". The carrier disappears within 5 seconds of this entry on each day. I have no idea what the entry means. Day 098 (DSS 54; X-band only) ----------------------------- 20:17:57 DKF (xd013b.00.dkf) says BEGIN RADIO SCIENCE FIX SUBREFLECTOR 20:28:00 Begin queried data processed at Stanford (8 ksps) Carrier stable (-11 dB with respect to A/D maximum) 20:29:48 SOE (xd013b.00.tsoe) says MEX went 1-way Nothing seen in data 20:33:33 SOE says spacecraft went into Earth occultation 20:34:31 SOE says RANGING OFF TELEMETRY OFF SET DOWNLINK BAND: NONE 20:34:31 Signal rose to -6 dB with respect to A/D maximum; then disappeared (the real occultation?) The one minute error in predicting occultation time means that there were many changes in spacecraft configuration at exactly the time the real occultation took place. It is not clear why the spacecraft went into occultation with telemetry and ranging ON; maybe this was not a radio science activity despite the DKF. Day 099 (DSS 54; X-band only) ----------------------------- 18:41:35 SOE and DKF say telemetry and ranging OFF 19:02:48 DKF says BEGIN RADIO SCIENCE FIX SUBREFLECTOR 19:10:00 Begin queried data processed at Stanford (2 ksps) Carrier stable (-10 dB with respect to A/D maximum) 19:14:37 SOE says MEX went 1-way Nothing seen in data 19:18:22 SOE says MEX enters occultation 19:19:35 SOE says SET DOWNLINK BAND: NONE 19:19:40 Signal rose to -4 dB with respect to A/D maximum; then disappeared (the real occultation?) In the SOE and DKF this looks like the right preparation for an occultation (except for MEX being 1-way). But the signal observed is hardly distinguished from what we see on 098 - very stable and well below A/D saturation, then a big spike in amplitude just before occultation, which is 108 seconds later than predicted. Day 100 (DSS 65; X-band only) ----------------------------- 17:26:38 SOE says telemetry and ranging OFF 17:47:43 DKF says BEGIN RADIO SCIENCE FIX SUBREFLECTOR 17:55:00 Begin queried data processed at Stanford (2 ksps) Carrier level oscillating between -4 and -5 dB below A/D maximum (approx 2 min period) 17:59:31 SOE and DKF say begin 1-way Nothing seen in data 18:03:16 SOE says MEX enters occultation 18:04:39 SOE says SET DOWNLINK BAND: NONE 18:04:43 Signal disappears The preparation for this occultation appears to be very similar to that on day 099; but the carrier is 5-10 dB stronger, it oscillates, and it disappears without the amplitude spike seen on the previous two days. There are several spurs in the power spectra at 150-250 Hz from the carrier. These may be from power line modulation; SNR is nearly 59 dB/Hz in these data and we frequently see spurs at multiples of 50 and/or 60 Hz when SNR is this high. Regards, Dick From rsimpson Mon Apr 12 15:30:16 2004 Return-Path: Received: (from rsimpson@localhost) by magellan.Stanford.EDU (8.11.7p1+Sun/8.11.7) id i3CMUDo27301; Mon, 12 Apr 2004 15:30:13 -0700 (PDT) Date: Mon, 12 Apr 2004 15:30:13 -0700 (PDT) From: Dick Simpson 650-723-3525 Message-Id: <200404122230.i3CMUDo27301@magellan.Stanford.EDU> To: gene.goltz@jpl.nasa.gov, hinson@rocc.Stanford.EDU, joe@neptune.Stanford.EDU, len.tyler@stanford.Stanford.EDU, paetzold@geo.uni-koeln.de, rsimpson, sami.asmar@jpl.nasa.gov Subject: First Close Look at MEX OCI Data Content-Length: 1243 Status: RO Martin: We downloaded the SPK file which covers the occultation captured at DSS 65 on day 100, then looked closely at the amplitude and frequency behavior. As noted in my report last week, there is an oscillation in the carrier level of about 1 dB (peak to peak) and 2 minute period. This does not seem to have any effect on the frequency of the signal. The frequency behaves as we would expect during an entry occultation, but the carrier is cut off at what Hinson believes is about the 50 km altitude in the atmosphere. That is, we see the beginning of the phase retardation in the upper atmosphere; but, before it is fully developed, the spacecraft carrier was turned off. So we do not see the lower 50 km of the atmosphere. If the occultation time had been predicted correctly, we would probably not be suffering from this problem. But it appears from preliminary examination of all the data collected so far that in all cases (except possibly 095) the carrier was turned off before the ray reached the surface. If true, the only way to correct this error is to leave the spacecraft transmitter turned on longer. Dave may have additional details in a follow-up message. Dick From paetzold.martin@web.de Tue Apr 13 09:18:17 2004 Return-Path: Received: from mailgate5.web.de (mailgate5.web.de [217.72.192.165]) by magellan.Stanford.EDU (8.11.7p1+Sun/8.11.7) with ESMTP id i3DGIGU11191 for ; Tue, 13 Apr 2004 09:18:16 -0700 (PDT) Received: by mailgate5.web.de (8.11.6p2/8.11.2/SuSE Linux 8.11.0-0.4) with SMTP id i3DGHt406800; Tue, 13 Apr 2004 18:17:55 +0200 Received: from 80.141.184.71 by freemailng5601.web.de with HTTP; Tue, 13 Apr 2004 18:17:49 +0200 Date: Tue, 13 Apr 2004 18:17:49 +0200 Message-Id: <11926483@web.de> MIME-Version: 1.0 From: =?iso-8859-1?Q?"Martin=20P=E4tzold"?= To: gene.goltz@jpl.nasa.gov, hinson@rocc.Stanford.EDU, joe@neptune.Stanford.EDU, len.tyler@stanford.edu, paetzold@geo.Uni-Koeln.DE, "DickSimpson650-723-3525" , sami.asmar@jpl.nasa.gov Subject: Re: First Close Look at MEX OCI Data Precedence: fm-user Organization: http://freemail.web.de/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Length: 1103 Status: RO Friends, after a long Easter weekend I am still on vacation but back in business..... ok, what we know is - that there may be timing errors of the ESOC event file by up to 2 minutes. - that there are discrepancies between our computations of the occultation time and the event file due to the fact that the Munich group uses an ellipsoidal figure for the shape of Mars and the times of the event file are computed for a sphere. The consequence is that MIRA always produces warning message when compiling our request file. The difference is in the order of a few minutes. - I suspect that the PTR is reflecting the event file times. We are just checking this. - the transmitter is switched off, one minute into the occultation. Probably for the actual SOE the event file was used. we check. Solution: the easiest way would be to change the sequence and switch the transmitter off five minutes into the apparent occultation. At the same time enter the discussion about the Martian figure to change MIRA (that might be of no great success...... in view of the discussions in the past....) Martin From rsimpson Tue Apr 13 12:25:45 2004 Return-Path: Received: (from rsimpson@localhost) by magellan.Stanford.EDU (8.11.7p1+Sun/8.11.7) id i3DJPiA20153; Tue, 13 Apr 2004 12:25:44 -0700 (PDT) Date: Tue, 13 Apr 2004 12:25:44 -0700 (PDT) From: Dick Simpson 650-723-3525 Message-Id: <200404131925.i3DJPiA20153@magellan.Stanford.EDU> To: paetzold.martin@web.de Subject: Re: DOY 101 MEX OCI Cc: rsimpson Content-Length: 1096 Status: R >Dick, does it mean that you covered this occultation at DSS65? >>When it is DSS65 finally, why is there only X-band? According >to my info, there must also be an S-band My messages yesterday were not very clear. I tried to compose reports on both 101 and 102 at the same time, and some of the information became confused. The occultation on 101 was captured at DSS 65; the occultation on 102 was captured at DSS 55. Both were X-band only. I see nothing in the DKF about S-band for the DSS 65 pass; there was some S-band activity on day 100, but not day 101. The same is true for the SOE - there is no mention of S-band after day 100. Without S-band in the DKF, the station personnel will not set up the required hardware. It doesn't matter what Sami's group does in that case; the RSR simply won't be connected to an S-band antenna. Sometimes the 'briefing message' can be used to supersede the information in the DKF; but I don't receive those (except for bistatic radar), and don't know whether they would have included instructions regarding S-band.