Changes to my Analysis Code

My working areas

  • /afs/cern.ch/user/v/venturia/scratch0/dev/CMSSW_4_2_0_pre7
  • /afs/cern.ch/work/v/venturia/CMSSW_4_2_8_SLHCtk3_patch1
    • ad hoc working area for pixel phase 1 inefficiency problem studies. It could be removed
  • /afs/cern.ch/work/v/venturia/CMSSW_5_3_3/src
    • several cfg changes and some changes in the code to add debug printout. No real development.
  • /afs/cern.ch/work/v/venturia/CMSSW_5_3_13_patch1/src
    • Production working area. No real development not committed yet
  • /afs/cern.ch/work/v/venturia/CMSSW_6_1_1_SLHCphase1tk1/src
    • ad hoc working area for pixel phase 1 inefficiency problem studies. It could be removed
  • /afs/cern.ch/work/v/venturia/CMSSW_6_2_0_pre7/src
    • Used to debug OOT pileup
  • /afs/cern.ch/work/v/venturia/CMSSW_6_2_0_pre8/src
    • Used to debug OOT pileup
  • /afs/cern.ch/work/v/venturia/CMSSW_6_2_0_patch1/src
    • Production working area. No real development not committed yet
  • /afs/cern.ch/work/v/venturia/CMSSW_6_2_0_SLHC9
    • Production working area.
  • /afs/cern.ch/work/v/venturia/CMSSW_7_0_3_patch2/src
    • Production working area.
  • /afs/cern.ch/work/v/venturia/CMSSW_7_1_0_pre5/src
    • Production working area.

For SiStrip monitoring

  • /afs/cern.ch/cms/tracker/sistrcalib/MonitorConditionDB/CMSSW_4_4_3
    • Used to monitor the DB content. It contains few changes about the size of the histogram plot and of the tracker map which are not propagated to git
  • /afs/cern.ch/cms/tracker/sistrcalib/MonitorConditionDB/CMSSW_5_3_14
    • Most update working area based on git to monitor DB content. Everything is pushed in github
  • /afs/cern.ch/cms/tracker/sistrcalib/MonitorConditionDB/CMSSW_7_0_4
    • Most updated working area based on git to monitor DB content in the 7_0_X cycle. Everything is pushed in github
  • /afs/cern.ch/cms/tracker/sistrcalib/MonitorConditionDB/CMSSW_7_1_0_pre6
    • Most updated working area based on git to monitor DB content in the 7_1_X cycle. Everything is pushed in github

For TrackingPFG

  • /afs/cern.ch/cms/tracking/workareas/CMSSW_4_2_5
  • /afs/cern.ch/cms/tracking/workareas/CMSSW_4_2_8_patch7
    • "official" TrackingPFG 4_2_X area. No special development ongoing
  • /afs/cern.ch/cms/tracking/workareas/CMSSW_4_2_9_HLT3_hltpatch3
  • /afs/cern.ch/cms/tracking/workareas/git_workareas/CMSSW_4_4_5_patch3
    • "official" TrackingPFG 4_4_X area. No special development ongoing
  • /afs/cern.ch/cms/tracking/workareas/git_workareas/CMSSW_5_3_11
    • "official" TrackingPFG 5_3_X area. No special development ongoing
  • /afs/cern.ch/cms/tracking/workareas/git_workareas/CMSSW_6_2_0
    • "official" TrackingPFG 6_2_X area. No special development ongoing
  • /afs/cern.ch/cms/tracking/workareas/git_workareas/CMSSW_7_0_3_patch2
    • "official" TrackingPFG 7_0_X area. No special development ongoing

TrackingPFG

Tags/branches to be used

  • 71x: in git my-71x
  • 70y: in git trackingpfg-70x or my-70x to get everything, even the packages which are in CMSSW
  • 62x: in git my-62x to get everything, even the packages which are in CMSSW
  • 53x: in git my-53x to get everything, even the packages which are in CMSSW
  • 52x: V52x-00-02
  • 51x: V51x-00-01
  • 44x: in git my-44x to get everything, even the packages which are in CMSSW
  • 42x:
  • 39x: V_399_00_00

DPGAnalysis/SiStripTools

Tags to be used

  • 42x: V00-08-03-18 (it requires 4_2_8 or later) APVShotAnalyzer not updated
    • V00-08-03-00-01: minimal to introduce multiplicity filter
  • 44x: Branch my-44x in git
    • V00-09-12-09 (before 4_4_2) APVShotAnalyzer not updated
    • V00-09-00-00: minimal to introduce multiplicity filter
  • 5xy: Branch my-53x in git
    • V00-11-23 (not fully updated: DetIdSelectorTest, FEDBadModules)
    • V00-10-10-01: minimal to introduce multiplicty filters in tag mode
    • V00-10-10-07: minimal to introduce the use of ClusterSummary and the new threshold on the number of strip clusters for the ALCARECO
  • 60x: V00-12-08 (it requires CommonTools/UtilAlgos V00-02-12)
    • V00-11-23 (not fully updated: DetIdSelectorTest, FEDBadModules)
    • V00-10-10-01: minimal to introduce multiplicty filters in tag mode
    • V00-10-10-06: minimal to introduce the use of ClusterSummary
  • 61x: V00-12-08
  • 62x: Branch my-62x in git
  • 7xy: HEAD of CMSSW_7_0_X and CMSSW_7_1_X branches

Tests to be done

  • New filter configurations in official working area

General

  • Improve use of const
  • Add module selector class
  • Add class to fill digi/cluster profiles
  • Review the binning of the profiles vs time: use LS as quantum

Macros and Scripts

  • Move in the package the macros in the tracking afs areas

New Developments

  • Producer for per event histograms (cluster charge) to be added by the analyzers

EventWithHistory

  • Add protections against unphysical BX numbers: warning
  • Transform into a warning the message when there is an offset change
  • Do not fill EventWithHistory when there is an inconsistency: unphysical BX number

DigiLumiCorrHistogramMaker

  • Add per fill histograms of cluster vs lumi

DigiVertexCorrHistogramMaker

  • Add per fill histograms of cluster vs lumi

EventWithHistoryFilter

  • allow negative values in range
  • allow multiple latency and mode (OR)

APVCyclePhaseMonitor

  • transform histograms into RunHistograms

APVShots

  • Evolution of the mean median vs time
  • Add single shot/event debug options
  • Define APV shot selector
  • Factorize class that fills histograms

DigiTimeCorrelations

  • Class for the filling of DBXDebugging
    • Fill the "-1" DBXDebugging histos with ALL the events (if no cut)
  • Add the multiplicity plot in the event part or remove it completely since it is in the DigiInvestigator

Validation/RecoVertex

Tags to be used

  • 7_x_y: use validation_recovertex-70x git branch or my-70x
  • 6_2_x: use my-62x git branch
  • 5_3_x : my-53x git branch
  • 5_1_x : V00-13-05-05-02
  • 4_4_x : V00-13-04-04-17
    • V00-13-04-04-17 for 4_4_0
  • 4_2_x :
    • V00-13-04-04-14 (with 4_2_8 and later releases)
    • V00-13-04-04-07 (before 4_2_8)

General

  • Review the binning of the vs time profiles: use LS as quantum
  • Per fill histograms of PV multiplicity vs lumi

My Code in UserCode/VenturiA

My CVS tags

  • V02-00-00 last tag used with 2_2_6
  • v01-00-00 last tag used with 2_1_12
  • v00-01-00 before the introduction of the history in the future
  • v00-00-01 before the code reorganization:
    • DataFormats no more separated
    • use of plugins directories

Tags to be used

UserCode/VenturiA/DebugTools
  • 7xy: use trackingpfg-70x or my-70x git branch
  • 62x: use my-62x git branch
  • 53x: use my-53x git branch
  • 52x: V52x-00-00
  • 51x: V51x-00-02
  • 44x: V44x-00-02
  • 42x: V42x-00-02

UserCode/VenturiA/trackCount/TrackCount
  • 7xy: use trackingpfg-70x or my-70x git branch
  • 62x: use my-62x git branch
  • 53x: use my-53x git branch
  • 52x: V52x-00-00
  • 51x: V51x-00-00
  • 44x: V44x-00-00
  • 42x:

UserCode/VenturiA/tracking/TrackRecoMonitoring
  • 7xy: use trackingpfg-70x or my-70x git branch
  • 62x: use my-62x git branch
  • 53x: use my-53x git branch
  • 52x: V52x-00-00
  • 51x: V51x-00-00
  • 44x: V44x-00-00
  • 42x:

General

  • use beginJob without argument
  • use CommonTools/UtilAlgos/interface/TFileService.h
  • use SiStripQuality to reject digis from bad modules
  • being able to fill SiStripQuality with a user-defined module list
  • Split TEC+ and TEC-
  • Move histogram booking in beginRun
    • introduce a tag here? A new branch?
  • Add to the EDAnalyzer which can analyze the summary products, the possibility to filter the events with the HistoricizedEventFilter
  • Add struct dictionary to the data formats

To Be Removed

  • BigEvents: now in DPGAnalysis/SiStripTools
  • myTools: check about summary products
  • ModuleWithXXX: now in DPGAnalysis/SiStripTools

Maps

  • Improve the interface to create the map in beginRun, fill it in produce and save it in endRun
  • Do I need a CommonModule class for the detid?
  • List of concrete classes from BasicModule
    • MultiplicityFloatModule
      • it contains a float which has to be added when add is used
      • usually the CommonStructure is filled with its value normalized to the number of entries
    • MeanFloatModule
      • it contains a float with the average value and an integer with the number of events used to compute the mean
      • add should provide the proper combined mean
      • CommonStructure will be filled with the value returned by getValue
    • Max/MinFloatModule
      • it contains the maximum/minimum value. add should choose the maximum/minimum between the two objects to be combined
      • CommonStructure will be filled with the value returned by getValue
  • mergeProduct must work
  • dedicated methods to Load them into CommonStructure
  • interface to TempMeas to create the proper Measurement based on the BasicModule concrete class
  • EDProducers to be (re)done and tested
    • DigiMap
      • it has to produce the same kind of maps with the new classes
    • UnpackBadListMap

trackCount/TrackCount/TrackCount

  • review binning
    • number of hits
  • add histograms
    • 2D eta,phi (and pt)
    • TProfile2D Nhit vs eta/phi (and pt)
  • Add Tracks vs MC lumi histograms
  • Add Tracks vs reco vertices histograms
  • track properties vs pileup/luminosity/nvtx

trackCount/ClusterChargeInvestigator/ClusterChargeInvestigator

  • Add another cluster multiplicity distribution with a narrower range when inclusive clusters and analyzed

-- AndreaVenturi - 03 Apr 2009

Edit | Attach | Watch | Print version | History: r87 < r86 < r85 < r84 < r83 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r87 - 2014-04-25 - AndreaVenturi
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback