Changeset 1739


Ignore:
Timestamp:
Aug 23, 2005, 2:27:05 PM (19 years ago)
Author:
ole
Message:

Recovered comments from 18 Aug

File:
1 edited

Legend:

Unmodified
Added
Removed
  • inundation/wiki/future_directions.txt

    r1690 r1739  
    2121Functionality issues
    2222
    23 Mesh generation:
     23Mesh generation: (Duncan)
    2424    Through graphical generator
    2525    Through scripts
    2626    Alternative triangulators (Strang, ?.)
    2727    alpha-shapes
    28 
    29 refactoring triangle interface
    30 outputting a ?triangle? readable file (from pmesh?)
    31 
    32   from pmesh issues file:
    33       Main issues  (TBA) 
    34 
     28   
     29
     30   refactoring triangle interface
     31   outputting a "triangle" readable file (from pmesh?)
     32   
     33   simple method in mesh factory that will convert regularly gridded data to mesh using
     34   points as vertices
     35
     36Pmesh (Duncan)
     37    - from pmesh issues file:
     38        Main issues  (TBA) 
     39     
     40    - Better API for handling (scripted) meshes:
     41        *Error messages
     42        *Refined regions should be specified easily
     43        *Ways of handling different point sets (e.g. 10m, 100m, 250m)
     44         and populate according to refinement of mesh
     45         
     46     
    3547Georeferencing
    3648  Code works in UTM coordinates. Zone boundaries cannot be crossed
    3749  Could code be cast in terms of lat/lons?
    38 
    39 least_squares, use of quad-tree may not use all datapoints
    40         (currently fixed by expand search, need algorithm for searching neighbouring    treenodes)
     50  make sure that georeferencing is used consistently (domain, pmesh, sww files, ...) (Duncan) 
     51
     52Least_squares, (Duncan)
     53        use of quad-tree may not use all datapoints
     54        (currently fixed by expand search, need algorithm for searching neighbouring treenodes)
    4155
    4256        Give feedback when
    4357                points outside mesh
    4458                mesh outside points boundary
    45 
    46         use sparse matrix (CSR) format in ?build_interpolation_matrix_A?
     59                if mesh is corrupted (see lwru2.py and create_mesh.py in debug dir)
     60                if segments are repeated (maybe in mesh.check_integrity)   
     61
     62        use sparse matrix (CSR) format in "build_interpolation_matrix_A"
    4763        simplify geo-referencing (make sure that coordinate changes 'change_points' are
    48         used everywhere
    49         memory issue: Compute self.Atz directly and avoid self.A
    50 
     64        used everywhere)
     65       
     66        memory issue: !
     67                If LS is used for fitting
     68                    compute self.Atz and self AtA directly and avoid self.A.
     69                    need alpha
     70                If LS is to be used for interpolation
     71                    compute self.A
     72                    no alpha needed
     73               
     74               
     75refactor interpolate_sww in terms of Interpolation_function (Ole or Duncan)
     76
     77               
    5178Checkpointing (largely done but needs to be revisited)
    5279
     
    5683
    5784
    58 File management (msh, pts, dem, ..) ? introduce the notion of a project
    59  - reduce # of methods that read/write sww files (Yes)
     85File management (msh, pts, dem, ..) - introduce the notion of a project
     86
     87Reduce # of methods that read/write sww files (Yes)
    6088
    6189 
     
    6391Efficiency issues
    6492
    65 Parallelisation
     93Parallelisation (First cut is done)
    6694
    6795Edgefluxes are currently computed twice (f01 = -f10)
    68 (This has been fixed by Matt Hardy)
     96(This has been fixed by Matt Hardy in June 2005)
    6997
    7098Increase Timesteps (Implicit techniques?)
    7199
    72 Optimise creation and importing of domains (C-code and caching)
     100Optimise creation and importing of domains (C-code and caching)  (Ole)
    73101
    74102
     
    76104Architecture
    77105
    78 Settle dataflows and formats (pts, dem, msh, sww, etc)
     106Settle dataflows and formats (pts, dem, msh, sww, etc) (Duncan)
    79107 
    80108finaltime to be renamed duration
     
    113141           
    114142
     143        IDEA for set_quantity:
     144              Use keywords and call underlying specific method, e.g.
     145             
     146              if filename is not None:
     147                 vertex_values = caching( fitfunc, filename, dependencies = ...)
     148                 set_quantity(..., ..., vertex_values)
     149              elif:
     150             
     151           
    115152Making methods private, using _private
    116153Or write the API in a separate module.
     
    132169
    133170
    134 Boundary (Dirichlet): Think about specifying values by quantity name
     171Boundary (Dirichlet): Think about specifying values by quantity name (and having defaults)
     172     Dirichlet(stage = 1.0, ymomentum = 0.2)
     173     
     174Finish MOST2SWW with bathymetry(Trevor)     
     175
     176Make Steve's new boundary spatially dependent (Ole)
    135177
    136178Look at matplotlib's verbosity object.
     
    144186
    145187Move py code into files such as quantity_ext.py and have python wrappers with doc strings for all functions. Name the code in extensions _ext and conditional import as usual.
     188
     189Generally separate file_format stuff from functionality (and work with a small number of formats)
     190
     191
     192Have a .tms format for straight timeseries, use sww for f(t,x,y).
     193Modify Interpolation function and file_function accordingly. (Use lwru2.py as test bed)
    146194
    147195
     
    162210
    163211
    164 
     212       
     213-----------
     214Installation and setup
     215
     216- Assume that root dir for AnuGA is on Pythonpath. That way the same code can work with
     217  sandpits and final installation
     218- need installers for all modules       
     219- pmesh needs a compile.py that will compile triangle whan used from a sandpit.
     220  Currently it seems one noods a full setup to use pmesh
     221
     222 
    165223-----------
    166224Development
    167225
    168 Restructuring and moving svn repository
    169 
    170 Flatten directory structure
     226Restructuring and moving svn repository (Ole)
     227
     228Flatten directory structure (OLe or DUncan)
    171229
    172230Apply buildbot
     
    185243- Getting started
    186244- User guide
    187 - Reference manual ? semi automated
     245- Reference manual - semi automated
    188246
    189247Mathematical model description  (Steve & Chris)
     
    198256SMEC (Lex)
    199257CSIRO (Kathy)
     258Watertank study (Okushiri) (Ole)
    200259Macca...
    201260
Note: See TracChangeset for help on using the changeset viewer.