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 2006/116." END_OBJECT = TEXT END From Maria.Schellpfeffer@jpl.nasa.gov Wed Mar 29 14:04:03 2006 Return-Path: Received: from nmta2.jpl.nasa.gov (nmta2.jpl.nasa.gov [137.78.160.215]) by magellan.stanford.edu (8.11.7p1+Sun/8.11.7) with ESMTP id k2TM43d13902 for ; Wed, 29 Mar 2006 14:04:03 -0800 (PST) Received: from xmta3.jpl.nasa.gov (xmta3.jpl.nasa.gov [137.78.160.111]) by nmta2.jpl.nasa.gov (Switch-3.1.8/Switch-3.1.7) with ESMTP id k2TM42Hg020547; Wed, 29 Mar 2006 14:04:02 -0800 Received: from bigwood-xp.jpl.nasa.gov (pc04040103217.jpl.nasa.gov [137.78.144.67]) by xmta3.jpl.nasa.gov (Switch-3.1.8/Switch-3.1.7) with ESMTP id k2TM3wn6007730; Wed, 29 Mar 2006 14:04:01 -0800 Message-Id: <6.1.1.1.2.20060329134319.0417f3f0@mail.jpl.nasa.gov> X-Sender: mschell@mail.jpl.nasa.gov X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1 Date: Wed, 29 Mar 2006 14:03:58 -0800 To: Daniel S Kahan From: Maria Schellpfeffer Subject: Re: February Ingress Cc: sami.asmar@jpl.nasa.gov, aseel.anabtawi@jpl.nasa.gov, David Hinson , len.tyler@stanford.edu, rsimpson@magellan.stanford.edu In-Reply-To: <55fac5798f.5798f55fac@jpl.nasa.gov> References: <55fac5798f.5798f55fac@jpl.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Source-IP: pc04040103217.jpl.nasa.gov [137.78.144.67] X-Source-Sender: Maria.Schellpfeffer@jpl.nasa.gov X-AUTH: Internal IP Content-Length: 8044 Status: O Danny, I agree that it makes the most sense for the request for a specific campaign to come from the radio science team. I think I was just sort of operating under the way things were done during Beta-Supplement for the egress scans where we handled the scheduling of them. However, since implementing the ingress scans has a lot less impact on the background sequence than the egress scans did, we can basically accommodate a request for any date, as long as we know early enough to get it in the build cycle. I think the best way to handle this would be for the Radio Science team to identify a few days that would be desirable for conducting ingress scans - successive days would be fine. I could then look at the DSN coverage and orbit planning to pick the best one from a mission planning point of view. We can plan to discuss it during the next available Mission Planning meeting and then get it in the build after that. This way, there should be many more people aware of the campaign, and if any information is missing, we'll be in a much better position to catch it. I think Dale's latest analysis showed June 19 as the date we'd be able to resume normal ingress measurements. We could support one or possibly two campaigns - if it would be valuable - during the time from May 1 - June 19. I'll probably touch on the topic at the next Mission Planning meeting to let everyone know what we figured out and that we will not be conducting a campaign any earlier than May 1. I don't know how far in advance you are able to determine whether a specific day for an ingress campaign would be valuable, but I think we'd be safe to say that we could get everything incorporated if the request was initiated 3 weeks prior to the requested day. That's not a hard deadline - just a suggestion so we have time to comfortably discuss it at a Mission Planning meeting and build it into the background sequence. Does this all sound okay? Thanks, Maria At 05:27 PM 3/28/2006, Daniel S Kahan wrote: >Maria, > >We checked our email records, and they are basically consistent with what >you've described. And I know we did not attend that meeting. I wish I had >thought to follow up with you after the campaign was brought up, but I'm >sure that after a few weeks it slipped from my radar. Therefore, I agree >with your assessment of the reason for lack of data collection. > >As you suggested, if we can be more involved in choosing the time of the >campaigns, it would certainly elliminate this problem in unusual >circumstances since we'd be expecting them. Also, considering that there >are limited opportunities to do these scans, we could select times that >would be the most valuable. I'm sure we'd be glad to provide that >information if it is then reasonable for you to work it into your sequence. > >It seems that April is not that valuable; perhaps you can tell us how >often and how many more of these campaigns we can do before we return to >nominal operations. > >As always, we appreciate your efforts, > >Danny > >----- Original Message ----- >From: Maria Schellpfeffer >Date: Tuesday, March 28, 2006 10:03 am >Subject: Re: February Ingress > > > Hi Danny, > > > > I'm trying to put together the ISA on not collecting the data > > during the > > last ingress campaign. As I said in the meeting, I think the > > reason was > > strictly a lack of communication. However, that doesn't really > > alleviate > > the problem that occurs when I am the only one responsible for the > > information and I end up being out of the office, like I was in > > this > > case. So I'm trying to track down exactly what happened and > > figure out a > > way to make sure things like this don't happen again. Obviously I > > will do > > my best to not let it slip, but there is always the chance of > > unexpected > > circumstances. > > > > From my email records, I see that we scheduled a topic to discuss > > an > > ingress campaign at the 1/24/06 Mission Planning Meeting. The > > charts that > > went out with that agenda were from Dale Howell and described the > > method we > > intended to use for performing the ingress scans. The next email > > I can > > find is to Kelly Bender with TES, explaining that we'd "talked > > about it at > > the team meeting today, and decided we'd like to do a campaign in > > February". I don't have any other records stating that we > > specifically > > decided on the date of Feb 20 in the Mission Planning meeting, > > other than > > this reference. Do you or any of the other RS team members have a > > record > > of attending this meeting and/or whether we'd decided to do the > > scans on > > that date? > > > > Finally, I'm also wondering how valuable ingress campaigns are > > during this > > time period. When the original issue was brought up, I believe > > the > > statement from Radio Science was that ingress measurements during > > this time > > would have moderate value and that they should be pursued if they > > required > > little effort and proved low risk. I believe we meet the low risk > > and > > effort conditions, provided Dale does not find any issues with > > needing to > > do anything but go to nadir for the measurement, but I'd like to > > be sure > > that this is something the Radio Science team desires. If the > > request to > > do the ingress campaign is coming from the RS team, rather than > > the project > > (or me) just blindly scheduling a time - which is how I would > > describe the > > situation so far - I think it would be less likely that > > information would > > get lost, since your team would be expecting the information. > > > > I appreciate any information and/or suggestions. We want to > > continue to > > support the Radio Science team and experiment to our full > > capability in the > > extended mission time frame, and I'd like to be sure we're all > > heading down > > that track as much as possible. > > > > Thanks! > > Maria > > > > At 07:49 AM 3/28/2006, Maria Schellpfeffer wrote: > > > > >Hi Danny, > > > > > >I looked through my emails and couldn't find any reference to a > > final > > >report or anything either, but I see that we did have the > > commands in the > > >background sequence. > > > > > >I was out for the week and a half prior to the ingress scans we > > had > > >planned for unexpected reasons, and I guess things just fell > > through the > > >cracks...I remember talking with the team afterwards about > > momentum and > > >such, but I don't remember there being any discussion about the > > RS team > > >not being notified, or not collecting the data. I'm sorry that > > >happened. We'll be sure you have the correct information this > > time > > >around, and we can talk about it more at the meeting today. > > > > > >Thanks, > > >Maria > > > > > > > > > > > >At 05:40 PM 3/27/2006, you wrote: > > >>Maria, > > >> > > >>In regards to the February 20 ingress campaign referred to in > > the meeting > > >>agenda (and earlier when we spoke), I must unfortunately report > > that we > > >>never recorded any data. Although we can find reference to the > > campaign > > >>being planned, we have no record of a final date being set or a > > time > > >>schedule/sequence to review, as was sent for the previous egress > > campaigns.>> > > >>I plan to call in to tomorrow's mission planning meeting. Please > > let us > > >>know if there are any products for us to review for the upcoming > > >>campaign, and we'll make sure to get this one. > > >> > > >>Thanks, > > >> > > >>Danny > > > > > > > > >-------------------------------------------------------- > > >Maria Schellpfeffer > > >Mars Global Surveyor Project > > >Mission Planning & Sequencing Team > > >Jet Propulsion Laboratory > > >Office: (818) 393-0514 > > >Cell: (818) 731-4860 > > >Fax: (818) 393-3147 > > >Email: Maria.Schellpfeffer@jpl.nasa.gov > > >Office: 264-235F > > >-------------------------------------------------------- -------------------------------------------------------------------------- From Daniel.S.Kahan-121461@jpl.nasa.gov Wed Mar 29 15:06:49 2006 From: Daniel S Kahan To: Maria Schellpfeffer Cc: sami.asmar@jpl.nasa.gov, aseel.anabtawi@jpl.nasa.gov, David Hinson , len.tyler@stanford.edu, rsimpson@magellan.stanford.edu Date: Wed, 29 Mar 2006 15:06:48 -0800 MIME-Version: 1.0 Content-Language: en Subject: Re: February Ingress X-Accept-Language: en Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Source-IP: eis-msg-065.jpl.nasa.gov [137.78.160.102] X-Source-Sender: Daniel.S.Kahan-121461@jpl.nasa.gov X-AUTH: Internal IP This sounds very good to me. Dave, Dick, when would it be best to conduct a couple of ingress scans in May/June? -------------------------------------------------------------------------- From dhinson@stanford.edu Wed Mar 29 16:18:02 2006 Return-Path: Received: from smtp2.Stanford.EDU (smtp2.Stanford.EDU [171.67.16.125]) by magellan.stanford.edu (8.11.7p1+Sun/8.11.7) with ESMTP id k2U0I1d26245 for ; Wed, 29 Mar 2006 16:18:01 -0800 (PST) Received: from [171.64.91.124] (atmosdyn.Stanford.EDU [171.64.91.124]) by smtp2.Stanford.EDU (8.12.11/8.12.11) with ESMTP id k2U0HxS3007986; Wed, 29 Mar 2006 16:18:00 -0800 Mime-Version: 1.0 X-Sender: dhinson@dhinson.pobox.stanford.edu Message-Id: In-Reply-To: <798d479419.79419798d4@jpl.nasa.gov> References: <798d479419.79419798d4@jpl.nasa.gov> Date: Wed, 29 Mar 2006 16:18:16 -0800 To: Daniel S Kahan From: David Hinson Subject: Re: February Ingress Cc: sami.asmar@jpl.nasa.gov, rsimpson@magellan.stanford.edu, len.tyler@stanford.edu Content-Type: text/plain; charset="us-ascii" ; format="flowed" Content-Length: 196 Status: O Hi Danny, Well, the timing is not critical. Let's ask for one around May 10th and another around June 1st. Normal ingress observations would resume around June 19th. Sound ok? Thanks, Dave -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Wed Apr 26 10:38:02 2006 Received: from mx2.stanford.edu (mx2.Stanford.EDU [171.67.22.30]) by magellan.stanford.edu (8.11.7p2+Sun/8.11.7) with ESMTP id k3QHc2208190 for ; Wed, 26 Apr 2006 10:38:02 -0700 (PDT) Received: by mx2.stanford.edu (Postfix) id 44B874BE87; Wed, 26 Apr 2006 10:38:02 -0700 (PDT) Delivered-To: rfj@stanford.edu Received: from mx2.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 39E744BE83; Wed, 26 Apr 2006 10:38:02 -0700 (PDT) Received: from airmail.fltops.jpl.nasa.gov (airmail2.fltops.jpl.nasa.gov [137.228.96.27]) by mx2.stanford.edu (Postfix) with ESMTP id EB0EE4BE7F; Wed, 26 Apr 2006 10:38:01 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (rsops2.fltops.jpl.nasa.gov [137.228.136.22]) by airmail.fltops.jpl.nasa.gov (Postfix) with ESMTP id AA84A1090D; Wed, 26 Apr 2006 10:37:31 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (localhost [127.0.0.1]) by rsops2.fltops.jpl.nasa.gov (8.12.10+Sun/8.12.8) with ESMTP id k3QHc1PC005019; Wed, 26 Apr 2006 17:38:01 GMT Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.12.10+Sun/8.12.8/Submit) id k3QHc11G005018; Wed, 26 Apr 2006 17:38:01 GMT Date: Wed, 26 Apr 2006 17:38:01 GMT From: aseel anabtawi Message-Id: <200604261738.k3QHc11G005018@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; DSS: 24 RSR: RSR1A Subchannel: 1 Orbit Number: 31866 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/115-23:14:00 End Record: 2006/115-23:27:00 DSS: 24 RSR: RSR1A Subchannel: 1 Orbit Number: 31867 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-01:12:00 End Record: 2006/116-01:25:00 DSS: 24 RSR: RSR1A Subchannel: 1 Orbit Number: 31868 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-03:10:00 End Record: 2006/116-03:22:00 DSS: 24 RSR: RSR1A Subchannel: 1 Orbit Number: 31869 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-05:07:00 End Record: 2006/116-05:20:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Wed Apr 26 10:39:02 2006 Received: from mx2.stanford.edu (mx2.Stanford.EDU [171.67.22.30]) by magellan.stanford.edu (8.11.7p2+Sun/8.11.7) with ESMTP id k3QHd2208268 for ; Wed, 26 Apr 2006 10:39:02 -0700 (PDT) Received: by mx2.stanford.edu (Postfix) id DEE8D4BE08; Wed, 26 Apr 2006 10:39:01 -0700 (PDT) Delivered-To: rfj@stanford.edu Received: from mx2.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id D4C974BE11; Wed, 26 Apr 2006 10:39:01 -0700 (PDT) Received: from airmail.fltops.jpl.nasa.gov (airmail2.fltops.jpl.nasa.gov [137.228.96.27]) by mx2.stanford.edu (Postfix) with ESMTP id B06224BDE7; Wed, 26 Apr 2006 10:39:01 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (rsops2.fltops.jpl.nasa.gov [137.228.136.22]) by airmail.fltops.jpl.nasa.gov (Postfix) with ESMTP id 5763B1090D; Wed, 26 Apr 2006 10:38:31 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (localhost [127.0.0.1]) by rsops2.fltops.jpl.nasa.gov (8.12.10+Sun/8.12.8) with ESMTP id k3QHd1PC005099; Wed, 26 Apr 2006 17:39:01 GMT Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.12.10+Sun/8.12.8/Submit) id k3QHd1bY005098; Wed, 26 Apr 2006 17:39:01 GMT Date: Wed, 26 Apr 2006 17:39:01 GMT From: aseel anabtawi Message-Id: <200604261739.k3QHd1bY005098@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; DSS: 54 RSR: RSR1A Subchannel: 1 Orbit Number: 31872 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-11:01:00 End Record: 2006/116-11:13:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Thu Apr 27 14:09:05 2006 Received: from mx2.stanford.edu (mx2.Stanford.EDU [171.67.22.30]) by magellan.stanford.edu (8.11.7p2+Sun/8.11.7) with ESMTP id k3RL95221988 for ; Thu, 27 Apr 2006 14:09:05 -0700 (PDT) Received: by mx2.stanford.edu (Postfix) id 610D14BEC5; Thu, 27 Apr 2006 14:09:07 -0700 (PDT) Delivered-To: rfj@stanford.edu Received: from mx2.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 510F14BDB1; Thu, 27 Apr 2006 14:09:07 -0700 (PDT) Received: from airmail.fltops.jpl.nasa.gov (airmail2.fltops.jpl.nasa.gov [137.228.96.27]) by mx2.stanford.edu (Postfix) with ESMTP id 108F64BEB1; Thu, 27 Apr 2006 14:09:05 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (rsops2.fltops.jpl.nasa.gov [137.228.136.22]) by airmail.fltops.jpl.nasa.gov (Postfix) with ESMTP id 157681090B; Thu, 27 Apr 2006 14:08:35 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (localhost [127.0.0.1]) by rsops2.fltops.jpl.nasa.gov (8.12.10+Sun/8.12.8) with ESMTP id k3RL91PC006311; Thu, 27 Apr 2006 21:09:01 GMT Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.12.10+Sun/8.12.8/Submit) id k3RL91Pb006310; Thu, 27 Apr 2006 21:09:01 GMT Date: Thu, 27 Apr 2006 21:09:01 GMT From: aseel anabtawi Message-Id: <200604272109.k3RL91Pb006310@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; DSS: 63 RSR: RSR1B Subchannel: 1 Orbit Number: 31874 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-14:56:00 End Record: 2006/116-15:09:00 DSS: 63 RSR: RSR1B Subchannel: 1 Orbit Number: 31875 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-16:54:00 End Record: 2006/116-17:07:00 DSS: 63 RSR: RSR1B Subchannel: 1 Orbit Number: 31876 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-18:52:00 End Record: 2006/116-19:04:00 -------------------------------------------------------------------------- Return-Path: Received: from mx2.stanford.edu (mx2.Stanford.EDU [171.67.22.30]) by pobox02.stanford.edu (Cyrus v2.2.12) with LMTPA; Thu, 27 Apr 2006 14:25:05 -0700 X-Sieve: CMU Sieve 2.2 Received: by mx2.stanford.edu (Postfix) id 681204BE9E; Thu, 27 Apr 2006 14:25:05 -0700 (PDT) Delivered-To: jtwicken@stanford.edu Received: from mx2.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 5DCC64BE05 for ; Thu, 27 Apr 2006 14:25:05 -0700 (PDT) Received: from nmta1.jpl.nasa.gov (nmta1.jpl.nasa.gov [137.78.160.214]) by mx2.stanford.edu (Postfix) with ESMTP id D769C4BEDA for ; Thu, 27 Apr 2006 14:25:04 -0700 (PDT) Received: from xmta2.jpl.nasa.gov (xmta2.jpl.nasa.gov [137.78.160.56]) by nmta1.jpl.nasa.gov (Switch-3.1.8/Switch-3.1.7) with ESMTP id k3RLP3sZ026864; Thu, 27 Apr 2006 14:25:04 -0700 Received: from jpl.nasa.gov (eis-msg-065.jpl.nasa.gov [137.78.160.102]) by xmta2.jpl.nasa.gov (Switch-3.1.8/Switch-3.1.7) with ESMTP id k3RLP3Kp022008; Thu, 27 Apr 2006 14:25:03 -0700 Received: from [137.78.160.72] (Forwarded-For: [137.78.78.109]) by mailhost4.jpl.nasa.gov (mshttpd); Thu, 27 Apr 2006 21:25:03 GMT From: Daniel S Kahan To: Dick Simpson 723-3525 Cc: jtwicken@stanford.edu, Aseel Anabtawi Message-ID: Date: Thu, 27 Apr 2006 21:25:03 GMT X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar 3 2004) MIME-Version: 1.0 Content-Language: en Subject: 2006/116 at DSS-63 X-Accept-Language: en Priority: normal Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Source-IP: eis-msg-065.jpl.nasa.gov [137.78.160.102] X-Source-Sender: Daniel.S.Kahan-121461@jpl.nasa.gov X-AUTH: Internal IP Hello, The first two occultations (31874e & 31875e) on DOY 116 at DSS-63 show no signal because the antenna was not able to move until 18:26 (DR #M103672). Regards, Danny DSS: 63 RSR: RSR1B Subchannel: 1 Orbit Number: 31874 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-14:56:00 End Record: 2006/116-15:09:00 DSS: 63 RSR: RSR1B Subchannel: 1 Orbit Number: 31875 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-16:54:00 End Record: 2006/116-17:07:00 DSS: 63 RSR: RSR1B Subchannel: 1 Orbit Number: 31876 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-18:52:00 End Record: 2006/116-19:04:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Thu Apr 27 14:20:02 2006 Received: from mx3.stanford.edu (mx3.Stanford.EDU [171.67.20.23]) by magellan.stanford.edu (8.11.7p2+Sun/8.11.7) with ESMTP id k3RLK2223025 for ; Thu, 27 Apr 2006 14:20:02 -0700 (PDT) Received: by mx3.stanford.edu (Postfix) id 23DB84BEE3; Thu, 27 Apr 2006 14:20:04 -0700 (PDT) Delivered-To: rfj@stanford.edu Received: from mx3.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 173EF4BEE0; Thu, 27 Apr 2006 14:20:04 -0700 (PDT) Received: from airmail.fltops.jpl.nasa.gov (airmail2.fltops.jpl.nasa.gov [137.228.96.27]) by mx3.stanford.edu (Postfix) with ESMTP id CCD6C4BE49; Thu, 27 Apr 2006 14:20:03 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (rsops2.fltops.jpl.nasa.gov [137.228.136.22]) by airmail.fltops.jpl.nasa.gov (Postfix) with ESMTP id 3F5EB10902; Thu, 27 Apr 2006 14:19:35 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (localhost [127.0.0.1]) by rsops2.fltops.jpl.nasa.gov (8.12.10+Sun/8.12.8) with ESMTP id k3RLK1PC006434; Thu, 27 Apr 2006 21:20:01 GMT Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.12.10+Sun/8.12.8/Submit) id k3RLK1KP006433; Thu, 27 Apr 2006 21:20:01 GMT Date: Thu, 27 Apr 2006 21:20:01 GMT From: aseel anabtawi Message-Id: <200604272120.k3RLK1KP006433@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; DSS: 14 RSR: RSR1A Subchannel: 1 Orbit Number: 31877 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-20:49:00 End Record: 2006/116-21:02:00 -------------------------------------------------------------------------- Return-Path: Received: from mx1.stanford.edu (mx1.Stanford.EDU [171.67.22.29]) by pobox02.stanford.edu (Cyrus v2.2.12) with LMTPA; Thu, 27 Apr 2006 14:29:46 -0700 X-Sieve: CMU Sieve 2.2 Received: by mx1.stanford.edu (Postfix) id 87DD44BE45; Thu, 27 Apr 2006 14:29:46 -0700 (PDT) Delivered-To: jtwicken@stanford.edu Received: from mx1.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 7BEEF4BE38 for ; Thu, 27 Apr 2006 14:29:46 -0700 (PDT) Received: from nmta3.jpl.nasa.gov (nmta.jpl.nasa.gov [137.78.160.108]) by mx1.stanford.edu (Postfix) with ESMTP id 33CE74BE6D for ; Thu, 27 Apr 2006 14:29:44 -0700 (PDT) Received: from xmta2.jpl.nasa.gov (xmta2.jpl.nasa.gov [137.78.160.56]) by nmta3.jpl.nasa.gov (Switch-3.1.8/Switch-3.1.7) with ESMTP id k3RLThTF015659; Thu, 27 Apr 2006 14:29:43 -0700 Received: from jpl.nasa.gov (eis-msg-065.jpl.nasa.gov [137.78.160.102]) by xmta2.jpl.nasa.gov (Switch-3.1.8/Switch-3.1.7) with ESMTP id k3RLTgcY023881; Thu, 27 Apr 2006 14:29:43 -0700 Received: from [137.78.160.72] (Forwarded-For: [137.78.78.109]) by mailhost4.jpl.nasa.gov (mshttpd); Thu, 27 Apr 2006 21:29:42 GMT From: Daniel S Kahan To: Dick Simpson 723-3525 Cc: jtwicken@stanford.edu, Aseel Anabtawi Message-ID: Date: Thu, 27 Apr 2006 21:29:42 GMT X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar 3 2004) MIME-Version: 1.0 Content-Language: en Subject: 2006/116 at DSS-14 X-Accept-Language: en Priority: normal Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Source-IP: eis-msg-065.jpl.nasa.gov [137.78.160.102] X-Source-Sender: Daniel.S.Kahan-121461@jpl.nasa.gov X-AUTH: Internal IP Hello, Occultation 31877e shows no signal because of a late change in DSN coverage to DSS-25 in order to perform corrective maintenance at DSS-14. There was no other radio science scheduled during the DSS-25 track, so a log was not sent. Regards, Danny DSS: 14 RSR: RSR1A Subchannel: 1 Orbit Number: 31877 Occultation Sense: e SOE: mm476a.06.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2006/116-20:49:00 End Record: 2006/116-21:02:00