Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/barneydobson/integrated-modelling-template
Integrated modelling workshop and repository template
https://github.com/barneydobson/integrated-modelling-template
Last synced: about 1 month ago
JSON representation
Integrated modelling workshop and repository template
- Host: GitHub
- URL: https://github.com/barneydobson/integrated-modelling-template
- Owner: barneydobson
- Created: 2024-08-01T08:18:11.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2024-12-02T09:38:58.000Z (about 2 months ago)
- Last Synced: 2024-12-02T10:29:37.956Z (about 2 months ago)
- Language: Python
- Homepage:
- Size: 3.04 MB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- Contributing: docs/CONTRIBUTING.md
Awesome Lists containing this project
README
# Integrated modelling workshop
Overview of the technical parts of the workshop:
Day 2
- 09:00-09:10 Explain the day (now)
- 09:10-09:40 Present overviews:
- [Inputs/outputs](#water-in-water-out)
- [Conceptual diagram](#conceptual-diagram)
- 09:40-13:30 (30 min coffee break, 1 hour lunch break):
- [Fill in integration templates](#20-minute-integration-template)
Day 3
- 09:30-11:30 (30 min coffee break):
- [Give shape to your project](#what-next)
- 13:00-14:30:
- [Make a GitHub for your project](#turn-your-plan-into-github-issues)
## Example: groundwater (MODFLOW) and supply distribution (EPANET)
I don't know either of these models well, I just asked ChatGPT for info in the
inputs/outputs. These examples will be used throughout this explanation
## Introduction (pre-workshop homework)
Please do this section before the workshop and include it preferably in your group's presentation on Day 1 (some groups may present in Day 2 if they need so). The individual participants (not assigned to preliminary groups) can present their model/system in Day 2. You only need to do one model/system that you can describe in < 4-5 min during the workshop.
Explain your system, I will present groundwater and supply distribution side-by
-side.
### Water in-water out
Where does water/pollutants come in/go out?
MODFLOWEPANET
Inputs
Recharge from surface (includes precipitation, irrigation, or other surface water bodies).
Reservoirs, with a fixed head thus representing a large store.
Rivers and streams (boundary condition model).
Tanks, sources or sinks with variable elevation and head.
Generalised/fixed head boundaries (reservoirs, lakes, lateral aquifer flows?)
Other external inflows.
Point and distributed pollutant sources/Injection wells.
Outputs
Generalised/fixed head boundaries.
Nodes representing demand.
Rivers and streams (boundary condition model).
Tanks, sources or sinks with variable elevation and head.
Evapotranspiration.
Reservoirs, with a fixed head thus representing a large store.
Extraction wells.
Leaks and valves.
### Conceptual diagram
Other information is fine, but make sure to highlight all of your inputs and
outputs, in particular dynamic ones!
_Made with [draw.io](https://app.diagrams.net/?src=about#)_
## 20-minute integration template
You can find a fillable version [here](https://forms.gle/QNAvMLefKcAe4EoBA).
- [What models/systems do you care about?](#models)
- [Do any inputs/outputs directly match?](#direct-integration)
- [Do any inputs/outputs indirectly match?](#indirect-integration)
- [Update conceptual diagram](#conceptual-diagram-integrated)
- [Explore feasibility](#explore-feasibility)
### Models
- Groundwater: MODFLOW
- Supply distribution: EPANET
### Direct integration
- Leaks/Valves -> MODFLOW? I guess leak could be a point water/pollutant source,
or maybe aggregate into recharge from surface.
- If there is a groundwater supply borehole, then that could be pumped from
MODFLOW enter the EPANET tanks?
- EPANET reservoirs seem like the system outflow - perhaps some of this can go
into MODFLOW depending on the case study.
### Indirect integration
- Generalised head boundaries in MODFLOW - maybe these could match with network
head in distribution? Presumably enabling infiltration (in the unpressurised
sections) or exfiltration (anywhere).
- Leaks/valves -> MODFLOW via river interactions (depends where the leaks go..).
- Garden water use interacting with recharge/evapotranspiration (probably needs
a model to 'translate' the EPANET demand outputs).
### Conceptual diagram integrated
Make sure to highlight all of your inputs, outputs and integration links!
### Explore feasibility
Note, you're not expected to complete all of this in the 20-minutes, but please
at least try and have a go at **1.**!
1. **Are these identified integrations likely to induce boundary condition errors
in one system or the other! (i.e., why integrate)**
2. What temporal scale mismatches exist?
3. What spatial scale mismatches exist?
4. How complicated are the processes in between [indirect integration](#indirect-integration)?
5. What kind of case studies might these work for?
For example:
1. Would the integration tell us anything important?
- Anecdotal evidence that leakage plays a significant groundwater source in urban
areas (i.e., importance of exfiltration), though this is probably more useful for
leakage estimation because groundwater will not be that sensitive to the day-to-day
dynamics of leakage.
- Suppose distribution networks are nearly
always pressurised (i.e., unimportance of infiltration).
- Garden water use can be
seasonally a very significant portion of water supply, though unsure if this is
over timescales that would impact groundwater (i.e., unknown importance of garden
water use).
- Although boreholes do provide supply, I would expect that daily variations
that EPANET captures are unlikely to significantly impact groundwater (i.e., expected
unusefulness of abstraction), same is probably true for outflows/leaks.
2. Temporal scale mismatch:
- EPANET typically run at 1-15 minute resolution.
- MODFLOW at daily or monthly, or possibly hourly on small scales.
- The resolutions aren't aligned, but not insurmountable. The more important
question is whether there will be any interesting questions that can be
answered if the dynamics that EPANET provides are mostly smoothed out.
3. Spatial scale mismatch:
- Both models accommodate wide variety of scales.
- Key spatial challenge is mapping pipes to MODFLOW grid.
4. Indirect processes:
- The infiltration/exfiltration "adaptor" doesn't sound overwhelmingly
complicated to me, accommodating the scale mismatches sounds hardest part.
Validating it may be difficult because of lack of data.
- Garden water use is a reasonably well-studied field, don't anticipate
significant difficulties.
5. Case studies:
- Whether integration is interesting seems to rely heavily on the temporal scales
being sufficiently near that the dynamics may interact. Presumably the most
promising case studies would thus have quick to respond groundwater (gravels,
etc.) and also be on relatively small scales (e.g., distribution network
causing localised basement flooding).
- Highly urbanised areas seems to be a given considering the EPANET focus.
- Leaks->rivers, outfalls->groundwater, or groundwater->infiltration seem to
be unlikely for the most part, but there may be specific case studies where
this behaviour occurs.
## What next?
1. Identify a research question(s) - why integrate?
2. Formalise your integrated conceptual model, using it as a map to build around:
- Include the internal model processes as well as interactions.
- Identify if you have any relevant case studies, even if they only cover
part of the integrated conceptual model.
- Consider scale mismatches in more detail, map where this mismatches occur
and what can be done to fix them.
- How do the model software work? Which bits can be interfaced with and which
will require something custom? Is new code required, where?
3. Make a plan:
- Who is in charge?
- What are the key tasks and how long might they take?
- Who can do what?
- What's missing?
### Turn your plan into GitHub issues
If you want to use this page to take your project further then please use
the [GitHub template](docs/template.md), and read [contributing](docs/CONTRIBUTING.md)
You can use the GitHub [issues](https://github.com/barneydobson/integrated-modelling-template/issues) as a to do list. With an added bonus that your `git`
setup will already be in place when it comes to software development.
**Hint:** It may be easiest to start trying to create a standard WSIMOD node that has your required inputs and outputs, and then thinking about
wrapping a more complex model.
It is sensible to organise issues with ["big-picture"](https://github.com/barneydobson/integrated-modelling-template/issues/9) issues and checklists.
And then use separate issues when you are ready to get [specific](https://github.com/barneydobson/integrated-modelling-template/issues/10).
