Tracking Studies with DataMixer


Currently working on 4_4_0.

cvs co -d edwenger/HiVertexAnalyzer UserCode/edwenger/HiVertexAnalyzer
cvs co -d edwenger/HiTrkEffAnalyzer UserCode/edwenger/HiTrkEffAnalyzer
cvs co -d  MitHig/PixelTrackletAnalyzer UserCode/MitHig/PixelTrackletAnalyzer/
cvs co -r hi44X_04 -d SimGeneral/DataMixingModule UserCode/yetkin/SimGeneral/DataMixingModule
cvs co HeavyIonsAnalysis/Configuration
cvs co -d CmsHi/Analysis2010 UserCode/CmsHi/Analysis2010
cvs co -d PbPbTrackingTools/HiTrackValidator UserCode/ASYoon/PbPbTrackingTools/HiTrackValidator
cvs co -d PbPbTrackingTools/VertexConstraintProducer UserCode/ASYoon/PbPbTrackingTools/VertexConstraintProducer

Problematic python configuration: /net/hisrv0001/home/yetkin/hidsk0001/mix/calo01_d1123/

Samples (with parentage)

Mother of All : RAW (MIT, Global)
  • /HICorePhysics/StoreResults-HICorePhysics_Skim_MinimumBias_RAW-a606dc809a29a92e17749e5652319ad0-SD_MBHI/USER
  • /pnfs/

PreMix Min Bias (MIT, ph_analysis_01)

  • /HICorePhysics/yilmaz-MinBias_PreMix_440_test26-2a3fd0a01656fd762e353d50bd946d2c/USER
  • /pnfs/
  • Scripts: svmithi01:/d101/yetkin/prod/test29_mbPreMix

Pion Flat pt = 0 - 200 GeV (MIT, Private)
  • /pnfs/
  • Scripts: /net/hisrv0001/home/yetkin/hidsk0001/mix/pion1_DBS_d0931

Ntuples & Histograms
  • /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks1_DBS_d0931/test.root
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks1_DBS_d0931
  • /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks1_DBS_d0931/signal01/signal.root
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks1_DBS_d0931/signal01

Pythia pthat > 170 GeV (MIT, Private) : Submitted
  • /pnfs/
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/pythia170_d0931

Ntuples & Histograms
  • /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_pythia170_d1009/test.root
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_pythia170_d1009
  • /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_pythia170_d1009/signal01/signal.root
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_pythia170_d1009/signal01

PreMix HLT_HIJet50U, 0 - 10%

  • /HICorePhysics/yilmaz-Jet50U_0to10_PreMix_440_test32-f17fd2ed8b87d0940b5b303282977643/USER
  • Scripts: /d101/yetkin/prod/test32_Jet50U_0to10_preMix

Pion Flat pt = 0 - 200 GeV (MIT, Private), pion pt < jet pt, for jets in all acceptance and all pt.
  • /pnfs/
  • Scripts: /net/hisrv0001/home/yetkin/hidsk0001/mix/probeJet_d1008

Ntuples & Histograms
  • /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_probeJet_d1009/trees_*.root
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_probeJet_d1009
  • /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_probeJet_d1009/signal01/signal_*.root
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_probeJet_d1009/signal01

Pion Flat pt = 0 - 200 GeV (MIT, Private), pion pt not limited by jet pt, jets |eta| < 2.8 , pt > 30 GeV
  • /pnfs/
  • Scripts: /net/hisrv0001/home/yetkin/hidsk0001/mix/probeJet_d1010

Ntuples & Histograms
  • /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_probeJet_d1010/trees_*.root
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_probeJet_d1010
  • /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_probeJet_d1010/signal01/signal_*.root
  • Scripts : /net/hisrv0001/home/yetkin/hidsk0001/mix/tracks_probeJet_d1010/signal01

PreMix HLT_HIJet50U

Not ready

PreMix 0 - 10%

Not ready

Progress Log

pt distribution of MC input : Unresolved

Currently we embed pions with flat pt. How good is this, when we want to make comparisons with data? We can start embedding pythia events, however, if the embedding is done in the direction of the jet, embedding another full jet into it may not be good. If we want a realistic pt distribution in particle gun events, should we use the PtYDistributorGun, or should we keep producing flat and reweight in analysis? If we will use the PtYDistributorGun, Andre has to generate a text input file such as:

ProbeGenerator : Track into jet or bad APV mixing : Unresolved

Yetkin will implement a generator that creates the pion in the direction of the jet or an interesting APV.

Sanity of results : Unresolved

We need to compare the track parameter distributions (particularly those related to vertex compatibility) and check how realistic they are.

High pT efficiency : October 6, 2011 : Unresolved

