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

Proposed SOOP Coordinators

S. Krucker, D. Berghmans, L. Harra, J. Hirzberger, N. Vilmer, D. Hassler, S. Parenti, R. Wimmer-Schweingruber, A. De Groof, D. Long, S. Matthews


This SOOP is aimed at understanding SEP properties and dynamics in relation to Flare events. EUI and STIX are leading this SOOP, while IS payload provides continuous observations. Synoptic support from other full disk RS instruments. Disk centre pointing preferred. 

 For most of the science objectives SPICE is good to have, but as the SEP events are rather rare, it is not feasible to go hunting for these events and to point SPICE to any particular region. However, since all other instruments are involved, SPICE will probably be observing anyway (SPICE best mode TBC).

Default SOOP duration: 1 day

Pointing requirements: disk centre preferred

Triggers: IS + metis trigger active


EUI (leads)

FSI Synoptic mode (S),

EUV & LYA Active Region modes (A) (triggered) with 1min cadence (default = 1or2s)

Most of the objectives in this SOOP are too exceptional to be hunted for with high-res high-cadence observations, except when they can be triggered by a STIX flag whenever the flare is in the HRI FOV.

Trigger needed: EUI to download only 1 event in HRI AR mode (~120kbits/s for 1 hour)

STIX (leads)

STIX Normal Mode


METIS standard modes GLOBAL,METIS special modes CMEOBS

CMEOBS starts after CME flag rise, min.obs time 1 hr (high cadence, 1 min), data volume~ 2.137 Gb


SoloHI Shock and Synoptic modes


PHI_magnetograph_FDT_2 (FDT)FDT in general
SPICESPICE Waves mode (is sit-and-stare)

SPICE is good to have, but no target hunting will be performed in this SOOP, so SPICE will be disk centre pointed 


MAG Normal Mode


EPD Normal Mode


RPW Normal Mode and RPW Burst Mode


SWA Normal Mode

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

Operational constraints 

Additional comments What causes SEPs' spectral breaks?Corona + Heliosphere


Radial dependence

Multiple orbits

PHI, STIX and FSI seem to be the most valuable RS instruments to address this goal. 

SoloHI + SPP would be interesting combination as well.

EUI/FSI 174, 304, 5 min cadence (FSI default cadence is 10 minutes)

EUI/HRI 174 & Ly-alpha if source is connected to SolO

SPICE would be helpful if by chance the SEP source region is in the HRI FOV AND EUI/HRI (Lya alpha) observed it -> not feasible to go hunting for these events (TBC by SWT) Explore the fact that only some of the hard X-ray peaks are related to escaping electrons, while others are notCorona & Heliosphere


PerihelionMetis compatible

EUI/HRI 1 min cadence for 30 min before and during X-ray peak (EUI AR mode triggered based on STIX flare)

EUI/FSI 10 min cadence

SoloHI & Metis connectivity with Probe.



PHI/FDT X-ray prompt events

Corona & Heliosphere

In-situ observed electron spectrum and hard X-ray photon spectrum correlation



TBC: EUI/FDT 10 min cadence, EUI/HRI 1 min cadence for 30 min before and during X-ray peak

EUI is required to see details of the flare region in order to decide if electrons and ions are accelerated by different processes at different times (but not sure how this is done in practice, we should discuss what EUI mode is needed, synoptic as described in the objective page does not seem adequate).

This question should be asked to Sam Krucker. Delayed events (between X-ray peak and electron release time)

Corona & Heliosphere

Explore the origin of the delay

It is about a secondary faint emission after the main X-ray burst that could be possibly detected for the first time.



Best when the solar limb from SolO is connected to Earth, or other s/c.

Metis compatible

TBC: EUI/FDT 2 min cadence, EUI/HRT 1 min cadence for 30 min before and during X-ray peak

EUI could be needed for studying the flare region. If there is a CME shock (2nd case)

SoloHI & METIS could be interesting. Explore the type III radio bursts delays

Corona & Heliosphere

1)Propagation effects in the interplanetary medium.

2)Coronal magnetic restructuring in the aftermath of CMEs (PHI needed)


Perihelion for Propagation effects in the interplanetary medium 

Track connected region for many days at different distances from Sun does not seem to be needed, even the value of high-res data for this objective seems doubtful (or too ambitious to plan for). If it would drive the SOOP, this would mean tracking connected region for many orbits, to enhance the chance of catching a type III radio burst.

Metis compatible

EUI/FDT 174, 304 5 min cadence (EUI default cadence is 10 minutes)

EUI/HRI 174 & Ly-alpha 2 min cadence

SPICE again, not to be hunted for. If SPICE sees it, that is better but not driver for the SOOP. Double-power law spectra

Corona + Heliosphere


Metis compatible

Metis & SoloHI for the shock observations and EUI/FSI+STIX for the flare ones

PHI not needed.

3.2.2 Latitudinal and longitudinal transport of SEPs

Corona + HeliosphereStatisticsNeeds range of latitudes but indeed this SOOP needs to be scheduled at some high-lat windows as wellMetis compatible

Best addressed by multi-viewpoint statistical dataset, e.g. SPP (really close to the sun) + SolO + earth-based RS data. -> need many events, viewed from different viewpoints and different distances

Multi-viewpoint (stereo), thus multiple SC or Earth assets

SolO: full disk imagery + Metis 

  • No labels

1 Comment

  1. SOOP ID in SOOP Kitchen = LB4