Difference between revisions of "CommonNtuple"
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
data10_7TeV.00155678.physics_MuonswBeam.recon.ESD.f261 | data10_7TeV.00155678.physics_MuonswBeam.recon.ESD.f261 | ||
data10_7TeV.00155697.physics_MuonswBeam.recon.ESD.f261 | data10_7TeV.00155697.physics_MuonswBeam.recon.ESD.f261 | ||
+ | |||
+ | monte carlo at nikpc10: | ||
+ | /data/sandstro/NTUP/MC/ | ||
short (PERSONAL) recipe how I got thing to work at lxplus: | short (PERSONAL) recipe how I got thing to work at lxplus: |
Revision as of 12:31, 9 June 2010
code:
https://svnweb.cern.ch/trac/atlasusr/browser/sandstro/CommonNtuple contains MuonESDAnalysis and MCPAnalysis
ntuples (output of MuonESDAnalysis):
at nikhef: /data/atlas2/users/egge/MuonESDAnalysis/MuonswBeam/
used datasets (status 9 June 2010):
data10_7TeV.00153565.physics_MuonswBeam.recon.ESD.r1297/ data10_7TeV.00153599.physics_MuonswBeam.recon.ESD.r1297/ data10_7TeV.00154810.physics_MuonswBeam.recon.ESD.r1297/ data10_7TeV.00154813.physics_MuonswBeam.recon.ESD.r1297/ data10_7TeV.00154815.physics_MuonswBeam.recon.ESD.r1297/ data10_7TeV.00154817.physics_MuonswBeam.recon.ESD.r1297/ data10_7TeV.00154822.physics_MuonswBeam.recon.ESD.r1299/ data10_7TeV.00155073.physics_MuonswBeam.recon.ESD.r1299/ data10_7TeV.00155112.physics_MuonswBeam.recon.ESD.r1299/ data10_7TeV.00155116.physics_MuonswBeam.recon.ESD.r1299/ data10_7TeV.00155160.physics_MuonswBeam.recon.ESD.r1299/ data10_7TeV.00155228.physics_MuonswBeam.recon.ESD.f259 data10_7TeV.00155280.physics_MuonswBeam.recon.ESD.f259 data10_7TeV.00155569.physics_MuonswBeam.recon.ESD.f260 data10_7TeV.00155634.physics_MuonswBeam.recon.ESD.f260 data10_7TeV.00155669.physics_MuonswBeam.recon.ESD.f260 data10_7TeV.00155678.physics_MuonswBeam.recon.ESD.f261 data10_7TeV.00155697.physics_MuonswBeam.recon.ESD.f261
monte carlo at nikpc10:
/data/sandstro/NTUP/MC/
short (PERSONAL) recipe how I got thing to work at lxplus:
/afs/cern.ch/user/e/egge/public/instructionsMuonESDAnalysis.txt
Production is done on lxplus batch, using FileStager to retrieve ESD's from Grid. An example of a batch job I run for production:
#!/bin/zsh source /afs/cern.ch/atlas/project/muon/software/egge/15.6.9.13/setup.sh -tag=15.6.9.13,AtlasProduction source /afs/cern.ch/user/e/egge/grid.sh cp /afs/cern.ch/user/e/egge/public/MuonESDAnalysis/readesdGrid.py . cp /afs/cern.ch/user/e/egge/public/MuonESDAnalysis/an.py . cp -r /afs/cern.ch/user/e/egge/public/MuonESDAnalysis/samples/ . cp /afs/cern.ch/user/e/egge/public/MuonESDAnalysis/input_FileStager.py . cp /afs/cern.ch/user/e/egge/public/MuonESDAnalysis/configureServices.py . ln -s samples/0155116_0.def sample.def athena -s readesdGrid.py >! log.l &
Action Items:
Just as a summary, here are the action items from our meeting. I tried to put the names of the responsible person next to it: 1) Check that all the variables are in Egge's Ntuples: a) truth info (Michele->Egge) b) Alan's variables (Giuseppe->Egge) 2) Check that all the needed MC/data is produced (all) If you're missing something, send an email to Egge stating the dq2 sample name and he will start if for you. 3) For may-reprocessing data check that all the right LB's are used as given by MCP (Alex) 4) Ks->pi pi to validate the templates for decays-in-flight (Alex) 5) MEETING FRIDAY 11 june at 10:00 (ALL) see Giuseppe's email for details
ps. I understand that there were many more requests and action-items, but agreeing with Michele I do no think that it is feasible to finish all of that before friday/monday-tuesday MCP meetings, but feel free to add items to my list.