HOP list   Monthly Events

HINODE Operation Plan (HOP)

accepted on

15-sep-2022


 HOP No.

 HOP title

HOP 0442

Solar Orbiter coordinated observations of long-term monitoring of an AR

plan term

2022/10/17-2022/10/27
2023/10/12-2023/10/23

@ @

proposer

 name : Valori, Parenti, Orozco Suarez, Strecker,  Hirzberger, Lagg,  Buchlin, Janvier, and the SO/PHI team @  e-mail : valori[at]mps.mpg.de, susanna.parenti[at]ias.u-psud.fr, orozco[at]iaa.es, streckerh[at]iaa.es, hirzberger[at]mps.mpg.de, lagg[at]mps.mpg.de, eric.buchlin[at]ias.u-psud.fr, miho.janvier[at]universite-paris-saclay.fr

contact person in HINODE team

 name : DeRosa, Shine @  e-mail : derosa[at]lmsal.com, Shine[at]lmsal.com

 abstract of observational proposal
Main Objective: Coordinated observations with the Solar Orbiter (SO) Polarimetric and Helioseismic Imager (PHI) High-Resolution Telescope (HRT) for the long-term evolution of a tracked active region (AR) will take place from 17th to 26th October 2022. These observations are associated with the R_SMALL_MRES_MCAD_AR-Long-Term SOOP (see link below).

Scientific Justification: SO was successfully launched on Feb. 10th, 2020, the nominal mission phase started on Jan 1st, 2022. All its onboard instruments are performing nominally and were commissioned during the early phase of the mission. Among them, SO/PHI provides maps of the vector magnetic field and line-of-sight velocities with two telescopes (Full Disk Telescope, FDT, and HRT); SPICE is the UV spectrometer and EUI/HRIEUV is the coronal high cadence/spatial resolution imager which provide transition region and coronal plasma parameters.

Scientific goal: The proposed HOP is planned to run in parallel to the R_MRES_MCAD_AR_Long_Term SOOP that will combine observations by SO and Earth-bound observatories to follow one AR for as long as possible. The AR will be selected from low-latency data when SO is behind the Sun. Depending on where the AR is located, the combined coverage can be in excess of two weeks, thus providing the data for one of the major scientific goals of SO: the combined data will be used to study the formation and decay of the target AR, ongoing processes of filament formation and stability, the evolution of magnetic helicity in the AR, and, possibly, CME triggering, in a continuous manner for an unprecedented span of time. Details about this specific science SOOP are public and can be found in:
https://issues.cosmos.esa.int/solarorbiterwiki/display/SOSP/R_SMALL_MRES_MCAD_AR-Long-Term

 request to SOT
We request two fast maps (320"x164") daily on the interval 12/10/2023 - 19/10/2023
  (end date inclusive - following dd/mm/yyyy format)
The first map we request to start at 9UT to coincide with the start of the EUI
  HRI high cadence 1hr burst, and the GREGOR & SST co-observations at 9UT
The second map we request to start at 20UT to coincide with DKIST's observation time
On 17/10/2023 we do not request a map at 20UT, as there is an interruption due the
  R_SMALL_HRES_MCAD_Polar-Observations SOOP (11:30-21:00UT)
For the period following the end of the SOOP (20/10/2023 to 25/10/2023, or whenever the
  target AR reaches the West limb as seen from Earth): we request two fast maps, 320hx164h, starting at 9UT and 20UT
The above are intended as starting times of SP observations. Notice that, in the above, we
  considered one-hour duration for the SP scan of 320h width, and that the AR will be at the centre of the FoV.
Telemetry requirement is expected to be 600 Mbits for each map. In the case of telemetry
  conflict with other HOPs, we would
1. Accept a reduced width of the field of view, as long as the AR is contained within the FoV
2. Prioritize later dates in the SO+Hinode co-observation interval, or whenever the target AR reaches the limb as seen from Earth, over earlier ones.

---
Science support for the HRT high-resolution campaign.
Two fast maps at the start and after the end of the SOOP window?
The above are intended as starting times of SP observations. Notice that, in the above, we considered one-hour duration for the SP scan of 320h width, and that the AR will be at the centre of the FoV, resulting in SP starting to observe 20 minutes earlier than the corresponding PHI observation of the same time.
Adjustments might be necessary.
Telemetry requirement is expected to be 600 Mbits for each map. In the case of telemetry conflict with other HOPs, we would
1) Accept a reduced width of the field of view, as long as the AR is contained within the FoV and the time of SP scans overlap with the corresponding time of PHI-HRT observations given in gTarget of Interesth
2) Prioritize later dates in the SO+Hinode co-observation interval and in the days following the end of the SOOP (2022/10/28 to 2022/11/2, or whenever the target AR reaches the limb as seen from Earth) over earlier ones.

---
For SO+Hinode co-observation interval (2022/10/17 to 2022/10/27): we request two fast maps,
320hx164h, with the first starting at 06:40 UT on 2022/10/17, at 13:40 UT on 2022/10/18, and at 18:40 UT from 2022/10/19 to 2022/10/26; and the second starting at 08:40 UT for all days.
For the period following the end of the SOOP (2022/10/28 to 2022/11/2, or whenever the target AR reaches the limb as seen from Earth): we request two fast maps, 320hx164h, starting at 08:40 UT and 18:40 UT.
The above are intended as starting times of SP observations. Notice that, in the above, we considered one-hour duration for the SP scan of 320h width, and that the AR will be at the centre of the FoV, resulting in SP starting to observe 20 minutes earlier than the corresponding PHI observation of the same time.
Adjustments might be necessary.
Telemetry requirement is expected to be 600 Mbits for each map. In the case of telemetry conflict with other HOPs, we would
1) Accept a reduced width of the field of view, as long as the AR is contained within the FoV and the time of SP scans overlap with the corresponding time of PHI-HRT observations given in gTarget of Interesth
2) Prioritize later dates in the SO+Hinode co-observation interval and in the days following the end of the SOOP (2022/10/28 to 2022/11/2, or whenever the target AR reaches the limb as seen from Earth) over earlier ones.

(edited on 2022.10.13)

 request to XRT
On each day of the SOOP, from 12/10/2023 to 19/10/2023, we would like to run the Be-thin
  filter at 30s cadence (or less) once a day, during the high cadence burst of EUI/HRI which will
  always take place at 9:00-10:00UT
On each day of the SOOP, from 12/10/2023 to 19/10/2023, we would like to run the Be-thin
  filter at 30s cadence (or less) once a day, during the co-observation with DKIST from 20-21UT,
  (except for 17/10/2023 during the Polar Observation SOOP interruption).
Outside of these times, we would like to run the same filter at 1 min cadencefor the rest of
  the observing slot.
The same raster can be applied in the days following the end of the SOOP (20/10/2023 to
  25/10/2023), or whenever the target AR reaches the West limb as seen from Earth)
Timing can be adapted to needs

---
On each day of the SOOP, we would like to run the Al/poly at 30s cadence (or less) once a day, during the high cadence of EUI/HRIs.
Outside of these times, we would like to run the same filter at 1 min cadence for the rest of the observing slot. The same raster can be applied in the days following the end of the SOOP (whenever the target AR reaches the limb as seen from Earth); timing can be adapted to needs; timing can be adapted to needs.

---
On each day of the SOOP, from 2022/10/17 to 2022/10/26, we would like to run the Al/poly at 30s cadence (or less) once a day, during the the high cadence of EUI/HRIs, which are
from 07:00 to 07:30 on 2022/10/17;
from 14:00 to 14:30 on 2022/10/18;
from 19:00 to 20:00 on 2022/10/19, 2022/10/20 and 2022/10/21
from 19:00 to 19:30 on the remaining days of the SOOP from 2022/10/22 to 2022/10/26;
Outside of these times, we would like to run the same filter at 1 min cadence for the rest of the observing slot. The same raster can be applied in the days following the end of the SOOP (2022/10/28 to 2022/11/2, or whenever the target AR reaches the limb as seen from Earth); timing can be adapted to needs; timing
can be adapted to needs.

 request to EIS
EIS in parallel with eSPICE_COMPOSITIONf study of Solar Orbiter/SPICE (3h46min):
1. Run 1 ID 600 (DHB_007v2) followed by 2 runs of ID 381 (YKK_ARabund01).
  Do not run 1 YKK_ARabund01 alone.
2. If we need to reduce the TM: run 1 ID 600 (DHB_007v2).
SPICE_COMPOSITION study times:
12/10/2023 0:00-7:34UT: Run point 1 twice.
  If telemetry constraints, run it only once close to the next DYNAMICS study.
13/10/2023 0:36-4:23UT: Run point 1
13/10/2023 22:19-2:06UT (ending on 14/10/2023): Run point 1.
  If telemetry problems, remove this run.
15/10/2023 3:29-7:16UT: Run point 1
16/10/2023 0:57-4:44UT: Run point 1
17/10/2023 22:00-5:34UT (ending on 18/10/2023): Run point 1.
  If telemetry problems, remove this run.
18/10/2023 22:00-5:34UT (ending on 19/10/2023): Run point 1

EIS in parallel with eSPICE_DYNAMICSf study of Solar Orbiter/SPICE: run EIS raster ID 495 EIS_HH_frare_raster_v5. Be sure that the run is within the high cadence slot time of EUI/HRI which is 9-10UT each day.
SPICE_DYNAMICS study times:
12/10/2023 7:38-21:00UT
12/10/2023 21:05-23:37UT
13/10/2023 4:23-21:13UT
14/10/2023 5:52-20:59UT
14/10/2023 21:04-23:26UT
15/10/2023 7:15-21:01UT
15/10/2023 21:05-00:00UT (ending on 16/10/2023)
16/10/2023 4:44-21:00UT
17/10/2023 1:47-11:17UT
18/10/2023 5:34-21:03UT
19/10/2023 5:34-20:17UT
19/10/2023 20:31-23:50UT

---
On each day of the SOOP, we would like to run the Raster ID 573 (el_dhb_raster2) or ID 555 (flare_SNS_v2, sit and stare) once a day. This is supposed to run in parallel to the SPICE dynamic studies.
If there are telemetry constraints, the cadence will be discussed with the HOP PI. Priority is given during the period of the high cadence of EUI/HRIs.
On each day of the SOOP, we would like to run the Raster ID 381 (YKK_ARabund01) or ID 600 (DHB_007_v2) once a day (except on the 2022/10/25 where we request two slots). This is supposed to run in parallel to the SPICE composition studies.
The same raster can be applied in the days following the end of the SOOP (whenever the target AR reaches the limb as seen from Earth); timing can be adapted to needs.

---
EIS in parallel with eSPICE_COMPOSITIONf study:
o Run 1 ID 600 (DHB_007v2) followed by 2 runs of ID 381 (YKK_ARabund01).
 Do not run 1 YKK_ARabund01 alone.
o If we need to reduce the TM: run 1 ID 600 (DHB_007v2)
E October 16th 23:25 - 17th 06:59 UT
E October 19th 05:00 - 07:39 UT
E October 26th 03:50 - 10:20 UT
o 1 Run ID 600 (DHB_007v2) or more depending on the TM:
E October 18th 03:10 - 07:00 UT
E October 20th 03:10 - 07:00 UT
E October 20th 23:15 - 21st 03:07 UT
E October 22nd 03:20 - 07:55UT If enough TM only.
E October 22nd 21:00 - 23st 00:47 UT.
E October 23rd 19:55 - 23:10 UT. If enough TM run also YKK_ARabund01.
E October 24th 23:20 - 25st 02:35 UT
E October 25th 19:54 - 25st 23:09 UT
E October 29th
E November 1st
E November 2nd
E November 3rd
E November 6th

