-
Notifications
You must be signed in to change notification settings - Fork 2
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
GUI: Spectra OPIs in DAE not always connecting #7216
Comments
May be fixed when issue with dae caching too many spectra is resolved |
Check if restarting IOC speeds things up. |
@FreddieAkeroyd will check whether or not a ticket exists for the issue mentioned in his comment above. |
Trying to remove old PVs/spectra looks a bit messy, however though memory can get a bit large it is not the biggest issue. The failing to connect may be due to there being too many slow scan timer loops left running after a scan, so have attempted to improve the performance of this
In addition, i have occasionally seen a pink border arounf a plot so also tried
|
Happy with the changes once I got my head around them, but my server has fallen over at some point so I'm rebuilding in order to check it actually runs. Sadly not going to be ready before review/retro at this point, but pretty much certain it'll go straight to review complete |
Did you rebuild your |
As a user of the IBEX client, I would like to be able to see all spectra plots on the DAE immediately when I open the relevant tab.
POLREF have reported a bug where currently, some or all of the spectra OPIs show as disconnected initially. The workaround they have used is to keep resetting the layout until all plots have successfully connected.
Not sure if this has been observed anywhere else, please comment if you can confirm or deny whether this is a problem on other beamlines
Acceptance Criteria
What is the acceptance criteria?
How to Test
@ThomasLohnert is this easily reproducible (on POLREF)? Otherwise more a test it doesn't make things worse.
caget %MYPVPREFIX%DAE:SPEC:1:1:Y.STAT
andcaget %MYPVPREFIX%DAE:SPEC:1:1:Y.UDF
will not work before PR but will afterwardsvar isisdaePCASDebug 1
in the isisdae IOC console window and it will print a message each time an update timer expires, a spectra pv is updated (scanned), and interest (basically a camonitor) happens to a PV. You should only see expiring timers for items being monitored, a caget on an unmonitored PV will just print a "doscan" message to console. Previously there would have been a lot of unnecessary scans on items that were no longer of "interest", but you would need to back port a few print statements to show this.The text was updated successfully, but these errors were encountered: