You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
|
#This is the readme document for the modeling of climate change impacts in the Hunter River estuary project
|
|
|
|
|
#participants: Mat Deiber, Tino Heimhuber + 2/3 CVEN Master’s Thesis Students
|
|
|
|
|
#Goal: use state of the art high-resolution climate change projection data (NARCLIM regional climate model ensemble)
|
|
|
|
|
in conjunction with sea level rise scenarios to model the potential impacts of climate change on the hydrodynamics,
|
|
|
|
|
salinity and temperature (potentially water quality) of the estuary system.
|
|
|
|
|
|
|
|
|
|
Folder Structure:
|
|
|
|
|
|
|
|
|
|
Modeling
|
|
|
|
|
01_Input
|
|
|
|
|
BC_Generation (this is where all the rainfall runoff modeling etc. is done for generation of the boundary condition input file for RMA)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Key steps:
|
|
|
|
|
The hydrological and hydrodynamic model is already fully set up and calibrated. We basically just need to create a plausible
|
|
|
|
|
range of future boundary condition scenarios and run them through the model
|
|
|
|
|
|
|
|
|
|
The first step will be to generate new freshwater inflow time series for the small catchments by using NARcLIM forcing data.
|
|
|
|
|
For each catchment, we’ll use the GRID cell of which the GRID centerpoint is closest to the Catchment centerpoint.
|
|
|
|
|
|
|
|
|
|
NARCLIM will provide 12 rainfall time series per gridpoint so we need to adjust the python codes to automate the whole workflow even more.
|
|
|
|
|
|
|
|
|
|
To begin with, we can pick 1-3 scenarios and test how well the “present-day” reanalysis
|
|
|
|
|
data can reproduce the observed catchment flow time series and also how different the NARcLIM ET is from the observed.
|
|
|
|
|
Once we generated 12 RMA boundary condition files, one for each NARCCLIM ensemble member,
|
|
|
|
|
the next step will be to automate the climate change scenario runs for NARcLIM.
|