motivation for developing spice n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Motivation for Developing SPICE PowerPoint Presentation
Download Presentation
Motivation for Developing SPICE

Loading in 2 Seconds...

play fullscreen
1 / 7

Motivation for Developing SPICE - PowerPoint PPT Presentation


  • 92 Views
  • Uploaded on

Motivation for Developing SPICE. July 2013. Why Did NAIF Build SPICE?. Scientists said they would like to: use common tools and methods throughout a project’s lifecycle, and for all projects (national and international)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Motivation for Developing SPICE' - whitney


Download Now 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
why did naif build spice
Why Did NAIF Build SPICE?
  • Scientists said they would like to:
    • use common tools and methods throughout a project’s lifecycle, and for all projects (national and international)
    • understand the calculations and transformations used to produce observation geometry data
    • be able to produce custom geometry calculations themselves, whenever and however they want
    • have the ability to revise the fundamental data and software tools used to produce their own observation geometry data

Motivation for SPICE

what existed prior to spice

SEDR

Generation

EDR

EDR

What Existed Prior to SPICE ?

“SEDR” - Supplemental Experiment Data Record

Scientist’s Institution

JPL

Trajectory

Data

Scientist’s Data

Analysis Program

S/C

Orientation

Data

SEDR

SEDR

Scientist’s

Software

Modules

Science

Results

SEDR

Parameters

Database

SEDR

Commands

Science

Instrument

Data

EDR*

Generation

Science

Telemetry

* EDR = Experiment Data Record = "raw" science instrument data

Motivation for SPICE

sedr system characteristics
SEDR System Characteristics
  • The SEDR Generation program was built and operated at JPL
    • Scientist’s requirements on SEDR had to be provided long before launch
      • Late or post-launch updates were hard/expensive to accommodate
        • Difficult to change WHAT gets computed
        • Difficult to change HOW items are computed (algorithms, parameters)
        • Difficult to change the TIMEs at which items get computed
    • Generally only one SEDR file would be produced for each period of time
      • Result: the scientist can’t get better ancillary data if/when better inputs (e.g. spacecraft trajectory or orientation) are determined
    • SEDR generation was done “in the blind”
      • Operators were not familiar with processes used to make the inputs
      • Operators were not familiar with scientist’s processing schemes
      • Result: SEDR may not fully meet science team’s expectations
    • The SEDR system was not exportable to other institutions

Motivation for SPICE

the spice idea
The SPICE Idea

Any Mission

Operations Center

Scientist’s Institution

Scientist’s Data

Analysis Program

SPICE

Kernels

Generation

And

Collection

Selected

SPICE

Modules

Scientist’s

Software

Modules

Wonderful Science

Results

Science Telemetry

Motivation for SPICE

spice benefits vs sedr
SPICE Benefits vs. SEDR
  • The customer has great flexibility in deciding:
    • what observation geometry parameters are computed
    • at what times or at what frequency these parameters are computed
    • for what time span these parameters are computed
    • electing if/when to re-do parameter computations using new (better) or otherwise different data as inputs
  • The customer also has:
    • common tools and methods that can be reused on many tasks
    • good visibility into algorithms and data used in geometry calculations
  • The flight project operations center can:
    • concentrate on producing better ancillary data, rather than on producing lots of SEDRs and frequently updating the SEDR software
  • The SPICE process may be replicated anywhere

Motivation for SPICE

spice detriments vs sedr
SPICE Detriments vs. SEDR
  • End users ("consumers") must do some non-trivial programming to read SPICE data and compute whatever is needed
  • If the mission operations center is other than JPL, the appropriate project people need to learn how to produce SPICE data
  • In some areas of SPICE the offering of choices to allow correct handling of different situations may present complexity that is unwarranted for “simple” problems

Motivation for SPICE