A desktop app for working with UCI's HPC3 cluster without living in the terminal:
- Job Management — view, submit, and cancel Slurm jobs
- Node Status — live CPU / memory / GPU usage across nodes
- VSCode — launch one or multiple remote VSCode sessions (each writes its own
~/.ssh/configentry, soRemote-SSH: Connect to Host…just works) - Account Balance — your SU balance per account
Sign in once with your UCInetID + Duo; the app installs an SSH key so every later launch is password-less.
Renamed from
UCI-ClusterManager. Originally by Song Liangyu and contributors; maintained by the Molloi Lab. GPL-3.0.
Grab the latest installer from the Releases page:
| Platform | File |
|---|---|
| macOS | HPC3-Launcher-<version>-macos.dmg |
| Windows | HPC3-Launcher-<version>-windows-setup.exe |
| Linux | HPC3-Launcher-<version>-linux.deb |
On Windows, double-click the setup.exe to install (Start Menu shortcut + uninstaller included).
The macOS build is not yet notarized by Apple, so the first launch needs one extra step. This is a one-time thing.
-
Open the
.dmgand drag HPC3-Launcher into Applications. No admin rights? Drag it into~/Applicationsin your home folder instead (create that folder if it doesn't exist) — it runs the same. -
Clear the download quarantine flag (this is what lets it open without the "Apple cannot check it for malicious software" error). Open Terminal and run (adjust the path if you used
~/Applications):xattr -dr com.apple.quarantine "/Applications/HPC3-Launcher.app" -
Open HPC3-Launcher from Applications normally.
Prefer not to use Terminal?
Double-click the app; when macOS blocks it, go to System Settings → Privacy & Security, scroll to the message about HPC3-Launcher, and click Open Anyway. Then open the app again and choose Open.
Once the project has an Apple Developer ID configured (see
docs/SIGNING.md), releases are notarized automatically and this step goes away — users just double-click.
The Windows build installs per-user and needs no admin rights — it works on lab machines where you don't have administrator access.
- Download and double-click
HPC3-Launcher-<version>-windows-setup.exe. It installs to your user profile (no UAC/admin prompt) and adds a Start Menu shortcut. - The installer (and first app launch) is not yet code-signed, so Windows SmartScreen may show "Windows protected your PC." Click More info → Run anyway. This is a one-time thing.
Once Azure Trusted Signing is configured (see
docs/SIGNING.md), releases are signed automatically and this warning goes away.
# Option A: conda (matches CI)
conda env create -f scripts/environment.yml # creates env "hpc-mgmt"
conda activate hpc-mgmt
# Option B: venv
python3 -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
python hpc3_launcher/main.pyReleases are automated:
- release-please watches
mainand keeps a "Release PR" open that bumps the version and updatesCHANGELOG.mdfrom Conventional Commits (feat:,fix:, …). - Merging that PR tags
vX.Y.Zand publishes a GitHub Release. - The build-release workflow then builds the macOS
.dmg, Windowssetup.exe(Inno Setup installer), and Linux.deband attaches them to that release. - Every release is launch-tested on all three OSes before it's trusted. A
verify-<os>job re-downloads the published installer, installs/extracts it exactly as a user would, and launches the frozen app headlessly (QT_QPA_PLATFORM=offscreen). The app builds its full main window, confirms the Qt event loop starts, and writes a marker; the job fails if it doesn't — so a package that can't actually run (the old Windows failure mode) turns the release red instead of shipping broken.
To set up zero-friction (notarized) macOS builds, see docs/SIGNING.md.
GNU GPL v3.0 — see LICENSE.