prjemian
commented
4 months ago Thanks for posting the issue. I believe this is more about the best choice for the %matplotlib magic function to enable dyanmic updates of the plot. Different options supplied will produce or not produce the error.
Why this is more appropriate for the bluesky_training repository comes down to a couple bits of code in the notebook:
P = "sky:"Most of the training notebooks have been homogenized to use gp: instead of various other IOC prefixes, including sky:. A consistency problem in the bluesky_training repo due to evolution.
from bluesky.utils import install_nb_kicker
install_nb_kicker()These two lines are no longer needed by the BestEffortCallback. This indicates the notebook has not been revised in a few years.
Probably best to switch notebooks to this one: https://bcda-aps.github.io/bluesky_training/tutor/_basic_c.html
Still remaining is the question of which %matplotlib OPTION to pick. I'm still looking into it... Here's my concise test notebook:
%matplotlib inline
# %matplotlib ipympl
# %matplotlib nbagg
# %matplotlib notebook
# %matplotlib widget
from bluesky import plans as bp
from bluesky import RunEngine
from bluesky.callbacks import LiveTable, LivePlot
from ophyd import EpicsMotor
from ophyd.scaler import ScalerCH
RE = RunEngine({})
P = "gp:"
m1 = EpicsMotor(f"{P}m1", name="m1")
scaler = ScalerCH(f"{P}scaler1", name="scaler")
scaler.wait_for_connection()
scaler.channels.chan01.chname.put("clock")
scaler.channels.chan02.chname.put("I0")
scaler.channels.chan03.chname.put("scint")
scaler.preset_time.put(0.4)
scaler.select_channels()
m1.move(1)
print("Starting the scan ...")
RE(bp.scan([scaler], m1, 1, 5, 11), LivePlot("scint", "m1"))
lcgallington
When I try to run the jupyter notebook code for lesson 3 ( https://bcda-aps.github.io/bluesky_training/tutor/_lesson3a.html ) on the 2024_1 Bluesky training VM, I get an error that iPython is not defined. If I replace
%matplotlib notebookwith%matplotlib widget, the error goes away, but the plots are not updated real-time like the LiveTable, but after the scans are complete. Relevant code snippet below. I assume this is a case of a missing package rather than an issue with the code itself, so I posted here instead of bluesky training.There is a callback routine that will plot the data as it is acquired. When starting graphics, it is necessary to first initialize the graphics manager of the display. The setup is specific to the graphics manager. For command line or python program use, see https://blueskyproject.io/bluesky/callbacks.html#aside-making-plots-update-live .
For jupyter notebooks:
We’ll import the
LivePlotcallback from the Bluesky library:Count the scaler 5 times. We’ll just plot the
scintsignal.