VMS FILTER
                ----------

    
b Physics Group:

- Most of our analyses use VMS FILTER to help determine trigger efficiencies
- Difficult to extract efficiencies from data, because we are dealing,
  generally, with low energy Large Tiles and Muons.
- Rely on VMS FILTER, but compare with data whenever possible
- IT IS IMPORTANT THAT ALL BUGS BE WELL DOCUMENTED!



Post-Geant Processing:

- Two things have hindered this project.

    1) VMS Filter only runs on VMS platform.
    2) It is difficult to get a handle on all VMS_FILTER bugs

- On a positive note: VMS FILTER runs quickly compared to D0Reco and NOISY.



A Suggestion for the future:

Currently we have the following methods for recording bugs:
   
    1) Release Notes
    2) D0Notes
    3) Ask your L2 rep and hope s/he remembers

The end user wants/needs to know:

    1) What is the bug
    2) What does it effect
    3) When did it begin and end
    4) Is it an online or Simulator Problem

This information can *usually* be extracted from the above mentioned sources,
but not always.  Sometimes you are forced to rely on the memories of the various
experts that originally fixed the problem (if they're still around)

A better reporting system needs to be created to record bugs.  Hopefully one
that the end user can understand.  (Web page?)....