Received: from cluster-jaune.cls.fr (cl1-jaune.cls.fr [91.207.20.90])
	by sympa-ext.cls.fr (8.13.1/8.13.1) with ESMTP id o9CJR4lr008563
	for <ids.analysis.forum@sympa-ext.cls.fr>; Tue, 12 Oct 2010 19:27:04 GMT
Received: by cluster-jaune.cls.fr (Postfix)
	id 301892EAF3; Tue, 12 Oct 2010 19:27:04 +0000 (GMT)
Delivered-To: ids.analysis.forum@ids-doris.org
Received: from cluster-d.mailcontrol.com (cluster-d.mailcontrol.com [85.115.60.190])
	by cluster-jaune.cls.fr (Postfix) with ESMTP id 180402EAAD
	for <ids.analysis.forum@ids-doris.org>; Tue, 12 Oct 2010 19:27:04 +0000 (GMT)
Received: from ndjsnpf01.ndc.nasa.gov (ndjsnpf01.ndc.nasa.gov [198.117.1.121])
	by rly53d.srv.mailcontrol.com (MailControl) with ESMTP id o9CJQxGH005367
	for <ids.analysis.forum@ids-doris.org>; Tue, 12 Oct 2010 20:27:01 +0100
Received: from ndmsppt04.ndc.nasa.gov (ndmsppt04.ndc.nasa.gov [198.117.0.103])
	by ndjsnpf01.ndc.nasa.gov (Postfix) with ESMTP id 7953F328D02
	for <ids.analysis.forum@ids-doris.org>; Tue, 12 Oct 2010 14:26:57 -0500 (CDT)
Received: from ndmshub01.ndc.nasa.gov (ndmshub01-pub.ndc.nasa.gov [198.117.0.160])
	by ndmsppt04.ndc.nasa.gov (8.14.3/8.14.3) with ESMTP id o9CJQvqa031412
	for <ids.analysis.forum@ids-doris.org>; Tue, 12 Oct 2010 14:26:57 -0500
Received: from wcne-128-154-203-98.gsfc.nasa.gov (128.154.203.98) by
 smtp02.ndc.nasa.gov (198.117.0.160) with Microsoft SMTP Server (TLS) id
 8.3.106.1; Tue, 12 Oct 2010 14:26:56 -0500
Message-ID: <4CB4B67B.9080306@nasa.gov>
Date: Tue, 12 Oct 2010 15:26:51 -0400
From: Frank Lemoine <Frank.G.Lemoine@nasa.gov>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: <ids.analysis.forum@ids-doris.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000
 definitions=2010-10-12_11:2010-10-12,2010-10-12,1970-01-01 signatures=0
X-Mailcontrol-Inbound: UaGaIYaeJ2noGC3+4HOWm2hmz2zQyNKrNKaQ3LZxmP91GmsDC50eqQ==
X-Spam-Score: -0.364
X-Scanned-By: MailControl A_09_40_00 (www.mailcontrol.com) on 10.68.0.163
X-Validation-by: lsoudarin@cls.fr
Subject: [ids.analysis.forum] Jason-1 EOL Discussion Continued & Future
 Orbits Beyond Jason-3 for Jason-CS

Dear IDS Analysis Forum:

I forward below the comments from Luca Cerri (CNES)
regarding the Jason-1 End of Life proposals, and the new
orbits being proposed for the Jason-CS missions.

These topics will be discussed at the OSTST (Ocean surface
topography Science Team) meeting in Lisbon next week, October
18-22, 2010.

Those attending the meeting should be prepared to provide their
thoughts or comments on these issues (Apologies for the duplication
of posts for those who have seen this message more than once).

Best regards,
Frank Lemoine
NASA GSFC
================================================================
================================================================



Dear all,

As most of you already know, we have been asked to give our advice as
Jason POD team on  

1) a possible change of orbit for Jason-1, and a possible change of
orbit for 
the upcoming Jason-CS mission. (see attached slides in the zip folder)
2) how to maintain a 1 mm/yr drift accuracy for the Jason series,
particularly in 
preparation for Jason-3. 

 We will do our best to find the time at the end of the POD splinter in
Lisbon to 
discuss these issues and either I or Frank will present a 1 or 2 slides
summary of the 
discussion. 

Concerning issue number 1 , especially for Jason-CS, the main point in
my opinion is that
a drastic change in the orbit geometry will make the solution react
differently to errors 
in dynamical models (some examples follow below). In particular, this
would have an impact
in the calval analysis between Jason-3 (classic T/P orbit) and Jason-CS
(new orbit), 
at the 1-cm level. For example, some inconsistencies are reported now
when comparing Jason 
with Envisat data, even if orbit solutions for both missions share
common models and 
processing strategies.

Concerning issue number 2 , the POD contribution to the drift error
budget can be reduced 
by regularly reprocessing the entire series of orbits with the best
available standards.
In the near future that means updating GDR-C orbits with ITRF2008 and
the latest generation 
of GRACE-derived time varying gravity field (special care should be
taken in handling drifts 
from these tvg models). 
In order to reprocess jason orbits in ITRF2008, we will need a
consistent GPS constellation 
solution throughout the entire Jason-1 and Jason-2 lifetime. 
Willy, can JPL provide this as it was done when we switched to ITRF2005?


Thank you in advance for your comments and inputs!

Best regards

Luca

========================================================================
===============

Some comments on ISSUE NR 1 
- Moving Jason-1 to a long-repeat geodetic orbit (1288 km altitude ?
TBC) 
- Moving Jason-CS to a completely different orbit , the candidate orbit
shortlist
  would is (A=altitude, i=inclination, c=repeat cycle)
  A878_i66_c10, A926_i67_c13, A801_i71_c22 (from CLS study) 
  A640_i78_c20, A820_i78_c20, A942_i78_c20 (from UHH study) 

- Decreasing Jason-1 altitude of about 50 km should not have a large
impact on POD.
We should check however if the change in ground-track and the
long-repeat nature 
of the new orbit will require an update to SAA model

Few examples of causes of incosistencies between Jason-3 and the
follow-n Jason-CS

- Lowering the orbit while keeping similar inclination will decrease the
beta angle period.
Radial errors induced by SRP model deficiencies will not have identical
patterns between 
Jason-3 and the following Jason-CS mission

- different platform and different attitude regime might also completely
change 
the surface forces scenario that we are used to with the Jason series. 

- Depending on the satellite configuration, lower orbit means higher
drag and we might be 
at a new solar max by Jason-CS launch (2017 or so)

- Lower altitude means higher sensitity to errors in the time-varying
gravity field.
Different inclination might change the typical order-one pattern that we
have on jason.

- We might argue that with an "agressive" reduced dynamic approach we
would be able to 
compensate most of these errors on both Jason-3 and Jason-CS. But for
this we would need 
full GPS capability (no SAA loss) on both satellites and probably
ambiguity fixing processing 
schemes. Will both GPS receiver be adapted for such a challenge? 







                           Cliquez sur l'url suivante 
https://www.mailcontrol.com/sr/drKA4AnfCePTndxI!oX7UguoYhQx!y1a!lYgmTJb3Xf1Qw47ofnOTaDVwk5H73vtvvmRGwCfDItd8GUOJKJHvw==  
                    si ce message est indésirable (pourriel).
