Experimental Physics and
| |||||||||||||||
|
I think what is important in this thread is not what naming convention is being used at site X, but rather what makes a GOOD naming convention. There is clearly a need to maintain both "mission oriented" and "hardware oriented" mechanisms for referring to channels. The former is needed for facility operation, and the latter for tasks such as installation, debug, and maintenance. Aliases are not the only way of achieving this. Other alternatives generally use the "mission oriented" name as a key to lookup the "hardware oriented" channel description. It may be a matter of personal preference which technique seems most natural. Facilities which make good use of DBs to manage their H/W configuration might wonder why this is even a subject of discussion! In the absence of a comprehensive configuration DB, the alias solution seems to offer substantial benefit. Even in the presence of a configuration DB, the alias solution seems very natural to me (FWIW). -- Larry
| ||||||||||||||
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |