MVD software "to do" list

The following list of people and jobs is based on discussions at MVD group meetings in Los Alamos. The list was first created in October 1997. Periodically, I remove completed jobs from the list and add new jobs. The previous version of this list is available here.

First, things which we must do for the Mock Data Challenge:

  • create input calibrations file with calibration constants -- (SangSoo)
  • separation of ``data'' and ``real'' quantities (John is working on this)
  • fix dN/deta from pads, since it seems to be broken -- (John) (DONE)
  • fill official output tables -- (JungHwan)
  • finalize pisa model of MVD -- (John)
  • remake CDR plots -- (part, not all, being done by Mike and John).

    Next, things we should do before the Mock Data Challenge, but are not absolutely necessary.

  • calibration software to take "data" and produce calibrations -- (SangSoo)
  • remove HBOOK use from analysis modules and use tnt at end of event. I am not sure this is what we should do right now, but at the minimum we should change the code to use a separate directory for the MVD code. This is discussed in several email messages including a message sent by Jeff Mitchell to phenix-trksoft-l and a reply from Charlie Maguire.
  • 3D vertex finding -- (JungHwan) (DONE)
  • discriminator performance -- (John)
  • code to turn output on/off/and change volume of output -- (John) (DONE)

    Finally, things we could do for the Mock Data Challenge, but could be done later.

  • Convert MVD code to C++ -- (JungHwan)
  • improved vertex algorithms -- (James and GuangHua)
  • try to speed up code

    updated April 30, 1998
    John P. Sullivan, sullivan@lanl.gov