EIS in parallel with eSPICE_DYNAMICSf study: Be sure that the run is within the high cadence slot time of EUI/HRIEV (see https://docs.google.com/spreadsheets/d/120XJuJ8ZQv8Aj1bH_9WUuwHfSKXX2tgdRpuYf-cVPOs/edit#gid=1607350597). EIS study: raster ID 495EIS_HH_frare_raster_v5
o October 17th 07:00 - 24:00 UT. Priority given to cover earlier than 23:03UT.
    o EUI high cadence 2022-10-17 07:00 - 2022-10-17 07:30 UT
o October 18th 07:55 - 24:00 UT. If enough TM, start 1h earlier.
    o EUI high cadence 2022-10-18 14:00 - 2022-10-18 14:30
o October 19th 07:40 - 24:00 UT. Priority given to cover earlier than 23:00UT.
    o EUI high cadence 2022-10-19 19:00 - 2022-10-19 20:00
o October 20th 08:00 - 23:05 UT. If enough TM, start 1h earlier.
    o EUI high cadence 2022-10-20 19:05 - 2022-10-20 20:05
o October 21th 07:55 - 24:00 UT. Priority given to cover earlier than 23:00UT. If enough TM start at 03:10UT.
    o EUI high cadence 2022-10-21 19:05 - 2022-10-21 20:05
o October 22nd 08:00 - 20:46 UT.
    o EUI high cadence 2022-10-22 19:05 - 2022-10-22 19:35
o October 23nd 06:30 - 19:51 UT. If enough TM, start earlier. Priority to the extra composition after 23 UT (see above).
    o EUI high cadence 2022-10-23 19:05 - 2022-10-23 19:35
o October 24th. 08:00 - 22:19 UT. If enough TM start earlier (after 03:15 UT).
    o EUI high cadence 2022-10-24 19:05 - 2022-10-24 19:35
o October 25th. 07:10 - 19:50 UT.
    o EUI high cadence 2022-10-25 19:05 - 2022-10-25 19:35
o October 26th. 10:20 - 23:06 UT.
    o EUI high cadence 2022-10-26 19:05 - 2022-10-26 19:35
o October 29th. Priority starting after 23:30 October 31st
o October 31st
o November 2nd. Priority given to cover earlier than 22:34 UT.
o November 3rd. Priority given to cover earlier than 22:30 UT.
o November 6th. Priority given to cover earlier than 08:21 UT.

 other participating instruments
N/A

 remarks
Dates: Oct 12-19, 2023

Time window: Variable with pause for SO-PO on Oct 17.
See: https://s2e2.cosmos.esa.int/confluence/display/SOSP/Solar+Orbiter+Planning+-+for+coordination+with+external+parties DKIST co-observations are planned to start at around 18:00UT.

Target(s) of interest: SO will point at an AR, which will be identified, likely, three days in advance of the first observation on October 12th. The same AR is expected to be tracked during the whole duration of required co-observation.

---
Solar Orbiter/SPICE/EUI detailed planning and other useful information for the coordination: https://docs.google.com/spreadsheets/d/120XJuJ8ZQv8Aj1bH_9WUuwHfSKXX2tgdRpuYf-cVPOs/edit#gid=1607350597 This includes the pointing coordinates as seen from Earth.

Target: At the beginning of the sequence, priority will be given to a structure on the east quadrants, as seen from Solar Orbiter. This means east limb or close to the limb as seen from Earth.

When on the disk, tracking mode ON. For limb observations, this will to be confirmed.

---
Dates: We request support for scientific activities during the SO PHI/EUI/SPICE high-resolution observations:
From approximately 2022/10/17 (start of the SOOP) to 2022/11/2 (last day that an AR is on disk as viewed from Earth, if it were at -135 degrees for SO on 2022/10/17). The actual interval will be adapted after target selection. On each day of the requested interval the same set of observations for SOT, EIS, and XRT are requested. The AR should be tracked for the whole duration of the HOP, if feasible.

The exact start and end of the requested Hinode coverage will be known after the target selection, which will happen on 2022/10/12 on a preliminary base, and confirmed in the following days until 2022/10/16 (last pointing update possibility for SO). It is understood that any updates communicated to Hinode between 2022/10/12 and 2022/10/16 may not be implemented until 2022/10/18 due to the Hinode upload schedule.

Time window: Various times; see instrument-specific instructions below.

Target(s) of interest: SO will point at an AR, which will be identified, likely, three days in advance of the first observation on October 17th. The same AR is expected to be tracked during the whole duration of required co-observation.
For reference, the SO position on the relevant days is (Ecliptic longitude and latitude distance from Earth in degrees)
2022/10/17: -86.84, 1.38
2022/10/27: -47.55, 6.76

Previous HOPs:
HOPS 432 and 433: SO-PHI/Hinode-SOT cross-calibration data, which are still processed. No paper was yet published.

Additional remarks:
Tracking pointing ON.
Pointing requires special coordination between SO and Hinode teams. The exact pointing coordinates (AR) will be provided about three days in advance of the requested Hinode observation.

HOP list   Monthly Events