Skip to content
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

fix gray time definition code #13

Closed
sbailey opened this issue Dec 19, 2016 · 2 comments · Fixed by #14
Closed

fix gray time definition code #13

sbailey opened this issue Dec 19, 2016 · 2 comments · Fixed by #14
Assignees
Labels

Comments

@sbailey
Copy link
Contributor

sbailey commented Dec 19, 2016

There is a bug in the implementation of the definition of gray time. Below is a plot of moon altitude vs. moon illumination fraction from a surveysim run for dark (blue) bright (red) and gray (black) observations. The upper panel is the assignments from obslist_all.fits; bottom panel is what they should be based upon the DESI-0311 site alteratives definition:

  • dark = moon down
  • gray = moon up and illum<0.6 and illum*alt < 30 deg
  • bright = everything else

Note: there are no illum>0.85 points on these plots because of the 1 week engineering/other downtime around full moon.

graydefn

I haven't tracked down if this definition code is in desisurvey or desisim, but I'm filing the ticket against desisurvey since that is where it should be :)

Guess: a radians vs. degrees bug.

@sbailey sbailey added the bug label Dec 19, 2016
@sbailey
Copy link
Contributor Author

sbailey commented Dec 20, 2016

Update: the current code uses the alternate gray time definition from DESI-0333 of illum<0.2 or illum*alt<12 deg. It also allows gray tiles to be observed during dark time if all dark tiles for that LST have already been completed, which is reasonable. i.e. I'm not sure if there actually is a bug here, or if it is just using a different gray time definition (we should switch to baseline definition anyway).

@mlandriau
Copy link
Contributor

mlandriau commented Dec 20, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants