Changes between Version 16 and Version 17 of pleiadescsh

Timestamp:

05/18/23 17:10:55 (2 years ago)

Author:

schlegel

Comment:

--

pleiadescsh

@@ -17 +17 @@
 == Environment ==
 
-Pleiades uses `csh` and not `bash`, add the following to your `~/.cshrc`:
+Pleiades generally uses `csh` by default instead of `bash`.  If you are using the `csh`, then add the following to your `~/.cshrc`:
 {{{
 
@@ -29 +29 @@
 
 #Packages
-module load pkgsrc/2020Q4
 module load comp-intel/2018.3.222
-module load mpi-intel/2018.3.222
+module load /nasa/intel/impi/2021.3/modulefiles/mpi/2021.3.0
 
 #Set compilers
@@ -44 +43 @@
 
 '''Do NOT install mpich'''. We have to use the one provided by NAS. Pleiades will ''only'' be used to run the code, you will use your local machine for pre and post processing, you will never use Pleiades' matlab. You can check out ISSM and install the following packages:
- - PETSc (use the pleiades script install-3.14-pleiades.sh or newer)
+ - PETSc (use the pleiades script install-3.17-pleiades.sh or newer)
  - m1qn3
 
@@ -83 +82 @@
 For Dakota to run, you will not need to remake PETSc and m1qn3, as long as you made them using the intel mpi and the mpi compilers, as described above. 
 
-In your `~/.cshrc`, change your loaded packages to remove the pkgsrc. Since pkgsrc loads an incompatible boost, it needs to be removed to build dakota:
+Dakota will require that you have a python that is of version python2. The easiest way to do this is to define an alias for python that calls `/usr/bin/python2` in your `~/.cshrc`:
 
 {{{
-#Packages
-module load comp-intel/2018.3.222
-module load mpi-intel/2018.3.222
+alias python '/usr/bin/python2'
 }}}
 
@@ -128 +125 @@
 }}}
 
-Note, if you would like the capabilities of pkgsrc/2020Q4, including updated svn, make sure that you build dakota without that package loaded.  Once you have ISSM compiled and installed with dakota, feel free to add back in to your `~/.cshrc`:
+Note, if you would like to use the python 3 version that loads in the environment, you will need to call `python3` to do so, as long as the python alias is set to python2.
 
-{{{
-#Packages
-module load pkgsrc/2020Q4
-}}}
 
 == pfe_settings.m ==
@@ -150 +143 @@
 use your username for the `login` and enter your code path and execution path. These settings will be picked up automatically by matlab when you do `md.cluster=pfe()`
 
-Make sure your module list includes scicon/app-tools, comp-intel/2018.3.222, and mpi-intel/2018.3.222. You can specify your own list of modules by adding to `pfe_settings.m`, for example:
+Make sure your module list includes scicon/app-tools, comp-intel/2018.3.222, and /nasa/intel/impi/2021.3/modulefiles/mpi/2021.3.0. You can specify your own list of modules by adding to `pfe_settings.m`, for example:
 
 {{{
-cluster.modules = {'comp-intel/2018.3.222' 'mpi-intel/2018.3.222' 'scicon/app-tools'};
+cluster.modules = {'comp-intel/2018.3.222' '/nasa/intel/impi/2021.3/modulefiles/mpi/2021.3.0' 'scicon/app-tools'};
 }}}