[PIPE2D-1252] LSF is broader than the observation Created: 11/Jul/23  Updated: 03/Oct/23  Resolved: 03/Oct/23

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

Type: Task Priority: Normal
Reporter: Masayuki Tanaka Assignee: sogo.mineo
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-07-27-20-03-26-096.png     PNG File image-2023-07-27-20-03-53-460.png     PNG File image-2023-07-27-20-04-19-383.png     PNG File image-2023-07-27-20-04-32-385.png     PNG File image-2023-07-27-20-04-44-940.png     PNG File image-2023-07-27-20-04-54-874.png     PNG File image-2023-07-28-06-51-33-920.png     PNG File image-2023-07-28-06-51-48-907.png     PNG File image-2023-07-28-06-52-14-503.png     PNG File image-2023-07-28-06-52-26-854.png     PNG File image.png     PNG File pfsMergedLsfCorrected.png     PNG File pfsMergedLsf.png    
Issue Links:
Relates
relates to PIPE2D-1239 Robustify radial velocity measurements In Progress
Reviewers: price

 Description   

As reported in PIPE2D-1239, the LSF-convolved model templates do not resolve the NaD doublet, while the lines are resolved in real data. Check the observed LSF using arcs.



 Comments   
Comment by sogo.mineo [ 24/Jul/23 ]

Tanaka-san found that LSF's widths becomes better when he divides the widths by 2.354. The black lines in the image below are pfsMergedLsf:

The black lines in the image below are pfsMergedLsf, whose widths are divided by 2.354:

The origin of pfsMergedLsf can be traced back to reducedExposure.py's config (gaussianLsfWidth). The values in this list are FWHM. They are input to GaussianLsf's constructor without being converted to standard deviations.

Comment by sogo.mineo [ 24/Jul/23 ]

Could you review this PR?

Comment by Masayuki Tanaka [ 27/Jul/23 ]

I made Gaussian fits to multiple arc lines. See figs here. Although they can/should be cleaned up a bit, the running median shown as the red points suggest that the line width is roughly constant. The horizontal line is the global median after excluding bad fits (e.g., poitns at sigma=0.1, which is the initial guess). r3 and m3 look bad because these are from the Apr 2023 data.

Comment by Masayuki Tanaka [ 28/Jul/23 ]

The spectral resolution is dependent on fiberId. The dependency is different for different arms/grating, and the p-p variation is about 0.005-0.01nm. We need to account for this, but for now, I propose to adopt a constant LSF with sigma=0.081nm for b, 0.109nm for r, and 0.059nm for m. I will look at the n-arm and update this ticket.

Comment by Masayuki Tanaka [ 28/Jul/23 ]

There is no science arc for the n-arm in Run 11. There are some data in Run12 and I made an attempt to reduce them, but I am missing most of the lines at lambda>1000nm. I am not sure why, but I think I will wait for new calibs from this run and come back later.

Comment by Masayuki Tanaka [ 31/Jul/23 ]

I propose that we go with a specification resolution listed at https://pfs.ipmu.jp/research/performance.html for the n-arm for now, i.e., sigma=0.109 nm. I will measure the resolution once we have better calibs from the July 2023 run and file a separate ticket to update the number.

Comment by sogo.mineo [ 31/Jul/23 ]

I revised the numbers in the ticket branch.

Comment by sogo.mineo [ 03/Oct/23 ]

Merged. Thanks for reviewing.

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