Introduction: This workshop will discuss how the various Python related tools work together on the cluster and introduce a series of best practices for managing these environments.
Course Goals:
Understand where pip installs packages within a user’s home folder with respect to different versions of Python.
Understand how to use pip to install a package within a conda environment.
Demonstrate how to create a conda environment, with pip installs, that can be shared across a project.
Demonstrate creating a module file to load a conda/python environment.
Note:
The focus of this workshop is on how to use Python, Pip and Conda explicitly on the ARCC clusters (not on desktops).
This is NOT an introduction to Python programming. Users should be familiar with python, using pip, and creating conda environments.
Headers and Sections
Each sections should start with a header of ‘Heading 1’. This helps to make sure that the Table of Contents operates like an agenda. Also it helps when we “advance a slide” it jumps to the top of the section. Each section should be limited in length to no more than 14 lines of straight text to ensure that when presenting it can be viewed as a “Slide”.
This is 14 lines. A.K.A. the End
Code Examples
Two Column Tables are nice ways to separate content/ Background info along with a code example on the same “Slide”. Please notice the table width. This should stop scroll bars from appearing
| Please use the "code snippet" in the + button when creating code examples. Also please do not go past the width of the table. This is to prevent scroll bars appearing This is the Max number of code lines to show an example |
Straight Code - No context
Limit to 16 lines in the example. This is the end
Same Thing With Images
Two Column Tables are nice ways to separate content/ Background info along with an image example on the same “Slide”. Please notice the table width. This should stop scroll bars from appearing
|
|
Alternatively No Table
Finally The End
Link to Previous sub-module or Home Module |
Align left link to next sub-module or home |