w

csaxs_bec/devices/jungfraujoch/eiger.py

@@ -1,54 +1,17 @@
 """
+
 Integration module for Eiger detectors at the cSAXS beamline with JungfrauJoch backend.
-There are currently two supported Eiger detectors:
-- EIGER 1.5M
-- EIGER 9M
 
-This module provides a base integration for both detectors. A short list of useful
-information is also provided below.
+A few notes on setup and operation of the Eiger detectors through the JungfrauJoch broker:
 
-The JungfrauJoch WEB UI is available on http://sls-jfjoch-001:8080. This is an interface
-to the broker which runs on sls-jfjoch-001.psi.ch. The writer service runs on
-xbl-daq-34.psi.ch. Permissions to get access to these machines and run systemctl or
-journalctl commands can be requested with the Infrastructure and Services group in AWI.
-
-Useful commands for the broker service on sls-jfjoch-001.psi.ch:
-- sudo systemctl status jfjoch_broker # Check status
-- sudo systemctl start jfjoch_broker # Start service
-- sudo systemctl stop jfjoch_broker # Stop service
-- sudo systemctl restart jfjoch_broker # Restart service
-
-For the writer service on xbl-daq-34.psi.ch:
-- sudo journalctl -u jfjoch_writer -f # streams live logs
-- sudo systemctl status jfjoch_writer # Check status
-- sudo systemctl start jfjoch_writer # Start service
-- sudo systemctl stop jfjoch_writer # Stop service
-- sudo systemctl restart jfjoch_writer # Restart service
-
-Scientists need to have permission
-to connect and run systemctl commands on these machines Beamline scientists have access to this
-server and can connect to it through SSH in case further debugging is needed.
-On sls-jfjoch-001.psi.ch, you can use the following useful commands:
-
-- sudo systemctl status jfjoch_broker
-- sudo systemctl restart jfjoch_broker
-
-The JungfrauJoch server for cSAXS runs on sls-jfjoch-001.psi.ch
-User with sufficient rights may use:
-- sudo systemctl restart jfjoch_broker
-- sudo systemctl status jfjoch_broker
-to check and/or restart the broker for the JungfrauJoch server.
-
-Some extra notes for setting up the detector:
 - If the energy on JFJ is set via DetectorSettings, the variable in DatasetSettings will be ignored
 - Changes in energy may take time,  good to implement logic that only resets energy if needed.
 - For the Eiger, the frame_time_us in DetectorSettings is ignored, only the frame_time_us in
   the DatasetSettings is relevant
 - The bit_depth will be adjusted automatically based on the exp_time. Here, we need to ensure
-  that subsequent triggers properly
-  consider the readout_time of the boards. For Jungfrau detectors, the difference between
-  count_time_us and frame_time_us is the readout_time of the boards. For the Eiger, this needs
-  to be taken into account during the integration.
+  that subsequent triggers properly consider the readout_time of the boards. For the Eiger detectors
+  at cSAXS, a readout time of 20us is configured through the JungfrauJoch deployment config. This
+  setting is sufficiently large for the detectors if they run in parallel mode.
 - beam_center and detector settings are required input arguments, thus, they may be set to wrong
   values for acquisitions to start. Please keep this in mind.
 
@@ -65,9 +28,6 @@ Hardware related notes:
         - cd power_control_user/
         - ./on
         - ./off
-
-Further information that may be relevant for debugging:
-JungfrauJoch - one needs to connect to the jfj-server (sls-jfjoch-001)
 """
 
 from __future__ import annotations