## Current Behavior <!--- If describing a bug, tell us what happens instead of the expected behavior --> <!--- If suggesting a change/improvement, explain the difference from current behavior --> - DAQ subscribes to the RE's doc stream to figure out that it needs to end a run when the RE's run ends - This involves a lot of gross logic that can fall apart - This creates confusing scenarios where certain bluesky plans can accidentally run multiple DAQ runs - This creates weird edge cases where only a special RE in a session can run a DAQ scan ## Possible Solution <!--- Not obligatory, but suggest a fix/reason for the bug, --> <!--- or ideas how to implement the addition or change --> - Replace auto run start/end with explicit daq.run_start_plan, daq.run_stop_plan - Include these in the nabs decorators ## Steps to Reproduce (for bugs) <!--- Provide a link to a live example, or an unambiguous set of steps to --> <!--- reproduce this bug. Include code to reproduce, if relevant --> 1. Create a daq scan that does multiple plans from bluesky.plans 2. Run it ## Context <!--- How has this issue affected you? What are you trying to accomplish? --> <!--- Providing context helps us come up with a solution that is most useful in the real world --> - Common issue when creating more complex plans
