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.
Use the run queue
Line several simulations up and let them solve one after another, instead of sitting by the machine and pressing Start run each time one finishes.
Runs on the free tier. Queued jobs go through the same solver and the same limits as a run started by hand.
Queue the work
Four buttons, in two places, spelling out two independent choices — which simulations, and where they run:
| Local | SHD Cloud | |
|---|---|---|
| The open simulation | Active → local | Active → cloud |
| Every simulation in the case | All → local | All → cloud |
They are on the Queue section of the Simulation runs pane, and again across the top of the Simulation queue panel. Model → RUN → Queue this is the same as Active → local.
The cloud columns cost money and say so before you press anything: with cloud
jobs waiting, both places show ~N Compute Hours estimated, charged on actual
solver runtime. See run on SHD Cloud.
Work through it
Press Run queue — on the same pane, in the panel, or at Model → RUN → Run queue, which is greyed with "The queue is empty" until there is something in it. The jobs are worked through in order.
The Simulation queue panel has Stop, which halts the queue, and Clear, which empties it.
Watch it
The status bar along the bottom of the window carries a running/queued counter
beside the cores and iteration read-outs. Click it to open the Simulation
queue panel. Each job is a card carrying:
- The simulation's name, and its analysis, solver and detail.
Local, orCloudwith that job's own estimate in Compute Hours.- Its status, colour-coded, with the running one highlighted.
- A progress bar.
- Open, which switches the workbench to that simulation, and Remove, which drops it from the queue. Remove is disabled on the job that is running.
The counts read N jobs while the queue is idle and
Running N, waiting M once it is going.
Check it worked
- The panel's header count falls as jobs finish, and the estimate falls with it.
- Each finished simulation has a run under Simulation runs with an outcome,
not
not run. - For cloud jobs, the Log tab carries the estimate line the job was submitted with; the charge is measured from actual solver runtime, so the final figure will differ.