|
Size: 723
Comment:
|
Size: 823
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 |
| Line 5: | Line 5: |
| (setenv DISPLAY irmultia:0 ; testcontrol-server) | (setenv DISPLAY irmultia:0 ; testcontrol-server &) |
| Line 7: | Line 7: |
| That is, redefine DISPLAY only for the '''testcontrol-server''' application. | That is, redefine DISPLAY only for the '''testcontrol-server''' application and start the control application as a background task. |
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]