-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HIRES wavelengths and a bit more #1628
Changes from 42 commits
cb52d46
f074e6d
3001b80
25a3d36
9761588
e039188
58871ca
01c8702
e738f91
85bc73b
73a91fa
9ef5fa0
bd38ce1
db75b59
8a82176
69e32e7
e9ebbf9
7463cdd
d8e314f
e1327b1
71f2cb3
ba74766
5c2ae30
97627dd
d50b53d
35c3d3a
0939c93
c11a0b5
a3fd75f
569a736
336f3a3
c8479ad
969a930
3d40489
2db1699
1e513ef
74cd1a0
f8a0ff8
bdc4296
ea55d54
3198a88
c1eb574
f3fcde3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
========== | ||
Keck HIRES | ||
========== | ||
|
||
Overview | ||
======== | ||
|
||
This file summarizes several instrument specific settings that are related to the Keck/HIRES spectrograph. | ||
|
||
|
||
Wavelengths | ||
=========== | ||
|
||
See :ref:`wvcalib-echelle` for details on the wavelength calibration. | ||
|
||
We also note that several Orders from 40-45 are | ||
frequently flagged as bad in the wavelength solution. | ||
This is due, in part, to very bright ThAr line contamination. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,3 +10,51 @@ This file summarizes several instrument specific | |
settings that are related to the VLT/XShooter spectrograph. | ||
|
||
|
||
Wavelengths | ||
=========== | ||
|
||
As it is common for ESO to obtain calibrations with different | ||
slit widths and binning, this can lead to various challenges | ||
for PypeIt. | ||
|
||
As regards wavelengths, the varying binning and slit widths lead | ||
to differing FWHM of the arc lines. And because the RMS threshold | ||
for a good solution is scaled to FWHM, the default is to measure | ||
the FWHM from the lines themselves. | ||
|
||
If too many orders are being rejected, you may wish to adjust things | ||
in one or more ways. | ||
|
||
FWHM | ||
---- | ||
|
||
For the UVB or the VIS, you may turn off measuring the FWHM (in units | ||
of binned pixdels) from the arc lines | ||
by adding this to your :doc:`pypeit_file`: | ||
|
||
|
||
.. code-block:: ini | ||
|
||
[calibrations] | ||
[[wavelengths]] | ||
fwhm_fromlines = False | ||
|
||
This will set the FWHM to the default value for UVB/VIS which | ||
may yield a better set of discovered arc lines. | ||
|
||
RMS | ||
--- | ||
|
||
Another option is to increase the RMS threshold for a good solution. | ||
This may be done in the :doc:`pypeit_file` as well: | ||
|
||
.. code-block:: ini | ||
|
||
[calibrations] | ||
[[wavelengths]] | ||
rms_threshold = 1.5 | ||
|
||
|
||
Note that this is scaled by the ratio of the measured FWHM value | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "Note that the rms_threshold is unit of the measured FWHM value, in other words, if the FWHM = 3 pixels, then the rms_threshold would be 4.5 pixels in this case." What I've written above is my understanding of what you have implemented, but it also cannot be correct. But your new definition of rms_threshold is unclear to me. Can you please be as explicit as possible in the docs. What are the units of rms_threshold, what are the units of fwhm, write out the equation that determines the actual final rms threshold in pixels or whatever that we use for determining whether fits are good. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes, this is a bit confusing. I've expanded the discussion on this in |
||
to the default value. See :ref:`_wvcalib-echelle` for | ||
further details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My suggestion is that we instead define:
rms_pixels = rms_threshold*FWHM
Where FWHM is either the default FWHM or the measured FWHM, i.e. it will be the latter when the automatic FWHM determination is turned on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is what we are trying to handle:
rms_threshold
(pixels) corresponding to a defaultfwhm
(pixels) which we tune from the DevSuite. Both of these depend on slit width and binningrms_threshold
by the measured fwhm. This works relatively well but is not perfect. Nothing ever is for wavelengths.. This is what is currently implemented in the code and described in the docs.The
fwhm_fromlines
parameter only refers to whether to use the measured_fwhm when finding arclines.It doesn't play a role
rms_threshold
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add an issue to updated the docs and spectrograph files to the convention that we discussed, i.e using rms_threshold_frac_fwhm. That need not be done for this PR, but clearly should be done asap.