Ignore:
Timestamp:
08/04/06 10:40:48 (19 years ago)
Author:
tbretz
Message:
*** empty log message ***
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/MagicSoft/Mars/NEWS

    r7841 r7845  
    2626   - callisto: Updated absolute calibration constants (muon calibration)
    2727
     28   - callisto: fixed a bug which caused the hi-gain saturation not
     29     to be handled properly
     30
     31   - callisto fixed a bug which gave weird results if hi- and lo-gain
     32     could not be extracted properly
     33
    2834   - callisto: Fixed a bug regarding the use of the QE which doesn't
    2935     effect the result because the default is used anyhow.
    3036     (The bug was there since 14/07/2005)
     37
     38   - callisto: Changed the default for fgLoGainStartShift
    3139
    3240   - callisto: Fixed a bug which caused all hi-/lo-gain calibration
     
    3846     mainly for timing studies, not for the automatic standard analysis.
    3947
    40    - callisto: Implemented two new tabs, the pulse position of pulses
    41      not saturating the hi-gain (and above 50phe) and the pulse-position
    42      saturating the hi-gain (means the pulse position of signal extracted
    43      from the lo-gain and above 320phe) This can be used to check (and/or
    44      correct) the hi-/lo-gain offset.
     48   - callisto: Now tab "HiLoCal" which shows the ratio between hi- and
     49     lo-gain pulse for data pulses if hi- and lo-gain have saturated
     50     and both were extracted because the hi-gain was above the
     51     LoGainSwitch.
     52
     53   - callisto: Now tab "HiLoOff" which shows the offset between hi- and
     54     lo-gain pulse position (after application of LoGainOffset, which
     55     means in the ideal case it is 0) for data pulses if hi- and lo-gain
     56     have saturated and both were extracted because the hi-gain was above
     57     the LoGainSwitch.
    4558
    4659   - callisto: After extensive tests a new threshold level for determination
     
    5063     range and starts sticking to non-floating point numbers (5, 6, 7, ...)
    5164
    52    - star: changed the fit for the ffective on time such that initial
     65   - star: changed the fit for the effective on time such that initial
    5366     values are calculated automatically now instead of using build
    5467     in values. This makes the fit more indepedant of the underlaying
Note: See TracChangeset for help on using the changeset viewer.