Phillip Weinberg

>Sometimes you need to share tools between different plot objects (for example sync crosshair between timeline channels you need to pass the tools around, or sync data between register and...

Also Add Bloqade Radius to `AnalogCircuit.show()` and fix line weight to scale with zooming out/in.

I think we should probably extend IR to include execution instructions to the different backends: - For hardware this is straightforward we would need a device nodes and nodes to...

I propose the following. Since we don't really plan on expanding AHS too much more, we should: 1. remove dictionaries from the IR types and replace them with attributes, e.g....

I don't think automatically doing this is the best idea, I recall this being a bit of an issue in Bloqade.jl

@jon-wurtz He means is would be something on the level of `parallelize` so you would do something like: ``` program.assign(...).batch_assign(...).args(...).transform("Aquila").braket.aquila().run_async(...) ```

`run` and `run_async` have very different behaviors. `run` *regardless of the backend* will guarantee that the results are returned to you either because its an emulation job which runs automatically...

That is exactly how we implement `run` for hardware jobs, the difference is we `fetch` is not blocking either, what you want is `pull` which is blocking. But `run_async` doesn't...

I really hope you look at the [tutorials](https://queracomputing.github.io/bloqade-python-examples/latest/), these show how you can combine emulation and hardware submission making use of the different API's

One issue with this feature would be how to handle the `Report` output when your patches have sites that are shared amongst the different patches. the naive implementation would just...