Herschel: Diff for "PACS/FM_ILT_Procedures/CUSprocedures"

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

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 setup of the PACS MPE FM Databases are described : [wiki:PACS/FM_ILT_Procedures/DatabaseProcedures DatabaseProcedures]

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

Edit conflict - other version:

The setup of the PACS MPE FM Databases are described : [wiki:PACS/FM_ILT_Procedures/DatabaseProcedures DatabaseProcedures]

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

Edit conflict - your version:

End of edit conflict

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

[wiki:PACS/FM_ILT/CorrectCUS Correcting CUS procedures]

[wiki:PACS/FM_ILT/SupportCUS Support Procedures]

[wiki:PACS/FM_ILT/Use CUS for commanding]

[wiki:PACS/FM_ILT/CUSDev CUS Procedures Development]

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

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