Updating Tile_maskedDB_Run2.conf with final Run 2 status
While the JetTileCorrectionTool is not recommended for general use by Jet/EtMiss, it is a useful and centralised way to determine which jets are pointing at (or near) dead tile modules in data & simulation. I am updating the configuration file used to determine which modules have been disabled in certain data runs, and including the various disabled modules in our MC campaigns.
For reference -- The tool is documented on this TWiki: https://twiki.cern.ch/twiki/bin/view/AtlasProtected/JetTileCorrectionTool
... and in this note: https://cds.cern.ch/record/2226554
The information I am including was taken from this HCW2019 contribution: https://indico.cern.ch/event/798446/contributions/3435678/attachments/1846094/3028917/PawelKlimek_TileCal_2019-05-15.pdf