Before you use HiPerGator

Read the usage policy first

Do not run DeepSeek or other models covered by UFRC's policy on HiPerGator. Read the current LLM usage policy before using the department allocation.

Quick path

Account request and department access

1

Identify your professor

Know the specific professor you work with so you can name them in Comments.

2

Create a key pair

Generate an SSH key pair locally and keep the private key private.

3

Submit the appropriate account request

Use your institutional credentials when federation is available; otherwise ask UFRC Support which account path applies.

4

Verify department access

After approval, confirm access to the department group or request membership for an existing account.

Already have a HiPerGator account? Skip the new account request and request department-group membership instead.

Choose your identity path

Use your own institution's identity

Applicant from another federated institution

If your home institution appears in the UFRC federated liaison list, select it and use that institution's credentials and email.

Applicant without federated access

Contact UFRC Support and the FSU professor you work with before applying. UFRC will confirm the correct account path for your institution.

Department allocation

What the department allocation provides

This shared allocation supports approved users across the FSU Computer Science Department.

128

NCPU

24

NGPU

20 TB

Blue storage

8 TB

Orange storage

NCPU and NGPU are UFRC allocation units; Blue and Orange are storage systems. See the current UFRC documentation for their definitions and usage limits.

  • The current allocation period is March 12, 2026 through March 11, 2031.
  • The department group for this allocation is fsu-compsci-dept.
  • The allocation does not create an account or approve an individual user automatically.
  • Confirm your approved storage path before moving data.
  • If you already have a HiPerGator account, request department-group membership instead of submitting another account request.

Before applying

Have these details ready

If Dr. Yu or fsu-compsci-dept is not available in the form, contact the department administrator or UFRC Support instead of selecting another sponsor or group.

SSH public key

Create the key before opening the form

Linux or macOS

ssh-keygen -t ed25519 -C "your_institutional_email" -f ~/.ssh/id_ed25519_hipergator
cat ~/.ssh/id_ed25519_hipergator.pub

Windows PowerShell

ssh-keygen -t ed25519 -C "your_institutional_email" -f $env:USERPROFILE/.ssh/id_ed25519_hipergator
type $env:USERPROFILE/.ssh/id_ed25519_hipergator.pub

Upload the file ending in .pub. Never upload or send the private key. The public key may be required even when you plan to start with a browser-based interface.

Submit the request

Identify your faculty collaboration in Comments

  1. Open Request HiPerGator Account.
  2. Use Federated Account Request if your institution participates in federation. Otherwise, ask UFRC Support which account path applies.
  3. Enter your legal name, institutional email, and actual organization. Select Dr. Weikuan Yu in the Group Sponsor field for fsu-compsci-dept, and use cs-hipergator@fsu.edu as the sponsor contact email.
  4. In Comments, state the full name of the professor you work with. Do not write only "Computer Science Department."
  5. Paste the requested information or upload the public key as directed by the form.
  6. Open the confirmation email, accept the terms and conditions, and complete any remaining verification step.
  7. Wait for sponsor approval. Account creation usually takes two to three business days after approval.

Comments template

I am a [FSU student/staff member OR student/researcher at HOME INSTITUTION] working with Professor [FULL NAME]. I am requesting HiPerGator access to fsu-compsci-dept for [PROJECT, COURSE, OR PURPOSE]. My institutional email is [EMAIL].

Replace every bracketed field. External applicants should use their home institution and institutional email.

After approval

Verify your account and department access

Complete any required onboarding or training, then test an interactive login and a small job.

SSH login

ssh -i ~/.ssh/id_ed25519_hipergator YOUR_HIPERGATOR_USERNAME@hpg.rc.ufl.edu

Username

Use the HiPerGator username from your account email. It may differ from the local part of your institutional email address.

Network access

Follow the current UFRC network guidance. Federated SSH access may require eduVPN before connecting.

Allocation check

Confirm your default group, Slurm account, storage path, and the department group you were approved to use.

Department membership

Add an existing account to fsu-compsci-dept

  1. Confirm that your HiPerGator account is active and record your exact username.
  2. Open a request at UFRC Support asking to add your username to fsu-compsci-dept.
  3. Include your full name, institutional email, home institution if applicable, the professor you work with, and the purpose of the request.
  4. Wait for department approval through UFRC Support.
  5. After confirmation, verify the group and Slurm account on HiPerGator before submitting production work.

FAQ

Common questions

Which professor should I name?

Name the professor whose project, course, or research work you are joining. This may be different from the Group Sponsor. If you work with more than one professor, list the primary contact first.

Do I need a new account to use the department allocation?

No. If your account already exists, request group membership through UFRC Support and provide your existing HiPerGator username.

What if the department group is not visible?

Contact the department administrator or UFRC Support and state that you are requesting access to fsu-compsci-dept. Do not select another sponsor or group.

Can an external student use this guide?

Yes. Use a federated home-institution account when available. If federation is unavailable, ask UFRC Support which account path applies. The FSU professor you work with should confirm the work before you apply.

Official references

Use UFRC documentation for current policy