[solved] Classes catalogue: categories

# 2 years ago
philippeg	Hi tangoers, I noticed the presence of https://www.tango-controls.org/developers/dsc/families/?family=Motion and https://www.tango-controls.org/developers/dsc/families/?family=Motors Is there a reason to have 2 distinct categories? Regards. - Philippe Edited 2 years ago

# 2 years ago
Reynald	Hi Philippe, I guess it is because the 2 device servers on the Motors Family are written in Python HL and were not generated with Pogo which tends to help standardizing the common families (but each site can customize its own set of families in POGO anyway). These 2 devices servers were added manually to the class catalog (no xmi file) so the class family was entered manually and was not deduced from the xmi file generated by Pogo. It seems that in this use case, you don't have a combo box on the web interface with predefined families. You need to enter the family manually directly. So when you don't have much ideas about the existing class families, you might end up creating a new family easily. See this page and then click on Manual checkbox, you will see that the "Class family" field is a simple text field whereas the "Additional families" field is a more advanced field where you can see the already existing families. Maybe it's something that could be improved on the device classes catalog import interface. Feel free to create an issue on https://gitlab.com/tango-controls/dsc to report this problem on the dsc project (Device Server Catalog which got renamed Device Classes Catalog): https://gitlab.com/tango-controls/dsc Kind regards, Reynald Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 2 years ago

Reynald

Hi Philippe,

I guess it is because the 2 device servers on the Motors Family are written in Python HL and were not generated with Pogo which tends to help standardizing the common families (but each site can customize its own set of families in POGO anyway).
These 2 devices servers were added manually to the class catalog (no xmi file) so the class family was entered manually and was not deduced from the xmi file generated by Pogo. It seems that in this use case, you don't have a combo box on the web interface with predefined families. You need to enter the family manually directly. So when you don't have much ideas about the existing class families, you might end up creating a new family easily.

See this page and then click on Manual checkbox, you will see that the "Class family" field is a simple text field whereas the "Additional families" field is a more advanced field where you can see the already existing families.
Maybe it's something that could be improved on the device classes catalog import interface.

Feel free to create an issue on https://gitlab.com/tango-controls/dsc to report this problem on the dsc project (Device Server Catalog which got renamed Device Classes Catalog): https://gitlab.com/tango-controls/dsc

Kind regards,
Reynald

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 2 years ago
philippeg	Thank you Reynald, I created a dedicated issue. - Philippe