Current the control links of the detector system are connected to switch and the synchronization between detector PCs are done via DESY detector net (192.168.138.*). The data links of each slave module are connected to one detector PC.
On each server, a receiver tango server is running to receive data from data links and save them in storage. The control tango server is running on haspp03lmbd01. This tango server is for
- communicate with the detectors via eno3
- communicate with all the receivers
Detector configuration files
The detector configurations are done via yaml file. Each tango server (receiver, control) has it's own file, the file can be found in /localdata/config/ on corresponding detector PCs.
Run the detector
Before running the detector, some configurations might need to be changed depending on the use case.
Disable specific module ( use disabling module 2 as an example here):
Specific module can be removed during initialization.
- In the corresponding yaml file which can found in Properties of LambdaCtrl tango server in Jive, one may comment out the module entry under detectors section, so that module will not connected by software.
Comment out the following part in ctrlall.yml in /localdata/config
Remove the IP of the PC where this module is connected from slaves list in sync section
- Remove "p03/lambdarecv/02" the Receivers property in LambdaCtrl tango server and remove that receiver too.
- Comment out the line which start the receiver tango server (ssh -n haspp03lmbd03 /usr/lib/tango/server/LambdaRecv m03 -v2 &) in startalllambda.sh.
Change buffer size:
The buffer size decides how much RAM need to be reserved for receiver during data acquisition. This shows how many images can be taken for each acquisition. This can be checked by FreeBuffer attribute in the receiver tango server.
NOTE: allocating large amount of RAM can last long (current benchmark shows the memory allocation speed is ~1.2GB/s)
Control the detector
Once the tango server is ready, the detector can be controlled via LambdaCtrl tango server.
Be aware that changing some attributes(EnergyThreshold, OperatingMode) may take some time (more than 3 seconds) and it's recommended to check the status of the tango server when changing those attributes.
At the moment, there are two sources of live images, one from receiver side(haspp03lmbd01:10000/p03/lambdarecv/#/LiveLastImageData), which is taken from data stream written to Nexus file, this live image is only for each slave module. The other one from control tango server(haspp03lmbd01:10000/p03/lambdactrl/1/LiveLastImageData) stitches the slave module images into one large image with translation information.
Both live image has refresh rate 1 frame/second by default. Lavue can be used to view the live images. ATKpanel is not recommended.
NOTE: The stitched image is relatively large. If one uses this, the ATKpanel should not be used, otherwise it causes Java heap memory error.
By default, the stitched image update is disabled, this is controlled by EnableFullImageView. If this is set true, the stitched live image is available in LiveLastImageData attribute of the LambdaCtrl tango server. However DO NOT use this together with ATKpanel as mentioned above.