EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  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  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Making a case for cases
From: Ralph Lange <[email protected]>
To: "[email protected]" <[email protected]>
Date: Fri, 06 Aug 2010 09:17:30 -0400
On 05.08.2010 19:23, Zhukov, Alexander P. wrote:
And the next step will be booting IOC not form text file but from a central database. And the only way to put records/PVs in the database is being accepted by validator.
So IOC cannot be booted in production environment unless all PVs are validated.

I truly believe that this is the only way to make an IOC engineer to follow any convention.

That may be true...


But all these mechanisms only validate the *syntax* of names. It is just as important to enforce the *semantics*, i.e. keep people from using a perfectly valid name for something not appropriate.

So your signal list and (even more importantly) signal domain list must contain comprehensive yet full definitions of the entries.
E.g. if "Rd"="readback" and "Set"="setpoint" only apply to analog values, if "Sw"="switch" only should be used for two-way switches (and "Sel"="selector" for more choices), if "St"="status" should a two-way (binary) status etc. etc., these facts must be mentioned in the lists and have to be manually enforced - using the stick Dave mentioned.


Also, don't let people get away with introducing "funny" names into the system - these usually stop being funny after a few years.
And don't allow implementation details (vendor, bus type, signal polarity, ...) in the names - or you are screwed once you have to change the implementation.


Ralph


References:
medm Mezger Anton-Chr.
Re: Making a case for cases Steven M. Hartman
Re: Making a case for cases Purcell, J. David
Re: Making a case for cases Andrew Johnson
RE: Making a case for cases Steiner, Mathias
Re: Making a case for cases Ralph Lange
RE: Making a case for cases Zhukov, Alexander P.

Navigate by Date:
Prev: Re: Making a case for cases Ned Arnold
Next: Looking for an experienced data acquisitoin architect Dalesio, Leo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Making a case for cases Zhukov, Alexander P.
Next: Re: Making a case for cases Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  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 ·