-
Notifications
You must be signed in to change notification settings - Fork 41
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
Improve bad pixel monitor plots #1202
Improve bad pixel monitor plots #1202
Conversation
In order for this to work on the servers, we'll need to install the packages described in #1200. This is done on the test server and I didn't see any problems. |
@mfixstsci this is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for submitting this @bhilbert4 just a couple of comments here.
@bhilbert4 thanks for the responses, I am going to wait for the branch to rebase and then will merge the changes. |
Remove bokeh templating from the bad pixel monitor plots, and make some tweaks to make them more useful and faster to load.
I'm trying to make these a little more interactive than the plots from the dark monitor. In this case, the figure/plot creation will be called as the final step of the bad pixel monitor itself (or it can be called separately at any time). The output will be a separate html file for each instrument. Then when a user requests the bad pixel monitor page, it simply loads the html file.
Bokeh creates and saves the html file itself. There is then a bit of editing to place the relevant lines from that file into our jinja template. The bokeh lines can end up being quite long since they contain all of the plotted points and hover tools. So we sacrifice some speed there compared to the dark monitor plots, which are simply png files that are loaded and displayed. But in return for that we get more interesting/useful plots.