-
Notifications
You must be signed in to change notification settings - Fork 9
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
Validate specsim sky brightness against DES photometry #55
Comments
Here is a plot of sky brightness as predicted by What is shown includes the following cuts:
The model does a good job of predicting sky+moon in the g- and r-bands, although there is a slight offset in the g-band where |
@moustakas Should Bela post this update to the BGS mailing list or what's the best way to follow up and get feedback? |
@moustakas Here is a plot with the axes adjusted. |
Belaa, this is really great to see. I'd like to see histograms of the residuals, measured-model, and perhaps how they vary with transparency cut. Is the offset in the g band understood? -- Shaun |
@ShaunMCole Here are the residuals, which contain all the original cuts (including transparency): And here is a plot that shows how the data varies with transparency (this plot includes cuts on sun and moon altitude, but not transparency): Do you by any chance know the units for transparency? I gathered it to be the percentage of expected light that reaches us, but I may be wrong. The residuals show an offset in both the g- and z-bands. Right now, |
According to my notes from @annis the units of |
Thanks @moustakas. I see you mentioned that in your note earlier. Some of the values for transparency were 99.0 and above so I was a little confused. Were these observations for which the transparency couldn't be determined? I've adjusted the color bars in each band to correspond to values within a percentile range that excludes transparency >=99.0. So points in the plot that are above/below this range are set to the max/min color. |
I think if you plot exposure time (if it's available) vs. transparency that'd help you see if it's bad or good. I think to first order it looks like g has a simple offset, r is mostly OK, but z has large deviations that just aren't captured by the model (i.e. the model matches the best-case scenario mostly well with a modest offset, but the worst case is a whole lot worse). I'm a little surprised the excursions only get to a magnitude though, I've observed on a cloudy moony night and believe it was getting brighter than that at bad times vs good. |
UPDATE: the specsim-predicted surface brightnesses in the plots above are under-estimated because they used a filter curve that includes extinction through an airmass 1.2 atmosphere, but extinction has already been applied to the spectrum being convolved with the filter. This is at least part of the reason for the systematic offset in the g-band comparison. As a rough estimate, this should bring the predictions down by 0.25 (g) 0.12 (r) 0.13 (z). |
Note that the data used here is from DES year-1, not DECaLS as indicated in the plot labels. |
This is a parallel issue to the SDSS-centric #40 (which was originally spun off from #9) focused on using DES photometry (using a file originally provided by @annis) to validate whether the
lunar/sky model currently implemented in
specsim
accurately captures measured variations in sky brightness, especially during non-photometric conditions with the moon up.The datafile can be grabbed here. The file should be self-documenting except note that the column
trans
is in magnitudes. Also there may be more data from subsequent years of DES observations but I haven't corresponded with Jim about this since late-2015.Let's try to post updates and progress on this topic here.
The text was updated successfully, but these errors were encountered: