For obvious reasons the Petra-3 beamlines are setting up a remote operation mode allowing users to conduct experiments from their home institutes. This service has be implemented in a save way in the sense that personal safety has always to be guaranteed. An addition, users should be prevented from unintentially damaging precious beamline components. The MacroExecutor serves this purpose. On the one hand, users have access to the full functionality of the macro interface and on the other hand the beamline staff selects the devices being visible to the user.
... <device> <name>eh_mot04</name> <type>stepping_motor</type> <tags>remote</tags> <module>oms58</module> <device>p99/motor/eh.04</device> <control>tango</control> <hostname>haspp99:10000</hostname> </device> ...
The motor eh_mot04
has the tag remote. To make it
available for the users the following command has to be executed:
$ SardanaAIO3.py -x -t remote
This way, only devices with the remote tag will be created inside the Pool and will therefore be available for all actions performed by the MacroServer. The user will not have access to the untagged devices through the SardanaMacroExecutor.
Beamline staff members who need access to all devices start e.g. TngGui3.py.
Figure 7.2 shows the MacroExecutor. It can be launched from TngGui or from the command line:
SardanaMacroExecutor.py (Debian-9) SardanaMacroExecutor3.py (Debian-10)
The elements of the main widegt:
["tst.fio"]
to create .fio files, ["tst.spe"]
to create spec files or ["tst.fio", "tst.nxs"]
to
create .fio and HDF files.
The Tools menu:
The Misc menu: