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
While `_matmul`, `_size`, and`_transpose_nonbatch` might seem like a limited set of functions,
175
188
it turns out that most functions on the `torch`and`torch.linalg` namespaces can be efficiently implemented
176
189
using only these three primitative functions.
@@ -181,8 +194,13 @@ This makes it possible to define very complex compositional structures that stil
181
194
182
195
Finally, `LinearOperator` objects can be composed with one another, yielding new `LinearOperator` objects and automatically keeping track of algebraic structure after each computation.
183
196
As a result, users never need to reason about what efficient linear algebra routines to use (so longas the input elements defined by the user encode known input structure).
197
+
<!-- docs_about_end -->
184
198
See the [using LinearOperator objects](#using-linearoperator-objects) section for more details.
185
199
200
+
201
+
<!-- docs_usecases_start -->
202
+
203
+
186
204
## Use Cases
187
205
188
206
There are several use cases for the LinearOperator package.
@@ -236,6 +254,10 @@ torch.linalg.solve(A, torch.randn(20000)) # Sub O(N^3) routine!
236
254
```
237
255
238
256
257
+
<!-- docs_usecases_end -->
258
+
<!-- docs_using_start -->
259
+
260
+
239
261
## Using LinearOperator Objects
240
262
241
263
LinearOperator objects share (mostly) the same APIas`torch.Tensor` objects.
@@ -330,6 +352,11 @@ This includes:
330
352
331
353
See the documentation for a [full list of supported composition and decoration operations](https://linear-operator.readthedocs.io/en/latest/composition_decoration_operators.html).
332
354
355
+
356
+
<!-- docs_using_end -->
357
+
<!-- docs_install_start -->
358
+
359
+
333
360
## Installation
334
361
335
362
LinearOperator requires Python >=3.8.
@@ -357,6 +384,10 @@ To install what is currently on the `main` branch (potentially buggy and unstabl
0 commit comments