-
Notifications
You must be signed in to change notification settings - Fork 1
Add embedded uncertainty model #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: SMHTT2017-dev
Are you sure you want to change the base?
Conversation
| cb.cp() | ||
| .channel({"et", "mt", "tt", "em"}) | ||
| .process({"EMB"}) | ||
| .AddSyst(cb, "CMS_htt_emb_ttbar", "shape", SystMap<>::init(1.00)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$ERA postfix fehlt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sind die ganzen uncertainties korreliert ueber alle channels?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ja, die sind korreliert. das ist die uncertainty auf die menge an ttbar events die wir im embedded drin haben, das ist bei allen gleich
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
genauso CMS_htt_doublemutrg_13TeV, das ist das unfolding der selektion, und die hadronic tau track effizienzen. nur eine uncertainty gilt nur fuer tt, das bezieht sich auf den doubletau trigger-sf
| cb.cp() | ||
| .channel({"et", "mt", "tt", "em"}) | ||
| .process({"EMB"}) | ||
| .AddSyst(cb, "CMS_3ProngEff", "shape", SystMap<>::init(1.00)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$ERA postfix fehlt
| cb.cp() | ||
| .channel({"et", "mt", "tt", "em"}) | ||
| .process({"EMB"}) | ||
| .AddSyst(cb, "CMS_1ProngPi0Eff", "shape", SystMap<>::init(1.00)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$ERA postfix fehlt
| .channel({"et", "mt", "tt", "em"}) | ||
| .process(mc_processes) | ||
| .process(JoinStr({mc_processes, {"EMB"}})) | ||
| .AddSyst(cb, "lumi_$ERA", "lnN", SystMap<>::init(1.025)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wird EMB immer hinzugefuegt, wenn auch mc_processes dabei sind? Falls ja, kann man die collection mc_processes auch umbennen und es oben hinzufuegen. Falls nein, so lassen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wie funktioniert das bei embedded mit der lumi? ist ja halb MC, halb daten (und daten brauchen keine lumi uncertainty)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bei der lumi kommt es natuerlich nicht dazu.. ich korrigiere es
| using ch::JoinStr; | ||
|
|
||
| void AddSMRun2Systematics(CombineHarvester &cb, bool jetfakes, bool embedding) { | ||
| // Error-handling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wirf auch noch den comment // Error-handling weg, wir brauchen das nicht mehr.
HTTSM2017/bin/MorphingSM2017.cpp
Outdated
| bkg_procs["mt"] = {"ZTT", "ZL", "TTT", "VVT", "EWKZ", "jetFakes"}; | ||
| bkg_procs["tt"] = {"ZTT", "ZL", "TTT", "VVT", "EWKZ", "jetFakes"}; | ||
| bkg_procs["em"] = {"ZTT", "ZL", "TTT", "VVT", "EWKZ", "jetFakes"}; | ||
| if (jetfakes) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Das ist irgendwie unschoen. Embedding und fake factors modifizeren unabhaengige Prozesse (?) Dh, kann man nicht die full-MC collection von den backgrounds nehmen und je nach Option diese Collection editieren? So was ungefaehr (in C++):
bkgs = ["W", "ZTT", "QCD", "ZL", "ZJ", "TTT", "TTJ", "VVJ", "VVT", "EWKZ"]
if embedding:
bkgs = [b for b in bkgs if bkgs not in ["ZTT", "TTT"]] + ["EMB", "TTL"]
if jetfakes:
bkgs = [b for b in bkgs if bkgs not in ["QCD", "VVJ", "TTJ"]] + ["jetFakes"]There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am besten drunter noch eine kurze section, die die selektierten Prozesse printed. Sonst hab ich angst, dass wir irgendwo was vergessen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ja, finde ich gut so
HTTSM2017/bin/MorphingSM2017.cpp
Outdated
| bkg_procs["em"] = {"ZTT", "ZL", "TTT", "VVT", "EWKZ", "jetFakes"}; | ||
| if (jetfakes) { | ||
| if(embedding) { | ||
| bkg_procs["et"] = {"EMB", "ZL", "TTL", "VVT", "jetFakes"}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Embedding absorbiert EWKZ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
edit: habe nochmal geschaut, da steckt noch mehr drin als nur WWZ->mumu. ich lasse es mal drin
cdb6ad2 to
5b3b1a4
Compare
No description provided.