Difference: TrackerAlignmentHowTo (43 vs. 44)

Revision 442012-03-12 - PalHidas

Line: 1 to 1

META TOPICPARENT	name="TrackerAlignment"

Changed:

<
<

Mille/Pede Tracker Alignment How-To

>
>

Tracker Alignment How-To

Mille/Pede Tracker Alignment

This page serves as a How To for running MillePede

Tracker alignment framework. Commands are shown as step-by-step guide with brief descriptions.

Tracker Alignment How-To

Changed:

<
<

I. Mille/Pede setup used for CRAFT11

>
>

I. Mille/Pede setup used for CRAFT11

The common alignment area for MP can be found here:

/afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction

Line: 111 to 112

This procedure will then create a new alignment db file in the jobData/jobm folder.

Changed:

<
<

II. Offline Validation Tools

>
>

II. Offline Validation Tools

This step is to rerun the track fitting using various alignment.db files. E.g. including that that has just been created by You with the MPS system above.

Line: 231 to 232

6) Make sure you always know what plots are the important ones as the MPS and the Validation is generating a looots of plots....

Changed:

<
<

Useful links and literature

>
>

Useful links and literature

Hamburg CMS Alignment Workshop: https://indico.cern.ch/conferenceOtherViews.py?confId=137973

Millepede II manual: Mptwo.pdf

Line: 240 to 241

Calibration and Alignment of the CMS Silicon Tracking Detector (Markus Stoye, PhD Thesis)

Changed:

<
<

The role of various scripts and the 2011 alignment validation

How to produce a new alignment .db file?

>
>

The role of various scripts and the 2011 alignment validation

How to produce a new alignment .db file?

1. Choose a CMSSW version for alignment:

Line: 326 to 327

mps_fire.pl -mf

The output .db will be located in jobData/jobm.

Changed:

<
<

How to run compare the content of the newly created .db file with the default one?

>
>

How to run compare the content of the newly created .db file with the default one?

1. Set up CMSSW and create a new directory for validation:

cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/CMSSW_4_1_2/

Line: 413 to 414

Justyna's talk: https://indico.cern.ch/getFile.py/access?contribId=4&sessionId=0&resId=0&materialId=slides&confId=127136

Changed:

<
<

Alignment campaign 2011

>
>

Alignment campaign 2011

1. Set up CMSSW:

cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/CMSSW_4_2_4_patch1

source /afs/cern.ch/user/r/radbal/public/TrackerAlign/setup_env.sh

Line: 471 to 472

root -x -b -q E_odd_isosample_PlotTheResiduals_8geom.C
root -x -b -q E_odd_TkAlExtendedOfflineValidation.C

Changed:

<
<

September 2011 alignment (Krisztian's guesses)

Mille/Pede

1. Setup the CMSSW version (pure guess based on this email):

>
>

September 2011 alignment (Krisztian's guesses)

Mille/Pede

1. Setup the CMSSW version (pure guess based on this email):

cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction/CMSSW_4_2_4_patch1_TkAl3
source /afs/cern.ch/user/r/radbal/public/TrackerAlign/setup_env.sh

Line: 482 to 483

source /afs/cern.ch/user/k/krajczar/public/TrackerAlignment_setup_env.csh

Changed:

<
<

2. Setup a new directory on the common alignment area (DO THIS ONLY ONCE!)

>
>

2. Setup a new directory on the common alignment area (DO THIS ONLY ONCE!)

cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction
./setupNewAlignment.sh

Do not foget to edit MP_ali_list.txt.

Changed:

<
<

3. Copy the config files

>
>

3. Copy the config files

from ../mp0789 and edit them according to Joerg's and Gero's instructions. About the dataset to be used please see Gero's email.

Line: 509 to 510

- I DID NOT update alignable.txt!!! See Gero's (already linked) email

- I changed the value of the $millescript, $pedescript, and $mpsdir variables from ...TkAl1 -> ...TkAl3. NOTE THAT THIS WAS NOT SUGGESTED BY JOERG!

Changed:

<
<

4. Create jobs, submit them, check their status, and get the output files

>
>

4. Create jobs, submit them, check their status, and get the output files

perl setup_align.pl
mps_fire.pl 1000
mps_stat.pl

Line: 521 to 522

until all are successfully done.

Changed:

<
<

5. Run Pede

>
>

5. Run Pede

mps_fire.pl -mf

The output .db will be located in jobData/jobm.

Changed:

<
<

MC alignment, 10.2011

Important emails on the topic (time ordered list): Joerg's summary of his work, Gero's 1st, Gero's 2nd, Roberto's 1st, Gero about weighting, Gero about Pede job being failed with CPU time issue, Gero about Pede job being failed due to some other reason, Gero about the meaning of method 1a)

Line: 538 to 541

Joerg's talk: Joerg's talk mentioned in Gero's first email

Changed:

<
<

Part 1

>
>

Part 1

cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction/CMSSW_4_2_4_patch1_TkAl3

Line: 551 to 554

Then repeat Gero's work copying his mp0895 directory; no modification to be made yet:

cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction etc.

Changed:

<
<

Part 2

>
>

Part 2

Changed:

<
<

Comparing geometries

>
>

Comparing geometries

The instructions were included in Roberto's email: email

Line: 571 to 574

at this point the Deltas will be automatically applied (running TkAlCompareCommonTracker .Geom1-Geom2_cfg.py) to the ideal geometry in the output sqlite file: IDEAL+Deltas (change the inputs in the file according to the names) and a sqlite file is produced as output. This output could be used directly as starting geometry to be included in your alignment job, as we did for the one I produced for the MC scenario.

Changed:

<
<

How to create histograms after validation (Ádám)

>
>

How to create histograms after validation (Ádám)

Set up your working area

Changed:

<
< 1, Setup the CMSSW version
cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/CMSSW_4_2_4_patch1

source /afs/cern.ch/user/a/agocsa/public/TrackerAlignment_setup_env.sh

of (if you want to use tcsh shell)

source /afs/cern.ch/user/k/krajczar/public/TrackerAlignment_setup_env.csh

2. Go to the validation area and create a new directory
cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/
mkdir <New_DIRECTORY>
cd <NEW_DIRECTORY>

3. Copy .root files
cp -r /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/test_agocs/Histograms .

4. Modify the given .root files
According to All-in-One validation tool (https://twiki.cern.ch/twiki/bin/viewauth/CMS/TkAlAllInOneValidation), there are 4 different validations. This recepie presents 3 of them (Offline validation, Geometry comparison and Track Splitting).

4a. Offline validation
Scripts for offline validation can be found at <NEW_DIRECTORY>/Histograms/offline.

4a1. Modify and run TkAlExtendedOfflineValidation .C
Open TkAlExtendedOfflineValidation .C file with your favourite editor (e.i vi TkAlExtendedOfflineValidation ).

At line 11 there is a object decleration:
PlotAlignmentValidation p("/afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/results/agocsa/New_Start/AlignmentValidation_IDEALplus_02Delta.root", "IDEALplus_02Delta MC_42_V15B", 1, 1);
At this line validation results of the first geometry can be defined with the following sintax:
PlotAlingmentValidation p(<Path_of_validation_result>, <Name_of_the_result>, <Color_of_line>, <Style_of_line>);

New validation results can be added with the following lines:
p.loadFileList("/afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/results/agocsa/New_Start/AlignmentValidation_IDEALplus_033Delta.root", "IDEALplus_033Delta MC_42_V15B", 2, 1);

The sintax is the following:
p.loadFileList(<Path_of_validation_result>, <Name_of_the_result>, <Color_of_line>, <Style_of_line>);

Run TkAlExtendedOfflineValidation as
root -x -b -q TkAlExtendedOfflineValidation

4a2. Modify and run isosample_PlotTheResiduals_8geom.C
Open isosample_PlotTheResiduals_8geom.C with your favourite editor (e.i. vi isosample_PlotTheResiduals_8geom.C).

>
>

1, Set up the CMSSW version
cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/CMSSW_4_2_4_patch1

source /afs/cern.ch/user/a/agocsa/public/TrackerAlignment_setup_env.sh

of (if you want to use tcsh shell)

source /afs/cern.ch/user/k/krajczar/public/TrackerAlignment_setup_env.csh

2. Go to the validation area and create a new directory
cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/
mkdir <New_DIRECTORY>
cd <NEW_DIRECTORY>

3. Copy .root files
cp -r /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/test_agocs/Histograms .

Validations

Changed:

<
< From line 67 to line 81 there are TFile* declaration which open the files of validation results of geometries. Originally, this file is optimalized for 8 validation results of geometries. Therefore if you want to run this macro for another number of validation results of geometries, you should modify the following lines (I give an example for 3 geometries):

At line 181: Remove source code from line 183 to line 187 because these lines can modify the maximum value of the plots.
At line 247: Modify the name of the validation results of geometries.
At line 273: Remove source code from line 276 to line 280 because these lines modify the subtitles (TLegend) of the plots.
At line 283: Remove source code from line 299 to line 317 because these lines reference to removed variables.
At line 329: Remove source code from line 333 to line 337 because these lines want to draw unused plots.

At line 613: Remove source code from line 616 to line 620 because these lines want to modify the maximum value of the plots.
At line 729: Remove source code from line 741 to line 759 because these lines modify the subtitles (TLegend) of the plots.
At line 762: Remove source code from line 792 to line 845 because these lines reference to removed variables.
At line 924: Remove source code from line 951 to line 955 because these lines response to draw plots.

Run isosample_PlotTheResiduals_8geom.C as
root -x -b -q isosample_PlotTheResiduals_8geom

4b. Geometry Comparison
These histograms are created by All-in-one Validation tool.
4c. Track Splitting
Script for Track Splitting can be found at <NEW_DIRECTORY>Histograms/split/

Open cosmicSplittingValidation_v7.C with your favourite editor (e.i. vi cosmicSplittingValidation_v7.C).

From line 343 to line 350 there are input files declarations. Originally, cosmicSplittingValidation_v7.C have been optimalizied for 7 validation results of geometries. Therefore you should modify this macro if you want to execute it for another number of validation results of geometries (I give an example for 3 geometries). Note that source code from line 357 to line 364 describes names of the geometries.

At line 328: Modify the nGeoms variable to the given number. Our case: const int nGeoms = 3;
At line 343: Remove source code from line 347 to line 350 because these lines reference to another input files.
At line 357: Remove source code from line 361 to line 364 because these lines response to name of these geometries which are not used.
At line 379: Remove source code from line 382 to line 385 because these lines reference to invalid variables.
At line 391: Remoce source code from line 394 to line 397 because these lines reference to invalid variables too.

Run cosmicSplittingValidation_v7.C as
root -x -b -q cosmicSplittingValidation_v7

5. Results of macros
Results of these macros can be found at /tmp/<USERNAME> directory.

>
>

4. Modify the given .root files
According to All-in-One validation tool (https://twiki.cern.ch/twiki/bin/viewauth/CMS/TkAlAllInOneValidation

), there are 4 different validations. This recepie presents 3 of them (Offline validation, Geometry comparison and Track Splitting).

Offline validation

Changed:

<
<

Z->mumu validation

>
>

4a. Offline validation
Scripts for offline validation can be found at <NEW_DIRECTORY>/Histograms/offline.

4a1. Modify and run TkAlExtendedOfflineValidation .C
Open TkAlExtendedOfflineValidation .C file with your favourite editor (e.i vi TkAlExtendedOfflineValidation ).

At line 11 there is a object decleration:
PlotAlignmentValidation p("/afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/results/agocsa/New_Start/AlignmentValidation_IDEALplus_02Delta.root", "IDEALplus_02Delta MC_42_V15B", 1, 1);
At this line validation results of the first geometry can be defined with the following sintax:
PlotAlingmentValidation p(<Path_of_validation_result>, <Name_of_the_result>, <Color_of_line>, <Style_of_line>);

New validation results can be added with the following lines:
p.loadFileList("/afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/results/agocsa/New_Start/AlignmentValidation_IDEALplus_033Delta.root", "IDEALplus_033Delta MC_42_V15B", 2, 1);

The sintax is the following:
p.loadFileList(<Path_of_validation_result>, <Name_of_the_result>, <Color_of_line>, <Style_of_line>);

Run TkAlExtendedOfflineValidation as
root -x -b -q TkAlExtendedOfflineValidation

4a2. Modify and run isosample_PlotTheResiduals_8geom.C
Open isosample_PlotTheResiduals_8geom.C with your favourite editor (e.i. vi isosample_PlotTheResiduals_8geom.C).

From line 67 to line 81 there are TFile* declaration which open the files of validation results of geometries. Originally, this file is optimalized for 8 validation results of geometries. Therefore if you want to run this macro for another number of validation results of geometries, you should modify the following lines (I give an example for 3 geometries):

At line 181: Remove source code from line 183 to line 187 because these lines can modify the maximum value of the plots.
At line 247: Modify the name of the validation results of geometries.
At line 273: Remove source code from line 276 to line 280 because these lines modify the subtitles (TLegend) of the plots.
At line 283: Remove source code from line 299 to line 317 because these lines reference to removed variables.
At line 329: Remove source code from line 333 to line 337 because these lines want to draw unused plots.

At line 613: Remove source code from line 616 to line 620 because these lines want to modify the maximum value of the plots.
At line 729: Remove source code from line 741 to line 759 because these lines modify the subtitles (TLegend) of the plots.
At line 762: Remove source code from line 792 to line 845 because these lines reference to removed variables.
At line 924: Remove source code from line 951 to line 955 because these lines response to draw plots.

Run isosample_PlotTheResiduals_8geom.C as
root -x -b -q isosample_PlotTheResiduals_8geom

Geometry comparison

4b. Geometry Comparison
These histograms are created by All-in-one Validation tool.

Track splitting

4c. Track Splitting
Script for Track Splitting can be found at <NEW_DIRECTORY>Histograms/split/

Open cosmicSplittingValidation_v7.C with your favourite editor (e.i. vi cosmicSplittingValidation_v7.C).

From line 343 to line 350 there are input files declarations. Originally, cosmicSplittingValidation_v7.C have been optimalizied for 7 validation results of geometries. Therefore you should modify this macro if you want to execute it for another number of validation results of geometries (I give an example for 3 geometries). Note that source code from line 357 to line 364 describes names of the geometries.

At line 328: Modify the nGeoms variable to the given number. Our case: const int nGeoms = 3;
At line 343: Remove source code from line 347 to line 350 because these lines reference to another input files.
At line 357: Remove source code from line 361 to line 364 because these lines response to name of these geometries which are not used.
At line 379: Remove source code from line 382 to line 385 because these lines reference to invalid variables.
At line 391: Remoce source code from line 394 to line 397 because these lines reference to invalid variables too.

Run cosmicSplittingValidation_v7.C as
root -x -b -q cosmicSplittingValidation_v7

Results

5. Results of macros
Results of these macros can be found at /tmp/<USERNAME> directory.

Z->mumu validation

The instructions were included in Roberto's email: email

Line: 593 to 612

After this step Robert says that ``compile it from CMSSW_4_2_3_patch5/src''. This directory indeed seems to be produced, but scram fails to run in that directory. If I copy MuonAnalysis/MomentumScaleCalibration/ from Roberto's directory to the src of my local CMSSW release and try to compile it, it fails.

Changed:

<
<

Pal's way (2012 january)

>
>

Pal's way (2012 january)

Initialize your working area:

cd /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/CMSSW_4_2_3_patch5/

Line: 700 to 719

Here at section 5) above, if using (t)csh then some extra attention is needed. tcsh here will not work. RooFitSetup is a (ba)sh initilizator from which it is very starightforward to write a (t)csh one. But then the fit will not build, cause some header files would not be found. Change shell here in your window and do this step in bash, instead.

Changed:

<
<

February alignment - Krisztian

>
>

February alignment - Krisztian

Email from Roberto about our resposibility and out job: email

View topic | History: r46 < r45 < r44 < r43 | More topic actions...

Copyright &Â© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback