PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 2007-09-11 NOTE = " E-mail and other messages concerning MGS Radio Science on or about 2003/110." END_OBJECT = TEXT END From aseel@airmail.fltops.jpl.nasa.gov Tue Apr 22 00:10:50 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 h3L5WOk22248; Sun, 20 Apr 2003 22:32:24 -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 2725843332; Sun, 20 Apr 2003 22:34:02 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h3L5Y1Z25524; Mon, 21 Apr 2003 05:34:01 GMT Date: Mon, 21 Apr 2003 05:34:01 GMT From: aseel anabtawi Message-Id: <200304210534.h3L5Y1Z25524@rsops2.fltops.jpl.nasa.gov> To: aseel.anabtawi@jpl.nasa.gov, data@magellan.stanford.edu, joe@neptune.stanford.edu, kusza@magellan.stanford.edu, rsimpson@magellan.stanford.edu Content-Length: 1140 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 18385 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/109-18:12:00 End Record: 2003/109-18:22:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 18386 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/109-20:10:00 End Record: 2003/109-20:19:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 18387 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/109-22:07:00 End Record: 2003/109-22:17:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 18388 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-00:05:00 End Record: 2003/110-00:15:00 DSS: 34 RSR: RSR2A Subchannel: 1 Orbit Number: 18389 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-02:03:00 End Record: 2003/110-02:12:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Tue Apr 22 00:12:52 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 h3L5eNk22262; Sun, 20 Apr 2003 22:40:23 -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 279224332F; Sun, 20 Apr 2003 22:42:01 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h3L5g0F25583; Mon, 21 Apr 2003 05:42:00 GMT Date: Mon, 21 Apr 2003 05:42:00 GMT From: aseel anabtawi Message-Id: <200304210542.h3L5g0F25583@rsops2.fltops.jpl.nasa.gov> To: aseel.anabtawi@jpl.nasa.gov, data@magellan.stanford.edu, joe@neptune.stanford.edu, kusza@magellan.stanford.edu, rsimpson@magellan.stanford.edu Content-Length: 912 DSS: 54 RSR: RSR2A Subchannel: 1 Orbit Number: 18390 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-04:00:00 End Record: 2003/110-04:10:00 DSS: 54 RSR: RSR2A Subchannel: 1 Orbit Number: 18391 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-05:58:00 End Record: 2003/110-06:08:00 DSS: 54 RSR: RSR2A Subchannel: 1 Orbit Number: 18392 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-07:56:00 End Record: 2003/110-08:06:00 DSS: 54 RSR: RSR2A Subchannel: 1 Orbit Number: 18393 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-09:53:00 End Record: 2003/110-10:03:00 -------------------------------------------------------------------------- From aseel@airmail.fltops.jpl.nasa.gov Tue Apr 22 00:17:04 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 h3L5KNk22222; Sun, 20 Apr 2003 22:20:23 -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 2CA724332F; Sun, 20 Apr 2003 22:22:01 -0700 (PDT) Received: (from aseel@localhost) by rsops2.fltops.jpl.nasa.gov (8.11.6+Sun/8.11.6) id h3L5M0h25390; Mon, 21 Apr 2003 05:22:00 GMT Date: Mon, 21 Apr 2003 05:22:00 GMT From: aseel anabtawi Message-Id: <200304210522.h3L5M0h25390@rsops2.fltops.jpl.nasa.gov> To: aseel.anabtawi@jpl.nasa.gov, data@magellan.stanford.edu, joe@neptune.stanford.edu, kusza@magellan.stanford.edu, rsimpson@magellan.stanford.edu Content-Length: 1140 DSS: 25 RSR: RSR2A Subchannel: 1 Orbit Number: 18393 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-09:53:00 End Record: 2003/110-10:03:00 DSS: 25 RSR: RSR2A Subchannel: 1 Orbit Number: 18394 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-11:51:00 End Record: 2003/110-12:01:00 DSS: 25 RSR: RSR2A Subchannel: 1 Orbit Number: 18395 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-13:49:00 End Record: 2003/110-13:59:00 DSS: 25 RSR: RSR2A Subchannel: 1 Orbit Number: 18396 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-15:46:00 End Record: 2003/110-15:56:00 DSS: 25 RSR: RSR2A Subchannel: 1 Orbit Number: 18397 Occultation Sense: i SOE: mm272a.04.tsoe Ground Mode: 1 Uplink Station: -- Sampling Rate: 2K Bit Resolution: 16 Begin Record: 2003/110-17:44:00 End Record: 2003/110-17:54:00 -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Wed Apr 23 10:49:32 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 h3NHnVk15721; Wed, 23 Apr 2003 10:49:31 -0700 (PDT) Received: from aseel (aseel.jpl.nasa.gov [137.78.78.43]) by godzilla.jpl.nasa.gov (8.9.3p2.cm/8.9.3) with SMTP id KAA16362; Wed, 23 Apr 2003 10:49:31 -0700 (PDT) Message-ID: <004601c309c0$a6152400$2b4e4e89@jpl.nasa.gov> Reply-To: "Aseel Anabtawi" From: "Aseel Anabtawi" To: "Dick Simpson 723-3525" , , "Kerri Kusza 3-3669" Subject: 2003/110 at DSS-54 Date: Wed, 23 Apr 2003 10:49:11 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Length: 814 Status: O > Sal, > > Due to a failure in RCP5, the MGS tracking for DOY 110 was transferred to > DSS-65. > > Regards > Jes s No DR was written for this, and nothing is mentioned in the TMOD Daily Status Report about coverage being switched from DSS-54 to DSS-65! A few months ago, the MGS NOPE agreed to develop a procedure for Radio Science to be notified in case of a real-time MGS DSN coverage change, most likely by the Ops Chiefs (with the understanding that the Ops Chiefs will not be held responsible if, for some reason, RS was not contacted and data were lost). I provided the NOPE with my contact information, but it seems that the information was not passed on to the Ops Chiefs (they checked their list of contacts, and Radio Science is not on the list). Sal is now checking with the NOPE on why that is. -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Wed Apr 23 13:06:11 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 h3NK6Bk21809 for ; Wed, 23 Apr 2003 13:06:11 -0700 (PDT) Received: from aseel (aseel.jpl.nasa.gov [137.78.78.43]) by godzilla.jpl.nasa.gov (8.9.3p2.cm/8.9.3) with SMTP id NAA16862 for ; Wed, 23 Apr 2003 13:06:10 -0700 (PDT) Message-ID: <006b01c309d3$bd6554f0$2b4e4e89@jpl.nasa.gov> Reply-To: "Aseel Anabtawi" From: "Aseel Anabtawi" To: "Dick Simpson 723-3525" References: <200304231752.h3NHqPp16058@magellan.stanford.edu> Subject: Re: 2003/110 at DSS-54 Date: Wed, 23 Apr 2003 13:05:47 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Length: 848 Status: O > >Sal is now checking with the NOPE on why that is. > > This sounds like a DR from you against the NOPE. > If you don't want to do that, I can submit an ISA. > I think this needs more documentation than Sal > checking with the NOPE. I agree with you. However .... Sal got a hold of the NOPE, and he said that he never received the contact information from us. Sal says that he remembers sending it to him, but can't find it in his "sent email" mailbox anymore (this was back in January). Sal and I are making sure that the information gets to him now. I'm also going to talk to the Ops Chief Supervisor. If I write a DR against the NOPE, he's going to say that he never received the information. I can write a DR for lost data due to antenna changes, but then who's responsibility it is to inform us of coverage changes. -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Wed Apr 23 13:41:40 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 h3NKfdk22110 for ; Wed, 23 Apr 2003 13:41:39 -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 NAA16960 for ; Wed, 23 Apr 2003 13:41:39 -0700 (PDT) Message-Id: <200304232041.NAA16960@godzilla.jpl.nasa.gov> Date: Wed, 23 Apr 2003 13:41:39 -0700 (PDT) From: Aseel Anabtawi Reply-To: Aseel Anabtawi Subject: Re: 2003/110 at DSS-54 To: rsimpson@magellan.stanford.edu MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: pyEHm7j+D98e2VjFlRRjNw== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc Content-Length: 6258 Status: O > >Sal says that he remembers sending it to him, but can't > >find it in his "sent email" mailbox anymore (this was back in > >January). > > I thought we did this a couple years ago. Well, we started a couple of years ago, but then the NOPE retired. I didn't know, and I was sending emails to him without any response, until I was told last October that he has retired. That's when we started this again. > >Sal and I are making sure that the information gets > >to him now. I'm also going to talk to the Ops Chief Supervisor. > >If I write a DR against the NOPE, he's going to say that he never > >received the information. I can write a DR for lost data due to > >antenna changes, but then who's responsibility it is to inform us > >of coverage changes. > > If I submit an ISA AND you/Sal send a very comprehensive set > of instructions to the NOPE/Ops Chief Supervisor (and you > copy everyone in the world), is that sufficient? The NOPE is supposed to be the one to develop a procedure/ instructions (that was the Ops Chiefs' Supervisor request), but I did send an email explaining what we are asking for and why. ISAs do not go to the DSN (for example, the NOPEs); only DRs do. Just wanted to make sure you are aware of this. > In your set of instructions, you might as well cover all other > possible anomalies along these lines. I would be GENERAL rather > than try to list a lot of specific situations. If we don't do > it this way, we'll get caught in variation N next time, where > the NOPE will claim the instructions didn't cover the new > problem. > > Does this make sense? Sure does. Below is what I sent the NOPE back in October. I basically ask that Radio Science be contacted anytime there's a real-time change in DSN coverage. Please let me know if it's not general enough. ------------- Begin Forwarded Message ------------- Date: Mon, 21 Oct 2002 20:05:59 -0700 (PDT) From: Aseel Anabtawi Subject: Procedure to Contact RS To: ashort@jftl.jpl.nasa.gov Cc: akern@jftl.jpl.nasa.gov, Sami.W.Asmar@jpl.nasa.gov, SAbbate@jftl.jpl.nasa.gov Hello Al, I was told earlier today that Eugene Sax has retired, and you are the NOPE for MGS. I'm forwarding to you an email that I sent to Eugene about a week ago regarding notifying Radio Science of real- time MGS DSN coverage changes. In my email below, I suggest asking the Ops Chiefs for help since there is no continuous NOPE or ACE support. I had a talk with the NOCC Supervisor, Jerry Verlinde, this morning, and he expressed the following: - This would be an additional responsibility for the Ops Chiefs during a time when a lot would be going on. - The Ops Chiefs would be held responsible if RS was not contacted and data were lost. - Other teams/individuals may make similar requests and the Ops Chief would end up with a long list of people to contact. - How will the Ops Chief know if RS is impacted. I understand Jerry's concerns, but I'd like to point out that: - We would greatly appreciate the help of the Ops Chiefs, and we will not hold them responsible if a procedure is written but, for some reason, we are not contacted and data are lost. - ANY real-time change in DSN coverage (antenna changes) will impact RS. Changing a pass from 2-way to 1-way due to transmitter failure, for example, will not impact RS, but switching from one antenna to another will. - Our request to be contacted is to help save data. Based on the antenna switch information that we get, we can make real-time changes to our RSR scripts and predicts that would prevent data loss. By the way, more data were lost last Friday (DOY 291) because of a real-time switch from DSS-65 to DSS-63 that I was not aware of. Actually, all RS measurements over that pass were lost. If not the Ops Chiefs, who else can we ask for help? Your help in resolving this matter will be greatly appreciated. Please call me if you have questions or if you'd like to talk about this. Best Regards, Aseel Anabtawi ------------- Begin Forwarded Message ------------- Date: Sun, 13 Oct 2002 16:56:11 -0700 (PDT) From: Aseel Anabtawi Subject: Procedure to Contact RS To: Eugene.L.Sax@jpl.nasa.gov Cc: sami.asmar@jpl.nasa.gov Hello Eugene, As you know, MGS Radio Science measurements are scheduled about every two hours whenever DSN tracking passes are available. All of the data acquisition is done by scripts: Predicts and RSR scripts are generated for each pass before it starts (sometimes days before), and are then transmitted to the RSR where the script is set to execute at a certain time (normally at pre-cal). Some measurements are monitored in real-time, but other measurements, particularly weekend, late night or early morning ones, are unmonitored. The RSRs are very reliable, and we rarely lose any data due to RSR problems during an unmonitored measurement. Once in a while, however, Radio Science data are lost because of a real-time switch in support from one antenna to another that we are not aware of. The most recent example of this occurred last week on DOY 276 when MGS support was switched from DSS-25 to DSS-15 (DR G101659). The RSR was configured assuming DSS-25 was tracking, and three measurements were lost. Any real-time DSN coverage change will definitely impact Radio Science data collection. If we are not aware of antenna switches, we won't be able to make the necessary changes to the predicts and scripts, and data will be lost. This data loss can be easily prevented if the antenna switch information is passed on to Radio Science by simply calling or paging us. Since there isn't a continuous ACE or NOPE support for MGS, maybe the Ops Chief or Data Control can help. I've discussed this with a couple of Ops Chiefs, and they suggested that I talk to you, the NOPE, about developing a procedure for Radio Science to be contacted whenever a change in MGS DSN coverage occurs. Can you please help. Best Regards, Aseel ------------- End Forwarded Message ------------- --- Aseel Anabtawi MGS Radio Science Operations Engineer Radio Science Systems Group (818)393-1073 ------------- End Forwarded Message ------------- -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Wed Apr 23 15:13:36 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 h3NMDZk24000 for ; Wed, 23 Apr 2003 15:13:35 -0700 (PDT) Received: from aseel (aseel.jpl.nasa.gov [137.78.78.43]) by godzilla.jpl.nasa.gov (8.9.3p2.cm/8.9.3) with SMTP id PAA17322 for ; Wed, 23 Apr 2003 15:13:35 -0700 (PDT) Message-ID: <001501c309e5$89eac0d0$2b4e4e89@jpl.nasa.gov> Reply-To: "Aseel Anabtawi" From: "Aseel Anabtawi" To: "Dick Simpson 723-3525" References: <200304232059.h3NKxfB22211@magellan.stanford.edu> Subject: Re: 2003/110 at DSS-54 Date: Wed, 23 Apr 2003 15:13:16 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Length: 27 Status: O > ISA Z80354 Thank you. -------------------------------------------------------------------------- From aseel@godzilla.jpl.nasa.gov Wed Apr 23 15:33:17 2003 From: "Aseel Anabtawi" To: "Dick Simpson 723-3525" , , "Kerri Kusza 3-3669" Subject: More on DOY 110, DSS-54 Date: Wed, 23 Apr 2003 15:32:57 -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_003D_01C309AD.9D733070 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The Ops Chief clarified what happened on DOY 110: DSS-66 was red (not DSS-54), so support was switched so that DSS-54=20 took over DSS-66 support, and DSS-65 took over DSS-54 support (MGS=20 and Odyssey). As I've mentioned, the changes were not noted in the Daily Status = Report,=20 but the Ops Chief said that they were noted in other reports. No data, = other=20 than Radio Science data, were lost, so no DR was issued. The Ops Chief=20 commented that nothing in their procedure tells them to notify Radio = Science,=20 and he actually remembered me and him having a similar conversation = before. -------------------------------------------------------------------------- From jtwicken@stanford.edu Tue Apr 29 20:50:02 2003 Received: from nova.Stanford.EDU (IDENT:OpioLP9kSyf2V6ImXTMyUuJP7hdSml+Q@nova [171.64.90.123]) by magellan.stanford.edu (8.11.6/8.11.6) with ESMTP id h3U3o1d29347 for ; Tue, 29 Apr 2003 20:50:01 -0700 (PDT) Received: from neptune.Stanford.EDU (neptune.Stanford.EDU [171.64.90.149]) by nova.Stanford.EDU (8.12.8/8.12.8) with ESMTP id h3U3o8b7027614; Tue, 29 Apr 2003 20:50:08 -0700 Received: from neptune.Stanford.EDU (joe@localhost) by neptune.Stanford.EDU (8.11.6/8.11.6) with ESMTP id h3U3o6A07927; Tue, 29 Apr 2003 20:50:06 -0700 (PDT) Message-Id: <200304300350.h3U3o6A07927@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: hinson@nova.stanford.edu, joe@nova.stanford.edu, rsimpson@nova.stanford.edu Subject: Re: RSR Notice: /users/z08/procRSR/31191622 In-reply-to: Your message of "Tue, 29 Apr 2003 09:36:22 PDT." <200304291636.h3TGaMc19589@magellan.stanford.edu> References: <200304291636.h3TGaMc19589@magellan.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Apr 2003 20:50:06 -0700 Content-Length: 905 Status: RO (1) There was no HGA motion compensation for these recordings >31100005.RSR p 34XR1IRXN101 34XR1IC1XX01 34XR1IF1S101 34XR1IS1T101 34XR1IS1T201 34XR1IS1T301 34XR1IS1T401 34XR1IS1T501 >31100203.RSR p 34XR1IRXN101 34XR1IC1XX01 34XR1IF1S101 34XR1IS1T101 34XR1IS1T201 34XR1IS1T301 34XR1IS1T401 34XR1IS1T501 >3110095D.RSR p 25XR1IRXN101 25XR1IC1XX01 25XR1IF1S101 25XR1IS1T101 25XR1IS1T201 25XR1IS1T301 25XR1IS1T401 25XR1IS1T501 >31101151.RSR p 25XR1IRXN101 25XR1IC1XX01 25XR1IF1S101 25XR1IS1T101 25XR1IS1T201 25XR1IS1T301 25XR1IS1T401 25XR1IS1T501 >31101349.RSR p 25XR1IRXN101 25XR1IC1XX01 25XR1IF1S101 25XR1IS1T101 25XR1IS1T201 25XR1IS1T301 25XR1IS1T401 25XR1IS1T501 >31101546.RSR p 25XR1IRXN101 25XR1IC1XX01 25XR1IF1S101 25XR1IS1T101 25XR1IS1T201 25XR1IS1T301 25XR1IS1T401 25XR1IS1T501 >31101744.RSR p 25XR1IRXN101 25XR1IC1XX01 25XR1IF1S101 25XR1IS1T101 25XR1IS1T201 25XR1IS1T301 25XR1IS1T401 25XR1IS1T501