An Approach to Survey Operations
A formal proposal is in ops.proposal.html
The elements:For the testbed system of spectroscopy this will take the form of monthly reports on dark runs.
- Create a signed paper trail for each run, chunk, and plate
- Institute a formal data acceptance step
- Develop a consistent response to our mailing list based science reports
The Dark Run Report
The dark run report:
- first, look at the Dark Run Calender to find out the dates of the dark run,
- then turn to the SDSS MJD Calender to find the MJD.
- % setup dp; astrotools;
- astls> surveyAllPlates 19 surveySum.par $spectroRoot
- Next comes the search of the mailing lists: the observing logs are to be read as primary, watching the discussions on sdss-obs, and sdss-spectro. Things to look for are problems noted by the observers, and exposure times for target/science images of less than 900 seconds.
- If problems found:
edit /data/dp9.a/data/spectro/speclog/$mjd/sdHdrFix-$mjd.par run sdReport generation? check into cvs? the factory will pick up the need to re-reduce astls> prepareSpectroReport surveySum.par specReport-Feb 52662 52681 19 Survey Strategy
- Dates: the SDSS Calender, the Dark Run Calender (and see also the observers pages)
- Mailing Lists: the observing logs, the the observation mailing list, and the the spectro mailing list.
- QA data: SOS @ APO, DP @ Fermi QC @ Fermi
- plate database and it's map report
The Mailing Lists
We should have a better rate of reading science reports on the mailing lists. (see the proposal).Other Links
Paper Trails
- Data processing weekly reports
- Mountain top automatic reports for imaging runs
- Data processing reports for Chunks
- Mountain top automatic reports for spectroscopic plate (or at plate-mapper).
- opdb cookbook
Survey Strategy Databases
- Plate mapper database
- MOPDB the MOP database
- PTDB Munn's WWW interface to opdb/ptdb
Other
- The Knowledge Bases
- We need a FAQ
- We will want a community mailing list, with a searchable archive.
James Annis
15 June 2000
Chicago