Best practice for including surface waterbodies in dewatering model setup? #113
andreitablan
started this conversation in
General
Replies: 1 comment 2 replies
-
|
Thanks for your question. I assume you are interested in the lowering of the head because of your dewatering activities. For that, you only need a timflow.transient model. timflow.transient simulates the change in head caused by the transient stresses: in you case the change in head caused by turning on the dewatering pumps. If the water level in the surface water does not change in response to the dewatering (which is common), you can specify them with the River or RiverString element and by specifying |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
We're developing a dewatering calculation workflow where we model drawdown in groundwater due to pumping. Our current approach uses a steady model for initial conditions (natural baseline), then a transient model to simulate the dewatering effect over time.
We now want to account for surface waterbodies (rivers, lakes, canals) as boundary conditions in addition to the phreatic line, since they influence both the initial water table and the drawdown behavior in nearby areas.
We understand that we should represent these as RiverString elements in TimFlow, but we're unsure about the conceptual approach:
Should we add the surface waterbodies to the steady model (natural baseline conditions), the transient model (dewatering scenario), or both?
Which TimFlow model properties/functions would you recommend for setting fixed-head boundary conditions on surface water features?
Any guidance on the best practice would be helpful! :))
Beta Was this translation helpful? Give feedback.
All reactions