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

Legend:

Unmodified
Added
Removed
  • trunk/MagicSoft/Mars/mbadpixels/MBadPixelsPix.cc

    r5797 r7188  
    4444// are coded in the following form:
    4545//
     46//
     47// * Set bits leading to an unsuitable flag:
     48//
     49// BIT(7 ): kLoGainSaturation     :  The Low Gain signals were saturated during calibration
     50// BIT(8 ): kChargeIsPedestal     :  The calibration signal contained only pedestals - presumably dead pixel
     51// BIT(12): kMeanTimeInFirstBin   :  The signal has its mean maximum in the first used FADC slice - signal extractor bad
     52// BIT(13): kMeanTimeInLast2Bins  :  The signal has its mean maximum in the last two used FADC slice - signal extractor bad
     53// BIT(14): kDeviatingNumPhes     :  The calculated number of phes deviates by more than +6-5.5 sigma of the phes mean of the same area idx.
     54// BIT(19): kHiGainOverFlow       :  The Hi-Gain calibration histogram showed overflow in more than 0.5% of the events
     55// BIT(20): kLoGainOverFlow       :  The Lo-Gain calibration histogram showed overflow in more than 0.5% of the events
     56// BIT(23): kDeadPedestalRms      :  The pedestal RMS was 4.5 sigma below or 25 sigma above the average per area idx.
     57// BIT(24): kFluctuatingArivalTimes: The RMS of the position of the pulse maximum is larger than 3.5 FADC slices.
     58// BIT(24): kLoGainBlackout       :  A high gain saturated pixel had too many blackout events in the low gain
     59//
     60//
    4661// * Set bits leading to an unreliable flag:
    4762//
     
    5267// BIT(5 ): kLoGainOscillating   :  The Low  Gain signals fourier transform showed abnormal behavior 
    5368// BIT(6 ): kRelTimeOscillating  :  The High Gain arrival times fourier transform showed abnormal behavior 
    54 // BIT(14): kDeviatingNumPhes    :  The calculated number of photo-electrons deviates too much from the mean - inconsistency
     69// BIT(11): kChargeSigmaNotValid :  The sigma of the signal distribution is smaller than the pedestal RMS - presumably a pixel with a star in its FOV only during the pedestal taking
    5570// BIT(16): kDeviatingFFactor    :  The calculated overall F-Factor deviates too much from the mean - inconsistency
    5671// BIT(15): kDeviatingNumPhots   :  The calculated number of calibrated photons deviates too much from the mean - inconsistency
    5772//
    58 // * Set bits leading to an unsuitable flag:
    59 //
    60 // BIT(7 ): kLoGainSaturation    :  The Low  Gain signals were saturated during calibration
    61 // BIT(8 ): kChargeIsPedestal    :  The calibration signal contained only pedestals - presumably dead pixel
    62 // BIT(9 ): kChargeErrNotValid   :  The absolute error of the derived charge has given non-sense - presumably pedestal
    63 // BIT(10): kChargeRelErrNotValid:  The relative error of the derived charge was too large or too small
    64 // BIT(11): kChargeSigmaNotValid :  The sigma of the pedestal distribution smaller than the pedestal RMS - presumably a pixel with a star in its FOV only during the pedestal taking
    65 // BIT(12): kMeanTimeInFirstBin  :  The signal has its mean maximum in the first used FADC slice - signal extractor bad
    66 // BIT(13): kMeanTimeInLast2Bins :  The signal has its mean maximum in the last two used FADC slice - signal extractor bad
    67 // BIT(19): kHiGainOverFlow      :  The Hi-Gain calibration histogram showed overflow without saturating the FADC
    68 // BIT(20): kLoGainOverFlow      :  The Lo-Gain calibration histogram showed overflow
    6973//
    7074// * Set bits leading to not useable low-gain signal:
    7175//
    72 // BIT(17): kConversionHiLoNotValid: The calibrated Conversion between Hi-Gain and Low Gain gives absurd results
     76// BIT(17): kConversionHiLoNotValid: The inter-calibration constant between Hi-Gain and Low Gain does not exist.
    7377//
    7478// These bits can be called with the enum MBadPixelsPix::UncalibratedType_t in combination
Note: See TracChangeset for help on using the changeset viewer.