Search NASA⌕ Search

NASA NTRS · 20130001787

Autonomous Navigation Performance During The Hartley 2 Comet Flyby

Abstract

On November 4, 2010, the EPOXI spacecraft performed a 700-km flyby of the comet Hartley 2 as follow-on to the successful 2005 Deep Impact prime mission. EPOXI, an extended mission for the Deep Impact Flyby spacecraft, returned a wealth of visual and infrared data from Hartley 2, marking the fifth time that high-resolution images of a cometary nucleus have been captured by a spacecraft. The highest resolution science return, captured at closest approach to the comet nucleus, was enabled by use of an onboard autonomous navigation system called AutoNav. AutoNav estimates the comet-relative spacecraft trajectory using optical measurements from the Medium Resolution Imager (MRI) and provides this relative position information to the Attitude Determination and Control System (ADCS) for maintaining instrument pointing on the comet. For the EPOXI mission, AutoNav was tasked to enable continuous tracking of a smaller, more active Hartley 2, as compared to Tempel 1, through the full encounter while traveling at a higher velocity. To meet the mission goal of capturing the comet in all MRI science images, position knowledge accuracies of +/- 3.5 km (3-?) cross track and +/- 0.3 seconds (3-?) time of flight were required. A flight-code-in-the-loop Monte Carlo simulation assessed AutoNav's statistical performance under the Hartley 2 flyby dynamics and determined optimal configuration. The AutoNav performance at Hartley 2 was successful, capturing the comet in all of the MRI images. The maximum residual between observed and predicted comet locations was 20 MRI pixels, primarily influenced by the center of brightness offset from the center of mass in the observations and attitude knowledge errors. This paper discusses the Monte Carlo-based analysis that led to the final AutoNav configuration and a comparison of the predicted performance with the flyby performance.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Abrahamson, Matthew J, Kennedy, Brian A., Bhaskaran, Shyam. 2012-06-14. Autonomous Navigation Performance During The Hartley 2 Comet Flyby. https://ntrs.nasa.gov/citations/20130001787

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related reports

Navigating Stardust-NEXT: The Road to Tempel 1

The Stardust-NExT (New Exploration of Tempel) mission, a follow-on to the Stardust prime mission, successfully completed a flyby of comet Tempel-1 on 2/14/11. However there were many challenges along the way in navigating this mission to its successful conclusion, most significantly low propellant margin and detection of the comet in imagery later than anticipated. These challenges and their ramifications forced the navigation team and the project to respond with flexibility and ingenuity. As a result, the resulting flyby at an altitude of 178 km was nearly flawless, accomplishing all its science objectives.

flyby↗

Deep Impact : the mission and results

The Deep Impact project completed its mission on July 4, 2005 with a spectacularly successful encounter with the comet Tempel 1, culminating a four-year development effort and a six-month cruise period. The project's primary purpose was to conduct what can be considered a simple experiment that occurs in space on a very frequent basis: to impact a cometary nucleus with a man made meteor and excavate a crater to reveal the interior of a nucleus.

flyby↗

Design of High-Accuracy Multiple Flyby Trajectories Using Constrained Optimization

The trajectory optimization technique described in this paper provides several distinct advantages over previous formulations. First, fully numerically integrated trajectory modeling is used. That is, no approximations to the trajectory are made and the inclusion of any level of complicated force models desired is allowed. Second, only trajectory propagation is used so there is no requirement for optimization. This is accomplished by the novel method of splitting the trajectory into independent legs, which are then subjected to constrained optimization. Third, each of the trajectory legs may be specified by any convenient set of parameters particularly useful for that leg. Any of these parameters may then be subject to constraints. Fourth, the nonlinear optimization problem is solved by solving a sequence of linear problems which converges to the optimal nonlinear solution. Fifth, the robustness of this formulation requires little or no user interaction with the optimization once a feasible problem has been posed.

flyby↗