[PIPE2D-489] Characterize the RMS wavefront across the detector Created: 17/Dec/19  Updated: 14/Jan/20  Resolved: 04/Jan/20

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

Type: Task Priority: Normal
Reporter: ncaplar Assignee: ncaplar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Comparison_of_spots_sims_real_data.png     PNG File wavefront_across_detector_2d_full.png     PNG File wavefront_across_detector_2d_full_z4_11_22_set_to_0.png     PNG File wavefront_across_detector_2d_full_z4_11_22_set_to_0_Zemax.png     PNG File wavefront_across_detector_2d_full_Zemax.png     PNG File wavefront_across_detector_2d.png     PNG File wavefront_across_detector_2d_Zemax.png     PNG File wavefront_characterization.png     PNG File wavefront_characterization_Zemax.png     PNG File wavefront_characterization_Zemax_scaled_as_data.png    
Story Points: 8

 Description   

There were discussions during the PFS meting about focus issues and how to optimize the instrument. There was discussions about the difference between ensquared energy requirement and how does it correlate with wavefront parameters that I am determined from the donut analysis.  My understanding is that Jim wants to see the RMS wavefront error image across the detector and compare that with ensquared energy measured. I will verify this with Jim and than update this ticket. 



 Comments   
Comment by ncaplar [ 18/Dec/19 ]

Verified that this is indeed what Jim wanted to see. Produced the figure wavefront_characterization, which shows the evolution of the wavefront RMS, max value of wavefront - min value of wavefront and median value of wavefront. Jim was also interested in seeing a figure showing how wavefront changes across detector. 

Comment by ncaplar [ 19/Dec/19 ]

Added figure showing how wavefront changes across the detector. The wavefront positions correspond to positions in Figure wavefront_characterization. The limits on the color intensity is +- 3 waves.

 

 

Comment by ncaplar [ 19/Dec/19 ]

I am working on add these few spots which are missing. I do not think this is a systemic issue, I think it is just my error that those were not included. At the moment stuck in the queue on the cluster. 

Comment by ncaplar [ 31/Dec/19 ]

I have updated the figures, with 88 spots out of 90 available now. RHL asked to create the same plot without detector shadow - this is what I am working on now, it shouldn't be very hard.

Comment by ncaplar [ 31/Dec/19 ]

Added the ``full'' image.

Comment by ncaplar [ 03/Jan/20 ]

I added an image which shows the comparison of spots from the real data and the simulations (see also PIPE2D-443). From this figure you see that real data, taken in the corners of the detector, has larger aberrations than the simulated data. This is consistent with the statement made by Jim, who did not expect such large wavefront aberrations in the corners of the detector.  I will compose an email to send to LAM to hear their opinion tomorrow (Friday - Jan 3).

Jim asked if we could see how do simulated aberrations looks when going out of focus. Analysis of these images and comparison to the real data is the next step (probably a new ticket).

Comment by ncaplar [ 10/Jan/20 ]

I have added the images that show how individual Zernike components look at: https://sumire.pbworks.com/w/file/137918349/Individual_Zernike.zip

 

Comment by ncaplar [ 14/Jan/20 ]

I have added:

1. Wavefront images for which I have set z4, z11 and z22 at 0, i.e., all of the Zernike components which have only radial dependence are set at zero. This was requested by Kjetil in order to make it easier to see aberration components. 

2. I have also added all of the images describing the wavefront made in Zemax, based on work done in PIPE2D-421. As mentioned there  is always confusion in Zemax what is up-down, left-right. I do think that I am doing it correctly, but you should keep it as a caveat. 

 

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