Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.stsci.edu/spst/lrpg/documentation/procedures/lrpg_managing_constraint_scenarios.html
Дата изменения: Fri Apr 2 18:57:46 2004 Дата индексирования: Sun Mar 2 12:47:14 2014 Кодировка: Поисковые слова: р р р с р с р р р с р с р р р с с р р с р с р р п п р п п п п |
In mid-2003, the manner in which SPIKE Constraint sets are managed was changed. This document provides an overview of the new architecture and provides tips on managing the constraint sets.
In order to generate suitabilities, SPIKE requires information about various spacecraft, instrument, and communications constraints (located in /data/operational1/constraint-sets/ ) which are primarily stored in the constraint set file loaded when SPIKE loads a "control" file (located in /data/operational1/control/ ). When a proposal is loaded into SPIKE, it checks to see if new cv-descs, orient-tables, and events files need to be generated or regenerated (stored in a suitable subdirectory in /data/operational1/description-files/ ).
The constraint set used is identified in the control-file by the parameter ":constraint-scenario". The value in the field identifies a record which must exist in the constraint_scenarios assist table with the value in the field "scenario_name" corresponding to the :constraint-scenario value in the file. If the record does not exist, there will be an SPIKE error. If ":constraint-scenario is set to ":default", then the record in the constraint_scenario table identified by the field "default" set to "Y" is chosen.
The tool scenario-manager is used to manage insertion, deletion, and change of default record in the constraint_scenarios table. The database table cross-references constrain_set names (names of the *.lisp file in /data/operational1/constraint-sets/ , names of the subdirectory tree in /data/operational1/description-files/ ) with scenario_name s ( value in the field :constraint-scenario in the control files).
Running the tool standalone with no parameters shows the syntax of how to run the tool as well as all of the records in the table.