...
There will also be an offline monitoring running locally.
Computer names in the PS area
Cern is filtering ports below 1024! A work-around is to operate the sshd on port 2222 instead of 22. For the moment, I did this for pcglast37 only! Volunteers? This means that for connecting to pcglast37 ALWAYS the port has to be specified: ssh -p 2222 pcglast37.cern.ch (note the lower-case p). To use scp files, useissue: scp -P 2222 pcglast37.cern.ch (note the upper-case P ... it's not me, it's a feature).
"Socket-Gleam" PC: name pcglast37.cern.ch, IP 137.138.66.137, username online, password ** (ask somebody!). Intended for online analysis using socket-Gleam. BeamtestRelease installations are found in /data/users/online/builds. The latest build is *BR v4r0909p3 in /data/users/online/builds/BeamtestRelease-v4r0909p3-rh9_gcc32opt. For detailed instructions on how to use GLAST software, check the workbook (link?). Here, a quick list only to analyze data:
- source source /data/users/online/builds/BeamtestRelease-v4r0909p3-rh9_gcc32opt/BeamtestRelease/v4r0909p3/cmt/setup.sh
- ln -s /pathToDataDir/nameOfLdfFile.ldf file.ldf
- $GLEAMROOT/$CMTCONFIG/Gleam.exe $BEAMTEST06ROOT/jobOptions/ldf2digi.txt
- $GLEAMROOT/$CMTCONFIG/Gleam.exe $BEAMTEST06ROOT/jobOptions/readigi_runrecon.txt
With some luck, you should have digi.root, recon.root, merit.root, and calTuple.root. For creating the beamtest tuple, check $BEAMTESTTUPLEROOT/src/envVarOptions.dat. Set the appropiate env variables, and execute:
- $BEAMTESTTUPLEROOT/$CMTCONFIG/RunRootAnalyzer.exe $BEAMTESTTUPLEROOT/srv/envVarOptions.txt
"Data-server" PC: name ??? (at Pisa, was called pcglast30), IP ???pcglast30.cern.ch, IP 137.138.66.138, username online, password *** (ask somebody!). Has ca. 500GB disk space. Doesn't have a monitor. Intended as data server only. Should store the root files produced in the SLAC pipeline. We need a concept how to do it.
...