Changeset 8217 for trunk/MagicSoft
- Timestamp:
- 12/04/06 14:26:04 (18 years ago)
- Location:
- trunk/MagicSoft/Mars
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/MagicSoft/Mars/Changelog
r8215 r8217 18 18 19 19 -*-*- END OF LINE -*-*- 20 2006/12/04 Thomas Bretz 21 22 * mcalib/MCalibrationChargeCalc.cc: 23 - fixed a typo in a console message 24 25 20 26 21 27 2006/11/16 Daniela Dorner -
trunk/MagicSoft/Mars/NEWS
r8214 r8217 182 182 not be opened. 183 183 184 - callisto: In some rare cases it could happen that in the hi-gain184 - callisto: In some rare cases it could happen that in the signal 185 185 extraction of the digital filter the extractor returned nonsense 186 results due a wrong initializion of a variable 186 results due a wrong initializion of a variable (this happens in 187 cases in which the extracted signal is exactly zero or the 188 digital filter couldn't slide because of a too small extraction 189 window, which could happen in the lo-gain extraction) 187 190 188 191 - callisto: The lo-gains have been marked as valid in some cases … … 195 198 196 199 - callisto: fixed a bug which caused the hi-gain saturation not 197 to be handled properly 200 to be handled properly in the spline (the position of the 201 saturation was calculated incorrectly) 198 202 199 203 - callisto: fixed a bug which gave weird results if hi- _and_ 200 lo-gain could not be extracted properly 204 lo-gain could not be extracted properly. In some cases hi- 205 and lo-gain have not been extracted at all and the random result 206 got calibrated. In other cases the hi-gain was saturating and the 207 lo-gain has not been extracted. For this a completly arbitraty 208 scale factor was applied to the result from extracting the 209 charge of the saturating hi-gain. 201 210 202 211 - callisto: improves handling of extracted signal if lo- and/or … … 207 216 - callisto: Fixed a problem in the spline extraction which gave 208 217 weird results if the signal was extracted from the first (and 209 highest) slice 218 highest) slice (as a workaround extraction from the first 219 slice has been forbidden) 210 220 211 221 - callisto: Fixed a bug regarding the use of the QE which doesn't … … 213 223 (The bug was there since 14/07/2005) 214 224 215 - callisto: Changed the default for fgLoGainStartShift 225 - callisto: Changed the default for fgLoGainStartShift to -2.4 216 226 217 227 - callisto: Fixed a bug which caused all hi-/lo-gain calibration -
trunk/MagicSoft/Mars/mcalib/MCalibrationChargeCalc.cc
r8147 r8217 1 1 /* ======================================================================== *\ 2 ! $Name: not supported by cvs2svn $:$Id: MCalibrationChargeCalc.cc,v 1.17 0 2006-10-23 12:27:21tbretz Exp $2 ! $Name: not supported by cvs2svn $:$Id: MCalibrationChargeCalc.cc,v 1.171 2006-12-04 14:22:29 tbretz Exp $ 3 3 ! -------------------------------------------------------------------------- 4 4 ! … … 1066 1066 if (!fExtractor) 1067 1067 { 1068 *fLog << err << "Extractor resolution has been chosen, but no textractor is set. Cannot calibrate." << endl;1068 *fLog << err << "Extractor resolution has been chosen, but no extractor is set. Cannot calibrate." << endl; 1069 1069 return kFALSE; 1070 1070 }
Note:
See TracChangeset
for help on using the changeset viewer.