# Getting Started with Blackwell ## Using Blackwell You can use [ssh keys](../connect/ssh_keys) to login to Blackwell (x500@blackwell.msi.umn.edu). To login, use your HST Active Directory (AD) password. Currently, forwarding (e.g., SSH with X11/Wayland forwarding) is disabled on interactive Blackwell sessions to prevent unwanted data egress. MSI is planning for an interactive GUI capability in the future. If you have a defined workflow on Agate, you can containerize it and port it to Blackwell. ## Cluster Partitions | Partition | Nodes | Cores (Per Node) | RAM (GB) | Scratch (TB) | Max Runtime (Hours) | Max # of Nodes | |-----------|-------|------------------|----------|--------------|---------------------|----------------| | Batch | 16 | 128 | 512 | 1.5 | 96 | 4 | | HighMem | 4 | 128 | 2000 | 1.5 | 96 | 1 | | A100 | 4 | 24 | 384 | 1.5 | 96 | 1 | ### Transferring Data into the Cluster via SFTP All data transferred into blackwell are processed through a 'Data Transfer Node' that first scans the data before allowing you to move it into your project space. This host is specifically configured to support high-throughput SFTP transfers to get data into the cluster safely. For more information on using the DTN to put data into Blackwell, refer to the [Data Transfer Nodes Page](./data_transfer_nodes.md) This host is specifically configured to support high-throughput SFTP transfers to get data into the cluster efficiently. Upload.opts should generally go last in case the SFTP connection unexpectedly disconnects partway through. Remember to use a device that conforms to University Information Security standards for ePHI. If you need assistance with this, please reach out to [OIT's Help Desk](mailto:help@umn.edu). ### Supported SFTP Clients You can connect to transfer.msi.umn.edu using command-line tools or graphical clients. Tested clients include: - sftp (Command Line): Included with the standard ssh package on all MSI systems - [FileZilla](https://filezilla-project.org/) (GUI): A graphical file transfer client for Windows, macOS, and Linux ### Destination Paths & Sensitive Data Compliance When choosing a target directory on the cluster, ensure you adhere to MSI's data classification guidelines: - **Home Directory (~):** Intended for individual scripts, small configuration files, and non-sensitive user data - **Project Space (/projects/regulated/[your-project-name]):** The primary storage location for shared project data, large datasets, and sensitive files ```{note} If your data is restricted, the project space path will be: **/projects/restricted/[your-project-name]** All data requiring compliance with HIPAA will be in the 'restricted' project space ``` #### PHI and Controlled Data Guidelines - **Sensitive & Regulated Data:** Project data that contains **Protected Health Information (PHI)** or other contractually/regulatorily controlled data **must** be transferred to the project directory allocated for that data by MSI Contractually regulated and/or ePHI data is prohibited from being stored in your home directory.