General description
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: 1 hour (can be repeated several times when it fits)
Pointing requirements: may be run at disk-centre or off-pointed
Triggers: disabled
Observations requirement (baseline)
Instrument | Mode | Comment |
---|---|---|
EUI | HRI high res / high cadence modes, depending on target: (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. We download all generated data. |
PHI | PHI_nominal_HRT_0 for HRT | In mode 0, PHI generates at 1607 kbps (about 80x EIDA rate) |
SPICE | Depending 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. |
STIX | STIX Normal Mode | |
Metis | Metis FLUCTS mode at highest cadence (1s) (METIS special modes) | Only if disk centre pointed! The detection of high frequency fluctuations in the extended corona would be a new result. |
Science objectives
SAP objective | Target | Duration | Opportunity (e.g., orbital requirements, solar cycle phase, quadrature ...) | Operational constraints | Additional comments |
---|---|---|---|---|---|
1.2.1.1 Energy flux in the lower atmosphere | Bright source (could be AR but not necessary) | 20mins to 3/5 hours | perihelion for highest resolution, multiple orbits good to have | Better 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. |
1.2.1.3 Contribution of flare-like events on all scales | Flaring region (could be 'quiet' sun for nanoflares) | 2-3 hours | near-perihelion | Need EPD/SIS as well | |
1.2.1.4 Observe and explore flare-like ‘heating events’ from the quiet corona | Quiet Sun | ? | perihelion preferred but not required | multiple orbits good to have | |
1.2.1.5 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, QS | several hours | multiple orbits good to have | ||
1.2.1.8 Investigate the role of small scale magnetic flux emergence in energizing the above laying layers | several hours | near-perihelion (<0.5AU) | multiple orbits good to have | PHI/HRT leading, EUI/HRI required as support | |
1.2.2.3 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!):
| ||||
1.3.1 Solar and local origin of Alfvénic fluctuations | spicules above limb, | 1-2 hours | perihelion | Better early in mission for Ly alpha degradation. | to be combined with I_DEFAULT |
1.2.1.7 Detect and characterise waves in closed and open structures | spicules at limb, AR loobs |
Instances run / planned, differences from the baseline observations
LTP9
2022-10-12 & 13 (SOOP Coordinators: H. Peter)
LTP11
2023-03-29 and 2023-04-06 (SOOP Coordinators: H. Peter)
Any further information to be added:
(e.g. pointing description, evolution of target, coordinated observations, ...)
Science outcomes
Ref of paper using the SOOP data
Original SOOP proposers
D. Berghmans, S. Krucker, J. Hirzberger, L. Harra, D. Hassler, S. Parenti, A. De Groof, A. Zhukov
3 Comments
Jayne Lefort
For EUI, which one shall be modelled for the basic soop?
Jayne Lefort
minimum flush vol for EUI mode?
Anik De Groof
SOOP ID in SOOP Kitchen = RS5