Fan Xia Home Page:

• http://smodels.hephy.at/wiki/ListOfAnalyses
• CMS Supersymmetry Physics Results: https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhysicsResultsSUS
• SUSY Cross Section: https://twiki.cern.ch/twiki/bin/view/LHCPhysics/SUSYCrossSections
• RUN2 MC Cross Section: https://twiki.cern.ch/twiki/bin/viewauth/CMS/SummaryTable1G25ns

• 8TeV AN -Brian Francis Twiki: https://twiki.cern.ch/twiki/bin/view/Main/ARCReviewSUS15009
• Run1 SUSYPhotonStopBinoPrivateMC and slha files: https://twiki.cern.ch/twiki/bin/viewauth/CMS/SUSYPhotonStopBinoPrivateMC

• Run2 Cutbased Photon ID: https://twiki.cern.ch/twiki/bin/viewauth/CMS/CutBasedPhotonIdentificationRun2
• Run2 Cutbased Electron ID: https://twiki.cern.ch/twiki/bin/viewauth/CMS/CutBasedElectronIdentificationRun2
• Run2 EgammaPFBasedIsolation: https://twiki.cern.ch/twiki/bin/view/CMS/EgammaPFBasedIsolationRun2
• Run2 Muon ID: https://twiki.cern.ch/twiki/bin/view/CMS/SWGuideMuonIdRun2
• Btag in Analysis: https://twiki.cern.ch/twiki/bin/viewauth/CMS/BtagRecommendation

• ggNtuplizer: https://twiki.cern.ch/twiki/bin/view/CMS/ggNtuplizer
  • Github: https://github.com/cmkuo/ggAnalysis
  • ggNtuple production: https://docs.google.com/spreadsheets/d/1yDiNc4PB5sUb6p25BXSRn8K3qYu7XmDYaD_2lS2n0RU/edit#gid=1862737812

• Run2 SUSY signal MC:
  • SUSY group signal list: https://indico.cern.ch/event/379687/contribution/1/attachments/757478/1039091/Signal_proposal__10.3.pdf
  • SUSY signal production for run2: https://github.com/CMS-SUS-XPAG/GenLHEfiles/tree/master/Run2Mechanism
  • SUSY group signal stored at:
  • How to produce private susy signal:

• pt(top-quark) based reweighting of ttbar MC: https://twiki.cern.ch/twiki/bin/viewauth/CMS/TopPtReweighting

1 Data pileup is calculated by using the corresponding pileup JSON file by masking lumi sections out of the certain datasets. An important parameter is the minibias cross section. Now recommend is 69000+-5%, I used 69400, and 80000 was said being under review for run2. (The current results show the larger one in better, say 71000 is much better than 69000)

2 MC pileup is simulated based on the expected data pileup, but not accurate sometime(like the runII_spring _74x_mc, produced before the runII data taking, much like guess, pretty off). The same MC campaign (the same cmssw version), should has the same pileup input, which can be found in the cmssw pdf directly.

3 Get the pileup weight factor depends on the TrueNumInteractions(puTrue in ggNtuples) by data_pu/mc_pu

4 Apply the pu weight factor to the mc samples, using the nVtx to test to see how the data the mc agree.

The follows plots use data JSON: Cert_246908-260627_13TeV_PromptReco_Collisions15_25ns_JSON_Silver_v2.txt

MC pdf: mix__2015__25ns__Startup__PoissonOOTPU__cfi_8py_source.html from CMSSW_7_4_15_patch1

True PU distributions:

Before PU, the nVtx probability distributions

After PU, the nVtx probability distribution

The first steps are the same as To_Load_the_New_Timing_Parameter

• Log on to P5

pro
xmas
source setup_trigger_trans.sh
pwd

• This takes you to:

/nfshome0/ecalpro/trigger_config/CMSSW_5_2_3_TRANS/src/CalibCalorimetry/EcalTPGTools/test

• An example of script generating parameters:

produceTPGParameters_beamv6_transparency_spikekill.py

• dry run:

writeToDB = cms.bool(False),

• To update OMDS (online database). Switch on the "writeToDB". And the DB will be updated.

writeToFiles = cms.bool(True),

• Here we set the High interest: 2.5 GeV & Low interest: 1.5 GeV, change the parameters as the following lines:

 TTF_lowThreshold_EB = cms.double(1.5), ## EB Trigger Tower Flag low threshold in GeV
 TTF_highThreshold_EB = cms.double(2.5), ## EB Trigger Tower Flag high threshold in GeV
 TTF_lowThreshold_EE = cms.double(1.5), ## EE Trigger Tower Flag low threshold in GeV
 TTF_highThreshold_EE = cms.double(2.5), ## EE Trigger Tower Flag high threshold in GeV

• Execute the config below, then you will get the Output text file TPG_beamv6_trans_spikekill.txt (you can edit the output filename in the script as well) with the new TPG param updated

cmsRun produceTPGParameters_beamv6_transparency_spikekill_2015.py

• Open the Output file TPG_beamv6_trans_spikekill.txt to check the parameters, search for LUT until you find the lines below:

LUT 0
0x0
0x0
0x0
0x0
0x1
0x1
0x1
0x1
0x2
0x2
0x2
0x2
0x103
0x103
0x103
0x103
0x104
0x104
0x104
0x104
0x305
0x305
...

• The last digit of each line shows the ADC counts, convert it to Et by mutiplying 0.5 GeV /ADC. The third digit from right is the TTF. So, 0x0 presents 0 ADC which converts to 0 GeV, goes to zere suppression region with TTF=0, here we omit the 0 (it should look like 0x000 by principle), 0x104 presents 4 ADC which converts to 2.0 GeV, TTF=1, and 0x305 presents 5 ADC which converts to 2.5GeV, TTF=3.
• Why we have the same text printed four times? The original ADC are 10 digits binary with the last two digits for decimals part which have four possibilities .00, .01,.10, .11), while convert to Et, the decimal parts are left out, but each possibility still counts, so we get the "exact" same lines four times.