-
Notifications
You must be signed in to change notification settings - Fork 16
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
Contents of the output files #19
Comments
Telluric correction (divide-a0v) in the pipeline is unfortunately very primitive. And I do not recommend to use it directly if telluric correction is critical for your science. The output is simply the target spectra divided by a nearby A0V (corrected by Vega model). It does not even try to match different wavelength solutions of target and A0V. And a simple Vega model is applied without correcting for doppler shift, etc. For your question 1, there is no easy way for now. The information should be available in the header though. I will try to push the relevant changes soon. The wanvelength solution of the target can be different from that of A0V, so the initial wavelength solution is kept for now (it does not mean that it is correct). I have been planning to fine-tune the wavelength solution of the target using its own telluric lines and/or OH lines, but this has not happened yet. I know there is no proper documentation and some key features (e.g, proper telluric correction) are missing, but progress has been very slow. Any help/contribution will be very much appreciated. |
Thanks for the response.
Could you point me to the relevant keyword? |
I meant that I will put it in the header by changing the code. |
Ah. Great! |
This is now implemented in the new versions. See my comment at the end of following page. https://github.com/igrins/plp/wiki/Plotting-spectra-&-divide-by-A0V |
So I too was confused about what is in the
|
There isn't much documentation on the output of the pipeline and I'm having a little trouble parsing all the files. There also seems to be a lot of the same data in duplicate locations. I've gather that my telluric-corrected spectrum is in a file named something like SDCH_20161112_0026.spec_a0v.fits, with five extensions: telluric-corrected spectrum, wavelength, target spectrum, A0V spectrum, and a Vega spectrum. I'm left with two questions.
How do I figure out which A0V spectrum was used for telluric correction for each target?
Is there a quick way to get the variance of the telluric-corrected spectrum?
The 2nd and 3rd extensions of the .spec_a0v.fits are the same as the 2nd and 1st extensions of the .spec.fits file of the target, respectively. I've figured out that the telluric-corrected spectrum is nearly exactly = target / (A0V / Vega). If I choose the right A0V, I can just do the target/(A0V/Vega) myself and get nearly exactly what is in the .spec_a0v.fits file. So I could just propagate the variances myself, but that requires going through and confirming I am using the right A0V in each case. Knowing which A0V the pipeline used would make this easier and not a big deal.
Furthermore, the wavelengths in the .spec_a0v.fits file are the same as in the .spec.fits file. I would have guessed they would be the same as what is in the .wave.fits file for the A0V star because that has gone through a fine-tuning based on a telluric absorption model, correct?
The text was updated successfully, but these errors were encountered: