X-Sympa-To: ids.analysis.forum
Received: from hector.cls.fr (osis.cls.fr [62.161.32.21])
	by hermes.cls.fr (8.9.3/8.9.3) with ESMTP id NAA22357
	for <ids.analysis.forum@hermes.cls.fr>; Fri, 24 Mar 2006 13:00:02 +0100
Received: by hector.cls.fr (Postfix)
	id B1EABEEACA; Fri, 24 Mar 2006 11:01:54 +0000 (GMT)
Delivered-To: ids.analysis.forum@cls.fr
Received: from CLS-SOUDARIN.cls.fr (orange-102.cls.fr [62.161.32.13])
	by hector.cls.fr (Postfix) with ESMTP id 5A6AE20ABA
	for <ids.analysis.forum@cls.fr>; Fri, 24 Mar 2006 11:01:54 +0000 (GMT)
Message-Id: <6.1.1.1.2.20060323113309.020f6b78@pop.cls.fr>
X-Sender: lsoudarin@pop.cls.fr
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Thu, 23 Mar 2006 11:33:19 +0100
To: ids.analysis.forum@cls.fr
From: "Erricos C. Pavlis" <epavlis@umbc.edu>(au lieu de Laurent Soudarin <laurent.soudarin@cls.fr>)
Subject: Re: estimating DORIS pole motion rates? 1-week preliminary
  results
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Validation-by: laurent.soudarin@cls.fr

Frank,

The ILRS AWG tackled this issue more than two years ago and after
some deliberations, tests, and comparisons, we came to the conclusion
that Daniel is now finding out about DORIS and GPS rates. Without
taking the time to go too deep in the reasons why satellite
techniques do not get the rates correctly, I can assure you that you
will destroy your polar motion estimates if you allow the
simultaneous estimation of rates. This is different for LOD, where we
DO estimate LOD (the rate of UT1), rather than UT1 itself (which is
confounded with the errors in our definition of the node). Make sure
that when you estimate LOD, you do let UT1 loose, because if you do
not allow for that, Geodyn will use it as is in the tables, i.e. fix
it, thereby delivering LOD which is indistinguishable from that of
the tables!

ecp


On Mar 3, 2006, at 8:05 PM, Frank Lemoine wrote:

>Erricos and Ron
>  Did the ILRS come to any conclusion about the estimation of pole
>rates?
>  Is this done as a matter of routine?
>Frank-
>
>------ Forwarded Message
>From: "Daniel Gambis" <daniel.gambis@obspm.fr>
>Date: Fri, 17 Feb 2006 12:25:52 +0100
>To: "Pascal Willis" <Pascal.R.Willis@jpl.nasa.gov>, "Laurent
>Soudarin" <Laurent.Soudarin@cls.fr>, "Frank Lemoine"
><flemoine@bowie.gsfc.nasa.gov>
>Cc: "Daniel Gambis" <gambis@hpopa.obspm.fr>, "Richard Gross"
><rsg@mail.jpl.nasa.gov>, "Zuheir Altamimi" <altamimi@ensg.ign.fr>,
>"Gilles Tavernier" <Gilles.Tavernier@cnes.fr>, "Jean-Jacques
>Valette" <valette@cls.fr>, "Jayles Christian"
><Christian.Jayles@cnes.fr>, "Ron Noomen"
><Ron.Noomen@lr.tudelft.nl>, "Markus Rothacher" <rothache@gfz- potsdam.de>
>Subject: RE: estimating DORIS pole motion rates? 1-week preliminary
>results
>
>Dear colleagues
>
>The discussions we had last year within the GPS community showed
>that pole rates
>were not useful to improve EOPs. According to the analyses I made,
>for interpolation
>it is better to use a linear fit than using estimated pole rates.
>The situation is as you imagin
>not better with DORIS than with GPS.
>I attach thereafter 2 plots showing polar rates. You can see that
>DORIS pole rates are very noisy.
>In DORIS data processing, there is probably a significant
>correlation between estimates of pole
>and pole rates. I thus guess that estimating pole rates leads to a
>degradation of the pole components
>derived and I would recommend NOT to estimate anymore pole rates.
>
>Regards
>
>Daniel
>
>
>
>------ End of Forwarded Message
><pdorisx.ps>
><pdorisy.ps>


   +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
   Dr. Erricos C. Pavlis                       Phone:    +1 (410)
455-5832
   Research Associate Professor         FAX:    +1 (410) 455-5868

   Joint Center for Earth Systems Technology, (JCET/UMBC)
   University of Maryland Baltimore County & NASA Goddard
   Academic IV  Wing A  Suite 114E
   1000 Hilltop Circle
   Baltimore, Maryland
   U S A    21250           epavlis@umbc.edu

   +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++





