• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT

    User name A. Deur

    Log entry time 21:01:37 on July18,2003

    Entry number 104543

    This entry is a followup to: 104516

    keyword=Helicity check

    I looked at run 2416, 2417 and 2418 taken for helicity check.

    run 2418 was a good run. I applied relatively loose cut on reconstructed quantities and pid detectors so I am sure to clean up any junk. The asymmetry found is:
    3.52% +/- 0.28
    we had no events 2 (no error message was diplayed during the replay) and 1.16% of the events are helicity 0.


    2416 and 2417 were bad runs (wrong prescaler and 100% deadtime) and display the usual error message when replayed. After analysis, all of the events are helicity 2 . But I don't know if we should conclude from this that the error messages we see on other (good) runs are trigger by deadtime.