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-521 DRP 2-D Pipeline <p>This is to create the 2d PSF solution for the July data, using the improvements from 2020:</p> <ol> <li>Proper bilinear interpolation (mentioned in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-408" title="More than bilinear centering of the model for PSF 2d modeling" class="issue-link" data-issue-key="PIPE2D-408"><del>PIPE2D-408</del></a>)<br/> 2. Consistent pupil sizes (<a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-516" title="Different results from different size images with same physical parameters" class="issue-link" data-issue-key="PIPE2D-516"><del>PIPE2D-516</del></a>)<br/> 3. Analysis of 2 sources in the image (<a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-420" title="Modify donut code so that it can handle overlapping donuts" class="issue-link" data-issue-key="PIPE2D-420"><del>PIPE2D-420</del></a>)</li> </ol> <p>I have created 3 ``subtickets'', in an effort to granulate the problem and make it easier to track different steps towards the final goal. </p> <p> </p> PIPE2D-521

Create global PSF solutions for the July 2019, using 2020 improvments

Task Normal Done Done ncaplar ncaplar Thu, 12 Mar 2020 14:41:19 +0000 Tue, 28 Apr 2020 21:24:50 +0000 Wed, 22 Apr 2020 16:05:57 +0000 0 1 <p>I hope that I am close to creating the first version of the solution. I am adding Figure ``Overview.png'' which shows that is the minimal value of predicted LSF across the detector (as a function of fiber and y-value on the detector). As you can see there is not a single position where the LSF is negative. At the moment I am studying the strange cluster of the high value at y=650. When I solve this, I think this can be the first version of new solutions. </p> <p>I am almost certain that the problem is that I have been extra stupid when doing extrapolation...</p> <p> </p> <p>I have added  ``Overview_interpolation.png'' which shows that is the minimal value of predicted LSF across the detector (as a function of fiber and y-value on the detector). This new figure is created with the new interpolation schema that I am proposing.</p> <p>Beforehand the algorithm was searching for two nearest points to either interpolate or extrapolate the solution. </p> <p>The new schema searching for two spots which straddle the position that you are asking for, i.e., it always does the interpolation. If you are asking for a position that is outside the last available spot (at the edges of the wavelength coverage) the algorithm at the moment returns the last available spot, without any extrapolation. Therefore the solutions at the edges will be deficient in this type of algorithm. Covere_space.png shows the part of the space where we interpolate (dark blue) and where we do not interpolate (yellow).</p> <p>Solutions are placed in `/tigress/ncaplar/<a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-521" title="Create global PSF solutions for the July 2019, using 2020 improvments" class="issue-link" data-issue-key="PIPE2D-521"><del>PIPE2D-521</del></a>`. The description is the same as in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-450" title="Create array_of_arrays that contains 2d PSF model inputs" class="issue-link" data-issue-key="PIPE2D-450"><del>PIPE2D-450</del></a>. </p> <p>positions_of_simulation_00 array contains positions of each PSF model. The columns are: 1. fiberId, 2. approximate x coordinate, 3. approximate y coordinate, 4. wavelength.</p> <p>array_of_simulation_00 array contains arrays with 189x189 PSF models (9x times oversampled).</p> <p>At the moment there are *_Apr15_v1 and *_Apr_v2 versions.</p> <p>*_Apr15_v1 version is created with the lines as they appear on the detector, i.e., the with broad HgAr lines identified in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-439" title="Is HgAr and Neon PSF really different?!" class="issue-link" data-issue-key="PIPE2D-439"><del>PIPE2D-439</del></a>.</p> <p>*_Apr15_v2 version is created by artificially narrowing these lines, i.e, how I believe they should appear if they were not broadened due to atomic issues. This narrowing is done quite crudely at the moment, I just set the argument controlling the Lorentzian width component so that is roughly similar to the other nearby lines. This needs to be improved. </p> <p>These PSFs are valid for F/2.8 data taken in July 2019 (e.g.,  runs 21400, 21604 and 21808.)</p> <p>The updated method is available at <a href="https://github.com/Subaru-PFS/dev_2ddrp/blob/master/2d_PSF_code/PIPE2D-521/Provide_PSF_2D.py" class="external-link" rel="nofollow">https://github.com/Subaru-PFS/dev_2ddrp/blob/master/2d_PSF_code/PIPE2D-521/Provide_PSF_2D.py</a></p> <p>I have added *_Apr15_v3 solutions. The v3 version includes the artificial narrowing of the Hg lines, identified in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-564" title="Investigate discontinuity in some of the April 2020 PSF solutions" class="issue-link" data-issue-key="PIPE2D-564"><del>PIPE2D-564</del></a>. </p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=price" class="user-hover" rel="price">price</a> identified that the new implementation did not handle the case when the requested spot is at the exact position of the input spot correctly. This has been rectified and pushed to <a href="https://github.com/Subaru-PFS/dev_2ddrp/blob/master/2d_PSF_code/PIPE2D-521/Provide_PSF_2D.py" class="external-link" rel="nofollow">https://github.com/Subaru-PFS/dev_2ddrp/blob/master/2d_PSF_code/PIPE2D-521/Provide_PSF_2D.py</a>. </p> Blocks PIPE2D-568 PIPE2D-550 PIPE2D-551 PIPE2D-561 Relates PIPE2D-552 PIPE2D-450 Development Rank 0|zzs0uw: Reviewers price Story Points 20.0