Experimental Physics and
| |||||||||||||||||
|
Hi Jameson,
On Fri, Aug 15, 2014 at 12:52 AM, Jameson Graef Rollins <[email protected]> wrote:
--Matt Newville
If you're really just doing a loop like the above example, and already waiting for the put() to complete, the small extra time to wait for the "real, explicit" ca_get() to run is probably insignificant. If that was just a test to show the inconsistency, then, yeah it depends on how soon you need the value. It's probably reasonable to have PV.get() do an explicit ca.get() by default -- have use_monitor=False as the default -- and use the "value" attribute to hold "the most recent value posted by monitor" without doing an explicit ca.get(). I don't think that would really break much code. It might cause other confusion, but probably less than the current state. I'd happily listen to advice on "the right behavior" for this, but probably want to wait for a new minor version to make this change. Like Tim said, the PV() class does not expose supplying a callback to get() and then waiting for that to have run before updating the fetched value. That might be worth having too.
| ||||||||||||||||
ANJ, 17 Dec 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |