Difference: SplitClusterStudy (1 vs. 11)

Revision 112017-12-19 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Line: 29 to 29
 git remote add hunyadix git@github.com:hunyadix/cmssw.git git fetch hunyadix git checkout -t hunyadix/ModForPixelMerger
Changed:
<
<
...
>
>
git clone git@github.com:hunyadix/PhaseISplitClusterAnalyzer.git DPGAnalysis/PhaseISplitClusterAnalyzer scram b -j 20
 

Generating a CMSSW config file

Line: 91 to 92
  Running the HistogramMerger is as simple as checking out the git repository and specifying the target files and the output name in src/main.cxx.
Added:
>
>

Tests

  • The pixel markers are seemingly present for all the cluster pixels when the pileup is 0 (1). The function checkDetIdToMarkerPtrMap() is currently run for each of the events and it prints out how many of the clusters have a corresponding marker.
  • In the analyzer testPairFinding() tests the private areClustersPair() for pair finding efficiency. Seems like the pair finding works just fine if the cluster objects have properly set x, y and size fields.
 

Results

TTbar events, no pileup, 95% dcol efficiency statistics files:

Revision 102017-12-18 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Changed:
<
<
>
>
 
Line: 21 to 21
 
export SCRAM_ARCH=slc6_amd64_gcc530
cmsrel CMSSW_9_3_0_pre1
Changed:
<
<
cd CMSSW_9_3_0_pre1src
>
>
cd CMSSW_9_3_0_pre1/src
 cmsenv git cms init git cms-addpkg SimTracker /SiPixelDigitizer

Revision 92017-12-15 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Line: 58 to 58
  For no PU, I usually generate TTbar events.
Deleted:
<
<

Running the HistogramMerger

Running the HistogramMerger is as simple as checking out the git repository and specifying the target files and the output name in src/main.cxx.

 

How to add dynamic inefficiency

The tag is set when the db file is generated.

Line: 82 to 78
 process.dynineffprefer = cms.ESPrefer("PoolDBESSource", "DynIneffReader")
Added:
>
>

Calculating the pileup for data files

Example:

brilcalc lumi --byls -u /nb --minBiasXsec 78100 --begin 5659 --end 9999 | head -n-8 | tail -n+5 | sed "s;|;;g;s;:; ;g"):

This bash-script can be called from the SplitClusterStudy analyzer (currently commented out), but opening a socket to store the string as a result still regularly fails (and also takes up too much time when testing).

Running the HistogramMerger

Running the HistogramMerger is as simple as checking out the git repository and specifying the target files and the output name in src/main.cxx.

 

Results

TTbar events, no pileup, 95% dcol efficiency statistics files:

Line: 98 to 107
 

Validation

Examples for module cluster plots of single events are shown below. Nothing unordinary to be seen.
Added:
>
>
Low eta module, 50 events merged High eta module, 50 events merged
 

Fluctuations in the leftmost and the rightmost pixels

Positions for the boundary clusters in pixels:

All boundary pixels Leftmost pixels Rightmost pixels
Changed:
<
<
>
>
 
Since the dcol loss has the opposite effect on the rightmost and leftmost pixels, the total boundary pixel distribution does not show any fluctuation effect. For 95% dcol efficiency the leftmost cell shows ~8.5-10.5% less pixels in the odd columns For 95% dcol efficiency the rightmost cell shows ~8.5-10.5% less pixels in the even columns

Plans for the analysis

Line: 117 to 130
 
META FILEATTACHMENT attachment="CLUSTER_BOUNDARY_PIX_COLS_BPIX.png" attr="" comment="Boundary cols. BPIX example" date="1513345428" name="CLUSTER_BOUNDARY_PIX_COLS_BPIX.png" path="CLUSTER_BOUNDARY_PIX_COLS_BPIX.png" size="12828" stream="CLUSTER_BOUNDARY_PIX_COLS_BPIX.png" tmpFilename="/usr/tmp/CGItemp131" user="AdamHunyadi" version="1"
META FILEATTACHMENT attachment="CLUSTER_LEFTMOST_PIX_COLS_BPIX.png" attr="" comment="Leftmost pixels, BPIX example" date="1513345784" name="CLUSTER_LEFTMOST_PIX_COLS_BPIX.png" path="CLUSTER_LEFTMOST_PIX_COLS_BPIX.png" size="13001" stream="CLUSTER_LEFTMOST_PIX_COLS_BPIX.png" tmpFilename="/usr/tmp/CGItemp5080" user="AdamHunyadi" version="1"
META FILEATTACHMENT attachment="CLUSTER_RIGHTMOST_PIX_COLS_BPIX.png" attr="" comment="Rightmost pixels, BPIX example" date="1513345822" name="CLUSTER_RIGHTMOST_PIX_COLS_BPIX.png" path="CLUSTER_RIGHTMOST_PIX_COLS_BPIX.png" size="12588" stream="CLUSTER_RIGHTMOST_PIX_COLS_BPIX.png" tmpFilename="/usr/tmp/CGItemp4992" user="AdamHunyadi" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Low_eta_example.png" attr="" comment="Low eta module cluster plot example" date="1513348926" name="Low_eta_example.png" path="Low_eta_example.png" size="32355" stream="Low_eta_example.png" tmpFilename="/usr/tmp/CGItemp5021" user="AdamHunyadi" version="1"
META FILEATTACHMENT attachment="High_eta_example.png" attr="" comment="High eta module cluster plot example" date="1513348943" name="High_eta_example.png" path="High_eta_example.png" size="31463" stream="High_eta_example.png" tmpFilename="/usr/tmp/CGItemp5003" user="AdamHunyadi" version="1"

Revision 82017-12-15 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Line: 10 to 10
 
  • The pileup mixing seems to throw away all the digis that are coming from the mixed pileup. This makes it difficult to add the digi markers.
  • The digi collection does not exactly contain the same pixels as the cluster collection. Mostly the digis is a bigger set (with all the cluster pixels available in it), but for now on I create a lookup table and add zero markers for any extra cluster digis that might turn up. The rate of "mocked digis" is a good number to pay attention to when running the simulations even on the grid.
Changed:
<
<

TODOs

>
>

TODOs (problem fixes, find plans at the end of this page)

 
  • Add modifications to the pileup mixing modules so that it propagates the digi flag collection from the mixed data and it can be combined to a correct flag collection
  • Modify the histogram merger code not to merge the "ModuleClusterPlots" even if they are from the same run/lumiblock/event
Line: 92 to 90
 /store/user/ahunyadi/SCS/Run2_CMSSW93X/SCS_93X_mcRun2_DynIneff_95_GEN_SIM_RAWTODIGI_evt100000
Added:
>
>
For users on the ui3 of the Wigner institute:
/data/gridout/ahunyadi/SCS/Run2_CMSSW93X/SCS_93X_mcRun2_DynIneff_95_GEN_SIM_RAWTODIGI_evt100000/171212_101805/0000/

Validation

Examples for module cluster plots of single events are shown below. Nothing unordinary to be seen.

Fluctuations in the leftmost and the rightmost pixels

Positions for the boundary clusters in pixels:

All boundary pixels Leftmost pixels Rightmost pixels
Since the dcol loss has the opposite effect on the rightmost and leftmost pixels, the total boundary pixel distribution does not show any fluctuation effect. For 95% dcol efficiency the leftmost cell shows ~8.5-10.5% less pixels in the odd columns For 95% dcol efficiency the rightmost cell shows ~8.5-10.5% less pixels in the even columns
 

Plans for the analysis

Added:
>
>
  • Write a tool to properly calculate the percentage differences in the even and odd cols (excluding the fidicual areas)
  • Measure the correspondence of the fluctuation in the leftmost and rightmost pixel position to the dcol efficiency correspondence by creating an efficiency scan with the SplitClusterStudy plugin
  • Measure distributions for the left- and rightmost pixels in the data and give estimation for dcol efficiency loss.
 -- AdamHunyadi - 2017-12-04 \ No newline at end of file
Added:
>
>
META FILEATTACHMENT attachment="CLUSTER_BOUNDARY_PIX_COLS_BPIX.png" attr="" comment="Boundary cols. BPIX example" date="1513345428" name="CLUSTER_BOUNDARY_PIX_COLS_BPIX.png" path="CLUSTER_BOUNDARY_PIX_COLS_BPIX.png" size="12828" stream="CLUSTER_BOUNDARY_PIX_COLS_BPIX.png" tmpFilename="/usr/tmp/CGItemp131" user="AdamHunyadi" version="1"
META FILEATTACHMENT attachment="CLUSTER_LEFTMOST_PIX_COLS_BPIX.png" attr="" comment="Leftmost pixels, BPIX example" date="1513345784" name="CLUSTER_LEFTMOST_PIX_COLS_BPIX.png" path="CLUSTER_LEFTMOST_PIX_COLS_BPIX.png" size="13001" stream="CLUSTER_LEFTMOST_PIX_COLS_BPIX.png" tmpFilename="/usr/tmp/CGItemp5080" user="AdamHunyadi" version="1"
META FILEATTACHMENT attachment="CLUSTER_RIGHTMOST_PIX_COLS_BPIX.png" attr="" comment="Rightmost pixels, BPIX example" date="1513345822" name="CLUSTER_RIGHTMOST_PIX_COLS_BPIX.png" path="CLUSTER_RIGHTMOST_PIX_COLS_BPIX.png" size="12588" stream="CLUSTER_RIGHTMOST_PIX_COLS_BPIX.png" tmpFilename="/usr/tmp/CGItemp4992" user="AdamHunyadi" version="1"

Revision 72017-12-14 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Line: 12 to 12
 

TODOs

  • Add modifications to the pileup mixing modules so that it propagates the digi flag collection from the mixed data and it can be combined to a correct flag collection
Changed:
<
<
  • Create an ROOT histogram merger repo to generate merged histograms based on the statistics of the output files of crab jobs
>
>
  • Modify the histogram merger code not to merge the "ModuleClusterPlots" even if they are from the same run/lumiblock/event
 

Recipe to run the framework

Line: 58 to 58
  For no PU, I usually generate TTbar events.
Added:
>
>

Running the HistogramMerger

Running the HistogramMerger is as simple as checking out the git repository and specifying the target files and the output name in src/main.cxx.

 

How to add dynamic inefficiency

The tag is set when the db file is generated.

Revision 62017-12-12 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Added:
>
>
 

Issues

  • The pileup mixing seems to throw away all the digis that are coming from the mixed pileup. This makes it difficult to add the digi markers.

Revision 52017-12-12 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Line: 11 to 11
 

TODOs

  • Add modifications to the pileup mixing modules so that it propagates the digi flag collection from the mixed data and it can be combined to a correct flag collection
Added:
>
>
  • Create an ROOT histogram merger repo to generate merged histograms based on the statistics of the output files of crab jobs
 

Recipe to run the framework

Line: 76 to 77
 process.dynineffprefer = cms.ESPrefer("PoolDBESSource", "DynIneffReader")
Added:
>
>
 

Results

Added:
>
>
TTbar events, no pileup, 95% dcol efficiency statistics files:

/store/user/ahunyadi/SCS/Run2_CMSSW93X/SCS_93X_mcRun2_DynIneff_95_GEN_SIM_RAWTODIGI_evt100000
 

Plans for the analysis

-- AdamHunyadi - 2017-12-04

Revision 42017-12-06 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Line: 15 to 14
 

Recipe to run the framework

Added:
>
>

Deploy script

