-
Notifications
You must be signed in to change notification settings - Fork 4
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
Wavelength limits of throughput and resolution #7
Comments
@dkirkby, I'm assigning this to you so that you can assign it to someone who can actually resolve this. |
The difference between psf-quicksim and thru*.fits comes from the difference between what wavelengths all fibers see vs. the min/max that any fiber might see. psf-quicksim uses the range for fiber 100 which is a "typical" case in between. Quoting from a June 29, 2014 "Big desimodel update" email:
i.e. the throughput files cover what might happen for some fiber, while the psf-quicksim file covers a typical range that should be used for the quick simulations, even though some fibers will see higher/lower wavelengths. This has come up multiple times so better documentation could be in order, but I don't think it requires any code or data file changes. |
OK, so where exactly should the documentation go? In the data model for desimodel perhaps? Or in desimodel's own documentation? |
There is some explanation now in the DESI config file used by specsim:
|
If this documentation is sufficient, I propose we close this. |
Ok with me. |
Closing. |
The files
data/specpsf/psf-quicksim.fits
anddata/throughput/thru-*.fits
have different wavelength coverage:Questions:
This is relevant to getting the edge effects right in specsim (desihub/specsim#17 and desihub/specsim#18).
The text was updated successfully, but these errors were encountered: