Issues: bluesky/ophyd
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
More informative debug logs on callbacks from monitored EpicsSignal
#1188
opened Apr 11, 2024 by
DominicOram
pip installation does not have all required dependencies
#1170
opened Oct 25, 2023 by
marcomontevechi1
Docs: Reintroduce overview of architecture + explanations of "hints", "components"
documentation
#1164
opened Oct 7, 2023 by
padraic-shafer
Idea: Add a human-readable "display name" to Ophyd Objects to supplement name
#1161
opened Oct 4, 2023 by
cjtitus
v2: Devices with a mixture of timing-out and erroring signals throw some exceptions away
bug
#1153
opened Aug 21, 2023 by
callumforrester
v2: Should we handle errors from signals that don't handle
CancelledError
idea
#1152
opened Aug 21, 2023 by
callumforrester
v2: BUG: No error raised upon casting array data from np.int64 to np.int32
#1145
opened Aug 4, 2023 by
olliesilvester
v2: Make the split between Signal and SignalBackend support tables
#1120
opened May 25, 2023 by
coretl
ADTriggerStatus (v1) notifies watchers after completion hook
bug
help wanted
needs_review
question
#1115
opened May 2, 2023 by
callumforrester
v2: DeviceCollector does not connect variables that existed before being entered.
#1100
opened Mar 13, 2023 by
rosesyrett
SoftPositioner is not identified as device or signal using walk_components()
bug
#1095
opened Feb 24, 2023 by
prjemian
Ophyd.v2: async get_value() calls don't work with ipython await syntax
#1092
opened Feb 13, 2023 by
rosesyrett
Previous Next
ProTip!
Updated in the last three days: updated:>2024-05-12.