ISIM Dictionary File Update Template Parameters
JWST's ISIM Dictionary File Update Template, available in the Astronomer’s Proposal Tool (APT), is used for initializing or updating one of four "dictionary files" onboard and synching the onboard scripts with the modified dictionary file(s).
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.
The ISIM Dictionary File Update template is to be used by the Commanding Team for initializing or updating one of four "dictionary files" onboard and synching the onboard scripts with the modified dictionary file(s). The dictionary files are generated by the Commanding Team from Project Reference Database items and used by the onboard scripts to construct Flight Software commands, table loads and telemetry requests, and to retrieve symbol-of-interest mnemonics. The ISIM Dictionary File Update visit is not intended to be a real-time visit. However, the ISIM Dictionary File Update visit will need to be scheduled in the onboard Observation Plan such that it is compatible with the PRD items used by onboard scripts that are executed in subsequent visits.
Multiple Dictionary updates may be done at once.
Note to developer: Populate the order_number field for each separate update specification.
Note for developer: The column for choosing the ACTION does not appear in the UI. All exports to isim_dictionary_exposure_specification should always have the value 'CHANGE' for the ACTION column.
Note that this type of visit must be PRIME only because this visit changes the version of the Dictionary File(s) on-board and the Dictionary file(s) version must be in sync with the on-board scripts at all times; the special requirement NO PARALLEL should be added by default, as should the special requirement REQUIRED.
The following parameters are used to define Realtime Commanding observations.
|assign observation number||number|
|Observation Label||provide observation label||text|
|Observation Comments||provide observation comments||text|
|specify special requirements||choose from list||if needed|
|Template specific information|
|Dictionary Type||choose a dictionary type||choose from list|
|Dictionary File Name||specify dictionary file name||text|
DICTIONARY TYPE [DICTIONARY_TYPE] = CMD, TBL, TLM, SOI
This parameter is used to select the Dictionary Type – CMD (command), TBL (table), TLM (telemetry) or SOI (symbol-of-interest).
Dictionary File Name
This parameter is used to specify the dictionary FILE NAME [FILE_NAME], with extension (e.g. IC14_141106.cin). Note that OPGS will automatically prefix "ram:/" to the filename when generating the visit file.
Note for developers: APT should automatically set Target to NONE.
Note for developers: The database visit table values should be:
internal_target = 'Y'
external_target = 'N'
pcs_mode = 'NONE'
schedule_as_parallel = 'N'
parallels_allowed = 'N'
realtime = 'N'
required = 'Y' -> Special Requirement
data_volume = 0
science_duration = 60 sec per file
scheduling_duration = 60 sec per file
charged_duration = 60 sec per file
(All other duration fields in the "visit" relation = 0)