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

Proposed SOOP Coordinators

D. Berghmans, S. Krucker, J. Hirzberger, L. Harra, D. Hassler, S. Parenti, A. De Groof, A. Zhukov


This SOOP describes a coordinated observation of all high resolution RS instruments, running at highest resolution and variable but high cadence, for a short period of time.

As a planning scenario, we propose to run this SOOP at every perihelion window where we have some extra TM to spare, or where the campaign would fit without sacrificing too much of the rest of the orbit.

This SOOP can be run for different targets, also at plain disk centre, as it is aimed to discover new physics and compare high cadence dynamics in all kinds of solar regions.

Ideally, we would like to observe the same active region close to the disk center and at the limb. This will probably be not possible, so two active regions (one close to the disk center, one at the limb) should be observed. The ideal duration would be 1 hour for each pointing, i.e. 2 hours of observations in total. If this is too much telemetry-wise, then we could perhaps go down to 30 minutes of continuous observations for each pointing, but 10 minutes sounds too short.

Default SOOP duration: 10 mins (can be repeated several times when it fits)

Pointing requirements: may be run at disk-centre or off-pointed

Triggers: disabled


HRI high res / high cadence modes, depending on target:
EUV & LYA Quiet Sun modes (Q),
EUI/HRI Coronal hole mode (C) and
EUI/HRI Active Region mode (A))
EUI/HRI Discovery mode (D) to "discover" periods <10s, min observation time 300s.

(currently modelled with AR mode with default cadence (1&2s), 5400kbps )

QS and AR mode, as defined now, generate at 4600-5400 kbps. (i.e about 250x EIDA rate)

In most extreme case, i.e. Discovery mode, HRI would generate 543MB per 10 mins SOOP duration.
(data rate = 7240 kbps, i.e. about 350x EIDA rate)

We download all generated data.


PHI_nominal_HRT_0 for HRTIn mode 0, PHI generates at 1607 kbps (about 80x EIDA rate)
SPICEDepending on science goal, but SPICE Waves mode for highest resolution sit-and-stare,
SPICE 30"-wide Movie if you want more spatial information 
In Waves mode, SPICE generates at ~50 bkps (about 3x EIDA rate). Model as SPICE Waves mode for SAP v0.
STIXSTIX Normal Mode

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

Operational constraints 

Additional comments Energy flux in the lower atmosphereBright source (could be AR but not necessary)20mins to 3/5 hoursperihelion for highest resolution, multiple orbits good to haveBetter early in mission for Ly alpha degradation.

Duration for EUI observations depend on mode: discovery mode may not run long but can be combined with other mode like A or Q.

EUI/HRI-LyA preferred over HRI-EUV. Contribution of flare-like events on all scalesFlaring region (could be 'quiet' sun for nanoflares)2-3 hoursnear-perihelion
Need EPD/SIS as well Observe and explore flare-like ‘heating events’ from the quiet coronaQuiet Sun?perihelion preferred but not requiredmultiple orbits good to have Determine whether coronal heating is spatially localized or uniform, and time steady or transient or impulsive for a wide range of magnetic loops with different spatial scales.AR, AR moss, QSseveral hours
multiple orbits good to have Investigate the role of small scale magnetic flux emergence in energizing the above laying layers
several hoursnear-perihelion (<0.5AU)multiple orbits good to havePHI/HRT leading, EUI/HRI required as support What is the nature and origin of waves, turbulence and small-scale structures?

to be combined with L_FULL_HRES_HCAD_Coronal-Dynamics (RS cadence TBC!):

  • Long-term observations.
  • Short duration bursts near perihelion.
1.3.1 Solar and local origin of Alfvénic fluctuations

spicules above limb,
AR loops,

1-2 hoursperihelionBetter early in mission for Ly alpha degradation.

to be combined with I_DEFAULT Detect and characterise waves in closed and open structuresspicules at limb, AR loobs

  • No labels


  1. For EUI, which one shall be modelled for the basic soop?

  2. minimum flush vol for EUI mode?

  3. SOOP ID in SOOP Kitchen = RS5