XSEDE New User Tutorial

XSEDE New User Tutorial
Jay Alameda National Center for Supercomputing Applications

Yeah! I got an XSEDE allocation!
Now what?

Learning Outcomes After completing this tutorial, you will be able to: Use the XSEDE User Portal Access your XSEDE resources Manage files Run jobs Get help

XSEDE User Portal (XUP)
URL: portal.xsede.org Single point-of-entry to information about XSEDE services and utilities for using them Anyone can create an XUP user account and access non-project features Only XSEDE allocation project members can access project features Open the XUP in a web browser. The XUP's features enable you to effectively use XSEDE’s services. For example, from the XUP you can: Login to your XSEDE accounts View and monitor systems and jobs Find and register for training classes Commuicate with other XSEDE users via discussion forums Request assistance from the XSEDE Help Desk Subscribe to user news and announcements Anyone can create an XUP user account. Much of the XUP's information can be viewed without creating a user account but to experience many of its features you must have one. For example, you must have an XUP account to post on the user discussion forums or register for training classes. Only project members of an XSEDE allocation can access features for using resources and managing a project.

Create and login to your XUP Account Use XSEDE resources responsibly
Using the XUP Create and login to your XUP Account Use XSEDE resources responsibly Get added to your XSEDE project Navigate your personal My XSEDE webpage Navigate the information in the XUP In this lesson we focus on the basics you need to know about using the XUP to find information about your XSEDE resource(s) and access the utilities it provides for using them. After completing this lesson, you will be able to: Create and login to your XUP Account Use XSEDE resources responsibly Get Added to your XSEDE project Navigate your personal MY XSEDE webpage Navigate the information in the XUP There are many other capabilities provided by the XUP that are not covered in this lesson. However, you will learn how to use many of them later in this tutorial.

Create and login to your XUP account
portal.xsede.org From the XUP homepage, click CREATE ACCOUNT Complete the User Account Form Verify your account request Select your username and password Login to the XUP Click the CREATE ACCOUNT link to display the user account form. Describe the steps to create an XUP account or step through the process by creating a fictitious account. If time permits ask students to follow along and create an account if they do not already have one. From the User Portal homepage at portal.xsede.org, click the CREATE ACCOUNT link. This link can be found in the lower portion of the gray 'Enter the Portal' box. After clicking the CREATE ACCOUNT link, a form where you can enter your personal information to request a user account will be displayed. In the form's 'Personal Information' section, enter your information by filling in the form fields and using the drop-down lists. In the form's 'Choose A Registration Key' section, enter a maximum of six characters, using letters and numbers only. Remember what you enter because you will need it later to verify your account. In the form's 'Prove You Are Human' section, enter the words you see in the Captcha challenge box. If you are not sure what the words are, either enter your best guess or, to the left, click the Get a new challenge icon. If you are visually impaired you can click the Get an audio challenge icon to hear an audio version of the displayed words. Click the Submit button to request your XUP account. After requesting your account, a verification form will be displayed and you will receive an message containing an account verification code you will need to complete the form. In the form's 'Verify Your Account Request' section, enter your address, registration key, and the code from the verification . In the form's 'Choose Your XSEDE User Name and Password' section, enter your preferred user name and password following the guidance given on the form. In the form's 'Prove You Are Human' section, enter the words you see in the Captcha challenge box. Click the Submit button to verify your request.After verifying your request, your account is created and a login form is displayed. In the login form, enter the XUP user name and password you selected and click the Submit button.

XSEDE Acceptable Use Policy
Must accept the User Responsibilities Form after creating your XUP account and again at the beginning of each allocation you receive. Choose a strong password and protect it. Close SSH terminals and log out of the User Portal when you are finished with your session. Report Suspicious Activity : call immediately, regardless of the time of day. XSEDE Cybersecurity Tutorial The first time you login to the XUP you will be asked to read and accept the XSEDE usage policies. These policies outline the practices you need to follow to protect XSEDE's shared resources and intellectual property. You will also need to sign this form again at the beginning of each allocation you receive. If you do not do this within 30 days of the approval of your allocation, your account will be deactivated. The key usage policies include: Do not share passwords, do not write passwords down where they can be easily found, and do not use tools that expose passwords on the network. This includes private keys. You must make sure they are password-protected. Close SSH terminals and log out of the User Portal when you are finished with your session. Report Suspicious Activity. If you have any reason to suspect that your account or personal computer has been compromised, call immediately, regardless of the time of day. Taking the steps necessary to protect your XSEDE account is very important. Please see the XSEDE Cybersecurity tutorial for more detail.

Get Added to Your XSEDE project
If you are not the project PI, you will need to be added to your project’s account in the XUP. Contact your project’s PI or Allocation Manager and request that you be added to the project. You will need to provide them with your XSEDE User Portal user name. Only the Principle Investigator and the people they designate as a project member will have access to an allocation’s account information and utilities. If you are the Principle Investigator, you will have created your XUP account during the allocation request process and you will automatically have full access when your allocation request is approved. All other members must be added to the project by the PI or their designated Allocation Manager using the ‘Add User’ option in the XUP. To get this done, contact the PI or Allocation Manager and request that you be added to the project. You will need to provide them with your XSEDE User Portal user name.

Your My XSEDE webpage (1) WELCOME TO XUP
Quick access to commonly used features. (2) LATEST UPDATES Latest information specific to your user account. (3) MY ACTIVE ALLOCATIONS Summary of the active projects for which you are either a PI or member. When you login to the XUP, you will see your MY XSEDE summary page. This is a page customized for you so you can quickly access information and utilities pertaining to your XSEDE account. On this page, you will see a set of three display boxes titled: WELCOME TO XUP LATEST UPDATES MY ACTIVE ALLOCATIONS The WELCOME TO XUP box (1) contains links to functions that are frequently accessed by XSEDE users such as managing your allocations and logging in to your XSEDE accounts. You can use these links to quickly reach these functions without the need to find them from the main navigation. The LATEST UPDATES (2) box provides access to the latest information specific to your user account. In it you will see: A space displaying the avatar you setup in your user profile Your last login date A listing of your open help tickets and a link to submit a ticket Information about any jobs you have running on your XSEDE resource(s) A listing of publications you have added to your user profile A listing of training classes for which you have registered along with a link to the training calendar A link to update your profile The MY ACTIVE ALLOCATIONS box (3) gives a summary of the active projects for which you are either a PI or member. This summary includes the percentage left, end date, and burn rate on your allocation.

Update your XUP User Profile
7/6/11 Update your XUP User Profile MY XSEDEProfile View and or change your user information (organization, address). Make sure your address is correct. XSEDE staff will use it to communicate with you regarding your allocation. Highlight the user profile option. Click the Update Profile link in the Latest Updates box on the My XSEDE web page or the My XSEDE > Profile link. Show that users can change their user information here. Stress that they make sure address is correct since it will be used by XSEDE staff to communicate with them regarding their allocation. 10

Navigating the XUP My XSEDE Resources Documentation Allocations
Training User Forums Help About From your web browser, demonstrate navigating the XUP and describe each main menu option briefly. Highlight a few key options in following slides. From CI-Tutor: The XUP is your primary source for the information and utilities you need to use your allocation effectively. You can easily navigate the XUP using the menu options found at the top of the XUP webpages. The main XUP content categories are defined by the headings contained in the tabs in the top navigation row. When a tab is selected, the sub-categories are listed in the row below. You will learn more about many of these options further in this tutorial. For now we give just a brief overview of each main category in the table below. MY XSEDE - Provides options for accessing information and utilities pertaining to your XSEDE account. From this tab you can view information specific to your account including allocation usage; an account listing of your allocated resources along with links to quickly login to each one; and current and historical data for jobs you run on XSEDE resources. You can also view and update your user profile and your publications in the XSEDE publications database; change your XUP password, add users to your account (if you are a project PI); access gateway community accounts; and open an SSH Terminal window where you can directly connect to your XSEDE resources from the XUP. RESOURCES - Provides options for finding information specific to XSEDE services. From this tab you can find information about all of the services and software currently available on XSEDE and view a status monitor of XSEDE HPC systems. From the Queue Prediction option you can provide the details of your job and get a prediction of the wait time, start time or both.There is also a calendar of scheduled downtimes for XSEDE services. DOCUMENTATION = Provides options for finding documentation for XSEDE services. The documentation provided includes quick start guides for getting started on XSEDE, accessing resources, and managing data; user guides for all XSEDE resources; the XSEDE usage policy; and instructions for downloading several XSEDE file management tools and GSI-SSH. To keep you up-to-date on the latest happenings in XSEDE, the News options lists all XSEDE news announcements and gives you the option to subscribe to the news announcements RSS feeds. XSEDE's extensive knowledge base of frequently asked questions and introductory documentation is available from the Knowledge Base option. The Knowledge Base provides a listing of help documents and the ability to search for information by entering individual words or phrases. ALLOCATIONS - Provides options for learning about and requesting an XSEDE allocation and extended collaborative support to enhance the effectiveness and productivity of your work performed on an XSEDE resource. TRAINING - Provides options for accessing XSEDE's training offerings. The Course Calendar option provides a list of upcoming live training events offered on-site or via webcast with links to event registration forms. The Online Training option provides a list of self-paced tutorials covering programming principles and techniques for using XSEDE resources and services effectively. USER FORUMS - Provides access to discussion forums in the XUP. These forums enable you to communicate with other users and XSEDE staff by sharing experiences, asking questions, and giving advice. HELP - Provides options for requesting assistance from XSEDE support staff and reporting security incidents. In addition, an overview is provided of selected resources helpful to using XSEDE resources. ABOUT - Provides an overview of the XUP and its development team. Also provides a form for giving feedback to the development team.

View the XSEDE Resource Monitor
Resources -> Systems Monitor Provides technical and status information for all of XSEDE's resources. The STATUS column indicates whether the system is up or down. If down, can click on status to find when the machine is expected to come back up.

Accessing XSEDE Resources
Authentication Methods Password XUP credentials Site-password One-time password Key-based Single Sign-On Enables logging in once to access all of your allocated resources Connection Methods XUP GSI-SSHTerm GSI-OpenSSH OpenSSH XSEDE Authentication Methods There are two authentication methods supported by XSEDE - password and key-based. Password authentication is the most commonly used method for connecting to XSEDE resources. Depending on the resource to which you want to connect there may be a combination of password authentication methods available. The most consistently supported method on XSEDE allows you to login to all of your resources using your XUP (also called XSEDE-wide) username and password. Some resources also allow you to login using site-local passwords or one-time password tokens. For example,if you are connecting to Blacklight at PSC you can use either your XUP credentials or a site-local password provided to you by PSC. There are reasons for using one over the other and you will learn more about this later in the lesson. With key-based authentication you connect remotely using an encrypted file as a key instead of using a password. To use it you need to setup two keys, a public key to encrypt messages and its corresponding private key to decrypt messages. As with your password, you should not share your private key with anyone. This method is not supported by all XSEDE service providers. Single Sign-On Single Sign-on (SSO) is an access service that enables users to authenticate once and move among multiple systems without needing to repeatedly login to each one. XSEDE's SSO capability is based on Grid Security Infrastructure (GSI), a tool within the Globus Toolkit, used to create XSEDE proxy certificates. A [?]proxy certificate[/?] is a temporary credential that confirms your identity and that you are authorized by a trusted authority to access your XSEDE resources. A 12 hour proxy certificate is automatically generated for you when you authenticate with a method using SSO. You then use this certificate to authenticate to remote login, data transfer, batch job submission, and other services. Connection Methods Given the available XSEDE authentication methods, you can access XSEDE resources using any of the following software programs that enable secure connections to remote systems: XUP GSI-SSHTerm applet GSI-SSHTerm application OpenSSH The diagram illustrates connecting to XSEDE with these programs using the available authentication methods. Your XUP credentials can be used with all three programs. Site-password, OTP, and key-pairs can only be used with SSH. The first two methods are based on GSI-OpenSSH. GSI-OpenSSH works like SSH with the advantage that it uses GSI to authenticate the user and enable SSO. The third method, OpenSSH, requires that you use an OpenSSH client from your workstation. OpenSSH will already be installed on Linux or Mac workstations. For Windows, you will need to install an OpenSSH client. There are several free ones available, such as PuTty. You can do web search to find them. Authentication with a site password is supported by some but not all XSEDE service providers. To find out if a specific resource supports its use, see the System Access section of its User Guide or contact the XSEDE Help Desk. You can login to XSEDE resources using key-based authentication. Key-based authentication uses two keys, a public key to encrypt messages and its corresponding private key to decrypt messages. Like SSO, this method enables you to move seamlessly among resources but you must first distribute your key to each system. Note that service providers differ in the way they let user’s authenticate to their systems. It is important to check the System Access section of your resource’s User Guide to determine how you should authenticate. Using OpenSSH to connect to the XSEDE Login Hub is the recommended method for connecting to XSEDE services. It will be described in a following slide.

XSEDE User Portal GSI-SSHTerm
It’s quick and SSO enabled Requires Java 1.5 or later installed on your workstation Access from My XSEDE > Accounts Click ‘Login’ link for the resource to which you want to connect The XSEDE User Portal provides the capability to quickly login to your resources using a GSI-SSHTerm applet. You must have Java version 1.5 or later installed on your workstation to use it which can be a drawback. It does automatically enable SSO. Given that you are logged into the XSEDE User Portal: Click on the ‘My XSEDE’ tab Click on the ‘Accounts’ link The resources to which you have access will be displayed and you will see a link titled ‘Login’ in the column titled ‘CONNECT.’ Click on the ‘Login’ link of the resource to which you want to connect. The GSI- SSH Terminal applet will log you into the account you selected. (A security warning dialog box may appear. If it does, check the box to accept the risk and click the Run button.)

Moving among resources via XUP
Since SSO is enabled using this login method, you can easily move among your resources. To switch to another resource, select it from the drop-down menu provided above the terminal window.

XSEDE SSO Login Hub An SSO enabled connection point to XSEDE resources
Move among resources using gsissh command The XSEDE Single Sign-On Login Hub (login.xsede.org) is a connection point from which you can access all of your XSEDE resources. To access the hub, SSH to login.xsede.org using your XUP credentials. Use GSI-SSH from the command line to access XSEDE digital services without entering system-specific usernames and passwords. SSH to login.xsede.org using your XUP credentials

Managing your XSEDE files
Where to store files Home directory Scratch directory Archival storage How to move files Command line using globus-url-copy, uberftp, scp, or sftp Globus Online There are essentially two things you need to do to manage your files – store them and move them. All of the XSEDE HPC and Visualization allocations include access to file system space to store your project files and run your applications. This lesson will describe how to use them and how to move files among your storage locations. For information specific to your particular resource, you should see its User Guide. Note: XSEDE also offers long term storage for your project data. This archival storage requires a separate allocation and is beyond the scope of this tutorial. For more information about archival storage and how to receive an allocation see the XSEDE Storage webpage.

XSEDE File Systems Home directory Scratch directory Archival storage
Location specified in the environment variable $HOME. Use to store project files you want to keep long term such as source code, scripts, and input data sets. Not backed up regularly and not purged. Quotas typically set to limit amount of disk space available. Scratch directory Location specified in environment variable varies among resources but will include the term SCRATCH, e.g. $SCRATCH_DIR. Use to temporarily store files produced during application runs. Not backed up and routinely purged. No quotas. Available space depends on cumulative use by all users. Archival storage Must request through allocation process

Your XSEDE Compute Environment
Your default XSEDE compute environment provides access to the compilers, directories, and software you will need to efficiently use your XSEDE resources. Customize it using Modules Your default compute environment provides access to the compilers, directories, and software you will need to efficiently use your XSEDE resources. From CI-Tutor: A default computing environment for each of your allocated resources is automatically set up for you when your XSEDE account is created. This environment provides access to the default compilers, directories, and software you will need to efficiently use your resources. Eventually, you may find that the default environment doesn't meet your specific usage requirements. When that happens, you may customize it by configuring various settings and creating shortcuts for accomplishing tasks you perform regularly. In this tutorial you will learn some basic techniques for customizing your environment. First, you will be introduced to the UNIX login shell and your default XSEDE computing environment. Next, you will learn how to use UNIX commands to explore and modify your default environment. Finally, you will learn how to dynamically set up your environment using the Environment Modules package provided by XSEDE.

Modules Package A command line interface used to configure the shell for an application. Two components: Modulefiles - contain configuration information Module command - interprets modulefiles Pre-written modulefiles available for compilers, mpi implementations Pre-written modulefiles available for common software, e.g. NAMD, GAMESS Modules is a command line interface comprised of two components - modulefiles and the module command. Modulefiles are the basic building blocks of Modules. A module file contains the information needed to configure the shell for an application. Module command interprets the information contained in a modulefile to modify the computing environemnt. It is also used to find information about modulefiles available on the system. Your XSEDE account is setup so that modulefiles configuring a basic environment for your default compilers, tools, and libraries are invoked in the shell startup files at login. These modulefiles are referred to as the XSEDE Common User Environment (CUE). The CUE provides a standard XSEDE-wide environment for setting up the default development and applications packages on each system. You can use these modulefiles as they are provided or modify them to customize your own environment.

Module Commands module unload modulefile
Description module avail [path...] List all modulefiles available on the system. module list List the modulefiles currently loaded in the shell environment. module help modulefile Print help information for the modulefile specified in the argument. module display modulefile Display the changes made to the environment when the specified modulefile is loaded. module load modulefile Interpret the commands contained within the specified modulefile. module switch modulefile1 modulefile2 Remove the environment changes made by modulefile1 and make the changes specified in modulefile2. module unload modulefile Remove the environment changes made by modulefile.

Module Commands Example
% module list Currently Loaded Modulefiles: 1) torque/2.3.13_psc 4) icc/ ) globus/ ) mpt/2.04 5) imkl/ ) xdusage/1.0-r7 3) ifort/ ) psc_path/1.0 % module avail gcc /usr/local/opt/modulefiles gcc/4.3.5 gcc/4.4.6 gcc/4.5.3 gcc/4.6.0 gcc/4.7.2 gcc/4.8.0 gcc/4.8.1 % module load gcc/ ) torque/2.3.13_psc 5) imkl/ ) mpfr/ ) mpt/2.04 6) psc_path/1.0 10) gmp/ ) ifort/ ) globus/ ) mpc/ ) icc/ ) xdusage/1.0-r7 12) gcc/4.8.1 % module unload gcc Demonstrate various module commands.

Moving Files - Globus Online
A fast, reliable, and secure file transfer service geared to the big data needs of the research community. Moves terabytes of data in thousands of files Automatic fault recovery Easy to use No client software installation Consolidated support and troubleshooting Supports file transfer to any machine Accounts are free -

Globus Online Dashboard

Globus Online File Transfer

Read/write data from compute nodes to Scratch directory.
Running Jobs Overview When you connect to a resource, you are on a login node shared by many users. Researcher Command Line Login Batch Script Commands for code execution, copy input files to scratch,… Specify number/type of nodes, length of run, output directory, … Data Job Login Nodes Run jobs by submitting your batch script to the compute nodes using the "qsub" command. Store project files Such as source code, scripts, and input data sets to Home directory. Use for tasks such as file editing, code compilation, data backup, and job submission. Compute Nodes Home Scratch File System Data Your job is submitted to a queue and will wait in line until nodes are available. Queues are managed by a job scheduler that allows jobs to run efficiently. Read/write data from compute nodes to Scratch directory.

Login nodes When you login, you are in the login node.
Login nodes should only be used for basic tasks such as file editing, code compilation, data backup, and job submission. Login nodes should not be used to run production simulations. Production work should be performed on the system's compute resources.

Batch Jobs Number/type of nodes you need. How long you need to run.
Compute jobs *cannot* be run on the login nodes. All XSEDE compute resources use some form of batch scheduler. There are several batch systems in use, but all work basically the same way. Create a job script specifying: Number/type of nodes you need. How long you need to run. Where your output files should be written to.

7/6/11 Create a script Example script for running an MPI job on Blacklight at PSC. Actual commands are site and machine specific, but they follow general principles. Needs to be modified to run on other XSEDE machines. 29

Submitting/Manipulating Batch jobs
Batch system should be used to run your job. Do not run on the login nodes. Submit the script that you have created: Actual commands are machine specific, but they follow general principles. qsub jobname qstat –a qstat -u username qdel jobid man qsub 30

Batch command examples
qsub amber.job qstat –a Job ID Username Queue Jobname SessID NDS Tasks Memory Time S Time user1 batch job :00 R 02:28 user2 batch run :30 Q -- user3 batch STDIN :00 R 00:10 user2 batch jobL :00 R 00:09 user4 batch STDIN :30 R 00:06 user1 batch amber :10 R :00 qdel 29668 After job runs: user1 should get file amber.job.o29898 with output/errors (log file)

Never made it to the queue: Job not accepted by the queue:
Why has my job not run? Never made it to the queue: Job not accepted by the queue: Core requests on Kraken must be a multiple of twelve. You have requested an invalid number of cores ( 8 ). Please resubmit the job requesting an appropriate number of cores. Solution: Change the job script to request correct number of cores or memory for the resource.

My job did not complete Check the log files created job.e job.o.89890 One common problem: job run out of CPU time. Check the job script: time and memory requested, directory where you are writing files to. Do the input files exist in the directory where you specified? Do you have permission to use software? Waiting a very long time in the queue… If all fails… submit a ticket

Queue structure: job priority
Job priority in the batch queues is based on the number of cores and wall clock time requested. Differs by site. Examples: Blacklight: approx. FIFO system. (Mechanisms in place to prevent a single user from dominating the batch queue and to prevent idle time on the machine). Flexible time request can improve your turnaround. Packing small jobs. Kraken: Priority to jobs that request large number of cores (over 32K processors) (except capability and dedicated jobs). Jobs with smaller core counts run on other systems (Trestles). However, they can run effectively on Kraken as backfill. Backfill: While the scheduler is collecting nodes for larger jobs, those with short wall clock limits and small core counts may use those nodes without delaying the start time of the larger job.

Queue structure: Backfill, Flexible time
Backfill: While the scheduler is collecting nodes for larger jobs, those with short wall clock limits and small core counts may use those nodes without delaying the start time of the larger job. The system will not start a job that will not finish before the system maintenance time begins. Ex. Will run a 512 core jobs next. Waiting to finish a 256 core job that will take 4 more hours. Can run jobs that add up to 256 cores and will finish in 4 hours. To take advantage of this, request flexible walltime in your job script. A flexible walltime request can improve your job's turnaround in several circumstances.

Improving job turnaround
Try to be as accurate as possible in estimating the walltime request for your job. Asking for more time than your job will actually need will almost certainly result in poorer turnaround for your job: Asking for the maximum walltime you can ask for a job will almost always result in poorer turnaround. Use flexible walltime

Improving job turnoaround: Flexible time
-l walltime_min=HH:MM:SS -l walltime_max=HH:MM:SS Using flexible walltime limits increases the opportunity for your job to run on backfill blades. Example: if your job requests 64 cores and a range of walltime between 2 and 4 hours and a 64-core slot is available for 3 hours, your job could run in this slot with a walltime request of 3 hours. If your job had asked for a fixed walltime request of 4 hours it would not have been started.

Flexible time If the system starts one of your jobs with a flexible walltime request, it selects a walltime within the two specified limits. This walltime will not change during your job's execution. Can determine the walltime your job was assigned by qstat –f $PBS_JOBID | grep Resource_List.walltime Your program should begin writing checkpoint files sufficiently in advance of the walltime so that the file writing is completed when the limit is reached. Save time to allow your job to transfer files after your program ends but before your job ends. timeout --timeout=$PROGRAM_TIME -- mpirun -np 32 ./mympi

Packing your jobs Running many small jobs places a great burden on the scheduler and is probably inconvenient for you. Pack many executions into a single job, which you then submit to PBS with a single qsub command.

Packing your jobs Run each program execution in the background and place a wait command after each execution. Sample job to pack serial executions: #!/bin/csh #PBS -l ncpus=96 #PBS -l walltime=5:00 #PBS -q batch dplace -c 0 ./myserial1 < serial1.dat & dplace -c 32 ./myserial2 < serial2.dat & dplace -c 64 ./myserial3 < serial3.dat & wait

Packing your jobs, serial or MPI:
dplace -c 0 ./myserial1 < serial1.dat & dplace -c 32 ./myserial2 < serial2.dat & dplace -c 64 ./myserial3 < serial3.dat & wait The dplace command insures that each execution will run on its own set of 32 cores. The executions will run concurrently. Same approach using the dplace command can be used to pack MPI executables. .

Packing your jobs: OpenMP
To pack OpenMP executables, replace the dplace command with the omplace command. Sample job to pack OpenMP executables: omplace -nt 32 -c 0 ./myopenmp1 < myopenmp1.dat & omplace -nt 32 -c 32 ./myopenmp2 < myopenmp2.dat & omplace -nt 32 -c 64 ./myopenmp3 < myopenmp3.dat & omplace -nt 32 -c 96 ./myopenmp4 < myopenmp4.dat & wait

Need help? Reporting and Tracking Issues
portal.xsede.org  Help Submit ticket portal.xsede.org  My XSEDE  Tickets View past tickets (both open and closed) Can also or call , at any hour (24/7)

Discussing your problems… User Portal: User Forums
The User Forums are a great place to ask questions, get help, or discuss ideas about XSEDE.

More “helpful” resources
xsede.orgUser Services Resources available at each Service Provider User Guides describing memory, number of CPUs, file systems, etc. Storage facilities Software (Comprehensive Search) Training: portal.xsede.org  Training Course Calendar On-line training Get face-to-face help from XSEDE experts at your institution; contact your local Campus Champions. Extended Collaborative Support (formerly known as Advanced User Support (AUSS))

Thanks for listening and welcome to XSEDE!

XSEDE New User Tutorial

Similar presentations

Presentation on theme: "XSEDE New User Tutorial"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

XSEDE New User Tutorial

Similar presentations

Presentation on theme: "XSEDE New User Tutorial"— Presentation transcript:

Similar presentations

About project

Feedback