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/120." END_OBJECT = TEXT END From aseel@airmail.fltops.jpl.nasa.gov Thu May 1 05:27:17 2003 Received: from airmail2.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 h411P0d28603; Wed, 30 Apr 2003 18:25:00 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (rsops2.fltops.jpl.nasa.gov [137.228.136.22]) by airmail2.fltops.jpl.nasa.gov (Postfix) with ESMTP id BD29E4332C; Wed, 30 Apr 2003 18:25:01 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h411P1Z12296; Thu, 1 May 2003 01:25:01 GMT Date: Thu, 1 May 2003 01:25:01 GMT From: aseel anabtawi Message-Id: <200305010125.h411P1Z12296@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; Content-Length: 912 DSS: 26 RSR: RSR2A Subchannel: 1 Orbit Number: 18516 Occultation Sense: i SOE: mm274a.05.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/120-11:09:00 End Record: 2003/120-11:19:00 DSS: 26 RSR: RSR2A Subchannel: 1 Orbit Number: 18517 Occultation Sense: i SOE: mm274a.05.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/120-13:07:00 End Record: 2003/120-13:16:00 DSS: 26 RSR: RSR2A Subchannel: 1 Orbit Number: 18518 Occultation Sense: i SOE: mm274a.05.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/120-15:04:00 End Record: 2003/120-15:14:00 DSS: 26 RSR: RSR2A Subchannel: 1 Orbit Number: 18519 Occultation Sense: i SOE: mm274a.05.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/120-17:02:00 End Record: 2003/120-17:12:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Thu May 1 05:27:24 2003 Received: from airmail2.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 h411Q0d28619; Wed, 30 Apr 2003 18:26:00 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (rsops2.fltops.jpl.nasa.gov [137.228.136.22]) by airmail2.fltops.jpl.nasa.gov (Postfix) with ESMTP id C648F4332C; Wed, 30 Apr 2003 18:26:01 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h411Q1h12350; Thu, 1 May 2003 01:26:01 GMT Date: Thu, 1 May 2003 01:26:01 GMT From: aseel anabtawi Message-Id: <200305010126.h411Q1h12350@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; Content-Length: 228 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 18520 Occultation Sense: i SOE: mm274a.05.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/120-19:00:00 End Record: 2003/120-19:10:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Thu May 1 05:27:30 2003 Received: from airmail2.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 h411lxd28630; Wed, 30 Apr 2003 18:47:59 -0700 (PDT) Received: from rsops2.fltops.jpl.nasa.gov (rsops2.fltops.jpl.nasa.gov [137.228.136.22]) by airmail2.fltops.jpl.nasa.gov (Postfix) with ESMTP id 1E49B4332C; Wed, 30 Apr 2003 18:48:01 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h411m1P12914; Thu, 1 May 2003 01:48:01 GMT Date: Thu, 1 May 2003 01:48:01 GMT From: aseel anabtawi Message-Id: <200305010148.h411m1P12914@rsops2.fltops.jpl.nasa.gov> Content-Type: text To: undisclosed-recipients:; Content-Length: 684 DSS: 45 RSR: RSR2B Subchannel: 1 Orbit Number: 18521 Occultation Sense: i SOE: mm274a.05.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/120-20:57:00 End Record: 2003/120-21:07:00 DSS: 45 RSR: RSR2B Subchannel: 1 Orbit Number: 18522 Occultation Sense: i SOE: mm274a.05.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/120-22:55:00 End Record: 2003/120-23:05:00 DSS: 45 RSR: RSR2B Subchannel: 1 Orbit Number: 18522 Occultation Sense: i SOE: mm275a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/121-00:53:00 End Record: 2003/121-01:02:00 -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Thu May 1 01:36:59 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 h418awd28837; Thu, 1 May 2003 01:36:58 -0700 (PDT) Received: from R2D22k (dialin-103.jpl.nasa.gov [128.149.231.103]) by godzilla.jpl.nasa.gov (8.9.3p2.cm/8.9.3) with SMTP id BAA18893; Thu, 1 May 2003 01:36:54 -0700 (PDT) Message-ID: <01bf01c30fbe$5723c230$9865fea9@R2D22k> From: "Aseel Anabtawi" To: "Dick Simpson 723-3525" , , "Kerri Kusza 3-3669" , Cc: "aseel Anabtawi" Subject: Lost Data on DOY 120 Date: Thu, 1 May 2003 01:47:42 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01BC_01C30F83.A7B204E0" 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: 9839 Status: O This is a multi-part message in MIME format. ------=_NextPart_000_01BC_01C30F83.A7B204E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I did not get a chance to send this email before I left work, so=20 I apologize that I'm missing some information, but I'll send it tomorrow. DOY 120, DSS-26 The antenna was red at BOT, so coverage was switched to=20 DSS-15. The Ops Chief paged me and left me voice message=20 on my cell phone to notify me of the change (WOW!!), but I was=20 deep asleep and did not hear either one go off (took Nyquil before=20 I slept, and it completely knocked me out!). I finally get added=20 to the Ops Chiefs list of contacts and I get called, but I don't=20 wake up!!! By the time I got the messages in the morning, two=20 measurements had completed (lost), and coverage was switched=20 back to DSS-26, so the remaining two measurements were fine. =20 I don't have the DR number, but I will provide you with that tomorrow. =20 I'll also send you the times when coverage was switched back to=20 DSS-26 (just before the third measurement). I believe that DSS-25=20 was also brought up for some time to provide uplink because=20 DSS-26 transmitter was down. Also, the SNR during the third measurement was slightly over=20 58 dB, which is what I had for RSR fgain value. I didn't see=20 any clipping warning messages, but it's possible that the data=20 are clipped. DOY 120 DSS 43 =20 (or was it 34?! .. I have to check. It was the second SPC-40=20 pass that day) The last measurement was not collected. This pass started=20 in one sequence and ended in another. I scripted the pass=20 using sequence mm274, but the last measurement was in=20 sequence mm275, so it did not get included in the script. =20 I normally catch this because the software that I use to=20 generate scripts looks for EOT, and in such cases, that would=20 normally be in the later sequence, so if I use the earlier=20 sequence to generate the script, the line for EOT would look=20 like 03/----:--:--:--. This time, however, EOT was in both=20 sequences, so when I generated the script using 274, the EOT=20 line looked fine (I hope this is not confusing). I did not catch=20 this until I was setting up the notification to go out, and noticed=20 that there was enough time between the second measurement=20 and EOT for another measurement. I checked 275, and sure=20 enough, the third measurement was there. It was too late=20 to try to capture it, but I added it to the email notification. I'll=20 check with the sequence team to make sure that nothing was=20 done differently this time, and I'll remind myself to pay more=20 attention to sequence boundaries. Sorry! -Aseel ------=_NextPart_000_01BC_01C30F83.A7B204E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
I did not get a chance to send this = email before I=20 left work, so
I apologize that I'm missing some = information,=20 but I'll send it
tomorrow.
 
DOY 120, DSS-26
The antenna was red at BOT, so coverage = was=20 switched to
DSS-15.  The Ops Chief paged me = and left me=20 voice message
on my cell phone to notify me of the = change=20 (WOW!!), but I was
deep asleep and did=20 not hear either one go off (took Nyquil before
I slept, and it=20 completely knocked me out!).  I finally get = added 
to the Ops Chiefs list of contacts and = I get=20 called, but I don't
wake up!!!  By=20 the time I got the messages in the morning, two
measurements had completed (lost), and coverage was switched=20
back to DSS-26, so the remaining two measurements were=20 fine. 
I don't have the DR number, but I will provide you with that tomorrow. 
I'll also send you=20 the times when coverage was switched = back to=20
DSS-26 (just before the third = measurement). =20 I believe that DSS-25
was also brought up=20 for some time to provide uplink because
DSS-26 transmitter=20 was down.
 
Also, the SNR during the third = measurement was=20 slightly over
58 dB, which is what I had for RSR = fgain=20 value.  I didn't see
any clipping warning messages, but it's = possible=20 that the data
are clipped.
 
DOY 120 DSS 43    =
(or was it 34?! .. I have to = check.  It was=20 the second SPC-40
pass that day)
The last measurement was not = collected.  This=20 pass started
in one sequence and ended in = another.  I=20 scripted the pass
using sequence mm274, but the last = measurement was=20 in
sequence mm275, so it did not get = included in=20 the script. 
I normally catch this because the = software=20 that I use to
generate scripts looks for EOT, and in such cases, that would =
normally be in=20 the later sequence, so if I = use the=20 earlier
sequence to generate=20 the script, the line for EOT would look
like 03/----:--:--:--.  = This time, however, EOT was in both =
sequences, so when I generated the script using 274, the EOT
line looked fine (I hope this is not confusing).  I did not catch =
this until I was setting up the notification to go out, and noticed =
that there was enough time between the second measurement
and EOT for another=20 measurement.  I checked 275, and sure
enough, the third=20 measurement was there.  It was too late
to try to capture=20 it, but I added it to the email notification.  I'll
check with the=20 sequence team to make sure that nothing was
done differently=20 this time, and I'll remind myself to pay more
attention to=20 sequence boundaries.
 
Sorry!
 
-Aseel
------=_NextPart_000_01BC_01C30F83.A7B204E0-- -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Thu May 1 19:57:59 2003 From: "Aseel Anabtawi" To: "Dick Simpson 723-3525" , , "Kerri Kusza 3-3669" , Subject: Re: Lost Data on DOY 120 Date: Thu, 1 May 2003 19:57:45 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C3101B.EED56630 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Here's the missing information: DRs from DSS-26 pass: G102705 and G102706 And that second SPC-40 pass was neither DSS-43 nor DSS-34. It was=20 DSS-45, but you already got that in the today's Health Report.