Received: from cluster-jaune.cls.fr (cl1-jaune.cls.fr [91.207.20.90])
	by sympa.cls.fr (8.13.1/8.13.1) with ESMTP id o2634ZUV026006
	for <ids.analysis.forum@sympa.cls.fr>; Sat, 6 Mar 2010 03:04:35 GMT
Received: by cluster-jaune.cls.fr (Postfix)
	id 02376383E9; Sat,  6 Mar 2010 03:04:35 +0000 (GMT)
Delivered-To: ids.analysis.forum@cls.fr
Received: from cluster-d.mailcontrol.com (cluster-d.mailcontrol.com [85.115.60.190])
	by cluster-jaune.cls.fr (Postfix) with ESMTP id CFF8C385D9
	for <ids.analysis.forum@cls.fr>; Sat,  6 Mar 2010 03:04:33 +0000 (GMT)
Received: from sol.csr.utexas.edu (sol.csr.utexas.edu [129.116.190.1])
	by rly22d.srv.mailcontrol.com (MailControl) with ESMTP id o2634Tdq010465
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ids.analysis.forum@cls.fr>; Sat, 6 Mar 2010 03:04:31 GMT
Received: from localhost (sol.csr.utexas.edu [127.0.0.1])
	by sol.csr.utexas.edu (8.13.8/8.13.8) with ESMTP id o2634R9D012399;
	Fri, 5 Mar 2010 21:04:27 -0600
