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.

Sign up for GitHub

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

Jump to bottom

write the detector x & y directions to H5 #9

Open
leofang opened this issue Jan 15, 2019 · 2 comments
Open

write the detector x & y directions to H5 #9

leofang opened this issue Jan 15, 2019 · 2 comments

Comments

@leofang
Copy link
Collaborator

leofang commented Jan 15, 2019 •
edited

This is an important info that's missing currently. GUI needs to detect this automatically. Perhaps these were not stored in the databroker? Need to check.

Related: #8
@leofang leofang mentioned this issue Jan 15, 2019
Open
3 tasks
@leofang
Copy link
Collaborator Author

leofang commented Feb 19, 2019

@xiaojinghuang said this info is unfortunately not stored in Databroker as no one understands the legacy control script. As long as the scan setup is not changed (very likely) we can safely write the default values to H5.

@leofang
Copy link
Collaborator Author

leofang commented Jan 30, 2020

Now that CSX joins the game, we need to reconsider this. I say for each beamline we find and write the correct, default values?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@leofang