-
Notifications
You must be signed in to change notification settings - Fork 79
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
Ophyd devices do not comply to the protocols defined in bluesky
bug
#1212
opened Oct 9, 2024 by
DiamondJoseph
Update intersphinx inventory to use https://blueskyproject.io/bluesky/main/objects.inv
#1197
opened Jun 27, 2024 by
mrakitin
Is the BadPVName exception enforcing an EPICS naming rule or just a convention?
#1196
opened Jun 19, 2024 by
gazzar
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
Previous Next
ProTip!
Follow long discussions with comments:>50.