CMS Wiki Pages - phase2

bensnotes

Anonymous (anonymous@undisclosed.example.com) — 2015-01-09T14:33:57+00:00

A short description from Ben: # delphes-cups.tgz had my local delphes area from git # note that it is big because it has 1 GB MC files in the genevt directory # the card I was running was in delphes/Delphes/Cards # example of extending eta of muon detectors to 4 CMS_PhaseI_PU50_muPOGeff-eta4.tcl # example of extending eta of muon detectors to 3 CMS_PhaseI_PU50_muPOGeff-eta3.tcl delphes-cups.tgz # tklayout.env is the environment that points to both my local tklayout area # and the dis…

bjets

Anonymous (anonymous@undisclosed.example.com) — 2015-01-26T15:48:21+00:00

Few events occur for track transverse momenta over 60 GeV with most resolution discrepancy for tracks with pT between 1.0 and 10.0 GeV. Momentum chosen for transverse impact momentum (d0) resolutions at points: TKG_MOMENTA=“1.00, 2.00, 5.00, 20.00

bjetvariabledist

Anonymous (anonymous@undisclosed.example.com) — 2015-01-27T13:27:51+00:00

Transverse momentum of b-jet tracks (tracks matched within a cone of dR<0.5 from jet axis) for HH->WWbb Transverse momentum of b-jet with a cut of pT > 20 GeV b-jet track multiplicity track IP versus track pT (all tracks)

different_scenarios

Anonymous (anonymous@undisclosed.example.com) — 2015-01-27T16:23:08+00:00

Different configurations of the Pixel Detector have been studied to determine which one would be the best wrt pt and impact parameter resolution for tracks. For the tracks we are interested in the pt range compatible with the one of tracks coming from a b-hadron decay (pt~ 3.5 GeV).

experts

Anonymous (anonymous@undisclosed.example.com) — 2015-01-28T08:42:44+00:00

Expert groups Basics Impact parameters * export impact parameter resolutions from tklayout * import impact parameter resolutions into our analysis code * to calculate impact parameters in analysis * smear impact parameter resolutions in analysis code * calculate a b-tagger based on impact parameters Analysis * b-jet ID * tau ID * photon ID * signal analysis * background analysis * Delphes batch scripts * jet selection * flavor identification of jets from truth lev…

ipanalysis

Anonymous (anonymous@undisclosed.example.com) — 2015-01-27T20:36:57+00:00

[Efficiency versus discriminant cut for the track with the highest impact parameter in jet] [Efficiency versus discriminant cut for the track with second highest impact parameter in jet] [Efficiency versus discriminant cut for the track with third highest impact parameter in jet]

jetresolution

Anonymous (anonymous@undisclosed.example.com) — 2015-01-27T11:30:07+00:00

Default Delphes jet configuration:

layers

Anonymous (anonymous@undisclosed.example.com) — 2015-01-26T15:58:42+00:00

To remove the 3rd layer in the Technical Proposal, I commented out in PixelTechnicalProposal2014.cfg the lines : // Layer 3 { // radiusMode fixed // placeRadiusHint 109 // } The original resolution is: pt 1000 Real 2.30948 Ideal 0.53651 Loss 4.3

layout

Anonymous (anonymous@undisclosed.example.com) — 2015-01-26T16:48:12+00:00

To change the layer length in the BPix you want to change the number of modules per half rod in the “Barrel PXB” section of PixelTechnicalProposal2014.cfg: Barrel PXB { numLayers 4 numModules 4 <---------------- this what you want to change innerRadius 29 outerRadius 161 width 22 <------------ this is the module length along x (local x) length 71 <-------------- this is the module length along z (local y) ..... }

material

Anonymous (anonymous@undisclosed.example.com) — 2015-01-27T10:36:33+00:00

A simple test to figure out what the material parameters do: Use Technical proposal benchmark as reference: Default material is written down in this file: tkgeometry/config/stdinclude/PixelMaterials.cfg M Si 0 0 0 0.3 mm L ; pt 1000 Real 2.30948 Ideal 0.53651 Loss 4.3

modules

Anonymous (anonymous@undisclosed.example.com) — 2015-01-28T08:58:51+00:00

Titled modules We can tilt the pixel barrel modules around their transverse axis by specifying the coordinates of each module. The syntax is as follows: Barrel PXB { numLayers 4 //numModules 4 maxZ 205 <--- need to specify maxZ if using titled modules innerRadius 29 outerRadius 161 width 22 length 71 smallParity 1 bigParity -1 Layer 2 { tiltedLayerSpecFile pixel_BL2_tilt.csv } <--- reference file of module coordinates here Layer 3 { radiusMode fixed…

old_phase2

Anonymous (anonymous@undisclosed.example.com) — 2015-01-15T17:59:23+00:00

Alternative Delphes instructions Getting the software * You can either use the CMS “short-version” or the official version of Delphes. The CMS version contains Detector Cards for the Phase 2 detector layout with 140 PU and is recommended for our purposes.

old_tklayout

Anonymous (anonymous@undisclosed.example.com) — 2015-01-16T14:55:19+00:00

Obs! The official version of tkLayout does not include Delphize, a separate tool needed to convert tkLayout output into format readable by Delphes. If you intend to use tkLayout at the UZH CMS Phase 2 Workshop, go to tkLayout with Delphize. Getting the software

phase2

Anonymous (anonymous@undisclosed.example.com) — 2015-03-02T13:05:45+00:00

Phase 2 Upgrade Studies Phase 2 Workshop January 26-27 A two day workshop (Indico) will be held at the end of January with the aim of exploring what can be achieved with a better CMS detector for Phase 2 LHC. For these studies we will be using the Delphes fast simulation framework overlaid with

photons

Anonymous (anonymous@undisclosed.example.com) — 2015-01-27T11:41:34+00:00

Electron ID pT > 10GeV abs(eta) < 2.5 and not in {1.44,1.56} Barrel isolationVar < 0.15 H/E < 0.015 End Caps isolationVar <0.15 Muon ID pT > 10 abs(eta) < 2.4 isolationVar > 0.15 Photon ID pT > 20GeV abs(eta) <2.5 and not in {1.44,1.56} Barrel

resolution

Anonymous (anonymous@undisclosed.example.com) — 2015-01-26T11:57:35+00:00

A simple test to figure out what the pixel hit resolution parameter does: Use Technical proposal benchmark as reference: Default pixel resolution is written down in this file: tkgeometry/config/stdinclude/ModuleTypes/pixel resolutionLocalX 0.013 resolutionLocalY 0.028

tracker_resolution

Anonymous (anonymous@undisclosed.example.com) — 2015-01-27T08:54:13+00:00

Removing one layer from the tracker: layer 2 TBPS. Barrel TBPS { numLayers 2 <---- previously 3 maxZ 1150 startZMode moduleedge compressed true innerRadius 230 ...} Impact parameter resolution is almost identical to the Technical Proposal. Slight improvement in the pt resolution due to the reduction of material budget.