https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/PIPE2D-631 DRP 2-D Pipeline <p>As mentioned in the comments of <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-614" title="Illumination estimate of the pupil should be constant across different defocuses for single spot" class="issue-link" data-issue-key="PIPE2D-614"><del>PIPE2D-614</del></a>, ``At the moment the code still effectively analyzes individual images, suggests solutions for each image, and then interpolates the solution before going to the next step in the iteration. The proper way would be to analyze all images at once. '' </p> <p>I am currently implementing this algorithm. </p> <p> </p> <p> </p> PIPE2D-631

Illumination constant defocuses - improvement of the analysis

Task Normal Done Done ncaplar ncaplar Wed, 2 Sep 2020 18:40:00 +0000 Mon, 4 Jan 2021 20:23:21 +0000 Fri, 20 Nov 2020 13:59:58 +0000 0 2 <p>I have implemented the analysis that truly fits all of the images at once, using the Tokovinin algorithm (see comments in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-614" title="Illumination estimate of the pupil should be constant across different defocuses for single spot" class="issue-link" data-issue-key="PIPE2D-614"><del>PIPE2D-614</del></a>). As it is obvious from the ``Fitting_example.png'', the fitting issues that I noticed in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-614" title="Illumination estimate of the pupil should be constant across different defocuses for single spot" class="issue-link" data-issue-key="PIPE2D-614"><del>PIPE2D-614</del></a> has not been removed by this procedure. </p> <p>Is this all images for one <tt>(fibre, wavelength)</tt> or all images for one fibre, or for the whole focal plane?  I suspect the first.</p> <p>Yes, it is the first, 9 images going into this evaluation. In this case, it is 3 images on one side of defocus (+4mm,+3.5mm,+3mm slit movement), 3 around focus (+0.5,0,-0.5), and 3 from other side of defocus (-4mm,-3.5mm,-3mm). </p> <p>It is quite fast, converging in about an hour while using 120 cores - but that is because it is a very brutal straightforward algorithm that linearly converges and gets stuck in these weird minimums.</p> <p>I want to below give a short overview of some work that I have done last week. Unfortunately, I think that this was somewhat a red herring and in the next post, I will describe some of my current ideas.</p> <p>I wanted to see if I can specify the wavefront that I need to achieve to explain the observed data by changing individual pixels in the wavefront. So instead of modifying a relatively small set of Zernike parameters, I was modifying a large number of individual pixels in the wavefront. In this context, I have split my wavefront into 51x51 pixels. I would move the wavefront by a small amount in each of those pixels and record the change that this causes in the model image. After that, I looked at the linear combination of these movements that would minimize the residual from the input science image. For instance, one example of the prediction of this improvement is shown in ``Linear_prediction_of_change_to_model.png''. ``Wavefront_pixel_change'' shows the change to the wavefront that I have applied in order to predict the improved residual.</p> <p>``Actual_change'' shows the result of this change to the wavefront. As we can see, the change is very different than what is expected from our nice prediction. </p> <p>I also tried to directly fit this proposed wavefront with Zernike polynomials in order to get a smooth solution to the problem. This is shown in ``Zernike_interpolation_to_wavefront''. The results are again unsatisfactory (Actual_change_after_Zernike_wavefront_aprox).</p> <p>At the moment I think the problem is that I am fitting wavefront parameters and pupil parameters separately. So, I first propose a change to the wavefront, and then I move pupil parameters. What happens here is that A) the initial guess for the pupil parameters is a little bit off (as one can see from the struts and detector edges being visible in the residuals) b) I propose a change to wavefront parameters which try really hard to compensate these differences from struts and detector c) when I try to fit pupil parameters they fail to reach correct solutions because wavefront parameters have been stretched so hard to compensate.</p> <p>Obviously, these need to fit together. I am have avoided that so far because changes in the pupil illumination parameters do not have such nice linear properties as wavefront parameters (i.e., changing the amplitude of a Zernike parameters changes the amplitude of flux in the final image at the same spots in a linear fashion, as long the change is small). Moving detector to the left or right does not have the same property.</p> <p>I think the solution is to determine which parts of the donut are obscured when moving pupil parameters (e.g., moving detector), so I can have a shortcut to determine what changing those parameters will have on the final image, without having to regenerate the whole image each and every time when I move the detector in the fitting procedure.</p> <p> </p> <p>summarized in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-614" title="Illumination estimate of the pupil should be constant across different defocuses for single spot" class="issue-link" data-issue-key="PIPE2D-614"><del>PIPE2D-614</del></a>.</p> Blocks PIPE2D-614 Development Rank 0|02qps2:mi Sprint 2DDRP-2021 A Story Points 6.0