Difference: OnlineAlignmentHowTo (1 vs. 72)

Revision 722018-04-12 - GiulioDujany

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

Running the online alignment in run 2

Line: 352 to 352
 
user@plus $ cd /group/online/dataflow/cmtuser
user@plus $ git clone ssh://git@gitlab.cern.ch:7999/lhcb/Alignment.git
Changed:
<
<
user@plus $ mv AlignmentOnline AlignmentDev_vXrY
>
>
user@plus $ mv Alignment AlignmentDev_vXrY
 user@plus $ cd AlignmentDev_vXrY
Changed:
<
<
user@plus $ git checkout satellite_vXrY
>
>
user@plus $ git checkout vXrY user@plus $ git checkout -b satellite_vXrY
 user@plus $ lb-project-init user@plus $ git update-index --assume-unchanged CMakeLists.txt user@plus $ chmod g+rw ../AlignmentDev_vXrY # to allow colleagues to make changes in the directory
Line: 375 to 376
 user@plus $ git clone ssh://git@gitlab.cern.ch:7999/lhcb/AlignmentOnline.git user@plus $ mv AlignmentOnline AlignmentOnlineDev_vXrY user@plus $ cd AlignmentOnlineDev_vXrY
Added:
>
>
user@plus $ git checkout vXrY
 user@plus $ git checkout satellite_vXrY user@plus $ lb-project-init user@plus $ git update-index --assume-unchanged CMakeLists.txt

Revision 712018-03-22 - GiulioDujany

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

Running the online alignment in run 2

Line: 346 to 346
  A new release area can be created with the following steps.
Changed:
<
<
First a clone of the project is needed:
>
>
First a clone of the Alignment project is needed:

user@plus $ cd /group/online/dataflow/cmtuser
user@plus $ git clone ssh://git@gitlab.cern.ch:7999/lhcb/Alignment.git
user@plus $ mv AlignmentOnline AlignmentDev_vXrY
user@plus $ cd AlignmentDev_vXrY
user@plus $ git checkout satellite_vXrY
user@plus $ lb-project-init
user@plus $ git update-index --assume-unchanged CMakeLists.txt
user@plus $ chmod g+rw ../AlignmentDev_vXrY # to allow colleagues to make changes in the directory

And modify its CMakeLists.txt by changing Alignment to AlignmentDev

# Declare project name and version
gaudi_project(AlignmentDev vXrY
              USE  Phys v25r0
              DATA AppConfig
                   FieldMap
                   ParamFiles)

Then clone the AlignmentOnline project:

 
user@plus $ cd /group/online/dataflow/cmtuser
user@plus $ git clone ssh://git@gitlab.cern.ch:7999/lhcb/AlignmentOnline.git
user@plus $ mv AlignmentOnline AlignmentOnlineDev_vXrY
user@plus $ cd AlignmentOnlineDev_vXrY
Changed:
<
<
user@plus $ git checkout satellite
>
>
user@plus $ git checkout satellite_vXrY
 user@plus $ lb-project-init user@plus $ git update-index --assume-unchanged CMakeLists.txt user@plus $ chmod g+rw ../AlignmentOnlineDev_vXrY # to allow colleagues to make changes in the directory
Changed:
<
<
Then modify the CMakeLists.txt by adding the following lines at its top
>
>
Then modify the CMakeLists.txt by adding the following lines at its top putting the approriate version of the Alignment and Online packages
 
Changed:
<
<
set(OnlineVersion vUrV) # <-- Change this to the latest version of Online (or the one suggested by the Online team) set(OnlineDev_DIR /group/online/dataflow/cmtuser/OnlineDev_${OnlineVersion}/InstallArea/$ENV{CMTCONFIG})
>
>
set(AlignmentDev_DIR /group/online/dataflow/cmtuser/AlignmentDev_vXrY/InstallArea/$ENV{CMTCONFIG}) set(OnlineDev_DIR /group/online/dataflow/cmtuser/OnlineDev_vXXrYY/InstallArea/$ENV{CMTCONFIG})
 
Changed:
<
<
and the dependency on the OnlineDev release
>
>
and change the dependency to the OnlineDev and AlignmentDev release
 
Changed:
<
<
gaudi_project(AlignmentOnlineDev vXXrY USE OnlineDev ${OnlineVersion} AlignmentOnline vXXrY)
>
>
gaudi_project(AlignmentOnlineDev vXrY USE AlignmentDev vXrY OnlineDev vXXrYY)
 
Line: 375 to 398
 online@plus $ dataflowcmt online@plus $ cd $User_release_area online@plus $ export CMTPROJECTPATH=/group/online/dataflow/cmtuser:$CMTPROJECTPATH
Changed:
<
<
online@plus $ cd AlignmentOnlineDev_vXXrY
>
>
online@plus $ cd AlignmentDev_vXrY online@plus $ rm -rf build.x* #(carefully) online@plus $ do_configure online@plus $ do_install online@plus $ cmsetup #(one should call this after every installation) online@plus $ cd AlignmentOnlineDev_vXrY
 online@plus $ rm -rf build.x* #(carefully) online@plus $ do_configure online@plus $ do_install online@plus $ cmsetup #(one should call this after every installation)
Changed:
<
<
Beware that this procedure could fail with CMake failing to find OnlineDev project. This may happen if /group/online/dataflow/cmtuser is not in the CMTPROJECTPATH.
>
>
Beware that this procedure could fail with CMake failing to find OnlineDev project. This may happen if /group/online/dataflow/cmtuser is not in the CMTPROJECTPATH.
 To fix this

online@plus $ export CMTPROJECTPATH=$CMTPROJECTPATH:/group/online/dataflow/cmtuser
Changed:
<
<
Once finished modify the link to the current and old version of AlignmentOnline:
>
>
Once finished modify the link to the current and old version of AlignmentOnline:
 
user@plus $ rm AlignmentRelease_old
user@plus $ mv AlignmentRelease AlignmentRelease_old

Revision 702017-08-17 - SilviaBorghi

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

Running the online alignment in run 2

Line: 107 to 107
 

Compile the alignment framework online

Changed:
<
<
The code used online for the alignment can be found in /group/online/dataflow/cmtuser/AlignmentRelease/ (Link to the appropriate AlignmentOnlineDev _vXYrZ, e.g. AlignmentOnlineDev _v11r0 for 2016 or AlignmentOnlineDev _v11r3 in 2017,). To recompile the code after having made some changes, login to plus as online (ui does not work) and follow the prescription and troubleshooting help here:
>
>
The code used online for the alignment can be found in /group/online/dataflow/cmtuser/AlignmentRelease/ (Link to the appropriate AlignmentOnlineDev _vXYrZ, e.g. AlignmentOnlineDev _v11r0 for 2016 or AlignmentOnlineDev _v11r4p1 in 2017). To recompile the code after having made some changes, login to plus as online (ui does not work) and follow the prescription and troubleshooting help here:
  You are now ready to compile (as online)
Line: 285 to 285
 If you want to produce the "standard plots " for Velo, Tracker and Muon you can use the script Alignment/AlignmentMonitoring/examples/makePublicityPlots.sh, it just calls the previous one with the appropriate options. You may want to open it and change some options like the min and max run number or the date in the label.
Changed:
<
<
lb-dev Alignment v11r0 cd AlignmentDev_v11r0
>
>
lb-dev Alignment v11r4p1 cd AlignmentDev_v11r4p1
 git lb-use Alignment git lb-checkout Alignment/master Alignment/AlignmentMonitoring make configure

Revision 692017-07-14 - FrancescaDordei

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

Running the online alignment in run 2

Line: 274 to 274
  To see how to use them call them with the -h option.
Added:
>
>
E.g. for the Tracker use: /group/online/dataflow/cmtuser/AlignmentRelease/build.x86_64-centos7-gcc62-opt/run bash

/group/online/dataflow/cmtuser/AlignmentDev_v11r4p1/Alignment/AlignmentMonitoring/scripts/moniPlots_Tracker.py -r 194913 --alignlog /group/online/AligWork/Tracker/run194913_v3/alignlog.txt --histoFiles /hist/Savesets/2017/LHCbA/AligWrk_Tracker/07/14/AligWrk_Tracker-19491418-20170714T101919-EOR.root(OLDFILE) /hist/Savesets/2017/LHCbA/AligWrk_Tracker/07/14/AligWrk_Tracker-19491425-20170714T183340-EOR.root(NEWFILE) -o test.pdf

 

Make trend plots

To make the trend plots you can use the scripts Alignment/AlignmentMonitoring/scripts/trendPlots.py call it with the option -h to see the options available.

Revision 682017-07-14 - MaurizioMartinelli

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

Running the online alignment in run 2

Line: 369 to 369
 
online@plus $ dataflowcmt
online@plus $ cd $User_release_area
Added:
>
>
online@plus $ export CMTPROJECTPATH=/group/online/dataflow/cmtuser:$CMTPROJECTPATH
 online@plus $ cd AlignmentOnlineDev_vXXrY online@plus $ rm -rf build.x* #(carefully) online@plus $ do_configure

Revision 672017-05-31 - FrancescaDordei

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

Running the online alignment in run 2

Line: 107 to 107
 

Compile the alignment framework online

Changed:
<
<
The code used online for the alignment can be found in /group/online/dataflow/cmtuser/AlignmentRelease/AlignmentOnlineDev_vXYrZ (Link to the appropriate AlignmentOnlineDev _vXYrZ, e.g. AlignmentOnlineDev _v11r0,). To recompile the code after having made some changes, login to plus as online (ui does not work) and follow the prescription and troubleshooting help here:
>
>
The code used online for the alignment can be found in /group/online/dataflow/cmtuser/AlignmentRelease/ (Link to the appropriate AlignmentOnlineDev _vXYrZ, e.g. AlignmentOnlineDev _v11r0 for 2016 or AlignmentOnlineDev _v11r3 in 2017,). To recompile the code after having made some changes, login to plus as online (ui does not work) and follow the prescription and troubleshooting help here:
  You are now ready to compile (as online)
Line: 138 to 138
 First, follow the instructions for the installation explained at the step before. The functions that can be used to run the tracker alignment are defined under
Changed:
<
<
/group/online/dataflow/cmtuser/AlignmentRelease/AlignmentOnlineDev_vXYrZ/Alignment/TAlignment/python/TAlignment/AlignmentScenarios.py
>
>
/group/online/dataflow/cmtuser/AlignmentRelease/Alignment/TAlignment/python/TAlignment/AlignmentScenarios.py
  E.g. configureEarlyDataAlignment (for early 2012 alignment)
Changed:
<
<
configureTrackerAlignment (default 2016 alignment)
>
>
configureTrackerAlignment (default 2016/2017 alignment)
  configureFirstTrackerAlignment (early runs 2016 alignment)
Line: 152 to 152
  The function that one want to run can be found in
Changed:
<
<
/group/online/dataflow/cmtuser/AlignmentOnlineDev_v10r5/AlignmentOnline/AlignOnline/python/AlignmentConfigurations/TrackerAlignment.py
>
>
/group/online/dataflow/cmtuser/AlignmentRelease/AlignmentOnline/AlignOnline/python/AlignmentConfigurations/TrackerAlignment.py
  Just uncomment the related lines.
Line: 235 to 235
 
    • The constants are available in the online.db for all the runs declared ready for hlt2. Time validity time of the start of the run to the next run with valid constants (if no further run, infinite).

Changed:
<
<
    • The location of the Survey info can be found in: /group/online/dataflow/cmtuser/AlignmentOnlineDev_v10r6/Alignment/SurveyConstraints.py and it is called by AlignmentScenarios.py (in the same directory)
>
>
    • The location of the Survey info can be found in: /group/online/dataflow/cmtuser/AlignmentRelease/Alignment/SurveyConstraints.py and it is called by AlignmentScenarios.py (in the same directory)
 

Histograms location

The histograms are produced automatically when running the alignment. We have one root file for each iteration, they are at:

Changed:
<
<
the histograms are at /hist/Savesets/2015/LHCbA/
>
>
the histograms are at /hist/Savesets/"YEAR"/LHCbA/
 Nomenclature convention: ex. /hist/Savesets/2015/LHCbA/AligWrk_Muon/07/10/AligWrk_Muon-15691601-20150710T100630-EOR.root
  • Muon is the name of the activity (Muon, Tracker or Velo)
Line: 250 to 250
 
  • 20150710T100630 is the time when the file has been generated.

To run root on plus:

Added:
>
>
/group/online/dataflow/cmtuser/AlignmentRelease/build.x86_64-centos7-gcc62-opt/run bash

or (not working in 2017):

  lb-run root root.exe FILENAME.root

Location of Automatically produced plots

Revision 662017-05-26 - FrancescaDordei

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

Running the online alignment in run 2

Line: 12 to 12
  ssh -Y ui
Changed:
<
<
/group/online/ecs/Shortcuts311/LHCb/ECS/ECS_UI_FSM.sh
>
>
/group/online/ecs/Shortcuts315/LHCb/ECS/ECS_UI_FSM.sh
  Open the LHCb_Align tree (right click).

Revision 652017-04-24 - ParasNaik

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

Running the online alignment in run 2

Line: 107 to 107
 

Compile the alignment framework online

Changed:
<
<
The code used online for the alignment can be found in /group/online/dataflow/cmtuser/AlignmentRelease/AlignmentOnlineDev_vXYrZ (Link to the appropriate AlignmentOnlineDev _vXYrZ, e.g. AlignmentOnlineDev _v11r0,). To recompile the code after having made some changes, login to plus as online (ui does not work) and do
>
>
The code used online for the alignment can be found in /group/online/dataflow/cmtuser/AlignmentRelease/AlignmentOnlineDev_vXYrZ (Link to the appropriate AlignmentOnlineDev _vXYrZ, e.g. AlignmentOnlineDev _v11r0,). To recompile the code after having made some changes, login to plus as online (ui does not work) and follow the prescription and troubleshooting help here:

You are now ready to compile (as online)

<!--
 
make purge
Line: 127 to 131
 
online@plus $ cmsetup 
Added:
>
>
-->
 

Function to be used

First, follow the instructions for the installation explained at the step before.

Line: 352 to 358
  USE OnlineDev ${OnlineVersion} AlignmentOnline vXXrY)
Added:
>
>
 You are now ready to compile (as online):
online@plus $ dataflowcmt
online@plus $ cd $User_release_area
online@plus $ cd AlignmentOnlineDev_vXXrY
Added:
>
>
online@plus $ rm -rf build.x* #(carefully)
 online@plus $ do_configure online@plus $ do_install
Changed:
<
<
online@plus $ cmsetup
>
>
online@plus $ cmsetup #(one should call this after every installation)
 
Changed:
<
<
Beware that this procedure could fail with CMake failing to find OnlineDev project. This may happen if /group/online/dataflow/cmtuser is not in the CMTPROJECTPATH.
>
>
Beware that this procedure could fail with CMake failing to find OnlineDev project. This may happen if /group/online/dataflow/cmtuser is not in the CMTPROJECTPATH.
 To fix this

Revision 642017-04-10 - MaurizioMartinelli

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

Running the online alignment in run 2

Line: 335 to 338
 user@plus $ cd AlignmentOnlineDev_vXrY user@plus $ git checkout satellite user@plus $ lb-project-init
Added:
>
>
user@plus $ git update-index --assume-unchanged CMakeLists.txt
 user@plus $ chmod g+rw ../AlignmentOnlineDev_vXrY # to allow colleagues to make changes in the directory

Then modify the CMakeLists.txt by adding the following lines at its top

Line: 360 to 361
 online@plus $ do_install online@plus $ cmsetup
Changed:
<
<
Once finished modify the link to the current and old version of AlignmentOnline:
>
>
Beware that this procedure could fail with CMake failing to find OnlineDev project. This may happen if /group/online/dataflow/cmtuser is not in the CMTPROJECTPATH. To fix this
 
Added:
>
>
online@plus $ export CMTPROJECTPATH=$CMTPROJECTPATH:/group/online/dataflow/cmtuser

Once finished modify the link to the current and old version of AlignmentOnline:

 user@plus $ rm AlignmentRelease_old user@plus $ mv AlignmentRelease AlignmentRelease_old user@plus $ ln -s AlignmentOnlineDev_vXrY AlignmentRelease

Revision 632017-03-16 - MaurizioMartinelli

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

Running the online alignment in run 2

Line: 76 to 76
  From the top panel click on RunInfo, then in the panel that appears click on Trigger. In the panel that appears the information can be found under Trigger.DeferredRuns
Changed:
<
<
>
>

Software development in the satellite area (online)

AlignmentOnline is installed in the satellite area and a specific branch is devoted to development in there. The suggested workflow is the following

<make changes until sensible workpoint>
git add <files>
git commit -m '<a meaningful message>'
<make changes until sensible workpoint>
git add <files>
git commit -m '<a meaningful message>'
<ready to go to the main repository without breaking the nightlies>
git pull origin master
<fix any conflict (hopefully none) and check that things work as expected>
git push origin satellite
<open merge request from given link or gitlab webpage>

If some modification in Alignment is needed, the corresponding package can be developed with the workflow described in Git4LHCb:

git lb-use Alignment
git lb-checkout Alignment/master Some/Package
<make changes and test>
git add Some/Package/src/MyStuff.cpp
git commit -m 'fixing feature abc (JIRATICKET-123)?
git lb-push Alignment JIRATICKET-123

Donít forget to open a merge request in Alignment after pushing.

 

Compile the alignment framework online

The code used online for the alignment can be found in /group/online/dataflow/cmtuser/AlignmentRelease/AlignmentOnlineDev_vXYrZ (Link to the appropriate AlignmentOnlineDev _vXYrZ, e.g. AlignmentOnlineDev _v11r0,). To recompile the code after having made some changes, login to plus as online (ui does not work) and do

Line: 244 to 272
 git lb-checkout Alignment/master Alignment/AlignmentMonitoring make configure make -j8
Changed:
<
<
./run Alignment/AlignmentMonitoring/examples/makePublicityPlots.sh
>
>
./run Alignment/AlignmentMonitoring/examples/makePublicityPlots.sh
 

Update reference histograms in the presenter

Line: 297 to 324
 

Create a new release area

Changed:
<
<
A new release area can be created with the following steps (as online):
>
>
A new release area can be created with the following steps.

First a clone of the project is needed:

 
Changed:
<
<
online@plus $ dataflowcmt online@plus $ cd $User_release_area online@plus $ use_slc6_gcc49 online@plus $ lb-dev AlignmentOnline vXXrY online@plus $ cd AlignmentOnlineDev vXXrY
>
>
user@plus $ cd /group/online/dataflow/cmtuser user@plus $ git clone ssh://git@gitlab.cern.ch:7999/lhcb/AlignmentOnline.git user@plus $ mv AlignmentOnline AlignmentOnlineDev_vXrY user@plus $ cd AlignmentOnlineDev_vXrY user@plus $ git checkout satellite user@plus $ lb-project-init user@plus $ chmod g+rw ../AlignmentOnlineDev_vXrY # to allow colleagues to make changes in the directory
  Then modify the CMakeLists.txt by adding the following lines at its top
Added:
>
>
 
set(OnlineVersion vUrV) # <-- Change this to the latest version of Online (or the one suggested by the Online team)
set(OnlineDev_DIR /group/online/dataflow/cmtuser/OnlineDev_${OnlineVersion}/InstallArea/$ENV{CMTCONFIG}) 
Line: 316 to 350
  USE OnlineDev ${OnlineVersion} AlignmentOnline vXXrY)
Added:
>
>
You are now ready to compile (as online):

online@plus $ dataflowcmt
online@plus $ cd $User_release_area
online@plus $ cd AlignmentOnlineDev_vXXrY
online@plus $ do_configure
online@plus $ do_install
online@plus $ cmsetup

Once finished modify the link to the current and old version of AlignmentOnline:

user@plus $ rm AlignmentRelease_old
user@plus $ mv AlignmentRelease AlignmentRelease_old
user@plus $ ln -s AlignmentOnlineDev_vXrY AlignmentRelease
 

Troubleshooting

Revision 622017-03-02 - MaurizioMartinelli

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

Running the online alignment in run 2

Line: 299 to 299
  A new release area can be created with the following steps (as online):
Changed:
<
<
online@plus $ export User_release_area=/group/online/dataflow/cmtuser
>
>
online@plus $ dataflowcmt
 online@plus $ cd $User_release_area
Added:
>
>
online@plus $ use_slc6_gcc49
 online@plus $ lb-dev AlignmentOnline vXXrY online@plus $ cd AlignmentOnlineDev vXXrY

Revision 612016-11-21 - GiulioDujany

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

Running the online alignment in run 2

Line: 239 to 239
 If you want to produce the "standard plots " for Velo, Tracker and Muon you can use the script Alignment/AlignmentMonitoring/examples/makePublicityPlots.sh, it just calls the previous one with the appropriate options. You may want to open it and change some options like the min and max run number or the date in the label.
