archive-edu.com » EDU » C » COLORADO.EDU

Total: 508

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Home | Research Computing
    Jobs File System and Storage Queues Maintenance Schedule Fixed Allocations Jobs and Queues FAQ Support User Guide Quick Start Basic HPC Concepts Logging In Getting an Allocation Password Authentication Slurm The RC Environment Using the Shell Storage Allocations Compilers and MPI Queues Submitting a Job Submitting Serial Jobs Submitting MPI Jobs Interactive Jobs Job Information File Transfer Scontrol in Detail Advanced Topics Software Software Request Policy Applications Compiled Languages Debugging

    Original URL path: https://www.rc.colorado.edu/user/login?destination=comment/reply/165%23comment-form (2014-12-04)
    Open archived version from archive


  • Allocations | Research Computing
    if it requires the Allocation Committee s approval so it is important to be aware of your allocation balance and the rate at which you are using your allocation Processor hours are expressed in SU or Service Units which are generally equivalent to CPU hours Please scroll down for allocation request details and a link to our allocation request form Submitting against an Allocation Jobs will submit against your default allocation unless you specify one with a A flag this can be done at submission or in your job script To submit a job with the A flag bash 3 2 sbatch A UCB7111101 myjob sh Multiple flags can be used on the command line This example starts an interactive job on a debug node charged against a Startup allocation bash 3 2 salloc A S99000001 qos janus debug In a job script you would use a SBATCH A allocation to specify an allocation Run against allocation UCB7111101 Molecular dynamics 2014 SBATCH A UCB7111101 Checking your Allocation The sbank command allows you to check your allocation balances Allocations are called accounts in Slurm bash 3 2 sbank balance statement U USER User Usage Account Usage Account Limit Available CPU hrs ralphie 48 S00000005 4 352 1 666 667 1 662 314 ralphie 1 UCB000000122 88 667 610 351 521 684 Please be aware that if an allocation has no available time left jobs submitted against it will not move through the queue and will be marked as unable to run due to AssociationJobLimit Default Allocation Users with multiple allocations can see their default allocation with the Slurm command sacctmgr p show user USER sacctmgr p show user USER User Def Acct Admin ralphie ucb00000055 None We are working on a tool to allow users to more easily check and set their default allocation At present if you need to change your default you can email rc help however you can always use the A flag to select the allocation you would like a job to run against Requesting an Allocation As of January 2013 all users are allowed a Startup or Testing allocation of 50K SU one time upon request This amount of time is generally enough for a lot of testing and a proof of concept for a larger allocation request Larger Project allocations are also available but will require more supporting documentation such as Previous work that informs the request How the size of the request was determined and were other implementations that would have used more or fewer CPU hours tested Optimization of code and workflow compiler optimization workflow optimization to fully utilize nodes Planned runs roughly how many jobs of what size and what sort of monthly load we should expect i e will the compute time be used roughly equally each month or 6 months of heavy usage and then a small amount of post processing work Expected results publications degrees presentations If the project will continue beyond this one year allocation please inform us

    Original URL path: https://www.rc.colorado.edu/crcdocs/allocations/ (2014-12-04)
    Open archived version from archive

  • Getting an Allocation
    time Startup or Testing allocation of 50K SU 50 000 CPU Hours is available to all users PI s may request a Project allocation or collaborators can make the request for the PI by selecting the PI from the drop down list Your PI will need to have an RC account but need not get an OTP device and log in if they do not wish to Grad students and

    Original URL path: https://www.rc.colorado.edu/book/export/html/168 (2014-12-04)
    Open archived version from archive

  • Home | Research Computing
    Jobs File System and Storage Queues Maintenance Schedule Fixed Allocations Jobs and Queues FAQ Support User Guide Quick Start Basic HPC Concepts Logging In Getting an Allocation Password Authentication Slurm The RC Environment Using the Shell Storage Allocations Compilers and MPI Queues Submitting a Job Submitting Serial Jobs Submitting MPI Jobs Interactive Jobs Job Information File Transfer Scontrol in Detail Advanced Topics Software Software Request Policy Applications Compiled Languages Debugging

    Original URL path: https://www.rc.colorado.edu/user/login?destination=comment/reply/168%23comment-form (2014-12-04)
    Open archived version from archive

  • Password Authentication
    application based authenticators and audio authenticators for the visually impaired More information on standard VASCO GO 6 can be found on the VASCO GO 6 Page Information on the Digipass for Mobile Devices coming soon is on the VASCO Mobile Digipass page Obtaining an OTP Authenticator device An authenticator can be obtained in person from Research Computing s office on East campus or from the OIT help desk in the Telecom building on Main Campus Research Computing does not have regular office hours so most users contact the OIT help desk If you would like to get an authenticator from us at RC please make arrangements with us to meet by emailing us at rc help colorado edu You will need to come in person and bring your state issued ID Authenticators are also available on the Auraria and Anshutz campuses If you cannot come to get an authenticator in person contact us to make arrangements for an alternative method of distribution To request an OTP Authenticator from OIT formerly ITS on Main Campus follow their procedure from their OTP information page http www colorado edu oit otp and pick up the authenticator in person from their Help Desk when

    Original URL path: https://www.rc.colorado.edu/book/export/html/169 (2014-12-04)
    Open archived version from archive

  • Home | Research Computing
    Jobs File System and Storage Queues Maintenance Schedule Fixed Allocations Jobs and Queues FAQ Support User Guide Quick Start Basic HPC Concepts Logging In Getting an Allocation Password Authentication Slurm The RC Environment Using the Shell Storage Allocations Compilers and MPI Queues Submitting a Job Submitting Serial Jobs Submitting MPI Jobs Interactive Jobs Job Information File Transfer Scontrol in Detail Advanced Topics Software Software Request Policy Applications Compiled Languages Debugging

    Original URL path: https://www.rc.colorado.edu/user/login?destination=comment/reply/169%23comment-form (2014-12-04)
    Open archived version from archive

  • Interactive Jobs | Research Computing
    job reserving a complete node see below might be safer as the compile nodes are shared To start an interactive job first load the module for Slurm with the module load command bash 3 2 module load slurm Then you use the command salloc to request an interactive job If you need X11 forwarding replace salloc with sinteractive in the following examples You would also likely want to select a QOS to get the type of node and walltime you need with the same arguments you use when using salloc to submit a job script Without arguments you will get a single node job in normal that may be slow to start Here is an example that requests a node on Janus via the debug QOS bash 3 2 salloc qos janus debug bash 3 2 When the job runs you are transported to a session on the requested node Your my bashrc should be sourced but the prompt will probably look the same and you may not immediately see that you have been logged into a different host The hostname command will tell you where you are Your environment will be preserved between the login node and the job bash 3 2 hostname node0501 bash 3 2 ctrl d will log out out of the interactive session and return you to the login node you started from Interactive jobs wait in the queue like any other jobs so generally they are only used for short and small jobs that might start in a few minutes The terminal you use to salloc the interactive job is locked until that job starts so if you are waiting a long time for your job to start you will want to start another terminal window and use scontrol show job jobid or squeue

    Original URL path: https://www.rc.colorado.edu/node/186 (2014-12-04)
    Open archived version from archive

  • Queues | Research Computing
    Library Job Arrays Job Serialization Example Load Balance IPython Load Balance Tool MPI Compile and Run Matlab on Janus SSH config Simple Test Job Consulting Contact Us You are here Home Support User Guide Queues Queues SLURM uses Quality of Service requests in place of queues We have simplified the structure also as SLURM gives us more ability to maintain fair wait times without the need for many queues The QoSes for the Janus nodes are the following QoS Max Walltime Default Walltime Max Nodes Max Running Jobs Max Queued Jobs Priority Explanation janus 24 hours 24 hours 600 unlimited 0 This is the default QoS for all jobs janus long 7 days 7 days 40 unlimited 200 For any long running jobs There is a total of 80 nodes for this QoS janus debug 1 hour 1 hour 480 2 4 400 Strictly for debugging purposes The maximum queued jobs includes any running jobs The QoSes for all other Research Computing resources are the following QoS Max Walltime Default Walltime Max Nodes Max Running Jobs Max Queued Jobs Priority Explanation himem 14 days 14 days unlimited 0 Allows a job to run on any of the high memory nodes

    Original URL path: https://www.rc.colorado.edu/node/182 (2014-12-04)
    Open archived version from archive



  •