Once you have created a set of Observation Template files ("obs files") for all of your program targets, you use the Phase II Submission Form to submit them to the YALO queue for implementation along with a set of detailed instructions for how to execute your observing program.
You should submit one observing program form for all targets that are ready to be implemented for your project. This is meant to keep things simple. If you submit many separate files, it gets complicated and your program could be delayed while we sort things out.
A Phase II program submission consists of two parts:
The Phase II Submission Form requests the following information:
Examples of program instructions are given below.
If any old or defunct obs files appear in this list, you might want to take a moment when your submission is complete and clean up your project's obs file directory using the Obs File Manager Form provided among the observing preparation tools.
The astronomer who creates the obs files and submits the Phase II observing program is responsible for providing valid target names and celestial coordinates. They are also responsible for providing ephemerides for solar system targets that are not already in the telescope control computer system (i.e., ephemerides major planets are pre-loaded into the telescope controller, minor planets and comets are not). Neither the queue manager nor the on-site observers will enter, validate or correct target names or coordinates. Although if there are problems with your coordinates, the queue manager will be in touch.
This is a set of instructions for a program to observe 47 Tucanae using the dual CCD/IR mode of ANDICAM. For this project, 5 obs files have been prepared (named tucik, tucvk, tucbh, tucuk, and tucuh).
Instructions are as follows: 1) Go to coords given and execute tucik tucvk tucbh The object title here should be 47Tuc #1 2) If the moon is down AND the seeing is <2.0" execute tucuk tucuh Object title 47 Tuc #1 3) offset dec +00:04:00 and repeat the above two steps with the object title 47 Tuc #2 4) If u-band images are obtained, we will need sky flats. If they haven't been obtained at the beginning of the night, we will need them at the end. Probably wise to check if the moon will be down at the end of the night in advance, so we know if we won't need them.Example 2:
This is an observing program adding 2 new targets to the OSU Microlensing followup program (these are fictitious additions):
Add two targets to our observing list as follows: MB99007 - RA=12:13:14.5 DEC=-22:33:44 (2000.0) obs file: mb99007ih, dual IR/CCD images MB99007 is a high-amplification microlensing event approaching peak brightness during the next 2 weeks. It should be observed with high priority at least once per hour until further notice. Current brightness is V=14, I=13. A finder chart is on anonymous ftp at ftp.astronomy.ohio-state.edu/pub/stuff/mb99007i.gif MB99008 - RA=13:14:15.6 DEC=-33:44:55 (2000.0) obs file: mb99008ih - dual IR/CCD imaging at I andH Long-timescale event, should be monitored at least once a night. Do not observe if there is heavy cirrus or seeing worse than 2", as the field is crowded and the target is faint (currently V=19). A finder chart is on anonymous ftp at: ftp.astronomy.ohio-state.edu/pub/stuff/mb99008i.gifIn this example, the astronomer has provided GIF finding charts at the URL given. In this form, the observers can use Netscape on the data-taking computer to download and display the finding charts by entering the URL:
ftp://ftp.astronomy.ohio-state.edu/pub/stuff/mb99007i.gifThis feature of the web can make it easy for you to provide finders to the on-site observers using your own ftp or web servers as appropriate.