Opened 17 years ago
Closed 15 years ago
#191 closed enhancement (fixed)
time varying bathymetry
Reported by: | ole | Owned by: | ole |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | Functionality and features | Version: | |
Severity: | normal | Keywords: | elevation |
Cc: |
Description (last modified by ole)
time varying bathymetry - could be used for sediment transport, coastal erosion, storm surge etc (see ticket:281) Tom has a PhD student looking at aspects of this using 2flow (Ted identified some issues with 2flow for this sort of problem) For hydraulic jumps, can you get a measure of turbulence? Video evidence
Change History (5)
comment:1 Changed 17 years ago by ole
- Description modified (diff)
comment:2 Changed 16 years ago by ole
- Owner changed from someone to ole
comment:3 Changed 15 years ago by ole
comment:4 Changed 15 years ago by ole
Started this process in changeset:7339
comment:5 Changed 15 years ago by nariman
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
I propose introducing a new dictionary: quantities_to_be_stored name: flag where name is a quantity name conserved or not flag is either None (this quantity is not stored), 1 (quantity is stored once) or 2 (quantity stored at every time step)