All use of Scientific Computing and Data resources in publications and presentations must acknowledge Mount Sinai’s CTSA funding award. Click here

Scientific Computing and Data / High Performance Computing / Request an Account / User Needing Project Allocation

Request an Account

Select the account type that best fits your access requirements:

Connecting to Minerva

How to log in

Questions? hpchelp@hpc.mssm.edu

User Needing Project Allocation

Mount Sinai HPC offers two separate clusters, each with its own allocation process. Select the cluster appropriate for your project’s data type and compliance requirements:

General Purpose

Minerva

Standard HPC cluster for general research computing. Suitable for most computational workloads without controlled-access data requirements.

Minerva Allocation Policy

Restricted / Controlled Data

Minerva-Res

Secure, NIST SP 800-171-compliant cluster for projects involving NIH controlled-access data or CMS RIF/LDS data paired with a Minerva HPC DMP SAQ. Requires an active Data Use Agreement (DUA).

Minerva-Res Allocation Policy
·
Docs

Rolling Allocation Process & Annual HIPAA ReviewView / hide details

Effective 2021 — Rolling Allocation Process: Based on user feedback, we moved to a rolling allocation model. This means:

  1. NO renewal allocation requests needed for existing projects.
  2. NO annual allocation request due date for new projects — the usual May allocation cycle has been eliminated.*

* We may reach out to project PIs/managers to update critical information or fill in new entries as needed from time to time.

Annual HIPAA Review Required: All users must review and agree to the HIPAA policies by December 31 every year, per compliance requirements.

Minerva Allocation Policy General ClusterView / hide details
Minerva Allocation Request Form
  1. New project on Minerva — Complete the Minerva Allocation Request Form. New allocation requests will be reviewed by the allocation committee; notices of award will be emailed to PIs and their delegates.
  2. Changes to an existing Minerva allocation (storage quota, delegate(s), etc.) — Log back into your original allocation form using your return code and update the relevant fields. We will update your allocation on Minerva accordingly.
  3. A Minerva project will be deactivated if any of the following occur:Show / hide list
Minerva-Res Allocation Policy Restricted ClusterView / hide details

Minerva-Res is a hardened HPC environment designed and operated in accordance with NIST SP 800-171 Rev. 3 security requirements. It is dedicated to projects involving genomic data from the NIH Controlled-Access repository (or equivalent CUI-like protections). For full environment details see the Minerva-Res documentation.

 

Important: User accounts on Minerva-Res can only be created after a project has been formally approved. An active Data Use Agreement (DUA) managed through the institution’s GCO is required before access is granted. External collaborator accounts are not currently supported on Minerva-Res.
Minerva-Res Allocation Request Form
Minerva-Res Documentation

  1. New project on Minerva-Res — Complete the Minerva-Res Allocation Request Form.

    • PI Requirement: The PI must review and acknowledge the Annual Minerva Restricted Supercomputer Policies and Procedures. After logging, navigate to Minerva-Res Forms, and select Minerva Restricted Supercomputer Policies and Procedures.
    • Next Steps: Requests are reviewed by the HPC team; you will be notified of approval status by email. Do not request individual user accounts before the project has been approved.
  2. Data Use Agreement (DUA) required — An active DUA managed by the GCO is required before any project access is granted or maintained. Contact the Grants and Contracts Office (GCO) to initiate or renew your DUA. See the GCO DUA SOP (PDF) for details.
  3. Changes to an existing Minerva-Res allocation — Log back into the Minerva-Res Allocation Request Form using your return code and update the relevant fields.
  4. Access will be deactivated if any of the following occur:Show / hide list
    • The account is no longer associated with an active, approved project.
    • The project’s Data Use Agreement (DUA) expires or is no longer active.
    • Employment or affiliation with the institution ends.
    • A policy or DUA violation occurs.
    • Project completion.
Log Back to the Allocation Form for Changes?View / hide details

Both forms support return access so PIs and delegates can modify or supplement a request without starting over.

 

The steps below apply to both the Minerva and Minerva-Res allocation forms:

  1. Save your return code immediately after submitting — it is the only way to modify your form without starting a new request. The code is shown on screen and can be emailed to you on completion.
  2. To return later, click the “Returning?” box in the top right of the form and enter your code.
  3. You can save and continue at any point if you cannot complete the form in one session.
  4. Once completed, request an email confirmation with the filled form as a PDF attachment for your records.
Annual Compliance RequirementsView / hide details
Cluster Annual Requirement Deadline / Frequency Reference
Minerva Review and agree to the HIPAA policies December 31, every year HIPAA Policy
Minerva-Res Maintain active DUA through GCO; HIPAA review also required Per DUA expiration + December 31 (HIPAA) GCO DUA SOP · HIPAA Policy