Mercurial > repos > public > sbplib_julia
comparison Notes.md @ 864:9a2776352c2a
Merge operator_storage_array_of_table
author | Jonatan Werpers <jonatan@werpers.com> |
---|---|
date | Wed, 19 Jan 2022 11:08:43 +0100 |
parents | fe8fe3f01162 |
children | 1784b1c0af3e eb03bda76bae |
comparison
equal
deleted
inserted
replaced
858:5088de9b6d65 | 864:9a2776352c2a |
---|---|
51 implemented through keyword arguments that are sent through all the layers of | 51 implemented through keyword arguments that are sent through all the layers of |
52 operator creation. | 52 operator creation. |
53 | 53 |
54 * Remove order as a table name and put it as a variable. | 54 * Remove order as a table name and put it as a variable. |
55 | 55 |
56 ### Parsing of stencil sets | |
57 At the moment the only parsing that can be done at the top level is conversion | |
58 from the toml file to a dict of strings. This forces the user to dig through | |
59 the dictionary and apply the correct parsing methods for the different parts, | |
60 e.g. `parse_stencil` or `parse_tuple`. While very flexible there is a tight | |
61 coupling between what is written in the file and what code is run to make data | |
62 in the file usable. While this coupling is hard to avoid it should be made | |
63 explicit. This could be done by putting a reference to a parsing function in | |
64 the operator-storage format or somehow specifying the type of each object. | |
65 This mechanism should be extensible without changing the package. Perhaps | |
66 there could be a way to register parsing functions or object types for the | |
67 toml. | |
68 | |
69 If possible the goal should be for the parsing to get all the way to the | |
70 stencils so that a user calls `read_stencil_set` and gets a | |
71 dictionary-structure containing stencils, tuples, scalars and other types | |
72 ready for input to the methods creating the operators. | |
56 | 73 |
57 ## Variable second derivative | 74 ## Variable second derivative |
58 | 75 |
59 2020-12-08 after discussion with Vidar: | 76 2020-12-08 after discussion with Vidar: |
60 We will have to handle the variable second derivative in a new variant of | 77 We will have to handle the variable second derivative in a new variant of |