Closed vargasa closed 4 years ago
This is the expected behaviour in files that contain no event in which that trigger was in the menu. There is no predefined trigger list stored in NanoAOD, the set of triggers is discovered dynamically and branches are created to accommodate only the bits that are found in the input file.
@vargasa HLT_TkMu50
is present from run 274954 on. I split 2016B in two parts for my analysis to deal with this, also in the DAS query with run between
(you can get this kind of information from brilcalc trg
- I wrote a script to parse the output and get more readable output for a list of triggers, I can push it somewhere if it can be useful also for other people).
@peruzzim thanks for the info! @pieterdavid it would be certainly be useful, can I find it somewhere on your repos? Thanks a lot!
@vargasa I uploaded them as snippets on gitlab: just the run ranges and with prescales (there may be better tools around for this - I wrote them for my own use, so there may be bugs)
Dear NanoAOD experts,
For the NanoAODv6 and v7
2016B
Dataset the content of theEvents
TTree
seems to be inconsistent. The branchHLT_TkMu50
is present in some root files but not in others even when looping through the same dataset. I was expecting theTTree
to have the same content through the entire dataset but that doesn't seem to be the case. For a more detailed version for v6 this please check (1). However, I see the same pattern on02Apr2020
release, check das query here.This is a sample, there are more files missing the branch. It is possible to verify this by running:
If this is not the right place for this issue, Can you please provide insights on where to place it or feedback if those files can be safely ignored/skipped ?
As always, thanks a lot!