Databroker v1 interface used about bluesky-queueserver HOT 2 OPEN

I would suggest to define RE and db in startup code, subscribe RE to db and start RE Manager with option --keep-re. This way you are not limited to built-in Queue Server options and you can subscribe RE to as many standard or custom callbacks as you need. Initially we had an idea to implement some small set of universal subscriptions sufficient for all workflows in the Queue Server code, but now it does not seem achievable. There is also push for higher flexibility from beamline staff. My current view is that the internal options for instantiation and configuration of RE will be used mostly for demos and all practical beamline applications will have RE defined and configured in startup code. This is the way we do it at the beamlines that are using the Queue Server.

Note that RE (mandatory) and db (optional) are reserved names of the objects that should be defined in global namespace of the startup script:

In my opinion we should change the built-in initialization code to Databroker V2 API, but we may not be ready to use V2 in basic tutorials.

from bluesky-queueserver.

Thank you for the response. I figured I'd eventually have to go down this route. I'm happy enough to close this ticket, unless you want the reminder around.

from bluesky-queueserver.