Closed joefowler closed 2 years ago
Original comment by Charles James Titus (Bitbucket: cjtitus, GitHub: cjtitus).
mass.EnergyCalibration with 6 entries
_ph: [-8842.82888657 15241.96150853 19054.56935384 19216.77239457
23806.29451809 29847.9585508 ]
_energies: [704.8 524.9 851.47 929.68 277. 392.4 ]
_names: ['FeLAlphaquick_linequick_line', 'OKAlphaquick_linequick_line', 'NiLAlphaquick_linequick_line', 'CuLAlphaquick_linequick_line', 'CKAlphaquick_linequick_line', 'NKAlphaquick_linequick_line']
_curvetype: 3
_use_approximation: False
This seems to be because the _ph in the energy calibration has a negative point. I suggest that calibrations that result in negative points be marked as bad.
Original comment by Charles James Titus (Bitbucket: cjtitus, GitHub: cjtitus).
I will also note that the _ph are in order of increasing energy, but the _energies are not. This sort of cross-over should never happen, and should result in a calibration being immediately marked bad. This channel indeed is missing the high energy peaks
as compared to a normal channel
The “dynamic time warping” algorithm seems to have just totally ignored this and spit out some garbage points.
Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).
Calibration should fail when PH,E not monotonic
Fixes #216.
Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).
Removing milestone: v0.7 (automated comment)
Original report by Charles James Titus (Bitbucket: cjtitus, GitHub: cjtitus).
Somehow, for some channels, the simple npts calculation in update_converters fails, and yields a negative npts.
This results in an uncaught exception. I will try to investigate exactly why this happens.