[PIPE2D-624] Resolve discontinuity in 2D FRD residuals Created: 18/Aug/20  Updated: 05/Jan/21  Resolved: 05/Sep/20

Status: Done
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Normal
Reporter: Brent Belland Assignee: Brent Belland
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 2DResidualsTotal.png     PNG File 2D_zerocenter.png     PNG File No_Recentering.png     PNG File Wavefront_test2.png    
Issue Links:
Blocks
blocks PIPE2D-602 Determine better diagnostics for FRD ... Open
blocks PIPE2D-613 Detectability of f-ratio in lab data In Progress
Relates
relates to PIPE2D-625 Neven - Resolve discontinuity in 2D F... Done
Sprint: 2DDRP-2021 A

 Description   

Comparison between residuals between detector images in focus between two FRD values show noticeable jumps between the third and fourth row, as well as between the 5th and 6th column. While the jump between the third and fourth row is likely correlated with the large spatial distance between the wavelengths of the lines in the detector, there is no apparent reason why there should be such a jump between the 5th and 6th column. This raises the question of if there is an issue with previous analysis, and if so, how it effects previous results. This ticket is to determine what is causing the issue and address these concerns.



 Comments   
Comment by Brent Belland [ 18/Aug/20 ]

The wavefronts at each position of the detector have been calculated and compared to those of PIPE2D-489, since (1) wavefront differences likely drive the FRD residuals, and (2) discrepancies between these wavefronts and those in PIPE2D-489, made from the same data set, would indicate an issue with wavefront incorporation in my FRD code. Wavefront_test2.png demonstrates the wavefronts I extracted, which qualitatively mirror that from PIPE2D-489. The FRD residual jump in 2DResidualsTotal.png between the third and fourth rows is also correlates with a large wavefront change between these rows. No clear reason driving the 5th and 6th column jump is apparent, however.

Comment by Brent Belland [ 18/Aug/20 ]

PSFs with and without the masking due to the camera, spiders, and slit were compared; these likely do not drive the large residual jump.

Comment by Brent Belland [ 18/Aug/20 ]

No_Recentering.png displays the residuals in 2D across the detector when the recentering algorithm is not implemented in the code. The most immediately noticeable trait is the continuity of the residual magnitudes across the detector across columns. This raises the strong possibility that the PSF alignment introduces the large discontinuity seen in No_Recentering.png. While recentering attempts in the oversampled regions were attempted, they failed due to poor downsampling implementation. Thus resulting in recentering in the downsampled region. Of course, recentering in the downsampled region can lead to artifacts in the image that may manifest with enough of a change in the initial centroid (which correlates with detector position). Currently I am rewriting my recentering code for the oversampled data after advice from Neven; the hope is that incorporating this will resolve this issue.

It should be noted that a similarly continuous 2D residual distribution across the detector was found when setting the z4, z11, and z22 components of the wavefront to 0; however, these circularly symmetric Zernikes were not expected to be the cause of the strong asymmetry of residual magnitudes across the 5th and 6th columns.

Comment by Brent Belland [ 05/Sep/20 ]

2D_ZeroCenter.png shows the 2D residuals when the center of the illumination and the fiber are set to have zero offset. Notably, the discontinuity in the 2D residuals is not present in this figure, indicating that the fiber-illumination offset was driving the discontinuity.

Generated at Sat Feb 10 15:55:32 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.