Projects and analysis
Solve queue and monitoring
The Solve Queue view lists every run in your workspace: what is waiting and running, and every finished run. Compute Analytics shows how the workstation is performing.
How the queue works
- Runs execute one at a time, in submission order on the connected ForgeNode.
- The queue keeps running while any LoudGears page is open in this browser: the workspace, the queue, reports or a project. Only one page runs it at a time; if that page closes, another open page takes over.
- You can keep working, in this project or another, while ForgeNode works through the queue.
- A run keeps its place and its bound inputs (file, load case, route) from the moment you add it.
- A file with a front and a rear wheel becomes two runs: the rear wheel is queued right behind the front. See Front and rear wheels in one file.
- If a run is interrupted before it reaches ForgeNode (the network drops, or ForgeNode restarts for an update), it waits for ForgeNode to come back, for up to 20 minutes, and then takes its turn. It is not marked as failed.
- If ForgeNode is still finishing the previous run, the next one is offered again until ForgeNode accepts it. This never starts a second run or charges a second credit.
Finding a run
Waiting and running work is listed first, in submission order. Every finished run follows under Finished, newest first, 50 at a time; finished runs stay listed until you delete them.
- Search by project, geometry, job or result.
- Filter by result: All, Passed, Failed, Review, Errors or Running. Each filter shows its count.
- Click a row to open the run, or choose Inspect to show it in the Job Inspector beside the list.
Run states
| State | Meaning |
|---|---|
| WAITING / PREPARING | Held on this workstation: waiting for its turn, or ForgeNode is preparing the file (including an IGES or X_T conversion). |
| QUEUED, ADMITTED, STARTING, RUNNING | LoudGears has admitted the run and ForgeNode is meshing and solving it. The line under the state shows the stage and progress. |
| PASSED / FEA FAILED / REVIEW REQUIRED | Finished with a verified result. See Read a result. |
| ERROR | The run stopped before a result. Open it for the diagnostic and what to do next. |
| CANCELLED / STOPPED / EXPIRED | The run was aborted, or it was never started in time. Any reserved credit was released. |
| RESULT UNAVAILABLE | The analysis finished, but the verified result could not be loaded yet. Do not rerun it. See Troubleshooting. |
| DEVICE NOT REPORTING / DEVICE TELEMETRY STALE | The run belongs to another workstation, which has not reported progress recently. Check that workstation and its ForgeNode. |
Removing and deleting runs
| Action | What it does |
|---|---|
| Remove from queue | Removes failed or cancelled runs that never reached LoudGears from this workstation's list. |
| Delete runs | Deletes the selected finished runs with their saved results and reports. Their projects stay in the workspace, and billing records are kept. Waiting or running runs are skipped. This cannot be undone. |
| Abort Solver | On a running run's page: cancels that run. ForgeNode stops the local mesh or solver process; the partial result cannot be recovered and the reserved credit is released. |
Job Inspector
Select a run in the queue to open the Job Inspector. It shows:
- the project, geometry, and status;
- Max von Mises stress, Factor of safety, and the surface mesh size, once available;
- the Operation ID and the Workstation that ran it;
- ForgeNode activity log: live log lines while the run is active.
From the inspector, Open run goes to the live run page, and Open verified result & PDF goes to the finished result. For a failed run, Get help with this run opens a support request with the run attached.
Tip When you contact support about a run, copy the Operation ID from the Job Inspector.
Compute Analytics
Compute Analytics shows read-only telemetry from the connected ForgeNode: GPU utilisation, memory, temperature and power, CPU utilisation and frequency, system memory, and progress of the current operation. Use it to confirm a run is using the GPU, or to spot a workstation that is overheating or short of memory.
If it shows ForgeNode update required, the installed ForgeNode is too old to report telemetry. See Update ForgeNode.