Difference: TrackerAlignmentHowTo (38 vs. 39)

Revision 392012-01-19 - PalHidas

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

Mille/Pede Tracker Alignment How-To (OBSOLETE)

Line: 557 to 557
  The instructions were included in Roberto's email: email
Changed:
<
<
Use 44X.
cmsrel CMSSW_4_4_2_patch9
cd CMSSW_4_4_2_patch9/src/
cmsenv
cvs co -A Alignment/OfflineValidation
cvs co UserCode/castello/Alignment/ToolforMisalignment/test
cp -r UserCode/castello/Alignment/ToolforMisalignment/test/* Alignment/OfflineValidation/test/
cvs co UserCode/castello/Alignment/ToolforMisalignment/plugins
cp -r UserCode/castello/Alignment/ToolforMisalignment/plugins/* Alignment/OfflineValidation/plugins/
cvs co UserCode/castello/Alignment/ToolforMisalignment/python
cp -r UserCode/castello/Alignment/ToolforMisalignment/python/* Alignment/OfflineValidation/python/
rm UserCode -R
scram b
>
>
scramv1 project -n CMSSW_4_2_8_patch7_StartGeo CMSSW CMSSW_4_2_8_patch7
cd CMSSW_4_2_8_patch7_StartGeo/src

cmsenv

cvs co -A Alignment/OfflineValidation
cvs co UserCode /castello/Alignment/ToolforMisalignment/plugins
cp -r UserCode /castello/Alignment/ToolforMisalignment/plugins/TrackerGeometryCompare.h Alignment/OfflineValidation/plugins/
cp -r UserCode /castello/Alignment/ToolforMisalignment/plugins/TrackerGeometryCompare.cc Alignment/OfflineValidation/plugins/

rm UserCode -R
scram b
 
Changed:
<
<
However, this does not compile:
>
>
Now for running, you have to replace in the cfg contained in the test/ directory (BUT THESE FILES ARE NOT THERE):
 
Changed:
<
<
/afs/cern.ch/user/k/krajczar/scratch0/NewStartingGeom/CMSSW_4_4_2_patch9/src/Alignment/OfflineValidation/plugins/TrackerOfflineValidation.cc: In member function 'virtual void TrackerOfflineValidation::analyze(const edm::Event&, const edm::EventSetup&)': /afs/cern.ch/user/k/krajczar/scratch0/NewStartingGeom/CMSSW_4_4_2_patch9/src/Alignment/OfflineValidation/plugins/TrackerOfflineValidation.cc:1156: error: 'const struct TrackerValidationVariables::AVHitStruct' has no member named 'overlapres'
>
>
TkAlCompareToNTuple .Geom1_cfg.py

TkAlCompareToNTuple .Geom2_cfg.py

with the two geometries (sqlite files) you want to compare and extract the Deltas:

Geom1-Geom2=Deltas

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.

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


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).

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.

 
Deleted:
<
<
The problem comes from Roberto's code in his UserCode area (the release Alignment/OfflineValidation area compiles successfully).
 

Z->mumu validation

The instructions were included in Roberto's email: email

 
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