IRIS30day
Back to current versionRestore this version

Coordinating EIS and IRIS observations#

WARNING: this is a discussion page for presenting provisional Hinode/EIS plans to coordinate with the IRIS initial 30 day science plan. All details given here are subject to change.

When to coordinate#

IRIS prepares one day plans on Monday to Thursday, and a 3 day plan on Friday. On each day the plan needs to be ready by 12:00 (local Pacific time), i.e., 20:00 UT in winter and 19:00 UT in summer. The plan will start at approximately 4 UT.

Specific timing details for the three Hinode Operation Periods (OPs) are discussed below. Key observing periods are highlighted, and represent those periods when both IRIS and Hinode can have reasonably "fresh" pointings. At other times IRIS would have to use "stale" Hinode pointings that may not be ideal.

Hinode OP1#

Key observing period: 11 UT Saturday to 4 UT Tuesday (65 hours).

The IRIS plan will start at 4 UT (Saturday) and the EIS plan will start around 11 UT (Saturday). The draft EIS plan will be made between 01:30 UT (Friday) and 01:30 UT (Saturday). The IRIS plan will be completed by 20:00 UT on Friday. The EIS plan will be finalized after 01:30 UT (Saturday).

Suggestion: IRIS sends provisional plan details to Hinode on Thursday. This feeds into the Hinode draft plan. IRIS then sends final plan details which then lead to pointing and timing changes to the Hinode final plan. IRIS should not make large changes between the provisional plan and final plan.

Note that between 4 UT and 11 UT on Tuesday coordination seems unnecessary so IRIS should run their own studies.

Hinode OP2#

Key observing period: 11 UT Tuesday to 4 UT Wednesday (17 hours).

The IRIS plan will start at 4 UT (Tuesday) and the EIS plan will start around 11 UT (Tuesday). The draft EIS plan will be made between 01:30 UT (Monday) and 01:30 UT (Tuesday). The IRIS plan will be completed by 20:00 UT on Monday. The EIS plan will be finalized after 01:30 UT (Tuesday).

Suggestion: IRIS sends provisional plan details for Tuesday and Wednesday to Hinode on Sunday. This feeds into the Hinode draft plan. IRIS then sends final plan details for Tuesday only at 20 UT (Monday) which then lead to pointing and timing changes to the Hinode final plan. IRIS should not make large changes between the provisional plan and final plan.

Hinode OP3#

Key observing period: 11 UT Thursday to 4 UT Friday (17 hours).

The IRIS plan will start at 4 UT (Thursday) and the EIS plan will start around 11 UT (Thursday). The draft EIS plan will be made between 01:30 UT (Wednesday) and 01:30 UT (Thursday). The IRIS plan will be completed by 20:00 UT on Wednesday. The EIS plan will be finalized after 01:30 UT (Tuesday).

Suggestion: IRIS sends provisional plan details for Thursday and Friday to Hinode on Wednesday. This feeds into the Hinode draft plan. IRIS then sends final plan details for Thursday at 20 UT (Wednesday) which then lead to pointing and timing changes to the Hinode final plan. IRIS should not make large changes between the provisional plan and final plan.

Pointing and raster considerations#

Many IRIS rasters will generally be very small (20" x 60" and smaller) and very quick (less than a minute). There is a fundamental uncertainty in the EIS absolute pointing of about 10" in X. This means that EIS rasters should generally have a minimum width of 30" (allowing some contingency). If EIS is in sit-and-stare mode, then IRIS should have a width of at least 30".

IRIS has one slit with width 0.33". Large rasters (>10") will generally have large step sizes (1" or larger).

IRIS slitjaw images will be in C II, Si IV and Mg II. There may be possibilities to align these with He II 256 slot images. Generally IRIS will align with AIA 1600 using the slitjaw images.

The IRIS 30 day plan#

The 30 day plan generally consists of blocks of several hours with the same pointing. Most of these blocks will be repeated several times during the 30 day period. Within the block IRIS will do several different observation types that last 1 hour (e.g., sit-and-stare followed by rasters). For the convenience of EIS planning, EIS should probably just repeat a single raster for the whole block with slot context rasters appended at the start and end.

I have labeled the blocks with codes such as "AR1" and "QS1" but these are not used by the IRIS team.

The EIS priority indicates the likely importance of having coordinated EIS data for the IRIS study. Since EIS will not be able to support IRIS 24 hours/day, then the EIS CO should give preference to studies with priority 1.

AR1 - active region tracking - 7 hours#

EIS priority: 1

IRIS: large raster plus a number of plage studies (each with the same pointing?).

EIS: HPW021_VEL_240x512v1, repeats of IUU_SCAN_STEPS_002

AR2 - sunspot observations - 3.5 hours#

EIS priority: 2

IRIS: sit-and-stare; deep raster.

EIS: tbd.

AR3 - active region tracking (short) - 2.25 hours#

EIS priority: 2

IRIS: large raster plus plage study.

AR4 - active region fan loops - 3.5 hours#

EIS priority: 1

IRIS: deep raster; sit-and-stare

EIS: IUU_SCAN_STEPS_002

QS1 - generic quiet Sun study - 6 hours#

EIS priority: 1

IRIS: large rasters, sit-and-stare, small rasters

EIS: medium size raster?

QS2 - limb quiet Sun study - 4 hours#

EIS priority: 2

IRIS: deep raster, small rasters, sit-and-stare

EIS:

CH1 - coronal hole - 5.5 hours#

EIS priority: 1

PR1 - prominence - 5.5 hours#

EIS priority: 2

PR2 - filament - #