about_the_class:about_the_class
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
about_the_class:about_the_class [2015/07/15 18:27] ceisenhart |
about_the_class:about_the_class [2015/07/15 18:34] ceisenhart |
||
|---|---|---|---|
| Line 23: | Line 23: | ||
| ==== Computer servers ==== | ==== Computer servers ==== | ||
| + | ==CampusRocks== | ||
| The servers and resources that have been used so far in the project. The most universal resource is UCSC's [[https://support.soe.ucsc.edu/craigslist | campusrocks server]], which requires a UCSC Cruz Blue ID and password to login. | The servers and resources that have been used so far in the project. The most universal resource is UCSC's [[https://support.soe.ucsc.edu/craigslist | campusrocks server]], which requires a UCSC Cruz Blue ID and password to login. | ||
| * [[computer_resources:campusrocks|Complete guide to campusRocks and SGE]] | * [[computer_resources:campusrocks|Complete guide to campusRocks and SGE]] | ||
| + | |||
| + | **Note that this is a computer cluster!** When you log in you will be on the 'head' node, this node is not meant for running programs! If you try and run programs on the head node the system administration will kill your program and send you an angry email. To run programs you must use the Sun Grid Engine (SGE). | ||
| + | |||
| + | The SGE takes in very simple shell scripts and assigns them to a non-head node in the cluster. You can provide commands when you submit the shell scripts (request a bigger node, parallelize across multiple nodes, etc). As the scripts are submitted they are queued, if there is heavy usage on the server your script may not run immediately. | ||
| + | |||
| + | ==Edser== | ||
| During the Spring 2015 [[https://www.soe.ucsc.edu/people/ed | Ed Green ]] was able to let students use his server edser (edser2.ucsc.edu). The server has 390 G of RAM, which is necessary for certain assembly algorithms (Discovar //de novo//). | During the Spring 2015 [[https://www.soe.ucsc.edu/people/ed | Ed Green ]] was able to let students use his server edser (edser2.ucsc.edu). The server has 390 G of RAM, which is necessary for certain assembly algorithms (Discovar //de novo//). | ||
| - | In both the Spring 2012 and Spring 2015 classes the server Kolossus was accessed. Kolossus is a 1TB RAM machine that the UCSC Genome Browser group uses. Access is restricted, but students interested in using it can contact the [[http://genome.ucsc.edu/staff.html | UCSC Genome Browser system administration staff]]. | + | ==Kolossus== |
| + | |||
| + | In both the Spring 2012 and Spring 2015 classes the server Kolossus was accessed. Kolossus is a 1TB RAM machine that the UCSC Genome Browser group uses. Access is restricted, students interested in using it should explain their request to the [[http://genome.ucsc.edu/staff.html | UCSC Genome Browser system administration staff]]. | ||
about_the_class/about_the_class.txt · Last modified: 2015/09/11 22:04 by 5.9.83.211
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
