REVISED ARC 3.5M SCHEDULE FOR 3RD QUARTER 2002 E. TURNER 6/18/02 NOTES: ***PLEASE READ*** 6/18/02 NOTE - There was a transcription error between my handwritten original of the preliminary 3Q schedule and the ascii version; it is corrected here. The affected programs are NM05, UC02 and UW03 on 7/5-6 and 7/12-13. There are no other changes. Except in cases where strong science drivers dictate otherwise (a minority of cases), observing time has again been scheduled in half night blocks. Scheduled engineering time for this quarter consists of 2 nights of routine maintenance (EN01) or 2.2% of the total available time. A summer shutdown for re-aluminization of the primary, work on the enclosure shutters and many other tasks is scheduled for 46 nights or exactly 50% of the quarter. In addition to scheduled engineering time, science observations may be pre-empted, sometimes on short notice, for urgent engineering tasks. Such tasks include both work that is required to safeguard observatory personnel or facilities and that allows "hot pursuit" of some significant problem. Please see links off of the APO home page (http://www.apo.nmsu.edu/) for a web based interactive version of this schedule. ----- EN Note: No science observations scheduled during EN time. ----- EN01 = EN01 Gill ? O Routine periodic engineering time. EN02 = EN02 Klae NA NA Summer shutdown. ----- DD Note: Director's Discretionary Time (2.2% of total time) ----- DD01 = 023DD01 Wodd FabPer O ----- CU Note: 100% of nominal share scheduled. ----- CU01 = CU01 Elli D O (Blow-Rmedium) CU02 = CU02 Mors E O? CU03 = CU03 Hear S/G O ----- JHU Note: 100% of nominal share scheduled. ----- JH01 = 1 Zhen G/S R I could not understand the implications of the email, forwarded separately from the main request, which indicated the possibile acceptability of time "right before Sep 13", so I ignored it. JH02 = 2 Sonn E R JH03 = 3 Hoop D R (high, medium) Please use the current version of the scheduling form. JH04 = 4 Glaz E O Very short notice (minutes) TOO program which may interupt scheduled programs virtually without warning, if triggererd. ----- NMSU Note: 108% of nominal share scheduled; extra time assigned to NM05. ----- NM01 = NM01 Walt D O (Rhigh) NM02 = NM02 Harr D R (Rhigh, medium) NM03 = NM03 McGe D O (medium, low) NM04 = NM04 Gold S/D O (NA) NM05 = NM05 Moor D R (Blow-Rmedium) ----- PU Note: 108% of nominal share scheduled; extra time assigned to PU02. ----- PU01 = PU01 Pind D R (low) PU02 = PU02 Stra D R (high) PU03 = PU03 Loh S R PU04 = PU04 Turn S O PU05 = PU05 Hall D R (medium) PU06 = PU06 Blak G R? ----- UC Note: 100% of nominal share scheduled. Scheduling arrangements for UC01, UC02 and UC04 are unconventional and somewhat unclear; I have taken my best guess at what you wanted. ----- UC01 = 398 Lamb D/S/E O/R (medium) No time has been explicitly scheduled for this program; I am assuming that up to 4 nights scheduled for UC02 will be used as swap time if UC01 activates its TOO time. That is my best guess at the intention of the TAC which allocated 15+4+4 half nights although the UC allotment was only 19 half nights. It would be best to discuss such unconventional allocations with me in advance so that I can understand the plan more clearly. UC02 = 397 York E/D R (NA) See my notes re UC01. I am assuming that time scheduled for UC02 will be re-allocated to UC04 and, if it activates for a TOO, also UC01. UC03 = 396 Frie D R (setup-1) UC04 = 399 York E/D/G/S R (NA) See my notes re UC01. I am assuming that time scheduled for UC02 will be re-allocated to UC04 at some point. ----- UW Note: 100% of nominal share scheduled. ----- UW01 = UW01 Stub D/S/G O (low) UW02 = UW02 Ande D R (low) Why was this program allocated bright time when it requested dark/grey but UW05 was allocated dark time which does not exist within its schedule constraints? It may be that both programs would benefit from internal UW swaps. UW03 = UW03 Hawl D R (Rmedium) UW04 = UW04 Szko D R (high) UW05 = UW05 Stub D/S/G R (low) Time could not be scheduled as requested at this priority; all its bright time was assigned during Sept 18-26 but not in whole night blocks. Some of its assigned dark time was converted to bright within this interval (which contains no dark time!) and some was assigned earlier in Sept. Why was this program allocated dark time that does not exist within its schedule constraints while UW02 was allocated bright time when it requested dark/grey time? It may be that both programs would benefit from internal UW swaps. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ MOST PROGRAMS ARE SCHEDULED IN HALF NIGHT BLOCKS. THE FIRST HALF OF EACH NIGHT EXTENDS FROM -12 DEGREE EVENING TWILIGHT UNTIL 0100 MDT. THE SECOND HALF FOLLOWS UNTIL -12 DEGREE MORNING TWILIGHT. FIRST HALF IS INDICATED BELOW AS "A"; THE SECOND, AS "B". THIS QUARTER ONE PROGRAM USES NON-BLOCK SCHEDULING. THIS PROGRAM IS INDICATED IN PARENTHESES () ON THE SCHEDULE AND ITS TIME ALLOTMENTS ARE LISTED HERE: PU04 = 40 MIN EACH TIME SCHEDULED. INSTRUMENT CHANGE TIMES ARE NOT INCLUDED BELOW BUT WILL BE INDICATED IN THE SCHEDULE ISSUED FROM APO AND WILL BE SHARED BETWEEN ADJOINING PROGRAMS AS USUAL. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 7/1 A: PU01 B: UC02 7/2 A: PU02 B: UW04/(PU04) 7/3 A: UW04 B: UW04 7/4 A: NM05 B: NM05 7/5 A: NM03 B: NM05/(PU04) 7/6 A: NM03 B: UC02 7/7 A: UC03 B: UC03 7/8 A: UC03 B: UC03/(PU04) 7/9 A: PU05 B: JH03 7/10 A: UW03 B: UW03 7/11 A: PU03 B: NM04/(PU04) 7/12 A: UW03 B: NM04 7/13 A: UW03 B: UC02 7/14 A: PU02 B: UC02/(PU04) 7/15 A: EN02 B: EN02 7/16 A: EN02 B: EN02 7/17 A: EN02 B: EN02 7/18 A: EN02 B: EN02 7/19 A: EN02 B: EN02 7/20 A: EN02 B: EN02 7/21 A: EN02 B: EN02 7/22 A: EN02 B: EN02 7/23 A: EN02 B: EN02 7/24 A: EN02 B: EN02 7/25 A: EN02 B: EN02 7/26 A: EN02 B: EN02 7/27 A: EN02 B: EN02 7/28 A: EN02 B: EN02 7/29 A: EN02 B: EN02 7/30 A: EN02 B: EN02 7/31 A: EN02 B: EN02 8/1 A: EN02 B: EN02 8/2 A: EN02 B: EN02 8/3 A: EN02 B: EN02 8/4 A: EN02 B: EN02 8/5 A: EN02 B: EN02 8/6 A: EN02 B: EN02 8/7 A: EN02 B: EN02 8/8 A: EN02 B: EN02 8/9 A: EN02 B: EN02 8/10 A: EN02 B: EN02 8/11 A: EN02 B: EN02 8/12 A: EN02 B: EN02 8/13 A: EN02 B: EN02 8/14 A: EN02 B: EN02 8/15 A: EN02 B: EN02 8/16 A: EN02 B: EN02 8/17 A: EN02 B: EN02 8/18 A: EN02 B: EN02 8/19 A: EN02 B: EN02 8/20 A: EN02 B: EN02 8/21 A: EN02 B: EN02 8/22 A: EN02 B: EN02 8/23 A: EN02 B: EN02 8/24 A: EN02 B: EN02 8/25 A: EN02 B: EN02 8/26 A: EN02 B: EN02 8/27 A: EN02 B: EN02 8/28 A: EN02 B: EN02 8/29 A: EN02 B: EN02 8/30 A: (PU04)/UC02 B: UC02 8/31 A: UC02 B: UC02 9/1 A: UW05 B: PU03 9/2 A: (PU04)/UW02 B: NM01 9/3 A: UW05 B: JH01 9/4 A: JH01 B: JH01 9/5 A: (PU04)/UW01 B: UW01 9/6 A: UW01 B: NM01 9/7 A: CU01 B: CU01 9/8 A: (PU04)/PU01 B: PU01 9/9 A: UW03 B: UW02 9/10 A: NM04 B: UW02 9/11 A: (PU04)/UC02 B: UC02 9/12 A: UC02 B: UC02 9/13 A: DD01 B: DD01 9/14 A: (PU04)/DD01 B: DD01 9/15 A: PU06 B: PU02 9/16 A: NM02 B: NM02 9/17 A: (PU04)/PU06 B: PU06 9/18 A: EN01 B: EN01 9/19 A: EN01 B: EN01 9/20 A: (PU04)/UW05 B: CU02 9/21 A: UW05 B: CU02 9/22 A: UW05 B: UW02 9/23 A: (PU04)/UW05 B: UW02 9/24 A: JH02 B: JH02 9/25 A: NM04 B: NM04 9/26 A: (PU04)/UW03 B: UW03 9/27 A: UW05 B: UW02 9/28 A: UC02 B: UC02 9/29 A: (PU04)/CU03 B: UW05 9/30 A: UC02 B: CU03 APO APO APO APO APO Apache Point Observatory 3.5m APO APO APO APO APO This is message 588 in the apo35-general archive. You can find APO the archive on http://www.astro.princeton.edu/APO/apo35-general/INDEX.html APO To join/leave the list, send mail to apo35-request@astro.princeton.edu APO To post a message, mail it to apo35-general@astro.princeton.edu APO APO APO APO APO APO APO APO APO APO APO APO APO APO APO APO APO