Friday, January 4th 2013 11:25:01 PM PST
Triton's access policy requires that all jobs be charged against a formal allocation. Jobs run on the 256GB PDAF nodes are currently charged at the base rate, and jobs run on the 512GB PDAFM nodes are charged a premium of two times the base rate. Please see the FAQ and Jobs pages for more details.
Users may continue to install software in their home directories if they require packages not provided by the Triton software stack.
Access to the UCSD Triton Resource at SDSC is governed by the Triton Affiliates and Partners Program, or TAPP. The policy supports current UCSD, SDSC and UC researchers, as well as non-UC industry partners, through a simple, streamlined allocation process with minimal overhead. For details, please visit the TAPP page.
All users are encouraged to join the Triton Discussion List for primary Triton support and community feedback.
To access Triton, you need a local account on the login node. If you already have a UCSD Active Directory (AD) account, it will be used to create your Triton account, and you will authenticate using the password associated with it. If you do not have a UCSD AD account, a Triton account will be created for you using an ssh public key you provide. The details of this setup will be handled through the TAPP Manager.
Login credentials must be entered at a Triton Resource login node. The primary login node is:
The alternate login node is:
Once logged in, users can submit jobs to all of the Triton compute nodes through the queue system. To find out more about running jobs, see the Running Jobs page. To find out more about logging in to Triton with a new account, please see the New User Guide.
The trial account phase for Triton Resource will end on Jan. 31, 2013. Please check for information about new research computing opportunities on the UCSD Research Cyberinfrastructure Website.
The Early Adopter phase of Triton ended on October 5, 2009. All accounts that existed at that time were granted an additional 1000 SUs, and all TAPP allocations were reset to their initial values plus the 1000 SU Startup Allocation.
Note that Startup Allocations are not transferrable and are intended for use only by the original grantee. If your Startup Allocation expires, contact the TAPP Manager about an extension.