Experimental Physics and
Industrial Control System

Emmanuel Mayssat <[email protected]> · Fri, 17 Nov 2006 10:30:32 -0800

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.

Here is what I learned from naming conventions with epics.

1/ I like to know which hardware part is providing the signal.
This provides a tremendous help for low level debugging.
(ex. Signals is from pin 2 on ADC 3 on computer X [located at Y])

2/ End user cares about the meaning of the signal. 
(ex. Temperature of gun, setting of 3rd magnet in transport line)

3/ PV names are often found hardcoded in programs

4/ Low level and high level programming is managed by 2 different
groups. 

Solution:
Use several (two) naming conventions! 
One for each level and use ALIASING!!!!!

Q: What happens if you change hardware?
You change the low level PV names and the inputs of aliases.
No need to change programs, striptools configuration files, etc.

Enjoy!

--
Emmanuel Mayssat
Lyncean Technologies, Inc

On Fri, 2006-11-17 at 12:33 -0500, Gurd, Pamela A. wrote:
> It's true that we have had problems with the sequencer going over 28
> characters, but I think they're less of a problem than it would be to
> try to stay within 28 characters.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System