Next: The following types of
Up: Guidance for proposal observations
Previous: Deadline for submission
The details of proposed observations should be clearly described in
the submitted proposals. The following items should be listed in the
proposal. It is important that all points be clearly addressed to
assist the Hinode Team in making successful observations.
- Title of the proposed observation.
- Short statement describing the observation, and scientific
justification.
- This should be as short and concise as possible, but it should
still contain all the key details. This statement is important
because Hinode's limited data volume situation may make it necessary
to modify some planned observations on some days. The Hinode team
will refer to this statement when setting priorities for which
observations to perform.
- Point of contact. Name and email address.
- Time period of proposed observations, if required.
- Provide the start and end dates with the reason.
- Provide the minimum number of observation days during the
period.
- Provide desires and requirements for continuity of observations,
for example: ``three consecutive days are desired, but not required,''
``three consecutive days are required,'' or ``it is not necessary for
observations to be on consecutive days.''
- Time window in day, if required.
- Provide the ``minimum'' duration with the start and end times in
UT, if it is a coordinated observation with ground-based or
space-based observatories.
- Specify whether any short interruptions (e.g., for ten-minute
synoptics) are allowed over the observing periods.
- Target of interest.
- Clearly specify the target of interest.
- Active region, quiet Sun, on-disk, near limb, limb, polar region, etc.
- More specific description of the target, if required.
- Indicate whether it is a target of opportunity (TOO). If so,
suitably describe the target.
- If a suitable target does not exist during the specified period,
we may not perform the proposed observation during that period.
- Required Hinode instruments and IRIS observations, and priority of observables.
- The Hinode team will take into account the stated priorities
if it is necessary to make adjustments to the proposed
observations to fit in the day's available telemetry, etc.
- Specify which Hinode instruments are really required for the
observation.
- Specify required observables (cadence, FOV vs pixel summation,
wavelengths etc), with priorities, for the primary required Hinode
instrument(s).
- Provide rough estimate of the total data volume to be collected,
if possible. See section 3 for estimating the total data collected.
- If support from non-primary Hinode instrument(s) is also desired,
give a rough idea regarding preferable observables (cadence, FOV vs pixel
summation, wavelengths etc).
- For IHOPs (IRIS/Hinode Operations Plans), specify the
requirements for the IRIS observations, ideally with:
- List of past HOPs in which the present proposer was the PI, and the publications out of those HOPs.
Next: The following types of
Up: Guidance for proposal observations
Previous: Deadline for submission
Hinode Team (ISAS/JAXA)