EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: GOOD Naming conventions for devices and Epics records
From: "Gurd, Pamela A." <[email protected]>
To: Emmanuel Mayssat <[email protected]>
Cc: Andrew Johnson <[email protected]>, tech talk <[email protected]>
Date: Fri, 17 Nov 2006 13:35:23 -0500
Okay, I'll bite - I don't really see how that helps you get from the
end-user name to the hardware name, and hence to the hardware address.
You can get from the end-user name, looking into the IOC, to the
hardware address anyhow.  And if you have a rudimentary database, you
can get there, too.

It just adds a layer of complication, it seems to me.

   Pam.

> -----Original Message-----
> From: Emmanuel Mayssat [mailto:[email protected]]
> Sent: Friday, November 17, 2006 1:31 PM
> To: Gurd, Pamela A.
> Cc: Andrew Johnson; tech talk
> Subject: GOOD Naming conventions for devices and Epics records
> 
> 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.
> 



References:
GOOD Naming conventions for devices and Epics records Emmanuel Mayssat

Navigate by Date:
Prev: GOOD Naming conventions for devices and Epics records Emmanuel Mayssat
Next: RE: GOOD Naming conventions for devices and Epics records Chestnut, Ronald P.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: GOOD Naming conventions for devices and Epics records Emmanuel Mayssat
Next: RE: GOOD Naming conventions for devices and Epics records Chestnut, Ronald P.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·