Difference: Conda (7 vs. 8)

Revision 82022-05-29 - WilliamSeligman

Line: 1 to 1

META TOPICPARENT	name="Computing"

Conda

Line: 10 to 10

Before you go to conda

Changed:

<
< One thing I've noticed is that users using conda to install packages that are already available in the Nevis environment modules. Before you use conda to have access to packages like numpy or matplotlib, try using this command to load the Python version and libraries that I've installed on our applications server:

>
> One thing I've noticed is that users are using conda to install packages that are already available in the Nevis environment modules. Before you use conda to have access to packages like numpy or matplotlib, consider an alternative: use this command to load the Python version and libraries that I've installed on our applications server:

module load python

Line: 31 to 31

If you want a package that's not on the list, you can install it in your home directory with:

Changed:

<
< pip install --upgrade <package-name>

>
> pip install --user --upgrade <package-name>

If a package is of sufficient interest that other users may want it, let WilliamSeligman know. He'll install it on the both the library server and the notebook server.

Line: 42 to 42

The library server directory /usr/nevis is available to every system in the Linux cluster, including the batch nodes. It might simplify the task of making necessary software packages available for your condor jobs.

Changed:

<
< Conda and module load are incompatible with each other. Don't try to use both at once, or you'll get lots of error messages.

>
> Conda and module load can be mixed, but it's tricky. If you try to use both at once, carefully consider what each will do to your $PATH and $LD_LIBRARY_PATH environment variables.

Setting up conda

View topic | History: r11 < r10 < r9 < r8 | More topic actions...