Dev on SLAC DAQ Server

The DAQ server is accessible at srv-esa-nw01 from SLAC SDF.

Prerequisites

• SLAC SDF account with SSH access (you can ssh s3dflogin.slac.stanford.edu)
• You need to be in the ldmx computing group. If ldmx is not listed in the output of groups when you SSH onto SLAC SDF. You need to ask around to find out how to get added to this group.

Only on first connection

The DAQ Server is not connected to the WAN (Wide Area Network - external internet). You can put the following in my ~/.ssh/config file so that you can access GitHub from the DAQ server.

# proxy jump for git commands on esa daq server
Host github.com
  ProxyJump rdsrv401

Test that this functions by trying to SSH to github from the DAQ server.

ssh -T git@github.com

Create an alternate "home" only on the SLAC DAQ server for all the stuff that is DAQ related.

cd /u1
mkdir ${USER}
cd ${USER}
git clone git@github.com:LDMX-Software/pflib.git

Beginning of Every Connection

Go to the alternate home and initialize the environment.

cd /u1/${USER}
source /u1/ldmx/miniforge3/etc/profile.d/conda.sh
conda activate ldmx-env-base

Note

The ldmx-env-base environment has everything you need to develop pflib. The ldmx-env environment has all this stuff and a fixed version of pflib for RunControl to access. (Although, we aren't trying to use pflib from RunControl at the moment.)

Configuring/Building/Running

cd /u1/${USER}/pflib
cmake -B build -S . # or `just configure`
cmake --build build # or `just build`
./build/pftool config/pftool/hcal-backplane-esa.yaml # or ecal-smm-esa-lN.yml for ecal layers