Experimental Physics and
Industrial Control System

On Aug 5, 2010, at 5:31 PM, Alan Biocca wrote:

> One thing that is worth considering for new projects is to make a program that builds names. A web based application might be best. So whatever is decided is codified into this one name ratifier.
> 
> Record aliases are of great use also where two naming conventions might meet. For example BPMs and other sensors are of several physical types, but from some views they might not have the same variation in naming as they might from a lower level view.
> 
> -- Alan


Another example of where two naming conventions overlap is when the hardware-oriented engineer want to name a PV based on it's hardware addresses for testing purposes  ...  IOC1:AB1771:C2:S1  ... and the application engineer wants to name that same channel as  LINAC:CAV1:Temperature.  Yes, we have all defined duplicate PVs to implement this (or have one link to the other) but PV aliases is a much more elegant solution.

  Ned

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 Alan Biocca

Navigate by Date:

Prev: BOY - XY Graph and macro substitution PaweÅ PrÄdki

Next: Re: Making a case for cases Ralph Lange

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

Navigate by Thread:

Prev: Re: Making a case for cases Alan Biocca

Next: Re: Making a case for cases Pete R. Jemian

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