Solar Orbiter SOC Public
Page tree
Skip to end of metadata
Go to start of metadata

During SOWG#10, a 2nd LTP planning exercise was held in which one 6-months long planning period during Cruise - Jan to Jun 2020 - was planned.
It was based on the Cruise Phase activity plans provided by the instrument teams, which were translated by the SOC in the following summary (reviewed by the Instrument Teams before the meeting):

The goals of the exercise were to:

  • Test out the Long Term Planning concept during SOWG meeting
  • Use the first release of LTP planning software SOOP kitchen, as built up from the prototype used during SOWG 8 Planning Exercise
  • Use the first release of the high level instrument models (i.e. observation definitions)
  • Exercise the LTP planning interfaces:
    • From SAP to LTP-plan 
    • From FECS to E-FECS
    • From Data return simulations to TM corridors
    • -> generate each of the formal LTP planning products, as input to IOR generation

Below we describe and attach the resulting output files of this exercise (see bold text above): the LTP planning products.

Formal LTP planning products / output files

The formal output files from an LTP planning are the E-FECS (Enhanced Flight Event Communication Skeleton) and the set of TM corridors (TMC), one for each instrument. These planning products serve as formal interfaces between LTP and MTP and as formal guideline for the writing of IORs (Instrument Operation Requests). The Interface Control Documents describing these planning products are available from SOC Public Documents.

  • SOWG-10 TMC example files : This confluence page contains the TMC files, in XML format, that were generated by the SOC based on the simulated planning period, together with the corresponding ICD and context information.
  • SOWG-10 EFECS example file : The E-FECS, in XML format, that was based on a MOC-generated FECS and enhanced by SOC with science planning constraints defined during the LTP planning simulation

The TMC and E-FECS output files from the planning exercise will be used as input for the 0th end-to-end test that will take place early 2018.

LTP documentation and context information: Science plan

Apart from the E-FECS and TM-corridors that formalise the constraints that instrument teams need to respect when writing IORs, the instrument commanding shall also respect the science and operational guidelines described in the SAP and the LTP plan.

  • The SAP is a document that will describe for each planning period - covering 6 months - what the science objectives are that will be addressed and how.
    As there was no SAP available for Cruise Phase, the context for planning was the instrument teams provided information in user manuals and calibration plans: Cruise Phase Checkout (RS) and Cruise Phase Science (IS)
  • The LTP plan, with instrument observation timelines is generated through the LTP planning process at the SOWG meeting. It consists of a description of the coordinated set of scientific observations that are needed to address a certain science goal, and any operational details that need coordination between instruments. 

Record of simulation output (for context only)

The input and results of the exercise during SOWG10 have been presented in the SOWG10 presentations: 

  • No labels