Differences between revisions 6 and 8 (spanning 2 versions)
Revision 6 as of 2006-04-04 08:26:10
Size: 823
Editor: pacsdac01
Comment:
Revision 8 as of 2006-09-26 09:44:40
Size: 908
Editor: dcesarsky
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
[wiki:Self:PACS/FM Setup to schedule CUS from TOPE] [wiki:Self:PACS/FM_ILT/SetupCUS Setup to schedule CUS from TOPE]
Line 11: Line 11:
[wiki:Self:PACS/FM Correcting CUS procedures] [wiki:Self:PACS/FM_ILT/CorrectCUS Correcting CUS procedures]

[wiki:Self:PACS/FM_ILT/SupportCUS Support Procedures]

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]

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