databroker icon indicating copy to clipboard operation
databroker copied to clipboard

Unified API pulling data from multiple sources

Results 112 databroker issues
Sort by recently updated
recently updated
newest added

https://github.com/bluesky/databroker/blob/970e9148dfab5e77101d40f059ecb30d064eac81/databroker/core.py#L2146 **Filling external events with dtypes other than "array" is currently broken, due to a lack of functionality in `extract_dtype`** When creating a descriptor document, a "dtype" is required for...

Some features available in earlier version of data broker V1 methodology are missing now in `databroker version 1.2.3`. Whether or not this was a design choice is not clear to...

## Current Behavior The Projector code in databroker supports defining an output of a stream's configuration settings. A stream can have multiple configurations (which are items in an array). Each...

enhancement

Hi there, I am relatively new to databroker, and I am trying to use a script that looks like it was written for the v1 API. I am able to...

![image](https://user-images.githubusercontent.com/11858848/112210167-bf21b000-8bf0-11eb-8adf-083dbc62a8fe.png) This should be run.canonical, not run.documents. The file is here: https://github.com/bluesky/databroker/blob/master/docs/source/tutorials/export.rst

I use the search keys function in `db()` to setup a big batch of header to then automate analysis. When it fails in the search phase, I have no idea...

Is it a feature of databroker to return a list of runs in any specific order (such as chronological)? When I use a catalog backed by MongoDB (such as https://github.com/BCDA-APS/apstools/issues/498),...

This would enable users to search like: ```py catalog.search({'plan_name': 'relative_scan'}, stop={'exit_status': 'success'}) ``` and search on descriptors as well, something that @CJ-Wright has been rightly requesting for some time.

## Summary Let's try refactoring Databroker's `Broker`, `BlueskyRun`, and `BlueskyEventStream` objects to drop the `intake.Catalog` and `intake.DataSource` base classes while remaining backward-compatible with `databroker.v2` and interoperable with intake and its...

As @untzag suggests, > You have some content in databroker-concepts that would be useful for this. https://blueskyproject.io/databroker/docs-rewrite-draft/explanations/relationship-to-intake.html#databroker-concepts