Next: On-line analysis Up: MiniDAQ instructions Previous: Copying data to mass storage

Obsolete!!! Obsolete!!! Obsolete!!!

See the Release notes and/or the start-up information for tpm V3.2.

Using Pad Monitor

PadMonitor supports 8- and 10-bit data, in native mode or mapped onto the padplane, with or without zero-suppression. It can also display the pedestal run results, but it is necessary to filter these events from the data stream with an independent version of Staf.

PadMonitor can display only data from the data stream. It is up to the user to request the necessary tables through Run Control (before ``Getset''), choosing from amongst those available for a given run type.

Since MiniDAQ supports on-line pedestal subtraction, with the pedestals averaged over many events, it is best to subtract pedestals this way. However, an alternative scheme is outlined below.

To pedestal-subtract data within PadMonitor:

  1. Save a raw pedestal event file to disk.
  2. Run a Staf executable containing the tfc package, such as:
    ~staronl/tfc/bin/irix/tfcStaf or
    ~staronl/tfc/bin/sun4os5/tfcStaf).
  3. Execute the ~staronl/tcl/wrk/macros/correct_data.kumac macro. It will ask for:
  4. The macro will subtract pedestals and write out events in a PadMonitor-readable format, so the data can be inspected before doing hit-finding.

To exit PadMonitor:

  1. Select Return to Staf via the Staf pull-down menu at the top of the PadMonitor screen.
  2. At the Staf prompt, type exit .
  3. Under Solaris, Staf will dump core as it exits (a ``feature'').


Written: October 7, 1996 by Nathan Stone
Last modified: May 25, 1997 by Susanna Jacobson and R.Bossingham


Page maintenance:

Roy Bossingham, LBNL
RRBossingham@lbl.gov