SVT Offline basic tools + Trigmon

The points listed below are intended to be a starting point for discussion and a better definition of them. I came to this list after discussions with several people, mainly Stefano Belforte and Lorenzo Moneta who has done some work already.

These points are not in order of priority. Some of them are easy, some other are difficult (at least for me).

The main point which worries me is the access to the pattern bank in order to calculate the hit coordinates in the SVX wedges. Suggestions and informations are appreciated.

Once the SVTD specification and the bank unpacking/dump are done, histograms are the next thing. There are several nice ideas about "advanced" histograms. Simple histograms are already in the code.

• SVTD bank format
  • Specifications
  • Unpacking, dump, "official" routines, SVTDMonitor, SVTDTrack,...
  • Consistency between documentation and real format
  • "# of tracks" word
  • Hit coordinates are relative to the beginning of the superstrip instead of the wedge (possibility: include hit buffer output to simplify and/or do more checks); access to the pattern bank

• Histograms, tables, messages
  • Most of the analysis of the commissioning run data could be included in SVTMon/Trigmon
  • Possible histograms are:
    simple hit distributions (# of hits and position, ...),
    chi-square
    track combinations,
    background and fake rates,
    track constraints/wedge,
    no. of tracks/wedge,
    tracks 5/5 and 4/5,
    ghost check using extrapolation,
    eigenvalues and detector alignment (nominal vs. real constants),
    track parameters (fitted vs. calculated),
    beam alignment (including z align.) and profile,
    fast beam position fit
    histograms in luminosity bins (low-medium-high)
    ......

• Error reporting and recovery
  • "syntax" check for bank format
  • comparison with simulated trigger