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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Possible to create aliases for record fields? |
From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
To: | Zimoch Dirk <dirk.zimoch at psi.ch> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 2 Jan 2023 12:37:33 -0800 |
On 12/28/22 03:47, Zimoch Dirk via Tech-talk wrote:
At the moment, that is not possible. I had planned for quite some time to implement that.
... But I don‘t know what the core developers think of this.
Aliasing fields seem like a reasonable feature. Although it isn't yet clear to me how this would work in detail. eg. to take an example from below.
alias("det1.NELM", "det1:NELM")
What would "caget det1:NELM.RTYP" return? There may also be complications depending on what changes to the 'struct dbBase' tree would be needed.
DirkAm 20.12.2022 um 19:50 schrieb Li, Ji via Tech-talk <tech-talk at aps.anl.gov>: 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, 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? Best, -Ji Li