Differences between revisions 5 and 6
⇤ ← Revision 5 as of 2006-03-23 12:06:02 →
Size: 780
Editor: pacsdac01
Comment:
← Revision 6 as of 2006-04-04 08:26:10 → ⇥
Size: 823
Editor: pacsdac01
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The '''testcontrol-server''' applications has to be started from an account that has access to the '''cus''' engine. 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 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

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 Setup to schedule CUS from TOPE]

[wiki:PACS/FM Correcting CUS procedures]

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