Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in or
create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision |
Your text |
Line 178: |
Line 178: |
| $ Rscript -e "rmarkdown::render('analysis.Rmd')" | | $ Rscript -e "rmarkdown::render('analysis.Rmd')" |
|
| |
|
| === Python Virtual Environments ===
| |
|
| |
| Python virtual environments are a great way to manage project dependencies, and they seem to work on HYAK in the same way that they do on local machines. First install virtualenv using pip (this only needs to be done once).
| |
|
| |
| $ pip install virtualenv --user
| |
|
| |
| Initialize a new virtual environment in the current directory. Many people create a new virtual environment for each project.
| |
|
| |
| $ # this virtual environment will use python 3
| |
| $ virtualenv venv -p python3
| |
|
| |
| To activate the virtual environment from a login node or an interactive compute node
| |
|
| |
| $ source <path_to_venv_parent_dir>/venv/bin/activate
| |
|
| |
| To load a virtual environment in parallel sql, add the following to your PBS bash script
| |
|
| |
| source <path_to_venv_parent_dir>/venv/bin/activate
| |
|
| |
|
| === Killing jobs on compute nodes === | | === Killing jobs on compute nodes === |