[PIPE2D-953] Create high signal-to-noise spectra of calib lamps Created: 01/Dec/21  Updated: 07/Mar/22  Resolved: 11/Feb/22

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: Zip Archive PFI_lines_csv_files_v4.zip     Zip Archive PFI_lines_pkl_files_v4.zip    
Issue Links:
Relates
relates to PIPE2D-998 Create plots of high signal-to-noise ... Done
Story Points: 2
Sprint: 2DDRP-2021 A12, 2DDRP-2022 A
Reviewers: hassan

 Description   

Using the observations taken with PFI in November and September runs, create the highest possible signal-to-noise spectra of all available calib lamps.



 Comments   
Comment by ncaplar [ 03/Feb/22 ]

I have created the spectra for our lamp lines at Subaru. The visit used are:

Krypton - from visits 71155, 71156, 71157
Argon - from visits 71162, 71163, 71164
Xenon - from visits 71159, 71160, 71161
Neon - from visits 68640, 68641, 68642
Hgcd - from visit 67757
Haloen - from visit 68087

I generate the lines by using interpolateFlux (from from pfs.drp.stella.interpolate) to interpolate all fibers from an exposure to the same grid. I then calculate mean out of all of the interpolated fibers, from all of the avaliable exposures. I normalize the flux to 1 second, by dividing the data by the effective exposure time.

I have also created csv files, which I have shared with JEG.

Comment by ncaplar [ 03/Feb/22 ]

Hassan can you please check that you can load pandas files and that they look reasonable?

Comment by price [ 03/Feb/22 ]

What was the quality of the wavelength solutions?

Comment by ncaplar [ 03/Feb/22 ]

Sent to JEG for his comments. Still working with him to understand if he is satisfied with the analysis I did.

price Can you perhaps elaborate? To get spectra I ran reduceExposure, and then interpolateFlux on pfsArm.flux arrays. See November 11, 2021 discussion in zoom chat with me, you and Hassan. I ran reduceExposure because reduceArc does not succeed for all arclines (if there are no lines on r or b detector for that particular arcline), so I wanted to be consistent across all detectors and lines. I have a felling that you would do something much differently?

Comment by price [ 03/Feb/22 ]

Did reduceExposure use the adjustDetectorMap feature? If so, what did it report as the quality of the fit?

Comment by ncaplar [ 03/Feb/22 ]

No, because it fails when there are not enough lines (fails in doAperatureCorrection ) step. Typical command I have used is:

reduceExposure.py /projects/HSC/PFS/Subaru --calib /projects/HSC/PFS/Subaru/CALIB-PFI-20211220/ --rerun ncaplar/PIPE2D-953 --id visit=71155 -j 20 -c isr.doFlat=False doAdjustDetectorMap=False photometerLines.doApertureCorrection=False --clobber-config
Comment by ncaplar [ 04/Feb/22 ]

Paul, I reran with  
doAdjustDetectorMap=True photometerLines.doApertureCorrection=False
and these are summary results at the end of processing. Find results in the gist below. Is that what you had in mind?

https://gist.github.com/nevencaplar/cdf761414ddd7febf42dc541ea49d01a

Comment by price [ 04/Feb/22 ]

That's good, thanks.

Comment by ncaplar [ 04/Feb/22 ]

I am currently waiting for comments by Jim if the format I have provided is acceptable to him. If he does not get back to me I will ask him on Monday meeting. I have also rerun everything with doAdjustDetectorMap=True, and changes are minor. If Jim gives ok, I will upload the final version and close.

Comment by ncaplar [ 09/Feb/22 ]

I have talked with Jim today. He is fine with the format and information contained, he only wants the continuum (halogen) lamp to be added to the mix.

Comment by ncaplar [ 10/Feb/22 ]

Added another version. The difference from last attempt is:

1. Continuum added
2. Pipeline ran with detectorMap being adjusted using lines from each lamp. Makes minimal differences to the actual result.

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