Separate vertex truth matching from vertex validation EDAnalyzer

[makortel]

This PR separates the vertex truth matching part of PrimaryVertexAnalyzer4PUSlimmed to a separate associator (following the mechanism introduced in #9223). Also the features of #8852 are forward-ported here by adding

• a possibility to require minimum fraction of tracks shared by reco::Vertex and TrackingVertex (by default off, to keep the current behaviour)
• monitoring histograms for the shared track fraction with various denominators (extending what was done in Add monitoring plots for shared track fraction to vertex validation #8852)

The VertexAssociatorByPositionAndTracks is added to a sequence intentionally in TrackValidation_cff.py, because I intend to use it later also in track validation.

In addition, the following modifications to VertexAssociatorByTracksProducer, that would in principle have belonged to #9223, are included here

• Migrate to fillDescriptions
• Replace couts with LogDebug/LogTrace
• Pass EDProductGetter to AssociationMap constructor
• Add dictionary for VertexToTrackingVertexAssociator

Tested in CMSSW_7_5_X_2015-05-25-2300 and rebased to CMSSW_7_5_X_2015-05-27-1100 (due to dependence on #9223). No changes expected in existing histograms.

@rovere @VinInn

[cmsbuild]

A new Pull Request was created by @makortel (Matti Kortelainen) for CMSSW_7_5_X.

Separate vertex truth matching from vertex validation EDAnalyzer

It involves the following packages:

SimDataFormats/Associations
SimTracker/VertexAssociation
Validation/RecoTrack
Validation/RecoVertex

@civanch, @nclopezo, @danduggan, @mdhildreth, @cmsbuild, @deguio can you please review it and eventually sign? Thanks.
@GiacomoSguazzoni, @rovere, @VinInn, @appeltel, @wmtford, @cerati, @threus, @dgulhan, @venturia this is something you requested to watch as well.
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.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[civanch]

please test

[cmsbuild]

The tests are being triggered in jenkins.

[deguio]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

[davidlange6]

+1