Access and Login
The Moonshot nodes are mostly integrated into the HorUS cluster. If you have HorUS access (you can find out how to get access here) you can also log into the Moonshot nodes.
The two login nodes have the designations
htc002 respectively, just like on the HorUS there is an allias
htcwhich will bring you onto one of the login nodes. You should use this alias whenever possible, since the load balancer will always bring you onto the less busy login node. Connection happens via
ssh just like on HorUS, by appending
.zimt.uni-siegen.de to the node name or the alias.
The remaining nodes
htc007 are compute nodes and are not directly accessible from the outside.
Another difference is the fact that the Moonshot nodes are not connected to the HorUS cluster’s Infiniband interconnect. File IO is therefore not as fast, even if you use workspaces.
In principle, all modules that ar einstalled on HorUS are also available on the HTC nodes. However, due to the different CPU architecture it is not guaranteed that a module works just because it is available.
Caution: ZIMT has not tested all HorUS modules on the HTC nodes and you should always conduct your own tests with a given module before you use it productively.
You can run compute jobs on the nodes
htc007 in the same way as on the HorUS: by queuing SLURM jobs in the
htc queue. Job and nodes status in the
htc queue can be monitored as usual with
sinfo, both from HorUS and from the HTC nodes. The individual SLURM commands are described here. The default and maximum walltime in the HTC queue are both set to 24 hours.
Caution: if you do not specify a queue (queue=partition in SLURM terminology), the job will be put into the default queue (
defq) and will therefore run on HorUS and not on the HTC nodes. You have to include the following line:
in your job script (or specify the
htc partition when calling
sbatch) if you want your job to run on the HTC nodes.
Can HTC jobs be queued from HorUS and vice versa?
Partially yes. You can queue jobs as long as the differences in the CPU architecture make no difference. In particular, ZIMT does not currently support cross-compiling.
For example, it should be easily possible to queue a Matlab job from HorUS into the HTC queue, because Matlab is installed on both. However, if you want to compile a C or Fortran program, this has to happen on the HTC front end (