Case lifecycle¶
Every Attitude follows the same lifecycle, from Launch to Sign-off Case. Bramble runs most of it automatically, but pauses at the points where an engineer's judgement matters. This page explains where it pauses, when the Account pays, and what signing off means. For every stage, status and button, see statuses and lifecycle.
Where Bramble waits for you¶
Launch → Create → Pre-Checks → wait → Mesh & Solve → Charge Account → solution checks, monitors and post-processing → wait → Sign-off Case
After pre-checks¶
Launch creates the case and runs the pre-checks, then stops. The next button in the Attitude's Transitions row is Mesh & Solve.
The reason is cost. Mesh & Solve is the stage that uses HPC time and is charged to the Account. Most set-up mistakes show up before it, in the pre-checks and their plots: a missing Part, a zone in the wrong force group, a mesh recipe that differs from the baseline. The pause gives you the chance to catch them before you pay for a solve.
That's why the Mesh & Solve Attitude Confirmation dialog asks you to check:
- the geometry plots, and the delta geometry plots if there's a baseline
- that the pre-checks found no errors
- that the CFD setup is correct
A failed pre-check always stops the Attitude, whatever its settings. If your Account has the feature, you can untick Hold After Checks for an Attitude, so that Mesh & Solve starts on its own once every pre-check passes. This suits sweeps where the set-up is already proven. See configure pre-checks.
Some Attitudes also wait for another case. An Attitude that starts from a mapped-solution donor can't start Mesh & Solve until the donor has solved.
Before sign-off¶
After post-processing, the Attitude waits at Sign-off Case. It always stops here.
While an Attitude is waiting at any stage after launch, you can also Reset it.
When credit is reserved and used¶
The Account is checked at Launch and charged at Charge Account, which runs straight after Mesh & Solve completes.
| Point | Pay per Run Accounts | Cash Payments and Core Hours Accounts |
|---|---|---|
| Launch | Credits are reserved for the Attitude | The balance is checked against an estimate. Nothing is set aside |
| Charge Account | The reserved credits are used | The cost is deducted from the Cash Payments balance, or the core hours from the Core Hours allowance |
If the Account can't pay at launch, or isn't active, the Attitude stops with Insufficient Credits.
What Reset gives back. Resetting an Attitude (or deleting it) before Charge Account returns any credits reserved for it. That covers an Attitude that failed or was aborted before or during Mesh & Solve. Aborting on its own doesn't release them: they stay reserved until you reset. Once the Attitude has been charged, resetting it doesn't refund anything. Skipping a failed Mesh & Solve moves the Attitude on to Charge Account, so the Account is charged.
Reset also deletes the case's files and unlocks its Parts, Template Case and Map entry, if nothing else uses them. The CFD setup is kept. See handle a failed Attitude.
For how usage is counted, see credits and billing.
Draft, sign-off and Completed¶
Signing off is how an engineer records that an Attitude's results have been checked and can be trusted. Until then, the results are a draft.
The Results page shows each Attitude's state in words:
| Label | Means |
|---|---|
| Draft | Post-processing is done. The Attitude is waiting at Sign-off Case |
| User Required | The Attitude is waiting for you at another stage, usually Mesh & Solve |
| "<stage>: <status>", e.g. "Mesh & Solve: Running" | A stage is queued, running or has failed |
| Completed | The Attitude has been signed off |
Draft results can already be viewed, and downloaded as PowerPoint, so check the label before you share them.
Signing off¶
To sign off, click Sign-off Case in the Attitude's Transitions row. Sign-Off Confirmation asks you to check that:
- convergence is acceptable
- forces and flow metrics are sensible
- the post-processing images and movies are correct
Bramble records who signed off, shown as "(By: <username>)" in the Sign-off Case cell.
Who can sign off. Any User in the Account who isn't restricted. There's no separate reviewer role, so agree within your team who signs off.
After sign-off¶
A signed-off Attitude can still:
- generate more postpro, with Re-run in the Post-Process or Create Delta PostPro row. It doesn't need signing off again afterwards
- be archived, which deletes its mesh and solution but keeps its results. Only signed-off Attitudes can be archived. See archive Attitudes
Related: Statuses and lifecycle · Launch and monitor a Run · Credits and billing · Handle a failed Attitude