Differences between revisions 1 and 5 (spanning 4 versions)
⇤ ← Revision 1 as of 2006-09-28 10:04:25 →
Size: 223
Editor: EkkehardWieprecht
Comment:
← Revision 5 as of 2009-07-15 14:32:36 → ⇥
Size: 933
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Describe PACS/FM ILT/CUSLoad here.* In the current configuration PACS5 is the operational database
   * "pacs_fm_ilt_1" is used as operational database
   * "pacs_fm_ilt_1" is used for commanding and telemetry ingestion		  * In the current configuration PACS5 is the operational database and "pacs_fm_ilt_3" is the operational database
 * To achieve versioning control, any change to '''CUS''' (amended or new script) will generate a new CUS model.
 * Scripts may be amended/created using the built-in editor of the CUSGUI, or standard editting of the ASCII copy of the script, to be found in the directory /home/oper/toREG/Name_of_Script.cus
 * If the script was modified within the CUSGUI, you must ''Commit'' your changes. If you have amended/created a file in toREG/, you must issue ''cus -f -import Name_of_Script.cus''
 * A dedicated procedure, invoked as '''''ccm -updatecus''''', creates the new model, updates the local CVS, and conditions '''testcontrol''' to work with the new model.
 * Only the test conductor should perform the ''updatecus'' procedure (the procedure stops testcontrol, causing any running TOPE task to abort in error)
  • In the current configuration PACS5 is the operational database and "pacs_fm_ilt_3" is the operational database

  • To achieve versioning control, any change to CUS (amended or new script) will generate a new CUS model.

  • Scripts may be amended/created using the built-in editor of the CUSGUI, or standard editting of the ASCII copy of the script, to be found in the directory /home/oper/toREG/Name_of_Script.cus

  • If the script was modified within the CUSGUI, you must Commit your changes. If you have amended/created a file in toREG/, you must issue cus -f -import Name_of_Script.cus

  • A dedicated procedure, invoked as ccm -updatecus, creates the new model, updates the local CVS, and conditions testcontrol to work with the new model.

  • Only the test conductor should perform the updatecus procedure (the procedure stops testcontrol, causing any running TOPE task to abort in error)

Herschel: PACS/FM_ILT/CUSLoad (last edited 2009-07-15 14:32:36 by localhost)