New horizons status
This presentation is the property of its rightful owner.
Sponsored Links
1 / 8

New Horizons Status PowerPoint PPT Presentation


  • 47 Views
  • Uploaded on
  • Presentation posted in: General

New Horizons Status. A’Hearn & Kolokolova. Mission Overview. New Horizons launched 19 Jan 2006 En route to Pluto with Jovian gravity assist Closest approach to Jupiter 28 Feb 2007 Speed 21 km/s Closest approach 32 R J (3x closer than Cassini) Pluto flyby July 2015. Payload.

Download Presentation

New Horizons Status

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


New horizons status

New Horizons Status

A’Hearn & Kolokolova


Mission overview

Mission Overview

  • New Horizons launched 19 Jan 2006

  • En route to Pluto with Jovian gravity assist

  • Closest approach to Jupiter 28 Feb 2007

    • Speed 21 km/s

    • Closest approach 32 RJ (3x closer than Cassini)

  • Pluto flyby July 2015

Management Council


Payload

Payload

  • ALICE - uv spectrograph

  • RALPH - optical/IR

    • LEISSA - Linear etalon spectrometer (IR)

    • MVIC - multispectral visible camera

  • REX - radio wave occultations

  • LORRI - long-range imager

  • SWAP - solar wind analyzer

  • PEPSSI - energetic particle spectrometer

  • SDU - dust counter (student built)

Management Council


Archiving status

Archiving Status

  • DMAP signed

  • ICD - implicit in DMAP

  • SIS -

    • Preliminary version reviewed for each instrument

    • Final version not yet available (but preliminary versions were prettty good)

  • Data

    • No sample data available yet

    • No calibration data available yet

  • Pipeline

    • All data to be processed at SOC (at SwRI Boulder)

    • Peer review of pipeline discussed several times over last year but never held

Management Council


Recent developments

Recent Developments

  • Jim Green announced that there will be a JDAP for New Horizons using FY07 money

  • SBN held discussions with New Horizons regarding “typical” requirements for data delivery to PDS for DAP eligibility

  • Kolokolova and Raugh attended SOC + Science Team meeting in November

  • New Horizons team still neither willing to schedule a pipeline peer review nor willing to provide sample data

Management Council


Current plan for jovian data

Current Plan for Jovian Data

  • Data taken and downlinked January 2007 to July 2007

  • April delivery of data through closest approach - both raw and calibrated (a change from plan as of two months ago)

  • All Jovian data will be delivered in August-September, including re-calibration of early data

  • Noting the huge improvement in their plan, we presume NASA told them they had to deliver in order to get DAP funds

Management Council


Data format volume

Data - Format & Volume

  • ALL data will be in PDS-labelled FITS format

    • This partly a result of A’Hearn’s attendance at an early science team meeting to urge uniformity across instruments - advantages recognized instantly by science team

  • Estimated volume at Jupiter

    • ALICE - 5 Gbits, images

    • LEISSA - 18 Gbits, cubes

    • LORRI - 12 Gbits, images

    • MVIC - 1 Gbit, images

    • PEPSSI - 10 Gbit, table

    • REX - 26 Mbits, table

    • SWAP - 900 Mbits, table

    • SDC - ??

Management Council


Pds roles

PDS Roles

  • Until now, all interaction with SOC has been by SBN

    • Minimizes need for SOC to deal with node-to-node vagaries

  • ATM interested because data at Jupiter are mostly atmospheric

  • PPI interested in SWAP and PEPSSI

  • Radio Science interested in REX

  • Original plan was to involve other nodes at time of pipeline review - with decision not to have a review, what should be role of other nodes? Don’t want SOC to have to deal with multiple nodes (cf ESA PSA position)

Management Council


  • Login