[PIPE2D-680] Add a config to change the order of merging and 1-D sky subtraction Created: 10/Dec/20  Updated: 20/Jan/21  Resolved: 11/Dec/20

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

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

Attachments: PNG File PIPE2D-680-new.png     PNG File PIPE2D-680-old.png    
Issue Links:
Relates
relates to PIPE2D-691 Fix sky subtraction for pfsObject Done
Reviewers: price

 Description   

When using all the information optimally, it's probably desirable to model the 1-D sky spectra for an arm (generating a 2-D model and making use of multiple dithered realisations to recover the sampling), subtract the sky, and then merge the 1-D sky spectra across the arms. The sky subtraction should be done pre-merge as the science spectra are not very well samples, and sky subtraction removes a lot of high-frequency power.
However, while we are using a simpler algorithm, merging the arms to create a per-arm sky then interpolating it to the per-fibre wavelength solutions means that we are interpolating the sky twice, and so with e.g. linear interpolation the sky lines have an extra sqrt(1/6) added in quadrature to the line widths. The simplest way to avoid this is to merge all the spectra (including the sky spectra) and then merge the sky spectra, and then subtract.

Please add an option doSubtractSky1dBeforeMerge to control this; for now the default should be False.



 Comments   
Comment by rhl [ 11/Dec/20 ]

See the attachments, sky-subtracted sky fibres before and after .

Comment by rhl [ 11/Dec/20 ]

merged

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