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: | Metadata for an NTTable |
From: | "Cobb, Tom \(DLSLtd,RAL,LSCI\) via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Fri, 15 Oct 2021 15:53:24 +0000 |
Hi all,
We're in the process of writing a
pythonSoftIOC that will allow every parameter from a
PandABox to be set. It will create the records by introspecting the PandA at startup, then run an IOC which will expose them over CA and PVA (via QSRV). All of the parameter types map to NormativeTypes, but there is more metadata for tables than will fit
in the
NTTable spec. Specifically:
The first could be solved by adding an optional
choices structure like
enum_t with entries for the columns which are enums and the second could be solved by adding optional
display and control structures like
NTScalar with entries for each column with this metadata. I could just add these to the IOC, but it would be good to discuss whether it is a good idea with others and make an addition to the normative types document.
Who would the right people be to discuss this with?
Thanks,
Tom
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |