Page tree
Skip to end of metadata
Go to start of metadata

During SOWG#8, an LTP planning exercise was held in which one 6-months long planning period - Jan to Jun 2022 - was planned based on input SAP.
The goals of the exercise were to:

  • Test out the SOOP planning concept during SOWG meeting
  • Use for the first time a prototype of LTP planning software (SOOP kitchen)
  • Use for the first time the preliminary, high level instrument models (i.e. observation definitions)
  • Exercise the LTP planning interfaces:
    • From SAP to SOOP-plan
    • From FECS to E-FECS
    • From Data return simulations to TM corridors
    • -> generate examples of each of the 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-08 TMC example filesThis 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.
  •  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 also serve as general example files for LTP planning output.

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 SOOP 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 first release of the SAP available for the SOWG#8 planning exercise, a mini-SAP for the 6-months planning period has been described and presented to the SOWG through slides:
    see  PlanningExercise2016.pptx slides 31 to 49.
  • The SOOP plan 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 (could be for example scheduled IS burst modes that need to be synchronised, RS data with synchronised cadence, IIC settings, etc.).
    For this LTP planning exercise, the spirit of each modelled SOOP has been described in the presentation slides: 
    see PlanningExercise2016.pptx  slides 31 to 50 (including the main calibration programs on slide 50).

Record of simulation output (for context only)

During the planning exercise, timelines of instrument observations were built and modelled at a high level. Both power consumption and data generation were simulated at high level and constraint-checked through SOC planning software.
Below, we attach a record of the simulated timelines and output of the planning simulations, as performed during and right after the planning exercise:

These files can serve as context information for IOR writing in the sense that they specify which observations were simulated during the LTP planning process and the corresponding output.

It is however important to note that:

  1. Observations are not planned to the fine granularity of the platform and science constraints in the (E-)FECSThis means that some observations in the  timelines and sous-chef output attached above may continue during short events (e.g. attitude disturbances) they are incompatible with. This is acceptable during the high level planning at LTP. For IORs however, the constraints set by the E-FECS take precedence over any observation setting in the simulated SOOP plan!
    Similarly, instrument teams are free to tweak start/end time and parameters of the observations as long as they do not violate neither the E-FECS nor the TMcorridors.
  2. The simulation ran at SOWG-8 was imperfect in the sense that not all instrument observations were planned according to the given boundaries: some instrument timelines generated less TM than the guidelines given in the presentation. At the time of the exercise there was no time to do an extra optimisation round. This resulted in lost downlink capability, suboptimal observation settings and packet stores with lower fill states than aimed for at the end of the planning period. (See annotations in the graphs on data generation attached above.)
    Again, the TM corridors are the only formal guideline for TM generation and take precedence over the simulated observation timelines attached below. Instrument teams need to make sure they follow the guidelines described in the science plan (SAP and SOOP description) while optimising TM generation within the TMcorridors.

 

 

  • No labels