Tracker Maps from eos
This document describes how to use the Tracker Maps from eos scripts provided in the repository :
https://github.com/amandeephy/StripTkMaps
.
Setup
To run in a CMSSW area (10_X_Y or higher):
cmsrel CMSSW_10_4_0
cd CMSSW_10_4_0/src
cmsenv
git cms-init
git cms-addpkg DQM/SiStripMonitorClient
cd DQM/SiStripMonitorClient/scripts
Once done, you should copy the
TkMaps_from_eos and
Ext_functions_from_eos to your scripts/ directory. Change the default output locations by modifying the
tkrunspath and
evedispath. You can also change the location of where the DQM file is temporarily copied, (say the /tmp/ directory) by editing the
filepath.
Running the script
To run the script :
python TkMaps_from_eos
--Run_type <Cosmics | ZeroBias | StreamExpress | StreamExpressCosmics>
--Run_number <List of valid integers>
--File_name <This option allows for directly using an xrootd file >
--Output_loc <Location of eos output>
--ML <Boolean (default : False)>
Filename is not required and can be reconstructed in the downloadfromeos function in the Ext_functions_from_eos script.
The --ML flag requires the config file :
StripDQM_OfflineTkMap_Template_cfg_ML.py
Alongside the tracker maps this should create a list of attributes of all modules. The updated
SiStripTrackerMapCreator.cc now allows for the number of top modules printed in the top modules log file (numTopModules) to be unsigned integer, passing a -1 will create a dump of all strip variables in
TopModules.log.
--
AmandeepSinghBakshi - 2020-02-28