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.
Coupled run
Where it is
Not a setup-tree node. Embedded in the application.
Controls
WHAT THIS NEEDS
Check again
- Control: action (
ToolButton2)
COUPLED CASE
Write coupled case
- Control: action (
ToolButton2) - Enabled when:
CouplingState.solvable && !CoupledJob.busy
Start both participants
- Control: action (
ToolButton2) - Enabled when:
CouplingState.runnable && !CoupledJob.busy && root.state.ok
Stop
- Control: action (
ToolButton2) - Enabled when:
CoupledJob.busy
QUEUE
Queue this
- Control: action (
ToolButton2)
Queue all
- Control: action (
ToolButton2)
Queue running
Label changes with the case; the source gives these forms: Queue running, Run queue.
- Control: action (
ToolButton2) - Enabled when:
!CaseState.simulationQueueRunning
Lists this panel shows
Read straight from the data behind the panel, not from a hand-written list.
WHAT THIS NEEDS
From a fixed list in the application.
| key | label | detail |
|---|---|---|
| preciceLibrary | preCICE | The coupling library itself. Both participants link against it. |
| foamAdapter | OpenFOAM adapter | A function object, compiled against this OpenFOAM. A copy built against another version loads and then behaves incorrectly. |
| pythonBindings | preCICE for code_aster | The solid participant drives preCICE from inside its own command file, so code_aster's Python is the one that has to import it. |
Problems reported against this step
The application reports no problems against this step.
… marks a value the application computes at run time, so the source carries no fixed text for it.