| Date |
Comments |
OBs | grade
(this run only) |
| 2003-03-21 |
Preparation loss: 3 min: wrong coordinates were set in OB -1672260099. The
time lost was the time needed to preset to these coordinates.
Technical time: 5 min: engineering work was done on the HBS in the
afternoon and the system was still under testing during the
observations. A valve had to be closed due to the low pressure in the
inner axial pads IAX3.1 and 3.2, hence the 5 min of technical time used.
Weather loss: 2h52min due to Clouds. This time also includes the time spent on
the OB executed just before closing and for which no useful data could be
obtained after the loss of the guide star.
Execution loss: 7 min: after restart of observations, a preset was sent too close
to the moon which was located at zenith and the selection of the next OB was
then delayed.
ToO observations for Prog. ID 70.C-0726(A), PI Arpigny, successfully performed early
during first twilight before reaching the telescope limits.
|
135124 | A
135147 | A
135183 | A
135201 | A
135202 | A
|
| 2003-05-05 |
FLAMES (giraffle and uves) were done with all light on in the enclosure (takes >7h to calibrate all)
Unclear to me how to check the quality of pipeline products, from the past night. I can't
read all the science proposal in the given time. Checklist is bad in this case.
Switch to FLAMES at UT 05:30.
Switched back to UVES at UT 06:35 because of technical problems.
|
135207 | A
135208 | A
|
| 2003-05-10 |
Sky conditions for the start of the night were 4THK. However, it soon cleared up above 30 degrees to 2CLR/3THN, hence we switched to 3CLR programmes.
Switching to FLAMES at 6:31 UT once the Moon was below the horizon.
OB number 138579 is logged out of sequence.
|
135122 | A
135123 | A
135125 | A
135176 | A
135182 | A
135185 | A
|
| 2003-05-11 |
UT2 technical tests until 01:50 UT, after which UVES was started up. The seeing was so bad (3-4 arcseconds at the middle-end of the night) that there was no point switching to FLAMES.
UT2 technical time was for TCS testing.
|
135127 | A
135128 | A
135188 | C
135189 | C
135192 | A
135194 | C
135197 | A
135198 | A
|
| 2003-05-12 |
Only UVES was used tonight because the weather was too poor for FLAMES.
For 4THK there is only Napiwotski, hence 3TN programmes were executed instead, and classed 'C' where appropriate.
During some of the time kueyen was closed, we did tests using the FLAMES fiber positioner.
Gap before OB=132554 was caused by an exposure being lost due to a Red FIERRA problem. See PPRS-9634.
Red FIERRA was shutdown and started up at about 05:30 UT.
|
135129 | A
135212 | A
135213 | A
|
| 2003-05-28 |
UVES LOSSES:
The 20 minutes Execution losses are due to:
- 13 minutes lost when trying to skip the PRESET in the second ETA CAR FOS4 esposure. In fact, this also skipped the telescope offset, so
the integration started on the ref. star and had to be aborted.
- Another 7 min were lost due to a wrong acquisition on ETA CAR STAR OB ( a ref. offset star was indicated in the finding chart, but was
in fact not used in the acquisition template)
UVES was also idle (acquisition loss?) 28 minutes just before the
ToO, while trying to point the telescope to such low airmass.
FLAMES LOSSES:
About 10 minutes execution were lost when switching from UVES to FLAMES. We were not sure if a FLAMES configuration could be started while still integrating with UVES.
(Turned out that it could, but we lost time checking in manuals...was
not written anywere).
..
|
135211 | A
|
| 2003-06-02 |
None
|
135189 | A
|
| 2003-06-08 |
FLAMES technical time was taken at the start of the night when the telescope opened at 23:41 in order to try and calibrate the FACBs. However, an increase in the seeing and cloud prevented this from being succesful (could not accurately locate the centers of the fibers so had to ABORT the procedure). Switched to UVES at 00:23.
A few C-class programmes were observed due to the combination of 3THN and the wind coming from the North above the pointing limit.
|
135188 | A
135223 | A
|
| 2003-06-12 |
Full Moon and 3THN precluded FLAMES observations.
|
135132 | A
|
| 2003-06-13 |
None
|
135131 | A
|
| 2003-06-17 |
None
|
135112 | C
135150 | A
135151 | A
|
| 2003-06-21 |
None
|
135199 | A
135210 | A
|
| 2003-06-22 |
OB 140857 logged in twice. The sencond time is the right one.
|
135216 | A
|
| 2003-06-23 |
None
|
135112 | A
|
| 2003-06-24 |
Please note that the gap from 05:51 to 08:22 is due to the fact that OB # 134953 could not be reported due to the BOSS
failure. The FLAMES time statistics will be updated tomorrow
depending on whether the files will be archived.
Update to the NR:
OB ID 134953, bulgeOGLE-fai-HR14-1 for Prog. ID 71.B-0617(A), PI Renzini,
was also successfully executed as the corresponding image that arrived in bits
due to a BOSS failure during the night is now merged and archived.
|
135200 | A
135203 | A
135205 | A
135206 | A
|
| 2003-07-01 |
FLAMES was used from 23:26 to 02:58 and again from 05:02 to 05:32. The switch to UVES was performed in both cases due to a deterioration in the seeing conditions.
|
135153 | A
|
| 2003-07-02 |
FLAMES was used between 23:26-01:36 and from 07:38-09:38. The rest of the time we used UVES.
|
135221 | A
|
| 2003-07-18 |
None
|
135148 | A
135196 | A
|
| 2003-07-26 |
None
|
135113 | A
135157 | A
135159 | A
|
| 2003-07-28 |
In spite of the problem decribed in PPRS-10351, the pipeline products for the 390nm setting (CD#2) looks okay.
|
135154 | A
135158 | A
|
| 2003-07-30 |
Execution downtime updated (now 1h18min) to include the 51min previously classified as
miscellaneous downtime.
|
135163 | A
135170 | A
|
| 2003-07-31 |
Daytime QC0 of today's calibration data seems to indicate that the
problem with the Blue CD#2 (see PPRS 10351) has disappeared.
However, the final QC of both calibration and science data,
especially those obtained with the B437 setting, and the usability of
the daytime FFs, will be provided by Garching. Should it appear that
some of the science data, for which no night-time FFs have been
attached, can not be properly reduced, the execution of the
corresponding OBs will have to be reclassified as "C" (to be
repeated). This includes the nights of 27-28/7 and following.
Weather downtime of 9min due to wind. Telescope open shortly after end of
twilight. First OB execution started at 23h45min UT.
Execution downtime of 9min due to the use of the blue template for attached flat
fields obtained after a Dichroic observation. In this case, Blue and Red images
may not be both saved on disk (possibly depending on the way the template is
edited to change exposure time). Actually, only the Red exposure was saved on
disk last night after the execution of 3 science OBs, namely 136885, 136898 and
137675, whereas only the Blue exposure was really needed.
Note: attached FFs also not taken after science OB 134533, which uses the 437+860
setting.
|
135168 | A
135175 | A
|
| 2003-08-01 |
Daytime calibration products checked.
|
135171 | A
|
| 2003-08-04 |
Daytime calibration checked ok.
CD stability check and Blue ccd tests done.
|
135204 | A
135219 | A
135220 | C
135222 | C
|
| 2003-08-09 |
None
|
135149 | A
135209 | A
135214 | A
|
| 2003-08-10 |
Two minutes of technical time to monitor CD#2.
|
135142 | A
135191 | A
135193 | A
135195 | A
135220 | A
135222 | A
|
| 2003-08-18 |
None
|
135215 | A
135217 | A
|
| 2003-08-30 |
None
|
135165 | A
135174 | A
|
| 2003-08-31 |
Execution downtime (10 min) due to rotator going to standby. The time lost
includes the time to reacquire the moving comet. The Blue and Red exposures
have been paused and successfully restarted afterwards.
|
135152 | A
135218 | A
|
| 2003-09-06 |
Last service night before work begins on M1 cell.
|
135133 | A
135134 | A
135155 | A
|
| 2003-09-19 |
At 1:10 the rotator limit was reached; exposure was paused, but the guide star was lost in the process; lost 0:05
At 2:15 we tried to acquire the Smartt et al. (see PPRS 10793) but did not succeed as FACB stars were well outside fibers. We did not realize this can happen at large airmass
and very blue wavelength settings. Lost 0:54 hours.
At 4:51 we acquired and aborted the visitor OB several times to estimate the correct position angle from the slitviewer image; lost 0:07 hours.
|
135156 | A
|
| 2003-09-20 |
01:45 UT: status of slitviewer CCDs was failed, it took 0:09 to recover. See PPRS 10805
03:36 UT: while still changing focus, the OB was already started. This caused rotator to go into interlock. Lost 0:20; see PPRS 10803. Because of this problem there was no time to perform FLAMES OB; changed focus back to UVES.
|
135114 | A
135130 | A
|
![[ down ]](arrow_down.gif){kind=icon}
![[ up ]](arrow_up.gif){kind=icon}