Kiowa Scott-Hurley (7e0fab10) at 02 Aug 16:42
Editing some typos in add-strudel2-conda
Chris Hines (ebcffa08) at 02 Aug 14:54
Chris Hines (e25f67cc) at 02 Aug 14:54
Merge branch 'otherenvs' into 'master'
... and 3 more commits
Chris Hines (ebcffa08) at 02 Aug 14:10
Update conda-env-jupyter.sh.template
Chris Hines (092d84fe) at 02 Aug 13:55
Update add-strudel2-conda
Chris Hines (bca47845) at 02 Aug 13:41
add other conda environments
Kiowa Scott-Hurley (ba924143) at 18 May 16:34
I've made some small changes (<20 lines) in preparation of advertising the miniconda install script on docs.massive following some feedback.
There is now a section that checks if the filepath to install miniconda in ends in /miniconda, and adds it if it doesn't, per Adam's feedback. Without this, if you try to install in /home/ksco0005 for example, I'll get an error about the directory already existing despite there being no conda install there.
We run the lines of code that specify packages and envs should be stored in the install directory instead of $HOME - I don't know if there is a better place/time to run this step?
I've changed SAMPLEENVNAME to mypythonenv to match the docs.massive terminology for consistency
I've also changed the instructions for conda create to include "python=3.6" so Python gets installed with your env, per comments from Jaf and Adam on my draft Python docs.
Let me know if there's anything glaringly wrong, I am not a bash programmer.
Jafar Lie (e92053df) at 18 May 16:34
Merge branch 'edit-install' into 'master'
... and 4 more commits
I've made some small changes (<20 lines) in preparation of advertising the miniconda install script on docs.massive following some feedback.
There is now a section that checks if the filepath to install miniconda in ends in /miniconda, and adds it if it doesn't, per Adam's feedback. Without this, if you try to install in /home/ksco0005 for example, I'll get an error about the directory already existing despite there being no conda install there.
We run the lines of code that specify packages and envs should be stored in the install directory instead of $HOME - I don't know if there is a better place/time to run this step?
I've changed SAMPLEENVNAME to mypythonenv to match the docs.massive terminology for consistency
I've also changed the instructions for conda create to include "python=3.6" so Python gets installed with your env, per comments from Jaf and Adam on my draft Python docs.
Let me know if there's anything glaringly wrong, I am not a bash programmer.
I've made some small changes (<20 lines) in preparation of advertising the miniconda install script on docs.massive following some feedback.
There is now a section that checks if the filepath to install miniconda in ends in /miniconda, and adds it if it doesn't, per Adam's feedback. Without this, if you try to install in /home/ksco0005 for example, I'll get an error about the directory already existing despite there being no conda install there.
We run the lines of code that specify packages and envs should be stored in the install directory instead of $HOME - I don't know if there is a better place/time to run this step?
I've changed SAMPLEENVNAME to mypythonenv to match the docs.massive terminology for consistency
I've also changed the instructions for conda create to include "python=3.6" so Python gets installed with your env, per comments from Jaf and Adam on my draft Python docs.
Let me know if there's anything glaringly wrong, I am not a bash programmer.
Kiowa Scott-Hurley (ba924143) at 18 May 15:36
Changed the example conda create command to include Python version ...
... and 1 more commit
Kiowa Scott-Hurley (264bc50b) at 18 May 14:57
Adding code to ensure packages and environments aren't put in /home...
... and 1 more commit
Kiowa Scott-Hurley (b751d71c) at 18 May 14:31
Chris Hines (96557fd2) at 23 Apr 11:48
Jafar Lie (b751d71c) at 23 Apr 11:48
Merge branch 'jupyter_usage' into 'master'
... and 1 more commit