export SCRAM_ARCH=slc6_amd64_gcc530
cmsrel CMSSW_9_3_0_pre1
cd CMSSW_9_3_0_pre1src
cmsenv
git cms init
git cms-addpkg SimTracker/SiPixelDigitizer
git cms-addpkg RecoLocalTracker/SiPixelClusterizer
git remote add hunyadix git@github.com:hunyadix/cmssw.git
git fetch hunyadix
git checkout -t hunyadix/ModForPixelMerger
...

Generating a CMSSW config file

cmsDriver.py \
-s GEN,SIM,DIGI,L1,DIGI2RAW,RAW2DIGI,RECO \
--evt_type SingleNuE10_cfi \
--process PrivateRECO \
--conditions auto:phase1_2017_realistic \
--era Run2_2017 \
--geometry DB:Extended \
--pileup Flat_0_50_25ns \
--relval 9000,50 \
--beamspot Realistic25ns13TeVEarly2017Collision \
--filein /store/relval/CMSSW_9_0_0_pre4/RelValMinBias_13/GEN-SIM/90X_upgrade2017_realistic_v6-v1/10000/0047A0C1-BDEC-E611-8FD9-0CC47A4D7630.root \
--pileup_input das:/RelValMinBias_13/CMSSW_9_2_3-92X_upgrade2017_realistic_v1_earlyBS2017-v1/GEN-SIM \
--eventcontent RECOSIM \
--datatier GEN-SIM-RECO \
--fileout file:GenNu_FlatPileup0to50_GENSIMRECO.root \
--python_filename PhaseI_GenNu_FlatPileup0to50_cfg.py \
--runUnscheduled \
-n 10 \
--no_exec

For no PU, I usually generate TTbar events.

How to add dynamic inefficiency

The tag is set when the db file is generated.

# Add dynamic inefficiency to simulate dcol losses
dynIneff_db     = 'sqlite_file:phase1_efficiencies_95_pure.db'
dynIneff_tag    = 'SiPixelDynamicInefficiency_v1'

process.DynIneffReader = cms.ESSource("PoolDBESSource",
    DBParameters = cms.PSet(
        messageLevel = cms.untracked.int32(0),
        authenticationPath = cms.untracked.string('')),
    toGet = cms.VPSet(cms.PSet(
        record = cms.string("SiPixelDynamicInefficiencyRcd"),
        tag = cms.string(dynIneff_tag))),
    connect = cms.string(dynIneff_db))
process.dynineffprefer = cms.ESPrefer("PoolDBESSource", "DynIneffReader")
 

Results

Plans for the analysis

Revision 32017-12-06 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Line: 13 to 13
 

TODOs

  • Add modifications to the pileup mixing modules so that it propagates the digi flag collection from the mixed data and it can be combined to a correct flag collection
Added:
>
>

Recipe to run the framework

 

Results

Plans for the analysis

Revision 22017-12-06 - AdamHunyadi

Line: 1 to 1
 
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Changed:
<
<

Checklist for the current issues

  • The pileup mixing seems to throw away all the digis that are coming from the mixed pileup. This makes it difficult to add the digi markers. For now, I don't do pileup scans.
>
>

Issues

  • The pileup mixing seems to throw away all the digis that are coming from the mixed pileup. This makes it difficult to add the digi markers.
  • The digi collection does not exactly contain the same pixels as the cluster collection. Mostly the digis is a bigger set (with all the cluster pixels available in it), but for now on I create a lookup table and add zero markers for any extra cluster digis that might turn up. The rate of "mocked digis" is a good number to pay attention to when running the simulations even on the grid.

TODOs

  • Add modifications to the pileup mixing modules so that it propagates the digi flag collection from the mixed data and it can be combined to a correct flag collection
 

Results

Revision 12017-12-04 - AdamHunyadi

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="AdamHunyadi"

Split Cluster Study

Links

Checklist for the current issues

  • The pileup mixing seems to throw away all the digis that are coming from the mixed pileup. This makes it difficult to add the digi markers. For now, I don't do pileup scans.

Results

Plans for the analysis

-- AdamHunyadi - 2017-12-04

 
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 TWiki? Send feedback