Gajdusek cleaning

docs.it4i/anselm/resources-allocation-policy.md

-# Resources Allocation Policy
+## Resources Allocation Policy
 
-## Introduction
+### Job queue policies
 
 The resources are allocated to the job in a fair-share fashion, subject to constraints set by the queue and resources available to the Project. The Fair-share at Anselm ensures that individual users may consume approximately equal amount of resources per week. Detailed information in the [Job scheduling](job-priority/) section. The resources are accessible via several queues for queueing the jobs. The queues provide prioritized and exclusive access to the computational resources. Following table provides the queue partitioning overview:
 
@@ -27,7 +27,7 @@ The resources are allocated to the job in a fair-share fashion, subject to const
 * **qnvidia**, qmic, qfat, the Dedicated queues: The queue qnvidia is dedicated to access the Nvidia accelerated nodes, the qmic to access MIC nodes and qfat the Fat nodes. It is required that active project with nonzero remaining resources is specified to enter these queues. 23 nvidia, 4 mic and 2 fat nodes are included. Full nodes, 16 cores per node are allocated. The queues run with very high priority, the jobs will be scheduled before the jobs coming from the qexp queue. An PI needs explicitly ask [support](https://support.it4i.cz/rt/) for authorization to enter the dedicated queues for all users associated to her/his Project.
 * **qfree**, The Free resource queue: The queue qfree is intended for utilization of free resources, after a Project exhausted all its allocated computational resources (Does not apply to DD projects by default. DD projects have to request for persmission on qfree after exhaustion of computational resources.). It is required that active project is specified to enter the queue, however no remaining resources are required. Consumed resources will be accounted to the Project. Only 178 nodes without accelerator may be accessed from this queue. Full nodes, 16 cores per node are allocated. The queue runs with very low priority and no special authorization is required to use it. The maximum runtime in qfree is 12 hours.
 
-### Notes
+### Queue notes
 
 The job wall clock time defaults to **half the maximum time**, see table above. Longer wall time limits can be  [set manually, see examples](job-submission-and-execution/).
 
@@ -35,7 +35,7 @@ Jobs that exceed the reserved wall clock time (Req'd Time) get killed automatica
 
 Anselm users may check current queue configuration at <https://extranet.it4i.cz/anselm/queues>.
 
-### Queue Status
+### Queue status
 
 !!! tip
     Check the status of jobs, queues and compute nodes at <https://extranet.it4i.cz/anselm/>
@@ -106,24 +106,8 @@ Options:
   --incl-finished       Include finished jobs
 ```
 
-## Resources Accounting Policy
+---8<--- "resource_accounting.md"
 
-### Core-Hours
 
-The resources that are currently subject to accounting are the core-hours. The core-hours are accounted on the wall clock basis. The accounting runs whenever the computational cores are allocated or blocked via the PBS Pro workload manager (the qsub command), regardless of whether the cores are actually used for any calculation. 1 core-hour is defined as 1 processor core allocated for 1 hour of wall clock time. Allocating a full node (16 cores) for 1 hour accounts to 16 core-hours. See example in the  [Job submission and execution](job-submission-and-execution/) section.
+---8<--- "mathjax.md"
 
-### Check Consumed Resources
-
-!!! note
-    The **it4ifree** command is a part of it4i.portal.clients package, located here: <https://pypi.python.org/pypi/it4i.portal.clients>
-
-User may check at any time, how many core-hours have been consumed by himself/herself and his/her projects. The command is available on clusters' login nodes.
-
-```console
-$ it4ifree
-Password:
-     PID    Total   Used   ...by me Free
-   -------- ------- ------ -------- -------
-   OPEN-0-0 1500000 400644   225265 1099356
-   DD-13-1    10000   2606     2606    7394
-```