KAUST Supercomputing Laboratory Newsletter 31st August

Maintenance Session Tuesday 20th September

The next scheduled maintenance on Shaheen will be Tuesday 20th September from 08:00 until 17:00. There will no access to the system during this period.

Two Factor Authentication

Following the maintenance session on 20th Sept, we will be moving to Two-Factor Authentication for all users. Please ensure that you have set up and tested your 2FA connection before this date. Further details can be found at https://www.hpc.kaust.edu.sa/content/two-factor-authentication-shaheen

RCAC Meeting

The project submission deadline for the next RCAC meeting is 31st August 2016. Please note that the RCAC meetings are held once per month. Projects received on or before this deadline will be included in the agenda for the next RCAC meeting, scheduled to be held in September 2016. The detailed procedure and the forms are available here:


Neser Last Day of Operation

Please note this system will be decommissioned on 30th November 2016.

After this date all data in /project and /home will be deleted. Please ensure that you have transferred any data you wish to retain.

Tip of the Week: Cray programming environment: explain

When you are facing compilation or run time error messages using the Cray Programming enviroment, the explain command will help you further identify and locate the problem in the source code.

  • at compilation, to get more information about a warning or an error that has a group code of ftn (Fortran compiler) and a message number of 101 for example:
ftn-101 crayftn: ERROR  ..... 
~>explain ftn-101
Error : Dummy argument "%s" has the INTENT(IN) attribute so it must not be given the %s attribute.

An object with the VOLATILE attribute must not be a dummy argument with the intent(in) attribute.
  • at Run time, with a I/O error:
Open IOSTAT=5016
~>explain lib-5016 

An EOF or EOD has been encountered unexpectedly. The file terminated unexpectedly, perhaps without the proper end - of - file record or end - of - data control information.  The file specification may be incorrect, or the file may be corrupted. Ensure that the file specification is correct.  If the file is corrupted, create the data again, if possible. See the man pages for assign(1) and  asgcmd (1). The error class is UNRECOVERABLE (issued by the run time library)


Follow us on Twitter

Follow all the latest news on HPC within the Supercomputing Lab and at KAUST, on Twitter @KAUST_HPC.

Previous Announcements


Previous Tips