comparison Notes.md @ 1232:a8fa8c1137cc refactor/grids

Merge refactor/LazyTensors/tuple_manipulation
author Jonatan Werpers <jonatan@werpers.com>
date Sun, 19 Feb 2023 22:07:57 +0100
parents 5f677cd6f0b6 e2f6dafb5d83
children 79647b60a73b
comparison
equal deleted inserted replaced
1222:5f677cd6f0b6 1232:a8fa8c1137cc
386 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 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.
387 387
388 388
389 ## Name of the `VolumeOperator` type for constant stencils 389 ## Name of the `VolumeOperator` type for constant stencils
390 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 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`
391
392
393 ## Implementation of LazyOuterProduct
394 Could the implementation of LazyOuterProduct be simplified by making it a
395 struct containing two or more LazyTensors? (using split_tuple in a similar way
396 as TensorGrid)