- Timestamp:
- Mar 1, 2005, 12:50:16 PM (20 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
inundation/ga/storm_surge/pyvolution/wiki/long_term_design.txt
r544 r977 1 1 2 3 Migrate code from domain.py so as much as possible is 4 done in terms of the consecutive arrays. 5 We can then destroy the Python objects after everything has been setup, 6 in order to conserved memory. 2 3 Make origins instances of a georeference class 4 (like class point from GPScape). 5 It would conatin multiple representation, projections and code for adding itself to e.g. NetCDF files. 6 7 7 8 8 9 9 10 Tagged regions, edges etc should be done in terms of set-theory, 10 11 so that each tag maps e.g. to a list of indices. 12 13 14 #DONE AND OBSOLETE 15 #Migrate code from domain.py so as much as possible is 16 #done in terms of the consecutive arrays. 17 #We can then destroy the Python objects after everything has been setup, 18 #in order to conserved memory.
Note: See TracChangeset
for help on using the changeset viewer.