Differences between revisions 8 and 10 (spanning 2 versions)
⇤ ← Revision 8 as of 2006-09-26 09:44:40 →
Size: 908
Editor: dcesarsky
Comment:
← Revision 10 as of 2006-09-28 09:52:16 → ⇥
Size: 1184
Editor: EkkehardWieprecht
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:

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

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

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

[wiki:Self: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 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.

[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]

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