Whet user guide, chapter 10, 2026-10-09
Your own server
Whet runs everything on your own computer. If you also own a stronger machine, such as a workstation, a box in a rack or a rented server, you can send the heavy work there. That means the mesh and solve of strength and heat studies, motion simulations and renders. The result comes back to your computer and is recorded there. The record names the machine that made it.
Nothing is installed as a service on the server. Nothing listens on a port. No account is created. Whet uses ssh and scp with your own key, the same way you would from a terminal.
What you need
- An ssh server on the other machine, and a key that logs in without a password prompt. A key with a passphrase is fine once your ssh agent has unlocked it. Whet never asks for a password, never stores one, and never creates, copies or moves a key.
python3on the server's path.- The engines on the server, at the same versions as on your computer. A stage whose engine version differs is refused. That is deliberate: the same versions give the same answer you would get at home.
- For renders, Blender on the server (optional).
The server needs no desktop, no display and no graphics card for studies and simulations. A card helps renders.
Check your key
In a terminal on your computer:
ssh -o BatchMode=yes user@your-server true && echo ok
If it prints ok, your key works. If it asks for a password or fails, set up a key first with ssh-keygen and ssh-copy-id user@your-server.
Which engines, which versions
Look at Preferences > Engines on your computer. It lists the version of each engine. The server's gmsh, CalculiX and MuJoCo must match them. Blender's version is recorded and not compared. Linux distributions usually ship other versions of gmsh and CalculiX, and a study sent to them is refused.
A Mac as the server
Install the same Whet app on the other Mac. It carries the same engines at the same versions, so nothing else needs installing. Turn on System Settings > General > Sharing > Remote Login for your user.
A Linux server
The engines inside Whet's Linux package are at the right versions. Set Up My Server, on the My Server page, tries to do the work for you. Over ssh it looks at the server, copies the server form of the package to a folder in your home directory there, reads the engine versions and fills in the settings. It stops with one sentence where the package cannot run. It supports 64-bit x86 Linux only. How reliable the button is on machines other than the ones it was tried on is (to be checked).
The My Server page
Open Preferences > My Server.
| Row | What to put there |
|---|---|
| Address | ssh://user@your-server, or ssh://user@your-server:2222 for another port |
| Key | Nothing. ssh uses your own key. |
| Stress and heat | My Server sends the mesh and solve there. |
| Simulation | Follows Stress and heat. It is greyed because one setting covers both. |
| Render | My Server sends renders there. |
| gmsh there, CalculiX there, Python there | Absolute paths on the server. Empty means gmsh, ccx and python3 on its path. |
| Blender there | Blender's path on the server. Empty means blender on its path. |
Press Save. Whet checks each value before it uses it. A value that does not fit is refused, and the reason is printed under Save. An address looks like ssh://user@host or ssh://user@host:port. A path is absolute and may hold only letters, digits and _ . - /.
Open Models Page takes you to the page where a model server on the same machine is set. See The assistant.
Press Test
Test runs the smallest real job of each kind on the server. It works in a scratch folder on your computer, which is deleted afterwards.
- A 20 mm steel cube is built here, then meshed and solved on the server.
- A 20 mm block is dropped for 50 milliseconds in the motion engine, on the server.
- The cube is rendered at 64 x 64 pixels with one sample on the server's processor.
Each engine gets a row. It says present with the version that answered, a different version, missing, or not reached. The fix is beside it, with the engine's own sentence under it. For example:
CalculiX present, 2.23, as here
MuJoCo version differs: 3.3.7 here, 3.12.0 there
Fix: install MuJoCo 3.3.7 there, or run the setup
Blender missing
Fix: install Blender there, and name it in the Blender there row if it is not on the path
Test reads the saved settings. Press Save first. It stays greyed until a server address is set.
Use it
Open a part, set up a strength study as usual, and press Solve. With Stress and heat on My Server, the mesh and solve run there. The Record dock names where it ran. The record lists the server, the engine versions that answered, and for each job the engine time, the copy time and the total. A small study can take longer on a server than at home, because of the copying and the connection. Those three times show why.
For a render, set Run On to My Server in the Render panel. See Rendering and video.
When the server refuses: Run Locally
If a job is refused because of the server, you get a Run Locally button. The server may be off, an engine may be missing or a version may differ. It appears on the Strength and Heat panels, the Render panel and the motion refusal dialog. One click runs the same job again on your computer. The record then says it ran locally.
A refusal about the job itself, such as a study the engine cannot read, does not offer Run Locally. It would be refused here too.
What is sent
| Goes to the server | Comes back | Never leaves your computer |
|---|---|---|
| The files each engine job needs: the part and the mesh script for a mesh; the solver input for a solve; the model and drive files for a simulation; the render script, job and meshes for a render | The mesh, the solver output, the motion track and load history, the picture | Your project, the study description, material cards, the records, your settings, environment variables, credentials and your licence |
Checking, materials, trial limits, reading the answer and writing the record all happen on your computer. STEP files are turned into meshes on your computer before a render is sent.
On the server each job gets its own private folder under /tmp, readable only by your user and deleted afterwards. The engines are started with a fixed path and nothing from your environment. Blender is started without your add-ons and with network access off.
If the connection drops in the middle of a job, a folder can be left in /tmp on the server. Its name starts with whet-compute- or whet-render-. Delete it once nothing is using it. Nothing is recorded from an incomplete job.
Troubleshooting
- Not reached, "ssh failed". Wake the machine, check the network, run the key check above, and unlock a passphrase key in your ssh agent.
- Missing. Install the engine at the right version and put its full path in the row.
- Version differs. Install the version the row names, or press Run Locally for this job.
- No python3 there. Install Python 3 on the server. It supervises every job.
- Save prints a refusal. The value does not fit the address and path rules above.
Limits
- Render device and graphics card choices (CUDA, OptiX, Metal, CPU, and which card) have no row on My Server. They are on the Render Server page under Settings > Render > Render Server.
- Whet does not compare the server's Blender version with yours. It records it.
- Mesh editing has no server setting and runs on your computer.
- Nothing about Windows servers has been tested (to be checked).
- Do not open a port, start a service, share a key, switch off host key checking, or run engines as root to make this work. None of these is needed.