Merged
Conversation
Collaborator
Author
|
I'm open to suggestions for changing the variable name |
b616f2e to
bd66ab7
Compare
YektaY
approved these changes
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
I encountered a problem where the Data Insight Tool was showing live data even if the plot's time range only included archived data. This could present a problem if someone wants to only export archived data. I noticed that the model was also never getting reset if the Live data was not within the plot's time range.
My solution is to move the model reset outside of the
get_live_datafunction call. This should have been the route from the beginning.Additionally, I moved the call for
DataInsightTool.blockSignals(False)inDataInsightTool.update_pv_select_box()until after the new PVs are added to the combobox. This was occasionally causing many sequential calls toDataInsightTool.get_data()and resulted in a warning message being spit out multiple time:[WARNING ] - Data Insight Tool: No data received from archiverBy blocking the signals for longer, I inadvertently prevented the call to
get_datawhen curves are added for the first time. My solution here was to add anunopenedflag to make a manual call toget_datawhen the DIT is opened for the first time (only if there is at least one curve to get data for).Motivation
Encountered a problem when showing trace to a potential user. Decided that it was a bad look and should be fixed ASAP.
Screenshots
Problem Example
In this picture I set the plot's time range to 10am - 12pm (noon). After refreshing the data in the DIT we would expect it to only show data within that range. Instead we see data after 12pm, including live data at the bottom of the table.

Pre-merge checklist