Mercurial > repos > public > sbplib_julia
comparison Notes.md @ 683:841ca12f3359 feature/boundary_quads
Add notes about embedded grids
| author | Jonatan Werpers <jonatan@werpers.com> |
|---|---|
| date | Tue, 09 Feb 2021 06:48:43 +0100 |
| parents | d26231227b89 |
| children | 3cd582257072 05d8ea88c690 |
comparison
equal
deleted
inserted
replaced
| 682:3ed922e95a35 | 683:841ca12f3359 |
|---|---|
| 296 component(gf,2) # Andra komponenten av en vektor | 296 component(gf,2) # Andra komponenten av en vektor |
| 297 component(gf,2,3) # (2,3) elementet av en matris | 297 component(gf,2,3) # (2,3) elementet av en matris |
| 298 component(gf,:,2) # Andra kolumnen av en matris | 298 component(gf,:,2) # Andra kolumnen av en matris |
| 299 @ourview gf[:,:][2] | 299 @ourview gf[:,:][2] |
| 300 ``` | 300 ``` |
| 301 | |
| 302 ## Grids embedded in higher dimensions | |
| 303 | |
| 304 For grids generated by asking for boundary grids for a regular grid, it would | |
| 305 make sense if these grids knew they were embedded in a higher dimension. They | |
| 306 would return coordinates in the full room. This would make sense when | |
| 307 drawing points for example, or when evaluating functions on the boundary. | |
| 308 | |
| 309 Implementation of this is an issue that requires some thought. Adding an extra | |
| 310 "Embedded" type for each grid would make it easy to understand each type but | |
| 311 contribute to "type bloat". On the other hand adapting existing types to | |
| 312 handle embeddedness would complicate the now very simple grid types. Are there | |
| 313 other ways of doing the implentation? |