This page provides you with the general information you need to know to as a SOOP coordinator

You have been assigned as a SOOP coordinator in the next RSWs. What's next?

  • Your name + email address should have been collected and is displayed here.  If you have not heard from the ESA Solar Orbiter team, please reach out.
  • A meeting will be organised after the executive SWT for a placement of your SOOP timeline, called the "MLP refinement planning" meeting. It is necessary to attend this meeting as decisions on the timings of your SOOP and placement on the orbit are made then. In order to prepare this meeting, have in mind the constraints necessary to effectively run your SOOP. You can also review the SOOP pages for further information. 
  • Following the meeting, you can request access to the SOOP Kitchen planning tool. Please contact the SOC team
  • This is the tool that is used to place your RS instruments observation blocks with details on the operations of each instrument to generate an estimation on the telemetry. You will be given a few months to:
    1. rethink/redesign your SOOP if the timeline given to your SOOP differs from your original plan (e.g. due to operational constraints)
    2. provide further information on the SOOP page related to your SOOP
    3. contact the instrument POCs (see the SOOPs Coordinators + POCs mailing list) to discuss the details of the instrument operations (cadence, FOVs, lines for spectroscopy, ...). This is also a good time to start thinking about any other coordinated observations you would want to have (e.g. IRIS, Hinode, ground-based observations). 
  • ~2 months before the LTP start, you will need to attend the Science Operations Working Group (SOWG). This is a crucial meeting where your role will be to guard the consistency of the SOOP and the coordination between each of the instrument contributions, while the instrument timelines are being filled by the instrument teams.

Are you requesting support from other observatories


  • In the same time frame, if you are requesting support from the IRIS mission, please send your suggestions to miho.janvier[at]esa.int so that the requests can be collated and sent to the IRIS team.


  • Currently, ground-based observatories (DKIST, Canary Islands observatories (Themis, Greggor, SST), ALMA, Big Bear Solar Observatory, LOFAR...) are happy to support Solar Orbiter whenever possible, but this is a case-by-case situation. You are welcome to reach out directly to the observatories via the list of contacts and let Miho know.

Up to ~2 weeks before your SOOP runs: close discussions with the instruments teams 

  • Two weeks before your SOOP is run during the so-called "Short-term planning", instrument teams will send their instrument commanding to SOC and MOC to be uploaded to the spacecraft.
  • Instruments teams may contact you prior to this cut-off line in case some tweaks are necessary. No changes (e.g. on timings) can be made after the operation requests are sent.

Your SOOP is ready to be run! Are you following a specific target? 

  • Depending on the SOOP you have proposed, your science target may need a specific pointing (e.g. slow solar wind source, active region). In such a case, as a SOOP coordinator, you will need to attend the pointing decision meetings. In general, these meetings are held 2 days prior to your target being observed. You will need to follow the procedures described here to use the JHelioviewer tool and provide the coordinates of your science target. If your science target includes a connection to a specific point in the heliosphere (e.g. Earth, Solar Orbiter, PSP), then a member of the Modelling and Data Analysis Working Group (MADAWG) will be present to provide you with information on the connectivity at the time of the pointing decision meeting. 

A note on data latency 

  • The data latency may be quite high on this mission, depending on the location in the orbit the SOOP was scheduled. As a rule of thumb, data taken when we are close to earth will come down in a few days max, while data taken at the far side of the sun may take up to 2-3 months to be retrieved. 

Your SOOP was run, and you are now working on the science results: what's next? 

  • Some instrument teams are making available "quicklooks" of the data so that you can check their availability. 
    This is the case for SPICE, where one can check these quicklooks in the following link.
  • As courtesy for future SOOP coordinators, and for the community at large, you will be requested to update the SOOP pages with the outcomes of your SOOP. This can be a link to the papers, science nuggets, or any activity that will be using your SOOP data. Please inform the ESA Solar Orbiter team of any information concerning your SOOP so this information can appear on the public SOOP Summary page.

Specific information for LTP13 (Q4 2023):

(greyed cells = past events)

The list of SOOP coordinators + Instrument POCs can be found here

DateMeetingEventSOOP COORDINATORS TO DO / OUTPUTS


