-
Type:
Story
-
Status: Done (View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Satoshi Hamano reports that the detectorMap adjustment of 80906r1 has very poor quality.
Running with w.2022.46, I get the following summary stats:
reduceExposure.adjustDetectorMap INFO: Final result: chi2=107354.909901 dof=44438 xRMS=0.063492 yRMS=0.234515 xSoften=0.040791 ySoften=0.049777 from 34832 lines reduceExposure.adjustDetectorMap INFO: Stats for OH: chi2=60810.024394 dof=19260 xRMS=0.081180 yRMS=0.234515 xSoften=0.000000 ySoften=0.345114 from 9630 lines reduceExposure.adjustDetectorMap INFO: Stats for OI: chi2=0.000000 dof=0 xRMS=nan yRMS=nan xSoften=0.000000 ySoften=0.000000 from 0 lines reduceExposure.adjustDetectorMap INFO: Stats for Trace: chi2=46544.885507 dof=25202 xRMS=0.060551 yRMS=nan xSoften=0.051768 ySoften=0.000000 from 25202 lines
The "Final result" line looks like it might be acceptable at first glance, judging from the xSoften and ySoften values being ~ 0.05; though the yRMS value of 0.23 is concerning, one might think that it's just reflecting measurement errors. But when looking at the stats for OH lines, we see ySoften=0.345 and that's just unacceptable.
The expected position of lines using the adjusted detectorMap do not visually coincide with the lines on the image.