Changeset 1739

Timestamp:

Aug 23, 2005, 2:27:05 PM (19 years ago)

Author:

ole

Message:

Recovered comments from 18 Aug

File:

• inundation/wiki/future_directions.txt (modified) (10 diffs)

inundation/wiki/future_directions.txt

@@ -21 +21 @@
 Functionality issues
 
-Mesh generation:
+Mesh generation: (Duncan)
     Through graphical generator
     Through scripts
     Alternative triangulators (Strang, ?.)
     alpha-shapes
-
-refactoring triangle interface
-outputting a ?triangle? readable file (from pmesh?)
-
-  from pmesh issues file:
-      Main issues  (TBA)  
-
+    
+
+   refactoring triangle interface
+   outputting a "triangle" readable file (from pmesh?)
+   
+   simple method in mesh factory that will convert regularly gridded data to mesh using 
+   points as vertices 
+
+Pmesh (Duncan)
+    - from pmesh issues file:
+        Main issues  (TBA)  
+      
+    - Better API for handling (scripted) meshes:
+        *Error messages
+        *Refined regions should be specified easily
+        *Ways of handling different point sets (e.g. 10m, 100m, 250m) 
+         and populate according to refinement of mesh
+          
+      
 Georeferencing
   Code works in UTM coordinates. Zone boundaries cannot be crossed
   Could code be cast in terms of lat/lons?
-
-least_squares, use of quad-tree may not use all datapoints 
-        (currently fixed by expand search, need algorithm for searching neighbouring    treenodes)
+  make sure that georeferencing is used consistently (domain, pmesh, sww files, ...) (Duncan)  
+
+Least_squares, (Duncan) 
+        use of quad-tree may not use all datapoints 
+        (currently fixed by expand search, need algorithm for searching neighbouring treenodes)
 
         Give feedback when
                 points outside mesh
                 mesh outside points boundary
-
-        use sparse matrix (CSR) format in ?build_interpolation_matrix_A?
+                if mesh is corrupted (see lwru2.py and create_mesh.py in debug dir)
+                if segments are repeated (maybe in mesh.check_integrity)    
+
+        use sparse matrix (CSR) format in "build_interpolation_matrix_A"
         simplify geo-referencing (make sure that coordinate changes 'change_points' are 
-        used everywhere
-        memory issue: Compute self.Atz directly and avoid self.A
-
+        used everywhere)
+        
+        memory issue: ! 
+                If LS is used for fitting 
+                    compute self.Atz and self AtA directly and avoid self.A. 
+                    need alpha 
+                If LS is to be used for interpolation 
+                    compute self.A
+                    no alpha needed
+                
+                
+refactor interpolate_sww in terms of Interpolation_function (Ole or Duncan)
+
+                
 Checkpointing (largely done but needs to be revisited)
 
@@ -56 +83 @@
 
 
-File management (msh, pts, dem, ..) ? introduce the notion of a project
- - reduce # of methods that read/write sww files (Yes)
+File management (msh, pts, dem, ..) - introduce the notion of a project
+
+Reduce # of methods that read/write sww files (Yes)
 
  
@@ -63 +91 @@
 Efficiency issues
 
-Parallelisation
+Parallelisation (First cut is done)
 
 Edgefluxes are currently computed twice (f01 = -f10) 
-(This has been fixed by Matt Hardy)
+(This has been fixed by Matt Hardy in June 2005)
 
 Increase Timesteps (Implicit techniques?)
 
-Optimise creation and importing of domains (C-code and caching) 
+Optimise creation and importing of domains (C-code and caching)  (Ole)
 
 
@@ -76 +104 @@
 Architecture
 
-Settle dataflows and formats (pts, dem, msh, sww, etc)
+Settle dataflows and formats (pts, dem, msh, sww, etc) (Duncan)
  
 finaltime to be renamed duration
@@ -113 +141 @@
             
 
+        IDEA for set_quantity:
+              Use keywords and call underlying specific method, e.g.
+              
+              if filename is not None:
+                 vertex_values = caching( fitfunc, filename, dependencies = ...)
+                 set_quantity(..., ..., vertex_values) 
+              elif:
+              
+            
 Making methods private, using _private
 Or write the API in a separate module.
@@ -132 +169 @@
 
 
-Boundary (Dirichlet): Think about specifying values by quantity name
+Boundary (Dirichlet): Think about specifying values by quantity name (and having defaults)
+     Dirichlet(stage = 1.0, ymomentum = 0.2)
+     
+Finish MOST2SWW with bathymetry(Trevor)     
+
+Make Steve's new boundary spatially dependent (Ole)
 
 Look at matplotlib's verbosity object.
@@ -144 +186 @@
 
 Move 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.
+
+Generally separate file_format stuff from functionality (and work with a small number of formats)
+
+
+Have a .tms format for straight timeseries, use sww for f(t,x,y).
+Modify Interpolation function and file_function accordingly. (Use lwru2.py as test bed)
 
 
@@ -162 +210 @@
 
 
-
+        
+-----------
+Installation and setup
+
+- Assume that root dir for AnuGA is on Pythonpath. That way the same code can work with 
+  sandpits and final installation
+- need installers for all modules       
+- pmesh needs a compile.py that will compile triangle whan used from a sandpit. 
+  Currently it seems one noods a full setup to use pmesh 
+
+  
 -----------
 Development
 
-Restructuring and moving svn repository
-
-Flatten directory structure
+Restructuring and moving svn repository (Ole)
+
+Flatten directory structure (OLe or DUncan)
 
 Apply buildbot
@@ -185 +243 @@
 - Getting started 
 - User guide
-- Reference manual ? semi automated
+- Reference manual - semi automated
 
 Mathematical model description  (Steve & Chris)
@@ -198 +256 @@
 SMEC (Lex)
 CSIRO (Kathy)
+Watertank study (Okushiri) (Ole)
 Macca...