there has been a scattering of work on putting bluesky behind a GUI (use the UI to collect user input, call the RE on pushing a button). It works, but we have not fully settled on "the" solution or a standard set of widgets etc
https://github.com/bluesky/bluesky-ui <- that needs some love
we also have some very very beamline specific tools that have grown
I tend to think if this is nested control loops. There is a very tight loop that should be below the control system (things like PID loops etc), tight human-in the loop tweaking (due with an engineering screen interacting directly with the control layer), scientific orchestration (done via bluesky plans), CLI driven data acquisition (using RE + plans), user acquisition screens (which in turn defers to bluesky)
Dear all, I'm new to bluesky and trying to create a ophyd object.
I have a very basic problem, but I don't know how to fix it.
When I typed these command lines, lots of errors occurred.
In [1]: from ophyd import EpicsMotor
In [2]: motor = EpicsMotor('Newport:m1', name='motor')'Newport:m1' is the motor's PV name in EPICS ioc and the IOC works well.
Can you give me any advice?
what do you get if you do
import epics?
In fact, I had already installed pyepics under the epics directory. But why did it go wrong? Is it because I didn't add the directory into PATH?
I am not sure what you mean by " had already installed pyepics under the epics directory", but package installation is one of the surprisingly tricky things about this operation. This is compounded by pyepics upstream making some choices about their packaging that in my view complicate getting it correct
Hi! I'm running through the bluesky tutorial and installing the packages in a conda environment, I ran into an error when opening ipython with the --matplotlib=qt5 flag:
Original error was: dlopen(/Users/pennebak/miniconda3/envs/bluesky/lib/python3.7/site-packages/numpy/core/_multiarray_umath.cpython-37m-darwin.so, 2): Library not loaded: @rpath/libgfortran.4.dylib
Referenced from: /Users/pennebak/miniconda3/envs/bluesky/lib/libcblas.3.dylib
Reason: image not foundHave any of you seen this before?
but installing from conda should work\
numpy/numpy#12970 <- I think that issue is related?
My knee-jerk guess is we have something on nsls2forge that pins to the broken version of numpy
No it looks the numpy is consistent between the two.
could this also have been the problem? or does the libblas cause this:
working:
vs
failing:
working:
libgfortran 4.0.0 2 conda-forgevs
failing:
libgfortran 4.0.0 0 nsls2forge
I'm working up a tutorial on EPICS area detector (using ADSimDetector). It's a Jupyter notebook, still in a draft form, but has some words in between the lines of bluesky/ophyd code. Perhaps this may be useful to you? Feedback is welcome. https://github.com/BCDA-APS/use_bluesky/blob/master/lessons/lesson6.ipynb
are you call the RE from inside another event loop?
I use one event loop to create the datagram endpoints. I use run_until_complete() to create the endpoints. The protocol instantiates the devices during this time. Once the devices are created, I pass the loop to the RunEngine, but the datagram_received() for my protocol never fires.