[PIPE2D-1330] Investigate the large scale feature of detectorMap offsets on detector Created: 14/Nov/23  Updated: 01/Feb/24  Resolved: 01/Feb/24

Status: Won't Fix
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Kiyoto Yabe Assignee: Satoshi Hamano
Resolution: Won't Fix Votes: 0
Labels: EDR
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to PIPE2D-1329 Individual fibers have significant of... Won't Fix
Sprint: EDR+AIT

 Description   

Satoshi Hamano reports the large scale feature of dx offset in the extractionQA with the latest rerun (edr2-20231106-qa); there is generally positive (negative) offsets in right(left)-hand side of the detector. Confirm that this is real and fix the problem. Some plots are hopefully posted later.



 Comments   
Comment by rhl [ 14/Nov/23 ]

How are you measuring these offsets? Are they consistent with the measurements in the arcLines files?

Comment by price [ 15/Nov/23 ]

At the meeting, Satoshi Hamano said the positions are measured by fitting a Gaussian to the image, and then the offset is calculated as the difference with respect to the detectorMap_used. However, I've been unable to reproduce these results (PIPE2D-1329) with the arcLine measurements, so I think we need more information. Satoshi Hamano said he could provide his work as a script that we could run in the next couple of days.

Comment by rhl [ 15/Nov/23 ]

There are details in even Gaussian fitting. I think Satoshi Hamano should take the lead on comparing his measurements with the arcLine files. It'd be good for him to look at some DCB data too, where crowding isn't an issue.

If the code isn't pushed to GitHub (presumably to tickets/PIPE2D-1330) that should be done as part of the delivery "as a script" – i.e. all the algorithmic parts should be in .py files in git.

Comment by Kiyoto Yabe [ 20/Jan/24 ]

The offset problem has been solved in PIPE2D-1329 and the results are reasonably consistent with detectorMapQa, so I think we can close this ticket.

Generated at Sat Feb 10 16:06:12 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.