Millepede-II Result Analysis

This script provides a fast opportunity to gain plots of the fitted parameters. The data for the plots is extracted from the file treeFile_merge.root. Also, the plots from the millePedeUser_monitor.root file are used. To get additional information about the millipede process the pede.dump.gz and the alignment_merge.py file is parsed. The plots are provided in various formats in the output folder, which can be specified in the ini-file. The output is arranged in a latex, latexbeamer and HTML file.

Usage

General information about the configuration

The configuration could be done in various ways. In each configuration step the newly given information overrides the previous one. The order of the procession of the configuration sources is:

  1. default.ini file in the mpsvalidate directory
  2. ini-file which could be given by the user with the -i command
    example
    mps_validate.py -i user.ini
  3. command-line arguments

Structure of the default.ini file

The default.ini file is divided in several regions ([EXAMPLE]). Each region contains variables with their values (outputpath = output).
The effect of each value:
[GENERAL]

  • jobdatapath
    path to the jobm directory
    Warning, important the trailing / must be omitted
    Warning, important if a value is given, the automatically generated path by the job variable is overridden
    (default: blank)
  • job
    specifies the number of the jobmX folder
    is used to generate the input-path when no jobdatapath is given
    (default: 0)
  • time
    specifies the MillePedeUser_X TTree
    (default: 1)
  • outputpath
    path where the output should be stored
    Warning, important the trailing / must be omitted
    (default: if no -p command-line argument is given, the default outputpath is in the jobm directory (/jobm/validation_output/)
    if a -p command-line argument is given, the default output path is at the current location (./validation_output/) )
  • latexfile
    name of the generated tex-file
    (default: latex.tex)
  • limit
    is a list (separated by commas) with limits for translation, rotation and deformation (this order must be provided); if there is a value (in the high level structure plots or the module plots) bigger than the given limit, a warning is shown in the top left corner
    (default: 100, 0.005, 0.05)
  • statboxsize
    defines the size of the statistics box in comparison to the plot itself
    (default: 0.3)

[SHOW]

  • showmonitor, showadditional, showdump, showtime, showhighlevel, showmodule, showsubmodule, showtex, showbeamer, showhtml
    If you set one of these values to 0, the associated part of the script is not executed.
    (default: 1)
    Warning, important to show the submodule plots you must also activate the module plots
    Warning, important to create the tex and beamer file all other parts must be activated

[MODULEPLOTS]

  • rangemode
    Specifies which plot range should be used. There are three possible configurations (default: given):
    • all
      The range is set to a value where all data points are shown.
    • stddev
      If there are big outliers (see defpeak), the range is set to a multiple of the standard deviation (see widthstddev).
    • given
      The ranges given in rangeXXX are used. The smallest range which covers all bins is used. If no range is big enough, the biggest given range is used
  • samerange
    If this value is set to 1, the plots for all parameters (e.g. X, Y, Z) are set to the same (highest) value.
    (default: 1)
  • rangexyz, rangerot, rangedist
    list of ranges (separated by commas) which are used if the rangemode is set to given
    (default: 50,100,150, 0.00004,0.00006,0.001, 0.03)
  • defpeak
    only has an impact if the rangemode is set to stddev
    definition of big outliers; if the condition maximum outlier / standard deviation > defpeak is fulfilled, it is assumed that there are big outliers
    (default: 9)
  • widthstddev
    only has an impact if the rangemode is set to stddev
    if there are big outliers, the plot range is set to widtstddev * standard deviation
    (default: 3)
  • numberofbins
    specifies how many bins should be visible in plots (result can differ a bit)
    (default: 100)

[HIGHLEVELPLOTS] This setting has an impact on the high level structure plots and on the time (IOV) dependent plots.

  • rangemode
    Specifies which plot range should be used. There are two possible configurations (default: given):
    • all
      The range is set to a value where all data points are shown.
    • given
      The ranges given in rangeXXX are used. The smallest range which covers all bins is used. If no range is big enough, the biggest given range is used
  • rangexyz, rangerot
    list of ranges (seperated by commas) which are used if the rangemode is set to given
    (default: 50,100,150, 0.00004,0.00006,0.001)
  • samerange
    If this value is set to 1 the plots for all parameters (e.g. X, Y, Z) are set to the same (highest) value.
    (default: 1)

[TIMEPLOTS]

  • firsttree
    Specifies which MillePedeUser_X should be used as a starting point in the time-dependent plots. Only the structures which are aligned in this TTree are plotted in the time-dependent plots.
    (default: 1)

User created ini file

It is possible to write your own ini file. The easiest way is to use the command mps_validate.py -c to create a copy of the validation_user.ini file in the current directory. If you want to copy it manually the script can be found in the CMSSW_X_X_X/src/Alignment/MillePedeAlignmentAlgorithm/python/mpsvalidate/default.ini directory. In this copy of the default.ini file you can change all variables. Variables that should not be changed can be erased or left blank. The variables in your own copy follow the same rules as the one in the default.ini. You are able to copy this file and create multiple ini files which fit your needs.
The ini file is hand over to the script by the command-line argument -i. Example:

mps_validate.py -i user.ini
Warning, important It is important to know that the configuration done in the ini file is overridden by the given command-line arguments.

Possible command-line arguments

Command-line arguments that could be given:

  • -i
    your own ini file can be handed over by this command
  • -p
    specifies the jobdatapath where the input files are located
    Warning, important the outputpath is set to the current directory
  • -o
    specifies the outputpath
    Warning, important overrides every other configuration of the outputpath
  • -j
    specifies the number of the jobmX folder
    Warning, important the jobdatapath specified in the ini file is overridden by the created path
    Warning, important this is overriden by the -p command
  • -t
    specifies the MillePedeUser_X TTree
  • -m
    identification message which is shown on every plot; for example the name of the alignment mpXXXX
  • -c
    creates a copy of the validation_user.ini configuration file in the current directory and terminates the script afterwards

Output

General information about the output

Structure of the output-directory:

+---outputpath/
    +---plots/
    |   +---png/
    |   |   +---plots.png
    |   +---pdf/
    |       +---plots.pdf
    +---latexfile.tex
    +---beamer.tex
    +---html_file.html

High-level parameter plots

The plots show the alignment parameters of all high level structures which were aligned. There are a own plots for translation and rotation. Additional information is provided in the top left corner.
Warning, important if [HIGHLEVELPLOTS] -> rangemode is set to to given and there are outliers => the outliers are hidden

Example:

High-level parameters versus time (IOV)

The plots show the alignment parameters of the high level structures in the different IOVs. The first IOV is selected via [TIMEPLOTS] -> firsttree . Empty steps are skipped. All parts of a structure are placed in the same plot.
Warning, important if [HIGHLEVELPLOTS] -> rangemode is set to to given and the values are higher than the biggest given range => the outliers are hidden

Example:

Module-level parameters

The aligned parameters of all modules of a structure are shown.

Example:

Modules of a part of a structure

The aligned parameters of all modules of a part of a structure are shown. The modules of a part are shown in the same color. This plot is overlayed by the plot of the hole structure (black). All the plots are normalized.

Example:

Plots from the millePedeMonitor_merge.root file

Some of the plots are taken from the millePedeMonitor_merge.root file .

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng config.png r1 manage 38.6 K 2016-06-22 - 12:12 PhilippRigoll  
PNGpng highlevel.png r1 manage 24.1 K 2016-06-22 - 12:06 PhilippRigoll  
PNGpng module.png r1 manage 26.9 K 2016-06-22 - 12:06 PhilippRigoll  
PNGpng submodule.png r1 manage 26.4 K 2016-06-22 - 12:06 PhilippRigoll  
PNGpng time.png r1 manage 15.0 K 2016-06-22 - 12:06 PhilippRigoll  
Edit | Attach | Watch | Print version | History: r17 < r16 < r15 < r14 < r13 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r17 - 2016-08-09 - PhilippRigoll
 
    • 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-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback