| Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision |
| software:java:caviness [2020-03-18 17:36] – anita | software:java:caviness [2021-01-28 09:39] – anita |
|---|
| Check the version of the java compiler and java available on Caviness by using | Check the version of the java compiler and java available on Caviness by using |
| |
| <code> | <code bash> |
| $ javac -version | $ javac -version |
| $ java -version | $ java -version |
| and determine if this is acceptable for your java application to compile and create the ''HelloWorld.class'' file. The following example is based on the user ''traine'' in workgroup ''it_css'' on Caviness utilizing the directory ''/work/it_css/traine/java'' to store all the files associated with this example, and compiling and testing ''HellowWorld'' on the login (head) node. | and determine if this is acceptable for your java application to compile and create the ''HelloWorld.class'' file. The following example is based on the user ''traine'' in workgroup ''it_css'' on Caviness utilizing the directory ''/work/it_css/traine/java'' to store all the files associated with this example, and compiling and testing ''HellowWorld'' on the login (head) node. |
| |
| <code> | <code bash> |
| [traine@login00 ~]$ workgroup -g it_css | [traine@login00 ~]$ workgroup -g it_css |
| [(it_css:traine)@login00 ~]$ javac -version | [(it_css:traine)@login00 ~]$ javac -version |
| If you want to compile on a compute node, use ''salloc --partition=devel'' to make sure you are allocated a compute node with the development tools, libraries, etc. which are needed for compilers. It is a good idea to use a compute node especially for lengthy compiles or those requiring multiple threads to reduce the compilation time. The following example is the same as above except the compile and test ''HelloWorld'' is done on a compute node ''r00n56'' based on the job allocated from ''salloc --partition=devel''. | If you want to compile on a compute node, use ''salloc --partition=devel'' to make sure you are allocated a compute node with the development tools, libraries, etc. which are needed for compilers. It is a good idea to use a compute node especially for lengthy compiles or those requiring multiple threads to reduce the compilation time. The following example is the same as above except the compile and test ''HelloWorld'' is done on a compute node ''r00n56'' based on the job allocated from ''salloc --partition=devel''. |
| |
| <code> | <code bash> |
| [traine@login00 ~]$ workgroup -g it_css | [traine@login00 ~]$ workgroup -g it_css |
| [(it_css:traine)@login00 ~]$ salloc --partition=devel | [(it_css:traine)@login00 ~]$ salloc --partition=devel |
| Now submit the job using ''sbatch submit.qs'' on the head node after you make sure you are in your workgroup. The example below shows the output from the job submission and how to view the results of the job run. | Now submit the job using ''sbatch submit.qs'' on the head node after you make sure you are in your workgroup. The example below shows the output from the job submission and how to view the results of the job run. |
| |
| <code> | <code bash> |
| [traine@login00 ~]$ workgroup -g it_css | [traine@login00 ~]$ workgroup -g it_css |
| [(it_css:traine)@login00 java]$ sbatch submit.qs | [(it_css:traine)@login00 java]$ sbatch submit.qs |
| </code> | </code> |
| |
| <note tip>Please review the templates for job submission scripts in ''/opt/templates'' on Caviness. There are ''README.md'' files in each subdirectory to explain the use of these templates. If you do not specify any resources, by default you will get the stahdard partition, with 1 core and 1GB of memory (a simple serial job) and 20 minutes runtime on Caviness.</note> | <note tip>Please review the templates for job submission scripts in ''/opt/templates'' on Caviness. There are ''README.md'' files in each subdirectory to explain the use of these templates. If you do not specify any resources, by default you will get the standard partition, with 1 core and 1GB of memory (a simple serial job) and 20 minutes runtime on Caviness.</note> |
| |