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

General description

Full-Disk, high resolution SOOP designed to catch eruptive events.  

This SOOP can also be aimed at measuring in-situ SEPs properties and kinetics and linking them to the observing SEPs CME acceleration.  To that end, determining the location, timing, and motion of CMEs and shocks is important.

SoloHI and Metis are leading this SOOP, while IS payload provides continuous observations. 

Default SOOP duration: 1 day (to 10 days to maximise the possibility to catch an eruptive event)

Pointing requirements: disk centre

Coordination: Can be run when Parker Solar Probe is within 0.25 AU and optimally to the east of SO (to triangulate the CME shocks).

Triggers: enabled for both IS and RS (especially if flare > M5).

Observations requirement (baseline)


Metis (lead)

METIS standard modes: GLOBAL + CMEOBS on trigger

(modelled as 2 CME events of 1 hr in the 1-day-SOOP)

CME Trigger on, Disk centre pointing needed
SoloHI (lead)Combination of shock and synoptics at perihelionCombine HI_SHOCK_PER + HI_SYN_PER (each 50% of time)
EUIGlobal Eruptive Event Mode: FSI Global eruptive event mode (G)Triggered:

EUI will be in global mode all the time (i.e. full SOOP length) but it will only prioritize the data of 1-2 events. 

Global mode generates 4,42 Gbit/hr. Let's say for now that we flush 2 hrs of data = ~8Gbits.


FDT, 2-5 minute cadence, highest spatial resolution
(PHI_nominal_FDT/HRT_0 with FDT and 5 mins cadence)

Selection of data so will check LLD


SPICE Composition Mapping (or alternatively SPICE Dynamics at start,

then SPICE Waves mode (sit-and-stare)

Off-pointing would be interesting for SPICE, but even if disk-centre pointed Composition mapping or Dynamics (both with the maximum SPICE FOV) should be ran before running Waves sit-and-stare.

SPICE_WAVES has been used for modelling SAP v.0

STIXStandard Operations: STIX Normal Mode
MAGNormal Mode
EPDNormal Mode
RPWDetection ModeDetection algorithms active
SWANormal Mode

Science objectives

SAP objectiveTargetDurationOpportunity
(e.g., orbital requirements, solar cycle phase, quadrature ...)

Operational constraints 

Additional comments CME initiationFull Disk1 Day (limited by EUI/PHI internal memory)Perihelion preferred. Quadrature with Earth preferred. Interesting throughout the solar cycle.No offpointing beyond Metis limit.

EUI/PHI at highest cadence appropriate to spatial resolution (could be slower if further away). SPICE Sit & Stare in waves mode to try and catch EUV waves.

Metis Modes:

  • GLOBAL (before the event, if possible), min. obs time 2 hr, data volume ≤ 300 Mb.
  • CMEOBS, starts after CME flag rise, min. obs time 1 hr (high cadence, 1 min), data volume ~ 2.137 Gb.
  • GLOBAL (after the event), min. obs time 2 hr, data volume ≤ 300 Mb. Where and when are shocks most efficient in accelerating particles?

Corona + Heliosphere

Particles acceleration


Good radial spread.Good to have Metis compatible

SWA 5 minutes captures

SoloHI needed for estimating the total CME energy

FSI not needed Intensity variability


Gradual SEP events


Preferable with Earth images and SO +/- 70 degrees from Earth-Sun line (probably because gradual events extend up to 100 degrees in longitude)Metis compatible

MAG/RPW/SWA not needed

FSI 5 min cadence for source identification (FSI is 10 min cadence by default) Are there favourable environments for particle acceleration?Corona + Heliosphere


FSI 10 min cadence (default)

Instances run / planned


2022-03-22 to 30 (SOOP coordinators: D. Spadaro)


2022-10-28, 2022-10-30 to 11-06 (SOOP coordinators: D. Spadaro)


2023-03-22 to 27 (SOOP coordinators: D. Spadaro)

Science outcomes

Zimbardo G., et al., A high-latitude coronal mass ejection observed with a constellation of coronagraphs: Solar Orbiter/Metis, STEREO-A/COR2, and SOHO/LASCO, A&A (special issue), submitted, 2023

Original SOOP proposers

D. Berghmans, A. Giunta, J. Hirzberger, D. Spadaro, D. Long, L. Green

  • No labels

1 Comment

  1. SOOP ID in SOOP Kitchen = LF2