SOC simulation use cases Roland Vavrek (ESA) OU-SIM Meeting, - - PowerPoint PPT Presentation

soc simulation use cases
SMART_READER_LITE
LIVE PREVIEW

SOC simulation use cases Roland Vavrek (ESA) OU-SIM Meeting, - - PowerPoint PPT Presentation

SOC simulation use cases Roland Vavrek (ESA) OU-SIM Meeting, Marseille, CPPM 13/01/2016 ESA UNCLASSIFIED For Official Use Scope Top-level simulation use-cases required to support performance monitoring and development of SOC components :


slide-1
SLIDE 1

ESA UNCLASSIFIED – For Official Use

SOC simulation use cases

Roland Vavrek (ESA) OU-SIM Meeting, Marseille, CPPM 13/01/2016

slide-2
SLIDE 2

SOC simulations use cases | Roland Vavrek | ESAC| 13/01/2016 | Slide 2 ESA UNCLASSIFIED – For Official Use

Scope

Ø Top-level simulation use-cases required to support performance monitoring and development of SOC components:

  • Simulation use cases typically required for system level

performance monitoring; for SOC components development, testing and verification (QLA and Archive); and for supporting the SSO SWG simulation needs (position transients) Ø OU-SIM/SOC collaboration on usability of OU-SIM infrastructure for SOC use cases

  • Installation, updates, MDB and parameterization, add-on

modules, alternative DP algorithms, alternative instrument model, debugging, database, feedback etc.

slide-3
SLIDE 3

SOC simulations use cases | Roland Vavrek | ESAC| 13/01/2016 | Slide 3 ESA UNCLASSIFIED – For Official Use

Top level SOC simulation use cases - 1

Ø System level performance analysis and monitoring for verification of MRD level requirements following the compliance verification approach outlined in the Mission Verification and Validation Plan (MVVP). Required for post- PDR performance analysis verification, supporting system performance analysis for CDR and for Science Performance Review. Requires L2 calibrated exposures in units of e/s/pix, sky scene shall be specific for simulation scenario.

  • Verify BRJF allocations in mission-level performance budgeting flow-down, specifically, the MRD

science performance requirements justification applying as required sub-system level performance

  • Verify the impact of as designed or evolving as measured module level performance knowledge on

system performance, identify CBE system performance and verify its roboustness against possible sub-system level performance variability

  • Verify the impact of uncertainty in environment models on system performance (e.g. straylight

variability with IR sky model applied, detector performance with environment radiation model) Ø Simulations profile:

Science scene Instrument simulators Mission level features HK fidelity Observations scenario & detector selection Data model representative- ness Processing level and ext./ calibration data completeness Processing functions representative- ness

low No cosmological signal required, source content and spatial distribution shall be specific to scenarios, high flexibility needed High Instrument simulators shall be as complete as possible Medium Starting with time resolved attitude simulation only. Later thermal behaviour simulations in terms of time- dependent system PSF modeling required low No HK data required low+ from individual detectors to 4 dithers with complete FPA. Spectroscopy performance require few sq. degrees consecutive area coverage. low medium L2 (calibration data required for L3 generation will be necessary at later stages) medium Important up to L2 generation, but at early stages the extraction

  • f observables

is a task for the Simulation Analysis Procedures

slide-4
SLIDE 4

SOC simulations use cases | Roland Vavrek | ESAC| 13/01/2016 | Slide 4 ESA UNCLASSIFIED – For Official Use

Top level SOC simulation use cases - 2

Ø QLA development, testing and verification requires simulated L1 science frames in raw (ADU) units and external data and/or calibration files (FF, dark, bias, CCD diagnostics etc.). Data content shall be representative as much as possible for typical observation (calibration or science). Header structure and meta-data shall be representative.

  • Verify data-flow through interfaces and through QLA processing steps on flight representative data-

sets (in terms of structure, ordering and conventions, data rate, meta data, HK)

  • Optimize and test QLA common module diagnostics and specific diagnostic functions performance (in

terms of characterizing and trending nominal behaviour; finding and characterizing outliers and anomalies)

  • Verify QLA diagnostics performance according to QLA success criteria

Ø Simulations profile:

Science scene fidelity Instrument fidelity/ instrument modes S/C fidelity and mission level features HK fidelity Observations scenario & detector selection Data model representative- ness Processing level and ext./ calibration data completeness Processing functions representative- ness

medium/high No cosmological signal required, source flux and shape distribution shall be representative (incl. saturating sources) medium Besides nominal instrument behaviour, at later stages,

  • instr. anomalies

