Repository navigation
Windows support, solver choice in the interface, NVIDIA builds - #4
Merged
Merged
Conversation
Windows:
- hypre threads on Windows: MSVC's /openmp:llvm puts it on LLVM's OpenMP
runtime with MKL (856k-equation beam: CPU AMG solve 104 s -> 62 s).
- build-solver.py --cuda builds on Windows (solver-env-windows-cuda.yml);
hypre builds with Ninja there.
- tests/desktop.mjs runs on Windows and Linux too.
Solver choice:
- Studies choose direct or iterative, each the best this computer has
(PARDISO/SPOOLES; hypre BoomerAMG, else incomplete Cholesky). CPU or
GPU is a per-machine preference (?device=gpu), offered where a GPU
build works. GET /api/solvers reports what is available, and the
Mesh + Solver panel names the solver a choice runs.
NVIDIA builds:
- --cuda builds a second helper, sprung-solve-gpu, beside the CPU one.
Without an NVIDIA GPU it runs PARDISO alone, and the engine uses the
CPU helper's BoomerAMG.
- CUDA's own memory pool replaces Umpire (unpinned download, no MSVC
build); no cuBLAS or cuSOLVER; the CUDA runtime is linked statically.
- bundle-runtime.py --gpu and npm run package:{win,linux}:nvidia make
the NVIDIA installers, with NVIDIA's CUDA license.
- CI builds the NVIDIA editions for Windows and Linux, caching hypre's
CUDA build (--hypre-cache).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CUDA 12.9's nvcc refuses MSVC 19.50 and later, which the windows-latest runner's Visual Studio 2026 has. build-solver.py now picks the newest toolset older than 14.50 from any Visual Studio installed for the GPU build, and falls back to -allow-unsupported-compiler, saying so, when there is none. The hypre cache key names the toolset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gets the hypre/GPU work from ffc2e80 running on Windows, adds a direct/iterative and CPU/GPU solver choice to the interface, and builds NVIDIA editions of the Windows and Linux apps in CI.
Windows
/openmp:llvm, so hypre and MKL share LLVM's OpenMP runtime (libomp.dll); before, hypre ran on one thread. On an 856k-equation beam, CPU AMG setup went from 19.1 s to 5.3 s and CG from 54 s to 26 s, so a whole solve takes 62 s, against 114 s for PARDISO.--cudaworks on Windows, from a newnative/calculix/solver-env-windows-cuda.yml(CUDA 12.9).tests/desktop.mjsnow runs on Windows and Linux, not only macOS.Solver choice in the interface
?device=gpu, and applies to the iterative solver only.hypre 3.2.0 CG with BoomerAMG, on the GPU (NVIDIA GeForce RTX 3070).GET /api/solversreports what's available (worker commandsolvers, asked once per service).NVIDIA builds
build-solver.py --cuda ARCHbuilds a second helper,solver/sprung-solve-gpu/, beside the CPU one.cudaMallocAsync) on both platforms, replacing Umpire. Umpire was downloaded unpinned and doesn't build with MSVC.bundle-runtime.py --gpuandnpm run package:{win,linux}:nvidiaproduceSprung-FEA-Setup-<v>-NVIDIA.exeandSprung-FEA-<v>-x86_64-NVIDIA.AppImage, with NVIDIA's CUDA EULA (licenses/NVIDIA-CUDA.txt). The normal builds don't change.75;86-real;89-real;120-real: Turing with its PTX, Ampere, Ada, Blackwell. The runners have no GPU, so their tests check that the NVIDIA build falls back to CPU BoomerAMG.--hypre-cache, saved right after the build).Testing (Windows 11, RTX 3070)
unittest discover): 103 passedpackage:winandpackage:win:nvidia, thentest:packagedandtest:desktopon each: pass. The NVIDIA package solves on the GPU, and withCUDA_VISIBLE_DEVICES=-1falls back to CPU BoomerAMG. Installers are 208 MB (normal) and 570 MB (NVIDIA)I couldn't test the Linux NVIDIA job locally; this PR's CI is its first run.
🤖 Generated with Claude Code