Commit f15dc87c authored by David Hrbáč's avatar David Hrbáč

Markdown lint on you people...

parent f9bf8288
## Resources Allocation Policy
# Resources Allocation Policy
### Job queue policies
## 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.
### Queue 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/>
......
......@@ -59,7 +59,7 @@ local $
## Errata
Although we have taken every care to ensure the accuracy of the content, mistakes do happen.
Although we have taken every care to ensure the accuracy of the content, mistakes do happen.
If you find an inconsistency or error, please report it by visiting <http://support.it4i.cz/rt>, creating a new ticket, and entering the details.
By doing so, you can save other readers from frustration and help us improve.
We will fix the problem as soon as possible.
## Resources Allocation Policy
# Resources Allocation Policy
### Job queue policies
## 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:
......@@ -31,7 +31,7 @@ The resources are allocated to the job in a fair-share fashion, subject to const
!!! note
To access node with Xeon Phi co-processor user needs to specify that in [job submission select statement](job-submission-and-execution/).
### Queue 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/).
......@@ -39,7 +39,7 @@ Jobs that exceed the reserved wall-clock time (Req'd Time) get killed automatica
Salomon users may check current queue configuration at <https://extranet.it4i.cz/rsweb/salomon/queues>.
### Queue Status
## Queue Status
!!! note
Check the status of jobs, queues and compute nodes at [https://extranet.it4i.cz/rsweb/salomon/](https://extranet.it4i.cz/rsweb/salomon)
......
## Resource Accounting Policy
# Resource Accounting Policy
### Wall-clock Core-Hours WCH
## Wall-clock Core-Hours WCH
The wall-clock core-hours (WCH) are the basic metric of computer utilization time.
1 wall-clock core-hour is defined as 1 processor core allocated for 1 hour of wall-clock time. Allocating a full node (16 cores Anselm, 24 cores Salomon)
for 1 hour amounts to 16 wall-clock core-hours (Anselm) or 24 wall-clock core-hours (Salomon).
### Normalized Core-Hours NCH
## Normalized Core-Hours NCH
The resources subject to accounting are the normalized core-hours (NCH).
The normalized core-hours are obtained from WCH by applying a normalization factor:
......@@ -37,7 +37,7 @@ In future, the factors F will be updated, as new systems are installed. Factors
See examples in the [Job submission and execution](job-submission-and-execution/) section.
### Consumed Resources
## Consumed Resources
Check how many core-hours have been consumed. The command it4ifree is available on cluster login nodes.
......
......@@ -7,8 +7,8 @@ Conda as a package manager helps you find and install packages. If you need a pa
Conda treats Python the same as any other package, so it is easy to manage and update multiple installations.
Anaconda supports Python 2.7, 3.4, 3.5 and 3.6. The default is Python 2.7 or 3.6, depending on which installer you used:
* For the installers “Anaconda” and “Miniconda,” the default is 2.7.
* For the installers “Anaconda3” or “Miniconda3,” the default is 3.6.
* For the installers “Anaconda” and “Miniconda,” the default is 2.7.
* For the installers “Anaconda3” or “Miniconda3,” the default is 3.6.
## Conda on the IT4Innovations Clusters
......
......@@ -72,6 +72,7 @@ false
```
Show all files modified in last 5 days:
```csc
csharp> using System.IO;
csharp> from f in Directory.GetFiles ("mydirectory")
......
......@@ -12,35 +12,35 @@ $ ml av Tensorflow
Anselm provides beside others these three different TensorFlow modules:
* Tensorflow/1.1.0 (CPU only, not recommended), module built with:
* GCC/4.9.3
* Python/3.6.1
* GCC/4.9.3
* Python/3.6.1
* Tensorflow/1.1.0-CUDA-7.5.18-Python-3.6.1 (GPU enabled), module built with:
* GCC/4.9.3
* Python/3.6.1
* CUDA/7.5.18
* cuDNN/5.1-CUDA-7.5.18
* GCC/4.9.3
* Python/3.6.1
* CUDA/7.5.18
* cuDNN/5.1-CUDA-7.5.18
* Tensorflow/1.1.0-CUDA-8.0.44-Python-3.6.1 (GPU enabled), module built with:
* GCC/4.9.3
* Python/3.6.1
* CUDA/8.0.44
* cuDNN/5.1-CUDA-8.0.44
* GCC/4.9.3
* Python/3.6.1
* CUDA/8.0.44
* cuDNN/5.1-CUDA-8.0.44
## Salomon modules
Salomon provides beside others these three different TensorFlow modules:
* Tensorflow/1.1.0 (not recommended), module built with:
* GCC/4.9.3
* Python/3.6.1
* GCC/4.9.3
* Python/3.6.1
* Tensorflow/1.2.0-GCC-7.1.0-2.28 (default, recommended), module built with:
* TensorFlow 1.2 with SIMD support. TensorFlow build taking advantage of the Salomon CPU architecture.
* GCC/7.1.0-2.28
* Python/3.6.1
* protobuf/3.2.0-GCC-7.1.0-2.28-Python-3.6.1
* TensorFlow 1.2 with SIMD support. TensorFlow build taking advantage of the Salomon CPU architecture.
* GCC/7.1.0-2.28
* Python/3.6.1
* protobuf/3.2.0-GCC-7.1.0-2.28-Python-3.6.1
* Tensorflow/1.2.0-intel-2017.05-mkl (TensorFlow 1.2 with MKL support), module built with:
* icc/2017.4.196-GCC-7.1.0-2.28
* Python/3.6.1
* protobuf/3.2.0-GCC-7.1.0-2.28-Python-3.6.1
* icc/2017.4.196-GCC-7.1.0-2.28
* Python/3.6.1
* protobuf/3.2.0-GCC-7.1.0-2.28-Python-3.6.1
## TensorFlow application example
......
......@@ -239,7 +239,7 @@ $ spack edit git
```
!!! note
To change source link (ftp:// to http://) use `spack create URL -f` to regenerates rules.
To change source link (`ftp://` to `http://`) use `spack create URL -f` to regenerates rules.
#### **Example**
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment