Differences between revisions 6 and 20 (spanning 14 versions)
⇤ ← Revision 6 as of 2006-04-04 08:26:10 →
Size: 823
Editor: pacsdac01
Comment:
← Revision 20 as of 2009-07-15 14:32:36 → ⇥
Size: 1272
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The '''testcontrol-server''' application has to be started from an account that has access to the '''cus''' engine (usually account cususer@PACS1 here at MPE). The communication between TOPE and CUS is done by the system wide '''X-server''' application. Hence, '''testcontrol-server''' has to be associated, via the DISPLAY variable, with the '''''irmultia''''' processor. The association is implemented as
{{{
(setenv DISPLAY irmultia:0 ; testcontrol-server &)
}}}
That is, redefine DISPLAY only for the '''testcontrol-server''' application and start the control application as a background task.		 The '''testcontrol-server''' application is started automatically by the procedure that updates '''cus''' following adding or editing a script module into the CUS registry.
Line 9: Line 5:
[wiki:Self:PACS/FM Setup to schedule CUS from TOPE]
Line 11: Line 6:
[wiki:Self:PACS/FM Correcting CUS procedures] The setup of the PACS MPE FM Databases are described :
[[PACS/FM_ILT_Procedures/DatabaseProcedures|DatabaseProcedures]]


Current Datbase configuration for CUS use :
{{attachment:dbsetup7.jpg}}

* In the current configuration PACS5 is the operational database
   * "pacs_fm_ilt_2" is used as operational database
   * "pacs_fm_ilt_2" is used for commanding and telemetry ingestion

 * In the current configuration PACS1 is used for development of the CUS definitions and procedures.
   * "sftcode" is the CUS development database
   * "sftcode" is accessed from within MPE and remote via cusgui

[[PACS/FM_ILT/SetupCUS|Setup to schedule CUS from TOPE]]

[[PACS/FM_ILT/CorrectCUS|Correcting CUS procedures]]

[[PACS/FM_ILT/SupportCUS|Support Procedures]]

[[PACS/FM_ILT/CUSDev|CUS Procedures Development]]

[[PACS/FM_ILT/CUSExp|CUS Procedure export and configuration control]]

[[PACS/FM_ILT/CUSLoad|CUS Procedures loading into operational Database]]

To schedule a CUS "mode" script from TOPE requires the intervention of the testcontrol-server application.

The testcontrol-server application is started automatically by the procedure that updates cus following adding or editing a script module into the CUS registry.

The setup of the PACS MPE FM Databases are described : DatabaseProcedures

Current Datbase configuration for CUS use : dbsetup7.jpg

* In the current configuration PACS5 is the operational database

  • "pacs_fm_ilt_2" is used as operational database
  • "pacs_fm_ilt_2" is used for commanding and telemetry ingestion
  • In the current configuration PACS1 is used for development of the CUS definitions and procedures.
    • "sftcode" is the CUS development database
    • "sftcode" is accessed from within MPE and remote via cusgui

Setup to schedule CUS from TOPE

Correcting CUS procedures

Support Procedures

CUS Procedures Development

CUS Procedure export and configuration control

CUS Procedures loading into operational Database

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