Begin Here

Step 1: Getting an Account (select your location)

Sandia National Laboratories

Los Alamos National Laboratories

Lawrence Livermore National Laboratories

Step 2: Introduction to ASCI Red

Step 3: Location Specific Directions (select your location)

Sandia National Laboratories

Los Alamos National Laboratories

Lawrence Livermore National Laboratories

Step 4: Compiling, Debugging, and Running Jobs

Step 5: Optimization

Step 6: Related Documentation

Getting a DCE account. The three laboratories--Sandia, Los Alamos, and Lawrence Livermore-- have established a Distributed Computing Environment (DCE) which allows users to be authenticated at their local site and then that authentication is accepted at other sites. DCE involves establishing "cells" in which authentication occurs; once a user has been authenticated, then he or she can access resources in other cells. Sandia, Los Alamos, and Lawrence Livermore each have their own DCE cells. All Sandians that have SRN Kerberos accounts automatically have unclassified DCE accounts with the same name as their Kerberos name, all Sandians that have SCN Kerberos accounts automatically have classified DCE accounts with the same name as their Kerberos name. If you do not have a Sandia Kerberos account, contact Sandia Password Control via Sandia's Internal web, by phone at (505)845-9986, or by e-mail: Passwords@sandia.gov
For the ASCI Red system, you should use the automated workflow account request web page available on Sandia's Internal web. This WebCars system should be used by Sandians for obtaining an account on any classified or unclassified Sandia centrally maintained computer system. If you need long term file storage, be sure to request the Restricted Sandia Mass Storage System on the WebCars form.
To Non-Sandian ASCI machines, you will need to use these links to obtain an unclassified account or a classified account.

Getting a DCE account. The three laboratories--Sandia, Los Alamos, and Lawrence Livermore-- have established a Distributed Computing Environment (DCE) which allows users to be authenticated at their local site and then that authentication is accepted at other sites. DCE involves establishing "cells" in which authentication occurs; once a user has been authenticated, then he or she can access resources in other cells. Sandia, Los Alamos, and Lawrence Livermore each have their own DCE cells. The open LANL DCE cell is called: lanl.gov. To get an account in the open DCE cell, contact: Lynn Kluegel (dce-help@lanl.gov, (505) 667-4682). Contact Ron Wilkins (ronw@lanl.gov, (505) 665-1879) to get a Secure DCE account.
Then Non-Sandians will need to get an unclassified account or a classified account on the Sandia ASCI-Red machine (or any of the ASCI machines).

Getting a DCE account. The three laboratories--Sandia, Los Alamos, and Lawrence Livermore-- have established a Distributed Computing Environment (DCE) which allows users to be authenticated at their local site and then that authentication is accepted at other sites. DCE involves establishing "cells" in which authentication occurs; once a user has been authenticated, then he or she can access resources in other cells. Sandia, Los Alamos, and Lawrence Livermore each have their own DCE cells. All users of storage.llnl.gov (FAST), and blue.llnl.gov already have DCE accounts in the unclassified production DCE cell at LLNL, called spectrum.llnl.gov. If you need a DCE account or aren't sure, contact the Hotline (lc-hotline@llnl.gov, (510) 422-4531).
Then Non-Sandians will need to get an unclassified account or a classified account on the Sandia ASCI-Red machine (or any of the ASCI machines).

You will need to download Kerberos and SSH software (username and Kerberos password required). The Kerberos and SSH software may be downloaded for Unix and Windows (3.1, 95 and NT) workstations. The Kerberized version of SSH accepts the ticket generated by a "kinit" command; and hence the user is not prompted for his or her password for subsequent invocations of SSH or SCP for as long as the ticket is valid. If the non-Kerberized version is used, then the user will be prompted for his or her password whenever SSH or SCP is invoked.
Take a look at a brief or detailed description of the ASCI Red platform.
Consider reviewing the ASCI-Red Introductory course . . (Postscript viewer/printer must understand Postscript level 3)
You may wish to view ASCI Red for Dummies, a 19 page tutorial on using ASCI Red.

You should have a default .cshrc in you ASCI Red directory, but here is a more advanced .cshrc file for janus and sasn100.
Setting up the cross-compiler environment on sasn100.
Compile and run a f77 hello world on a single janus cougar compute node to verify basic functionality of your account.
Compile a f90 single parallel application on sasn100 using pgf90 and run the program on janus.
Metcalf's f90 tutorial on the web.
Info on cougar abend messages and finding where your program is abending.
NQS tips
- General NQS info
- How to submit a job to nqs and other nqs info
Debugging, xdebugging, perfomance monitoring and dbmalloc tutorial
- Debug tutorial (4up, 237 Kbytes) .
- Xdebug tutorial (4up, 746 Kbytes) .
- Sample source code 10 Kbytes.
Brief update for the debugger on ASCI Red .

Intel Teraflop/ASCI Red Frequently Asked Questions.

For technical assistance, contact:

janus-help -- ASCI Red help team at Sandia National Labs

For information about these pages, contact:

rkthoma@sandia.gov -- Robert K. Thomas

"Shift promptly from nuclear test-based methods to compute-based methods"

If you have any questions, email janus-help@sandia.gov

Updated: August 14, 2003
For information and feedback about these pages, please contact:
Robert K. Thomas -- rkthoma@sandia.gov

Site Map | Disclaimer | Search | Site Index