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) |
|