Updated staff info. A bit sad to remove Elenas name.

applications/physics/Star-CCM+/job_star2.sh

@@ -0,0 +1,84 @@
+#!/bin/bash -l
+
+###################################################
+#
+#  Star CCM+ job example script
+#
+###################################################
+#
+#SBATCH --job-name=StarCCM+ex
+#Running on default account, thus commented out the account giving comment:
+##SBATCH --account=
+# Stallo has 16 or 20 cores/node and therefore we take
+# a number that is divisible by both:
+#SBATCH --ntasks=80
+#Run for 2 Hrs (format is day-hrs:mins:secs)
+#SBATCH --time=0-02:00:00
+# In slurm, memory is hardlimit. Be carefull!
+#SBATCH --mem-per-cpu=1500MB
+# Normal partition should do it
+#SBATCH --partition=normal
+#
+
+##############
+# Setting software environment for STAR CCM+
+
+module purge
+module load STAR-CCM+/STAR-CCM+12.02.010
+
+##############
+# Setting up real time license on demand.
+# Users must specify their <licensekey>
+#
+
+#export LM_PROJECT=<licensekey>
+export LM_PROJECT=KZBaPT+lhIWMrpIo2vgCyA
+export CDLMD_LICENSE_FILE=1999@flex.cd-adapco.com
+
+#############
+Setting up work environment and preparing for job to run:
+
+# Specifying project name:
+case=$SLURM_JOB_NAME
+#Setting home for mpi:
+export INTEL_MPI_HOME=$EBROOTIIMPI
+# Moving to submit folder: 
+export submitdir=$SLURM_SUBMIT_DIR
+cd $submitdir
+# Definining, and creating if necessary, a temporary work directory:
+export tempdir=/global/work/${USER}/starccm/${SLURM_JOBID}
+mkdir -p $tempdir
+# Copy inputfile and move to working directory
+cp $case.sim $tempdir
+cd $tempdir
+# Defining number of mpi tasks to feed the mpi engine:
+procs=$(echo $SLURM_NPROCS)
+
+###############
+# Starting the program:
+
+starccm+ -bs SLURM -batch -power -mpi intel -pio -machinefile $SLURM_JOB_NODELIST -np $procs $case.sim
+
+# Preferable options: -mesa.
+
+# This should work:
+#srun starccm+ -power -pio $case.sim
+# Or this:
+#starccm+ -bs SLURM -power -pio $case.sim
+# Worst case scenario:
+#starccm+ -bs SLURM -batch -power -mpi intel -pio -machinefile $SLURM_JOB_NODELIST -np $procs $case.sim
+
+# Investigate potentially other files to keep:
+echo `pwd`
+echo `ls -ltr`
+
+# ALLWAYS clean up after yourself. Please do uncomment the following line
+#cd $submitdir
+#rm  $tempdir/*
+#rmdir $tempdir
+
+
+echo "Job finished at"
+date
+################### Job Ended ###################
+exit 0

help/staff.rst

@@ -60,6 +60,7 @@ Our team
 * `Roy Dragseth <https://uit.no/om/enhet/ansatte/person?p_document_id=42529&p_dimension_id=88223>`_
 * `Steinar Henden <https://uit.no/om/enhet/ansatte/person?p_document_id=43772&p_dimension_id=88223>`_
 * `Dan Jonsson <https://uit.no/om/enhet/ansatte/person?p_document_id=44087&p_dimension_id=88223>`_
-* `Elena Malkin <https://uit.no/om/enhet/ansatte/person?p_document_id=335339&p_dimension_id=88223>`_
+* `Ilia Zhakun <https://uit.no/om/enhet/ansatte/person?p_document_id=522532&p_dimension_id=88223>`_
 * `Espen Tangen <https://uit.no/om/enhet/ansatte/person?p_document_id=43808&p_dimension_id=88223>`_
 * `Giacomo Tartari <https://uit.no/om/enhet/ansatte/person?p_document_id=197816&p_dimension_id=88139>`_
+* `Stig Rune Jensen <https://uit.no/om/enhet/ansatte/person?p_document_id=168046&p_dimension_id=88139>`_

index.rst

@@ -81,7 +81,6 @@ HPC-UiT Services User Documentation
 
    software/applications.rst
    software/modules.rst
-   software/new_modules.rst
 
 
 .. toctree::

news/new_sw.rst

@@ -62,5 +62,3 @@ To solve this you need to remove your old collections and create them again. We
 If you are already using "mod_setup.sh" or "/home/easybuild/"
 ------------------------------------------------------------
 If you have already started using the new modules by loading the "notur" module and sourcing "mod_setup.sh", simply remove these two steps and continue working as normal. The same goes for any references to /home/easybuild/. We kept these options working for now to reduce the number of potentially crashing jobs, but we plan to remove them in the near future, so we recommend removing those lines from any new jobs you launch. You do not need the module "varset" any more, StdEnv has taken over its functionality. If the only reason you were using the "notur" module was to access the newer installations, you do not need it either. If you were using the "notur" module to run ADF or other software, then you still need to continue using it.
-
-For information about how to reach the "new" packages, before we make this scheme default, see in the software section :ref:`new_scheme`.

software/modules.rst

@@ -1,22 +1,21 @@
-.. _old_scheme:
+.. _module_scheme:
 
-Old Scheme Modules
-===================
+Software Module Scheme
+=======================
 
-Software installations on the clusters span many applications, and many
-different version numbers of the same application. It is not possible (nor
+Since a HPC cluster is shared among many users, and also holds a significant size in contrast to most desktop compute machinery around, the amount of installed software spans many applications in many different versions and quite a few of them are installed typically non-standard places for easier maintenance (for admin crew), practical and security reasons. It is not possible (nor
 desirable) to use them all at the same time, since different versions of the
-same application may conflict with each other. In order to simplify the control
-of which application versions are available in a specific session, there is a
-system for loading and unloading 'modules' which activate and deactivate the
-relevant parts of your user session.
+same application may conflict with each other. Therefore, it is practical to provide the production environment for a given application outside of the application itself. This is done using a set of instructions and variable settings that are specific for the given application called an application module. This also simplifies control of which application versions are available in a specific session. 
+
+We are also using the Easybuild system for installing software on Stallo (see https://easybuilders.github.io/easybuild/). 
+
 
 The main command for using this system is the *module* command. You can find a
 list of all its options by typing::
 
   module --help
 
-Below we listed the most commonly used options.
+We use the lmod module system; for more info see http://lmod.readthedocs.io/en/latest/ on Stallo. Below we listed the most commonly used options, but also feel free to ivestigate options in this toolset more thoroughly on developers site. 
 
 
 Which modules are currently loaded?
@@ -55,7 +54,7 @@ In order to make, for instance, the NetCDF library available issue the command::
 This will load the default NetCDF version. To load a specific version,
 just include the version after a slash::
 
-  module load netCDF/3.6.2
+  module load netCDF/4.3.3.1-intel-2016a
 
 
 
@@ -84,6 +83,9 @@ How do I switch to a different version of a module?
 
 Switching to another version is similar to loading a specific version.  As an
 example, if you want to switch from the default (current) Intel compilers
-version to version 14.0, type::
+version to version 2016b (aka 2016.3), type::
+
+  module switch intel intel/2016b 
+
 
-  module switch intel intel/14.0
+**Beware: by default on Stallo, you are not able to have two conflicting modules - f.e. openmpi and impi \ - loaded at the same time.** This is only partially true for these new packages. With the new packages it \ is also more common that when you load one package it will automatically load several other packages that \ it needs to function. We recommend doing ml after every load and unloading any conflicting packages.