New HCAL clustering in 72X

[bachtis]

Python configurations for the following :

1. Clustering of the HCAL from hits -removal of the custom PF CaloTower sequence. The clusters are made in layers and then merged to form multiplayer clusters using the Arbor algorithm and incorporating the transverse compatibility based on shower shapes
2. HCAL energy and time calculated with the two max time samples. Independently of the HCAL reconstruction the rechits are read and the 2 max time samples are used to define energy and time of the rec hits. This is a coarse stepo on what will be available in method 2.
3. 3D clustering with time. In this new reco OOT mitigation is done at clustering level by sharing the energy across the time dimension so that OOT clusters pull enerrgy out of in time clusters. Timing cuts are then applied on cluster level vs the energy and the HCAL layer before multidepth cluster creation.
4. Configurations changed to apply the same cleaning in HF in Data reconstruction as before
   -This cleaning has to be revisited and rediscussed with the HCAL DPG. Will try to bring it up
   in one of the next meetings to have uniform strategy for 73X

5.Fast sim configuration changed to remove special noise cuts in Fast sim as before

1. pfClusteringCutoms.py changed to revert to an HCAL reco that uses standard 2 clustering and energy and time from the default [whatever it is in the rechit] HCAL reco

[cmsbuild]

A new Pull Request was created by @bachtis for CMSSW_7_2_X.

New HCAL clustering in 72X

It involves the following packages:

Configuration/StandardSequences
FastSimulation/ParticleFlow
RecoParticleFlow/PFClusterProducer
RecoParticleFlow/PFProducer
SLHCUpgradeSimulations/Configuration

@civanch, @nclopezo, @lveldere, @vlimant, @mdhildreth, @cmsbuild, @franzoni, @StoyanStoynev, @slava77, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @mmarionncern, @GiacomoSguazzoni, @rovere, @VinInn, @cerati, @lgray 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.

[cmsbuild]

+1
Tested at: aedc6b0
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5195/835/summary.html

[civanch]

+1

[lgray]

@bachtis Agreed, this makes considerably more sense, good to see you got some of this under control.