• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT

    User name R. Michaels

    Log entry time 10:58:14 on October 7,2004

    Entry number 133257

    keyword=Helicity gated scaler code mod

    For the code that runs on TS1 which sorts the helicity gated scaler
    data by helicity, there was a problem that when the there are
    no triggers for a few minutes the "ring buffer" would wrap around.
    This almost never happened before because I always had some
    few-Hz pulser trigger. But it happens for several DVCS runs.

    For data with helicity in-time (as we run now), this "ring buffer"
    is irrelevant. It is a redundant check for delayed-helicity mode.
    But unfortunately the data from those periods were flagged,
    sorted, and stored as "bad". I fixed the logic so that when the
    helicity is in-time the ring buffer can wrap around and there is
    no error. This will take hold the next time you reboot TS1 crate.

    The (minor) implications: 1) Note, the normalization scaler which
    is NOT gated by helicity was NOT affected in any way; 2) The "bad"
    data are from periods of no beam, easily recognized in scalers, and
    you would presumably throw that out anyway. So the fact that some
    data from those periods was removed into the "bad" category would
    be ignored in any analysis of helicity scalers.