Add vtx smearing parameters from run 247324

[rmanzoni]

Add vtx smearing parameters from run 247324, as needed by dN/dEta analysis

[cmsbuild]

A new Pull Request was created by @rmanzoni (Riccardo Manzoni) for CMSSW_7_5_X.

Add vtx smearing parameters from run 247324

It involves the following packages:

IOMC/EventVertexGenerators

@cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[civanch]

@rmanzoni , it is not enough to add vertex smearing parameters in this file. You need also add corresponding lines into CMSSW/​Configuration/​StandardSequences/​python/​VtxSmeared.py

[cmsbuild]

Pull request #9645 was updated. @cmsbuild, @civanch, @franzoni, @mdhildreth, @davidlange6 can you please check and sign again.

[rmanzoni]

@civanch sorry, now the PR should be complete.
However I don't understand why I see this conflict from the web interface
https://github.com/cms-sw/cmssw/pull/9645/files#diff-e1cee80113cf1157608571659e48271dL43
while I think it shouldn't be there, as this is what I see in 75X
https://github.com/cms-sw/cmssw/blob/CMSSW_7_5_X/Configuration/StandardSequences/python/VtxSmeared.py#L43

[civanch]

@rmanzoni , this I do not know, from my point of view current PR is OK.

[civanch]

please test

[cmsbuild]

The tests are being triggered in jenkins.

[cmsbuild]

-1
@rmanzoni This pull request cannot be automatically merged, could you please rebase it?
you can see the log for git cms-merge-topic here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9645/8206/git-merge-result

[civanch]

+1

[davidlange6]

@rmanzoni - could I ask we change the name of this ZeroTeslaDNDEtaCollision2015Vtx to Run247324Vtx so that its self documenting where the numbers came from later.

[civanch]

May be ZeroTeslaRun247324Vtx ?

[rmanzoni]

@davidlange6 @civanch either is fine to me, let me just check with the AlCa folks @mmusich @diguida, who proposed the current name in first place

[diguida]

@davidlange6 @civanch @rmanzoni last bet:

ZeroTeslaRun247324CollisionVtxSmearingParameters

In this way we know:

• It is a collision run
• We have a run number
• We know the magnet field.

[davidlange6]

+1
Beam spot and collisions seem redundant but ok for me