| Space Telescope Science Institute |
| HST Call for Proposals and Primer |
| help@stsci.edu |
A GO proposal may be submitted for any amount of HST observing time, counted in terms of HST orbits. Chapter 6 of the HST Primer describes how the required number of orbits can be calculated for a particular set of observations. A new system of Small, Medium, and Large Program categories is being introduced this Cycle. Small Programs are those requesting up to 34 orbits (Section 3.2.1). Medium Programs are those requesting between 35 and 74 orbits (Section 3.2.2). Large Programs are those requesting 75 orbits or more (Section 3.2.3). Programs in each of these categories can request observing time in future cycles when this is scientifically justified (Section 3.2.5). The additional category of Treasury Programs (Section 3.2.6) is designed to stimulate certain types of ambitious and innovative proposals that may not naturally fit in the Small, Medium, or Large Program categories.
3.2.1 Small GO ProgramsSmall GO Programs are those that request between 1 and 34 orbits.3.2.2 Medium GO ProgramsMedium GO Programs are those that request between 35 and 74 orbits.3.2.3 Large GO ProgramsLarge GO Programs are those that request 75 orbits or more.Proposers submitting Large Programs should consult the Large Program Scheduling User Information Report linked from the HST Documents page and the HST Orbital Viewing and Schedulability page. These documents contain necessary information for developing a Large Program that is feasible with respect to HST orbit scheduling. Investigators proposing Large Programs must select the Large Program flag on the cover page, use a visibility that enhances schedulability, and include additional technical detail in the "Description of Observations" section to provide information on the scheduling aspects of their program. The shorter visibility period will be enforced in Phase II for each approved GO program that is awarded 75 orbits or more in a single cycle.Following the recommendations of the Space Telescope Users Committee, data taken for all Large Programs will have no proprietary period as a default. Proposers may request a proprietary period, and that request should be justified in the "Special Requirements" section of the proposal (see Section 9.3). Such a request will be subject to review by the TAC.In Cycle 21, 1000 orbits are available to new Large and Treasury Programs, and we anticipate the selection of four to eight Large Programs. For comparison, in Cycle 20 seven Large Programs were accepted for a total of 736 primary orbits; in Cycle 19 five were accepted for a total of 676 primary orbits. Descriptions of these programs are available on the Treasury, Archival Legacy and Large (TALL) Programs Webpage. Most Large Programs accepted in previous cycles were allocated between 110 and 150 orbits; that range may change in this Cycle given the newly introduced minimum size of 75 orbits for the Large Program category.3.2.4 Calibration GO ProgramsHST is a complex observatory, with many possible combinations of observing modes and spectral elements on each instrument. Calibrations and calibration software are maintained by STScI for the most important and most used configurations. However, STScI does not have the resources to calibrate fully all potential capabilities of all instruments. On the other hand, the astronomical community has expressed interest in receiving support to perform calibrations for certain uncalibrated or poorly calibrated modes, or to develop specialized software for certain HST calibration and data reduction tasks. In recognition of this, STScI is encouraging outside users to submit proposals in the category of Calibration Programs, which aims at filling in some of the gaps in our coverage of the calibration of HST and its instruments.
Users submitting Calibration Proposals must contact the appropriate instrument group to discuss their program prior to submission.
A specific science program that has special calibration requirements is not a Calibration Proposal; such a proposal should be submitted as a normal GO proposal and the necessary calibration observations should be added to the science program as described in Section 4.3.For a complete description of the instrument calibration plans/accuracies, and for other potential topics, please see the Scientific Instruments Webpage.The data obtained for a GO Calibration Proposal will nominally be non-proprietary, as is the case for regular calibration observations. Proposers may request a proprietary period (which should be explained in the ‘Special Requirements’ section of the proposal; see Section 9.3), but such a request will be subject to panel- and TAC review and will be granted only in exceptional circumstances if exceedingly well justified. Calibration Proposals can also be submitted as Snapshot Programs (see Section 3.3.2) or Archive Programs (see Section 3.4.3). Archival Research proposals are appropriate in cases where the necessary data have already been taken, or for programs that do not require specific data but aim to develop specialized software for certain HST calibration and data reduction tasks.
3.2.5 Long-Term GO Programs
You may request time in up to three observing cycles (21, 22, and 23). Long-Term Proposals should describe the entire requested program and provide a cycle-by-cycle breakdown of the number of orbits requested. The Cycle 21 review panels and TAC will only be able to award a limited amount of time in future cycles, so a scientific justification for allocating time beyond Cycle 21 must be presented in detail. Scheduling concerns are not a sufficient justification. The sum of all orbits requested in Cycles 21, 22, and 23 determines whether a Long-Term Program is Small, Medium, or Large. Target of Opportunity Programs are eligible to be Long-Term Programs if certain conditions are met (see Section 4.1.2).3.2.6 Treasury GO Programs
• Data taken under the Treasury Program will usually have no proprietary period (see Section 5.1), although brief proprietary periods may be requested if that will enhance the public data value.
• The emphasis in Cycle 21 remains on observations whose value is maximal if taken soon. However, Treasury Programs may request observing time to be distributed in future cycles if scientifically required (similar to the situation for Small, Medium, and Large Long-Term GO Programs; see Section 3.2.5). In this cycle approximately 1000 orbits of HST time will be available for new Large and Treasury Programs. For reference, one Treasury Program was accepted in Cycle 20 and one was accepted in Cycle 19. Descriptions of all Treasury Programs are also available on the HST Treasury, Archival Legacy and Large Programs Webpage.Selection of Treasury Programs will be handled by the TAC as part of the normal peer review process (see Section 6.1.2). Successful proposals will be reviewed by STScI to ensure observing efficiency. STScI resources may be made available to approved Treasury Programs by decision of the STScI Director. In particular, some programs require substantial pipeline processing of their data to generate the final products. Examples are large mosaics for surveys, or co-additions of many exposures in deep fields.Investigators proposing Treasury Programs must select the Treasury Program flag on the cover page, use a visibility that enhances schedulability, and include additional technical details in the “Description of the Observations” section to provide information on the scheduling aspects of their program. Note that a program can be both Large and Treasury, in which case both flags should be set. Proposers submitting Treasury Programs which are also Large Programs should consult the Large Program User Information Report, which can be found on the HST Documents webpage (linked from the Cycle 21 Announcement Page). This document contains a discussion of the issues surrounding Large Program scheduling.
The ‘Scientific Justification’ section of the proposal (see Section 9.1) should include a description of the scientific investigations that will be enabled by the final data products, and their importance. The ‘Description of the Observations’ section of the proposal (see Section 9.2) should not only describe the proposed observations and plans for data analysis, but should also describe the data products that will be made available to STScI and the community, the method of dissemination, and a realistic time line.