Changeset 7029
- Timestamp:
- 05/13/05 15:45:46 (20 years ago)
- Location:
- trunk/MagicSoft/Mars
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/MagicSoft/Mars/Changelog
r7026 r7029 25 25 * mreport/MReportCC.cc: 26 26 - fixed reading of rep-files for versions newer than V200404070 27 28 * mpointing/MSrcPosCalc.cc 29 - took a bugfix from Wolfgang to Loc0LocToCam and implemented it 30 Wolfgang: the results are changed only minimally 31 32 * msignal/MExtractTimeAndChargeSpline.cc 33 - integration ranges were shifted by 0.2 FADC slices to the right. 34 Fixed in the new algorithm according to Markus' change. 27 35 28 36 -
trunk/MagicSoft/Mars/NEWS
r7026 r7029 45 45 the setter functions of MSeqeunce instead) 46 46 47 - fixed a bug in MExtractTimeAndchargeSpline which could cause48 different results with different compiler optimiztaion options49 due to rounding errors.50 51 47 - MEventRateCalc handles the calculation of the event rate more 52 48 accurate now in case of the start of a new run inside a sequence … … 63 59 can be canged 64 60 65 - improved sho log such that it handles different verbosity levels61 - improved showlog such that it handles different verbosity levels 66 62 more accurate now. This mean you can suppress output when 67 63 using showlog. … … 83 79 kFluctuatingArrivalTimes 84 80 85 - the calibration now does a consistency check of the arrival time86 87 81 - the charge timit in the calibration has been raised from 2.5 to 4.5 82 83 - fixed reading of CC-REPORTS (weather data) for Arehucas file versions 84 newer than V200404070 85 86 - a bug in MSrcPosCalc has been fixed (The changes were taken from 87 a bugfix of Wolfgang to Loc0LocToCam; Wolfgang: the results are 88 changed only minimally 88 89 89 90 - callisto: new setup read from callisto.rc … … 92 93 + MHCalibrationChargeCam.NumLoGainSaturationLimit 93 94 94 - fixed reading of CC-REPORTS (weather data) for Arehucas file versions 95 newer than V200404070 95 - callisto: MExtractTimeAndChargeSpline extractor: 96 + The integration ranges were shifted by 0.2 FADC slices to the right. 97 + unreliable handling of floating point values caused different 98 results on different platform or with different compiler options 99 100 - callisto: set new defaults in MExtractTimeAndChargeDigitalFilter: 101 + extraction range in the high gain to 4. 102 + weights file to cosmics_weights46.dat 103 104 - callisto: 105 + introduce the check for fluctuating arrival times. 106 + set charge limit to from 2.5 to 4.5 107 + introduce asymmetric exclusion due to "deviating number of phes": 108 Default: -9.0 +4.5 109 + make deviating number of phes unsuitable (see David's findings). 96 110 97 111 -
trunk/MagicSoft/Mars/mjobs/MJPedestal.cc
r7028 r7029 987 987 { 988 988 const MExtractTimeAndCharge &e = *static_cast<MExtractTimeAndCharge*>(fExtractor); 989 hpedcam.SetFitStart(-5*e ->GetWindowSizeHiGain());989 hpedcam.SetFitStart(-5*e.GetWindowSizeHiGain()); 990 990 } 991 991 else -
trunk/MagicSoft/Mars/msignal/MExtractTimeAndChargeSpline.cc
r6980 r7029 1072 1072 const Int_t n = TMath::Nint((last-start)/step); 1073 1073 1074 start += step/2; 1075 1074 1076 sum = 0.; 1075 for (Int_t i= 1; i<=n+1; i++)1077 for (Int_t i=0; i<=n; i++) 1076 1078 { 1077 1079 const Float_t x = start+i*step; … … 1112 1114 const Int_t n = TMath::Nint((last-start)/step); 1113 1115 1116 start += step/2; 1117 1114 1118 sum = 0.; 1115 for (Int_t i= 1; i<=n+1; i++)1119 for (Int_t i=0; i<=n; i++) 1116 1120 { 1117 1121 const Float_t x = start+i*step;
Note:
See TracChangeset
for help on using the changeset viewer.