-
Notifications
You must be signed in to change notification settings - Fork 1
Create custom conda environment for 8ID #2
Comments
first, check that there is not a conda environment already named
Good, we can proceed with commands to build and populate with BS
you might get a warning that conda needs to be updated on the server, that's ok for now |
This is a good time to add some conda channels (web sites with software) for our upcoming downloads and maintenance. Here's what I have used elsewhere:
|
install bluesky and friends, see what else comes along, create a requirements file and install from that:
|
be sure to activate the new bluesky environment from a bash shell
Could be faster if we already used bash and had some conda environment already activated:
installation command (using the requirements file from previous step)
|
Note in our requirements that the tornado package must be kept at the latest version before major version 5 (see ContinuumIO/anaconda-issues#8789). We imposed that at the installation but we want to keep it from being updated later. We'll add a
|
Now we can test if we have installed enough software to be useful. Might still need more...
We need to wait for those PVs to connect. Check that
The complete structure is:
Current values are:
|
Good, our initial tests showed that we forgot to install PyEpics. That has been added to the requirements above now. |
@jkirchman See the new procedure at https://github.com/BCDA-APS/use_bluesky/blob/master/python_installation/environment.md |
Done with this conda environment. |
create a custom conda environment, local to the 8ID workstation to
insulate the beam line against unexpected changes in the /APSshare
installation of bluesky. There is some sensitivity to this at the beam
line and we should try to be conservative here.
The text was updated successfully, but these errors were encountered: