Nishita Desai, Manuel Drees, Herbi Dreiner, Jong Soo Kim, … · 2016-07-23 · Nishita Desai, Manuel Drees, Herbi Dreiner, Jong Soo Kim, Krzysztof Rolbiecki, Daniel Schmeier, Jamie

Nishita Desai, Manuel Drees, Herbi Dreiner, Jong Soo Kim, Krzysztof Rolbiecki,Daniel Schmeier, Jamie Tattersall

with contributions from

Sebastian Belkner, Anke Biekoetter, Tim Keller, Frederic Ponzca, Jan Schutte-Engel,Torsten Weber

MC4BSM2016, Beijing, July 22, 2016p p

CheckMATE: Confronting your Favourite New Physics Model with LHC DataDrees, Dreiner, Kim, DS, Tattersall

arXiv:1312.2591, Comput.Phys.Commun. 187 (2014) 227-265

A framework to create customised LHC analyses within CheckMATEKim, DS, Tattersall, Rolbiecki

arXiv:1503.01123, Comput.Phys.Commun. 196 (2015) 535-562

CheckMATE 2: (not) harder (but) better, faster, strongerDesai, Drees, Dreiner, Kim, Rolbiecki, DS, Tattersall

arXiv:16xx.xxxxx

K The Idea

“The idea is to create a program:You just enter a model, press a button, and it tells you whetherthe model is excluded by the LHC or not.”

“Sounds great! Let’s do it!”

Daniel Schmeier CHECKMATE

K Contents

Check Models at Terascale Energies

1 How to use CHECKMATE 1 ...... to test against results from LHC 8/13... to add new results... to estimate future results from LHC 13/14

2 How to soon use CHECKMATE 2 ...... with embedded event generation... wih greatly improved performance

K In Short

Step 1: Take simulated BSMevent files from Herwig,Pythia, CalcHEP,MG5_aMC@NLO, Whizard,Sherpa, . . .Step 2: Write a very smallparameter file param.dat,

Step 3: Run ./CheckMATEparam.dat and wait ...

## General Options[Mandatory Parameters]Name: My_CheckMATE_RunAnalyses: atlas_conf_2013_047

## Process Information[gluinopairproduction]XSect: 3.53 FBXSectErr: 0.01 PBEvents: /scratch/MSSM_gg.hep

Result: AllowedResult for r: r_max = 0.74SR: atlas_conf_2013_047 - ET

orResult: ExcludedResult for r: r_max = 1.33SR: atlas_conf_2013_047 - A

You quickly know if your model has been excluded by current LHCresults without writing a single line of analysis code

Daniel Schmeier CHECKMATE 0

K In ShortStep 1: Take simulated BSMevent files from Herwig,Pythia, CalcHEP,MG5_aMC@NLO, Whizard,Sherpa, . . .

Step 2: Write a very smallparameter file param.dat,








K In ShortStep 1: Take simulated BSMevent files from Herwig,Pythia, CalcHEP,MG5_aMC@NLO, Whizard,Sherpa, . . .Step 2: Write a very smallparameter file param.dat,








K In ShortStep 1: Take simulated BSMevent files from Herwig,Pythia, CalcHEP,MG5_aMC@NLO, Whizard,Sherpa, . . .Step 2: Write a very smallparameter file param.dat,Step 3: Run ./CheckMATEparam.dat and wait ...







K In ShortStep 1: Take simulated BSMevent files from Herwig,Pythia, CalcHEP,MG5_aMC@NLO, Whizard,Sherpa, . . .Step 2: Write a very smallparameter file param.dat,Step 3: Run ./CheckMATEparam.dat and wait ...







K Overview: Data Flow


K Input


K Input: Minimal Casecheckmate_input_parameter.dat

[Mandatory Parameters]Name: My_CMSSM_RunAnalyses: atlas_conf_2013_047

[gluinogluino]XSect: 3.53 FBXSectErr: 10 %Events: /scratch/cmssms_data/events/gg/tag1_pythia_events.hep

RequiredNameAt least one analysisAt least one [process] with at least one item in Events (.hep or.hepmc) and one total cross section and a total estimate on thesystematic error


K Input: Extended Case 1

checkmate_input_parameter.dat

[Mandatory Parameters]Name: My_CMSSM_RunAnalyses: atlas, cms_sus_13_016

[gluinogluino]XSect: 3.53 FBXSectErr: 10 %Events: /scratch/mycmssmscn/events/gg/tag1_pythia_events.hep

OptionalMore analyses


K Input: Extended Case 2checkmate_input_parameter.dat

[gluinogluino]XSect: 3.53 FBXSectErr: 10 %Events: /scratch/mycmssmscn/events/gg/tag1_pythia_events.hep,

/scratch/mycmssmscn/events/gg/tag2_pythia_events.hep

[squarksquark]XSect: 4.64 FBXSectErr: 0.25 FBEvents: /scratch/mycmssmscn/events/ss/tag1_pythia_events.hep

OptionalMany event files for one process(are processed one by one, normalised in total to the given cross section)

Events for different processes with individual σ ±∆σ(are processed one by one, normalised events independently added in the end)


K Step 1: Delphes


K Detector SimulationDelphes 3.0.10 Standard

p Simulates tracking and energy depositionp Applies efficiencies for photons and leptonsp Clusters jetsp Performs energy/momentum smearings of all

reconstructed objectsp Evaluates total missing energyp Checks isolation conditions for photons and

leptonsp Applies b-/ tau-tag on jetsp −→ see also Michele’s talk on Sunday

Extra Features / Improvementsp Added identification and isolation flagsp Tuned to better represent ATLAS detector


K Detector Tunings — Examplese reconstruction eff.

0 20 40 60 80≥ 80pT (e) in GeV

0.70

0.75

0.80

0.85

0.90

0.95

1.00’m

ediu

m’i

dent

ifica

tion

effic

ienc

y

CheckMATEATLAS

0 100 200 300 400 500 600 700 800pT (j) in GeV

0.01

0.02

0.03

0.04

0.05

light

jete

ffici

ency

CheckMATEFitATLAS

b-jet eff.

µ momentum smearing

50 100 150 200 250 300 350pT (µ) in GeV

−2.5−2.0−1.5−1.0−0.5

00.51.01.52.02.5

η(µ

)

0

10

20

30

40

50

smea

ringσp T

inG

eV

0 50 100 150 200 250pT (τ>1p) in GeV

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1.0

sign

alef

ficie

ncy

LooseMedium

Tight

CheckMATEATLAS

τ -jet eff.Daniel Schmeier CHECKMATE 6

K Step 2: Analyses


K Analyses

A CheckMATE analysis does the followingp Choose the objects of interest (leptons, jets,...)

p Filter objects (efficiency and isolation flags, kinematical cuts, overlap removals, ...)

p Check event vetoes (Too many/few objects, trigger efficiencies, ...)

p Check various signal region criteria ( total /ET , # and energy of objects, ...)

p Count number of input events that fall into each signal region

Outputp For each input file, store general information andp for each SR, store Σ (weights) and Σ( weights2) for the input

events that passed the respective signal region cuts


K Analyses

A CheckMATE analysis does the followingp Choose the objects of interest (leptons, jets,...)

p Filter objects (efficiency and isolation flags, kinematical cuts, overlap removals, ...)

p Check event vetoes (Too many/few objects, trigger efficiencies, ...)

p Check various signal region criteria ( total /ET , # and energy of objects, ...)

p Count number of input events that fall into each signal region

Outputp For each input file, store general information andp for each SR, store Σ (weights) and Σ( weights2) for the input

events that passed the respective signal region cuts


K Example Output# ATLAS-CONF-2013-047# 0 leptons, 2-6 jets, etmiss# sqrt(s) = 8 TeV# int(L) = 20.3 fb^-1

Inputfile: /hdd/results/cMSSM/delphes/000_delphes.rootXSect: 4.35 fbError: 1.22086 fb

MCEvents: 5000SumOfWeights: 5000SumOfWeights2: 5000NormEvents: 87.9518

SR Sum_W Sum_W2 Acc N_NormAL 1315 1315 0.263 23.1313AM 71 71 0.0142 1.24892BM 98 98 0.0196 1.72385BT 2 2 0.0004 0.0351807CM 505 505 0.101 8.88313CT 9 9 0.0018 0.158313D 184 184 0.0368 3.23663EL 613 613 0.1226 10.7829EM 398 398 0.0796 7.00096ET 149 149 0.0298 2.62096


K Step 3: Evaluation


K EvaluationInput and Setup

p We have number of expected signal S ±∆S in each signal regionp CheckMATE has a reference card with experimental results:

observed events Oexpected background plus uncertainty B ±∆B(in most cases) translated 95% upper limit on signal S95

max

User can choose

p Directly compare S to S95max

p If r c = S−2∆SS95

max> 1: Excluded!

p Quick and easy for limit setting

.p Evaluate CLs(O,B,∆B, S,∆S)p If CLs < 0.05: Excluded!p Slower, but limits can be set to

different confidence levels

Resultp Choose signal region with strongest expected exclusion (O = B)p Use its observed result to state final “excluded” or “allowed”





max

User can choose



max> 1: Excluded!









max

User can choose



max> 1: Excluded!






K Example

ATLAS Reference

ResultResult: AllowedResult for r: r_max = 0.74SR: atlas_conf_2013_047 - ET

atlas_conf_2013_047_r_limitsSR S dS_stat dS_sys dS_tot S95_obs S95_exp r^c_obs r^c_expAL 37.36 0.61 4.10 4.15 1341.20 1135.00 0.02 0.03AM 5.34 0.22 0.55 0.59 51.30 42.70 0.08 0.10BM 7.41 0.25 0.77 0.81 14.90 17.00 0.39 0.34BT 0.86 0.07 0.10 0.12 6.70 5.80 0.09 0.11CM 17.82 0.43 1.99 2.04 81.20 72.90 0.17 0.19CT 2.40 0.12 0.28 0.31 2.40 3.30 0.75 0.54D 12.14 0.34 1.29 1.33 15.50 13.60 0.61 0.70EL 21.26 0.46 2.35 2.39 92.40 57.30 0.18 0.29EM 16.14 0.40 1.79 1.83 28.60 21.40 0.44 0.59ET 7.95 0.28 0.87 0.91 8.30 6.50 0.74 0.95


K Example

ATLAS Reference

ResultResult: AllowedResult for r: r_max = 0.74SR: atlas_conf_2013_047 - ET



K Example

ATLAS ReferenceResultResult: AllowedResult for r: r_max = 0.74SR: atlas_conf_2013_047 - ET



K Example Input: Natural NMSSMIdea

Light g̃ , t̃, b̃, χ̃±, χ̃0 and many poss. decays [arXiv:1510.04871][Mandatory Parameters]Name: NMSSM_lambdaL_1000_800_500_250Analyses: atlas

[gluinopair]XSect: 0.239E-01 PBXSectErr: 0.00575 PBEvents: /scratch/11428609[184].pbs.baf.lan/herwig/gluinopair.hepmc

[stop1pair]XSect: 0.794E-02 PBXSectErr: 0.00149 PBEvents: /scratch/11428609[184].pbs.baf.lan/herwig/stop1pair.hepmc

[stop2pair]XSect: 0.122E-02 PBXSectErr: 0.00024 PBEvents: /scratch/11428609[184].pbs.baf.lan/herwig/stop2pair.hepmc

[sbottom1pair]XSect: 0.620E-02 PBXSectErr: 0.00119 PBEvents: /scratch/11428609[184].pbs.baf.lan/herwig/sbottom1pair.hepmc

[sbottom2pair]XSect: 0.419E-02 PBXSectErr: 0.00089 PBEvents: /scratch/11428609[184].pbs.baf.lan/herwig/sbottom2pair.hepmc


K Example Output: Nat. NMSSM

~: ./CheckMATE NMSSM_setupfile.txt

____ _ _ __ __ _ _____ _____/ ___| |__ ___ ___| | _| \/ | / \|_ _| ____|

| | | ’_ \ / _ \/ __| |/ / |\/| | / _ \ | | | _|| |___| | | | __/ (__| <| | | |/ ___ \| | | |___\____|_| |_|\___|\___|_|\_\_| |_/_/ \_\_| |_____|

[... roughly 2 minutes per 5k events later ... ]

******************************************* EVALUATION *******************************************

Test: Calculation of r = signal/(95%CL limit on signal)Result: ExcludedResult for r: r_max = 3.45937SR: atlas_conf_2013_061 - SR1L6JB



~: ./CheckMATE NMSSM_setupfile.txt

____ _ _ __ __ _ _____ _____/ ___| |__ ___ ___| | _| \/ | / \|_ _| ____|

| | | ’_ \ / _ \/ __| |/ / |\/| | / _ \ | | | _|| |___| | | | __/ (__| <| | | |/ ___ \| | | |___\____|_| |_|\___|\___|_|\_\_| |_/_/ \_\_| |_____|

[... roughly 2 minutes per 5k events later ... ]

******************************************* EVALUATION *******************************************

Test: Calculation of r = signal/(95%CL limit on signal)Result: ExcludedResult for r: r_max = 3.45937SR: atlas_conf_2013_061 - SR1L6JB



Scan Parameter RegionGen. events for each param. point (Trivial, once the setup is ready)Run CheckMATE on these events (Trivial, just change event-URL)Draw line between Excluded and Allowed (Trivial with Matplotlib)

200 300 400 500 600 700 800 900 1000mt̃1

in GeV

100

150

200

250

300

350

mχ̃

0 1 in

GeV

Most Sensitive Analysis + robs limit

Most Sensitive Analysis

other

atlas_1407_0583

atlas_1404_2500

atlas_1403_4853

atlas_1308_2631

atlas_conf_2013_062

atlas_conf_2013_061

atlas_conf_2013_024


K Performance Test via ModelsEffective DM via atlas_1502_01518 UED via atlas_conf_2013_089

100 101 102 103

mDM in GeV

300

400

500

600

700

800

900

1000

Λef

fin

GeV

CheckMATEATLAS

700 750 800 850 900 950 100010501100

10

20

30

40

Λ·R

1/R in GeV

CheckMATEATLAS

Simple SUSY via cms_1303_2985 MSUGRA via atlas_conf_2013_047

400 600 800 1000 1200 1400

200

400

600

800

1000

1200

Neu

tralin

om

ass

inG

eV

Gluino mass in GeV

CheckMATECMS

1000 2000 3000 4000 5000 6000

400

500

600

700

800

900

m1/

2in

GeV

m0 in GeV

CheckMATEATLAS

CheckMATE is a model-independent tool!


K Performance Test via ModelsEffective DM via atlas_1502_01518 UED via atlas_conf_2013_089

100 101 102 103

mDM in GeV

300

400

500

600

700

800

900

1000

Λef

fin

GeV

CheckMATEATLAS

700 750 800 850 900 950 100010501100

10

20

30

40

Λ·R

1/R in GeV

CheckMATEATLAS

Simple SUSY via cms_1303_2985 MSUGRA via atlas_conf_2013_047

400 600 800 1000 1200 1400

200

400

600

800

1000

1200

Neu

tralin

om

ass

inG

eV

Gluino mass in GeV

CheckMATECMS

1000 2000 3000 4000 5000 6000

400

500

600

700

800

900

m1/

2in

GeV

m0 in GeV

CheckMATEATLAS

CheckMATE is a model-independent tool!


K Performance Test via Cutflows

atlas_1405_7875 and g̃ → qq′χ̃±, χ̃± →W±χ̃0

Signal Region D Signal Region ETCut ATLAS Ch.M. ATLAS Ch.M.

Generated Monte Carlo events 20,000 50,000 20,000 50,000In % 100 % 100 % 100 % 100 %Jet cleaning * 99.8 % - 99.8 % -0 lepton * 63.7 % - 63.5 % -/ET≥ 160 GeV 50.0 % - 55.6 % -pT (j1) > 130 GeV 49.3 % 47.7 % 55.6 % 54.4 %pT (j2) > 130 GeV 49.2 % 47.6 % 55.6 % 54.4 %pT (j3) > 60 GeV 48.6 % 47.1 % 55.4 % 54.2 %pT (j4) > 60 GeV 44.5 % 43.8 % 53.4 % 52.8 %pT (j5) > 60 GeV 34.4 % 34.8 % 46.3 % 46.6 %pT (j5) > 60 GeV (only ET) 34.4 % 34.8 % 31.7 % 33.0 %∆φ(j1,2,3, /ET ) > 0.4 29.2 % 29.5 % 26.5 % 27.5 %∆φ(jk , /ET ) > 0.2 ∀k with pT (jk ) > 40 GeV 24.6 % 24.7 % 21.3 % 22.4 %/ET /meff(all jets) > 0.2(D), 0.25(ET) 21.6 % 21.2 % 12.0 % 11.2 %meff(all jets) > 1.6 TeV(D), 1.5 TeV(ET) 2.0 % 1.9 % 7.9 % 8.2 %Monte Carlo Error ±0.1 % ±0.1 % ±0.2 % ±0.1 %


K α / Fully Validated AnalysesName Search designed for

√s L NSR

atlas_1308_1841 new phenomena in final states with large jet multiplicities and /ET 8 20.3 19atlas_1308_2631 third-generation squark pair production with /ET and two b-jets 8 20.1 6atlas_1402_7029 charginos and neutralinos in events with 3 leptons and /ET 8 20.3 24atlas_1403_4853 top-squark pair production in final states with two leptons 8 20.3 12atlas_1404_2500 SUSY with jets and two same-sign leptons or three leptons 8 20.3 5atlas_1403_5222 top squark pair production in events with a Z boson, b-jets and /ET 8 20.3 5atlas_1405_7875 squarks and gluinos in final states with jets and /ET 8 20.3 15atlas_1407_0583 stop pair production in final states with one isolated lepton, jets, and /ET 8 20.3 27atlas_1407_0608 pair-produced third-generation squarks decaying via charm quarks or

in compressed supersymmetric scenarios8 20.3 3

atlas_1502_01518 new phenomena in final states with an energetic jet and large /ET 8 20.3 9atlas_1503_03290 Supersymmetry in events containing a same-flavour opposite-sign dilep-

ton pair, jets, and large /ET8 20.3 1

atlas_1506_08616 pair production of third-generation squarks 8 20.3 11atlas_conf_2012_104 Supersymmetry in final states with jets, /ET and one isolated lepton 8 5.8 2atlas_conf_2012_147 new phenomena in monojet plus /ET final states 8 10 4atlas_conf_2013_024 production of the top squark in the all-hadronic tt̄ and /ET final state 8 20.5 3atlas_conf_2013_049 direct-slepton and direct-chargino production in final states with two

opposite-sign leptons, /ET and no jets8 20.3 9

atlas_conf_2013_061 strong production of supersymmetric particles in final states with /ETand at least three b-jets

8 20.1 9

atlas_conf_2013_089 strongly produced supersymmetric particles in decays with two leptons 8 20.3 12atlas_conf_2015_004 invisibly decaying Higgs boson produced via vector boson fusion 8 20.3 1cms_1303_2985 supersymmetry in hadronic final states with missing transverse energy

using the variables αT and b-quark multiplicity8 11.7 59

cms_1408_3583 dark matter, extra dimensions, and unparticles in monojet events 8 19.7 7cms_1502_06031 BSM physics in events with two Leptons, jets, and /ET 8 19.4 6cms_1504_03198 production of dark matter in association with top-quark pairs in the

single-lepton final state8 19.7 1

cms_sus_13_016 new physics in events with same-sign dileptons and jets 8 19.5 1


K β / Partially Validated AnalysesName Search designed for

√s L NSR

atlas_1210_2979 WW production 7 4.6 1atlas_1403_5294 charginos, neutralinos and sleptons with 2 leptons and /ET 8 20.3 13atlas_1407_0600 strong production of SUSY particles with /ET and at least 3 b-jets 8 20.1 9atlas_1411_1559 new phenomena in events with a photon and /ET 8 20.3 1atlas_conf_2013_021 WZ production 8 20.3 4atlas_conf_2013_031 spin properties of h in h → WW (∗) → eνµν 8 20.7 2atlas_conf_2013_036 Supersymmetry in events with four or more leptons 8 20.7 5atlas_conf_2013_062 squarks and gluinos in events with isolated leptons, jets and /ET 8 20.1 19atlas_conf_2014_014 t̃ t̃∗ decaying to a b, a τ and weakly interacting particles 8 20.3 1atlas_conf_2014_033 WW production 8 20.3 3atlas_conf_2014_056 spin correlation in top–antitoptt̄ events and search for t̃ t̃∗ 8 20.3 1cms_1301_4698_WW WW production 8 3.5 1cms_1306_1126_WW WW production 7 4.92 1cms_1405_7570 electroweak production of charginos, neutralinos and sleptons de-

caying to leptons and W, Z, and Higgs bosons8 19.5 57

cms_smp_12_006 WZ production into 3` 8 19.6 4cms_sus_12_019 physics beyond the standard model in events with two opposite-

sign same-flavor leptons, jets, and missing transverse energy8 19.4 4

atlas_conf_2015_062 squarks and gluinos in final states with jets and /ET 13 3.2 7atlas_conf_2015_067 g̃ g̃ decaying via stop and sbottom in events with b-jets and /ET 13 3.3 8atlas_conf_2015_076 gluinos in events with an isolated lepton, jets and/ET 13 3.3 6atlas_1602_09058 SUSY with jets and 2 same-sign leptons or 3 leptons 13 3.2 4

atl-phys-pub-2014-010-sbottom

SUSY at the high lumi LHC with zero leptons, two b-jets and /ET 14 300 6

atlas-phys-pub-2013-011-stop

SUSY at the high lumi LHC with zero or one lepton 14 300 4

atlas_2014_010_hl_3l SUSY at the high lumi LHC with 3 ` + /ET 14 3000 9atlas_phys_2014_010_300 SUSY at the high lumi LHC with jets + /ET 14 300 10atlas_phys_2014

_010_sq_hlSUSY at the high lumi LHC with jets and /ET 14 3000 10

What do I need to add a new analysis on my own?p Ability to answer questionsp Some understanding of C++



√s L NSR












What do I need to add a new analysis on my own?

p Ability to answer questionsp Some understanding of C++



√s L NSR












What do I need to add a new analysis on my own?p Ability to answer questionsp Some understanding of C++


K The Analysis Manager

Running the Analysis Managerp Run make AnalysisManager; /bin/AnalysisManager

____ _ _ __ __ _ _____ _____/ ___| |__ ___ ___| | _| \/ | / \|_ _| ____|

| | | ’_ \ / _ \/ __| |/ / |\/| | / _ \ | | | _|| |___| | | | __/ (__| <| | | |/ ___ \| | | |___\____|_| |_|\___|\___|_|\_\_| |_/_/ \_\_| |_____|

/\ _ _ | _. _ |\/| _ _ _ _ _ _/--\| )(_||\/_)|_) | |(_|| )(_|(_)(-|

/ _/

What do you want?-(l)ist all analyses,-(a)dd a new analysis to CheckMATE,-(r)emove an analysis from CheckMATE]



Adding an analysisa

This will collect all necessary information to create a full analysis andTakes care for the creation and implementation of the source files into the code.Please answer the following questions.Attention: Your input is NOT saved before you finish this questionnaire.1. General Information to build analysisAnalysis Name:

ATLAS_1234_5678Description (short, one line):

ATLAS: many leptons, few jetsDescription (long, multiple lines, finish with ’;;’ on a new line):

ATLASmany leptons, few jetssqrt(s) = 9 TeVint(L) = 42 fb^-1;;

Luminosity (in fb^-1):42

Do you plan to implement control regions to that analysis? [(y)es, (n)o)n



Adding an analysis2. Information on Signal RegionsList all signal regions (one per line, finish with ’;;’ on a new line):1l2l

[...]Is the SM expectation B known? [(y)es, (n)o]?

yYou now have to add thenumbers for each of thegiven signal regions.1lobs:100

bkg:90

bkg_err:15

2lobs:200

bkg:180

bkg_err:30

[...]

nSignal regions are registered but without anynumbers associated to them.IMPORTANT: The analysis will be created and canthen be used like any other analysis.CheckMATE will skip the model exclusiontests as long as the expectation is notknown. You can e.g. use CheckMATE on backgroundsamples to estimate B and dB. As soon asyou know these numbers, run theAnalysisManager again and use the (e)ditfeature to add them.

Add a published analysisp Provide results straight

awayp Typical mode for 8 and

13 TeV

Add a new analysisp run on SM backgrounds firstp add these results to CMp Typical mode to project to 13 and 14

TeV and to invent new cutflows



Adding an analysis2. Information on Signal RegionsList all signal regions (one per line, finish with ’;;’ on a new line):1l2l

[...]Is the SM expectation B known? [(y)es, (n)o]?

yYou now have to add thenumbers for each of thegiven signal regions.1lobs:100

bkg:90

bkg_err:15

2lobs:200

bkg:180

bkg_err:30

[...]

nSignal regions are registered but without anynumbers associated to them.IMPORTANT: The analysis will be created and canthen be used like any other analysis.CheckMATE will skip the model exclusiontests as long as the expectation is notknown. You can e.g. use CheckMATE on backgroundsamples to estimate B and dB. As soon asyou know these numbers, run theAnalysisManager again and use the (e)ditfeature to add them.

Add a published analysisp Provide results straight

awayp Typical mode for 8 and

13 TeV

Add a new analysisp run on SM backgrounds firstp add these results to CMp Typical mode to project to 13 and 14

TeV and to invent new cutflows



Adding an analysis3. Settings for Detector Simulation3.1: MiscellaneousTo which experiment does the analysis correspond? (A)TLAS, (C)MSA

3.2: Electron IsolationDo you need any particular isolation criterion? [(y)es, (n)o]y

Isolation 1:Which objects should be considered for isolation? [(t)racks, (c)alo objects?t

What is the minimum pt of a surrounding object to be used for isolation? [in GeV]5

What is the dR used for isolation?0.4

Is there an absolute or a relative upper limit for the surrounding pt? [(a)bsolute, (r)elative]a

What is the maximum surrounding pt used for isolation [in GeV]?20

Do you need more isolation criteria? [(y)es, (n)o]n

3.3: Muon IsolationDo you need any particular isolation criterion? [(y)es, (n)o]n

3.4: Photon IsolationDo you need any particular isolation criterion? [(y)es, (n)o]n



Adding an analysis3.5: JetsWhich dR cone radius do you want to use for the FastJet algorithm?0.4

What is the minimum pt of a jet? [in GeV]10

Do you need a separate, extra type of jet? [(y)es, (n)o]n

Do you want to use b-tagging? [(y)es, (n)o]y

b-Tagging 1:What is the signal efficiency to tag a b-jet? [in %]70

Do you need more b tags? [(y)es, (n)o]y

b-Tagging 2:What is the signal efficiency to tag a b-jet? [in %]40

Do you need more b tags? [(y)es, (n)o]n

Do you want to use tau-tagging? [(y)es, (n)o]n



Adding an analysis- Variable values saved in /hdd/sandbox/managertest/data/atlas_conf_2013_047X_var.j- Created source file /hdd/sandbox/managertest/tools/analysis/src/atlas_conf_2013_047X.cc- Created header file /hdd/sandbox/managertest/tools/analysis/include/atlas_conf_2013_047X.h- Updated Makefile- Updated main source main.cc- Reference file created- List of analyses updatedAnalysis atlas_conf_2013_047X has been added successfully!Run ’make’ from the main CheckMATE folder to compile it!


K Some example lines

void Atlas_conf_2013_047::analyze() {missingET->addMuons(muonsCombined);electronsLoose = filterPhaseSpace(electronsLoose, 10., -2.47, 2.47);muonsCombined = filterPhaseSpace(muonsCombined, 10., -2.4, 2.4);jets = filterPhaseSpace(jets, 20., -2.8, 2.8);[...]jets = overlapRemoval(jets, electronsLoose, 0.2);electronsLoose = overlapRemoval(electronsLoose, jets, 0.4);if(!electronsLoose.empty())

return;[...]double HT = 0.;for(int j = 0; j < jets.size(); j++)

HT += jets[j]->PT;double mEffInc = missingET->P4().Et() + HT;[...]mEffA = missingET->P4().Et() + jets[0]->PT + jets[1]->PT;if (missingET->P4().Et()/mEffA > 0.2) {

countCutflowEvent("AL1");if (mEffInc > 1000.)

countSignalEvent("AL");}[...]


K What to do for CheckMATE 2?

We want to start early in the chain

Name: NMSSM_600_200Analyses: atlas

[gluinopair]XSect: 0.239E-01 PBXSectErr: 0.00575 PBEvents: /scratch/gluinopair.hepmc

N FRITZ = Flexible Rapid Interactive Tool Zipper N

We want to be fast

[... roughly 2 minutes per5k events later ... ]




Goal←→ RealityName: NMSSM_600_200Analyses: atlas



We want to be fast





So far the user has toprovide the eventfiles

Why not embed

event generation

within CheckMATE?

Name: NMSSM_600_200Analyses: atlas



We want to be fast






Why not embed

event generation

within CheckMATE?Name: NMSSM_600_200Analyses: atlas



We want to be fast






Why not embed

event generation




We want to be fast

Goal←→ Reality [... roughly 2 minutes per5k events later ... ]





Why not embed

event generation




We want to be fast

Simulations are slow

Try to speed upwhatever possible






Why not embed

event generation




We want to be fast

Simulations are slowTry to speed upwhatever possible






Why not embed

event generation




We want to be fast

Simulations are slowTry to speed upwhatever possible



K Old CheckMATE 1


K ...New CheckMATE 2 somewhat ready


K Working Pythia8 Functionalities

Example 1: Use Pythia on SLHA in specific SUSY production modesName: MSSM_GluinoPairAnalyses: cms & 8TeVSLHAFile: myspectrum.slha

[gluinopair]Pythia8Process: p p > go go~

Example 2: Provide .in file with arbitrary Pythia settings

Name: MSSM_SquarkPairAnalyses: atlas & 8TeV

[squ_squ]Pythia8Card: /scratch/files/pythiasqusqu.in

PDF:pSet = 8 !(CTEQ6L1)Beams:idA = 2212Beams:idB = 2212Beams:eCM = 8000.SLHA:file = /scratch/files/point.slhaSUSY:qq2squarksquark = onSUSY:idVecA = 1000001,1000002,[...]2000003,2000004

Example 3: Use Pythia to shower .lhes of an arbitrary modelName: NewModelTestAnalyses: atlas & 8TeV, cms & 8 TeV

[Supermodel]Events: test_events/mysupermodel_point1.lhe






















K CheckMATE 2.X In Development

Experimental

Publications

efficiencies

analysis

procedures

number of

expected and

observed events

Pythia

MadGraph

Delphes- Simulate track reconstruction and energy deposits

- Perform energy/momentum smearings on reconstructed objects

- Cluster jets

- Evaluate total missing energy

Analysishandler- Apply identification efficiencies for photons and leptons

- Apply tagging efficiencies for b- and tau-jets

- Checks isolation conditions that are required for the various analyses

- Generate SUSY events or shower provided .lhe files

- Merge .lhe files with different jet multiplicities

- generate .lhe files for SUSY model (soon: any model)

partonic LHE files

showered HepMC event object

detector level objects

CheckMATE analysis objects

- Perform overlap removals, trigger efficiencies, kinematical cuts

- Follow experimental analyses as closely as possible

- Count how many events fall into various signal regions

- Find signal region with largest expected exclusion potential

- compare expected signal to experimental observation

Analyses

EvaluationOutput

Input Possibility B

- For all signal regions...

... theoretical signal / experimental upper limit

... CLs(signal, background, observed)

- State if input is excluded or allowed

FRITZ

CheckMATE

- SUSY process and/or .in Pythia settings file

- SLHA file

- optionally: cross section or K-faktor

Input Possibility C- .lhe files

- if needed, matching scheme


Input Possibility A- SUSY process (soon: any process)

- SLHA file


Input Possibility D- .hep or .hepmc events

- cross sections

Input Possibility E- Delphes .root files

- cross sections


K Under DevelopmentExample 4: Shower and Merge Multiple LHEName: ZplusjetsAnalyses: atlas_1403_5222

[Zjets]Merging: ckkwlScale: 30MaxJets: 2Events: test_events/zRes_0jet_1k.lhe, test_events/zRes_1jet_1k.lhe, test_events/zRes_2jet_1k.lhe

Example 5: Link to MG5_aMC@NLOName: InertHiggsDoubletTestAnalyses: atlas & 8TeVMG5Model: InertDoubletSLHAFile: /scratch/my_inert_spectrum.slha

[a_h]MG5Process: p p > a hMaxEvents: 10000

Mode 5 already working in most simple way (see tutorial)In Development: proper tool combination via Pythia8’sLHAupMadGraph class see Philip’s Talk from WednesdayCheckMATE still simple to use via ./CheckMATE input.txt














K Other Features of 2.0Faster Event Procession

sizable speed boost (Now: ≈ 30s for creating 1000 events andtesting one analysis, 1 min for testing all analyses)Much better cluster performance

Fritz: Initialising handlers from file $CMDIR/results/ThesisExample/fritz/squ_squ.iniPythiaHandler ’pythia’: Initializing Pythia8 with $CMDIR/bin/thesisexample/pythiasqusqu.inPythiaHandler ’pythia’: Output redirected to $CMDIR/results/ThesisExample/pythia/pythia_squ_squ.logPythiaHandler ’pythia’: Pythia8 initialized successfully!DelphesHandler ’atlas8tev’: Initialising Delphes via linking to PythiaHandler ’pythia’[...]DelphesHandler ’cms8tev’: Delphes successfully initialised!AnalysisHandler ’atlas8tev’: Initialising AnalysisHandlerAnalysisHandler ’atlas8tev’: Loading Analysis atlas_1308_1841AnalysisHandler ’atlas8tev’: Successfully loaded analysis atlas_1308_1841[...]AnalysisHandler ’cms8tev’: AnalysisHandler successfully linked to DelphesHandler ’cms8tev’Fritz: Fritz successfully loaded command line parameters!Fritz: >> Successfully initialized and linked all handlers! <<Fritz: Starting event loop!Fritz: Progress: 10 %[...]Fritz: Progress: 100 %Fritz: >> Finalising after 1000 events. <<PythiaHandler ’pythia’: Pythia8 returned cross section of 2.43366 fbAnalysisHandler ’atlas8tev’: Analyses successfully finished!DelphesHandler ’cms8tev’: Delphes successfully finished!PythiaHandler ’pythia’: Pythia8 successfully finished!Fritz: >> Done <<


K Conclusions

Go ahead and have a look!

http://checkmate.hepforge.org/

and maybe see you later for the tutorial!

In which case, please download the VM (2 GB) beforehand fromhttp://checkmate.hepforge.org/16_07_MC4BSM/CheckMATE.vdi.zip

orhttp://alturl.com/3eabh


http://checkmate.hepforge.org/

http://checkmate.hepforge.org/16_07_MC4BSM/CheckMATE.vdi.zip

http://alturl.com/3eabh

Appendix


Documents

Nishita Desai, Manuel Drees, Herbi Dreiner, Jong Soo Kim, … · 2016-07-23 · Nishita Desai, Manuel Drees, Herbi Dreiner, Jong Soo Kim, Krzysztof Rolbiecki, Daniel Schmeier, Jamie