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/169." END_OBJECT = TEXT END From aseel@airmail.fltops.jpl.nasa.gov Wed Jun 18 07:45:04 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 h5IEj4808622; Wed, 18 Jun 2003 07:45:04 -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 2021810902; Wed, 18 Jun 2003 07:45:01 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h5IEj0713159; Wed, 18 Jun 2003 14:45:00 GMT Date: Wed, 18 Jun 2003 14:45:00 GMT From: aseel anabtawi Message-Id: <200306181445.h5IEj0713159@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; Content-Length: 912 Status: RO DSS: 24 RSR: RSR2A Subchannel: 1 Orbit Number: 19114 Occultation Sense: i SOE: mm289b.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-08:07:00 End Record: 2003/169-08:17:00 DSS: 24 RSR: RSR2A Subchannel: 1 Orbit Number: 19115 Occultation Sense: i SOE: mm289b.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-10:05:00 End Record: 2003/169-10:14:00 DSS: 24 RSR: RSR2A Subchannel: 1 Orbit Number: 19116 Occultation Sense: i SOE: mm289b.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-12:02:00 End Record: 2003/169-12:12:00 DSS: 24 RSR: RSR2A Subchannel: 1 Orbit Number: 19117 Occultation Sense: i SOE: mm289b.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-14:00:00 End Record: 2003/169-14:10:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Thu Jun 19 01:03:09 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 h5J0Yr807746; Wed, 18 Jun 2003 17:34:53 -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 780AB1090C; Wed, 18 Jun 2003 17:35:01 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h5J0Z1G13826; Thu, 19 Jun 2003 00:35:01 GMT Date: Thu, 19 Jun 2003 00:35:01 GMT From: aseel anabtawi Message-Id: <200306190035.h5J0Z1G13826@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; Content-Length: 1368 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 19117 Occultation Sense: i SOE: mm289c.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-14:00:00 End Record: 2003/169-14:10:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 19118 Occultation Sense: i SOE: mm289c.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-15:58:00 End Record: 2003/169-16:08:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 19119 Occultation Sense: i SOE: mm289c.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-17:55:00 End Record: 2003/169-18:05:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 19120 Occultation Sense: i SOE: mm289c.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-19:53:00 End Record: 2003/169-20:03:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 19121 Occultation Sense: i SOE: mm289c.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-21:51:00 End Record: 2003/169-22:00:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 19122 Occultation Sense: i SOE: mm289c.03.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/169-23:48:00 End Record: 2003/169-23:58:00 -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Mon Jun 23 15:25:43 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 h5NMPg807935; Mon, 23 Jun 2003 15:25:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by godzilla.jpl.nasa.gov (8.9.3p2.cm/8.9.3) with SMTP id PAA23796; Mon, 23 Jun 2003 15:25:41 -0700 (PDT) Message-Id: <200306232225.PAA23796@godzilla.jpl.nasa.gov> Date: Mon, 23 Jun 2003 15:25:41 -0700 (PDT) From: Aseel Anabtawi Reply-To: 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-Type: TEXT/plain; charset=us-ascii Content-MD5: iWoD+sIPYXoPbUsafHygrQ== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc Content-Length: 5128 Status: RO 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 ------------- Begin Forwarded Message ------------- -------------------------------------------------------------------------- From: Joe Twicken To: aseel@godzilla.jpl.nasa.gov (Aseel Anabtawi) cc: sami.asmar@jpl.nasa.gov (Sami Asmar), rsimpson@magellan.stanford.edu (Dick Simpson 723-3525), hinson@rocc.stanford.edu (Dave Hinson), len@nova.stanford.edu (len tyler), kusza@stanford.edu (Kerri Kusza) Subject: DSS 24/25 Comparison (2002/344) Date: Mon, 30 Dec 2002 20:53:29 -0800 Hello Aseel- Three ingress occultations (16793i-16795i) were recorded simultaneously on 2002/344 at both DSS 24 and 25. I have processed each open-loop recording, and the results may be found in the tables below. The USO frequency extracted from the recordings at stations 24 and 25 agreed to within 1 mHz for each occultation (Table 1). The SNR for each occultation was better at DSS 25 than DSS 24, the difference ranging from approximately 0.7 to 2 dB (Table 2). The frequency stability at DSS 25 was better than DSS 24 at integration times less than or equal to 4 seconds (the short integration times are those most affected by SNR); at integration times greater than or equal to 8 seconds the stability at station 24 was generally (except in one case) comparable or better than that at 25 (Table 3). Joe ****************************************************************************** Table 1 Estimated USO Frequency (Hz); T = 4.096 sec Occ DSS 24 DSS 25 16793i 8423153056.473 8423153056.473 16794i 8423153056.454 8423153056.454 16795i 8423153056.457 8423153056.458 ****************************************************************************** Table 2 Nominal SNR (dB/Hz) Occ DSS 24 DSS 25 16793i 50.0 50.7 16794i 49.0 51.1 16795i 48.8 50.6 ****************************************************************************** Table 3 Allan deviation Occ 16793i: 2002/344 15:33:00-15:43:00 T, sec DSS 24 DSS 25 (23441533.RSR) (2344153D.RSR) 0.512 7.8722e-13 6.0291e-13 1.024 4.9167e-13 3.0321e-13 2.048 2.1525e-13 1.7368e-13 4.096 1.3759e-13 1.3329e-13 8.192 7.7307e-14 1.0318e-13 32.768 5.8806e-14 7.2344e-14 Occ 16794i: 2002/344 17:31:00-17:41:00 T, sec DSS 24 DSS 25 (23441731.RSR) (2344173B.RSR) 0.512 8.3576e-13 6.3754e-13 1.024 4.6497e-13 2.7653e-13 2.048 2.4717e-13 2.0637e-13 4.096 1.5262e-13 1.2419e-13 8.192 9.8904e-14 9.9287e-14 32.768 1.3624e-13 1.4035e-13 Occ 16795i: 2002/344 17:29:00-19:39:00 T, sec DSS 24 DSS 25 (23441929.RSR) (2344192J.RSR) 0.512 7.5185e-13 5.8786e-13 1.024 4.8157e-13 3.0283e-13 2.048 2.5191e-13 1.8497e-13 4.096 1.6588e-13 1.3272e-13 8.192 1.3773e-13 1.5168e-13 32.768 9.7354e-14 9.3677e-14 ****************************************************************************** ------------- End Forwarded Message ------------- -------------------------------------------------------------------------- From rsimpson@magellan.stanford.edu Mon Jun 30 13:59:38 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 Status: R 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 Mon Jun 23 15:25:43 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 jtwicken@stanford.edu Mon Jun 30 14:22:39 2003 Received: from smtp5.Stanford.EDU (smtp5.Stanford.EDU [171.67.16.30]) by magellan.stanford.edu (8.11.6/8.11.6) with ESMTP id h5ULMc815046 for ; Mon, 30 Jun 2003 14:22:38 -0700 (PDT) Received: (from root@localhost) by smtp5.Stanford.EDU (8.12.9/8.12.9) id h5ULMcGO020532 for rsimpson@magellan.stanford.edu; Mon, 30 Jun 2003 14:22:38 -0700 (PDT) Received: from neptune.Stanford.EDU (neptune.Stanford.EDU [171.64.90.149]) by smtp5.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h5ULMWKq020473; Mon, 30 Jun 2003 14:22:32 -0700 (PDT) Received: from neptune.Stanford.EDU (joe@localhost) by neptune.Stanford.EDU (8.11.6/8.11.6) with ESMTP id h5ULMUJ27205; Mon, 30 Jun 2003 14:22:30 -0700 (PDT) Message-Id: <200306302122.h5ULMUJ27205@neptune.Stanford.EDU> X-Authentication-Warning: neptune.Stanford.EDU: joe owned process doing -bs X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Joe Twicken To: Dick Simpson 723-3525 , aseel@godzilla.jpl.nasa.gov (Aseel Anabtawi) cc: chinsan@magellan.stanford.edu, hinson@rocc.stanford.edu, joe@nova.stanford.edu, kusza@magellan.stanford.edu, len@nova.stanford.edu, sami.asmar@jpl.nasa.gov Subject: Re: Scheduling DSS-24 for MGS In-reply-to: Your message of "Mon, 30 Jun 2003 13:59:36 PDT." <200306302059.h5UKxaD14710@magellan.stanford.edu> References: <200306302059.h5UKxaD14710@magellan.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Jun 2003 14:22:30 -0700 Content-Length: 942 Status: RO I processed the 2003/169 data from DSS 24 late last week after the trajectory reconstruction for that date became available. I will look at the Allan deviations later today over a range of integration times to see if there is anything unusual. I will let you know... >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 jtwicken@stanford.edu Mon Jun 30 23:19:48 2003 Received: from smtp5.Stanford.EDU (smtp5.Stanford.EDU [171.67.16.30]) by magellan.stanford.edu (8.11.6/8.11.6) with ESMTP id h616Jl823295 for ; Mon, 30 Jun 2003 23:19:47 -0700 (PDT) Received: (from root@localhost) by smtp5.Stanford.EDU (8.12.9/8.12.9) id h616JmC0015123 for rsimpson@magellan.Stanford.EDU; Mon, 30 Jun 2003 23:19:48 -0700 (PDT) Received: from neptune.Stanford.EDU (neptune.Stanford.EDU [171.64.90.149]) by smtp5.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h616JgKq015093; Mon, 30 Jun 2003 23:19:43 -0700 (PDT) Received: from neptune.Stanford.EDU (joe@localhost) by neptune.Stanford.EDU (8.11.6/8.11.6) with ESMTP id h616Jgg28831; Mon, 30 Jun 2003 23:19:42 -0700 (PDT) Message-Id: <200307010619.h616Jgg28831@neptune.Stanford.EDU> X-Authentication-Warning: neptune.Stanford.EDU: joe owned process doing -bs X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: Joe Twicken To: aseel@godzilla.jpl.nasa.gov (Aseel Anabtawi) cc: rsimpson@magellan.stanford.edu (Dick Simpson 723-3525), chinsan@magellan.stanford.edu (Chinsan Han), hinson@nova.stanford.edu (Dave Hinson), kusza@stanford.edu (Kerri Kusza), len.tyler@stanford.edu (len), sami.asmar@jpl.nasa.gov (Sami Asmar) Subject: Re: Scheduling DSS-24 for MGS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Jun 2003 23:19:42 -0700 Content-Length: 4326 Status: RO Hello Aseel- Four ingress occultations (19114i-19117i) were recorded on 2003/169 at DSS 24. I have processed each open-loop recording, and determined nominal SNR and Allan Deviation over a range of integration times. This was the day that normal operations resumed after a 7-day MGS C-mode period. I have also determined nominal SNR and Allan Deviation for four open-loop recordings on 2003/161 at DSS 25 (19017i-19020i, just prior to C-mode) and for three open-loop recordings on 2003/170 at DSS 15 (19127i-19129i). It should be noted that there were minor data quality issues with the 2003/170 data at DSS 15 noted in the daily MGS RST Health Report (1 dB steps in the baseline with two of the recordings and +/- 0.5 dB fluctuations with the other). The results may be found in the tables below. As was evident the first time that open-loop data were recorded at DSS 24 (2002/344), the frequency stability at that station is very good in comparison with the other SPC 10 stations at the longest measured integration times (8 seconds and greater). At 4 seconds, the performance at DSS 24 was generally comparable or better than that at the other SPC 10 stations analyzed here. At the shortest integration times (2 seconds and less), the stability at the other SPC 10 stations was generally better than that at DSS 24. As was mentioned by Dick Simpson regarding scheduling DSS-24 for MGS, (1) data from DSS 24 are certainly better than no data at all, and (2) the "long term" stability at that station may actually be superior to that at the other SPC 10 34m stations. Dave Hinson might be able to comment on whether he would prefer better shorter term or longer term stability for retrieval of atmospheric profiles. I will continue to monitor the data quality at DSS 24, and will note any problems which may arise. Joe ****************************************************************************** Table 1a DSS 25, 2003/161 Nominal SNR (dB/Hz) Occ SNR 19017i 58.4 19018i 58.7 19019i 59.7 19020i 59.5 Table 1b Allan deviation T, sec Occ 19017i Occ 19018i Occ 19019i Occ 19020i 0.512 6.3037e-13 5.9790e-13 5.8722e-13 6.3914e-13 1.024 2.8176e-13 2.2411e-13 2.1448e-13 2.3392e-13 2.048 2.2757e-13 1.8178e-13 1.6639e-13 2.0461e-13 4.096 2.0378e-13 1.7270e-13 1.2767e-13 1.8108e-13 8.192 2.0458e-13 1.7319e-13 1.1099e-13 2.1740e-13 32.768 1.4820e-13 2.3888e-13 1.8264e-13 1.9935e-13 ****************************************************************************** Table 2a DSS 24, 2003/169 Nominal SNR (dB/Hz) Occ SNR 19114i 58.7 19115i 59.2 19116i 59.6 19117i 59.1 Table 2b Allan deviation T, sec Occ 19114i Occ 19115i Occ 19116i Occ 19117i 0.512 7.8124e-13 7.2605e-13 7.1330e-13 7.7181e-13 1.024 3.7581e-13 3.8524e-13 3.6511e-13 4.4942e-13 2.048 2.4547e-13 2.1400e-13 2.0561e-13 2.2171e-13 4.096 1.3531e-13 1.4479e-13 1.4419e-13 1.4612e-13 8.192 1.3253e-13 1.1916e-13 8.4962e-14 1.3539e-13 32.768 1.5947e-13 2.5275e-13 1.2875e-13 1.4746e-13 ****************************************************************************** Table 3a DSS 15, 2003/170 Nominal SNR (dB/Hz) Occ SNR 19127i 60.7 19128i 59.6 19129i 61.0 Table 3b Allan deviation T, sec Occ 19127i Occ 19128i Occ 19129i 0.512 5.3098e-13 5.8441e-13 5.6676e-13 1.024 2.2248e-13 2.3665e-13 2.1556e-13 2.048 1.7634e-13 1.8352e-13 1.4546e-13 4.096 1.4943e-13 1.4088e-13 1.5040e-13 8.192 1.2462e-13 1.4140e-13 1.8665e-13 32.768 1.4579e-13 2.0660e-13 2.2827e-13 ******************************************************************************