Preparation MLP for NMP (focus on 2023-H2 = LTP12+13):

  • Review PSP, Bepi coordination & any coordination with other missions/observatories (opportunities from Jul 2023 onwards) 
  • SOC prepares context for start NMP planning (orbit plots, important events, ...)
    and prepares downlink simulations

Think about what SOOP to be run. 

Contact instrument teams to get the SOOP approved by them + get it proposed at the SWT.

16 Nov 2022

>7m before Jul 2023

SWT 34

short, online

Nominal Phase MLP (2023-H2): Planning of science priorities for Jul-Dec 2023 (LTP12+13)

  • Prioritized list of SOOPs to run during LTP13 RSWs
  • + SOOP coordinators 

→ note: SOC understands these details may come later, timing TBD, ideally before April
confirmed to take place in Feb 2023


15 Feb 14:00-18:00 CET

SWT 35

short, online

Nominal Phase MLP (2023-H2): Planning of science priorities for Jul-Dec 2023 (LTP12+13)

  • Prioritized list of SOOPs to run during LTP13 RSWs
  • + SOOP coordinators 
SOOP coordinators should be notified by the instrument teams PIs if their SOOP has been selected.
Thursday 23rd 14:00 - 17:00 CET

Refinement of MLP for LTP13 RSWs

LTP13 SOOP coordinators + SOC meets to design and discuss a high-level SOOP plan for the 3 RS windows in LTP13, based on decisions made by SWT in Feb.

+ any requests for calibrations or special operations in LTP13 needing S/C manoeuvres.

Timing TBD, deadline for input on special manoeuvres and pVSTP needs is end May

Attend the meeting, provide information on SOOP constraints, decide on the timeline.
end June 2023

Preparation LTP13: 

  • Instrument teams review observation definitions in SOOP Kitchen
  • MOC distributes formal event skeleton for LTP13 (FECS+PTEL) 
  • SOC prepares SOOP Kitchen (obs definitions, events, ...)
  • Update context page LTP13 Q4-2023
SOOP coordinators to update SOOPKitchen w/ preliminary plans for observations
Early July 2023kick off LTP13 planningSOC and PSs inform the instrument teams about the planning goals of LTP13 + scope for plan optimisationAttend meeting
10-12 July 2023SOWG

NMP Planning LTP13: observations and SOOP planning for Q4-2022

Regular SOWG to plan for a 3 months period including RSWs.

There will be a high-level review of LTP14 (Q1-2024) as well
any S/C manoeuvres needed during LTP14, so the requests can be sent to MOC.

Attend meeting w/ instrument POCs + finalise the timeline with the instrument observations.
by early Aug 2023
~1m before first IOR deadline 

Output LTP13 planning:

  • SOC distributes formal products (EFECS, TMC, obs timelines)
    and context plan in SOOP Kitchen
  • = input for IOR writing for STPs included in LTP13 (star)


SOOP timeline - 2 weeks
IORs are sent by instrument teams
SOOP timeline - 2 days (if needed)

Attend pointing decision meeting (if needed). Calendar of meetings sent directly to the SOOP coordinators.
SOOP timeline + a few months

Feedback needed to update the SOOP pages + SOOP coordinators feedback meeting organised.

(star) STP planning schedules are published per LTP cycle, see child pages under the LTP pages, e.g. under LTP06 Q1-2022 


Specific information for LTP15 (Spring perihelion 2024):

(greyed cells = past events)

The list of SOOP coordinators + Instrument POCs can be found here

DateMeetingEventSOOP COORDINATORS TO DO / OUTPUTS


Preparation MLP for NMP (focus on 2024-H2 = LTP16+17):

  • Review PSP & any coordination with other missions/observatories
  • SOC prepares context for start NMP planning (orbit plots, important events, ...)
    and prepares downlink simulations

Think about what SOOP to be run. 

Contact instrument teams to get the SOOP approved by them + get it proposed at the SWT.

mid Oct date TBD

Refinement of MLP for LTP15 RSWs

LTP15 SOOP coordinators + SOC meets to design and discuss a high-level SOOP plan for the RS windows in LTP15, based on decisions made by SWT in April 2023.

+ any requests for calibrations or special operations in LTP15 needing S/C manoeuvres.