X-Virus-Scanned: amavisd-new at csr.utexas.edu
Received: from sol.csr.utexas.edu ([127.0.0.1])
	by localhost (sol.csr.utexas.edu [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id bM0YP4WYvXtB; Fri,  5 Mar 2010 21:04:23 -0600 (CST)
Received: from [192.168.0.4] (adsl-71-145-174-196.dsl.austtx.sbcglobal.net [71.145.174.196])
	(authenticated bits=0)
	by sol.csr.utexas.edu (8.13.8/8.13.8) with ESMTP id o2634Gwm012389
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 5 Mar 2010 21:04:16 -0600
Mime-Version: 1.0
Message-Id: <p06230902c7b7697685a3@[192.168.0.4]>
In-Reply-To: <51B876A1-4232-48A5-A7DD-CC96335C1E67@altimetrics.com>
References: 
 <FE24BB1AB6D3104BB08E5A321038B3DF9FA89A8329@MAILBOX.sgt-dom.com>
 <p06230900c7b61e01d638@[192.168.0.4]> 
 <FE24BB1AB6D3104BB08E5A321038B3DF9FA8A25A1D@MAILBOX.sgt-dom.com>
 <51B876A1-4232-48A5-A7DD-CC96335C1E67@altimetrics.com>
Date: Fri, 5 Mar 2010 21:04:17 -0600
To: Remko Scharroo <remko@altimetrics.com>, Steve Klosko <sklosko@sgt-inc.com>
From: "John C. Ries" <ries@csr.utexas.edu>
Cc: "jean-paul.berthias@cnes.fr" <jean-paul.berthias@cnes.fr>,
        Cerri Luca <luca.cerri@cnes.fr>,
        Eelco Doornbos <e.n.doornbos@tudelft.nl>,
        Marek Ziebart <marek.ziebart@ge.ucl.ac.uk>,
        Frank Lemoine <Frank.G.Lemoine@nasa.gov>,
        Scott Luthcke <scott.b.luthcke@nasa.gov>,
        Michiel Otten <michiel.otten@esa.int>,
        Eric Leuliette <Eric.Leuliette@noaa.gov>,
        "Mercier Flavien (contact)" <flavien.mercier@cnes.fr>,
        "ids.analysis.forum@cls.fr" <ids.analysis.forum@cls.fr>,
        Nikita Zelensky <nzelensky@sgt-inc.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Mailcontrol-Inbound: c!PzNVdyE6pAgYrdZN4HGLIOLgW8bYa616COtuSiUsY=
X-Spam-Score: 2.3
X-Scanned-By: MailControl A-09-22-10 (www.mailcontrol.com) on 10.68.0.132
X-Validation-by: lsoudarin@cls.fr
Subject: [ids.analysis.forum] Re: surface forces

Hi Remko,
>
>
>You are absolutely right that a radial offset of the CoM is hardly 
>"tamed" by the tracking data. I haven't done the exercise lately, 
>but I do remember checking this out in the ERS-1/2 era when I was 
>doing both short-arc (one rev or less) and long-arc (5.5 days) 
>solutions.
>
>In the long-arc solutions I could move the CoM up or down several 
>centimeters without affecting the orbit even as little as a 
>millimeter. Yes, the tracking residuals worsened, but the orbit 
>stayed basically in place.
>
>So in the framework of TOPEX and a "wobbling" solar panel, the 
>dynamic orbit determination will still position the CoM in the right 
>place, only the tracking data residuals would be slightly impacted. 
>To get the right sea level, we would need to make a geometric 
>correction to the altimeter range because the vertical distance 
>between the antenna feed and the CoM changes over time.

I agree that a constant bias in the CoM cannot be accommodated with 
the parameters we usually adjust, and so it is left in the residuals. 
For this reason, we can estimate the vertical antenna phase offset, 
for example. But if we were to estimate a CONSTANT radial 
acceleration, it would easily go into that parameter and bias the 
orbit. This is exactly what happened with the early JPL orbits for 
T/P, until they switched the reduced-dynamics to use 1/revs.

In the same way, a variable CoM, oscillating at the orbital period 
(as the solar arrays do) can go into the orbit since the 1/revs will 
accommodate that signal. Thus there is at least the potential for T/P 
to have been affected by the solar array warp. But given that we 
don't know the initial deployment angle error, we don't have precise 
models for the warping effect from heating (or the temperatures) 
without ground tests, and there are multiple hinges in the array that 
add to the uncertainty, we really have no hope of forward modelling 
this. Hence it hasn't been considered very much.

We did do a test in 1998 where Dochul Yang looked for a correlation 
in the crossovers for the first 50 cycles of T/P with the solar array 
warp (based on Kubitschek's dissertation), and we saw nothing 
convincing. (and he did check that the effect wasn't just cancelling).
>
>
>Let me remind everybody, that TOPEX seems NOT the issue in this 
>whole story. TOPEX does not seem to exhibit the 58-day cycle in sea 
>level, whereas Jason-1 and Jason-2 DO. One of the images in Eric 
>Leuliette's presentation, comparing Jason-2 to Envisat clearly shows 
>the S2 aliased variation, whereas we know Envisat cannot have an S2 
>alias (or rather, it is aliased to a constant).

This is the interesting part. I would ask for two clarifications

1) Is the 58-day cycle not seen because T/P is noisier or is the 
series from T/P good enough that we are sure that signal isn't there? 
i.e., is the determination of a lack of a 58-day cycle a clear and 
confident one? It's very important to this discussion to be sure 
about this. Is there evidence of a periodicity at twice that in any 
of the series?

2) Are the peaks associated with high beta prime or low? In the Jason 
POD paper that's about to be published, it was shown that the RMS 
differences were significantly larger during high beta prime, and the 
Z shifts were maximized where the cross-track differences were 
maximum, which was also at high beta prime. I saw the same thing in 
my tests.

The second item puzzles me more than a little. The geometry is right 
for SRP maximizing the cross-track effect at high beta-prime, but I 
have to wonder why the cross-track 1/revs don't 'whiten' the 
cross-track differences. It seems to me that the cross-track 1/revs 
ought to be trying to accommodate the cross-track orbit error, and 
they should succeed in an average sense, with some level of scatter 
about that. Yet the comparison in the POD paper, and indeed in my own 
test, the Z-shift is almost a pure scaling of the beta-prime angle. 
But as this is a purely 120-day signal, it is not necessarily 
relevant to the problem at hand.

So I come back to two scenarios.

1) T/P, with some sort of 58-day orbital error, has biased the S2 
tide to remove it from the T/P orbit. Now S2 shows up in Jason-1 and 
2. We can't test S2 with the sun-synchronous satellites. And S2 is 
hard to test with GRACE as it is also long-period there. This all 
depends on how much T/P has influenced the tide models being used. If 
the tide models used a lot of Jason-1 data, then this scenario 
becomes implausible.

2) Something besides SRP is affecting the Jason-type spacecraft, 
where a 1/rev variation along-track (or radial, or both) is occurring 
that is modulated by two-beta prime (for example, something that 
would one-beta-prime but where the yaw flip has created a symmetry 
that makes it two-beta-prime). If this is really occurring just in 
high beta-prime, then it is quite puzzling since this would seem to 
be the most steady temperature regime, and where the solar panels are 
articulating the least.

Best regards,
JR
