[PIPE2D-996] Add missing lines to sky line list Created: 03/Mar/22  Updated: 06/Apr/22  Resolved: 06/Apr/22

Status: Won't Fix
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: hassan Assignee: hassan
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2022-03-23 at 8.00.24 PM.png    
Issue Links:
Relates
relates to PIPE2D-1017 Revise sky line list Done
Story Points: 2
Reviewers: price

 Description   

As identified in PIPE2D-884 and during internal discussions 2022-02-28, there are a number of missing lines in skyLines.txt .

Please go through the literature and add those.

Restricting this ticket to providing a complete list of lines from two contiguous orders of Osterbrock (1996) (https://articles.adsabs.harvard.edu/pdf/1996PASP..108..277O), as requested following Princeton internal meeting 2022-03-21.

Additional lines will be added, but as part of separate tickets.



 Comments   
Comment by hassan [ 24/Mar/22 ]

Contiguous orders from Osterbrock (1996) chosen are 44 and 45 (782-819 nm). Please see attached , which shows a 2D-sky subtracted image of a recent SuNSS exposure. Blue crosses are lines identified in updated sky linelist in branch. Lines look pretty complete in this wavelength range.

Comment by price [ 24/Mar/22 ]

It looks like this is the same list, with different intensity values, and undoing the previous efforts to merge band-head close doublets. I don't think this is a particularly problematic wavelength region in terms of missing lines. We had more trouble at redder wavelengths.

We need to discuss:

Do we want the band-head close doublets individually or merged?
Do we want some lines in the list to have a different normalisation of intensity values?

Comment by hassan [ 06/Apr/22 ]

Following discussions within the Princeton Group, this work is discontinued. Replaced by PIPE2D-1017

Generated at Sat Feb 10 16:00:58 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.