Dan Allan
Dan Allan
Consider dropping usage of `Event.clear()` and using instead read--write locks. See discussion in https://github.com/caproto/caproto/pull/600
From Michael Davidsaver (recalled from conversation by me, I hope accurately): > Serve one PV that updates at a slow, steady rate. Serve a second PV whose update rate ramps...
Work in Progress -- Do not merge! ReadResponse has been deprecated by Channel Access, but it would be good if caproto could serialize them correctly anyway in case it encounters...
Punting an aesthetic dicussion from #427 to a separate issue here. The current "direction" of a message is indicted by one of the symbols: ``` --->>>
Clients should be able to consult a mapping before initiating UDP broadcast. This mapping could be backed by: * a plain text file of PV names and addresses * etcd...
At the most recent EPICS meeting in Australia, Andrew Johnson suggested that caproto would be a good place to experiment with adding new serialization formats to Channel Access. Here is...
Our clients should automatically turn EventsOff if they notice that they are getting behind and need time to catch up in order to stay current. This works similar to our...
Part of the fun of this project for me is that we could talk to a dusty crate in the corner of Los Alamos using our Python 3.7 library. An...
This creates a second Python package in the databroker repository, `bluesky-tiled-plugins`, with the "special client" objects `BlueskyRun`, `BlueskyEventStream`, and `CatalogOfBlueskyRuns`, as well as the custom query objects `PartialUID`, `ScanID`, and...
Per discussion with @tacaswell: In this same same repo, make a separate `bluesky-tiled-plugins` package that contains the objects in `databroker.client` and their associated entrypoint declarations. These are the objects like...