Top_SM meeting
  • Things to have a look at for events having different charges for the two algorithms
    • Event display
    • Hit distribution


Comments from lepton meeting
  • Hit resolution setting affects track finding algorithm. Larger resolution setting will yield more hits.
  • Can find the correct hit resolution value by looking at saturation of hit numbers by varying resolution value. However this method is meaningful when alignment is done perfectly.
  • It is better to compare charge (+/-) distribution for the two algorithms.


Tried to use the recomended global tag (refering to the following 'Global run discussion' e-mail)
  • tried to read raw data of run 58537 with CRUZET4_V4P::All , but no difference is found from the previous results obtained from reco data
  • plan to read this week data

Dear all,

a new global tag for this week run has been produced:

CRUZET4_V4P::All (prompt reco/prompt analysis)
CRUZET4_V4H::All (online/hlt)

which includes new ECAL and sistrip conditions. For a detailed list please
have a look at:

For DataOps, this global tag can be used for promptreco with the cfg file in:

cvs co -r  1.19 Configuration/GlobalRuns/python/recoT0DQM_EvContent_cfg.py

please consider use the above pair (globaltag/cfg) for any processing.

         Andrea and l.

-- HyunkwanSeo - 05 Sep 2008

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2011-12-22 - GunmoRyu
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding KoreaCmsWiki? Send feedback