You need to use:


in your cfg.py in place of:


You also need to remove from your cfg:


In addition, depending on the global tag used, you may need to remove the following lines from FrontierConditions_GlobalTag_noesprefer_cff.py to avoid EventSetup conflicts:

from CalibMuon.DTCalibration.DTFakeVDriftESProducer_cfi import *

You need to remove the above line only.  Don't forget to do scram b.


IDEAL alignment tag
Hi Hyunkwan.

The latest global tag for CRAFT data (intended for reprocessing) is 
CRAFT_ALL_V1.  In fact at the moment this global tag uses 
"ideal" (i.e. un-aligned) constants for muon geometry, since the new 
constants determined from CRAFT are still being finalized.  They 
should be ready in a day or two, then I will upload a CRAFT_ALL_V2 
with the aligned geometry.  So you will be able to compare these two.

However, the tracker already uses aligned geometry in CRAFT_ALL_V1, 
so if you want for consistency tracker and muon detectors non-
aligned, you should also use the ideal tag for tracker alignment on 
top of CRAFT_ALL_V1.  This can be done using the es_prefer mechanism, 
to use an alternative source to the global tag for a particular tag.

Instructions for doing this can be found here:


To pick up the ideal tracker alignment tag, you need:

from CondCore.DBCommon.CondDBSetup_cfi import *
process.trackerAlignment = cms.ESSource("PoolDBESSource",CondDBSetup,
                                         connect = cms.string
                                         toGet = cms.VPSet(cms.PSet(record = cms.string("TrackerAlignmentRcd"),
                                                                     tag = cms.string("TrackerIdealGeometry210_mc ")),
                                                          cms.PSet(record = cms.string("TrackerAlignmentErrorRcd"),
                                                                     tag = cms.string("TrackerIdealGeometryErrors210_mc"))
process.es_prefer_trackerAlignment = cms.ESPrefer



Meeting for alignment study with Martijn and Riccardo

Plan to start:

  • Send your user ID info to Riccardo, to sign up for CAF account
  • Choose a good CRAFT run from the run registry
  • Re-do Muon Reconstruction for this run, with a different alignment tag...
    (but keep the existing Muon Reco products in the events!)
    (Riccardo will send you the configuration file you should use (including DQM + instructions)
      Configuration/GlobalRuns/python/recoT0DQM_EvContent_xxx_cfg.py with xxx = [30T,38T,40T,<nothing>]

      inside there is a line
      process.GlobalTag.globaltag = "CRAFT_V3P::All" which should be changed in order to use the different alignment.

      Here there is the list with the cond tags

      For DQM, after you run the above cfg you can run:
      simply changing the input file.
  • Now you can make plots to compare the results with 'old' and 'new' alignment to see if there are differences, on event-by-event basis
    • look at number of tracks, number of hits per track, chi2, number of hits on muon part and tracker part of a global muon -- etc
  • To start we can compare the 'standard' CRAFT alignment used in the central CRAFT processing to the 'IDEAL' alignment
    • --> we will ask Rainer/Luca for the exact tag that you should use to get the 'IDEAL' alignment

-- HyunkwanSeo - 18 Nov 2008

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2008-12-01 - HyunkwanSeo
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