- 1 Overview
- 2 1 Request a Project Allocation
- 3 2 Request an Account
- 4 3 Access Technical Information
- 4.1 How do I activate/use my Titan SecurID fob?
- 4.2 How do I connect to Titan?
- 4.3 How can I keep up with system outages and other events?
- 4.4 What filesystems are available on the OLCF systems?
- 4.5 How do I transfer data between Titan and systems outside of ORNL?
- 4.6 Which third party software packages are available on Titan?
- 4.7 How do I compile on Titan?
- 4.8 How do I submit and run jobs on Titan?
- 4.9 What GPU programming techniques should I use on Titan?
Access to Titan through the NCRC project is limited to approved users and project allocations. This page lists the steps to gain access to Titan, as well as some basic system usage for new users.
Please read this guide carefully, as the process for gaining access to Titan is markedly different from that of gaining access to Gaea. NOAA users on Titan through the NCRC project must go through the same procedures and security checks as traditional Titan users. This process may be unfamiliar to most NOAA HPC end-users.
If you have any questions that are not answered here, feel free to contact the OLCF Accounts Team at firstname.lastname@example.org.
1 Request a Project Allocation
Titan resources are allocated via projects. Approved projects will be granted a project allocation of node-hours.
Each user account must be associated with at least one project allocation. Once a project allocation has been approved, users can apply for user accounts on the project to run jobs. If you would like to join an existing project allocation, you can skip the rest of this section and go directly to the next section, “Request an Account”.
Otherwise, begin by filling out and submitting the NOAA Project Allocation Request form.
- We send it to NOAA management for initial approval.
- If granted initial approval, an OLCF Accounts Team representative is assigned to the project. This representative will assist the PI with further steps.
- The signed Principal Investigator’s PI Agreement (submitted with the project application) is reviewed.
- Export Control: The project request will be reviewed by ORNL Export Control to determine whether sensitive or proprietary data will be generated or used. The results of this review will be forwarded to the PI. If the project request is deemed sensitive and/or proprietary, the OLCF Security Team will schedule a conference call with the PI to discuss the data protection needs.
- ORNL Personnel Access System (PAS): All PI’s are required to be entered into the ORNL PAS system. An OLCF Accounts Team member will send the PI a PAS invitation to submit all the pertinent information. Please note that processing a PAS request may take 15 or more days.
- User Agreement/Appendix A or Subcontract: A User Agreement/Appendix A or Subcontract must be executed between UT-Battelle and the PI’s institution. If our records indicate this requirement has not been met, all necessary documents will be provided to the applicant by the OLCF Account Team representative.
Upon completion of the above steps, the PI will be notified that the project has been created and provided with the Project ID and project allocation. At this time, project participants may apply for accounts.
The project allocation process can take up to 2 months, depending on the citizenship status of the PI and the export control considerations of the request.
2 Request an Account
Once a project allocation has been processed, end-users can apply for accounts on the project by filling out and submitting the OLCF Account Request Form with your information. Please be sure to follow these guidelines as well:
- For field Employer Type, select “Government not DOE” if you are a NOAA employee.
- For section Project Information, supply the information provided to you by the project’s PI.
- For field Publishable data as a result of this work, you must agree to publish in order to use Titan.
- For field System for which you are selecting an account, limit your selection to “Cray XK7 (Titan)”.
- The ORNL Account Team Member will contact the project principal investigator (PI) for his/her approval. The PI of the project must approve your account and system access.
- Additional paperwork will be sent to you via email to complete for identity proofing in order to receive an RSA SecurID for Titan.
- Foreign national applicants will be sent an Oak Ridge National Lab (ORNL) Personnel Access System (PAS) request specific for the facility. After receiving your response, it takes between 15-35 days for approval.
- A fully-executed User Agreement with your institution is required. If our records indicate your institution needs to sign either a User Agreement, the form(s) along with instructions will be sent via email.
- If you are processing sensitive or proprietary data, additional paperwork is required and will be sent to you.
Your account will be created and you will be notified via email when all of the following steps are complete:
- Account application form is completed.
- Account is approved by the project’s PI.
- RSA SecurID Identity proofing paperwork has been returned.
- PAS request has been approved for foreign nationals.
- A fully-executed institutional User Agreement is on file.
- If a proprietary/sensitive project, additional paperwork has been completed.
The account approval process can take up to 2 months, depending on the citizenship status of the applicant.
3 Access Technical Information
Once your user account is setup, take some time to access technical documentation on Titan. The Titan User Guide is the definitive source of support information for Titan end-users.
Some of the basic topics are covered briefly below.
To first activate a new SecurID key fob, do the following:
- Initiate an SSH connection to
- When prompted for a PASSCODE, enter the token code shown on the fob.
- You will be asked if you are ready to set your PIN. Answer with “Y.”
- You will be prompted to enter a PIN. Enter a 4-to-6-digit number you can remember. You will then be prompted to reenter your PIN.
- You will then be prompted to wait until the next token code appears on your fob and to enter your PASSCODE, which is now your PIN + 6-digit token code displayed on your fob.
- Your PIN is now set, and your fob is activated and ready for use. Exit your ssh session on
To subsequently use your fob in the future, do the following:
- When prompted for your PASSCODE, enter your PIN + 6-digit token code shown on the fob. For example, if your pin is 1234 and the token code is 987654, enter 1234987654 when you are prompted for a PASSCODE.
For complete details, see the Titan User Guide section on Authenticating to OLCF Systems.
To connect to Titan from a UNIX-based system, initiate an ssh connection to:
To avoid risks associated with using plain-text communication, the only supported remote clients on Titan are secure shell (SSH) protocol version 2 clients; this encrypts the entire session between Titan and the client system.
SSH clients are also available for Windows-based systems. Windows SSH clients must be configured to use keyboard-interactive authentication.
The only supported authentication method to Titan is one-time password (OTP) via SecurID fob.
The OLCF provides users with several ways of staying informed about system outages. For full details, see the Titan User Guide section on Communications to Users.
Titan users are provided with ‘Home’ storage areas, ‘Work’ storage areas, and ‘Archive’ storage areas for both user-centric data and project-centric data. For full details see the Titan User Guide chapter on Data Management.
Titan users have a number of different options to choose from for data transfer. For complete details see the Titan User Guide section on Transferring Data.
A complete list of all available software at the OLCF can be found at the OLCF Software page. Most software listed is available on Titan specifically.
Detailed information is available in the Titan User Guide’s Chapter on Compiling on Titan.
Detailed information is available in the Titan User Guide’s Chapter on Running Jobs on Titan.