APT Targets

JWST observing proposals must specify the proposed targets (and as appropriate, coordinates) in the Astronomer's Proposal Tool. Allowed types are: fixed targets, Solar System (moving) targets, or generic targets that have unknown coordinates at the time of the proposal. A special case called "target groups" is also available.

On this page

An astronomical target for JWST refers to any position on the celestial sphere at which the telescope needs to point. The target may be a physical object, a portion of an object, a background region, or even an unknown target at the time of proposal writing.

The Astronomer's Proposal Tool accepts 3 primary types of targets:

  • Fixed targets, typically associated with known astronomical objects outside the Solar System whose positions can be defined by specific celestial coordinates;
  • Solar System targets (also known as moving targets);
  • Generic targets, typically used for target of opportunity observations or pure parallel proposals where specific targets are not known at the time of the proposal submission.

Additionally, APT has the ability to ingest a catalog of targets from an appropriately formatted ASCII file.

The links above take you to proposal parameter articles on each target type; these articles contain technical details and legal values for many of the parameters listed in the APT target entry section.

A special use case called Target Groups may be useful for users proposing closely spaced targets that need to be observed with very similar observation specifications. (For cycle 1, the allowed templates include MIRI LRS, MIRI MRS, NIRSpec fixed slits, and NIRSpec IFU.)

Due by the single stream approach for JWST proposing, most proposers are required to submit a full list of targets with coordinates in order to accurately compute the total time allocation request.  Exceptions to this rule may be described in JWST Opportunities and Policies for each cycle; such exceptions may include targets of opportunity and NIRSpec multi-object spectroscopy proposals, where it is impossible to know all relevant details at the time of initial proposal submission. 



Fixed targets

See also: proposal parameters article on valid specifications for Fixed Targets.

Fixed targets may be entered in APT by hand (including the coordinates), found using the Fixed Target Resolver tool, or imported as a formatted ASCII table. Select Targets in the tree editor (in the left column), as shown in Figure 1. The active GUI window on the right displays the options for entering targets.

Figure 1. Target entry menu in APT

The target entry GUI contains options for entering a new fixed target, Solar System target, or generic target. For fixed targets, you can enter them manually by selecting New Fixed Target, use the Fixed Target Resolver tool to search for your targets, and Import Targets to load a list of targets from a file. There is also a special use case called New Target Group that will be discussed further below in this article.
The Fixed Target Resolver tool opens a separate window where you can select a catalog(s) to search for your target, specify a search method, and enter search values based on the search method you specified. A simple example is shown in Figure 2. If more than one catalog entry is returned, you can select the target of interest. If you commit a target from this search to your proposal, a note is automatically generated in the Comments section of the target GUI. (This comment can be edited by the proposer, if desired.)
Figure 2. The Fixed Target Resolver tool GUI

APT's Fixed Target Resolver tool is run in a separate pop-up window. Entering a resolvable target name (e.g., "SS Cyg" in this example) and selecting Search returns the coordinates from one of several  catalog services (SIMBAD by default, but one or more catalogs can be selected). If a list of targets is returned, select one of the entries and click Select Object as Target to commit that object as a new target in the proposal.

Importing from a bulk target list

See also: JWST Bulk Target Ingest

In the APT Targets form, users can upload a file containing a list of fixed targets into a proposal. Allowed file formats include comma-separated, tab-separated, and whitespace delimited values, as well as a Virtual Observatory format table. Additional details are available in JWST Bulk Target Ingest.

If you update your targets after ingesting the target list, you can also export your APT targets to a list. In the APT main menu, go to File  →  Export →  Export Fixed Target list. Please note that APT exports all coordinate uncertainties in arcsec, regardless of the units set in APT, and only supports the CSV output format.

Fixed target form GUI

Each target is described in its own form, listed under Fixed Targets in the tree editor. Each fixed target form has a number of parameters—some are required but many are optional, depending on your use case. 

Required parameters:

  • Number: Each target in APT is assigned a number. These numbers can be edited as desired by the user. They are useful for referencing a particular target in various pull-down menus and formatted listings elsewhere in APT.
  • Name in Proposal: Although this is a required entry, the name can be chosen at the user's discretion, and can help you in organizing your proposal.
  • Category and Description: These keywords are needed by the archive.
  • J2000 Coordinates: Use J2000 epoch coordinates.   

Optional parameters:

  • Name for the Archive: A standard searchable (resolvable) name should be entered for future use in archive searches.
  • Uncertainty (for J2000 Coordinates):The required accuracy depends on the observations you plan to obtain. High accuracy is not required for some observations such as imaging, but placing a particular object in a fixed slit for spectroscopy requires higher accuracy. 
  • Proper Motion, Annual Parallax:  Enter these values if they're relevant to your use case. If it's used, you must also specify the Epoch for your values.
  • Extended: Select YES or NO from a pull-down menu (the default is Unknown) to inform the data processing pipeline whether the extraction algorithm should consider the extent of the source or not. This is particularly relevant for spectroscopic observations where the source may or may not fill the aperture.
  • Comments: Enter anything you might find useful for future reference.

Below these parameters is the Background Target section that provides an optional check box where you can tell APT that observations of this target will require a separate background observation for use in data processing. If you have not yet entered the background target(s), the GUI box in this section will be empty. After you have entered the background targets, return to your science target and select the desired background target(s). (This information gets passed downstream to the data processing system.)

Special fixed target cases: mosaics, multi-object spectroscopic targets, and background targets

See also:  JWST Position Angles, Ranges, and Offsets
See also: Background-Limited Observations

Special target cases include target positions provided for mosaic observations and for NIRSpec multi-object spectroscopy

Mosaics are defined by a single coordinate position (the center of the mosaic) and a pattern of fields around this position. The (X,Y) positions of the individual mosaic fields are described in arcseconds relative to the central coordinates, in the reference frame of the detector used for the mosaic observation. A mosaic pattern rotates around the center coordinates, and so the position of each mosaic tile changes position in RA and Dec coordinates, but the (X,Y) coordinates remain fixed.

For NIRSpec multi-object spectroscopy, the target coordinates in APT serve as a reference position on the celestial sphere for the micro-shutter array. Target coordinates are not intended to indicate the position of a particular science target, pointing, or shutter coordinate. A fixed position angle is assigned prior to planning exactly what pointings and micro-shutters need to be opened to capture the spectra of particular objects in the field. The NIRSpec MSA Planning Tool l is used to ingest a catalog of candidate multi-object spectroscopy sources and to define the shutter configurations for each exposure in the observation.

For targets that require a dedicated background observation, a separate "background" target should be defined, and the observation of this target should be linked to the science observation of interest. (The observer should verify that the chosen coordinates provide a suitably clear field.) To create a background target: (1) add a new target with the coordinates for the background pointing. (2) Go back to the science target, and check the box for Observations of this target require companion background observation(s). (3) When that box is checked, a new field appears below it containing a list of other targets in your proposal. (4) Select the just-created background target by its name in the Target selection box.

In the observation template, you will see an error if the observational parameters (in this case, the need for a linked background observation) are not as expected. APT has special requirements that should be used to create an uninterruptible sequence that links the science observation and the separate background observation. A given background can be used for multiple observations provided that these observations use the same science target. To use different backgrounds for other observations of the same target, different background targets with relevant coordinates will need to be defined.  See the proposal parameters article on this topic for more details.

Note that targets chosen to be background targets cannot also be science targets. If your proposal has targets that serve as both science targets and background targets, you will need to create the target twice with slightly different names.



Solar System targets

See also: Proposal Parameters article on valid specifications for Solar System Targets

How to retrieve minor body orbital elements from Horizons

Solar System targets ("moving targets") are specified in APT by selecting New Solar System Target in the Targets page. The APT user has tremendous flexibility to identify specific targets and pointing positions relative to targets using a system of target Levels and pick list information provided.  Level 1 targets are solar system bodies directly orbiting the Sun (planets, comets. or asteroids), while  Level 2 and Level 3 targets are moons  of, or positions on or relative to, the specified Level 1 or Level 2 target.

Another APT distinction between types of moving targets is between Standard Targets and minor bodies (Asteroids and Comets). For Standard Targets, ephemerides can be computed using information directly accessible to and maintained by APT. For the minor bodies, the user must supply orbital elements, either manually or by retrieving them from the JPL Horizons system using the built-in APT function

Note that many of the high level APT entries for moving targets are analogous to the Fixed Target case (e.g. Name in Proposal, Name for the Archive, Description, and so forth). Observers familiar with specifying moving targets for HST observations will see that the functionality for JWST is identical.

For many more details about specifying solar system targets in APT, see the Solar System Targets proposal parameters article.  Also, information is available on Special Requirements needed for many moving target observations.



Generic targets

See also: Proposal Parameters article on valid specifications for Generic Targets.

Generic targets are targets that can only be described in terms of astronomical characteristics or general location in the sky at the time of the initial proposal. This category is used for Targets of Opportunity programs (i.e. where the details of the target or targets are not known until something happens at a later date).  This category is available for both Fixed and Solar System targets. Another use case will be for pure parallel proposals where the parallel observation slots can only be defined on the characteristics of the type of primary observation they may be attached to after acceptance.  Target of Opportunity observations are automatically ON HOLD and do not need the Special requirement, but any other observations using Generic Targets should have an ON HOLD  special requirement placed on them, to prevent the observations from being considered by the long range planning system until details are known.   When the target is fully specified, the ON HOLD is removed and the proposed observation then flows into the scheduling system.

Because of the nature of generic targets, the APT fields available in the target GUI are adjusted somewhat.  The Name in the Proposal field is still present (and required), but an entry for Criteria is provided. This is where you provide the criteria for the unknown target selection.  You may also wish to use the Comments box provided to specify further details about the target selection.

At such time that your proposal is accepted and a given target's details are known, the target information will need to be added into the appropriate Fixed target (or Solar System target) form in APT, including filling out keywords and all other relevant information in those forms.

For full details regarding specifying generic targets, refer to the  Generic Targets proposal parameters article.



The Special Case of Target Groups  

For JWST, APT supports the creation of a special target case known as a Target Group.  A target group is a set of closely-spaced (within one guide visit-splitting distance) fixed targets that are intended to be observed together and for which the observation specification is intended to be identical.  By placing targets in a target group, the user can specify the observational details once in the relevant observation template and then select the target group as the "target" of the observation.  The observational details will then be applied to all of the individual targets automatically.  Note that no changes in the template are allowed for the individual targets if using this configuration.

Because of the specific functionality of the target group concept, it is only applicable for use with four observation templates that involve small fields of view or apertures: the MIRI LRS, MIRI MRS, NIRSpec Fixed Slit and NIRSpec IFU templates.

Target Groups were created for a very specific use case, but excellent gains in efficiency and a tremendous reduction in mechanism motions can be garnered when that use case applies. For a set of targets needing identical observation and exposure specifications, and are within the visit splitting distance on the sky so that the targets can be observed sequentially in the same visit, unnecessary guide star acquisitions can be avoided and the ordering of activities can be adjusted for both efficiency and to save wear and tear on the filter/grating wheels of the affected instrument.

An example might be a grouping of pre-main sequence stars, all to be observed with the NIRSpec fixed slit or IFU.  To the extent that such a grouping lies within the visit splitting distance for a given place on the sky (typically 40 - 80 arcsec or so; reported in APT for reference), the observations can be accomplished very efficiently, since no new guide star acquisition is required for the individual targets.  Furthermore, let's assume a use case where the NIRSpec IFU is being used to create a small mosaic using multiple gratings/filters.  The Target Group concept allows the entire set of mosaic tiles to be observed with one grating/filter combination prior to moving the mechanism to the next grating/filter combination, instead of completing all gratings/filters on the first tile before moving to the next.  For a 5x5 IFU mosaic, this reduces 25 mechanism motions down to one for each grating/filter combination.




Published

 

Latest updates
  •  
    Article updated for Cycle 1 Call for Proposals release.