Page tree

Eiger Setup

Server

  • has to run on the node where HiDRA should be started and stopped
  • By default the server configures the started hidra instance in a way that only data written in the predefined directory structure is copied over, that means the directories

    current/raw
    current/scratch_bl
    commissioning/raw
    commissioning/scratch_bl
    local

    e.g. data written on the Eiger in current/raw is copied/moved but data written directly in the root dir is not.


Client

  • change to folder 

    cd /opt/hidra/src/hidra_control
  • The script only is allowed to be executed from beamline PCs corresponding to the specified beamline.
  • To change the default settings, create a beamline specific config script under /opt/hidra/conf/control_client_<beamline>.yaml
    (the default config /opt/hidra/conf/control_client.yaml can be used as reference) (only in 4.1.0 and newer)


The setup for ASAP3 allows interaction with detectors only if they are added to the beamline specific netgroup. The only exceptions are stop and getinstances (see below)

# Start:

./hidra_control_client.py --beamline <beamline> --det <detector ip or dns name> --start


  • The argument '--beamline' is mandatory for all commands. It can be one of the following:
    "p01", "p02.1", "p02.2", "p03", "p04", "p05", "p06", "p07", "p08", "p09","p10", "p11"
  • For starting hidra, the detector IP or DNS name is mandatory and the API version of the filewriter may be set (default is 1.6.0). The detector specified has to be registered for the beamline.

# Stop:

./hidra_control_client.py --beamline <beamline> --det <detector ip or dns name> --stop
  • The arguments '--beamline' and '--det' are mandatory (see description of start)


In case that hidra was not stopped before the detector was removed from the netgroup, it is still possible for a beamline to stop its own instance. Once the instance is stopped interaction is the not possible anymore without changing the netgroup.


# Check status:

./hidra_control_client.py --beamline <beamline> --det <detector ip or dns name> --status
  • The arguments '--beamline' and '--det' are mandatory (see description of start)

#Get the current settings

./hidra_control_client.py --beamline <beamline> --det <detector ip or dns name> --getsettings
  • The arguments '--beamline' and '--det' are mandatory (see description of start)
  • Displays the settings with which HiDRA was started on the server

#Get the current running instances

./hidra_control_client.py --beamline <beamline> --getinstances
  • The argument '--beamline' is mandatory (see description of start)
  • Returns the names of detectors for which hidra instances for the beamline are running.
  • This command can be executed independently from the netgroup
  • No labels