HET Beginning-Trimester Report
Second Period of 2005
April 1 - July 31

This report is composed of five sections:
Facility Status

In this section we will discuss the status of the HET facility and each instrument and any limitation to configurations that occurred during the period.


Expected Observing Conditions

NOTE: We are now using FWHM which is measured off both the LRS "pre" images and the FIF bent prime guider.

Here is a histogram from the last period.

For comparison here is the image quality for the period last year.

We expect to do about as good as the previous period and year. Note we have changed from a GFWHM on the LRS to a FWHM and we are measuring the FWHM on the ACQ camera using the same software.

We expect to have a similar overhead to last period. The following overhead statistics include slew, setup, readout and refocus between exposures (if there are multiple exposures per visit). In the summary page for each program the average setup time is calculated. The table below gives the average setup time for each instrument PER REQUESTED VISIT AND PER ACTUAL VISIT. The table also gives the average and maximum PROPOSED science exposures and visit lengths.

The "Exposure" is defined by when the CCD opens and closes. A "Visit" is the requested total CCD shutter open time during a track and might be made up of several "Exposures". "Visit" as defined here contains no overhead. To calculate one type of observing efficiency metric one might divide the "Visit" by the sum of "Visit" + "Overhead".

The average overhead per actual visit is the overhead for each acceptable priority 0-3 (not borderline, and with overheads > 4 minutes to avoid 2nd half of exposures with unrealistically low overheads) science target. This number reflects how quickly we can move from object to object on average for each instrument, however, this statistic tends to weight the overhead for programs with large number of targets such as planet search programs.

The average overhead per requested visit is the total charged overhead per requested priority 0-3 visit averaged per program. To get this value we average the average overhead for each program as presented in the program status web pages. The average overhead per visit can be inflated by extra overhead charged for PI mistakes (such as bad finding charts or no targets found at sky detection limits) or for incomplete visits e.g. 2 visits of 1800s are done instead of 1 visit with a CRsplit of 2. The average overhead per visit can be deflated by the 15 minute cap applied to the HRS and MRS. This method tends to weight the overhead to programs with few targets and bad requested visit lengths, ie. very close to the track length.

Instrument Avg Overhead per Actual Visit(min)Avg Overhead per Requested Visit(min) Avg Exposure (sec)Median Exposure (sec)Max Exposure (sec)Avg Visit (sec)Median Visit (sec)Max Visit (sec)
LRS 18.2 (from last period)19.1 (from last period) 595.7 600 1500 1043.26003000
HRS 11.3 (from last period)13.0 (from last period) 825.1 840 3253 1147.59004500
MRS 12.7 (from last period)14.8 (from 2004-1 period) 1248.12100 30001634.118003120

NOTE: AS OF 2003-3 THE SETUP TIME FOR AN ATTEMPTED MRS OR HRS TARGET IS CAPPED AT 15 MINUTES.

NOTE: STARTING IN 2004-3 THE SETUP TIME FOR AN ATTEMPTED LRS TARGET WILL CAPPED AT 20 MINUTES.

The overhead statistics can be shortened by multiple setups (each one counted as a separate visit) while on the same target as is the case for planet search programs. The overhead statistics can be lengthened by having multiple tracks that add up to a single htopx visit as can happen for very long tracks where each attempt might only yield a half visit.

A way to improve the overhead accumulated for programs with long exposure times is to add double the above overhead to the requested visit length and make sure that time is shorter than the actual track length. This avoids the RA having to split requested visits between several different tracks.


Observing Programs Status

The following links give the summary for each institution and its programs. The resulting table will give (for each program) the total number of targets in the queue and the number completed, the CCD shutter open hours, average overhead for that program, and the TAC allocated time. This usually will be the best metric for judging completeness but there are times when a PI will tell us that a target is "done" before the total number of visits is complete.


Institution Status

This is how each institution has allocated its time by priority.

Time Allocation by Institution (hours)
Institution Priority 0 Priority 1 Priority 2Priority 3 Priority 4
PSU 7.000 (5%) 26.200 (19%) 26.320 (19%) 26.210 (19%) 50.000 (37%)
UT 11.000 (5%) 52.500 (24%) 60.500 (27%) 55.500 (25%) 43.000 (19%)
Stanford 0.000 (0%) 11.000 (42%) 5.000 (19%) 5.000 (19%) 5.000(19%)
Munich 0.000 (0%) 5.000 (28%) 7.000 (39%) 2.000 (11%) 4.000 (22%)
Goetting 0.000 (0%) 6.000 (64%) 1.500 (16%) 1.830 (20%) 0.000 (0%)
SALT 0.000 0.000 0.000 0.000 0.000
DDT 0.000 0.000 0.000 0.000 0.000

Stanford and Goetting have under allocated time to their institutional share. Munich put in sufficient hours for this period but we could use more Munich targets to assist in their total deficit.


Future Priorities

The following are the high priority targets for the rest of the period for each institution:

UT05-2
RankProgram Constraints
1 UT05-2-001 MMJ_5330 HRS, EE50 < 2.0, Vsky > 19.0
2 UT05-2-013 J0821+3727 LRS g2, EE50 < 2.0, Vsky > 21.0
3 UT05-2-013 J0919+4356 LRS g2, EE50 < 2.0, Vsky > 21.0

PSU05-2
RankProgramConstraints
1 PSU05-2-015 PG1040+234 MRS, EE50 < 2.2, Vsky > 18.5
2 PSU05-2-015 PG1206+165 MRS, EE50 < 2.2, Vsky > 18.5
3 PSU05-2-012 VIPN-7-10 MRS, EE50 < 2.5, Vsky > 20.2

STA05-2
RankProgramConstraints
1 STA05-2-001 J0833+0350 LRS EE50 < 2.0, Vsky > 20.0
2 STA05-2-001 J0637+3322 LRS EE50 < 2.0, Vsky > 20.0
3 STA05-2-001 J0746+2734 LRS EE50 < 2.0, Vsky > 20.0

M05-2
RankProgramConstraints
1 M05-2-001 NGC3177 LRS e2 EE50 < 2.0, Vsky > 21.3,
2 M05-2-001 NGC4030 LRS e2 EE50 < 2.0, Vsky > 21.3,
3 M05-2-001 NGC5377 LRS e2 EE50 < 2.0, Vsky > 21.3,

G05-2
RankProgramConstraints
1 G05-2-001 NGC4235 LRS G2 EE50 < 4.0, Vsky > 18.0
2 G05-2-003 V396Her LRS G2 EE50 < 4.0, Vsky > 18.0



The following is a histogram of the current HET queue visits for the rest of the period. A line has been drawn at the expected number of hour long visits that we hope to achieve in each hour bin.

The following histogram shows some of the extrema in observing conditions: good seeing dark time, bright time and bad seeing dark time. A line has been drawn at the expected number of hour long visits that we hope to achieve in each hour bin.

The following histogram shows the bright time priority 0-3 contribution from each partner. The dashed line is a rough estimate of the number of hour long visits one could complete during the remainder of the period given each partner's institutional share.

The following histogram shows the dark time priority 0-3 contribution from each partner. The dashed line is a rough estimate of the number of hour long visits one could complete during the remainder of the period given each partner's institutional share.

The following histogram shows the use of LRS_g2 vs. LRS_g3 for priority 0-3 programs in this period.

From the above plots I have determined that:

  • Future IC and Engineering:
    The current plan is to do 5% IC, 10% Engineering and 85% Science during the remainder of this trimester. Much of the engineering will be during bright time. The IC will be for LRS J and will be during dark time.

    TAC Response