Shaheen and Neser unavailable 18th-20th March 2015
In preparation for the introduction of the new Cray supercomputer, there will be a site-wide power outage to the Data Centre currently housing Shaheen1 and Neser. All services, including Shaheen1 and Neser, will be shut down from 17:00 on Wednesday 18th March until approximately 11:00 on 20th March.
Intel HPC Workshop
The KAUST Supercomputing Laboratory is pleased to host the world largest chip manufacturer Intel on March 24th to present the latest hardware and software technologies developed by Intel that every developer needs to understand when implementing any HPC scientific applications. The event is in the form of a half day tutorial from 9AM to 12:30PM in the spine auditorium between Buildings 2 and 3. The registration is free but required.
To register, please fill out the online registration form at http://goo.gl/forms/qBX0wg4qVN.
The main event will be followed by a full day of hands-on sessions, when KAUST developers will be mentored by the Intel experts to put in practice what they have learned during the workshop. The hands-on session will take place on March 25th starting at 9:00AM, in Building 9, Lab 2220. Space will be limited to 15 developers only.
For more information about the venue, the registration and the details of the workshop technical content, please visit http://www.hpc.kaust.edu.sa/training/2015/intel/.
If you have any question, please contact us at email@example.com
Tip of the Week: What’s the status of my job?
llq –u , the ST column in the output shows the current state of the job step.
· I (Idle): the job step is waiting to be scheduled.
· NQ ( NotQueued): the job step is not being considered for scheduling, but it has been submitted to LoadLeveler
· H (User Hold): the job step is not being considered for scheduling. It can be released from hold using the
llhold -r command by the user who submitted the job.
· S (System Hold): the job step is not being considered for scheduling. It can be released only by a LoadLeveler administrator.
· HS (User & System Hold): the job must be released from hold by a LoadLeveler administrator and by the user before it can be scheduled.
· D(Deferred): The job step was submitted with a startdate, and that date and time have not yet arrived.
· R(Running ): the job step is currently running.
· P(Pending): the scheduler has assigned resources to the job step and is in the process of sending the start request to the resource manager.
· ST(Starting): the resource manager has received the start request from the scheduler and is in the process of dispatching the job step to the nodes where it will run. The next state will normally be Running.
· C (Completed) : the job step has completed.
· CA (Cancelled): the job step was cancelled by a user or an administrator.
· E (Preempted): the job step has been preempted by the suspend method, either by the scheduler or by an administrator using the llpreempt command.
· EP (Preempt Pending): LoadLeveler is in the process of preempting the job step.
· MP (Resume Pending): the job step is being resumed from preemption. The next state will normally be Running
Follow us on Twitter
Follow all the latest news on HPC within the Supercomputing Lab and at KAUST, on Twitter @KAUST_HPC.
KSL Announcements archives can be viewed at http://www2.hpc.kaust.edu.sa/mailman/private/announce.
Questions, concerns, or problems related to Shaheen should be directed to firstname.lastname@example.org. From there your issue will be assigned to an appropriate primary contact who will track your issue to resolution. We may sometimes have to request items from KAUST IT or other service providers.
Getting an account
FAQs on the process and requirements for obtaining access to the Shaheen Systems are available here.
Getting an account on Shaheen is a three-step process and is detailed in this flowchart.
You should consult our Terms and Conditions of Usage.
- Your organisation or department must submit the Organisational Access Application, establishing a relationship between your home organisation and the KAUST Supercomputing Laboratory (KSL).
- You (or your Principal Investigator) must submit a Project Proposal describing the work to be done and the resources your project will require.
- You must submit an Individual Account Application, supplying identification information from which we can generate login credentials.
Use the secure submission form to submit credentials or other private information.
Accessing KSL Systems
After you have been given login credentials (i.e., a username and password) you will be able to access any Shaheen systems to which you have been granted access. Primary computational access to Shaheen and Neser is available via the ssh (secure shell) protocol.
PIs are required to submit periodic project reports during the course of their work on the KSL systems, there is a template available for this.
Data Centre Visits
To request a visit to the Data Centre, in the first instance, please complete this form.
Because the Shaheen Systems are a widely shared resource, user reservations are not encouraged. However, if a user feels that making a reservation for dedicated access to all or part of the Shaheen systems is essential for their work, then KSL will consider such requests on a case-by-case basis within the bounds of the following guidelines:
- A minimum of 14 days, preferably 30 days, notice is required for all reservations.
- The maximum duration allowed for a reservation will be 48 hours.
- A reservation may request dedicated access to between 1 and 16 racks of the Shaheen BG/P system. Reservations of less than 1 rack of BG/P will not be permitted.
- Users’ project accounts will be charged for all racks reserved for the entire reservation period, regardless of whether they are all used or not.
- There are no guarantees that a reservation request will be accepted.
Exceptions to this policy may be allowed based on the merits of a request, but very rarely.
- If a user has a complaint about a KSL decision relating to resource allocation, and the user remains unhappy after discussing their concerns with KSL Management, users can request arbitration from the Chairman of the KSL Resource Allocation Committee (KSL RAC) (currently Dr David Keyes). If the user remains unhappy with the decision of the Chairman of the KSL RAC, users can request arbitration from the Chairman of the KSL Management Committee (KSLMC).
- If a user has a complaint about KSL policies, or other matters not relating to resource allocation, and the user remains unhappy after discussing their concerns with KSL Management, users can request arbitration from the Chairman of the KSL Management Committee (KSLMC).
- Get a quick look at the machines.