The correct solution is what I implemented 1 year ago and I re-propose 
here. Note that for non 53X releases the fix is properly in. I was not 
aware that it was step back till few days ago. It should have not been 
removed. "Fortunately" at the time we implemented some protections at 
*analysis* level, but the definitive fix is that one.


On 09/03/2013 02:50 PM, Volker Adler wrote:
>
> In RecoMuon/MuonIdentification/plugins/MuonIdProducer.cc:
>
> > @@ -255,6 +255,7 @@ void MuonIdProducer::init(edm::Event& iEvent, const edm::EventSetup& iSetup)
> >     reco::Muon aMuon( makeMuon( *(track.get()) ) );
> >
> >     aMuon.setMuonTrack(type,track);
> > +   aMuon.setBestTrack(type);
>
> Indeed, 
> https://hypernews.cern.ch/HyperNews/CMS/get/relAnnounce/1237.html 
> shows the step backwards for RecoMuon/MuonIdentification.
> A comment is found here: 
> https://twiki.cern.ch/twiki/bin/view/CMS/OfflineComputingPlanningMeeting20121019#Reconstruction_AN1, 
> the outcome found here: 
> https://twiki.cern.ch/twiki/bin/view/CMS/OfflineComputingPlanningMeeting20121026#Status_of_CMSSW_5_3_X_Shahzad
> So, the not available tagset with the fix was substituted by using the 
> older tag again. Was that intentional? A temporary solution? What is 
> the /correct/ solution?
>
> —
> Reply to this email directly or view it on GitHub 
> <https://github.com/cms-sw/cmssw/pull/684/files#r6124315>.
>