[PIPE2D-564] Investigate discontinuity in some of the April 2020 PSF solutions Created: 23/Apr/20  Updated: 05/Jan/21  Resolved: 12/May/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 Broad HgAr lines.png     PNG File HgI lines in red.png    
Issue Links:
Relates
relates to PIPE2D-582 Are broad lines in Hg from the same o... Won't Fix
Story Points: 2
Sprint: 2DDRP-2021 A

 Description   

When doing preliminary analysis of the solution in PIPE2D-521 I noticed that some nearby lines have quite different solutions in the wings. For example, this can be seen for fibers 339 and 401 around the y-position of 400. Investigate what is the cause of this effect. 



 Comments   
Comment by ncaplar [ 23/Apr/20 ]

The reason why there is some discontinuity is that there are more broad lines. Out of 4 HgI lines in the red, I have identified two HgAr lines, at 690 and 708 are obviously broader then nearby Neon lines. The flux for other lines is too low to make firm conclusions.

 

I have been using the line at 690 in my solutions. I will have to artificially narrow that line (as in PIPE2D-561). I will close this ticket when I have done so.

 

Comment by ncaplar [ 28/Apr/20 ]

Talked with Jim this morning (Mon, April 27, 2020). Jim suggests:

 

  1. Checking if this is allowed transition to the ground state i.e., if this is the same effect as seen in Argon lines. To do this, calculate the energy of the transition from NIST line list, transform to wavelength, and then compare with a list of known transition lines from the ``literature''.
  2. Compare the widths of Hg lines in the blue and see if only some lines exhibit this new broadening. 
Comment by ncaplar [ 12/May/20 ]

I will close this ticket and put the suggestion by Jim in new tickets for future work. 

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