lb-dev Alignment v11r0
Changed:
<
<
AlignmentDev_v11r0
>
>
cd AlignmentDev_v11r0
 git lb-use Alignment git lb-checkout Alignment/master Alignment/AlignmentMonitoring make configure

Revision 602016-11-16 - GiulioDujany

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

Running the online alignment in run 2

Line: 239 to 239
 If you want to produce the "standard plots " for Velo, Tracker and Muon you can use the script Alignment/AlignmentMonitoring/examples/makePublicityPlots.sh, it just calls the previous one with the appropriate options. You may want to open it and change some options like the min and max run number or the date in the label.
lb-dev Alignment v11r0
Added:
>
>
AlignmentDev_v11r0
 git lb-use Alignment git lb-checkout Alignment/master Alignment/AlignmentMonitoring
Added:
>
>
make configure make -j8
 ./run Alignment/AlignmentMonitoring/examples/makePublicityPlots.sh

Revision 592016-09-08 - GiulioDujany

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

Running the online alignment in run 2

Line: 232 to 232
 
  • moniPlots_Muon.py to produce the plots for the Muon

To see how to use them call them with the -h option.

Added:
>
>

Make trend plots

To make the trend plots you can use the scripts Alignment/AlignmentMonitoring/scripts/trendPlots.py call it with the option -h to see the options available. If you want to produce the "standard plots " for Velo, Tracker and Muon you can use the script Alignment/AlignmentMonitoring/examples/makePublicityPlots.sh, it just calls the previous one with the appropriate options. You may want to open it and change some options like the min and max run number or the date in the label.
lb-dev Alignment v11r0
git lb-use Alignment
git lb-checkout Alignment/master Alignment/AlignmentMonitoring
./run Alignment/AlignmentMonitoring/examples/makePublicityPlots.sh
 

Update reference histograms in the presenter

Instructions to change the reference histograms in the presenter can be found in this page.

Revision 582016-06-29 - LuciaGrillo

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

Running the online alignment in run 2

Line: 234 to 232
 
  • moniPlots_Muon.py to produce the plots for the Muon

To see how to use them call them with the -h option.

Added:
>
>

Update reference histograms in the presenter

 
Added:
>
>
Instructions to change the reference histograms in the presenter can be found in this page.
 

Using the hlt1 conditions instead of the ones in the online.db

If you want to run on plus using the same hlt1 (and hlt2) conditions and not the one in the online.db you should use add the following options (example for a Brunel job).

Revision 572016-06-12 - GiulioDujany

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

Running the online alignment in run 2

Line: 226 to 226
 All the pdfs can be found here. The naming convention is FIRST_RUN_NUMBER.pdf if the update was not triggered or vVERSION_FIRST_RUN_NUMBER.pdf
Added:
>
>

Make the Automatically produced plots yourself

To make the automatically plroduced plots you can use the scripts in Alignment/AlignmentMonitoring/scripts/.

  • moniPlots.py to produce the plots for the Velo
  • moniPlots_Tracker.py to produce the plots for the Tracker
  • moniPlots_Muon.py to produce the plots for the Muon

To see how to use them call them with the -h option.

 

Using the hlt1 conditions instead of the ones in the online.db

If you want to run on plus using the same hlt1 (and hlt2) conditions and not the one in the online.db you should use add the following options (example for a Brunel job).

Revision 562016-06-09 - GiulioDujany

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

Running the online alignment in run 2

Line: 171 to 171
  From this panel you can select the cond db and dddb tags needed, and Save the update with the buttom at the bottom of the window. (you will be asked to confirm your choice before the change is saved).
Added:
>
>
ALERT! NOTE: It is possible that you also have to change also the version on Moore to the latest version.
 TrigConfig_edit.png

ALERT! NOTE: Once you have saved the new tags, for the give trigger configuration (PassThrough in this case), you need to select again the Trigger configuration (PassThrough in this case) in the LHCb_Align TOP level panel.

Revision 552016-06-02 - GiulioDujany

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

Running the online alignment in run 2

Line: 207 to 207
 We have one root file for each iteration, they are at: the histograms are at /hist/Savesets/2015/LHCbA/ Nomenclature convention:
Changed:
<
<
ex. /hist/Savesets/2015/LHCbA/AligWrk_Muon/07/10/AligWrk_Muon-15691601-20150710T100630-EOR.root
>
>
ex. /hist/Savesets/2015/LHCbA/AligWrk_Muon/07/10/AligWrk_Muon-15691601-20150710T100630-EOR.root
 
  • Muon is the name of the activity (Muon, Tracker or Velo)
  • 156916 is the first run number in the run list
  • 01 is the number of iteration
Line: 216 to 216
 To run root on plus: lb-run root root.exe FILENAME.root
Added:
>
>

Location of Automatically produced plots

A pdf containing monitoring and convergency plots is produced after the alignment (only a pdf is produced per run analysed). If the alignment needs updating or if the variation of the alignment constants is too big the pdf is uploaded to the logbook. If no alignment update is needed the pdf is not attach to the logbook but only a message appears. All the pdfs can be found here. The naming convention is FIRST_RUN_NUMBER.pdf if the update was not triggered or vVERSION_FIRST_RUN_NUMBER.pdf

 

Using the hlt1 conditions instead of the ones in the online.db

If you want to run on plus using the same hlt1 (and hlt2) conditions and not the one in the online.db you should use add the following options (example for a Brunel job).

Revision 542016-05-28 - LuciaGrillo

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

Running the online alignment in run 2

Line: 150 to 150
 

Check and change the CONDDB and DDDB tags used by the Alignment

The CONDDB (LHCBCOND) and DDDB tags used by the LHCb_Align project are currently (April-May 2016) not automatically propagated from the tags used in the HLT. Therefore when there is a change in the tags used by the HLT, we need to update the tags used by the online Alignment as well.

Changed:
<
<

Check the CONDDB and DDDB tags currently used by Alignment

>
>

Check the CONDDB and DDDB tags currently used by Alignment

  On the LHCb_Align panel click on the "View.." button next to the Trigger Config
Line: 159 to 159
 The window that you now visualize, shows you the database tags currently used, but you cannot change them from this panel (see all the fields are grey and no "Save" button at the bottom of the window). To change the tags, see next point.

TrigConfig_view.png

Changed:
<
<

Change the CONDDB and DDDB tags to be used by the Alignment

>
>

Change the CONDDB and DDDB tags to be used by the Alignment

  On the LHCb_Align panel click on "RunInfo"
Line: 173 to 173
  TrigConfig_edit.png
Changed:
<
<
ALERT! NOTE: You can only choose the database tags which appear on the menu when you click on the arrow next to "Tags CONDDB (DDDB)". This is because you can only choose the tags which are already available for the HLT. (The HLT in order to make the tags available on the panels needs to put a snapshot into a specific location). For the Alignment we will always have to select a tag which is already available for the HLT, because we have to be consistent in the tags we use, we will never need a tag not already available for the HLT.
>
>
ALERT! NOTE: Once you have saved the new tags, for the give trigger configuration (PassThrough in this case), you need to select again the Trigger configuration (PassThrough in this case) in the LHCb_Align TOP level panel.
 
Changed:
<
<
ALERT! NOTE: Once you have selected the desired CONDDB and DDDB tags needed, Please do a Reset of LHCbA TOP level
>
>
ALERT! NOTE: You can only choose the database tags which appear on the menu when you click on the arrow next to "Tags CONDDB (DDDB)". This is because you can only choose the tags which are already available for the HLT. (The HLT in order to make the tags available on the panels needs to put a snapshot into a specific location). For the Alignment we will always have to select a tag which is already available for the HLT, because we have to be consistent in the tags we use, we will never need a tag not already available for the HLT.
 

Monitoring the automatic procedure

Revision 532016-05-24 - GiulioDujany

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

Running the online alignment in run 2

Line: 147 to 147
  and similarly for IT and OT. With the option --dry-run, the script only print the version used without changing it.
Changed:
<
<

Check and change the CONDDB and DDDB tags used by the Alignment

>
>

Check and change the CONDDB and DDDB tags used by the Alignment

  The CONDDB (LHCBCOND) and DDDB tags used by the LHCb_Align project are currently (April-May 2016) not automatically propagated from the tags used in the HLT. Therefore when there is a change in the tags used by the HLT, we need to update the tags used by the online Alignment as well.
Changed:
<
<

Check the CONDDB and DDDB tags currently used by Alignment

>
>

Check the CONDDB and DDDB tags currently used by Alignment

  On the LHCb_Align panel click on the "View.." button next to the Trigger Config
Line: 159 to 159
 The window that you now visualize, shows you the database tags currently used, but you cannot change them from this panel (see all the fields are grey and no "Save" button at the bottom of the window). To change the tags, see next point.

TrigConfig_view.png

Changed:
<
<

Change the CONDDB and DDDB tags to be used by the Alignment

>
>

Change the CONDDB and DDDB tags to be used by the Alignment

  On the LHCb_Align panel click on "RunInfo"

Revision 522016-05-24 - LuciaGrillo

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

Running the online alignment in run 2

Line: 19 to 19
 The firs thing to do is to write your name in the appropriate field and click on Reserve Alignment so that people know who to contact in case of need.

ALERT! Usually the farm should be taken by the run control in shared mode. if this is not the case you may have to:

Changed:
<
<
  1. take the project: click on the grey open lock and choice "take";
  2. Allocate: click on the State menu and select Allocate.
>
>
  1. take the project: click on the grey open lock and choice "take";
  2. Allocate: click on the State menu and select Allocate.
  panel.png
Line: 147 to 147
  and similarly for IT and OT. With the option --dry-run, the script only print the version used without changing it.
Changed:
<
<

Check and change the CONDDB and DDDB tags used by the Alignment

>
>

Check and change the CONDDB and DDDB tags used by the Alignment

  The CONDDB (LHCBCOND) and DDDB tags used by the LHCb_Align project are currently (April-May 2016) not automatically propagated from the tags used in the HLT. Therefore when there is a change in the tags used by the HLT, we need to update the tags used by the online Alignment as well.
Changed:
<
<
Check the conddb and dddb tags currently used by Alignment
>
>

Check the CONDDB and DDDB tags currently used by Alignment

  On the LHCb_Align panel click on the "View.." button next to the Trigger Config
Changed:
<
<
>
>
LHCbA_TrigConfView.png
  The window that you now visualize, shows you the database tags currently used, but you cannot change them from this panel (see all the fields are grey and no "Save" button at the bottom of the window). To change the tags, see next point.
Changed:
<
<

Change the conddb and dddb tags

>
>
TrigConfig_view.png

Change the CONDDB and DDDB tags to be used by the Alignment

  On the LHCb_Align panel click on "RunInfo"
Changed:
<
<
>
>
LHCbA_RunInfo.png
  and in the "RunInfo" panel, select Trigger Configuration, Create/Edit
Changed:
<
<
>
>
RunInfo_CreateEdit.png
  From this panel you can select the cond db and dddb tags needed, and Save the update with the buttom at the bottom of the window. (you will be asked to confirm your choice before the change is saved).
Changed:
<
<
>
>
TrigConfig_edit.png
  ALERT! NOTE: You can only choose the database tags which appear on the menu when you click on the arrow next to "Tags CONDDB (DDDB)". This is because you can only choose the tags which are already available for the HLT. (The HLT in order to make the tags available on the panels needs to put a snapshot into a specific location). For the Alignment we will always have to select a tag which is already available for the HLT, because we have to be consistent in the tags we use, we will never need a tag not already available for the HLT.
Line: 387 to 390
 
META FILEATTACHMENT attachment="runs4Align.py.txt" attr="" comment="script for knowing which runs for each fill are available on the HLT farm" date="1434637370" name="runs4Align.py.txt" path="runs4Align.py.txt" size="2410" user="gdujany" version="1"
META FILEATTACHMENT attachment="panel.png" attr="" comment="first panel" date="1438162113" name="panel.png" path="panel.png" size="78977" user="gdujany" version="3"
META FILEATTACHMENT attachment="runsSelector.png" attr="" comment="panel to select runs" date="1441962344" name="runsSelector.png" path="runsSelector.png" size="38867" user="sborghi" version="2"
Added:
>
>
META FILEATTACHMENT attachment="LHCbA_TrigConfView.png" attr="" comment="LHCbA TOP panel with the button to view the Trigger Config highlighted" date="1464095483" name="LHCbA_TrigConfView.png" path="LHCbA_TrigConfView.png" size="105374" user="lgrillo" version="1"
META FILEATTACHMENT attachment="TrigConfig_view.png" attr="" comment="LHCbA Trigger Config View pannel" date="1464096123" name="TrigConfig_view.png" path="TrigConfig_view.png" size="116496" user="lgrillo" version="1"
META FILEATTACHMENT attachment="LHCbA_RunInfo.png" attr="" comment="LHCbA TOP panel with the %22RunInfo%22 button highlighted" date="1464096223" name="LHCbA_RunInfo.png" path="LHCbA_RunInfo.png" size="103373" user="lgrillo" version="1"
META FILEATTACHMENT attachment="RunInfo_CreateEdit.png" attr="" comment="LHCbA RunInfo panel with Trigger Config create/edit button highlighted" date="1464096713" name="RunInfo_CreateEdit.png" path="RunInfo_CreateEdit.png" size="72537" user="lgrillo" version="1"
META FILEATTACHMENT attachment="TrigConfig_edit.png" attr="" comment="LHCbA Trigger Config Create/Edit panel" date="1464096778" name="TrigConfig_edit.png" path="TrigConfig_edit.png" size="130051" user="lgrillo" version="1"

Revision 512016-05-24 - GiulioDujany

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

Running the online alignment in run 2

Line: 14 to 14
  /group/online/ecs/Shortcuts311/LHCb/ECS/ECS_UI_FSM.sh
Changed:
<
<
Open the LHCb_Align tree (right click). If the tree is locked, take control (ask permission to the online piquet) by using the grey padlock.
>
>
Open the LHCb_Align tree (right click).
 
Changed:
<
<
panel.png
>
>
The firs thing to do is to write your name in the appropriate field and click on Reserve Alignment so that people know who to contact in case of need.

ALERT! Usually the farm should be taken by the run control in shared mode. if this is not the case you may have to:

  1. take the project: click on the grey open lock and choice "take";
  2. Allocate: click on the State menu and select Allocate.
 
Deleted:
<
<
The first action to perform is take the project: click on the grey open lock and choice "take"; write your name in the appropriate field and click on Reserve Alignment so that people know who to contact in case of need Then Allocate: click on the State menu and select Allocate.
 
Changed:
<
<
ALERT! NOTE: Usually the farm should be taken by the run control in shared mode. In this case it is not needed to take the partition but writing one's name is enough.
>
>
panel.png
  Then select the activity from the menu on the right of the Run Info panel. Normally, alignment activities are performed in this order:
  1. VELO
Line: 30 to 32
 
  1. RICH
  2. Muon
Changed:
<
<
Now you should select the run range to use in the alignment. This procedure will be fully automated after an initial testing period. The runs to use are the first ones of each fill.
>
>
Now you should select the run range to use in the alignment.
 
Changed:
<
<
To select the run range, click on the Choose Runs for Alignmnet button. Select the runs from the list and click Ok.
>
>
To select the run range, click on the Choose Runs for Alignmnet button. Select the runs from the list and click Ok. The runs corresponding to the last fill are in the bottom of the tyable .
 It is possible to select runs from any other type of data for a given alignment activity (by default it proposes the data corresponding to the activity).

runsSelector.png

Line: 49 to 51
  errorLog_yellow.png
Changed:
<
<
You are now ready to start (to check- and modify in case- the function and the conditions that are used see sections "Function to be used" and "Alignment constants"). From the LHCb_Align PVSS panel, click on the menu at the top and choose Configure. This can take a few minutes.
>
>
You are now ready to run the alignment: turn on the Auto Pilot and wait that it does the Configure and Start run. This will take several minutes; when it will be done everything should be in ready and the autopilot should be off.

(to check- and modify in case- the function and the conditions that are used see sections "Function to be used" and "Alignment constants")

Running without the autopilot

From the LHCb_Align PVSS panel, click on the menu at the top and choose Configure. This can take a few minutes.

  If the HLT subtree goes in Error state, you can open it and exclude the nodes or farms in error using the arrows in the Quick actions panel. To locate the troubling nodes, have a look at the PARTAlign tree.
Line: 169 to 177
  ALERT! NOTE: You can only choose the database tags which appear on the menu when you click on the arrow next to "Tags CONDDB (DDDB)". This is because you can only choose the tags which are already available for the HLT. (The HLT in order to make the tags available on the panels needs to put a snapshot into a specific location). For the Alignment we will always have to select a tag which is already available for the HLT, because we have to be consistent in the tags we use, we will never need a tag not already available for the HLT.
Changed:
<
<
ALERT! NOTE: Once you have selected the desired CONDDB and DDDB tags needed, Please do a Reset of LHCbA TOP level
>
>
ALERT! NOTE: Once you have selected the desired CONDDB and DDDB tags needed, Please do a Reset of LHCbA TOP level
 

Monitoring the automatic procedure

Line: 193 to 201
 
    • The constants are available in the online.db for all the runs declared ready for hlt2. Time validity time of the start of the run to the next run with valid constants (if no further run, infinite).

Changed:
<
<
    • The location of the Survey info can be found in: /group/online/dataflow/cmtuser/AlignmentOnlineDev_v10r6/Alignment/SurveyConstraints.py and it is called by AlignmentScenarios.py (in the same directory)
>
>
    • The location of the Survey info can be found in: /group/online/dataflow/cmtuser/AlignmentOnlineDev_v10r6/Alignment/SurveyConstraints.py and it is called by AlignmentScenarios.py (in the same directory)
 

Histograms location

Line: 248 to 256
 
  • It is possible that the job become stuck with the PARTAlign_Master in running and the various nodes (e.g. HLTA05_A) in ready. In this case from the top tree select again start run
Changed:
<
<
  • If only few nodes are in the "Included Nodes and Removed Nodes" in the panel Quick Actions of the window LHCbA _HLT: TOP, try to DEALLOCATE and then ALLOCATE again from the Top panel
>
>
  • If only few nodes are in the "Included Nodes and Removed Nodes" in the panel Quick Actions of the window LHCbA _HLT: TOP, try to DEALLOCATE and then ALLOCATE again from the Top panel
 
  • The histograms created before 21st July have a bug for all iterations except the first one (the histograms were not reset before filling in the second (or more) iterations, this results in histograms including entry of first iteration and second iteration (and all the previous for the other iterations). This problem was fixed on 21st July, thus re-running would produce the correct histograms.
Line: 323 to 331
 

Where in the code

The DIM service publish the content of the string m_align_message that has the following structure:

Changed:
<
<
"SeverityLevel: Subdetector message" where SeverityLevel can be INFO, WARNING or ERROR. In case of WARNING or ERROR an email will be sent to lhcb-onlinealignmentcalibration@cernNOSPAMPLEASE.ch; in case of ERROR a message will also appear in the alarm screen and require immediate action. The message will disappear at the next run of the alignment on the same subdetector when an INFO message is found.
>
>
"SeverityLevel: Subdetector message | further informations" where SeverityLevel can be INFO, WARNING or ERROR and the part = | further informations= is optional. In case of WARNING or ERROR an email will be sent to lhcb-onlinealignmentcalibration@cernNOSPAMPLEASE.ch; in case of ERROR a message will also appear in the alarm screen and require immediate action. In the alarm message only the Subdetector message will appear while the email will contain also the further informations. The error message will disappear at the next run of the alignment on the same subdetector when an INFO message is found.
 

How to see the dim service

Revision 502016-05-24 - LuciaGrillo

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

Running the online alignment in run 2

Line: 22 to 22
 write your name in the appropriate field and click on Reserve Alignment so that people know who to contact in case of need Then Allocate: click on the State menu and select Allocate.
Changed:
<
<
ALERT! NOTE: Usually the farm should be taken by the run control in shared mode. In this case it is not needed to take the partition but writing one's name is enough.
>
>
ALERT! NOTE: Usually the farm should be taken by the run control in shared mode. In this case it is not needed to take the partition but writing one's name is enough.
  Then select the activity from the menu on the right of the Run Info panel. Normally, alignment activities are performed in this order:
  1. VELO
Line: 141 to 139
  and similarly for IT and OT. With the option --dry-run, the script only print the version used without changing it.
Added:
>
>

Check and change the CONDDB and DDDB tags used by the Alignment

The CONDDB (LHCBCOND) and DDDB tags used by the LHCb_Align project are currently (April-May 2016) not automatically propagated from the tags used in the HLT. Therefore when there is a change in the tags used by the HLT, we need to update the tags used by the online Alignment as well.

Check the conddb and dddb tags currently used by Alignment

On the LHCb_Align panel click on the "View.." button next to the Trigger Config

The window that you now visualize, shows you the database tags currently used, but you cannot change them from this panel (see all the fields are grey and no "Save" button at the bottom of the window). To change the tags, see next point.