Merge branch 'master' into ngc-apptainer

help/writing-support-requests.md

@@ -25,9 +25,9 @@ way, that's almost always how we start to research issues too!
 
 Your subject line should be descriptive. "Problem on Star" is not a
 good subject line since it could be valid for basically every support
-E-mail we get. The support staff is a team. The subjects are the first
-thing that we see. We would like to be able to classify E-mails according
-to subjects before even opening the E-mail.
+Email we get. The support staff is a team. The subjects are the first
+thing that we see. We would like to be able to classify Email according
+to subjects before even opening the Email.
 
 ## Include the actual commands and error messages
 
@@ -45,7 +45,7 @@ down our research on your problem.
 
 Do not send support requests by replying to unrelated issues. Every
 issue gets a number and this is the number that you see in the subject
-line. Replying to unrelated issues means that your E-mail gets filed
+line. Replying to unrelated issues means that your Email gets filed
 under the wrong thread and risks being overlooked.
 
 ## The XY problem
@@ -79,7 +79,7 @@ nodes". The request then does not mention whether it worked on one node
 or on one core or whether it never worked and that this was the first
 attempt. Perhaps the problem has even nothing to do with one or two
 nodes. In order to better isolate the problem and avoid wasting time
-with many back and forth E-mails, please tell us what actually worked so
+with many back and forth Emails, please tell us what actually worked so
 far. Tell us what you have tried to isolate the problem. This requires
 some effort from you but this is what we expect from you.
 

jobs/submitting-jobs.md

@@ -160,7 +160,7 @@ This option requests 4 GB of memory per allocated CPU.
 --mail-user=your_email@example.com
 ```
 
-This configuration sends an email to the specified address at the start, completion, and failure of the job.
+This configuration sends an Email to the specified address at the start, completion, and failure of the job.
 
 ### Interactive Job Submission
 

quickstart/about-star.md

@@ -14,7 +14,6 @@ Users run many different applications on the cluster based on their needs, such
 
 Containerization is also increasingly popular in HPC it provides isolated environments that allow for the reuse of images for better reproducibility and software portability without the performance impact of other methods or the hastle of manualy installing dependencies. Containers are run using Apptainer (formerly Singularity), a containerization platform similar to Docker with the major difference that it runs under user privileges instead of `root`. Users can deploy images from NGC (NVIDIA GPU Cloud), which provides access to a wide array of pre-built images with GPU-optimized software for diverse applications. Leveraging container images can save a lot of time as users don’t need to set up the software applications from scratch and can just pull and use the NGC images with Apptainer.
 
-
 ## Hardware
 
 ### Login Node

quickstart/quickstart.md

@@ -35,7 +35,7 @@ To get an account on Star, you need to complete out the registration form at [St
     visitor/guest).
 -   Your mobile phone number. This is necessary for recovery of
     passwords.
--   Your institutional mail address (i.e. your work email at the
+-   Your institutional mail address (i.e. your work Email at the
     research institution to which you belong)
 -   The name and address of the instruction you belong to; also
     including name of the center, institute etc.
@@ -65,7 +65,17 @@ Submit the above information through the online registration form.
 
 ## Login node
 
-Access to the cluster is provided through SSH access to the login node. The login node serves as the gateway or entry point to the cluster. Note that most software tools are not available on the login node and it is not for prototyping, building software, or running computationally intensive tasks itself. Instead, the login node is specifically for accessing the cluster and performing only very basic tasks, such as copying and moving files, submitting jobs, and checking the status of existing jobs. For development tasks, you would use one of the development nodes, which are accessed the same way as the large compute nodes. The compute nodes are where all the actual computational work is performed. They are accessed by launching jobs through Slurm with `sbatch` or `srun`.
+### About the login node (named Binary)
+
+The login node serves as the gateway or entry point to the cluster. Note that most software tools are not available on the login node and it is not for prototyping, building software, or running computationally intensive tasks itself. Instead, the login node is specifically for accessing the cluster and performing only very basic tasks, such as copying and moving files, submitting jobs, and checking the status of existing jobs. For development tasks, you would use one of the development nodes, which are accessed the same way as the large compute nodes. The compute nodes are where all the actual computational work is performed. They are accessed by launching jobs through Slurm with `sbatch` or `srun`.
+
+### Connection and credentials
+
+Access to the cluster is provided through SSH to the login node. Upon your account's creation, you can access the login node using the address provided in your welcome Email.
+
+If you have existing Linux lab credentials, use them to log in. Otherwise, login credentials will be provided to you.
+
+Additionally, Binary provides access to your Linux lab files, **But not that** Binary is **not** just another Linux lab machine. It simply provides mutual features (e.g., credentials) for convenience.
 
 ## Scheduler policies
 
@@ -79,7 +89,7 @@ Storage quotas and usage limits are put in place to ensure fair use and equitabl
 
 It is important to know where to store different types of data (such as large datasets or temporary files).
 
-Your home directory provides a limited amount of storage for scripts, source code, and small datasets.
+Your home directory (`/home/your_username`) provides a limited amount of storage for scripts, source code, and small datasets.
 
 Project-specific directories may be created upon request for shared storage among multiple accounts.