PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2007-07-31 NOTE = " E-mail and other messages concerning MGS Radio Science on or about 2003/182." END_OBJECT = TEXT END From aseel@airmail.fltops.jpl.nasa.gov Thu Jul 3 20:29:12 2003 Date: Tue, 1 Jul 2003 08:30:00 GMT From: aseel anabtawi To: undisclosed-recipients: ; DSS: 54 RSR: RSR2A Subchannel: 1 Orbit Number: 19270 Occultation Sense: i SOE: mm292b.02.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/182-02:07:00 End Record: 2003/182-02:17:00 DSS: 54 RSR: RSR2A Subchannel: 1 Orbit Number: 19271 Occultation Sense: i SOE: mm292b.02.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/182-04:05:00 End Record: 2003/182-04:14:00 DSS: 54 RSR: RSR2A Subchannel: 1 Orbit Number: 19272 Occultation Sense: i SOE: mm292b.02.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/182-06:02:00 End Record: 2003/182-06:12:00 DSS: 54 RSR: RSR2A Subchannel: 1 Orbit Number: 19273 Occultation Sense: i SOE: mm292b.02.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/182-08:00:00 End Record: 2003/182-08:10:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Tue Jul 1 19:48:24 2003 Received: from airmail1.fltops.jpl.nasa.gov (airmail2.fltops.jpl.nasa.gov [137.228.96.27]) by magellan.stanford.edu (8.11.6/8.11.6) with ESMTP id h61Id5827414; Tue, 1 Jul 2003 11:39:06 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (rsops2.fltops.jpl.nasa.gov [137.228.136.22]) by airmail1.fltops.jpl.nasa.gov (Postfix) with ESMTP id BBFB91091B; Tue, 1 Jul 2003 11:39:01 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h61Id1C07851; Tue, 1 Jul 2003 18:39:01 GMT Date: Tue, 1 Jul 2003 18:39:01 GMT From: aseel anabtawi Message-Id: <200307011839.h61Id1C07851@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; Content-Length: 912 DSS: 14 RSR: RSR2A Subchannel: 1 Orbit Number: 19273 Occultation Sense: i SOE: mm292b.02.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/182-08:00:00 End Record: 2003/182-08:10:00 DSS: 14 RSR: RSR2A Subchannel: 1 Orbit Number: 19274 Occultation Sense: i SOE: mm292b.02.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/182-09:58:00 End Record: 2003/182-10:07:00 DSS: 14 RSR: RSR2A Subchannel: 1 Orbit Number: 19275 Occultation Sense: i SOE: mm292b.02.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/182-11:55:00 End Record: 2003/182-12:05:00 DSS: 14 RSR: RSR2A Subchannel: 1 Orbit Number: 19276 Occultation Sense: i SOE: mm292b.02.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/182-13:53:00 End Record: 2003/182-14:03:00 -------------------------------------------------------------------------- From rsimpson@magellan.stanford.edu Tue Jul 1 19:48:47 2003 Received: (from rsimpson@localhost) by magellan.stanford.edu (8.11.6/8.11.6) id h5UKxaD14710; Mon, 30 Jun 2003 13:59:36 -0700 (PDT) Date: Mon, 30 Jun 2003 13:59:36 -0700 (PDT) From: Dick Simpson 723-3525 Message-Id: <200306302059.h5UKxaD14710@magellan.stanford.edu> To: aseel@godzilla.jpl.nasa.gov, chinsan@magellan.stanford.edu, hinson@rocc.stanford.edu, joe@nova.stanford.edu, kusza@magellan.stanford.edu, len@nova.stanford.edu, rsimpson@magellan.stanford.edu Subject: Re: Scheduling DSS-24 for MGS Cc: sami.asmar@jpl.nasa.gov Content-Length: 2594 Aseel: I've not seen any reply to your message of 23 June. On the basis of Joe's Allan Deviation results, I think there's reason to lean away from DSS 24 when possible, but not enough to make it a big issue. In fact, Joe's results suggest DSS 24 may be BETTER for long term stability than DSS 25. Perhaps we should just see what happens as we collect a few occultations using DSS 24. If a significant difference develops in the data quality, we can revisit the question of whether to 'request' other antennas. But, as you note, the choice may not be meaningful when 'other' equates to 'none'. Dick -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Tue Jul 1 19:48:51 2003 Date: Mon, 23 Jun 2003 15:25:41 -0700 (PDT) From: Aseel Anabtawi Subject: Scheduling DSS-24 for MGS To: len@nova.stanford.edu, hinson@rocc.stanford.edu, rsimpson@magellan.stanford.edu, joe@nova.stanford.edu, kusza@magellan.stanford.edu, chinsan@magellan.stanford.edu Cc: sami.asmar@jpl.nasa.gov MIME-Version: 1.0 Content-MD5: iWoD+sIPYXoPbUsafHygrQ== Hello, I spoke to the new MGS DSN Scheduler about the scheduling of DSS-24. The last time I discussed this with the schedulers, I was told that there were no plans to schedule DSS-24 for MGS. However, there was a DSS-24 pass scheduled on DOY 169 (6/18), and more are coming up on weeks 32 and 33. Back in December, Sal Abbate ran Allan Deviation and Phase Noise tests, and reported that the results did not meet the science requirements for long periods of recordings, and possibly also for short periods of recordings. Joe then compared data recorded simultaneously at DSS-25 and DSS-24, and his report is attached below. The DSN Scheduler told me that the current plans are to utilize DSS-24 for MGS. However, if DSS-24 is scheduled, it's most likely because no other antennas are available and it's down to either DSS-24 or no coverage at all. I told him that if that's the case, then we'd definitely prefer DSS-24 to no coverage. But he also said that if we have antenna preference, that we should let him know. Sal said that he can run more Phase Noise tests if needed, although he doesn't expect the results to be different since nothing changed at DSS-24 since December that would improve the results. The DSN Scheduler said that he can probably schedule some demo passes so that we can collect data over DSS-24 and another SPC-10 antenna simultaneously. Please advise on how to proceed. If no more testing is necessary, please let me know. Regards, Aseel -------------------------------------------------------------------------- From Aseel.Anabtawi@jpl.nasa.gov Wed Jul 2 09:39:02 2003 Received: from godzilla.jpl.nasa.gov (godzilla.jpl.nasa.gov [137.78.78.95]) by magellan.stanford.edu (8.11.6/8.11.6) with ESMTP id h62Gd1804320; Wed, 2 Jul 2003 09:39:01 -0700 (PDT) Received: from R2D22k (dialin-087.jpl.nasa.gov [128.149.231.87]) by godzilla.jpl.nasa.gov (8.9.3p2.cm/8.9.3) with SMTP id JAA28188; Wed, 2 Jul 2003 09:38:55 -0700 (PDT) Message-ID: <044c01c340ba$35c5b530$9865fea9@R2D22k> From: "Aseel Anabtawi" To: "Dick Simpson 723-3525" , , "Kerri Kusza 3-3669" , "Chinsan Han" Subject: 2003/182 at DSS 63 Date: Wed, 2 Jul 2003 09:51:39 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0449_01C3407F.887D1970" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Content-Length: 1361 Status: R This is a multi-part message in MIME format. ------=_NextPart_000_0449_01C3407F.887D1970 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, The first measurement (19281i) was not captured because I did not script the pass in time. The measurement started just before BOT. Regards, Aseel -------------------------------------------------------------------------- From flemoine@ishtar.gsfc.nasa.gov Tue Oct 28 08:02:42 2003 Received: from ishtar.gsfc.nasa.gov (ishtar.gsfc.nasa.gov [128.183.107.195]) by magellan.stanford.edu (8.11.6/8.11.6) with ESMTP id h9SG2fQ22886 for ; Tue, 28 Oct 2003 08:02:41 -0800 (PST) Received: (from flemoine@localhost) by ishtar.gsfc.nasa.gov (8.11.7+Sun/8.9.1) id h9SG2SE00404 for rsimpson@magellan.stanford.edu; Tue, 28 Oct 2003 11:02:28 -0500 (EST) Date: Tue, 28 Oct 2003 11:02:28 -0500 (EST) From: flemoine@ishtar.gsfc.nasa.gov Message-Id: <200310281602.h9SG2SE00404@ishtar.gsfc.nasa.gov> To: rsimpson@magellan.stanford.edu Subject: two-way tracking Content-Length: 327 Status: RO Dick- I see a lack of two-way tracking for 48-hrs from 2003-06-29 08:10 to 2003-07-01 08:57. There are some one-way passes in this period. Is this information consistent with your records and sources? 48-hrs seems a long time to go without regular two-way tracking. Could this have been related to the MER launch? Frank