UKIRT shift log comments “Dos and Don’ts”

UKIRT shift log comments “Dos and Don’ts”

Do:

Before sunset:

  • Write a brief comment about weather conditions on arrival, i.e., while it is still bright enough to see cirrus etc. e.g.,
    • “On arrival: weather good, sky clear, light wind from the north and humidity 20%”
    • Add a brief note about the expected conditions.
  • Write a brief comment on the results of the instruments’ array tests. e.g.,
    • “WFCAM readnoise is nominal in all four cameras / readnoise high in camera ?, repeating the measurement”
    • If in a Cass run: “All instruments’ read noise and dark currents nominal / UIST needed a few extra flushes to bring down the dark current”.
  • Include a brief comment on any unusual circumstances for the night, e.g.,
    • “WFCAM first stage temperature is slightly above 82K.”
  • Add a note about the DVS opening status (of 2 or 3 vents) after the darks have been done

After sunset:

  • Please add a shift comment about the opening of the following systems: Dome shutter, mirror covers, moving out the windblind, all DVS.
    • If you happen to open or close these during the night due to changing circumstances (e.g., changing weather, closed while troubleshooting a time consuming fault), add a brief note.
  • Make a shift comment when a project is started stating the reason why this it is being done, e.g.,
    • “Seeing 0.5, starting project X, which is at the top of the queue”,
    • “Project Y is at top of the queue, but moving to project Z as the project-X target is close to the moon / moving to project Z to meet the ?? hr requirement for Z”.
  • If a project forced in for a particular time of the night cannot be observed, add a brief note about it
  • If you’re observing a project or MSBs that are long (e.g. planetary transit), or staying closed due to poor weather, please enter a shift comment every hour or so. e.g.,
    • “Conditions unchanged, continuing with project X”
    • “Closing the dome shutter / DVS as the humidity or wind speed is high” – mention when you open again
  • For projects like the satellite / orbital debris, check the first image of the MSB and add a very short note about the target detection / anything unusual. e.g.,
    • Target detected in camera 3
    • Target very much towards the edge of the array (if it is close to the center, no need to comment)
  • For UHS, log the guide loses as requested in the MSB notes
  • Please mention if the queue is empty and you are doing backup
  • If you reject an MSB, add a short comment with the reason
  • Add a note if the there is a weather change, or if any of the usual tools that help your judgement are not available. e.g.,
    • Thin cirrus coming in …. clouds cleared
    • Skyprobe is not available tonight
  • ompobslog – add a comment against any time gap
  • If there is a significant time-losing fault, please write a very brief note on what is happening, e.g.,
    • “Observations stopped as dome is not moving, we’re on the phone with John Doe in Hilo”.
  • Add a comment if any engineering work is done, e.g., hexapod resets or pointing runs.
  • If you call somebody for assistance, please mention them in a shift comment

End of the night:

  • If you are doing any end of night measurements (or not able to do when scheduled) please mention this briefly, e.g.,
    • “Ending the night with WFCAM twilight flats in ? band”.
    • “Flats’ observations are in the schedule, but skipping due to clouds.”
  • Add a note if any instrument fails to run down properly or you have some trouble while closing and you had to attempt again, e.g.,
    • DVS # / mirror cover failed to close on the first attempt, worked fine on the second attempt
    • If the problem needs more attention, file a fault / send a note to the support astronomer as needed. If the situation is unsafe, please call the support astronomer
  • Please state that all systems have been properly closed/parked/run down, e.g.,
    • (telescope parked / at the zenith for any non-standard reason); dome shutter, mirror cover, dvs closed
    • WFCAM end night done and run down
    • Do ompmsbcheck and mention it in the log.

Don’ts:

Before sunset:

  • There is no need to cut and paste, or give detailed numbers for array tests as these are all logged. Just mention if things are OK or not. (If something is outside spec, please give numbers)

After sunset:

  • TSS and support scientists: Do not use shift comments for filing or responding to faults. It’s fine to mention that a fault occurred or is occurring but details of the fault should go in the fault system and not in the night log.
  • No need to write all the seeing or focus measurements. The occasional seeing report is useful, especially when changing projects. If you notice any major changes in any, add a brief note.