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	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: PVI Prototype - a framework for specifying the interface to an EPICS driver in a single YAML file
From:	"Yendell, Gary \(DLSLtd, RAL, LSCI\) via Tech-talk" <tech-talk at aps.anl.gov>
To:	bob dalesio <bob.dalesio at gmail.com>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date:	Tue, 19 May 2020 18:02:35 +0000

Some of the main benefits are:

It makes it quicker and easier to add new parameters. You add an entry in the YAML file and regenerate and it then appears as a record and as an asyn parameters so you then just add the logic referencing the new parameter.

When a parameter is added it will appear on the generated screens for all supported UIs, so facilities using different screens will see any new parameters with no effort. This would be especially nice when it is a development branch, as there is no requirement for other sites to update the screens before they can try it out and give feedback. They just regenerate with their formatter.

An entry will also be added to a generated rst table to be displayed in the documentation.

I think it will also allow sharing of some parameters by composition rather than inheritance, such as the file parameters that are used in ADPilatus and the NDPluginFile drivers. This would simplify things for middleware services like Malcolm.

Cheers,

Gary

Sent from Outlook Mobile

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.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

References:: PVI Prototype - a framework for specifying the interface to an EPICS driver in a single YAML file Yendell, Gary (DLSLtd, RAL, LSCI) via Tech-talk

Navigate by Date:: Prev: RE: BASE 7.0.x@Windows_64 - Channel Access Context in shared library - "ca_context_destroy bug" Freddie Akeroyd - UKRI STFC via Tech-talk; Next: Displaying string Waveform in CaQtDM Paul Nord 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
Navigate by Thread:: Prev: PVI Prototype - a framework for specifying the interface to an EPICS driver in a single YAML file Yendell, Gary (DLSLtd, RAL, LSCI) via Tech-talk; Next: Re: PVI Prototype - a framework for specifying the interface to an EPICS driver in a single YAML file Peterson, Kevin M. 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

ANJ, 19 May 2020

· Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System