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

Misleading slits device name #529

Closed
keithralphs opened this issue May 14, 2024 · 5 comments · Fixed by #547
Closed

Misleading slits device name #529

keithralphs opened this issue May 14, 2024 · 5 comments · Fixed by #547

Comments

@keithralphs
Copy link
Contributor

f"s{slit_number}_slit_gaps",

From @Tom-Willemsen: Should be called "slits" rather than "slit_gaps".

Tagging @callumforrester @joeshannon

@Tom-Willemsen
Copy link
Contributor

From @Tom-Willemsen: Should be called "slits" rather than "slit_gaps".

Because the device has members for both gaps and centres - so I'd expect something like slits_1 at the user level. Looks weird to talk to s1_slit_gaps.x_centre for example.

@keithralphs
Copy link
Contributor Author

Are you happy with the form s1_slits, s2_slits, etc.?

@callumforrester
Copy link
Contributor

I think slits_1, slits_2 etc. is better as that mirrors the dodal factory function names

@Tom-Willemsen
Copy link
Contributor

I'd prefer it to be the same as the dodal device name - i.e. slits_1 I think.

Wasn't there discussion at some point about having blueapi automatically set the name of the device to the name in the dodal module anyway? Or perhaps I'm misremembering. If that's the case, then it would definitely be misleading to have different names depending on whether we're running in blueapi or not...

@callumforrester
Copy link
Contributor

@Tom-Willemsen there have been a few discussions around that, would be ideal if dodal set the name to the function name so you don't have to supply it all, that would save a lot of boilerplate. Might come out in the wash as part of the tickets coming out of #415

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

Successfully merging a pull request may close this issue.

3 participants