As said in the RECO/AT meeting, the dataformat might still undergo changes
(some more data might have to be added if studies during CSA14 show that it
is needed to allow covering the needs of more analyses)

After that it can go into DF/RecoCandidate? (it currently depends on
TrackReco and VertexReco, so DF/Candidate might not be ok)
That could happen at the time it also goes in RECO (7.2.X?).
Do you think we should already put it in the reco namespace to reduce the
amount of trivial code changes that will be needed then?

    Giovanni
Il 14-apr-2014 19:19 "Slava Krutelyov" <notifications@github.com> ha
scritto:

> In DataFormats/PatCandidates/interface/PackedCandidate.h:
>
> > @@ -0,0 +1,432 @@
> > +#ifndef __DataFormats_PatCandidates_PackedCandidate_h__
> > +#define __DataFormats_PatCandidates_PackedCandidate_h__
> > +
> > +#include "DataFormats/Candidate/interface/Candidate.h"
> > +#include "DataFormats/Candidate/interface/CandidateFwd.h"
> > +#include "DataFormats/Candidate/interface/iterator_imp_specific.h"
> > +#include "DataFormats/Common/interface/RefVector.h"
> > +#include "DataFormats/Common/interface/Association.h"
> > +#include "DataFormats/VertexReco/interface/VertexFwd.h"
> > +#include "DataFormats/VertexReco/interface/Vertex.h"
> > +#include "DataFormats/Math/interface/deltaPhi.h"
> > +/* #include "DataFormats/Math/interface/PtEtaPhiMass.h" */
> > +
> > +namespace pat {
> > +  class PackedCandidate : public reco::Candidate {
>
> this is also fairly generic and could've been placed in
> DataFormats/Candidate
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/cms-sw/cmssw/pull/3253/files#r11595935>
> .
>