Ignore:
Timestamp:
07/13/05 19:06:26 (20 years ago)
Author:
tbretz
Message:
*** empty log message ***
File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/MagicSoft/Mars/NEWS

    r7180 r7188  
    3333   - callisto: MCalibrationHiLoCam can now be printed from its context
    3434     menu, eg in the TBrowser
     35
     36   - callisto: fixed logain offset (fgOffsetLoGain) from 1.7 to
     37       - 1.39 (MExtractTimeAndChargeSpline)
     38       - 1.40 (MExtractTimeAndChargeDigitalFilter)
     39     This is important mainly for timing studies.
     40
     41   - callisto: Changed limits in MHCalibrationChargeCalc from
     42       - -100.125 to -98   (fgChargeHiGainFirst)
     43       - 1899.875 to 1902. (fgChargeHiGainLast)
     44       - -100.25  to -99   (fgChargeLoGainFirst)
     45       - 899.75   to 901.  (fgChargeLoGainLast)
     46     Introduced new limits:
     47       - fgNumLoGainBlackoutLimit: 0.05
     48       - fgLoGainBlackoutLimit: 3.5
     49       - fgLoGainPickupLimit: 3.5
     50
     51   - callisto: use a new criterium to exclude bad pixels: If the high-gain
     52     was saturated and the blackout-events in the low-gain exceed the
     53     fNumLoGainBlackoutLimit, the pixel is declared unsuitable.
     54     This excludes those pixels which have a saturating high-gain
     55     channel, but the low-gain switch does not switch often enough
     56     to make the distribution reliable.
     57
     58   - callisto: fix a bug counting the number of saturated events. Up to now,
     59     the number of saturated slices was counted (which is one for a not too
     60     high number), but for some (pathological) pixels, many more slices
     61     saturated and produced wrong limits.
     62
     63   - callisto: New options in in callisto.rc for MCalibrationRelTimeCalc:
     64     + MCalibrationRelTimeCam.CheckFitResults: Yes
     65     + MCalibrationRelTimeCam.CheckDeviatingBehavior: Yes
     66     + MCalibrationRelTimeCam.CheckHistOverflow: Yes
     67     + MCalibrationRelTimeCam.CheckOscillations: Yes
     68
     69   - callisto: introduce max. number of events for intercalibration,
     70     the rest gets skipped. Default: 4096
     71     The calibration causes too many un-reliable pixels if more
     72     than about 5000 events are treated (@500 Hz) because of the
     73     mode hopping of the VCSels. However, in the past, some
     74     calibration runs have been taken (erroneously) with more
     75     than 5000 events, especially the intensity scans where 
     76     a good precision is needed.
    3577
    3678   - star: fixed a bug which caused MEffectiveOnTime containers not to
Note: See TracChangeset for help on using the changeset viewer.