Local Offline Overview
The The local offline processes LDF into digi and uses calibrations that are installed in the SLAC database to produce reconstructed and high level data analysis files. The goal is to have a way to quick debug and characterize the beam during the set-up. If there is a copy of the database locally then we can use it to process events even when the connection to SLAC is down.
...
Computer names in the PS area
Cern is filtering ports below 1024! A work-around is to operate the sshd sshd is running 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, issue: scp -P 2222 pcglast37.cern.ch (note the upper-case P ... it's not me, it's a feature)by default. I was setting it on 2222 temporarily, but this was not appreciated. Hence, the computers are not accessible from outside CERN.
"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:
...
- $BEAMTESTTUPLEROOT/$CMTCONFIG/RunRootAnalyzer.exe $BEAMTESTTUPLEROOT/srv/envVarOptions.txt
For updating the calibration database description and the external libraries, there is a simple script ~online/bin/syncWithSLAC. It asks for your SLAC afs user name and password, runs rsync, and destroys the afs token again.
"Data-server" PC: name 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.
...