Page History

...

bravo@clonfarm2:/usr/clas12/release/1.4.0/slac_svt$ cat copy_libraries.sh
#!/bin/bash
rm -rf /usr/clas12/release/1.4.0/coda/Linux_x86_64/lib/librogue*
rm -rf /usr/clas12/release/1.4.0/coda/Linux_x86_64/lib/libhps*
\cp -a -v /usr/clas12/release/1.4.0/slac_svt/rogue_lite/lib/* /usr/clas12/release/1.4.0/coda/Linux_x86_64/lib/
\cp -a -v /usr/clas12/release/1.4.0/slac_svt/heavy-photon-daq/software/rogue_coda/install/x86_64-linux/lib/* /usr/clas12/release/1.4.0/coda/Linux_x86_64/lib/

Setting up a VNC for SVT DAQ work - DEPRECATED

SVT DAQ system implies running a gui for configuration and data taking. Setting up a VNC can speed up significantly work time. 
It is suggested to setup a VNC server on rdsrv305 as that is directly accessible via internet. 
General informations on how to setup a VNC are given here:
VNC on Unix

...

You should be able to connect to the vncserver via ssh tunnel through localhost:9999

Setting up a VNC for CODA Running and sharing work

The server machine rdsrv309 has a vncserver running as a service on desktop :2
It is run under clasrun user and it is bound to localhost. In order to access it from remote, an ssh tunnel needs to be setup on the client machine.

ssh -L <localClientPort>:localhost:5902 -C -N -l clasrun rdsrv309.slac.stanford.edu

Where <localClientPort> can be whatever port that is not used on the client side. To connect to the vncserver just connect to localhost:<localClientPort> after opening the ssh tunnel.

Basic SVT DAQ instructions for the test bed

...

• Connect to the rdusr219 machine

• Setup the general environment: 

  No Format
  source /u1/hps/setup_env.sh

• Start the conda environment:

  No Format
  conda activate rogue_5_8_0

• Run the software from this folder.

  No Format
  cd /u1/hps/server/heavy-photon-daq/software/scripts python SvtDaqGui.py --local --env SLAC21BOT [--epicsEn]

  The env command line is to tell which network configuration to load. The network configuration that gets loaded is stored in python/hps/constants.py
  Check the FebLinkStatus. In the RCE test, you should see FebFpga[0] and check the Link[0] state. If False, Read the variables again (click Read). If now True, means we are talking to the Feb. After the link is established one can load the configuration. 

...

To access this information, one needs to ssh to the clonfarm machines. In particular, clonfarm2 and clonfarm3 are the SVT DAQ machines.

Running the SVT Daq using CODA

A setup is available to run the SVT DAQ using CODA. As of 25th of June the following configuration has been tested and it is working:

• Running using rdsrv309 only
• 1 FEB ON but Hybrids OFF
• Threshold are not loaded as Daq mapping needs to be taken into account
• Random trigger rate at 5 kHz

Here are the instructions on how to setup CODA

• ssh as clasrun to rdsrv309

• The default shell for clasrun is tcsh. In order to start rogue one has to change to /bin/bash. Then setup the conda environment as shown in "Basic SVT DAQ instructions for the test bed"

  No Format
  /bin/bash source /u1/hps/setup_env.sh conda activate rogue_5_8_0 cd /u1/hps/server/heavy-photon-daq/software/scripts

• Run the Rogue instance for data taking. Epics connection has not been tested yet. So is kept off at the moment. in order for the coda system to run, both COBs need to be enabled. So use the full configuration even if a single FEB is attached. In the case the second COB is not populated, the system is smart enough to figure it out

• No Format
  python SvtCodaRun.py --local --env SLAC21

• This command will bring up the Rogue Gui and start the rogue server

Open a new terminal as clasun. To start CODA it's sufficient to type 

runcontrol -rocs

This will bring up the GUI interface. The following setup will guide you through the various transitions.

DEBUG:

Connect via minicom to the crate controller:

...