From 72909bb98143ba26326513abadf3c60154e9580b Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Thu, 1 Jul 2021 14:46:47 +0200
Subject: [PATCH] Move to archive
---
.../docs/{jobs => archive}/WindowsBatch.md | 38 +++++++------------
1 file changed, 14 insertions(+), 24 deletions(-)
rename doc.zih.tu-dresden.de/docs/{jobs => archive}/WindowsBatch.md (78%)
diff --git a/doc.zih.tu-dresden.de/docs/jobs/WindowsBatch.md b/doc.zih.tu-dresden.de/docs/archive/WindowsBatch.md
similarity index 78%
rename from doc.zih.tu-dresden.de/docs/jobs/WindowsBatch.md
rename to doc.zih.tu-dresden.de/docs/archive/WindowsBatch.md
index 085879892..ab82da6f6 100644
--- a/doc.zih.tu-dresden.de/docs/jobs/WindowsBatch.md
+++ b/doc.zih.tu-dresden.de/docs/archive/WindowsBatch.md
@@ -1,10 +1,10 @@
-## Batch System on the Windows HPC Server
+# Batch System on the Windows HPC Server
The graphical user interface to the Windows batch system is the HPC Job
Manager. You can find this resource under Start -> Programs -> Microsoft
HPC Pack -> HPC Job Manager.
-### Job Submission
+## Job Submission
To create a new job click at one of the job dialog items in the Actions
submenu Job Submission and specify your job requirements in the job
@@ -13,7 +13,7 @@ dialog.
It is advisable to give your job an unique name for distinguishing
reasons during the job monitoring phase.
-#### Job Types
+### Job Types
- **Job**: The Job is the convenient way to create a batch job where
you want to specify all job requirements in detail. It is also
@@ -21,16 +21,10 @@ reasons during the job monitoring phase.
dependencies between your tasks, e.g. task b should only be started
if task a has finished you can specify these dependencies in the
submenu item task list in the job dialog.
-
-<!-- -->
-
- **Single-Task Job**: The Single-Task Job is the easiest way to
create a batch job that consists only of one task. In addition you
can specify the number of cores that should be used, the working
directory and job input and output files.
-
-<!-- -->
-
- **Parametric Sweep Job**: The Parametric Sweep Job allows the user
to create a sweep job where the tasks only differ in one input
parameter. For this parameter the user can specify the start, end
@@ -38,23 +32,21 @@ reasons during the job monitoring phase.
of (end-start)/increment individual task, which will be placed on
all free cores of the cluster.
-#### Working Directories
+### Working Directories
-- `C:\htitan\<LoginName>`
-- `C:\titan\HOME_(TITAN)\<LoginName>`
-- `\\titan\hpcms-files\HOME_(TITAN)\<LoginName>`
-- `\\hpcms\hpcms-files\HOME_(TITAN)\<LoginName>`
-- `Z:\HOME_(TITAN)\<LoginName>` (only available at login node)
+- `C:\htitan\<LoginName>`
+- `C:\titan\HOME_(TITAN)\<LoginName>`
+- `\\titan\hpcms-files\HOME_(TITAN)\<LoginName>`
+- `\\hpcms\hpcms-files\HOME_(TITAN)\<LoginName>`
+- `Z:\HOME_(TITAN)\<LoginName>` (only available at login node)
### Job Queues
-The queues are named job templates and can be chosen in the job
-submission dialog.
+The queues are named job templates and can be chosen in the job submission dialog.
-#### Titan
+### Titan
-At the moment there are two queues both without a runtime and/or core
-limitation.
+At the moment there are two queues both without a runtime and/or core limitation.
| Batch Queue | Admitted Users | Available CPUs | Default Runtime | Max. Runtime |
|:---------------|:-----------------|:------------------|:----------------|:-------------|
@@ -63,7 +55,5 @@ limitation.
### Job Monitoring
-The status of the jobs is visible via the Job Management submenu. Via
-the context menu more detailed information of a job is available.
-
-- Set DENYTOPICVIEW = WikiGuest
+The status of the jobs is visible via the Job Management submenu. Via the context menu more detailed
+information of a job is available.
--
GitLab