You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some situations where you want an Ophyd device to be included as a detector even though it's not what we typically think of as a detector. An example from the recent beamtime with Jerry Seidler's group.
Each crystal analyzer has the following structure, where there individual items are positioners.
Users wanted to do a scan on analyzer.energy, e.g. bp.scan([I0, IpreKB], analyzer.energy, 7800, 7820). However, at each point in the scan, they also wanted to know the values for the other positioners, especially energy.horizontal. In Bluesky, this is easy, just include the analyzer as a detector: bp.scan([I0, IpreKB, analyzer], analyzer.energy, 7800, 7820). However Firefly only shows things with the "detectors" label right now.
Proposed Behavior
99% of the time, the list of options should just be things with the "detectors" label. However, we need a way to also include all the devices.
Maybe we can re-use the component selector for this?
Maybe the detector list is something where you can choose from a list and have to move the selection over to a second list. That way the source list could change depending on whether you want just detectors, or everything. Just an idea, not necessarily the best option. Here's a mockup of what I was thinking.
The text was updated successfully, but these errors were encountered:
Another thought I had, instead of putting tabs into the detector selector, maybe we should put a combobox at the top of the component selector with all the different labels, like "detectors", "ion_chambers", "motors", "all devices", etc.
There are some situations where you want an Ophyd device to be included as a detector even though it's not what we typically think of as a detector. An example from the recent beamtime with Jerry Seidler's group.
Each crystal analyzer has the following structure, where there individual items are positioners.
Users wanted to do a scan on
analyzer.energy
, e.g.bp.scan([I0, IpreKB], analyzer.energy, 7800, 7820)
. However, at each point in the scan, they also wanted to know the values for the other positioners, especiallyenergy.horizontal
. In Bluesky, this is easy, just include the analyzer as a detector:bp.scan([I0, IpreKB, analyzer], analyzer.energy, 7800, 7820)
. However Firefly only shows things with the "detectors" label right now.Proposed Behavior
99% of the time, the list of options should just be things with the "detectors" label. However, we need a way to also include all the devices.
Maybe we can re-use the component selector for this?
Maybe the detector list is something where you can choose from a list and have to move the selection over to a second list. That way the source list could change depending on whether you want just detectors, or everything. Just an idea, not necessarily the best option. Here's a mockup of what I was thinking.
The text was updated successfully, but these errors were encountered: