RFC 6 - Device Server Catalog

# 7 years ago
Andy	The Device Server Catalogue is a database of device servers which can be searched for existing device servers: http://www.tango-controls.org/resources/dsc/ The new catalog differs from the previous one that it is not only based on device servers stored on a limited set of SVN repositories like on SourceForge or other public repositories. It can be uploaded with metadata for any device server via the xmi file or manually (if the xmi file does not exist) from any public or limited access repository. It has an improved search facility. Planned enhancements include a rating system with users comments to encourage and improve sharing the most useful device servers quickly. Please try it either by uploading your server or searching for existing servers. Add your comments and feature requests to this RFC thread Andy

# 7 years ago

The Device Server Catalogue is a database of device servers which can be searched for existing device servers:

http://www.tango-controls.org/resources/dsc/

The new catalog differs from the previous one that it is not only based on device servers stored on a limited set of SVN repositories like on SourceForge or other public repositories. It can be uploaded with metadata for any device server via the xmi file or manually (if the xmi file does not exist) from any public or limited access repository. It has an improved search facility.

Planned enhancements include a rating system with users comments to encourage and improve sharing the most useful device servers quickly.

Please try it either by uploading your server or searching for existing servers. Add your comments and feature requests to this RFC thread

Andy

# 7 years ago
lorenzo	Looks nice. The search functionality works as expected! A chunk of info that's missing is the programming language; what about adding the programming language as fifth column in the Device Server table… as well as in the class description of each Class? Lorenzo

# 7 years ago
jan.meyer	Wow, this looks great. Already now, without the planed enhancements, it makes it much easier to find existing device servers. Anyway, I found some flaws in the catalogue. Nothing important, but I thought you might be interested in feedback. It seems dynamic attributes and commands are not listed. For some servers it makes it hard to get their functionality. Importing of multi class or inherited servers seems to result in mixed-up or duplicated information in some cases (OxfordCrypstream700, WagoRelay, GalilDMC) In this last case, I know it is me to blame for making the namespace non unique. However, GalilDMCSplit depends on the other, single listed GalilDMCMotor. Thanks for your great work! Jan

# 7 years ago

jan.meyer

Wow, this looks great. Already now, without the planed enhancements, it makes it much easier to find existing device servers. Anyway, I found some flaws in the catalogue. Nothing important, but I thought you might be interested in feedback.

It seems dynamic attributes and commands are not listed. For some servers it makes it hard to get their functionality.
Importing of multi class or inherited servers seems to result in mixed-up or duplicated information in some cases (OxfordCrypstream700, WagoRelay, GalilDMC)

In this last case, I know it is me to blame for making the namespace non unique. However, GalilDMCSplit depends on the other, single listed GalilDMCMotor.

Thanks for your great work!
Jan

# 7 years ago
pgoryl	lorenzo Looks nice. The search functionality works as expected! A chunk of info that's missing is the programming language; what about adding the programming language as fifth column in the Device Server table… as well as in the class description of each Class? Lorenzo Yes, it is something we have missed. For the search table it may do some trouble with table size. However for class view it will fit. Anyway, the language is already stored in a database. TO-DO.

# 7 years ago

pgoryl

lorenzo
Looks nice. The search functionality works as expected! A chunk of info that's missing is the programming language; what about adding the programming language as fifth column in the Device Server table… as well as in the class description of each Class?
Lorenzo

Yes, it is something we have missed. For the search table it may do some trouble with table size. However for class view it will fit. Anyway, the language is already stored in a database. TO-DO.

# 7 years ago
philippeg	Great work ! It will make it easier to find existing DS instead of coding new ones. - Philippe

# 7 years ago
Andy	I agree. Do you have any to share? Please upload them. Even if they are behind a firewall publishing them will make other people aware of them and they will contact you instead of rewriting them. Kind regards Andy

# 7 years ago
pgoryl	jan.meyer Wow, this looks great. Already now, without the planed enhancements, it makes it much easier to find existing device servers. Anyway, I found some flaws in the catalogue. Nothing important, but I thought you might be interested in feedback. It seems dynamic attributes and commands are not listed. For some servers it makes it hard to get their functionality. Importing of multi class or inherited servers seems to result in mixed-up or duplicated information in some cases (OxfordCrypstream700, WagoRelay, GalilDMC) In this last case, I know it is me to blame for making the namespace non unique. However, GalilDMCSplit depends on the other, single listed GalilDMCMotor. Thanks for your great work! Jan Welcome :). Thanks for the feedback. Regarding mixed-up information: The import script looks for folders with 'tag/trunk/src' subfolders and tries to identify a base for looking for .xmi files. Then it treats all files found there and in subfolders as a part of a device server. This is the case of OxfordCrypstream700, GalilDMC. I can run import script in Galil subfolders separately if you think it is worth. For WagoRelay, it was an issue with importing process. Already corrected.

# 7 years ago

pgoryl

jan.meyer
Wow, this looks great. Already now, without the planed enhancements, it makes it much easier to find existing device servers. Anyway, I found some flaws in the catalogue. Nothing important, but I thought you might be interested in feedback.
It seems dynamic attributes and commands are not listed. For some servers it makes it hard to get their functionality.
Importing of multi class or inherited servers seems to result in mixed-up or duplicated information in some cases (OxfordCrypstream700, WagoRelay, GalilDMC)
In this last case, I know it is me to blame for making the namespace non unique. However, GalilDMCSplit depends on the other, single listed GalilDMCMotor.

Thanks for your great work!
Jan

Welcome :). Thanks for the feedback. Regarding mixed-up information: The import script looks for folders with 'tag/trunk/src' subfolders and tries to identify a base for looking for .xmi files. Then it treats all files found there and in subfolders as a part of a device server. This is the case of OxfordCrypstream700, GalilDMC. I can run import script in Galil subfolders separately if you think it is worth.
For WagoRelay, it was an issue with importing process. Already corrected.