Colorado ARC Proposal Instructions

This information is based on information contained in message #321 in the apo35-general archive .

• DESCRIPTIVE TITLE: (but not extremely long)

• PI: one PI only, this name will appear on the 3.5m schedule; if the PI is not a member of the faculty or senior research staff, please also indicate who is sponsoring the proposal

• OBSERVER(S): additional observers; it is assumed that the PI will also participate in the observations unless it is explicitly indicated otherwise

• UNCERTIFIED/UNTRAINED OBSERVERS: remote observers who are not certified for remote operations or on-site observers in need of training/supervision should be listed here, along with plans for satisfying the 3.5m policy described in apo35-general message #219 and in the Guide Lines

• COLLABORATORS: additional scientific collaborators; it is assumed that the PI and the observers listed will also be scientific collaborators unless explicitly indicated

• CONTACT INFORMATION: Email address(es) and phone number(s) of at least the PI and principal observers; this information will be used, for example, if last minute technical problems or questions arise at the site.

• HALF NIGHTS: Please use units of half nights. Also please indicate whether you need dark, grey or bright time or some combination. Do *not* put any other information in this item, such as how you want the time broken up into different nights, what part of the night you want, etc.

• INSTRUMENT: J Just say which instrument(s); no details of internal instrument modes or why you need a particular instrument are needed here

• DIS GRATINGS: indicate which two, of the available three, pairs of DIS gratings you will want to use; low, medium and high dispersion are available; if you only need one pair, specify only it.

• OBSERVING MODE: This does *not* mean instrument mode; it means "remote" or "on-site" or "training" again with no particular justification needed. do keep in mind that you should have "on-site" experience, preferably with the instrument in question, before you can use it remotely. "training" means going to the site with an experienced observer/user.

• OBSERVING SCHEDULE CONSTRAINTS: This is the place to indicate how you need the time scheduled for astronomical or scientific reasons. the most obvious such constraint is that the target object(s) should be well placed in the sky but many others are also possible. please state BOTH the reasons for the restrictions AND explicitly list those dates/times which will satisfy them. preferred, acceptable and unusable dates/times would be useful. in other words, please do not leave it as an exercise for the scheduler to determine, say, what dates/times have M31 at least 45 deg above the horizon for a minimum of 3 hours during dark or grey time at either the beginning or end of the night, and also please do not leave the scheduler guessing why you need to, say, observe Jupiter on either October 7-11 or November 10-12. in addition, please make sure that what you request is physically possible; for example, don't request dark hours and then specify dates/times which are bright. in order to expedite the cumbersome chore of scheduling, inconsistent requests MAY simply be dropped without further consultation or recourse. also, if you have an explicit scientific reason to prefer whole or split nights, note it under this item. *at minimum* you should give the coordinates or coordinate ranges of your targets here and indicate which nights and times you consider optimal, even if "any time" will do. in many requests, this will be the longest and most complex entry. if you request observing times in blocks smaller than hours, please give the explanation in this section.

• SPECIAL REQUIREMENTS: this is the place to indicate scheduling constraints which are not directly related to the sky or the science to be done, e.g., "i will be out of the country nov 1-12", "not on Tuesday nights due to early wed am lectures", or "hot date next sat night". any other sorts of special needs, such as housing on site for a large observing group or use of your own instrument would also go under this item.

• SPECIAL PROTECTION JUSTIFICATION: please list any special reasons (e.g., a time critical occultation, last data needed to finish a thesis) that the program should be protected from unscheduled closures (for engineering or other purposes) when possible.

• BRIEF SCIENCE JUSTIFICATION: this will be used to help schedulers understand why you need what you request and to help those working at the site to better understand your requirements. Two or three hundred words should be plenty for any but the most complex programs. distribution of these forms to each ARC institution also allows your colleagues elsewhere to see what you are up to.

• PUBLICATIONS BASED ON APO 3.5m DATA: List all publications during the past three years which were based in significant part on data obtained with the 3.5m telescope. submitted and "in press" papers may be included, but please do not list papers "in preparation".