Re: Wrapper of pyepics and p4p

[André Favoto via Tech-talk <tech-talk at aps.anl.gov>]

Hi!

Coincidently or not, on the previous thread I was just talking about this. 

As epicsWS is already fully decoupled from WEISS frontend, I would be willing to make it a separate standalone module inside the organization, and just submodule it in the core project. This way, WEISS (and everyone else) could also benefit from improvements and effort you put into it.

I think it would be of better use for the community if we joined forces instead of maintaining separate projects for the same purpose

I'll reach out so we can talk a bit more about that :) 

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Wang, Lin via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, 09 June 2026 09:08:32
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Wrapper of pyepics and p4p

 

Dear all,

A wrapper of pyepics and p4p has been developed and shared in the following links,

https://github.com/wanglin86769/capva

https://pypi.org/project/capva

It is developed based on the epicsWS module of weiss [1] project and the EPICS client layer is extracted as a standalone PV client library. Single API for both CA and PVA is provided, and the data format for PV get and monitor operations is a unified PVData model, which is carried over directly from the weiss project.

For more detail, please refer to the GitHub link above.

Regards,

Lin

[1] https://github.com/weiss-controls/weiss