Guidelines for Preparing Keck Proposals
Based on recommendations of the UCO Advisory Committee and TACs.
[Format: 12 point font; single-spaced; one-inch margins]
1.0 Scientific Justification
Attach a clear, up-to-date discussion of the scientiﬁc goals of the proposed observations, including what new science will be learned, its overall astrophysical signiﬁcance, and how it relates to past work in the ﬁeld. Prose text should be limited to two pages, with up to two additional pages for ﬁgures and references. Up to one additional page describing progress on this project to date (including existing and planned publications) should be included if this is a resubmission. The TAC is instructed not to read any proposal text beyond these page limits.
2.0 Technical Remarks (2 pages max)
Include the following subsections:
2.1 Targets and Exposures:
Specify targets or ﬁelds and their coordinates, magnitudes (if known), exposure times, justiﬁcation for lunar phase, and justification for number of requested nights.
2.2 Backup Program:
Provide a short abstract of backup program(s) for poor observing conditions.
2.3 Supplementary Observations:
If supplementary observations from other observatories (including Lick or space) are needed, please describe. Specify how essential are the other data for completion of program. Make clear the role of non-UC collaborators and list any of their time at other observatories that may be part of this project.
2.4 Status of Previously Approved Keck Programs:
Review status of previously approved programs (not including the current project), including Title, PI, number of allocated nights, status of data and analysis, and publications to date. For papers in preparation, list an estimated time to publication. Do not go back more than five years.
3.0 Optional, but highly recommended, subsections
(2 pages max)
3.1 Path to Science from Observations:
Explain brieﬂy the path from observations to science, including plans for how the data will be taken, reduced, analyzed, and written up for publication. Include a brief description of who will be responsible for which tasks. If theoretical models or other data are needed, specify how these will be acquired.
3.2 Technical Concerns:
When appropriate, specify technical concerns or problems and provide sufficient information on how they will be addressed to enable the TAC to evaluate the feasibility of the project.
3.3 Experience and Publications:
Brief account of the experience of the proposer(s) with instrument and science. Provide no more than a one page list of publications relevant to this proposal that the PI has been involved with. Mark those using Keck or Lick data with an asterisk (*).
3.4 Resources and Publication Timescale:
Please describe what resources (such as computing, personnel, and grant funds) will be applied to this project. What is the expected timescale for publications? Be as specific as possible regarding topics for planned papers.
3.5. Service to UCO (new since 2017B):
The UCO Advisory Committee has requested that the following brief section be included:
Please describe any activities you have carried out in the service of UCO within the last two years e.g. enabling new or upgraded instrumentation, technology development, software development, committee service, fundraising, conference organization, public outreach, etc.