Improve ares guide

[lukemartinlogan]

• Add section telling people to upload their public SSH key to github for remote development
• List some rules about the master node
  • Avoid running code -- except sometimes compilation.
  • Primarily use for allocating jobs
• Add specific salloc commands for people to copy-paste from
  • salloc -N 4 -p compute allocates 4 compute nodes
  • salloc -w ares-comp-[08-10] allocates node 8-10.
  • squeue shows your current allocation
  • ${SLURM_JOB_NODELIST} for batch-based scheduling
• Add section for vscode. Remote debugging ares-comp-21 over ssh in vscode could be done with this ssh config param:

Host ares-comp
  HostName ares-comp-21
  User llogan
  ProxyJump ares.cs.iit.edu

[nrj5k]

Hi,

So, I have some questions regarding some points that need to be added to the guide. I would like some clarification about the intent of these points, as from my perspective, some of them exist already or is unclear about why it should be there. Understanding this would help me figure out why my initial version of the documentation was lacking (wrt details that are already present) and also write better, more thorough documentation in the future.

List some rules about the master node
Avoid running code -- except sometimes compilation.
Primarily use for allocating jobs

This already exists in the user guide and briefly in the FAQ as well.

Add specific salloc commands for people to copy-paste from
salloc -N 4 -p compute allocates 4 compute nodes
salloc -w ares-comp-[08-10] allocates node 8-10.
squeue shows your current allocation

This exists in the FAQ.
Though this section could use better formatting now that I look at it again.

Add section telling people to upload their public SSH key to github for remote development

Why should this be in the User Guide? As to me this is more about using GitHub, I would appreciate some clarification here.

The $SLURM_JOB_NODELIST and the ProxyJump are great points, and it will be added to the documentation.