81x: add pixel barycenter computation tool

[mmusich]

Making available in release tool needed for Pixel barycenter computation:
https://twiki.cern.ch/twiki/bin/view/CMS/TkAlignmentPixelPosition

attn: @tlampen, @mschrode,
@ghellwig please comment if there is any other more suitable place to put this.

[cmsbuild]

A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_8_1_X.

It involves the following packages:

Alignment/MillePedeAlignmentAlgorithm

@ghellwig, @cerminar, @cmsbuild, @franzoni, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@mschrode, @ghellwig, @tocheng, @tlampen this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

[mmusich]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/13307/console

[mschrode]

@mmusich @ghellwig @tlampen How about moving it to Alignment/TrackerAlignment/macros?

[ghellwig]

@mmusich do I understand it correctly that you rely on MillePede only with this tool? If yes, I think it is already at the right place. If not, @mschrode's suggestion looks reasonable.

[mmusich]

@ghellwig yes, basically was an add-on from Gero Flucke to quickly derive the barycenter position, designed to be included in MillePedeAlignmentAlgorithm making use of the existing suite of macros availble in Alignment/MillePedeAlignmentAlgorithm/macros/GFUtils/.
There is no particular reason in general to use MillePede to do this job, but since the parsing of the output was already at hand...
I've just updated the configuration to make it work in current releases.

[ghellwig]

@mmusich ok, this means, in its current implementation it works only with MillePede, but in principal it could be generalized to use, let's say, the resulting sqlite file instead of the millepede.res file, right?
I would then say that the current location is fine.

[ghellwig]

Before approving, I would like to hear the final opinion of @mschrode and @tlampen

[cmsbuild]

+1
Tested at: 9540567
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14730/13307/summary.html

[tlampen]

For me it seems that the directory MillePedeAlignmentAlgorithm/macros/ contains only files related to MPS. Therefore TrackerAlignment/macros would sound a more consistent location. Does the depencency of MillePede cause difficulties in that location?

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14730/13307/summary.html

[cmsbuild]

Pull request #14730 was updated. @ghellwig, @cerminar, @cmsbuild, @franzoni, @mmusich, @davidlange6 can you please check and sign again.

[mmusich]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/13322/console

[mmusich]

@ghellwig @mschrode @tlampen I moved the configuration to Alignment/TrackerAlignment/test. The macro stays in MillePedeAlignmentAlgorithm where I think it should belong in any case. The Alignment/TrackerAlignment/macros sub-package in any case doesn't exist.

[mschrode]

@mmusich @ghellwig @tlampen OK I was not aware the script depends on tools in MillePedeAlignmentAlgorithm/macros. Then I fully agree, it should stay there.

[ghellwig]

+1
provided jenkins agrees

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

[cmsbuild]

+1
Tested at: a36a6a4
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14730/13322/summary.html

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14730/13322/summary.html

[davidlange6]

+1