Gary,
I'm most familiar with the motor module, so my questions will be focused
on the changes to motor.
Should there be a YAML file in the dls-controls fork of motor?
I see the new ParamSet file:
https://github.com/dls-controls/motor/blob/pvi/motorApp/MotorSrc/asynMotorControllerParamSet.h
Was asynMotorControllerParamSet.h created by hand or generated based on
a YAML file?
Kevin
On 5/19/20 12:03 PM, Yendell, Gary (DLSLtd, RAL, LSCI) via Tech-talk wrote:
> Hi!
>
> At DLS we have been working on an idea of Tom Cobb's making: PVI (PV
> Interface).
>
> There is an outline hosted on readthedocs:
> https://pvi.readthedocs.io/en/latest/contents.html
>
> As a brief summary, the goal of PVI is to consolidate the duplicated
> boiler plate of an EPICS driver (templates, low-level screens and the
> parameter creation in the c++ code) into one place, allowing these
> pieces to be generated instead.
>
>
> The main purpose of this particular message is to point out the WIP
> branches of some key modules that have been updated for this framework:
> #
>
> asyn - https://github.com/dls-controls/asyn/tree/pvi
>
> ||
> #
>
> ADCore - https://github.com/dls-controls/ADCore/tree/pvi
>
> #
>
> ADSimDetector - https://github.com/dls-controls/ADSimDetector/tree/pvi
>
> #
>
> ADPilatus - https://github.com/dls-controls/ADPilatus/tree/pvi
>
> #
>
> motor - https://github.com/dls-controls/motor/tree/pvi
>
> #
>
> pmac - https://github.com/dls-controls/pmac/tree/pvi
>
>
> Other modules that we would like to extend this to are include further
> areaDetector drivers as well as streamDevice, but this has not been
> pursued as yet.
>
> We are hoping for people to take an interest in this idea so that it can
> be adopted more widely than just at DLS, so any thoughts and comments
> would be appreciated, especially from those who have an interest in
> these modules and can comment on the new structure.
>
> Cheers,
> Gary
>
> --
>
> 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
>
- Replies:
- Re: 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
- 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: Displaying string Waveform in CaQtDM Mark Rivers via Tech-talk
- Next:
Re: 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:
Re: 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 Yendell, Gary (DLSLtd, RAL, LSCI) 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
|