Introduction

For context, see 

What each SOOP coordinator will need to do

Ahead of the Progress Meeting on 21 June

What would we like you to do?

  1. Review the main science (or calibration) goal of the SOOP and the instruments that need to be involved, taking into account the tentative placement of the SOOP instance(s) on the 2022 timeline.
  2. Contact the involved instrument teams to
    1. discuss the modes the payload will run in and the parameters to be set (e.g. cadence, compression, etc.).
    2. Each choice of parameters may have a different data generation associated with it, so it's good to discuss the minimal acceptable and ideal level of TM generation.
    3. Also discuss any calibration needs before the SOOP can kick off
  3. With the inputs from all involved instrument teams, construct a set of instrument observations that is consistent and coordinated (e.g. aligning cadences).
    Again, a few flavours of the SOOP may be constructed: a minimal acceptable one and an ideal one. 
  4. Prepare to present at the Progress Meeting:
    1. Overview of the science (calibration) goals of the SOOP + instruments involved
    2. Proposed SOOP period(s) in the 2022 timeline + some context on the location(s) in the orbit
    3. Any need for S/C manoeuvres + any need of LL or other context data
    4. Proposed instrument contributions, i.e. required telescopes, modes, main parameters. With for each, the range within which the parameters could be tweaked without losing the science goal.
    5. Any need for calibrations, thermal adjustment, etc. beforehand 

How can you go about this?

Following tools and context information are available:

  • Temporary timeline of SOOPs in 2022: https://solarorbiter.esac.esa.int/soopkitchen/#/planning/plan/Mission%20Level%20Plan%20for%20NMP%20Segment%201
    (warning) Note none of the instrument-specific observations are representative, only the SOOP placeholders in the row called 'SOOPs'.
  • If considered useful, SOOP Kitchen can also be used to design the proposed SOOP timeline. We have copied across the plan agreed at the end of the SWT on to a child plan called SOOP Coordination for NMP Segment 1.
    (info) Note that it is not necessary to prepare a SOOP proposal in SOOP Kitchen by 21 June. It can also be prepared in a slide and SOC can help you prepare the timeline later in the tool.
  • Regarding data generation: The TM guidelines as published on Mission Level Planning of NMP Segment 1: Initial Analysis for SWT 29 can be used as guideline to find out what may be feasible and what not. But not all SOOPs in a set of RS windows need to have same TM production. Trade-offs between SOOPs can be proposed.
    Please take into account the downlink situation at the time of the scheduled SOOP to assess data latency: campaigns scheduled close to Earth (Jan-March and Nov-Dec 2022) will have hardly any data latency, while campaigns scheduled in the (more scientifically interesting) periods April-Oct may only get their data down after long delays, up to 6 months.
  • Orbit plots and movies are available here: Orbit Plots
  • Webgeocalc can be used for geometry calculations using SPICE kernels, e.g. angular separation, distance to Sun/Earth, etc.

Ahead of the Exec. SWT meeting on 13 July

After review and trade-off discussions during the Progress Meeting in June, following needs to be prepared ahead of the Executive SWT meeting:

  1. SOOP coordinators prepare the final SOOP proposals, based on the adjustments agreed in June.
  2. SOC runs a simulation with all SOOP proposals in the timeline, to check feasibility.

To be discussed how/when to fold in the results from (2) and adjust SOOP timeline to present executive SWT with a feasible baseline.


  • No labels