Mercurial > repos > public > sbplib_julia
comparison Notes.md @ 1240:a9ac86f6be8a
Merge refactor/LazyTensors/tuple_manipulation
| author | Jonatan Werpers <jonatan@werpers.com> |
|---|---|
| date | Tue, 21 Feb 2023 21:01:46 +0100 |
| parents | e2f6dafb5d83 |
| children | a8fa8c1137cc |
comparison
equal
deleted
inserted
replaced
| 1219:7ee258e5289e | 1240:a9ac86f6be8a |
|---|---|
| 385 A different approach would be to include it as a trait for operators so that you can specify what the adjoint for that operator is. | 385 A different approach would be to include it as a trait for operators so that you can specify what the adjoint for that operator is. |
| 386 | 386 |
| 387 | 387 |
| 388 ## Name of the `VolumeOperator` type for constant stencils | 388 ## Name of the `VolumeOperator` type for constant stencils |
| 389 It seems that the name is too general. The name of the method `volume_operator` makes sense. It should return different types of `LazyTensor` specialized for the grid. A suggetion for a better name is `ConstantStencilVolumeOperator` | 389 It seems that the name is too general. The name of the method `volume_operator` makes sense. It should return different types of `LazyTensor` specialized for the grid. A suggetion for a better name is `ConstantStencilVolumeOperator` |
| 390 | |
| 391 | |
| 392 ## Implementation of LazyOuterProduct | |
| 393 Could the implementation of LazyOuterProduct be simplified by making it a | |
| 394 struct containing two or more LazyTensors? (using split_tuple in a similar way | |
| 395 as TensorGrid) |