| 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: Possible to create aliases for record fields? |
| From: | "Li, Ji via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | Michael Davidsaver <mdavidsaver at gmail.com> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Tue, 20 Dec 2022 19:11:05 +0000 |
|
Thank you Michael.
Best,
-JiFrom: Michael Davidsaver <mdavidsaver at gmail.com>
Sent: Tuesday, December 20, 2022 13:58 To: Li, Ji <liji at bnl.gov> Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: Re: Possible to create aliases for record fields? On 12/20/22 10:49, Li, Ji via Tech-talk wrote:
> Hi, > > I'm trying to access record fields as PVs using alias command, such as: > > alias("det1.NELM", "det1:NELM") > alias("det1.TSEN", "det1:TSEN") > > The IOC didn't report errors, This lack of a warning/error is a bug. > but apparently they all pointed to det1 as the change to det1 appeared on these aliases, and vice versa, and this was proved by dbla. > > If alias command is not the right choice, are there any ways to create aliases/dummy PVs for fields? Field aliases are not currently possible. |