PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM DATA_SET_ID = "MEX-M-MRS-1/2/3-MCO-0024-V1.0" STANDARD_DATA_PRODUCT_ID = ENB PRODUCER_ID = "SUE" PRODUCT_ID = "M00SUE0L1A_ENB_040991910_00.TXT" PRODUCT_CREATION_TIME = 2005-07-26T16:36:53.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 07:12:47 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 i39ECk202606 for ; Fri, 9 Apr 2004 07:12:46 -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 i39ECkMG020174; Fri, 9 Apr 2004 07:12:46 -0700 (PDT) Message-Id: <5.1.0.14.2.20040409070418.017a0ed0@pop.jpl.nasa.gov> X-Sender: ggoltz@pop.jpl.nasa.gov X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 09 Apr 2004 07:12:45 -0700 To: Dick Simpson 650-723-3525 From: Gene Goltz Subject: MEX DOY 099 Occultation Data Cc: sami Asmar Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Content-Length: 391 Status: RO Dick, The MEX Occultation on DOY 099 (pass 0312) was performed over DSS-54. I recorded and played back RSR open-loop data as follows: - X-band only, 2-way - RSR1B1 - 2 kHz - start = 18:40:00 - LOS = 19:19:40 (approximately) - stop = 19:25:00 - SFDUs = 2,701 You should be able to query these data from the TDS at your leisure. 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 hinson@rocc.Stanford.EDU Tue Apr 13 11:36:14 2004 Return-Path: Received: from smtp3.Stanford.EDU (smtp3.Stanford.EDU [171.67.16.117]) by magellan.Stanford.EDU (8.11.7p1+Sun/8.11.7) with ESMTP id i3DIaEU16971 for ; Tue, 13 Apr 2004 11:36:14 -0700 (PDT) Received: from rocc.Stanford.EDU (rocc.Stanford.EDU [171.64.90.224]) by smtp3.Stanford.EDU (8.12.11/8.12.11) with ESMTP id i3DIaEgP008584 for ; Tue, 13 Apr 2004 11:36:14 -0700 Received: (from hinson@localhost) by rocc.Stanford.EDU (8.11.6/8.11.6) id i3DIZx606940 for rsimpson@magellan; Tue, 13 Apr 2004 11:35:59 -0700 (PDT) Date: Tue, 13 Apr 2004 11:35:59 -0700 (PDT) From: Dave Hinson 723-3534 Message-Id: <200404131835.i3DIZx606940@rocc.Stanford.EDU> To: rsimpson@magellan.Stanford.EDU Subject: MEX loss of signal X-Sun-Charset: US-ASCII Content-Length: 283 Status: RO On day 2004/099, the command "set downlink band: none" coincides with the last sample prior to the spike in intensity. This is similar to the situation on day 2004/100. In both cases, there is a brief transient and the signal disappears a couple seconds after that command. From hinson@rocc.Stanford.EDU Tue Apr 13 11:11:50 2004 Return-Path: Received: from smtp3.Stanford.EDU (smtp3.Stanford.EDU [171.67.16.117]) by magellan.Stanford.EDU (8.11.7p1+Sun/8.11.7) with ESMTP id i3DIBnU13520 for ; Tue, 13 Apr 2004 11:11:49 -0700 (PDT) Received: from rocc.Stanford.EDU (rocc.Stanford.EDU [171.64.90.224]) by smtp3.Stanford.EDU (8.12.11/8.12.11) with ESMTP id i3DIBntO029879; Tue, 13 Apr 2004 11:11:49 -0700 Received: (from hinson@localhost) by rocc.Stanford.EDU (8.11.6/8.11.6) id i3DIBY506916; Tue, 13 Apr 2004 11:11:34 -0700 (PDT) Date: Tue, 13 Apr 2004 11:11:34 -0700 (PDT) From: Dave Hinson 723-3534 Message-Id: <200404131811.i3DIBY506916@rocc.Stanford.EDU> To: jtwicken@stanford.edu Subject: Re: MEX 04/099 Ingress Cc: rsimpson@magellan.Stanford.EDU X-Sun-Charset: US-ASCII Content-Length: 494 Status: RO Hi Joe, I've looked at the data from the MEX ingress occultation on day 2004/099. The signal vanishes just as we begin to see a small Doppler shift (~0.1 Hz) from the neutral atmosphere. Loss of signal seems to occur when the ray path is still several 10s of kilometers above the surface. The disappearance of the signal is preceded by a large spike in intensity. This is probably a transient associated with the change in the configuration of the spacecraft radio system. Dave From rsimpson Tue Apr 20 05:07:48 2004 Return-Path: Received: (from rsimpson@localhost) by magellan.Stanford.EDU (8.11.7p1+Sun/8.11.7) id i3KC7lE09526; Tue, 20 Apr 2004 05:07:47 -0700 (PDT) Date: Tue, 20 Apr 2004 05:07:47 -0700 (PDT) From: Dick Simpson 650-723-3525 Message-Id: <200404201207.i3KC7lE09526@magellan.Stanford.EDU> To: art.freiley@jpl.nasa.gov, rsimpson Subject: MEX BSR DSS 14 Preliminary Results Content-Length: 3136 Status: R Art: As may have been the case with you, I've been swamped ever since I got back from our Goldstone trip. My plane to France leaves in 10 hrs, and I'll be gone for two weeks. However, I have downloaded all the RSR data (with help from Kamal and Gene Goltz); and I've just finished processing it, though not taken it all the way to system temperatures and noise diode values. The results look MUCH better in terms of linearity, so I'm assuming we have solved at least some of the major problems by going to Goldstone. I'm going to send you the results as I have them as a set of e-mail attachments. There will be 12 e-mails, each with one attachment. Four of the e-mails carry tables of power versus time - one for each of the channels (X-RCP, S-RCP, X-LCP, and S-LCP). The first column in each table gives time in seconds from 0h on 2004-04-08. The second column gives RSR power in the first 1/8th of the spectral window (0-3125 Hz in our case); the spacing is 10 seconds per row. Third column gives power in the range 3125-6250 Hz; ... the ninth column gives power in the range 21875-25000 Hz. The RSR collecting X-RCP data ran for 2506 seconds, so there are 250 rows in that table, each the result of a 10 s time average (and 3125 Hz frequency average). You should be able to load the tables into Excel, then can play with the numbers. It's usually easy to spot where the transitions occur by simply scrolling down. All of the frequency windows change simultaneously, though it usually takes a couple time steps for the new values to stabilize. I hope to do some of this during quiet times on my trip. Another four e-mails carry Postscript plots that show graphically what I have described above for the tables. Each figure includes 8 lines, one for each of the frequency windows. Because of the roll-off at each edge of the filter, Windows 1 and 8 have lower power values than Windows 2-7. With Excel you can average some or all of the windows to improve the noise statistics. Just using my eye and a plastic ruler, I determined that the S-RCP noise diode approximately doubles the power over cold sky. When the ambient load is on, the ADDITIVE effect of the noise diode is very nearly the same - hence my conclusion about linearity. The ambient load appears to be about 15x more noisy than cold sky, yielding a Top on the order of 20K - much better than the 35K is was deriving from the DSS 43 MEX bistatic radar data we collected on 21 January. The final four e-mails carry the same figures in JPEG format. These are poorer resolution than the Postcript plots; but some people find JPEG much easier to display and print, so I'm sending them along. There's not much in the S-LCP data. We never got a chance to compare that one against cold sky; the LNA was connected to the ambient load throughout, and the only change visible is the noise diode going on and off. I hope to be able to talk to you when I get back; but it probably won't be immediately since there are dozens of crises that need to be resolved after you return from two weeks of travel. More later. Thanks, Dick