Ignore:
Timestamp:
Jun 14, 2013, 9:13:24 PM (12 years ago)
Author:
steve
Message:

Small changes to deal with spatial functions

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/anuga_core/source/anuga/shallow_water/boundaries.py

    r8820 r8920  
    496496
    497497    This function is a thin wrapper around the generic File_boundary. The
    498     difference between the file_boundary and field_boundary is only that the
    499     field_boundary will allow you to change the level of the stage height when
     498    difference between the File_boundary and Field_boundary is only that the
     499    Field_boundary will allow you to change the level of the stage height when
    500500    you read in the boundary condition. This is very useful when running
    501501    different tide heights in the same area as you need only to convert one
    502502    boundary condition to a SWW file, ideally for tide height of 0 m
    503     (saving disk space). Then you can use field_boundary to read this SWW file
     503    (saving disk space). Then you can use Field_boundary to read this SWW file
    504504    and change the stage height (tide) on the fly depending on the scenario.
    505505    """
Note: See TracChangeset for help on using the changeset viewer.