Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2006-09-28 10:04:25 →
Size: 223
Editor: EkkehardWieprecht
Comment:
← Revision 2 as of 2006-12-11 17:33:33 → ⇥
Size: 554
Editor: dcesarsky
Comment:
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_2" is the operational database
 * To achieve versioning control, any change to '''CUS''' (amended or new script) will generate a new CUS model.
 * A dedicated procedure, invoked as '''''ccm -updatecus''''', creates the new model, updates the local CVS, and conditions '''testcontrol''' to work with te 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_2" is the operational database

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

  • A dedicated procedure, invoked as ccm -updatecus, creates the new model, updates the local CVS, and conditions testcontrol to work with te 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)