Search/Navigation:
Related:
SLAC/EPP/HPS Public
Jefferson Lab/Hall B/HPS Run Wiki
S30XL-LESA/LDMX
From counting house as hpsrun (should already be done):
In terminal: daqvnc.py connect config hps-svt-2
In another terminal: daqvnc.py connect config hps-svt-3
Remotely (in Hall B gateway):
ssh -Y clonfarm2
vncviewer :2
ssh -Y clonfarm3
vncviewer :2
Remotely (outside jLab network):
|
Then:
Any crate related command should be issued by SVT experts only
SDK software installation to talk to the atca crate
.... INFO : clonfarm2 go..... |
SVT software is installed in
|
On clonfarm2 start the rogue server
|
The "epicsEn" flag is necessary to enable controls via Epics.
On clonfarm3 start the dummy server
|
If opening the Rogue GUIs for the first time, make sure all of the FEBs are turned off.
To take a CODA run, both the rogue server and a dummy server need to be started. To start the rogue server, first ssh into clonfarm2 and issue the following commands
source /usr/clas12/release/1.4.0/slac_svt_new/anaconda3/etc/profile.d/conda.sh conda activate rogue_5.9.3 cd /data/hps/slac_svt/server/heavy-photon-daq/software/scripts/ python SvtCodaRun.py --local --env JLAB --epicsEn
The dummy server runs on clonfarm3 and can be brought up as follows after ssh'ing into that machine
source /usr/clas12/release/1.4.0/slac_svt_new/anaconda3/etc/profile.d/conda.sh conda activate rogue_5.9.3 cd /data/hps/slac_svt/server/heavy-photon-daq/software/scripts/ python SvtCodaDummy.py --local --env JLAB --epicsEn
At this point, the FEBs and hybrids can be brought up via the medm GUIs.
Once the hardware has been powered up, you can initialize a run in CODA using the configuration PROD77_SVT and the config file hps_v2_svtOnly_noThresh.
CODA run control should be running in a VNC on clondaq7. If not, contact the DAQ expert.
Start the online monitor
startSVTCheckout
Reset the dataDPM
heavy-photon-daq/software/scripts/resetDataDpm.sh
If the DPMs do not come up after several resets, one might try a cold reset (but might create issues in the recovery)
heavy-photon-daq/software/scripts/coldResetDataDpm.sh
At this point, the FEBs and hybrids can be brought up via the medm GUIs.
This is in the event builder and indicates that we are dropping packets.
This is raised in RssiContributor.cc in the event_builder by acceptFrame thread
Effect:
rol BUSY
Causes: Dropped frames.
Fix: Reset COBs
This usually indicates that the FEBs lost clock
Effect: not possible to run
Causes: FEBs lost clock
Fix: Recycle FEBs and run control