WFSC Commissioning Template Parameters
JWST's WFSC Commissioning Template, available in the Astronomer’s Proposal Tool (APT), is used for any commissioning activity that uses NIRCam exposures alternating with mirror moves.
Purple text indicates the parameter is Limited Access.
Boldface italics type indicates the name of an APT parameter or a value for a parameter.
Red text indicates restrictions on a parameter.
Black text indicates an important note.
Brown text indicates notes for the developers.
Green text indicates the name of the parameter used by Commanding.
Items in brackets - <value> - are required values.
Items in square brackets - [<value>] - are optional.
This method will be used during any commissioning activity that uses the following sequence, containing NIRCam exposures alternating with mirror moves.
- Take a NIRCam image
- Perform a group of mirror moves
- Take another NIRCam image
- Perform the next group of mirror moves
- Take a final NIRCam image
The length of the sequence is determined by the contents of the Wavefront Control File. There can be multiple mirror move groups in a Wavefront Control File.
The following parameters are used to define Wavefront Sensing and Control Commissioning Operations. A Wavefront Control File (provided by the WFSC Scientist) will be attached to each visit by the PPS Operator.
Currently, this method is specified for the following commissioning steps:
- Secondary Mirror Focus Sweep
- Segment ID
- Segment Image Array
- Pupil Imaging
- Coarse Phasing
- Segment Piston Scan
Note: A NIRCam Image will be taken before and after each set of mirror moves. All images will be Full frames using the same parameters on all the specified NIRCam detectors.
In addition to the following template parameters, this template will have the Special Requirement WAVEFRONT SENSING added with a default required value of SENSING_CONTROL .
Note that this type of observation cannot be obtained with other parallel observations or as a parallel to normal science observations.
The WFSC Commissioning template consists of the following parameters:
|Observation Number||assign observation number|
|Observation Label||provide observation label||text||optional|
|Observation Comments||provide observation comments||text||optional|
|Target||select Target Name||choose from list||from Target List|
|Special Requirements||specify special requirements||choose from list||if needed|
|Template Specific Information|
|select module||A, B|
|Short Wavelength Filter||select short filter||F200W, F212N|
|Long Wavelength Filter||select long filter||choose from list|
|Readout Pattern||select readout pattern||FAST, SLOW|
|Number of Groups/Integration||specify number of groups/integration||number|
|Number of Integrations/Exposure||specify number of integrations/exposure||number|
|Reacquisition||select reacquisition||REAC, NOREAC|
|Expected Number of WFC Groups||specify number of groups||number||1-200|
|Expected Number of WFC Commands||specify Expected Number of WFC Commands||number|
The following parameters are generic to all templates, and are not discussed in this article: Observation Number, Observation Label , Observation Comments, and Special Requirements.
Select the TARGET NAME from the list of targets previously entered.
Solar system targets may not be used with this template.
MODULE [MODULE] = A, B, ALL
This parameter specifies the module(s) to be used to obtain the data.
FILTER [FILTSHORT] = F200W, F212N
Select the name of the SHORT FILTER you wish to use. The same filter will be used in both modules, if both modules are specified.
FILTER [FILTLONG] = F322W2, F460M, F480M. F323N+F322W2
Select the name of the LONG FILTER [FILTLONG]you wish to use. The same filter will be used in both modules, if both modules are specified.
Developer note: In the database the default of FLAT will be stored in PUPILLONG. If long wavelength filter(s) are chosen (including F323N_F322W) they will be stored in the FILTLONG, and the PUPILLONG will be null.
READOUT PATTERN [READOUT PATTERN] = RAPID, BRIGHT1
This field specifies the readout pattern to be used to obtain the data.
Number of Groups/Integration
NUMBER OF GROUPS/INTEGRATION [NGROUPS] specifies the number of groups in an integration. Allowed values are shown in Table 1.
Table 1. Allowed values for NUMBER OF GROUPS/INTEGRATION and NUMBER OF INTEGRATIONS/EXPOSURE
|Module/Readout Pattern||Number of Groups/Integration||Number of Integrations/Exposure|
|all other combinations||1-10||1-10|
Number of Integrations/Exposure
NUMBER OF INTEGRATIONS/EXPOSURE [NINTS] field specifies the number of times the integration is repeated. Allowed values are shown in Table 1.
REACQUISITION [REACQ] = REACQ, NOREACQ
RThis parameter specifies if the guide star is to be re-acquired after each mirror move group is executed.
Note for developers: Visits created from this template should be marked in the database as WFS visits by APT (visit.wavefront_sensing) and as WFSC visit type in VSS.
Expected Number of WFC Groups
The expected number of WFC groups [NWFCGROUPS] specifies the expected number of mirror move groups in the WFC file to be associated with this observation. The number of groups controls the number of images taken through the iterative process described above. Note that this parameter is purely advisory for use in PPS calculations of visit duration and data volume; the number of groups executed on orbit will depend solely on the contents of the WFC file and not on this parameter. This parameter is an integer and must be in the range 1 to 200: the default value is 1.
Note for developers: The estimated duration of the observation should be calculated as follows:
estimated_duration = (NWFCGROUPS +1) * (duration of one NIRCam image including overheads) + NWFCGROUPS * T_MIRROR_MOVE,
where T_MIRROR_MOVE is time for a segment mirror move.
If REACQ then estimated_duration = NWFCGROUPS * (FGS overhead to get into tracking)
The estimated data volume should be calculated as (NWFCGROUPS + 1) * (the data volume for an individual exposure).
Throughout most of OTE commissioning the expected number is known in advance for each observation, and in the handful of cases where the WFC file may differ from the expected value it should not be necessary to reprocess this parameter in APT and reprocess the visits.
Expected Number of WFC Commands
EXPECTED NUMBER OF WFC COMMANDS = 1 - 2100
The number of WFC commands expected with this proposal. Default is 170.
December 16, 2022
- PROPINSTJWST-91148 In Introduction, changed "default" to "required" for SENSING CONTROL.
Version 5 (December 8, 2021)
Version 4 (January 19, 2021)
Version 3 (April 16, 2019)
- Editorial change (moved change log to main article)
Version 2 (May 7, 2018)
- PR 89947 - updated note to developer in Introduction section.
Version 1 (May 30, 2017)
- This is the converted Word File from Chapter 60.
- PR 87895 - revised names of Number of Groups and Integrations