ST 2010 Analysis Helpline

Tags

You can find RecommendedTags here

Data

• DataType is now 2010
• XXXX.DDDBtag = "head-20100407"
• CondDBtag = "head-20100414"

Simulation

• 3.5 TeV min bias MC
• DataType is now 2010
• Remember Simulation = True

Some old tags ! For the latest look at RecommendedTags

• XXXX.DDDBtag = "head-20100119"
• CondDBtag = "sim-20100321-vc-md100""

Databases

ST VCSEL death scenarios

To simulate scenarios with TED VCSELs I made two scenarios, optimistic (96.8 % working) and pessimistic (93.7 % working)

ST Charge Calibration (Before June 2010)

Official Databases

To use:

from Configurables import ( CondDB, CondDBAccessSvc )
   stcalib = CondDBAccessSvc('stCalib')
   stcalib.ConnectionString = 'sqlite_file:/File/Type'
   CondDB().addLayer(stcalib )

In addition, I prepared various intermediate slices

Alignment

If you use ~ Brunel v37r1 era data you need to do nothing. If you use earlier versions read on

Wouter has databases in his area. Last 2009 database is tagged as v2.3, first 2010 as v2.4.

from Configurables import ( CondDB, CondDBAccessSvc )
   mycalib = CondDBAccessSvc('myCalib')
   mycalib.ConnectionString = 'sqlite_file:/afs/cern.ch/user/w/wouter/public/AlignDB/v2.4.db/LHCBCOND'
   CondDB().addLayer( mycalib )

Online

If the data is new you need to either use Oracle or Matt has a slice he trys to keep up to date (use at own risk):

from Configurables import ( CondDB, CondDBAccessSvc ) 
   myOnline = CondDBAccessSvc( 'MyOnline' ) 
   myOnline.ConnectionString = 'sqlite_file:/afs/cern.ch/lhcb/group/tracking/vol1/mneedham/ONLINE.db/ONLINE'
   CondDB().addLayer( myOnline ) 

TT Pitch fix

The pitch was wrong, a fix + fixed alignment is available. FIXED by ~ Brunel v37r1

from Configurables import ( CondDB, CondDBAccessSvc ) 
  mycalib = CondDBAccessSvc('myCalib')  
  mycalib.ConnectionString = 'sqlite_file:/afs/cern.ch/user/w/wouter/public/AlignDB/v2.4.db/LHCBCOND'
  CondDB().addLayer( mycalib )
  ttPitchFix = CondDBAccessSvc( 'TTPitchFix' )
  ttPitchFix.ConnectionString = 'sqlite_file:/afs/cern.ch/user/w/wouter/public/AlignDB/TTPitchFix.db/DDDB'

Trigger

For many studies [e.g. occupancies] you should select a trigger line.

• A Trigger twiki
• Tutorial on the trigger
• The TCK is available in the Odin bank
• There is a useful command line tool in the DaVinci environment to give the lines in the TCK : at the prompt type TCKsh, then e.g. listHlt1Lines(0x00021810)
• Or use the Online TCK presenter

To create and use a trigger filter in python you do something like:

from Configurables import LoKi__HDRFilter   as HltFilter 
trigFilter = HltFilter( 'HltPassFilter', Code="HLT_PASS('Hlt1MBMicroBiasRZVeloDecision')" )

Pileup

The 2010 simulation has nu =1. To get the pile-up in the early data:

from Configurables import LoKi__VoidFilter
fltr = LoKi__VoidFilter( 'GenFilter' , Code = " 1 == CONTAINS('Gen/Collisions') ")

Selecting Beam-Beam crossings

The following filter does the job

from Configurables import LoKi__ODINFilter  
fltr = LoKi__ODINFilter( 'O1' , Code = " ODIN_BXTYP == LHCb.ODIN.BeamCrossing " )

Removing Lumi events

The following filter does the job

# routing bit filter to remove lumi
from Configurables import HltRoutingBitsFilter
physFilter = HltRoutingBitsFilter( "PhysFilter", RequireMask = [ 0x0, 0x4, 0x0 ])

Book-keeping

• Web access
• The RecommendedTags page explains how to find information on production conditions

Field Map

There are several field maps around. Though the original maps are used the modifed maps are prefered and will be used in the future

Comments:

• I put all the maps in /afs/cern.ch/lhcb/group/tracking/vol1/mneedham/FieldMap/cdf

• You can use an Up map for Down data by putting a negative scale factor MagneticFieldSvc().ForcedSignedCurrentScaling = -1

Example 1: Using the Tosca map

from Configurables import MagneticFieldSvc
MagneticFieldSvc().UseConditions = False
MagneticFieldSvc().FieldMapFiles = ["/afs/cern.ch/lhcb/software/releases/DBASE/FieldMap/v5r3/cdf/field047.cdf"] 

Example 2: Using the up map in the conditions for down data

from Configurables import MagneticFieldSvc
MagneticFieldSvc().ForceToUseUpMap = True
MagneticFieldSvc().ForcedSignedCurrentScaling  = -1 

Example 3: Using a different set of maps

from Configurables import MagneticFieldSvc
MagneticFieldSvc().UseConditions = False
MagneticFieldSvc().FieldMapFiles = ["/afs/cern.ch/lhcb/group/tracking/vol1/mneedham/FieldMap/cdf/c1_upward_and_downward_20100112.cdf" ,
                                    "/afs/cern.ch/lhcb/group/tracking/vol1/mneedham/FieldMap/cdf/c2_upward_and_downward_20100112.cdf" ,
                                    "/afs/cern.ch/lhcb/group/tracking/vol1/mneedham/FieldMap/cdf/c3_upward_and_downward_20100112.cdf" ,
                                    "/afs/cern.ch/lhcb/group/tracking/vol1/mneedham/FieldMap/cdf/c4_upward_and_downward_20100112.cdf" ]

Nota Bene:

• In old versions of the code ForcedSignedCurrentScaling was called ScaleFactor
• Instead of ForceToUseUpMap and ForceToUseDownMap there was Polarity option [+/-1]

Links

• Lots of useful information on ST software can be found here
• Viper python scripts
• Tutorial on filters etc

-- MatthewNeedham - 08-Apr-2010