Observer2's guide to why?¶
Observer2 is close to the data.Observer2 is responsible for
- making sure data quality monitoring tools are operating,
- monitoring data quality and reporting it in the ELog (tag bad image Elog entries with "Summary" tag),
- monitoring sky conditions and reporting it in the ELog,
- filling out the Night Summary and the CTIO Night Report,
- we are always interested in new tools or scripts to assess Data Quality,
- assisting Observer1 as needed.
What observer2 does all night is described in the obs2 setup and obs2 daily checklist.
What we will do here is to motivate the surveillance by the asking of questions.
Things observer2 should be able to answer:¶
- Is the telescope still there?
- be the one that goes upstairs during the dome flats to make sure the flat LEDs are on
- every day take a walk around the telescope: just after sunset is a good time
- Where has obtac taken data tonight?
- run the kentootls pointing
- Are all the CCDs being readout?
- do a kentools bigload and make the ds9 cover 2 screens
- How goes the SN observations: what is the state of the deadman switch?
- look at last night's night summary plot of SN gaps. ( http://des-ops.fnal.gov:8080/nightsum/nightsum.html )
- How does the data taken tonight compare against survey data quality ideals: seeing, whisker length / ellipticity, background cnts/sec?
- watch the strip charts of Quick Reduce (This is the "Observing History button": QR Description)
- compare the DIMM versus DECam FWHM
- Steve Kent Preliminary Quality Assessments (official ones come from DESDM) http://des-ops.fnal.gov:8080/QC/qc.html
- Steve Kent Preliminary Quality Assessments on Tonight's Images( Introduction to godb )
- Are the calibration data ok?
- check one/filter of the flat fields visually for saturation of other weird effects, using kenttools prompt> flatCheck ( Introduction to kentools )
- Is the pointing ok?
- run kenttools center on images, prompt> center, ( Introduction to kentools )
- If the pointing is off by more than 90 arcseconds (except for Standard Stars, which might be at high airmass) inform Telops. Elog it with a "summary" tag.
- Is the seeing ok?
- run kenttools seeingall on images, ( Introduction to kentools )
- What is the weather like?
- The big thing that is missing is paying attention to the sky conditions - clouds and seeing, mostly, but maybe also monitoring moonlight being scattered off of clouds near the pointing of the Blanco, stuff like that. This activity requires getting a sense of what RASICAM is reporting (calibrating with respect to one's own observations of clouds), and being systematic about reporting things. It is quite hard to reconstruct after the fact what the nature, and degree, of cloudiness was like during the night.
- Monitor the Wind Speed and follow the wind blind rules.
- see Windscreens
- What is that beautiful object?
- run kenttools prompt> ned, ( Introduction to kentools )
- Keep it up all night long?
- kenttools prompt> inv; load; center; seeingall ( Introduction to kentools )
- Do the cognoscenti know what is going on?
- comment in the elog, ( ELog Instructions on doc-db )
- Does CTIO know what happened during the night?
- work the draft of the CTIO night report ( CTIO Night Report Instructions)
- Does the world of the DES know what happened during the night?
- work the draft of the night sum ( Night Summary Instructions )
- But there is that nagging issue I want to understand...