Difference between revisions of "Set up PIHM for NTL"
From Age of Water
| (One intermediate revision by one user not shown) | |||
| Line 3: | Line 3: | ||
Plans for how to integrate lakes with PIHM, progressively more complex: | Plans for how to integrate lakes with PIHM, progressively more complex: | ||
| − | # Constant lake level | + | # Constant lake level. Streams flow in, flow out. |
| − | # Time variable boundary conditions (weakly coupled lake model) | + | # Time variable boundary conditions (weakly coupled with lake model). Prescribe levels in the lake from data or GLM. |
| − | # Sequential coupling | + | # Sequential coupling. Run PIHM, pass fluxes into GLM, pass the level back to PIHM. |
Other properties for initial runs: | Other properties for initial runs: | ||
* 30 year simulation period (1979-2009) | * 30 year simulation period (1979-2009) | ||
* Use 40 m deep land surface. (Aquifer consists of 40 to 60 m of unconsolidated Pleistocene glacial deposits, mostly glacial outwash sands and gravel. Horizontal hydraulic conductivities are estimated to be ~10 m/day Pint et al 2003). | * Use 40 m deep land surface. (Aquifer consists of 40 to 60 m of unconsolidated Pleistocene glacial deposits, mostly glacial outwash sands and gravel. Horizontal hydraulic conductivities are estimated to be ~10 m/day Pint et al 2003). | ||
| − | * Start with uniform soils | + | * Start with uniform soils. |
* Use single atmospheric data set for entire domain. Two options, hydroterre forcing data or NTL data. | * Use single atmospheric data set for entire domain. Two options, hydroterre forcing data or NTL data. | ||
* Define dirichlet boundary condition (fixed as constant head) for all lakes in the catchment. Start with median lake levels. Can then implement time variable from GLM. | * Define dirichlet boundary condition (fixed as constant head) for all lakes in the catchment. Start with median lake levels. Can then implement time variable from GLM. | ||
| − | * No lake ice for now | + | * No lake ice for now. |
* Inlet boundary condition for riv file? | * Inlet boundary condition for riv file? | ||
| Line 20: | Line 20: | ||
{{#set: | {{#set: | ||
Owner=Hilary_Dugan| | Owner=Hilary_Dugan| | ||
| − | |||
Participants=Chris_Duffy| | Participants=Chris_Duffy| | ||
| + | Participants=Lele_Shu| | ||
StartDate=2015-04-21| | StartDate=2015-04-21| | ||
| + | SubTask=Construct_catchment_mesh| | ||
TargetDate=2015-05-31| | TargetDate=2015-05-31| | ||
Type=Medium}} | Type=Medium}} | ||
Latest revision as of 16:37, 23 April 2015
Setup PIHM for North Temperate Lakes
Plans for how to integrate lakes with PIHM, progressively more complex:
- Constant lake level. Streams flow in, flow out.
- Time variable boundary conditions (weakly coupled with lake model). Prescribe levels in the lake from data or GLM.
- Sequential coupling. Run PIHM, pass fluxes into GLM, pass the level back to PIHM.
Other properties for initial runs:
- 30 year simulation period (1979-2009)
- Use 40 m deep land surface. (Aquifer consists of 40 to 60 m of unconsolidated Pleistocene glacial deposits, mostly glacial outwash sands and gravel. Horizontal hydraulic conductivities are estimated to be ~10 m/day Pint et al 2003).
- Start with uniform soils.
- Use single atmospheric data set for entire domain. Two options, hydroterre forcing data or NTL data.
- Define dirichlet boundary condition (fixed as constant head) for all lakes in the catchment. Start with median lake levels. Can then implement time variable from GLM.
- No lake ice for now.
- Inlet boundary condition for riv file?
