Gain Ratios

I have written a macro to measure gain ratios from beam

It is in CVS, UserCode/Torino/Ecal/TestBeam/User/EcalTBAnalyzer/macros/


measureGainRatio.C

note that one has to fix run numbers in ntuples by adjustRunNumber.C

The python writeStdGainRatioFile.py
takes a standard gain ratio file and, using the ouput of measureGainRatio, writes
a gain ratio file in the right format.

ssh tunneling to CERN

Two methods can be used:

1. modify ssh client configuration file
.ssh/config

#
#Usage:
#ssh -N -f -q lxtunnel; ssh pccmsto02

Host lxtunnel
HostName lxplus.cern.ch
User argiro
LocalForward 7777 pccmsto02.cern.ch:22
LocalForward 7778 pccmsto03.cern.ch:22
LocalForward 7779 lxcmsf3.cern.ch:22

Host pccmsto02.cern.ch
HostName localhost
User argiro
Port 7777


Host pccmsto03.cern.ch
HostName localhost
User argiro
Port 7778


Host lxcmsf3.cern.ch
HostName localhost
User argiro
Port 7779

then do :

ssh -Nfq lxtunnel this opens the tunnel

then you can normally ssh to lxcmsf3, or the other machines you have configured

2. Manual tunneling

ssh -L 7777:lxcmsf3.cern.ch:22 lxplus.cern.ch

meaning "forward requests to localhost:7777 to lxcmsf3".
In another window do

ssh -p7777 localhost

ECALTB06 analysis and submission howto

CMSSW 1_1_0, plus ECALTBH4_0_1_0
https://twiki.cern.ch/twiki/bin/view/CMS/ECALTBH4

Never versions coming sometime

Packages

User/EcalTBAnalyzer
User/EcalTBAnalyzerData
RecoTBCalo/EcalTBRecProducers

should be extracted from http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/UserCode/Torino/Ecal/TestBeam/

or CVS


go to the production area:

User/EcalTBAnalyzer/data
run `eval scramv1 runt -csh`
run the sumbission script

./tbsubmit_single -c tbanalysis-sm16.cfg.tmpl -r files-sm16.txt -e lxcmsf3:/data/argiro/ecaltb2

where

-c file is the configuration template
-r file is the file containg the list of files (runs) to be processed
-e dir is the destination directory, to be created ahead of time

bjobs can be used to monitor, dummye and dummy will contain stdout and stderr
of the job submission, while processing logs will be in the destination dir

It is a good idea to stage files from castor first

csa07_stager.py -r filelist -s


Analysis macros are in User/EcalTBAnalyzer/data

runxtals.C -> produces files containing only one xtal. Must be modified to select which xtals
select_xtal.C(xtal, dir) -> select one single xtal (used by runxtals)
lin.C -> the do-it-all analysis macro

TBNtuple.h is needed from User/EcalTBAnalyzerData/interface

Work - 4 Ott

TB: energies of some runs were missing in enerUff.txt file, that were discarded by select_xtal
Warning added, have to check that all useful runs have energy value

PhiSim: running onlin phisim on MinBias sample w/ raw and L1 info

DAQ: converting matric to xdata::vector

Work - 1 Oct 07

Testbeam

Bug found in analysis code: TBNtuple.h was present in dir too, and was the one linked -> posx was
always zero. Have to reprocess

./tbsubmit_single.py -c tbanalysis-sm16.cfg.tmpl -f files-sm16.txt -e lxcmsf3:/data/argiro/ecaltb2/sm16-v2


another bug fixed. Committed to cvs

Work - 27 Sett 07

1. Ran ecaltb sm16-v1, last version of macros copied to laptop, not commited to CVS (previously in pccmsto03:/store/argiro/ecaltb2/sm16-v1, with old ntuples (buggy))
2. last ntuples also on lxcmsf3:/data/argiro/ecaltb2/sm16-v1
   
3. tried running macro ... better but still problems
4. phi sim: verified chain w/ Andrea. To understand:
   
1. miscalibration
2. the eventSet=1 option: does it have to run after ?
5. Lesson on grad, rot, div. Stoke's teo and Div teo to be done
   

Today's work

DAQ meeting
planning w/ Nadia
Fixed with Andrea stager_qry and get (has to be run on lxplus)
Scripts put in CVS under Calibration/EcalCalibAlgos/scripts
Finished setup to run testbeam analisys

Linearity note in CVS

the draft linearity note is in CVS

from outside Cern:

export CVS_RSH ssh
export CVSROOT :ext:argiro@cmscvs.cern.ch/cvs_server/repositories/CMSSW

cvs co -d linearitynote UserCode/Torino/Ecal/linearitynote


from inside Cern do "project CMSSW" instead of the "exports"

Ecaltb stuff in CVS

I've put in CVS the ecaltb stuff
go to the CMSSW_1_5_2 project dir and do
cvs co -d src UserCode/Torino/Ecal/TestBeam
this will checkout subsystems in the right place

Today's work

1. Discussion w/ Meridiani on online Physim
1. phisym needs to be an item in the trigger menu
2. we need to establish which L1 trigger is our source. In absence of MinBias emulator we can use zerobias, or the method of any L1em candidate (iso/noniso). This could be advatageous over MinBias, because it would use regional unpacking
3. By the joint trigger/detector wshop we need to summarize timing
2. EcalTB analysis
1. Ported code under CMSSW_1_5_2
2. tidy up submission scripts

TODO: weights configuration for sm06

Today's work

1. Adjust ecaltb job submission for CSA07 PhiSym
2. Tidy up ecaltb code in ~/w0/ecaltb
   
1. moved Ntuple definition out of .cc code
2. included g6 nonlin corrections