v1.0

• Dates : Australian public holidays are indicated as shaded week-days.. Dark, Grey and Bright time is indicated by the 'D/G/B' column.
• NB: Important information for some proposals is given in the footnotes at the base of the schedule.
• ! : Exclamation marks indicate changes from the previous version of the schedule.
• Proposal : Likely observers names are indicated in upper case.
• Support : The initials indicate which member of AAO staff is assigned to support each program

1. If the astronomer's name appears in parentheses then is not expected the astronomer will be present at the telescope, though the astronomer will be responsible for any other support required.
2. If two support astronomers are listed, the FIRST name given is that of the primary support astronomer. The primary support astronomer is the principal contact for all matter relating to this proposal, and is responsible for coordinating the provision of position files etc. The primary support astronomer is responsible for co-ordinating service observing.
3. Support astronomers may be contacted at Email@aaoepp.aao.gov.au, where Email is the e-mail username in the following table:

PATT will not usually pay T&S for proposals from UK astronomers allocated only one night, or UK astronomers allocated time on 2dF. It is therefore assumed that such awards will be carried out in service mode by the nominated support astronomer. If proposers are able to travel to the telescope using other funding, they should inform the relevant support astronomer and the Scheduler (sched@aaoepp.aao.gov.au) as soon as possible.

ATAC programs are required to send at least one, and not more than two, observers for their 2dF runs. PIs should inform the AAO through the usual travel channels of the proposed observers well in advance of their runs.

Such nights are defined by appropriate fraction of the time between evening and morning astronomical twilight.

Standard over-ride conditions (http://www.aao.gov.au/astro/apply/override.html) apply. Extra contitions apply to completing over-rides for observations of the same targets (see below). Further specific conditions include:

A015– 6x1.0 hrs over-ride, with the following conditions:

1. The over-ride can only be invoked for IRIS2.
2. Any single program can be over-ridden for a total of 1x1.0hr (JHK imaging + spectroscopy) per GRB.
3. Stuart Ryder (sdr) to act as contact.

P007– 3 GRBs for a maximum of 2 epochs each, each epoch for 1.5 hr. The following conditions apply:

1. The over-ride can only be invoked for IRIS2.
2. Any single program can be over-ridden for a total of 2x1.5hr (zJHKs imaging) per GRB.
3. Stuart Ryder (sdr) to act as contact.

The following guidelines are intended to resolve contention between two competing over-ride teams attempting to address the same scientific questions with the AAT. The guidelines are careful and detailed because experience shows these situations can be problematic.

1. Both teams are expected to create a web page which will contain critical details that AAO staff will require in order to trigger any override, and to enable the uploading of acquired data (see http://www.mso.anu.edu.au/~joshua/telstat/iris2.php for an example of a web page that could be considered a guide). A program will not be considered eligible to trigger over-rides until its web page has been approved by the Director or his delegate. The planned observations must include all overheads for calibration and acquisition observations - the over-ride program will be charged for all time between when the over-ridden program stops observing, and when it starts observing again after the over-ride.

2. For the current semester both teams have created separate web pages, which have been approved by the Director. They can be found at:

   • ATAC/05B/15 (Rich et al.) http://www.mso.anu.edu.au/~joshua/telstat/iris2.php
   • PATT/05B/07 (Rol et al.) http://www.star.le.ac.uk/~er45/telescopes/aat/

3. An over-ride is considered to be triggered when an AAO astronomer, or AAT night assistant answers the phone at +61-2-6842-6279 and an approved member of the triggering team (named on the over-ride proposal) asks to trigger an over-ride. The requesting team member must, in particular, specify to the AAO astronomer (or AAT night assistant) the event which is responsible for the trigger (to ensure duplicate triggers are avoided).

   If no-one answers the phone, or the phone is engaged, or no member of AAO personnel is available, then the over-ride is not considered triggered. The teams will have to continue calling until AAO personnel are available. In particular, requesting an over-ride of a visiting observer will NOT be considered to have triggered the over-ride.

   Once triggered, an over-ride will be considered to have used all its time, regardless of whether or not the observations can be completed due to weather, the experience of the available observer at the AAT, or uncertainties in how to implement the over-ride program.

   Only one trigger will be considered for each event.

   The AAO astronomer or AAT night assistant will have the final say on the night in determining which trigger has been received first. Appeals may be made to the Director or his delegate. But the Director's decision on such appeals shall be considered final, and no correspondence will be entered into.

4. No observer has to give up more than 3 hours to over-rides in any single run.

5. The over-riding PIs are strongly urged to consider making all over-ridden observers and AAO support astronomers co-authors on papers resulting from over-ride observations.

6. Finally, the AAO reserves the right to impose further conditions if it becomes obvious that they are necessary for the efficient observation of these programs, as our experience with these programs evolves.

Scheduler (26/05/05)