Size: 844
Comment:
|
Size: 908
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] |
Line 13: | Line 13: |
SupportProcedures | [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]