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

PREOPS-3752: Add survey fields and telescope pointing to map. #38

Merged
merged 1 commit into from
Oct 15, 2023

Conversation

alserene
Copy link
Collaborator

  • Pass newly added conditions and survey parameters to schedview.plot.survey.map_survey_healpix()

  • Update Bokeh plot of key to match colour and alpha values of plot objects.

- Pass newly added conditions and survey parameters to
  schedview.plot.survey.map_survey_healpix()

- Update Bokeh plot of key to match colour and alpha values of plot
  objects.
@codecov
Copy link

codecov bot commented Oct 13, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (6fe190b) 12.41% compared to head (abfe5e5) 12.41%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #38   +/-   ##
=======================================
  Coverage   12.41%   12.41%           
=======================================
  Files          39       39           
  Lines        3078     3078           
  Branches      466      466           
=======================================
  Hits          382      382           
  Misses       2687     2687           
  Partials        9        9           
Files Coverage Δ
...iew/app/scheduler_dashboard/scheduler_dashboard.py 0.00% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@ehneilsen ehneilsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Eventually (but not needed for this issue) we may want to change how the legend is made so that the colors etc. are automatically kept the same, and we do not rely on hard-coding the values in two separate places. I can think of several different approaches:

  1. Use the legend-creating tools built into bokeh
  2. Leave the legend creation separate (as it is), but have the colors etc. read from a common location.
  3. Leave the legend creation separate, but instead of hard-coding the colors there, query the bokeh plot object for the colors used.

As a general rule, whenever two values are hard-coded separately but need to be the same, it makes maintaining the code long term harder.

@alserene
Copy link
Collaborator Author

Looks good!

Eventually (but not needed for this issue) we may want to change how the legend is made so that the colors etc. are automatically kept the same, and we do not rely on hard-coding the values in two separate places. I can think of several different approaches:

  1. Use the legend-creating tools built into bokeh
  2. Leave the legend creation separate (as it is), but have the colors etc. read from a common location.
  3. Leave the legend creation separate, but instead of hard-coding the colors there, query the bokeh plot object for the colors used.

As a general rule, whenever two values are hard-coded separately but need to be the same, it makes maintaining the code long term harder.

I agree that this is something we should do 👍 I'll have a think on the options.

@alserene alserene merged commit 3890707 into main Oct 15, 2023
6 checks passed
@alserene alserene deleted the tickets/PREOPS-3752 branch October 15, 2023 04:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants