-
Notifications
You must be signed in to change notification settings - Fork 4
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
Testing v6 ntuples #290
Comments
My condor jobs have finished for v6, and I am starting to look at the logs. |
There are 151590 data events (from all 2016 data sets combined) which are suspect and may have this issue.
|
Ok, it looks like 151573 events have MET_pt = 0.0.
|
2018 Data event with disagreement in passing MET cut
|
This is probably a ">" vs. ">=" issue for this 2018 event. The MET_pt = 0.0 issue for Data is only seen in 2016. |
Definition of Pass_MET stored in ntuples: https://github.com/susy2015/NanoSUSY-tools/blob/dev_v6/python/modules/Stop0lBaselineProducer.py#L225 Definition of SAT_Pass_MET in SusyAnaTools: https://github.com/susy2015/SusyAnaTools/blob/master/Tools/baselineDef.cc#L689 |
Both definitions use "met >= 250" . This may be a rounding issue... maybe the full precision value was less than 250, but the rounded value saved in the ntuples is 250.0. |
Testing 2016 for tag PostProcessed_StopNtuple_v6.1.1. Events with difference in selection (framework vs. ntuples):
|
Instances of NOT_EQUAL:
|
Using the v6 nuples and the top tagger “discriminator filter” module and the top candidates from the ntuple, we have agreement in number of tops for all events in:
SMS_T1tttt_mGluino2000_mLSP100_fullsim_(2016,2017,2018)
However, when running over Data_SinglePhoton_2016_PeriodB, we see this problem:
The text was updated successfully, but these errors were encountered: