Mercurial > repos > public > sbplib_julia
comparison Notes.md @ 702:3cd582257072 feature/laplace_opset
Merge in default
| author | Vidar Stiernström <vidar.stiernstrom@it.uu.se> |
|---|---|
| date | Mon, 15 Feb 2021 11:30:34 +0100 |
| parents | f1803ab08740 841ca12f3359 |
| children | f88b2117dc69 |
comparison
equal
deleted
inserted
replaced
| 679:54ce3f9771e5 | 702:3cd582257072 |
|---|---|
| 297 component(gf,2) # Andra komponenten av en vektor | 297 component(gf,2) # Andra komponenten av en vektor |
| 298 component(gf,2,3) # (2,3) elementet av en matris | 298 component(gf,2,3) # (2,3) elementet av en matris |
| 299 component(gf,:,2) # Andra kolumnen av en matris | 299 component(gf,:,2) # Andra kolumnen av en matris |
| 300 @ourview gf[:,:][2] | 300 @ourview gf[:,:][2] |
| 301 ``` | 301 ``` |
| 302 | |
| 303 ## Grids embedded in higher dimensions | |
| 304 | |
| 305 For grids generated by asking for boundary grids for a regular grid, it would | |
| 306 make sense if these grids knew they were embedded in a higher dimension. They | |
| 307 would return coordinates in the full room. This would make sense when | |
| 308 drawing points for example, or when evaluating functions on the boundary. | |
| 309 | |
| 310 Implementation of this is an issue that requires some thought. Adding an extra | |
| 311 "Embedded" type for each grid would make it easy to understand each type but | |
| 312 contribute to "type bloat". On the other hand adapting existing types to | |
| 313 handle embeddedness would complicate the now very simple grid types. Are there | |
| 314 other ways of doing the implentation? |