Merge branch 'remove_home' into 'master'

Remove parts that say the home directory is not writeable from the worker nodes

See merge request !364

content/_index.md

@@ -36,15 +36,6 @@ are new to using HCC resources, Swan is the recommended cluster to use
 initially. Swan has 2 Intel Icelake CPUs (56 cores) per node, with 256GB RAM per
 node.
 
-**Important Notes**
-
--   The worker nodes cannot write to the `/home` directories. You must
-    use your `/work` directory for processing in your job. You may
-    access your work directory by using the command:
-{{< highlight bash >}}
-$ cd $WORK
-{{< /highlight >}}
-
 Resources
 ---------
 

content/applications/app_specific/bioinformatics_tools/alignment_tools/blast/running_blast_alignment.md

@@ -46,7 +46,6 @@ If you want to create and use a BLAST database that is not mentioned above, chec
 
 Basic SLURM example of nucleotide BLAST run against the non-redundant **nt** BLAST database with `8 CPUs` is provided below. When running BLAST alignment, it is recommended to first copy the query and database files to the **/scratch/** directory of the worker node. Moreover, the BLAST output is also saved in this directory (**/scratch/blastn_output.alignments**). After BLAST finishes, the output file is copied from the worker node to your current work directory.
 {{% notice info %}}
-**Please note that the worker nodes can not write to the */home/* directories and therefore you need to run your job from your */work/* directory.**
 **This example will first copy the database and your input file to faster local storage called "scratch", assuming that the input file exists in your current directory.  This can greatly improve performance!**
 {{% /notice %}}
 
@@ -86,7 +85,6 @@ The default BLAST output is in pairwise format. However, BLAST’s parameter **-
 
 Basic SLURM example of protein BLAST run against the non-redundant **nr **BLAST database with tabular output format and `8 CPUs` is shown below. Similarly as before, the query and database files are copied to the **/scratch/** directory. The BLAST output is also saved in this directory (**/scratch/blastx_output.alignments**). After BLAST finishes, the output file is copied from the worker node to your current work directory.
 {{% notice info %}}
-**Please note that the worker nodes can not write to the */home/* directories and therefore you need to run your job from your */work/* directory.**
 **This example will first copy the database and your input file to faster local storage called "scratch", assuming that the input file exists in your current directory. This can greatly improve performance!**
 {{% /notice %}}
 

content/submitting_jobs/submitting_htcondor_jobs.md

@@ -26,12 +26,6 @@ queue
 The above script will translate the condor submit file into a SLURM
 submit file, and execute the `test.sh` executable on a worker node. 
 
-{{% notice warning %}}
-The `/home` directories are read only on the worker nodes. You
-have to submit your jobs from the `/work` directory just as you would in
-SLURM.
-{{% /notice %}}
-
 ### Using Pegasus
 
 If you are using [Pegasus](http://pegasus.isi.edu),