As agreed with EPSRC, the use of JADE is to be split approximately 50:30:20 between Machine/Deep Learning (ML), Molecular Dynamics (MD), and other applications, with up to 10% of the use being for research in non-EPSRC areas.

JADE is particularly intended for applications using up to 8 GPUs with a very high performance NVlink interconnect. It is not designed for MPI applications spanning multple compute nodes; for this purpose users should apply to use a more appropriate CPU/GPU Tier 2 system. Further details of these systems can be found here

Machine Learning

Researchers in partner universities should contact their local RSE support or Prof Wes Armour.

Researchers from other universities should apply for time through the twice-yearly EPSRC Tier 2 RAP (Resource Allocation Panel)

Tier 2 RAP Technial Assessments for JADE should be sent to:

Pump-priming time will also be available; please contact Prof Wes Armour in the first instance.

Molecular Dynamics

Time for Molecular Dynamics applications will only be allocated via the HECBioSim consortium.

Academic Access

To obtain a user account you need:

Hartree Centre Self Service Portal Account

In order to gain technical support for the JADE machine firstly register for access to the Hartree Centre Self-Service Portal (HCSSP), which is a web account used for reporting any operational issues with JADE and provides access to the Hartree knowledge base. An account can be obtained here, using the register option in the top right hand corner. Once registered a user will be able to access the user guides linked below.

To access the Hartree Centre status page click here.

For any account issues, please contact your local University JADE point of contact in the first instance.

Accessing the JADE Machine - SAFE Accounts

SAFE is the user account management system that the Hartree Centre currently use for accessing machines, this is a web account which will show you which projects you belong to, and your accounts associated with them.

Before applying for a SAFE account it is necessary to prepare an SSH key-pair, this will enable you to provide the public key as part of the SAFE registration. Information on generating and using SSH keys is available here for users who have already registered for the Hartree Self Service Portal.

Once your public SSH key is ready, apply for a SAFE account here. An email will be sent to your inbox containing a temporary password. Upon first login it will be necessary to update your password.

Further details on the SAFE registration process are available here.

In order to request access to a project, contact the PI of the project for the access code. Request access and await approval by the PI of the project. In order to learn how to request access, please read the section below.

JADE accounts

Use your SAFE account to apply for an account on JADE. Select the appropriate project from the drop-down list, found beneath your personal information and any existing login accounts. Then enter the JADE project access code which you will have received from the project PI or manager, and then click “Request”.

The approval process goes through several steps:

Once the account setup is complete, your SAFE account has full details on your new project account and you get a confirmation email. This process should not take more than 2 working days. If it takes more than that, check if the PI or project manager is aware that you have applied, and therefore your application needs their approval through the SAFE system.

Assuming your SAFE userid is xyz, and your project suffix is abc, then your project account username will be xyz-abc and you will login to JADE using the command

ssh -l xyz-abc

Note that some users may belong to more than one project, in which case they will have different account usernames for each project, and all of them will be listed on their SAFE web account.

Each project account will have a separate file structure, and separate quotas for GPU time, filestore and other system resources.

Note also that JADE has multiple front-end systems, and because of this some SSH software operating under stringent security settings might give warnings about possible man-in-the-middle attacks because of apparent changes in machine settings. This is a known issue and is being addressed, but in the meantime these warnings can be safely ignored.

We are always looking for new ideas and feedback.

Any questions or comments, please report it via GitHub issue tracker.