Understanding Exposure Times

All JWST detectors integrate using a non-destructive up-the-ramp sampling technique. The exposure time is determined from the users's selection of a Readout Pattern and specification of the number of groups and number of integrations to use.

On this page

See also: MIRI Detector Overview, NIRCam Detector Overview, NIRISS Detector Overview, NIRSpec Detectors

Words in bold are GUI menus/
panels or data software packages; 
bold italics are buttons in GUI
tools or package parameters.

The infrared-sensitive detectors in JWST science instruments operate very differently from the CCDs that many astronomers are familiar with from ground-based work or HST's ACS and WFC3/UVIS. These IR detectors, similar to those in the Spitzer Space Telescope instruments and HST WFC3/IR, are read out using a non-destructive up-the-ramp readout technique that provides a number of advantages.

But arriving at an exposure time is not as simple as requesting a total time. Rather, the exposure time is derived from the selection of a Readout Pattern and specifying 2 other parameters:

  • the number of groups per integration and
  • the number of integrations per exposure.

These are the parameters values that are available in the Exposure Time Calculator (ETC) and the Astronomers Proposal Tool (APT) for specifying exposures. In the ETC, the parameter names are Groups per integration and Integrations per exposure. In the APT, they are Groups/Int and Integrations/Exp.

For NIRSpec, NIRCam, and NIRISS, users will select Readout Patterns from a menu of available options that are optimized for different types of targets. MIRIon the other hand, only provides 2 readout options for science targets. See the instrument-specific detector articles listed above for more information.  

How up-the-ramp readouts work

The following is a generic description of the up-the-ramp readout (sometimes referred to as MULTIACCUM) that is the standardized readout sampling for all JWST detectors. In this readout mode, the array is read out non-destructively at intervals defined by the parameters described below during each exposure. Multiple non-destructive frames can be averaged by the onboard flight software into a group and transferred to the solid state recorder for downlinking to the ground. This can be an effective way to reduce the total data volume that needs to be downlinked and mitigate concerns about saturation.  

Ground-based data processing software can also correct bias drifts using reference pixels, and use up-the-ramp processing algorithms to reject cosmic rays. This approach is quite flexible since it allows for a large range of Readout Patterns. The instrument teams have pre-selected a relatively small set of optimal patterns for use in making observations on orbit.

Figure 1 provides a generic illustration of the components of each up-the- ramp exposure. The user does not choose the number of frames within each group directly, but rather selects various Readout Pattern options that define different numbers of frames per group, different numbers of Groups/Int and different numbers of Integrations/Exp. The specific details available for each instrument and readout mode may differ depending on assumptions regarding use of reset frames (or not), whether a frame is dropped (or not) between groups, and how these frames get used by the data processing software, which may be different between near-IR and mid-IR instruments. Proposers should refer to specific instrument detector pages for more detailed information.

Figure 1. Generic up-the-ramp (MULTIACCUM) readout scheme for each exposure

A generic illustration of the up-the-ramp readout scheme used in some format by all JWST IR detectors. Each exposure consists of some combination of frames, groups, and integrations. The frames are not selected directly, but encoded into the selected Readout Pattern chosen by the user. The mid-IR detectors do not drop any frames. See the individual instrument detector articles for details.

APT limits the total number of frames in any one exposure to 196,608 frames per detector. The total number of frames in an exposure is Integrations/Exp × Groups/Int × frames/group. For NIR detectors, frames/group includes coadded frames, but not dropped frames. For mid-IR detectors, frames/group is 1 for both FASTR1 and SLOWR1 Readout Patterns. Very long time-series observations with a small subarray can encounter this limit. In that case, use multiple exposures to cover the desired time interval.

Choosing parameters

See also: JWST Recommended Observing Strategies

Given the variables in play, there are multiple combinations of parameters that will result in the same reported exposure time. So how does one choose? There are no hard and fast rules to be applied to all cases. However, here are some guidelines to consider. The detailed instrument strategy articles may be helpful for specific cases.

For a given integration time, a larger number of Groups/Int is nominally preferred, primarily to mitigate cosmic rays. (This assuming that saturation is not a concern.) However, each saved frame contributes to the total data volumeso observers may want to consider a readout pattern that reduces Groups/Int while still preserving total integration time.

Adding more Integrations/Exp will also increase the exposure time. Breaking exposures into multiple integrations will be most useful for bright sources that would otherwise saturate in longer integrations. For faint source observations, a larger number of Integrations/Exp and/or simply more exposures may be preferred to achieve a given exposure time.

Finally, recall that it is recommended that most datasets obtained with JWST instruments be dithered. Each selected dither position is a separate exposure, so the total exposure time you will get depends on the number of dither steps. You should note that by default the Exposure Time Calculator is providing information on individual exposures, so you can specify the number of exposures to be the number of dithers expected in order to estimate the impact of multiple dither positions in APT.

Latest updates
    Updated text and use of Bold Italics for consistency with other JDox articles; added warning box for NFRAMES limit.

  • Final minor text modifications for 2020 Cycle 1.

    Revised description with more focus on user experience and additional descriptive material.
Originally published