Merge pull request #42 from mathiasbockwoldt/master

Fixed typo that caused wrong rendering of html

account/accounting.rst

@@ -19,15 +19,15 @@ Resource charging
 
 We charge for used resources, both cpu and memory.
 The accounting system charges for used processor equivalents (PE)
-times used walltime, so if you ask for more than (total memory pr. node)/(total cores pr. node)  
-- in the example below 32GB/20cores = 1.6 GB. 
+times used walltime, so if you ask for more than (total memory pr. node)/(total cores pr. node)
+- in the example below 32GB/20cores = 1.6 GB.
 
 The concept of PE defines a processor equivalent as the resource unit 1 core and 1 unit of memory.
-For a node with 2 GB og memory pr core, i.e. 32 GB of memory and 16 cores - 1 PE equals to 1 core and 
-2GB of memory. Currently there is no common definition on the memory unit, other than the one specified 
+For a node with 2 GB og memory pr core, i.e. 32 GB of memory and 16 cores - 1 PE equals to 1 core and
+2GB of memory. Currently there is no common definition on the memory unit, other than the one specified
 above.
 
-The best way to explain the concept of PE is by example: 
+The best way to explain the concept of PE is by example:
 Assume that you have a node with 20 cpu-cores and 32 GB memory::
 
     if you ask for less than 1.6GB memory per core then PE will equal the cpu count.
@@ -75,4 +75,5 @@ You can view the accounting history of your projects using::
     gstatement --hours --summarize -s YYYY-MM-DD -e YYYY-MM-DD -p nnXXXXk
 
 for more detail see::
+
     gstatement --man

applications/chemistry/VASP/VASP.rst

@@ -42,10 +42,9 @@ License and access policy
 
 The VASP license is proprietary and commercial. It is based on group license policy, and for NOTUR systems VASP packages falls in the "bring your own license" category. See :ref:`About_licenses`.
 
-
 The Vasp program is not distributed via site licences. However, HPC-staff in NOTUR have access to the VASP code to be able to support any research groups that have a valid VASP license.
 
-VASP is a commercial software package that requires a license for all who wants to run on Stallo. To get access you would need to prove that the group you are a member of holds a valid licence; a representative for the research group needs to contact VASP and ask for an aknowledgement of you connection to the license. A VASP representative sends this acknowledgement to us. Then your name is put into the VASP group, granting you access to the VASP 5 release of VASP on Stallo.
+VASP is a commercial software package that requires a license for all who wants to run on Stallo. To get access you would need to prove that the group you are a member of holds a valid licence; a representative for the research group needs to contact Dr. Doris Vogtenhuber (doris.vogtenhuber@univie.ac.at) from the VASP team and ask for an aknowledgement of you connection to the license. A VASP representative will send this acknowledgement to us. Then your name is put into the VASP group, granting you access to the VASP 5 release of VASP on Stallo.
 
 The support people in NOTUR, do not provide trouble shooting guides anymore, due to a national agreement that it is better for the community as a whole to add to the community info/knowledge pool where such is made available. Also, HPC staff from UiT does not provide any support to VASP 4 anymore, basically due to age of the code.
 

applications/chemistry/files/job_vasp.sh

@@ -24,6 +24,13 @@
 ######################################
 # Section for defining job variables and settings:
 
+# When you use this test script, make sure, your folder structure is as follows:
+# ./job_vasp.sh
+# ./CeO2job/INCAR
+# ./CeO2job/KPOINTS
+# ./CeO2job/POTCAR
+# ./CeO2job/POSCAR
+
 proj=CeO2job # Name of job folder
 input=$(ls ${proj}/{INCAR,KPOINTS,POTCAR,POSCAR}) # Input files from job folder