source: inundation/ga/storm_surge/pyvolution/HUSK.txt @ 643

Have the quantity label e.g. elevation, associated with the data in sww files.

Do data manager for non-smooth data + tests. Smooth is OK (7/9)
                
        
Perhaps control old/new style with minimum_allowed height
In any case get rid of old style.
Then optimise protect_against.....
        
Test friction term!

        
Create a pyvolution_interfaces.py module with all getters/setters
converts etc.


gradient should not require qs to be numeric arrays anymore.!!


Let rectangular mesh and others 
like it to generat the three lists for use when instantiating
Mesh and DOmain objects.


Don't use default conserved qs - hardwire into shallow_water.py
Even hardwire pertinent arrays from cons quan into shallow_water and use directly with flux etc


Interface

 set_quantity should be ablt take either a function or an array.
 

Design:  
explicit and implicit updates should be stored in each quantity. 

Create repr of a domain such that it lists all its parameters e.g. order