will be required low+ Starting with attitude simulation only. Later thermal behaviour simulations in terms of time- dependent system PSF modeling required medium TBD if simulated HK is required, or hybrid simulations where HK can be taken from WE avionics or ILT level tests low+ from 4 dithers to reference mission scenario (24h

  • perational day

TBD) medium+ QLA development applies the common data model high L1+external/cal data (flat-field, dark, bias, CCD diagnostics etc.) low N/A

slide-5
SLIDE 5

SOC simulations use cases | Roland Vavrek | ESAC| 13/01/2016 | Slide 5 ESA UNCLASSIFIED – For Official Use

Top level SOC simulation use cases - 3

Ø EAS/SAS development, testing and verification requires simulated L2 frames (individual exposures, as well as resampled and co-added images) in calibrated units (e/s/pix or flux density per pixel). Header structure and meta- data shall be representative.

  • Mainly for visualization and image analysis tools testing (EAS user interface, ESA Sky common x-

mission interface) Ø Simulations profile:

Science scene fidelity Instrument fidelity/ instrument modes S/C fidelity and mission level features HK fidelity Observations scenario & detector selection Data model representative- ness Processing level and ext./ calibration data completeness Processing functions representative- ness

low No cosmological signal required, TBD: source flux and shape distribution shall be representative low low low N/A high from 4 dithers to reference mission scenario and large-area (TBD) coverage high medium L2 low

slide-6
SLIDE 6

SOC simulations use cases | Roland Vavrek | ESAC| 13/01/2016 | Slide 6 ESA UNCLASSIFIED – For Official Use

Top level SOC simulation use cases - 4

Ø Solar System Objects detectability studies require simulated L2 science frames (individual exposures, as well as resampled and co-added images) in calibrated units (e/s/pix or flux density per pixel).

  • Derive detection envelop of SSOs on the brightness-apparent motion parameter space for CBE

system performance

  • Optimize SSO detection and characterization routines
  • SSO candidate detection pipeline could be connected to QLA (fast response needed for follow-

ups) Ø Simulations profile:

Science scene fidelity Instrument fidelity/ instrument modes S/C fidelity and mission level features HK fidelity Observations scenario & detector selection Data model representative- ness Processing level and ext./ calibration data completeness Processing functions representative- ness

low No cosmological signal required, source flux and shape distribution shall be representative, add SSO trails (with spatial

  • verdensity)

medium low+ Starting with attitude simulation only. Later thermal behaviour simulations in terms of time- dependent system PSF modeling required low N/A low+ from 4 dithers to few fields medium+ QLA development applies the common data model, SSO pipeline may be based on QLA high L1+external/cal data (flat-field, dark, bias, CCD diagnostics etc.) low N/A

slide-7
SLIDE 7

SOC simulations use cases | Roland Vavrek | ESAC| 13/01/2016 | Slide 7 ESA UNCLASSIFIED – For Official Use

Simulation process schematics

Parameter translation layer

MDB

  • As required
  • As designed
  • As built

Simulator configuration and parameter set applicable to scenario

EXTERNAL DATA

  • Out-of-field

straylight maps

  • Ground calibration

data/models

  • Performance

updates OBSERVATION CONFIGURATION

  • input sky

(oversampled intensity map or source catalogue)

  • instrument mode(s)
  • detector selection
  • pointing sequence

SIMULATOR CONFIGURATION

  • Simulation tasks

selection (shortcuts)

Instrument/spacecraft simulator components

Pipeline configurator Plug-in alternative simulation tasks L1 products Plug-in alternative processing algorithms L2 products

MISSION CONFIGURATION

  • MDB setup

Simulation Analysis Procedure (SAP) Simulation Scenario Definition (SSD)

Simulator functionality SOC scenario and plug-ins Dedicated simulation code not part of instrument simulators

L1 -> L2 processing

DB

  • Sim config.
  • Intermediate

prod.

  • Output prod.
slide-8
SLIDE 8

SOC simulations use cases | Roland Vavrek | ESAC| 13/01/2016 | Slide 8 ESA UNCLASSIFIED – For Official Use

Assumptions on simulations scenarios and simulation capabilities evolution

Ø QLA and Archive simulation plan shall be synchronized to the SGS development milestones Ø Performance simulation goals shall be synchronized to space segment development milestones Ø Performance simulation scenarios required to verify MRD requirements. The requirement flow-down to PERD, GDPRD and SRD defines which sub- system capability needs to be simulated for a given scenario.

  • The simulation plan shall map the required sub-system simulation

capabilities to a simulator code version taken into account the maturity of simulation tasks.

  • A Simulation Analysis Procedure (SAP) shall define the processing

steps (typically L2->L3) required to achieve the simulation

  • bjectives. At later stages (SGS CDR?), a large part of the SAP

shall be routed to the pipeline processing functions.