User Tools

Site Tools


info:coral

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
info:coral [2021/06/17 08:35]
mjm519 [Navigation]
info:coral [2021/11/12 13:33]
mjm519 [Navigation]
Line 20: Line 20:
 <​p>​Shark server manages various software licenses including AMPL license.</​p>​ <​p>​Shark server manages various software licenses including AMPL license.</​p>​
 <​h4>​polyps.ie.lehigh.edu</​h4>​ <​h4>​polyps.ie.lehigh.edu</​h4>​
-<​p>​Polyps is COR@L Lab’s cluster composed of 16 nodes (polyp1-polyp15,​ polyp30). It is our heavy duty cluster. Polyps has <a href="​http://​www.adaptivecomputing.com/​products/​torque"​ target="​_parent">​Torque</​a>​ installed as a job scheduler. Torque aims to maximize resource utilization and high throughput by scheduling jobs submitted by users and allocating resources (CPU, memory) of Polyps to them. For a brief introudction ​to Torque see Software section. Long lasting experiments should be submitted to polyps through Torque. You can also check the load of Polyp nodes from <a href="​http://​polyps.ie.lehigh.edu/​ganglia"​ target="​_parent">​ganglia</​a>​ web interface.</​p>​+<​p>​Polyps is COR@L Lab’s cluster composed of 16 nodes (polyp1-polyp15,​ polyp30). It is our heavy duty cluster. Polyps has <a href="​http://​www.adaptivecomputing.com/​products/​torque"​ target="​_parent">​Torque</​a>​ installed as a job scheduler. Torque aims to maximize resource utilization and high throughput by scheduling jobs submitted by users and allocating resources (CPU, memory) of Polyps to them. For a brief introduction ​to Torque see Software section. Long lasting experiments should be submitted to polyps through Torque. You can also check the load of Polyp nodes from <a href="​http://​polyps.ie.lehigh.edu/​ganglia"​ target="​_parent">​ganglia</​a>​ web interface.</​p>​
 <​p>​You can check hardware section on COR@L website for more technical information about servers.</​p>​ <​p>​You can check hardware section on COR@L website for more technical information about servers.</​p>​
 <​h3>​Personal Websites</​h3>​ <​h3>​Personal Websites</​h3>​
Line 28: Line 28:
 <​p>​All servers run Debian 8.10 Jessie.</​p>​ <​p>​All servers run Debian 8.10 Jessie.</​p>​
 <​h4>​Programming Languages, Compilers and Other Developer Tools</​h4>​ <​h4>​Programming Languages, Compilers and Other Developer Tools</​h4>​
-<p>We have C, C++, Fortran compilers available through GCC 4.7.2. GCC also implements shared memory parallel computing with OPENMP 3.1 standard. You can use GCC for your shared memory parallel computations on any polyp node. We also have MPICH2 implementation of MPI distibuted ​parallel computing standard available on polyps.</​p>​+<p>We have C, C++, Fortran compilers available through GCC 4.7.2. GCC also implements shared memory parallel computing with OPENMP 3.1 standard. You can use GCC for your shared memory parallel computations on any polyp node. We also have MPICH2 implementation of MPI distributed ​parallel computing standard available on polyps.</​p>​
 <​p>​Python 2.7 is installed on Polyps.</​p>​ <​p>​Python 2.7 is installed on Polyps.</​p>​
 <p>We have GNU Debugger (GDB) for debugging. Emacs and Vi is available as editors. Emacs comes with C/C++ and Python modes. We also have GNU make installed. Subversion and trac are also available. You can use your home directory and shark for setting Subversion repositories.</​p>​ <p>We have GNU Debugger (GDB) for debugging. Emacs and Vi is available as editors. Emacs comes with C/C++ and Python modes. We also have GNU make installed. Subversion and trac are also available. You can use your home directory and shark for setting Subversion repositories.</​p>​
Line 57: Line 57:
 <​li>​Be very careful with experiments you are conducting. Make sure that your experiments do not write large output files or extremely many of them (like hundred thousands). Keep your output files reasonable. Try to anticipate the output before you run your code.</​li>​ <​li>​Be very careful with experiments you are conducting. Make sure that your experiments do not write large output files or extremely many of them (like hundred thousands). Keep your output files reasonable. Try to anticipate the output before you run your code.</​li>​
 <​li>​Keep an eye on your processes after you started them. Act if something seems wrong.</​li>​ <​li>​Keep an eye on your processes after you started them. Act if something seems wrong.</​li>​
-<​li>​Do not forget to terminate processes that are not usefull ​or will not yield results.</​li>​+<​li>​Do not forget to terminate processes that are not useful ​or will not yield results.</​li>​
 <​li>​Keep an eye on resource use of your processes (CPU, memory etc.). If it uses excessive memory and starts using swap think about terminating it, if it is not reasonable to let it run then terminate it.</​li>​ <​li>​Keep an eye on resource use of your processes (CPU, memory etc.). If it uses excessive memory and starts using swap think about terminating it, if it is not reasonable to let it run then terminate it.</​li>​
 <​li>​Choose a secure password.</​li>​ <​li>​Choose a secure password.</​li>​
-<​li>​Be careful with your wordpress ​webpage. Do not leave comments section on. We get lots of spams if they leaved open.</​li>​+<​li>​Be careful with your Wordpress ​webpage. Do not leave comments section on. We get lots of spams if they leaved open.</​li>​
 <​li>​Your files and user account will not be guaranteed to exist after 6 months of your graduation. We will keep it for 6 months for you to copy your files. After six months we will remove it.</​li>​ <​li>​Your files and user account will not be guaranteed to exist after 6 months of your graduation. We will keep it for 6 months for you to copy your files. After six months we will remove it.</​li>​
 <​li>​There are two restrictions on processes in polyp1. First restriction is that a process is allowed to run only for 300 CPU time minutes. The second one is a process can use at most 10 Gb of memory. All long lasting experiments should be conducted through condor. You can see some guiding examples at directory “/​scratch/​coral_introduction” in polyp1. There are no restrictions in polyp2-12, they are only bounded by the hardware installed.</​li>​ <​li>​There are two restrictions on processes in polyp1. First restriction is that a process is allowed to run only for 300 CPU time minutes. The second one is a process can use at most 10 Gb of memory. All long lasting experiments should be conducted through condor. You can see some guiding examples at directory “/​scratch/​coral_introduction” in polyp1. There are no restrictions in polyp2-12, they are only bounded by the hardware installed.</​li>​
info/coral.txt · Last modified: 2021/11/12 13:55 by mjm519