... | ... | @@ -18,4 +18,15 @@ I stick to this fixed, but arbitrary numbering scheme amongst the applications b |
|
|
|
|
|
## Queried initial data
|
|
|
|
|
|
Accessing user specified constants in the spec file still does not work correctly, so there is a number of patch code which can access the environment variables instead. In all applications we have multiple initial data examples for a given PDE. This will always remain as we will always have lot's of sources for initial data. |
|
|
\ No newline at end of file |
|
|
Accessing user specified constants in the spec file still does not work correctly, so there is a number of patch code which can access the environment variables instead. In all applications we have multiple initial data examples for a given PDE. This will always remain as we will always have lot's of sources for initial data.
|
|
|
|
|
|
## Boundary values
|
|
|
|
|
|
The integration of exact boundary values is currently the same in all applications. What users typically want to do is to specify somewhere if they want
|
|
|
|
|
|
* reflecting
|
|
|
* outgoing
|
|
|
* exact
|
|
|
* periodic
|
|
|
|
|
|
BC. This is a typical run-time choice so there should be all possibilities already in the code. Another thing for redundancy we currently have as the implementation is always the same. |