Draft. This manual is new and still growing. If something here does not match what you see in the software, the software is right — tell us and we will fix the page.
Run on SHD Cloud
Package the case, solve it on metered hardware, and get the results back into the same case. No host to administer and no SSH.
Not part of the free tier. Selecting it as the executor is reported as an error on the Problems tab against Simulation control, and the job is refused with "SHD Cloud is not available on the Free tier". Settings → Licence lists what yours allows.
SHD Cloud is a separate route from Remote SSH and deliberately does not reuse the SSH machine configuration. There is nothing to configure: it talks to the SHD API only.
Before the first job
Settings → Licence must show a licence, and the installation must hold the licence key — a cloud job is authenticated with the key, not with the signed entitlement cache. Signing in again does not supply one; paste it from your account page into the Licence page. The application says exactly this if the key is missing, rather than telling you to sign in again.
Run a case on it
- Select Simulation control.
- Under Executor, set Run on to
SHD Cloud. - Set Cores as usual. On the cloud the machine is provisioned to match, so nothing is oversubscribed — cores set the rate you are charged at. The pane says so under the combo: N cores bill N compute hours per hour of solver time.
- Set Stop after, in minutes, if you want a wall-clock ceiling. Zero is none. The run is asked to stop and write rather than killed.
- Run as normal.
The case is written out, packaged with the commands to run, uploaded, solved, and the result archive is downloaded and unpacked back over the local case folder. The whole OpenFOAM pipeline goes — or, for a solid family, the prepared solver directory. The case is rewritten before every cloud run, so a setting changed after meshing is in the job.
What it costs
Before the job starts, the Log tab gets the estimate it was submitted with: compute hours, the core count, and the estimated solver duration. The charge is measured from the actual solver runtime, so the final figure will differ.
Queued cloud jobs are totalled before you press anything — see
use the run queue, where Active → cloud and
All → cloud show ~N Compute Hours estimated and each job card carries its
own figure.
While it runs
The progress read-out names the stage rather than sitting at "running": Packaging case, Creating cloud job, Uploading case, Waiting for worker, Starting worker, Running in SHD Cloud, Downloading result, Extracting result. Stop gracefully and Kill both cancel the cloud job.
Check it worked
- The Log tab carries the estimate line, then the solver's own output streamed back.
- Post-processing finds results afterwards. That is the proof the download and the unpack completed, not just the solve.
- The Problems tab carries no remote-execution error against Simulation control.