Difference between revisions of "GeP ECal cosmics DAQ"
From Hall A Wiki
(→VNC connection) |
(→VNC connection) |
||
| Line 13: | Line 13: | ||
./runDiagGui.sh ecaltest.txt | ./runDiagGui.sh ecaltest.txt | ||
| + | === ECAL VTP trigger === | ||
| + | * Each block reports a hit that is above the TET threshold to VTP and its crossing threshold time. | ||
| + | * For a super module, if there are more than "NBLOCK" blocks having a hit within "HIT_DT", it will register a trigger candidate at the time when the "NBLOCKS" requirement is first met. The trigger candidate for each super module is reported. | ||
| + | * For all three super modules, if there are more than "NSMO" super modules having a trigger candidate within "SMO_DT", a trigger is generated at the times when the "NSMO" are met. The | ||
| + | trigger is reported. | ||
| + | * SMO_DT>= HIT_DT | ||
=== VNC connection === | === VNC connection === | ||
* ssh adaq@adaq1 | * ssh adaq@adaq1 | ||
Revision as of 20:35, 8 May 2024
- CPU : sbsvme22
- VTP : hksvtp portservhats4 port 3 geptestvxs.jlab.org
- VXS crate : 129.57.188.101
2 FADCs in slot 8 and 9
- DiagGui
In sbs-onl account from daq computers or CPU
cd ecal/fe_diaggui
./runDiagGui.sh ecaltest.txt
ECAL VTP trigger
- Each block reports a hit that is above the TET threshold to VTP and its crossing threshold time.
- For a super module, if there are more than "NBLOCK" blocks having a hit within "HIT_DT", it will register a trigger candidate at the time when the "NBLOCKS" requirement is first met. The trigger candidate for each super module is reported.
- For all three super modules, if there are more than "NSMO" super modules having a trigger candidate within "SMO_DT", a trigger is generated at the times when the "NSMO" are met. The
trigger is reported.
- SMO_DT>= HIT_DT
VNC connection
- ssh adaq@adaq1
- ssh sbs-onl@eel124gemdaq
- Start a VNC session: start_daq_vnc
- Connect to a VNC session: connect_daq_vnc (same password as "adaq")
Set up CODA
- Use "sbs-onl@eel124gemdaq" to run CODA
- In
sbs-onl@eel124gemdaq: .bashrc, I changed
EXPID=EELDAQ
SESSION=EELRP
export CODA_SCRIPTS="${HOME}/SBS-GENRP/coda_scripts"
to
EXPID=COSMICDAQ
SESSION=ECALDAQ
export CODA_SCRIPTS="${HOME}/SBS-ECAL/coda_scripts"
- Create a softlink at "eel124gemdaq":
SBS-ECAL -> /adaqfs/home/sbs-onl/ecal/, and add a component table:SBS-ECAL/coda_scripts/config/ECALDAQ/coda_component_table.cfg - Change the
$COOL_HOMEand$JAVA_HOMEinSBS-ECAL/coda_scripts/setupCODA3.bash - Create a configuration "ecalcosmic" with "sbsvme22" and "hksvtp" in jceidt
- Change
$EXPIDand$SESSIONinSBS-ECAL/coda_scripts/coda_platform.sh - Modify
/etc/systemd/system/platform.serviceto point to the abovecoda_platform.sh, and restart the platform.service
Set up VTP
- Download the firmware "fe_vtp_v7_sbs_ecal.bin" and put it under
/adaqfs/home/sbs-onl/ecal/vtp/firmware - Update the DiagGUI to the latest version with ECAL implemented:
/adaqfs/home/sbs-onl/ecal/fe_diaggui/
FADC Scaler
- Scaler server auto start is set at jceidt "Expert->Supervisor Process"
