| 1 | QA: Have SMEC (and the likes) try the software for one of their projects |
|---|
| 2 | and ask them to comment on: |
|---|
| 3 | |
|---|
| 4 | quality |
|---|
| 5 | performance (size and speed) |
|---|
| 6 | ease of installation |
|---|
| 7 | documentation |
|---|
| 8 | |
|---|
| 9 | |
|---|
| 10 | NAME: How about naming the whole thing GANU or ANUGA ? |
|---|
| 11 | |
|---|
| 12 | |
|---|
| 13 | PROJECTS: |
|---|
| 14 | |
|---|
| 15 | One way of implementing parallelism would be through domain decomposition (DD). |
|---|
| 16 | Perhaps we can work with someone with experience in DD of PDEs and once that |
|---|
| 17 | works, parallelise the code by having several sub-domains on each processor. |
|---|
| 18 | |
|---|
| 19 | |
|---|
| 20 | Uncertainty modelling and MC simluations. |
|---|
| 21 | |
|---|
| 22 | Running a large simulation (Stress test): {Peter Row?) DONE (tsunamies) |
|---|
| 23 | |
|---|
| 24 | Momentum sink study. Scale, extent, |
|---|
| 25 | map various copmpositions of structures to friction terms |
|---|
| 26 | |
|---|
| 27 | |
|---|
| 28 | Stephen: Look at domain decomposition algorithms with a view of |
|---|
| 29 | parallelising pyvolution |
|---|
| 30 | |
|---|
| 31 | |
|---|
| 32 | Stephen: Timestepping to be controlled by error estimator. |
|---|
| 33 | |
|---|
| 34 | |
|---|
| 35 | |
|---|
| 36 | DESIGN PRINCIPLES (17/3/5) - as agreed to by Duncan and Ole |
|---|
| 37 | |
|---|
| 38 | Objects shared across project should not precompute |
|---|
| 39 | structures upon initialisation unless they are used by all clients. |
|---|
| 40 | Rather precompute on demand or split using inheritance. |
|---|
| 41 | Pro: Good separation of concepts |
|---|
| 42 | Con: It may be harder to find the right file |
|---|
| 43 | |
|---|
| 44 | Also, modules shared across project should not generally depend on other modules. |
|---|
| 45 | |
|---|
| 46 | |
|---|
| 47 | |
|---|
| 48 | Idea (ON 28/4/5): |
|---|
| 49 | Allow set_quantity to take a .pts file as argument. That should use least_squares to populate the quantity. |
|---|
| 50 | Furthermore use caching.py to assert whether this should be computed or read from cache. |
|---|
| 51 | |
|---|
| 52 | |
|---|
| 53 | Use logger module as suggested by steve |
|---|
| 54 | |
|---|
| 55 | See also HUSK.txt in pyvolution |
|---|
| 56 | |
|---|
| 57 | |
|---|
| 58 | Have the option of changing boundaries and forcing functions on the fly depnding on e.g. time or value of conserved quantities. |
|---|
| 59 | |
|---|
| 60 | |
|---|
| 61 | PROJECT IDEAS (NOV 2005) |
|---|
| 62 | |
|---|
| 63 | GBR Effect on tsunami (Stephen may get student) |
|---|
| 64 | Convection (Grad proposal 2005/2006, Ole) |
|---|
| 65 | Momentum sink (Grad proposal 2005/2006, Duncan) |
|---|
| 66 | Convergence study (Ole) |
|---|
| 67 | VRML export (David Beard, Malcolm Nicoll) |
|---|
| 68 | Proper installer |
|---|
| 69 | Overcome 2GB NetCDF limit |
|---|
| 70 | IO (data_manager) needs some TLC |
|---|
| 71 | |
|---|
| 72 | See also work program ideas 2005-2006 |
|---|
| 73 | |
|---|
| 74 | |
|---|
