You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: add describe(:cpu) and describe(:gpu) functionality
- Add examples showing describe(:cpu) and describe(:gpu) in main solve manual
- Enhance GPU manual with describe(:gpu) to show GPU-compatible strategies
- Remove unnecessary Draft meta blocks
- Update documentation assets for new CTSolvers version
Copy file name to clipboardExpand all lines: docs/src/manual-solve.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,6 +109,17 @@ Each method is a **quadruplet** `(discretizer, modeler, solver, parameter)`:
109
109
-`:cpu`: CPU execution (default)
110
110
-`:gpu`: GPU execution (only for `:exa` modeler with `:madnlp` or `:madncl` solvers)
111
111
112
+
You can inspect which strategies use a given parameter:
113
+
114
+
```@example main
115
+
describe(:cpu)
116
+
```
117
+
118
+
```@example main
119
+
using CUDA, MadNLPGPU
120
+
describe(:gpu)
121
+
```
122
+
112
123
!!! note "Priority order"
113
124
114
125
The order of methods in the list above determines the **priority** for auto-completion. When you provide a partial description, the first matching method from top to bottom is selected. This is why the first method `(:collocation, :adnlp, :ipopt, :cpu)` is the default.
0 commit comments