Timing TBD, deadline for input on special manoeuvres and pVSTP needs is early Nov (early deadline so we can process MOC input LTP15 before Xmas) 

 

Attend the MLP refinement meeting.


Following the MLP refinement meeting:

Pre-LTP TN for LTP15:

  • SOC requests S/C manoeuvres for LTP15 Q2-2024 to Flight Dynamics

Early December 

~3m before start LTP15


Preparation LTP15 : 

  • Instrument teams review observation definitions for NMP in SOOP Kitchen
  • MOC distributes formal event skeleton for LTP15 (~11 Dec)
  • SOC prepares SOOP Kitchen (obs definitions, events, ...)
  • Update context page LTP15 Q2-2024

 

Mid Dec

kick off LTP15 planning

SOC and PSs inform the instrument teams about the planning goals of LTP15 + scope for plan optimisation

 

16-18 Jan 2024

~2m before start LTP15

SOWG 24

NMP Planning LTP15  : observations and SOOP planning for Q2-2024

Regular SOWG to plan for a 3 months period including RSWs.

SOOP coordinators need to have prepared all their observation blocks in SOOPKitchen ahead of the meeting. Any tweak to the program can happen during the meeting, after which the plan is finalised.

Until mid-February 2024

 

External coordination requests

All requests for external coordination, especially Hinode and IRIS, should be sent by SOOP coordinators.

SOOP timeline - 2 weeks
IORs are sent by instrument teams
SOOP timeline - 2 days (if needed)

Attend pointing decision meeting (if needed). Calendar of meetings sent directly to the SOOP coordinators.
SOOP timeline + a few months

Feedback needed to update the SOOP pages + SOOP coordinators feedback meeting organised.


Specific information for LTP17 (Fall perihelion 2024):

(greyed cells = past events)

The list of SOOP coordinators + Instrument POCs can be found here

DateMeetingEventSOOP COORDINATORS TO DO / OUTPUTS


Preparation MLP for NMP (focus on 2024-H2 = LTP16+17):

  • Review PSP & any coordination with other missions/observatories (opportunities from Jul 2024 onwards) 
  • SOC prepares context for start NMP planning (orbit plots, important events, ...)
    and prepares downlink simulations

Think about what SOOP to be run. 

Contact instrument teams to get the SOOP approved by them + get it proposed at the SWT37.

18-20 September 2023, 14-18h CEST

>7m before Jul 2024

SWT-37 (online)

Nominal Phase MLP (2024-H2): Planning of science priorities for Jul-Dec 2024 (LTP16+17)

  • Define prioritized list of SOOPs to run during LTP16-17 RSWs
  • Appoint SOOP coordinators 


 

SOOP coordinators are assigned/


Output MLP (2024-H2):

  • SOC sends pass requests + RSW locations to MOC
  • MOC formally requests passes from ESTRACK (to be fed into FECS) & sets LTP boundaries for LTPs 16 and 17

Dates TBD

 

LTP17 MLP refinement meeting

SOOP coordinators need to attend

end June

~3m before start LTP

 

kick off LTP17 planning

 

SOC and PSs inform the instrument teams about the LTP planning goals + scope for plan optimisation

Jul 2024

~2m before start LTP

SOWG 25

NMP Planning LTP17  : observations and SOOP planning for Q2-2024

Regular SOWG to plan for a 3 months period including RSWs.

There will be a high-level review of LTP-18 (Q1-2025) as well
+ any S/C manoeuvres needed during LTP-18, so the requests can be sent to MOC.

 

SOOP coordinators need to have prepared all their observation blocks in SOOPKitchen ahead of the meeting. Any tweak to the program can happen during the meeting, after which the plan is finalised.

By mid-August 2024

 

External coordination requests

All requests for external coordination, especially Hinode and IRIS, should be sent by SOOP coordinators.

SOOP timeline - 2 weeks
IORs are sent by instrument teams
SOOP timeline - 2 days (if needed)

Attend pointing decision meeting (if needed). Calendar of meetings sent directly to the SOOP coordinators.
SOOP timeline + a few months

Feedback needed to update the SOOP pages + SOOP coordinators feedback meeting organised.


  • No labels