Mercurial > repos > public > sbplib_julia
diff Notes.md @ 1217:ea2e8254820a feature/boundary_conditions
Update docstrings and start implementing tests
author | Vidar Stiernström <vidar.stiernstrom@it.uu.se> |
---|---|
date | Tue, 07 Feb 2023 21:55:07 +0100 |
parents | 6757cc9ba22e |
children | bdcdbd4ea9cd |
line wrap: on
line diff
--- a/Notes.md Wed Dec 07 21:56:00 2022 +0100 +++ b/Notes.md Tue Feb 07 21:55:07 2023 +0100 @@ -4,19 +4,19 @@ Types for boundary conditions: - * abstract type `BoundaryDataType` - * abstract type `BoundaryCondition{T<:BoundaryDataType}` - * concrete types `ConstantBoundaryData <: BoundaryDataType` and similar - * concrete types `NeumannCondition{BDT<:BoundaryDataType} <: BoundaryCondition{BDT}` and similar -The concrete `BoundaryDataType` subtypes are "thin types" wrapping the boundary data, and are used to indicate how the boundary data should be used in e.g. sat routines. The concrete `BoundaryCondition{BDT}` subtypes are used for assembling the tensors used to construct e.g. a SAT. + * abstract type `BoundaryData` + * abstract type `BoundaryCondition{T<:BoundaryData}` + * concrete types `ConstantBoundaryData <: BoundaryData` and similar + * concrete types `NeumannCondition{BD<:BoundaryData} <: BoundaryCondition{BD}` and similar +The concrete `BoundaryData` subtypes are "thin types" wrapping the boundary data, and are used to indicate how the boundary data should be used in e.g. sat routines. The concrete `BoundaryCondition{BD}` subtypes are used for assembling the tensors used to construct e.g. a SAT. SAT methods: There are multiple options for what the SAT methods could return. -* (Current) a function which returns a `LazyTensorApplication`, e.g. `f = sat(grid,op,bc)`. The the resulting `LazyTensorApplication` can then be added to scheme i.e. `scheme = op*u + f(u)`. This is how one typically would write the SAT in the litterature. Depdending on the type of data in the BC, e.g. time-depdendent etc one can return f(u,t). +* (Current) a function which returns a `LazyTensorApplication`, e.g. `f = sat(grid,op,bc)`. The the resulting `LazyTensorApplication` can then be added to scheme i.e. `scheme = op*u + f(u)`. Depdending on the type of data in the BC, e.g. time-depdendent etc one can return f(u,t). * `LazyTensor`s `closure, penalty = sat(grid,op,bc)` like in the matlab version. Probably the most general one. Up to the user to make use of the returned `LazyTensor`s. One can for example then easily include the closures to the operator and have eg. `D = (op + closure)*u`. * A `LazyTensor` for closure, and a `LazyArray` for `penalty*data`. Mix of the above. +* Same as first but of the form sat = `sat_op*(L*u-g)`. This is how one typically would write the SAT in the litterature. The function `sat_tensors` would return `sat_op` and `L`. Need to get compositions working before we can implement this approach. -It is not clear if any of these are preferable as it currently stands. ## Reading operators