On this page:
- Introduction to TAMU Computing Accounts
- Getting a TAMU NetID for Remote Collaborators
- NetID Annual Renewal for Remote Collaborators
- Getting a Mitchcomp Membership
- Getting an HPRC Account
- Annual HPRC Account Renewal
See also:
WARNING: This documentation is for MITCHCOMP group members. If you are not a Mitchcomp member, please go to HPRC New User Information or User Services guides.
Introduction to TAMU Computing Accounts
There are two types of accounts needed for each MitchComp users:
- The campus-wide “NetID”: Which is associated with your A&M e-mail address, student or staff ID, and so on
- HPRC Computing Account: Which gets you access to the login and compute nodes, the HPRC OnDemand Portal, home and scratch directories, etc.
In order to use HPRC, you must have both accounts set up and active, and the accounts must be renewed annually before 1 September.
If you are a Texas A&M student, faculty, or staff, you should already have a NetID.
- If you have a NetID skip to “Getting an HPRC Account” If you don’t have a NetID and you are a Texas A&M student, faculty, or staff, you need to claim it at Aggie Account Gateway using these instructions: Activating/Creating a NetID IT Self-Service Webpage
Getting a NetID for Remote Collaborators
Before we can get you a NetID you need a Sponsor, typically Prof. David Toback, and you need an official affiliation with both the Department and the University which will need to be renewed yearly.
If you want to use Mitchcomp resources at the HPRC, you probably want it to be Toback for administrative purposes so he can handle all the paperwork even if you are working with someone else in the department.
To request a new account or account renewal, the remote collaborator must send a copy of their CV to their Texas A&M PI or Sponsor. It is the responsibility of the Texas A&M PI to send the CV to Carla Harris <cdharris@tamu.edu>. From here, the Texas A&M PI will be asked to fill out informational forms.
The ONLY things that the scholar should be providing are their CV and identification. The PI/Sponsor should be providing/filling out any other required internal forms.
-
Claim your NetID after you have been approved for it:
It usually takes several weeks to get the invitation approved. Then, it usually takes about 5 days for the Texas A&M NetID Identity Manager System Registration Authority to process the NetID request. Once it is done you need to follow these three steps to get your NetID and UIN (we recommend writing both down to save them for these steps as well as for your yearly renewal):- When you receive a notification email from Texas A&M Identity Management indicating that the account has been created, you will need to call 979-862-4300 to claim your UIN. They will ask you to provide the following: (a) the keystone number provided in the email, (b) your name, (c) your date of birth. An Identity Manager assistant will attend your call. If you have any problems contact Mitchcomp Help (mitchcomp_help@physics.tamu.edu) and we will get things sorted out.
- Claim your NetID: Go to http://gateway.tamu.edu/. Click Claim NetID. Enter new UIN and select birthdate. Click Log in. On the next screen, enter your chosen NetID and click Submit, next create a password.
NetID Annual Renewal for Remote Collaborators
Each year you will get an email from Account Life Cycle Monitor (with email address: alc-monitor@tamu.edu) which will ask you if you want to renew your NetID. You should send an Email to Prof. David Toback (toback@physics.tamu.edu) saying if you want to renew you account or not.
After your confirmation, the process of renewing your NetID is similar to the above,
The Mitchcomp Help team will no longer facilitate the adding/renewing of remote collaborator accounts.
To request a new account or account renewal, the remote collaborator must send a copy of their CV to their Texas A&M PI or Sponsor. It is the responsibility of the Texas A&M PI to send the CV to Carla Harris <cdharris@tamu.edu>. From here, the Texas A&M PI will be asked to fill out informational forms.
The ONLY things that the scholar should be providing are their CV and identification. The PI/Sponsor should be providing/filling out any other required internal forms.
Getting a Mitchcomp Membership
If you are a Remote Collaborator, and you followed the instructions to get a NetID, you don’t need to do anything and you will be a Mitchcomp member automatically in the process.
You should be able to access mitchcomp directory if you are a mitchcomp member. If not, you can follow these steps (for both group members and remote collaborators) to request for a membership:
- Fill in our unofficial “Basic Information” form: Link to the form. Make sure you have the updated form (last update was at 8/10/2020, and you should be able to see it as the header of the form)
- Attach the “Basic Information” form to an email and send it to Mitchcomp Help (mitchcomp_help@physics.tamu.edu)
Getting an HPRC Account
WARNING: This documentation is for MITCHCOMP group members. If you are not a Mitchcomp member, please go to HPRC New User Information or User Services guides.
Go to HPRC Policies webpage to read the relevant policies.
See also the Cluster Policies webpage and read the small text (Terra and Curie have the exact same policies too). They are important as the text contains data storage policies.
It is important to read the Resource Allocations Policy as it will be needed in next step.
In order to get an HPRC account, you need to fill an application form at https://hprc.tamu.edu/apply
You will need to enter your TAMU account. If you are a student (not a research associate) choose the ‘student‘ option and apply for a ‘basic‘ account.
It will ask for your PI’s email, phone, and NetID but all mitchcomp users should list David Toback as their “PI” for HPRC, so that we can easily allocate more CPU to you, as well as provide unified support to all Mitchell Institute users. On the HPRC application form, list:
David Toback, toback@tamu.edu, NetID: toback, phone (979) 218-7130
This will make you a part of Mitchcomp group so we can easily allocate more CPU to you
Now you need to fill in a simple form. As a ‘research description’ example, here is something a member of Dr. Toback’s group might write (DO NOT copy the text below directly; describe your own research project. You also DO NOT need to mention Dr. Toback here if you’re in another group; give your actual PI’s name):
I am working under Dr. Toback(toback@tamu.edu) in CDMS experiment group. CDMS experiment studies the physics of the dark matter detector. Detector Monte Carlo software has been developed by Super CDMS to simulate phonon and charge propagation within the detectors in addition to detector read out (for both charge and phonons). I will contribute to CDMS by simulating the response of the dark matter detector to known sources. The results from this monte carlo simulation will be used to analyze real experiment data. We expect to find evidence of dark matter, possibly in the form of WIMPs. Computational tools I will use: • Running i-Python (interactively or submitting a script) • processing CDMS data (CDMSbats) • running SCDMStools for matlab (matCAP) • Root by CERN • Geant4 • I also write my own software in shell, C, and python.
You will receive an e-mail when your account is created (probably within a day or two). It will be from help@hprc.tamu.edu, and probably in your NetID@tamu.edu address. Be sure to check your spam folders if you can’t find it.
After you got connected to TAMU VPN (connect.tamu.edu), or if you were on campus already, use the following command:
$ ssh YOUR-NET-ID@terra.tamu.edu (if you want to connect to Terra) $ ssh YOUR-NET-ID@grace.tamu.edu (if you want to connect to Grace)
Then you need to enter your howdy portal (NetID) password.
After that you need to choose a method for the two-step authentication. If you are not enrolled yet, enroll at https://gateway.tamu.edu/duo-enroll/
Terra has 3 login nodes: terra1~3
Grace has 5 login nodes: grace1~5
It’s a policy of HPRC NOT TO USE MORE THAN 8 CORES ON THE LOGIN NODES.
You CANNOT USE SUDO COMMANDS ON HPRC. To install software, you need to contact HPRC help.
Login sessions that are idle for 60 minutes will be closed automatically.
Processes run longer than 60 minutes on login nodes will be killed automatically.
People working in the Toback Group will need access to the Toback Mitchcomp Unix Group. This will give you access to the shared directories on the HPRC. In order to get your NetID added to the group, refer to the following instructions:
- Email help@hprc.tamu.edu cc’ing Dave Toback (toback@tamu.edu) and Mike Kelsey (kelsey@slac.stanford.edu)
- Make sure to include something like the following in the email:
“Howdy, my name is <your name> and I am Dave Toback’s MitchComp group. I am requesting to be added to the MitchComp Unix Group on Grace. Dave Toback and/or Michael Kelsey can approve this request if needed. My NetID is <your-net-id>.”
- Make sure to include something like the following in the email:
- To check your current group memberships, use the linux command: “groups <username>”
- To see all users in the mitchcomp group, use the linux command: “grep mitchcomp /etc/group”
Annual HPRC Account Renewal
Each year, HPRC closes each fiscal year at September 1st. For all users, regardless of whether you are TAMU person or a Remote Collaborator, this means that you can no longer submit jobs using your allocations after August 31, 2020. Therefore, each year about 2 weeks before September 1st (or sooner) you should submit your applications for next fiscal year.
The procedure to renew your account is the same for all users. To do so, you’ll use the same application form as described at Step 2. The application process is relatively like Step 2 even though it looks like you are creating a new account
-
- If you are a Remote Collaborator, first make sure your NetID is renewed! You can use NetID Annual Renewal for Remote Collaborators instructions to do that!
- Go to application form and login using your NetID
- Your user information should’ve already been filled in. Make sure they are correct and click on “Next” button
- In the “Renew using information from a previous High Performance Research Computing application” section, click on “Renew for FYXXXX” (replace XXXX with the NEXT year!)
- All the information should be already filled in. Double check all of them. Mitchcomp users should make sure that their allocation and PI have been listed right:
- The MitchComp users should do a renewal for the same “basic” allocation they got this year (5000 SU).
- The MitchComp users and Mitchcomp group should make sure they are listed as toback’s PI group for SU allocations
Mithcomp users should send an e-mail to Mitchcomp Help (mitchcomp_help@physics.tamu.edu) when they have renewed their HPRC account to help us to keep track of our group users to support them better.
You will automatically get 5000 SU. If you expect to use more than your 5000 SU of personal allocation, please send an e-mail to Mitchcomp Help (mitchcomp_help@physics.tamu.edu) with your guess of what you need for the year (and why) so we can transfer what you expect from the MitchComp group allocation into your account.
HPRC Setup Guide (Grace and Terra)
Here are some suggestions for setting up and organizing your HPRC (Grace and Terra) accounts for convenience, and for some shared access with the rest of the MitchComp group.
Directory Permissions:
At HPRC, user directories are configured so that no one can access your files other than yourself. Since we work in a more collaborative group
structure, we suggest that you make your /scratch space readable for the whole MitchComp group. You can do so by running the following command:
After you got connected to TAMU VPN (connect.tamu.edu), or if you were on campus already, use the following command:
$ chgrp -R mitchcomp /scratch/user/<username> $ chmod -R g+r /scratch/user/<username> find /scratch/user/<username> -type d | xargs chmod g+xs
You may choose to set “world readable” by using “go+r” and “go+xs”, but that’s not required. If you want to set your /home area similarly, use the same commands, but with /home/user/<username>.
Additional Directories:
Keeping your data organized will become important as you start working. In your home directory, create a directory where you can put configuration
scripts and general-purpose personal utilities as you need them:
$ mkdir $HOME/bin
Software packages and data should go in your /scratch area, which is much larger than /home.
$ mkdir /scratch/user/<username>/software $ mkdir /scratch/user/<username>/data $ cd $HOME $ ln -s /scratch/user/<username>/software $ ln -s /scratch/user/<username>/data
Environment
Your .bash_profile should contain the minimal setup you need for your environment under all conditions. For us, that means access to the shared /scratch/group/mitchcomp software. Add the following lines at the end.
$ export PATH=${PATH}:${HOME}/bin:/scratch/group/mitchcomp/bin source module-setup # This is in mitchcomp/bin
If you are working on a single experiment, you can also load the toolchain appropriate for that experiment, but don’t load the full environment:
$ module load foss/2022b # For CDMS users or $ module load foss/2020b # For DUNE/QPix users
You’ll need access to Git, Python, and possibly your favorite editor if you don’t use `vim`. You can add these to your .bash_profile as well:
$ export SCRATCH=/scratch/user/<username> $ export MITCHCOMP=/scratch/group/mitchcomp
You can put these in your .bash_profile as well.