Since the transition to stable operations under the S-band antenna, typical OP Period durations have been two or three days.
Once solar activity begins to increase, and solar unpredictability increases accordingly, Hinode may consider more frequent (i.e., one-day-long) OP Periods.
To avoid observing during the stabilisation of pointing, EIS observations normally start at least two minutes after a satellite re-point.
To see what an Hinode re-pointing schedule looks like, take a look at an example on the Hinode Daily Operations website here
The duration of night-time is calculated for the visible band, and in the peak of eclipse season (around mid-July [3]) this duration is about 20 minutes. EUV absorption (night ingress) begins about 10 minutes before the calculated entry into optical night (listed as NGT_ENTRY) and ends (night egress) in the EUV about 10 minutes after the optical band exit (NGT_EXIT). Thus, the EIS operations team recommend that you leave a ten-minute buffer around s/c night in eclipse season where possible. Extended-duration observations
At the middle of eclipse season, clear EUV day (i.e., not including transition into or out of eclipse) lasts for approximately 60 minutes (not taking into account expansion of the ionosphere with increased solar activity).
For some more information, see my notes on EclipseEffects.
Additionally, because the SAA rotates with the Earth — whereas the orbit of Hinode does not — the phase of Hinode's orbit at which each SAA event occurs varies.
However, around 12 UT, Hinode experiences a so-called Golden Period where the SAA itself does not intercept the s/c orbit. Because the SAA passes vary in time, the start of this period can range (approximately) from 10 to 11 UT, with the end being anywhere from 14 to 16 UT.
The EIS team use a rule of thumb that a 5-minute buffer around SAA events is sufficient to account for the variability in size of the anomaly itself.
N.B. the old restriction of not changing slit/slot choice during an SAA pass is no longer relevant, following an on-board software update in August 2007
As a result, a some parts of the day, the less-than-complete overlap of SAA and night means that the clear window for observing in such orbits can be shorter. 2009 was the first year for which XTW calcluations were made for Hinode. So taking into account the buffers (summarised below) around orbital events, I recalculated the distribution of clear observing windows from the middle of eclipse season in 2009.
You can see from the histogram below that there are two distinct populations (ignore the very short windows at the far left: these are due to vanishingly small SAA events that occur shortly after larger events).
The main population follows a distribution ranging from 44 to 62 minutes, with a mode and median of around 53 minutes in length. The second population is on the far right, and corresponds to observing windows in the Golden Period where there are no SAAs, and these windows are 65 minutes long.
The sum of all this means that if you want to be of a single raster or study fitting in between eclipses, it needs to be no more than 44 minutes long (the minimum window length). However, if you are happy accepting some curtailment of the raster at one or both ends outside the Golden Period, in order to make full use of those windows that fall inside the Golden Period, then you might design a study to have maximum 65 minutes' duration. It is a gamble, obviously, because they aren't so well suited to the majority of the observing day, and cause difficulties in forecasting the telemetry that will be accumulated because images will be taken when EIS can't see the Sun.
The table below summarises the time buffers recommended to separate observations from the corresponding events.
Event | Buffer |
---|---|
Re-point | 2 minutes after |
SAA_ENTRY | 5 minutes before |
SAA_EXIT | 5 minutes after |
NGT_ENTRY | 10 minutes before |
NGT_EXIT | 10 minutes after |
XTW_ENTRY | 2 minutes before |
XTW_ENTRY | 2 minutes after |
Please note that as of late 2008, the planning tool has a "SHOW OBEV WINDOWS" feature that factors in these buffers (with the exception of the XTW buffer, which we hope will be implemented shortly (2010/05/11).
For the most recent daily allocations, you should visit the Hinode Daily Events webpages, where operations are documented, and check the typical allocation for EIS over the last few weeks. (Remember to halve this number to get a rough idea of the volume you should limit yourself to).
Go over to the Study4LowDataVolume page on this Wiki for examples of programmes recently developed for EIS.
We warmly encourage you to use Hinode in achieving your scientific objectives.
The ISAS Hinode Operations website has a link to a new section on Guidance for Hinode Observations, which is worth reading through in preparation for making a proposal.
For background on the switch from X-band to S-band telemetering of data by Hinode, take a look at the Hinode Science Schedule Co-ordinators' announcement, first released in SolarNews.
Eighteen months of post-commisioning experience has given the Hinode team time to work out the kind of information and lead time that proposers and team personnel need in order to run observations successfully. So now, this information has been made available as ''Guidance for proposal observations (HOP)'' on the ISAS Hinode website.
[2]: Remember, Mb stands for megabits (1024 × 1024 bits), as distinct from MB (for megabytes). 1 MB = 8Mb.
[3]: Is this correct? I know it's approximately true, since we start in late April, and come out of eclipse season in early September.
[]: Hinode's orbital period is 98.5 minutes