-
Notifications
You must be signed in to change notification settings - Fork 13
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
Missing emission lines in galaxy templates #111
Comments
Here are some high SNR examples:
|
But more generally: these templates will never be as good as empirical templates that we build from the data themselves. My vision has always been that we will generate a pre-survey template set from SV observations, and that we'll periodically update our templates over the course of the survey as we probe more of galaxy/QSO parameter space. I'm sure other opinions abound, but this is a larger discussion that I would welcome. |
@moustakas would it make sense to build them from eBOSS data? What are those empirical models like? PCA or something else? |
I think eBOSS would be a great. I hadn't previously pursued using eBOSS spectra because the requisite data weren't public, but I'm sure the public samples are large enough now. I'm not a fan of PCA because stars are never negative. Non-negative matrix factorization or archetype methods (see, e.g., this notebook) would be preferable. The approach I've used for the current set of (galaxy) templates is to model the available data (spectra + broadband photometry, e.g., from DEEP2 for ELGs) using stellar population synthesis models for the continuum + Gaussian emission-line fitting. This model-based but empirically constrained approach yields spectral templates with the necessary spectral resolution and wavelength coverage for DESI. Archetypes or basis spectra can then be generated from this empirically constrained parent template set, as in redrock. But there are many other subtle issues to consider, like differences in the wavelengths of the near-UV absorption lines due to outflows / winds vs the nebular emission lines, which will show up as systematic redshift errors. However, I'm sure many of these issues have been worked on in eBOSS. My point is that I think we need to gradually move away from the templates I built which we've been using the past N years and get ready to use "real", DESI-like data. |
@moustakas, do you need only the wavelength or also the distribution of the strength of these lines? I agree that at least we have to compare the templates with desi-like data (=eBOSS). |
At minimum the wavelengths of the lines. In principle we can tune the relative strengths but I'd be surprised if this affected the redshift results in a measurable way. But I've been known to be wrong... |
@moustakas, do you need the wavelength in vacuum or in the air? In vacuum I suppose. |
Either, but vacuum is probably easiest. |
In the same rest frame as the desisim galaxies: Should not exist: |
(This issue should really be posted as a I never quite finished documenting how I incorporate emission lines into the ELG AND BGS templates, but here are some notes:
In case we want to add even more forbidden lines (about which I welcome your thoughts, @londumas), we could use galev_emlines.txt, which I obtained from R. Kotulla a few years ago, although some/many/most of the line-ratios are really only suitable for low-mass, low-metallicity starbursts. Alternatively, Let me know how you'd like to proceed. |
This is fixed thanks to @moustakas: desihub/desisim#426 and desihub/desisim#424
Here is what we use to have and what we get for one spectrum: |
Thanks for the multi-repo fix. Closing this ticket. |
Looking at the residuals of galaxy in DR7, DR12 and DR14 we can see that some lines are missing in the redrock galaxy templates, created from desisim galaxies. The following plots show these different lines for the three data sets. The last plot shows a line observed in the templates but not observed in the data.
The wavelength are by eye: 9533, 9071, 7137, 6301, 2496 A
DR7
BOSS
DR14
The text was updated successfully, but these errors were encountered: