databroker
databroker copied to clipboard
bluesky
Unified API pulling data from multiple sources
Entire text of message from Lin Yang: "It looks like the format of the event data returned from header.events() has changed. . That us causing the hdf5_export() function, which was...
## Description When pulling data back out of the msgpack backed temporary databroker we do not patch back on the filled dictionary indicating that some of the fields need to...
## Description All of the documented examples use the v2 interface. We should use a v2-compatible temporary databroker for self-consistency.
This needs careful review and a test. Just putting this here so we do not lose track of it.
When databroker was for both *writing* and reading it made some sense to put this here. Now it should be the job of writers (suitcase) or perhaps some separate separate,...
## Description: This PR adds a new filestore handler that should be used with the new filestore mixin defined in the PR [here](https://github.com/NSLS-II/ophyd/pull/623) ## Motivation: This was motivated by a...
- do not insert an invalid resource with both a non-trivial root and an absolute resource_path attn @CJ-Wright No test because I am racing the train into jamacia!
Get tz-aware datetime objects back This still needs tests + doc + consider if this is really the best way to do this.
In [b3a1d02](https://github.com/bluesky/databroker/pull/694/commits/b3a1d029c6032a928967fb6cfd7f8102847d99d5) I removed the documentation-building and documentation-publishing GitHub workflows. The docs use `databroker-unpack` to get some example data, and it's a bit convoluted. It also breaks when run against...