Hi Slava;
I prefered AssociationMap because there was good enough documentation available for it.

https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookAssociationMap

Indeed, ValueMap may be better, but is there such documentation for it as well? Would it be compatible with the cases where the mapped Candidate collection is filtered after creating the map?
Thanks.


On Jul 29, 2013, at 3:00 PM, slava77 wrote:

> In DataFormats/HeavyIonEvent/interface/VoronoiBackground.h:
> 
> > +  double pt_corrected;
> > +
> > +  double mt_preeq;
> > +  double mt_posteq;
> > +  double mt_corrected;
> > +
> > +  double voronoi_area;
> > +  //RefVector of neighbors...
> > +
> > +};
> > +
> > +
> > + // typedef edm::AssociationMap<edm::OneToValue<reco::PFCandidateCollection, reco::VoronoiBackground> > VoronoiBackgroundMap;
> > + // typedef edm::AssociationMap<edm::OneToValue<reco::CandidateCollection, reco::VoronoiBackground> > VoronoiBackgroundMap;
> > +
> > + typedef edm::AssociationMap<edm::OneToValue<reco::CandidateView, reco::VoronoiBackground> > VoronoiBackgroundMap;
> AssociationMap should be avoided for performance reasons. If every PFCandidate in the reference collection has a VoronoiBackground computed, then use ValueMap
> 
> —
> Reply to this email directly or view it on GitHub.
>