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

Status record #67

Open
lstebel opened this issue Jan 29, 2018 · 12 comments · Fixed by #69
Open

Status record #67

lstebel opened this issue Jan 29, 2018 · 12 comments · Fixed by #69
Assignees

Comments

@lstebel
Copy link
Collaborator

lstebel commented Jan 29, 2018

Import and "live" display status information.
Most importantly, the information should be available internally, for present and future sw developers.
Refer to my email dated Dec 18, 2017

@ajgdls
Copy link
Contributor

ajgdls commented Feb 1, 2018

When I read the registers on my system all return 0xFFFFFF is this expected currently? Also, do you expect to see all of these values in the GUI somewhere? If so this might require a new tab as there are so many items. @lstebel let me know what you think.

@lstebel
Copy link
Collaborator Author

lstebel commented Feb 2, 2018

No Alan, that is not expected. In particular, if you run a powerup and start an acquisition, then there should be several things that toggle (e.g. image number and status flags).
It would be useful to display status record in a pretty compact way, so that this could be kept in a certain area of the display. I don't know if it's better to have a new tab or a popup window. See what I did in LabVIEW.
status_monitoring

@lstebel
Copy link
Collaborator Author

lstebel commented Feb 2, 2018

When I read the registers on my system all return 0xFFFFFF is this expected currently?

I confirm that you must be doing something wrong. After FPGA configuration you should already be able to read this:
status_at_startup
There could be just small differences due to jumper settings or presence/absence of mezzanine board.

@lstebel
Copy link
Collaborator Author

lstebel commented Mar 19, 2018

Were you able to see this, in the end?
Also, I do expect to see all status values in the GUI somewhere. Could you provide this feature?

@ajgdls
Copy link
Contributor

ajgdls commented Mar 19, 2018

Hi Luigi, yes I did see this information and the values looked correct. I still need to add the display for this.

@ajgdls
Copy link
Contributor

ajgdls commented Apr 13, 2018

percival_status
Here is the status tab now present on the web based GUI.

@ajgdls
Copy link
Contributor

ajgdls commented Apr 13, 2018

@lstebel this is now ready for testing.

@lstebel
Copy link
Collaborator Author

lstebel commented Apr 24, 2018

@ajgdls
The webpage does what it is supposed to do, but it is not up-to-date.
In fact, the content of status register was recently modified: see documentation on Confluence (I will send it to you by email, too)

In principle I have learned how to make a part of the required changes in the Python code, but it's probably easier/faster/safer if you could care about that. Please update the web page, too.

@lstebel
Copy link
Collaborator Author

lstebel commented Apr 26, 2018

@ajgdls
I fixed the LSB/MSB inversion in train_number and I did part of the required changes. Still something needs to be done in order to have the webpage display the new set of settings. Please update the web page.

@ajgdls
Copy link
Contributor

ajgdls commented Apr 26, 2018

Hi @lstebel , sure thanks for making the updates I will try to update the GUI this afternoon or else Monday morning.

@ajgdls
Copy link
Contributor

ajgdls commented Apr 30, 2018

This has not been forgotten but I have been tied up with another urgent issue today...

ajgdls added a commit that referenced this issue May 1, 2018
Updated GUI to display new detector status items (issue #67).
@ajgdls
Copy link
Contributor

ajgdls commented May 1, 2018

@lstebel I have made updates to the GUI in line with the changes that you committed, please take a look.

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

Successfully merging a pull request may close this issue.

2 participants