PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2007-07-29 NOTE = " E-mail and other messages concerning MGS Radio Science on or about 1999/210." END_OBJECT = TEXT END From rsimpson Fri Feb 18 17:23 PST 2000 Received: (from rsimpson@localhost) by magellan.stanford.edu (8.9.3/8.9.3) id RAA15170; Fri, 18 Feb 2000 17:23:04 -0800 (PST) Date: Fri, 18 Feb 2000 17:23:04 -0800 (PST) From: Dick Simpson 723-3525 Message-Id: <200002190123.RAA15170@magellan.stanford.edu> To: flemoine@ares.gsfc.nasa.gov, rsimpson@magellan.stanford.edu, trish@rodan.jpl.nasa.gov Subject: Re: gap in tracking coverage Cc: medina@mail1.jpl.nasa.gov Content-Type: text Content-Length: 1195 Status: R >In going over some arcs from last July 1999, I found a gap in coverage >from 990728 14:06 20.0 to 990729 1449 50.0, or about 24 hours. >The coverage at 990728 14:06 is at station 45, and it doesn't start >up again until it is picked up at station 54 on 990729 1449. >Is this 24 hour gap for real? Was there really no tracking in this >24 hour interval? This gap appears to be real. The ATDF covering this period runs from 07-27T22:59:58 to 07-30T16:30:00 -- about 64 hrs, compared with the typical 36 hrs or so for an ATDF. If there's a shortage of data on the ATDF, I'd expect a comparable shortage in the ODFs. The clincher is the SOE. The SOE shows no DSN activity on MGS for about the 24 hrs you are asking about. The DSS 45 post-cal wrapped up at 209T14:30:00 and the next MGS pass began with the DSS 54 pre-cal at 210T13:05:00. I don't know what the DSN was doing, but it apparently wasn't tracking MGS. In looking back through our health reports, I see that this was the day we were hit by hackers for the second time in a couple weeks. Since there was SOME data on 209 and 210, I probably didn't notice anything amiss. Margie can relax.