-
Notifications
You must be signed in to change notification settings - Fork 24
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
should we be able to connect devices without the run engine? #81
Comments
At the moment the RE is only require if you do |
And you can pass |
+1 to defaulting to current loop, would be good minimize coupling between ophyd async and bluesky |
@coretl, @callumforrester, @OCopping and I had a meeting on this. we agreed to leave things how they are, but add documentation. A summary of how things currently work:
|
Part of the appeal of ophyd v1 is that you can use it stand-alone, without the run engine or bluesky. This is not true of ophyd-async, only because we need the bluesky event loop to be running to connect devices. Could we not change the connection logic so that;
The text was updated successfully, but these errors were encountered: