by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Kyle Sunden
    @ksunden_gitlab
    I follow along there (learned about it the same place you did over on pyqtgraph slack)... But hesitated posting yet because we don't have the best soluton for large array detectors yet
    Blaise Thompson
    @untzag
    wow... so many parallel projects
    blows my mind honestly
    Till Stensitzki
    @Tillsten
    @untzag We mostly doing pump-probe, my data pipeline for that is at https://github.com/Tillsten/skultrafast
    In the instrumentation space there is also https://github.com/Exopy/exopy
    Uses enaml which also quite cool, but again needs a buy in. Also the seperation between experiment and monitoring is a little bit to strict for my usecases.
    Due the amount on manual alignement we are doing, having direct responsive views for monitoring is abolutly essential.
    Till Stensitzki
    @Tillsten
    Alignment is much easier with 60 hz than with 10
    I would like to team up, but currently I have to write up some grants, since my funding ends this year.
    Blaise Thompson
    @untzag
    awesome thanks for the links @Tillsten
    Blaise Thompson
    @untzag
    are there examples or opinions regarding using bluesky as a "backend" for an entirely graphical user interface
    for example, write a custom pyside2 app that allows users to interactively set hardware, and then configure and launch plans
    not necessarily thinking of a gui which encompasses the full flexibility of bluesky, but just a simple ui for repetitive experiments on more "static" instruments
    any thoughts would be appreciated :smile:
    Thomas A Caswell
    @tacaswell
    You should look at pydm (https://github.com/slaclab/pydm)
    Thomas A Caswell
    @tacaswell
    which is more about working directly with the control layer to see the prompt monitoring / poking the hardware (the tight human-in-the-loop process Till was talking about above)
    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
    Blaise Thompson
    @untzag
    thanks---this is helpful
    Thomas A Caswell
    @tacaswell
    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)
    yangdl-github
    @yangdl-github

    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?

    Thomas A Caswell
    @tacaswell
    The issues is that we did not find either pyepics or caproto installed and have fallen back to a "dummy" backend which has enough of the API to let ophyd import and built purely synthetic Signals, but can not actually talk to EPICS
    what do you get if you do import epics?
    yangdl-github
    @yangdl-github
    Very helpful. Thanks, Tom.
    After I installed pyepics by using python -m pip install --upgrade pyepics, this issue was resolved.
    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?
    Thomas A Caswell
    @tacaswell
    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
    Tyler Pennebaker
    @ZryletTC

    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 found

    Have any of you seen this before?

    Thomas A Caswell
    @tacaswell
    that is a sign that your conda enviroment is not correct. What do you get for conda list and pip list ?
    Tyler Pennebaker
    @ZryletTC
    Thomas A Caswell
    @tacaswell
    Rescuing environments that are not consistent is frequently not worth doing (better to delete it and start over!)
    Tyler Pennebaker
    @ZryletTC
    Yeah this is from a fresh create
    Thomas A Caswell
    @tacaswell
    it looks like you conda installed everything instead of using pip?
    Tyler Pennebaker
    @ZryletTC
    yeah. was i not meant to?
    Thomas A Caswell
    @tacaswell
    the install instructions we have tested use conda to get a base python, and pip for everything else
    but installing from conda should work\
    numpy/numpy#12970 <- I think that issue is related?
    Tyler Pennebaker
    @ZryletTC
    Yeah, it looks like it. I'll try some of the recommendations
    Tyler Pennebaker
    @ZryletTC
    Hmm, what finally worked was reinstalling from conda-forge instead of nsls2forge
    Thomas A Caswell
    @tacaswell
    if you compare conda list from the working an non working envs are there any obvious issues?
    My knee-jerk guess is we have something on nsls2forge that pins to the broken version of numpy
    Tyler Pennebaker
    @ZryletTC
    Yeah, that was my guess. Checking now
    No it looks the numpy is consistent between the two.
    Thomas A Caswell
    @tacaswell
    how about libblas?
    Tyler Pennebaker
    @ZryletTC
    Same version, different build numbers
    Thomas A Caswell
    @tacaswell
    that i likely the culprit
    Tyler Pennebaker
    @ZryletTC
    libblas 3.8.0 16_openblas conda-forge
    vs
    libblas 3.8.0 14_openblas conda-forge
    Thomas A Caswell
    @tacaswell
    which one is the working one?
    Tyler Pennebaker
    @ZryletTC
    oh sorry, 16 is the working one
    could this also have been the problem? or does the libblas cause this:
    working: libgfortran 4.0.0 2 conda-forge
    vs
    failing: libgfortran 4.0.0 0 nsls2forge