Mercurial > repos > public > sbplib_julia
changeset 318:0c8d4a734c4f
Add some todos and add a Notes.md file
| author | Jonatan Werpers <jonatan@werpers.com> |
|---|---|
| date | Thu, 10 Sep 2020 10:55:30 +0200 |
| parents | 75c61d927153 |
| children | 05ac7d7f9176 |
| files | Notes.md TODO.md |
| diffstat | 2 files changed, 13 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Notes.md Thu Sep 10 10:55:30 2020 +0200 @@ -0,0 +1,4 @@ +# Notes + +## Known size of range and domain? +It might be a good idea let tensormappings know the size of their range and domain as a constant. This probably can't be enforced on the abstract type but maybe we should write our difference operators this way. Having this as default should clean up the thinking around adjoints of boundary operators. It could also simplify getting high performance out of repeated application of regioned TensorMappings. \ No newline at end of file
--- a/TODO.md Wed Sep 09 22:00:13 2020 +0200 +++ b/TODO.md Thu Sep 10 10:55:30 2020 +0200 @@ -16,15 +16,21 @@ - [ ] Update how dependencies are handled for tests. This was updated in Julia v1.2 and would allow us to use test specific dev packages. ## Reasearch and thinking - - [ ] Redo all Tensor applys to take Vararg instead of tuple of Index? - Have we been down that road before? Is there any reason not to do this? + - [ ] Use a trait to indicate if a TensorMapping uses indices with regions. + The default should be that they do NOT. + - [ ] What to name this trait? Can we call it IndexStyle but not export it to avoid conflicts with Base.IndexStyle? + - [ ] Use a trait to indicate that a TensorMapping har the same range and domain? + - [ ] Rename all the Tensor stuff to just LazyOperator, LazyApplication and so on? + - [ ] Figure out repeated application of regioned TensorMappings. Maybe an instance of a tensor mapping needs to know the exact size of the range and domain for this to work? - [ ] Check how the native julia doc generator works - [ ] Check if Vidars design docs fit in there - [ ] Formalize how range_size() and domain_size() are supposed to work in TensorMappings where dim(domain) != dim(range) (add tests or document) + - [ ] Create a macro @lazy which replaces a binary op (+,-) by its lazy equivalent? Would be a neat way to indicate which evaluations are lazy without cluttering/confusing with special characters. + - [ ] Specificera operatorer i TOML eller något liknande? + - [x] Redo all Tensor applys to take Vararg instead of tuple of Index? - [x] Should there be some kind of collection struct for SBP operators (as TensorOperators), providing easy access to all parts (D2, e, d , -> YES! H.. H_gamma etc.) - [x] Is "missing" a good value for unknown dimension sizes (of `e*g` for example) - - [ ] Create a macro @lazy which replaces a binary op (+,-) by its lazy equivalent? Would be a neat way to indicate which evaluations are lazy without cluttering/confusing with special characters. # Wrap up task @@ -45,4 +51,3 @@ en vektor, utan randvärdet plockas ut utanför. Känns inte konsistent med övrig design -Specificera operatorer i TOML eller något liknande?