EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  <19951996  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  Index 1994  <19951996  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 
<== Date ==> <== Thread ==>

Subject: Re: e2sr name mangling
From: [email protected] (Matthew Needes (LANL))
To: tech-talk@phoebus
Date: Tue, 20 Jun 1995 11:30:22 -0500
>RE: Matt Needes proposed changes to e2sr:
>
>I believe the whole approach of extensive use of properties and substitution
>in the schematic itself is clumsy, in that it requires additional work to
>maintain the schematic.  At CEBAF, we have used an additional utility program
>
>which encapsulates our desired naming convensions into rules, which operate
>correctly (99.9% of the time) on any record anywhere in the hierarchy, so that
>there is no burden to editing the schematic to get the names right.
>
>I think it would be a good idea to merge the two capabilities of e2sr and
>our name mangling program, but it should not be dependent upon setting
>properties in each record, but should instead be completely rule based.
>
>Chip

Part of the advantage of having more information on the schematic is that
you have more information at your fingertips while browsing a design.

A flat list of hierarchical substitution rules may or may not make much
sense until you compare them with your design anyway.  Why not just put
the rules on the schematic ?

Perhaps the additional schematic maintenance is not a big deal, because
in the absence of other requirements, a consistent naming scheme should
be the rule rather than the exception.  If you keep to a particular
standard you will avoid making wholesale changes to record instance
properties.  You may, however, have to maintain set properties on hierarchical
symbols (as in the PV substitutions).  Again, I think that watching these
values as you run down your design is an advantage.

If you want to define a different standard for yourself, you may have
to modify your symbol library (or perhaps just edb.def), and perhaps provide
"rules" (variable substitutions) at the top level of your schematic.

While I have not investigated the full power of either approach, I think
that top-level hierarchical substitution rules are equivalent to textfile
based substitutions anyway.

Matt


Navigate by Date:
Prev: Re: More changes.. when does Beta end watson
Next: Re: More changes.. when does Beta end Marty Kraimer
Index: 1994  <19951996  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: e2sr name mangling watson
Next: Re: e2sr name mangling Matthew Needes (LANL)
Index: 1994  <19951996  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·