| | 1 | |
| | 2 | == IDEAS == |
| | 3 | |
| | 4 | |
| | 5 | Settle dataflows and formats (pts, dem, msh, sww, etc) (Ole) |
| | 6 | |
| | 7 | |
| | 8 | finaltime to be renamed duration |
| | 9 | |
| | 10 | |
| | 11 | Making methods private, using _private or write the API in a separate module. |
| | 12 | |
| | 13 | |
| | 14 | Introduce create_quantity in domain.py: (Ole) |
| | 15 | It will make a new named instance and populate it by calling set_quantity |
| | 16 | if desired. Create_quantity would be called automatically by shallow_water. |
| | 17 | |
| | 18 | |
| | 19 | Make stage appear as any other quantity: |
| | 20 | Either |
| | 21 | 1: Make stage a subclass of quantity having knowledge of elevation and a special |
| | 22 | limiter (or more limiters) |
| | 23 | Or |
| | 24 | 2: Equip each quantity with a limiter class |
| | 25 | (Con: A limiter for stage should never be applied to any other quantity) |
| | 26 | |
| | 27 | |
| | 28 | Also, investigate if Quantity and Conserved_quantity should be one class (Steve). |
| | 29 | |
| | 30 | Finally, reconcile the optimised gradient limiter of Matt's with the more general framework (see wiki:NumericalIssues) |
| | 31 | |
| | 32 | |
| | 33 | |
| | 34 | |
| | 35 | Boundary (Dirichlet): Think about specifying values by quantity name (and having defaults) |
| | 36 | Dirichlet(stage = 1.0, ymomentum = 0.2) |
| | 37 | |
| | 38 | |
| | 39 | Finish MOST2SWW with bathymetry as one script |
| | 40 | |
| | 41 | |
| | 42 | Make Steve's new boundary spatially dependent (Ole) |
| | 43 | |
| | 44 | |
| | 45 | Look at matplotlib's verbosity object. It looks great. |
| | 46 | |