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  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  <2025 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  <2025
<== Date ==> <== Thread ==>

Subject: Re: EPICS CA Gateway Aliases
From: "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>
To: "Smith, William" <william.smith at helmholtz-berlin.de>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Mon, 13 Jan 2025 17:47:20 +0000

Hi William,

 

The ALIAS syntax requires you to specify the alias name using back-references \1 \2 etc. The exact pattern syntax depends on which regex engine you’re using. Our gateways are built using the GNU regex library, here are some examples from one of our pvList files:

 

^Mt:S:NumBucketsFilledAI\(.*\)  ALIAS   XFD:NumFilledBuckets\1

^Mt:S:FilledBucketsWF\(.*\)     ALIAS   S-INJ:ActiveBucketFillQueueArrayM\1

^Mt:S:FillPatternWF\(.*\)       ALIAS   XFD:FilledBuckets\1

^S:BeamStatusMBBI\(.*\)         ALIAS   XFD:BeamStatus\1

^S:InjectingStatusMBBI\(.*\)    ALIAS   XFD:InjectingStatus\1

 

If you’re using PCRE you won’t use back-slashes before the capturing parentheses on the left, but your back-references on the right side should be the same. Our configuration doesn’t specify an asg or asl for these PV names, you’ll add those as necessary.

 

HTH,

 

- Andrew

 

-- 

Complexity comes for free, Simplicity you have to work for.

 

 

On 1/13/25, 11:06AM, "Tech-talk" <tech-talk-bounces at aps.anl.gov> wrote:

 

We are attempting to update the PV naming scheme at our lab. Part of our plan is to use aliases in the EPICS CA Gateway to allow for clients in other networks to access PV's with old PV names for a while. 

Is it possible to define regular _expression_ mappings for the aliases, or do I have to define exact mapping from one PV to another?

So far I have not had much luck with for example:

SISSY2EX:.*    ALIAS SISSY2ES12X:.* BLC_EMIL

 

where "SISSY2EX:" is an old prefix and "SISSY2ES12X:" is a new prefix.


Replies:
Re: EPICS CA Gateway Aliases Ralph Lange via Tech-talk
References:
EPICS CA Gateway Aliases Smith, William via Tech-talk

Navigate by Date:
Prev: EPICS CA Gateway Aliases Smith, William via Tech-talk
Next: Re: EPICS CA Gateway Aliases Ralph Lange via Tech-talk
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  <2025
Navigate by Thread:
Prev: EPICS CA Gateway Aliases Smith, William via Tech-talk
Next: Re: EPICS CA Gateway Aliases Ralph Lange via Tech-talk
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  <2025
ANJ, 13 Jan 2025 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions ·
· Download · Search · IRMIS · Talk · Documents · Links · Licensing ·