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

Prevent truncation of EPICS PVs #15

Open
GDYendell opened this issue Oct 25, 2023 · 2 comments
Open

Prevent truncation of EPICS PVs #15

GDYendell opened this issue Oct 25, 2023 · 2 comments

Comments

@GDYendell
Copy link
Contributor

GDYendell commented Oct 25, 2023

It is easy when generating Attributes programmatically for the generated PVs to be too long and get truncated. I think the limit is 60 characters.

It would be good to define some logic to truncate the names in a sane way, ensuring the _RBV is preserved. This could be by truncating each individual word, removing vowels, or many other options. ADGeniCam does the former.

It might also show a warning to suggest to the developer that the name should be shortened in a way specific to the naming structure for the device.

@GDYendell
Copy link
Contributor Author

@marcelldls do you know if there is a similar limit in Tango? I imagine if there is is it a much bigger number.

@marcelldls
Copy link
Contributor

A tango attribute has a full name with the following schema: domain/family/member/attribute and according to https://tango-controls.readthedocs.io/en/latest/development/general-guidelines/naming.html the limits are 85/85/85/??. An alias can be defined to a maximum of 255 characters... I cant find specifically what the maximum attribute length is but I can ask in the Tango controls slack when I get added

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

No branches or pull requests

2 participants