The tracking efficiency (by rough pt spectrum comparison) drops very rapidly at highest pt in the flat pt pion sample. The pt resolution is not sufficient to explain the effect: EfficiencyMixing_d1005.gif
  • Need to plot efficiency properly.
  • Need to investigate issues with vertexing.

Memory Problem : October 6, 2011 : Unresolved

Currently running pion gun with more than 20 events per job causes a crash. Sometimes crash is explicitly reporting std::bad_alloc, sometimes not as clear. The VectorInputSource implementation in 440 was promising better performance. Is there a leak somewhere?

Note: It is crucial how many events per job are run, because one input file can be only consumed by single job.

Status : October 6, 2011


HBHE crash : September 2011 : Solved by removing the ZDC part and use digi mixing

  • configuration : /net/hidsk0001/d00/scratch/jazzitup/eventMixing/CMSSW_4_4_2_patch5/test/test1/

  • Error message
23-Nov-2011 10:40:01 EST  Successfully opened file file:/mnt/hadoop/cms/store/user/yilmaz/HICorePhysics/MinBias_PreMix_440_test26/2a3fd0a01656fd762e353d50bd946d2c/MinBias_PreMix_185_1_sNh.root
shared pointer ok
pointer ok
isource 1
isource 2
isource 3
%MSG-e FatalSystemSignal:  DataMixingModule:mixData 23-Nov-2011 10:40:02 EST  Run: 152047 Event: 61104
A fatal system signal has occurred: segmentation violation

A fatal system signal has occurred: segmentation violation
The following is the call s

#0  0x0000003f5289a115 in waitpid () from /lib64/
#1  0x0000003f5283c481 in do_system () from /lib64/
#2  0x00002b899b01a2a2 in TUnixSystem::StackTrace() ()
   from /afs/
#3  0x00002b899c594b33 in sig_dostack_then_abort ()
   from /afs/
#5  0x00002b89aecee2fe in CaloTDigitizer::run(MixCollection&, edm::SortedCollection >&) ()
   from /afs/
#6  0x00002b89aece460b in HcalDigitizer::produce(edm::Event&, edm::EventSetup const&) ()
   from /afs/
#7  0x00002b89af0dc202 in edm::DataMixingModule::put(edm::Event&, edm::EventSetup const&) ()
   from /home/yilmaz/CMSSW_4_4_0_B/lib/slc5_amd64_gcc434/
#8  0x00002b899955d55b in edm::EDProducer::doEvent(edm::EventPrincipal&, edm::EventSetup const&, edm::CurrentProcessingContext const*) ()

ESDigiCollection_ecalPreShowerDigis : September 2011 : Unresolved

The standard event content of datamixing (DATAMIXEREventContent) has:

'keep ESDataFramesSorted_ecalPreshowerDigis_*_*', 
but datamixer asks for:

I added keep of the DigiCollection as well to my cfg.

VectorInputSource : September 2011 : Resolved

The parameter passed into the bind should be the number of events, not the bunch crossing:

  boost::bind(&DataMixingModule::pileWorker, boost::ref(*this),
                             _1, bunchCrossing, _2, boost::cref(ES)),
Temporarily this works:
  boost::bind(&DataMixingModule::pileWorker, boost::ref(*this),
                             _1, 1, _2, boost::cref(ES)),

DataMixingSiStripRawWorker : September 2011 : Resolved

Changing the main loop that produces the output rawDigis

At the moment the code is generating as output the collection of the data and on top of that is simply added the signal of MC. This creates inconsistency in the reco using the MC GT. The code should be able to do the opposite and add on top of the MC modules, the data modules adcs.

  Looping over adding to produce
Previously the code was Data rawDigis MC Digis MC rawDigis
Now we want MC Digis Data rawDigis MC rawDigis

Memory optimization of temporary vectors and maps : Resolved

The changes that were made to provide the above introduced big memory problem. It produces huge vectors and maps. We have to optimize the code. The problem was due to forgetting to increment the iterator and filling up infinitely! In any case, we made the code more efficient by using DetSetVector properly instead of homemade map.

ZDC change : Resolved

Head of DataMixingModule can only be used with 4_4_X due to ZDCRecHit dataformat change.


Input RAW sample : September 2011 : Resolved

We use minimum bias skim of HICorePhysics. The reason I couldn't find the RAW before is I only looked for AllPhysics out of habit.

Preparing crab jobs : September 2011 : Testing

In interactive jobs, we guarantee the equality of the primary and secondary source by adding the line:
process.mixData.input.fileNames = process.source.fileNames
into the cfg file. However, crab executes the input cfg file only in the job preparation, and the input file name actually changes later for the job in the working node. One has to add this line back again to the final cfg that crab creates.

Solution: When preparing crab jobs execute:

detector condition coustomization





Muon chambers

Edit | Attach | Watch | Print version | History: r16 < r15 < r14 < r13 < r12 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r14 - 2011-11-28 - YenJieLee
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

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