You are in: Instruments > T-ReCS > Performance and Use > Observing Strategies    

T-ReCS Observing Strategies

Introduction

In addition to computing required integration times, a proposal writer should consider other details of an observation related to the telescope and instrument. For T-ReCS, the principal concerns are the relatively small field of view, the need to chop and nod, and the restricted chopping amplitude. A secondary concern is astrometric accuracy.

A high-quality observation may also require supporting data for photometric calibration, point-spread function characterization, and so forth. Ideally, every type of calibration would be available for each science observation. This is difficult in practice because of the significant telescope time required to take all possible data, but thankfully only certain calibrations are usually needed to obtain a specific scientific result. For example, while a program to measure the spectral energy distribution of bright circumstellar disk star may require careful photometric calibrations and airmass corrections to obtain high accuracy, a program to image an extremely faint high-redshift galaxy with expected S/N < 10 would probably not benefit from such an accurate calibration: most of the available telescope time is best spent integrating on the science target. In order to use telescope time most efficiently, observing programs should contain only those calibrations that are needed to achieve the desired science.

On this page we describe the principal observing and calibration issues that users of T-ReCS should consider when planning their programs and writing their proposals. We recommend that proposers weigh the importance of each issue to their program's scientific goals and formulate their observing plans accordingly. Phase I proposals should briefly outline the observing plan and necessary special calibrations in order to justify the program's feasibility and the observing time request. Phase II programs should contain complete details on the observing sequences, including any special calibrations.

For each issue, we briefly describe two cases for which the priority of the issue is "Low" and "High". Assigning a "Low" priority to a certain issue typically means that no special procedures are required or that baseline calibrations are acceptable. A "High" priority indicates that the issue needs careful attention and perhaps special observations. (Of course, the issues will likely have intermediate levels of priority for many programs.) We often give a specific example, and briefly discuss what information on each issue should be included in the Phase I and Phase II proposals.

Note that these "Low" and "High" priority labels are not reflected in the OT but are guidelines for creating either Phase I or Phase II files. One cannot simply ask for "High" quality astrometry (for example) and leave the details to the astronomer doing the observations at the telescope. If one wants more attention paid to a particular aspect of the calibrations one has to setup the associated observations in the phase II file and allow time for this in ones program.

It is also useful to provide details in NOTES in any phase II file to guide the astronomer who will be carrying out the queue observations. In general more detail of what is wanted and how the observations should be carried out is better. Another point to remember is that in queue observing it is unlikely that a long series of observations will be carried out in any particular order, unless one has a band 1 program. Particularly for band 3  programs it is very unlikely that all targets will be observed at optimum airmass or that all the observations of a given target will be done at once unless the observations are quite brief. One needs to keep these possibilities in mind when creating a phase II file.

Following the individual issues, we present observing strategies for several example science programs. For each program we rank the priority of each observing issue and discuss a specific strategy to make the best use of telescope time to meet the important science goals. We feel that many programs can be developed based on these examples; if your program does not seem to fit one of the examples, then perhaps Gemini staff should be contacted for advice.

Observing Issues:


Example Observing Strategies

  1. Simple Imaging
    The Simple Imaging strategy is suitable for quick snapshots of a large number of targets, or of a few targets in many filters, when the science goal is to determine approximate source positions, fluxes, and morphologies. In this case the photometric and PSF calibrations can be derived from the Baseline calibrations, the flat fields if needed can be taken from a library, and astrometry can be derived from the approximate (1") WCS in the FITS header and by registering the images with radio or NIR data.

  2. Mosaics
    This is similar to Simple Imaging, except that the field is larger than the T-ReCS detector. In this case the position of each sub-field must be specified, with due consideration of the desired overlap. The chopping limitation of about 15" must also be considered; it is generally difficult to make mosaics of large objects because one cannot chop entirely off-source.

  3. Deep Imaging of faint targets Faint targets require long integration times with minimal interruptions. If the final S/N is < 50 accurate flat fields are not a priority. If better than baseline calibration is required, special calibrations should be requested. In addition, the astrometry can be well determined by using a USER 1 star.

  4. High angular resolution imaging
    In this case the photometric accuracy and astrometry requirements are low because the star's total flux and position are already well known. The PSF characterization is critical because the goal is to separate faint disk emission from the bright, point-like stellar photosphere.The optimal integration times and number of cycles are dependent on the system stability and target brightness. One should go no longer than about 30 minutes between PSF observations if the highest accuracy is required.

    Note that the best PSF accuracy requires rather large overheads which are charged to the program since they are in excess of standard baseline calibrations.



[Science Operations home] [T-ReCS home]


Last update 2006 March 13; James Radomski