HOP 59 was run for a continuous 3 day period between 2008 January 22 11 UT to January 25 10 UT. A patch of quiet Sun was tracked during this time with pointing set to be at Sun centre at 0 UT on January 24.
EIS received an enhanced DR allocation of 23%, with SOT reduced to 62%. XRT was normal.
The planning period was affected by the ongoing X band antenna problem that has led to a reduced number of passes during the day. This effectively results in the EIS data rate being approximately half of the usual rate. Because of this, the planned study (QS_diagnostics_HI) could not be scheduled.
Instead the study cam_qs_2as_context was run. This covers a region 120x360 arcsec2 with the 2 arcsec slit in about 32 minutes. The line list covers many useful quiet Sun emission lines.
XRT went into standby mode at the weekend, and it wasn't clear at the meeting if it would remain in standby for this planning period. UPDATE: XRT was switched on again at 0930 on 21 Jan and so it will support HOP 59 fully.
At the daily meeting it was agreed to perform only two XRT synoptics: one at 10:49 and the second at 00:00.
The study cam_qs_2as_context could not be run continuously because of the data rate reduction. Instead it was scheduled every 48 minutes throughout the day. Sometimes a slightly faster cadence of 46 minutes was possible.
Two slot context rasters were performed using the study PRY_slot_context. One at 11:01 UT, and one at 00:02 UT. The latter was obtained while Hinode was repointed to Sun centre for the XRT synoptic. The tracked quiet Sun region will thus be to the solar-east side of the slot context raster.
Only one repointing for the XRT synoptic will be performed, and this at 09:38. Therefore Hinode will track my quiet Sun patch for the whole day after this. The synoptic at 00:00 will be a "drive by" synoptic since the HOP 59 pointing will be at Sun centre at this time.
My aim in planning today was to maintain an approximate cadence of 50mins with the cam_qs_2as_context raster. This was possible until around 05:00, but after this I could only run two more rasters in 5 hours. What I thus did was slip in slot context rasters to maintain the 50min cadence. I used PRY_slot_context (once) and IUU_slot_168x512 (three times).
The passes earlier in the day allowed some additional data to be taken, so I have inserted slot contexts, an engineering study and a SYNOP001 in the gaps between the cam_ qs_2as_context study. Note that the SYNOP001 is performed in the HOP 59 field of view and thus may be useful.
An extra pass was available for today's plan allowing a higher cadence. The initial two passes of the day are large, allowing a high data rate (> 80 kbps) for 3 hours or so. For this reason I scheduled QS_diagnostics_HI (the study originally intended for this HOP) for one repeat at the start of the plan in order to generate a lot of data. For the rest of the day I inserted the cam_qs_2as_context study at regular intervals.
From 12:30 to 23:45 I ran the study at 46 min cadence; from 00:03 to 06:08 at 45 min cadence; and for the rest of the plan at 50 min cadence.
I replaced the raster with a slot context for the last two runs (08:38 and 09:25) to keep the data down.
NOTE: I may change these back to the cam_ study tomorrow and use the initial two big passes to run out the data.
UPDATE: I modified the plan, replacing the slot context rasters at 08:38 and 09:25 with two runs of the cam_qs_2as_context raster. This generated an extra 200 Mb of data, but could be read out the following day.