For information on requesting an account on JADE please follow the link below:
Getting an account — JADE documentation
This link covers how to apply for a Hartree SAFE account, a JADE project account and a Hartree “ServiceNow” account (Hartree’s self-service customer portal). Please note access to ServiceNow will only be provided after the user has registered within SAFE and joined a project.
Please be aware, access to these systems and projects is not automatically approved. Project membership approval is completed by the project’s PI or PM. Hartree is responsible for account provisioning, but only once the project’s PI/PM has approved project membership and has added the user to one or more project groups.
Information on generating SSH keys is detailed below:
You will need to provide your SSH public key as part of your SAFE account registration process (you must never share your private key with anybody). Please note that new or updated SSH keys are deployed to the respective user account by Hartree during business hours, only.
Accounts pending SSH key availability will result in reminders sent at 1, 2- and 3-week intervals. After a period of 4 weeks pending, due to a missing key, the request for the account will be declined.
Local Institutional Support
Partner institutions provide technical support for their users through local HPC experts. They will provide guidance to users starting out on JADE and can also direct users to sources of specialist information if required.
Currently, the local points of contact are listed on the main support page linked below:
For specialist questions relating to the use of JADE please contact your local institutional support in the first instance, information for which can be found here:
For technical queries about software/drivers please use the GitHub Issue tracker.
When specific packages of maintenance work are scheduled, an announcement will be made via e-mail (subject to users having chosen not to opt out of informational e-mails) and the Message of the Day will be updated accordingly.
Any questions or comments, please report it via GitHub issue tracker.
GitHub