New ICHEC users should refer to the Fionn and Stoney support page as a starting point. Tutorials on specific topics can be found here. New users should also refer to the Education & Training section for training courses and upcoming workshop schedules.
When an account is created, your email address is automatically subscribed to a mailing list:
If you wish to receive updates about the Centre, please e-mail us at email@example.com, asking to be subscribed to the ichec-announce mailing list.
An overview of the application procedure from start to submitting jobs:
Once you have been assigned a username and initial password you can connect to the systems using SSH:
You will need SSH access outbound (port 22/tcp) to login to these machines. We have noticed in some institutions you will have to login to a network server with this SSH access first (e.g. DIAS). If you get a "Connection timed out" error, please contact your local network administrator first to ensure you have the appropriate ports open. Failing this, please submit an issue to the ICHEC Helpdesk.
To connect to ICHEC systems you need to be logging in from IP space assigned to a partner institution. This means that under normal circumstances you cannot connect directly from home or when travelling. However your host institution may well provide a system to which you can connect from home etc. and from which you can subsequently connect to ICHEC systems. Whether or not such a system is mechanism is provided is a matter for local policy at your institution.
Secure Shell (SSH) is a program to log into another computer over a network, to execute commands in a remote machine, and to move files from one machine to another. It provides strong authentication and secure communications over insecure channels. SSH provides secure X connections and secure forwarding of arbitrary TCP connections.
SSH works by the exchange and verification of information, using public and private keys, to identify hosts and users. The ssh-keygen command creates a directory ~/.ssh and files that contain your authentication information. The public key is stored in ~/.ssh/identity.pub and the private key is stored in ~/.ssh/identity. Share only your public key. Never share your private key! To further protect your private key you should enter a passphrase to encrypt the key when it is stored in the filesystem. This will prevent people from using it even if they gain access to your files.
If your desktop is on a private network and/or you need to ssh to ICHEC machines via a local ssh proxy then the best way to transfer files directly between your desktop and ICHEC is to use sftp over an ssh tunnel. To create the tunnel use something like:
ssh -f -N -L 2222:fionn.ichec.ie:22 firstname.lastname@example.org
Then all connections to port 2222 on your desktop will be forwarded via sshproxy to fionn.ichec.ie. So to ftp between ICHEC and your desktop you can simply use:
sftp -oPort=2222 ichec_username@localhost
If you receive a request for your login details either by email or telephone you should NOT disclose them regardless of whether the person contacting you purports to be from ICHEC or otherwise as it may be an attempt to steal your login credentials as can be the case with online banking for example. Please ignore the request and report it to us directly.
This problem can occur if you have commands in your .bashrc file which produce output, perhaps an error message which can cause the problem to appear to be intermittent. Such commands should be placed in your .bash_profile file instead where they will not interfere with the SFTP connection process.
Fortran, C, and C++ are available on the ICHEC systems. The commands used to invoke the compilers and/or loaders vary from system to system. For more information, see the system specific pages; Fionn and Stoney. A number of scripting and interpreted languages are also available.
We have included instructions on the Gaussian page of our software section.
On the Fionn cluster, batch processing is managed by the Portable Batch System (PBS) and Moab Scheduler. PBS batch requests (jobs) are shell scripts that provide timing, memory, and processor information. For example scripts, see the Fionn and Stoney support page. PBS uses qstat -a to check the status, and qdel to delete a batch request. For more information also see our tutorial on batch processing and queueing.
All jobs should be submitted to Fionn via the PBS. PBS uses qsub my_script_name to submit a job. A sample script can be found on the Fionn and Stoney support page.
A taskfarm utility is in place on Fionn you can find details here.
Use the mybalance command as follows:
This command will return the number of core hours available to all your projects (in the above example icphy001c). So for instance, if you wish to run a 48 CPU core job for 24 hours, you will need to ensure that you have a minimum of 24*48=1152 core hours on your project's account.
On Fionn and Stoney you can monitor the output to stdout/stderr while a job is running by examining the appropriate file in:
The order that jobs run in is decided by the Moab scheduler based on a priority it calculates for each job. The calculation of queue priority is relatively complex in order to deal with long queues, large numbers of jobs and various classes of project. Below is a list of the factors that affect queue priority:
In addition to priority, a backfill mechanism can allow jobs to skip the queue fill space that would otherwise have been unused. This allows smaller jobs with shorter runtimes to maximise our utilisation while larger jobs wait for processors to free up.
Fionn has hard and soft limits on the number of jobs and processors a single user can use. The soft limits apply when there is a queue and the considerably higher hard limits apply when there are no jobs waiting to run. When a user exceeds whatever limit is in force all their queued jobs are moved from the queue to a blocked state and are only unblocked when a job completes or the limit is no longer active. Blocked jobs are only checked periodically and not on the regular job scheduling interval.
In addition there is a limit on the number of jobs a user may have queued even when they have not exceeded the hard or soft limits. Additional jobs will be moved to a blocked state until a queued job runs or is cancelled. For further information see the scheduling policies page.
The ICHEC Helpdesk and the email address are the two main entry points to ICHEC's support teams for registered users. Here you can get help in using the service, find out more about ICHEC or send us your comments.
Please send an e-mail to email@example.com asking for a new password.
We would appreciate a formal acknowledgement of ICHEC by inclusion in any resulting publications of the following sentence or some variation thereof: "The authors wish to acknowledge the DJEI/DES/SFI/HEA Irish Centre for High-End Computing (ICHEC) for the provision of computational facilities and support."
It is also important that you notify us of the publication at firstname.lastname@example.org
When projects disk quota is exceeded the PI will received an email notification. You can check the disk usage using the
UNIX treats the end of lines differently than other operating systems. Sometimes when editing files in both Windows and UNIX environments, a CTRL-M character gets added to the end of each line as ^M in vi. To remove the ^M characters use the following command:
If you are connecting from a MS Windows machine you will need to have Xming, Hummingbird Exceed or similar installed and running on your workstation. You also need to ensure that X11 forwarding is enabled.
On a typical Unix system X11 support will already be in place and you need connect using: ssh -X email@example.com. Now you can execute any of your X applications and it should forward the X application via SSH to your local screen. For example:
You should now see the Xclock is running on your local screen.
In addition to individual user's home directories e.g. /ichec/home/users/username each project has an associated project directory /ichec/work/project_code which is accessible by all members of that group. By default a user's home directory and its contents cannot be read by other users though you can change the directory permissions to allow this if you wish.
This command will make the contents of the named directory readable by the other members of you project.