I just gave a talk at the Tracker DPG weekly meeting.

I outlined the next steps in getting a standard V0 reconstruction package into the CMSSW releases that will be run as part of the standard reconstruction chain, to be done by the end of June 07. This will involve the following (Steve Wagner's list):

need an EDProducter

takes arbritray list of tracks out of event

check to see if viable V0 candidate (overlap, angle between trks, charge, ...)

make every V0 fit for viable candidates

try 2 mass hypo (p+pi-, p-pi+, pi+pi-) and cut on mass

put successes into list

persist list (look thru DataFormats)

CMSSW/DataFormats/VertexReco/interface/Vertex.h good candidate

look thru existing documentation (Workbook, Vertex validation) to see
what people do already (b tagging group, Particle flow group)

generate package for module (EDProducer), make cfg, cfi, ...

add Workbook documentation so first thing CMS analyzer does is run default
-----------------------------------------------------------------------------

There was also some discussion about implementing TOB-TEC seeding for improved V0 reconstruction efficiency. We'd been looking at CMS IN-2007/017 for novel seeding algorithms, but Boris Magnano told me today that the CTF seeding is layer-agnostic, so we may be able to do TOB-TEC seeding without having to implement another full module -- might just have to make a new .cfi file that runs the seeding with whatever layers we want to use. This is down the road, though.

First priority is to get the check done, running right now, as to whether too many seeds being cleaned is the problem with RoadSearch efficiency in the 1_3_X series. I've run the standard 1_3_3 release, and it doesn't seem to have much of a positive effect (100 more events or so reconstructed of over 4000,) but Kevin Burkett gave me a couple of parameter changes, relaxing a vertex constraint AFAIK, and I'll see what the mass plots look like with these changes.

I'm also planning to shortly begin working on implementing the EDProducer module outlined above. The first step is to get some standard Monte Carlo samples (QCD jets will probably be the best bet) and loop over the tracks to find candidate charged track pairs to fit a vertex and do a mass cut to look for Vees. I'm going to start by implementing this in an EDAnalyzer, mainly because it's not clear yet which data format we should use to persist the reconstructed Vees into the Event.