This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Failed to move to find tip #924
Comments
DominicOram
added
the
needed_for_release
Issues that must be complete before the next release
label
Oct 9, 2023
DominicOram
added a commit
that referenced
this issue
Oct 9, 2023
We have seen this a couple of additional times when running overnight |
https://ispyb.diamond.ac.uk/samples/sid/5003238 initially found a tip at (608, 360) but then couldn;t find the loop. We could also fix this by tweaking the edge detection settings. Suggest we find some time in shutdown to leave the edge detection on with no pin then see if we can catch when it gives a false positive |
DominicOram
removed
the
needed_for_release
Issues that must be complete before the next release
label
Oct 12, 2023
Good solution will be wait until the pin tip is "stable". In which case it will be easier to do after #863 |
@dperl-dls waiting on ophyd2 oav stuff |
Hotfix in DiamondLightSource/dodal#242 works fine for now, let's call this done |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For collection https://ispyb.diamond.ac.uk/dc/visit/mx33658-16/dcg/10470342 Hyperion should have moved
x
around to try and find the tip, it didn't. From the logs it looks like Hyperion thought it found a tip. We should:The text was updated successfully, but these errors were encountered: