Comments (17)
Here is the list of Methods I gathered from the code, namelist.suews
. I also listed some of fixed internal parameters inside the code.
WRF-SUEWS coupling system
WRF-SUEWS available methods
Method | Option values | Current value | is used? | Explanation |
---|---|---|---|---|
SnowUse |
(0,1) | 0 | Y | Used but not active |
RoughLenHeatMethod |
(1,2,3,4) | 2 | Y | Kawai et al. (2009) |
RoughLenMomMethod |
(1,2,3) | 2 | Y | (Grimmond and Oke 1999 |
EmissionMethod |
(0,1,2,3) | 2 | Y | Järvi et al. (2011) |
NetRadiationMethod |
(0,1,2,3,100,200,300) | 1 | Y | Q* modelled with L↓ observations supplied |
StorageHeatMethod |
(1,2,3,4) | 1 | Y | Objective Hysteresis Model (OHM) |
AerodynamicResistanceMethod |
(1,2,3) | 2 | Y | Non-neutral stability (Documentation is missing in SUEWS site) |
LaiType |
- | (0,0,0) | Y | LAI calculation choice |
veg_type |
- | 1 | Y | Internal fix parameter |
gsModel |
(1,2) | 2 | Y | Formulation choice for conductance calculation-Internal fixed |
StabilityMethod |
(0,1,2,3,4) | 3 | Y | Defines which atmospheric stability functions are used-Internal fixed |
SMDMethod |
(0,1,2) | 0 | Y | Determines method for calculating soil moisture deficit (SMD) |
EvapMethod |
- | 2 | Y | Internal fix parameter |
LAICalcYes |
- | 1 | Y | Internal fix parameter |
WaterUseMethod |
(0,1) | 0 | Y | Defines how external water use is calculated |
Fixed parameters related to irrigation (Internal Fixed)
Method | Option values | Current value | is used? | Explanation |
---|---|---|---|---|
wu_m3 |
- | 0 | Y | External water use |
Faut |
- | 0 | Y | Fraction of irrigated area using automatic irrigation |
InternalWaterUse_h |
0 | Y | Internal water use [mm h-1] | |
IrrFracConif |
- | 0 | Y | Fraction of evergreen trees which are irrigated |
IrrFracDecid |
- | 0 | Y | Fraction of deciduous trees which are irrigated |
IrrFracGrass |
- | 0 | Y | Fraction of grass which is irrigated |
DayWat |
- | 0 | Y | Days of watering allowed |
DayWatPer |
- | 0 | Y | % of houses following daily water |
Fixed parameters related to snow (Internal Fixed)
Method | Option values | Current value | is used? | Explanation |
---|---|---|---|---|
CRWmax |
- | 0.2 | Y | Free water holding capacity of shallow SnowPack |
CRWmin |
- | 0.05 | Y | Free water holding capacity of deep SnowPack |
PrecipLimit |
- | 2.2 | Y | Temperature limit when precipitation occurs as snow |
PrecipLimitAlb |
- | 2 | Y | Precipitation limit for albedo change (in mm) |
RadMeltFact |
- | 0.001 | Y | Radiation melt factor |
SnowAlbMax |
- | 0.8 | Y | Mximum snow albedo |
SnowAlbMin |
- | 0.18 | Y | Minimum snow albedo |
SnowDensMax |
- | 450 | Y | Minimum density of snow |
SnowDensMin |
- | 100 | Y | Maximum density of snow |
SnowLimBldg |
- | 100 | Y | Snow removal limits for roofs in mm) |
SnowLimPaved |
- | 100 | Y | Snow removal limits for paved surfaces in mm) |
tau_a |
- | 0.01 | Y | Time constans related to albedo change |
tau_f |
- | 0.1 | Y | Time constans related to albedo change |
tau_r |
- | 0.02 | Y | Time constans related to albedo change |
TempMeltFact |
- | 0.12 | Y | Temperature melt factor |
SnowPackLimit |
- | 0 | Y | - |
snowProf_24hr |
- | 0 | Y | Timing of snow removal (0 or 1) Hourly, WD/WE |
from wrf-suews.
Good job!
I'll comment on each parameter below:
(as the OP is too long, I split them into separate posts.)
WRF-SUEWS available methods
Method Option values Current value is used? Explanation
SnowUse
(0,1) 0 Y Used but not active
OK.
RoughLenHeatMethod
(1,2,3,4) 2 Y Kawai et al. (2009)
OK
RoughLenMomMethod
(1,2,3) 2 Y (Grimmond and Oke 1999
OK
EmissionMethod
(0,1,2,3) 2 Y Järvi et al. (2011)
0
should be disabled as no input QF could be provided via forcing data.
NetRadiationMethod
(0,1,2,3,100,200,300) 1 Y Q* modelled with L↓ observations supplied
0
should be disabled as no input Q* could be provided via forcing data.200
: check if we have cloud coverage from forcing data; otherwise disable it.
StorageHeatMethod
(1,2,3,4) 1 Y Objective Hysteresis Model (OHM)
only allow 1
, i.e., OHM, to be used in this coupled version; others should be disabled due to incompatibility in inputs.
AerodynamicResistanceMethod
(1,2,3) 2 Y Non-neutral stability (Documentation is missing in SUEWS site)
this option is not exposed to users and fixed as 2
in offline SUEWS so the documentation is missing from user's perspective; but it is documented in the SUEWS code.
so we may consider using it as an internal option in the coupled version as well to be consistent with the offline version.
LaiType
- (0,0,0) Y LAI calculation choice
OK
veg_type
- 1 Y Internal fix parameter
OK: fixed to be consistent with the offline version.
gsModel
(1,2) 2 Y Formulation choice for conductance calculation-Internal fixed
OK: this option demands more parameters than normal users may understand and have; also the recent runs using the offline version all follow gsModel=2
as in Ward et al. (2016). so we can keep this internally fixed.
StabilityMethod
(0,1,2,3,4) 3 Y Defines which atmospheric stability functions are used-Internal fixed
OK. we keep this fixed as other options have some known issues (documented in the SUEWS code).
SMDMethod
(0,1,2) 0 Y Determines method for calculating soil moisture deficit (SMD)
we can fix this as nowhere else can provide this info: it can only be modelled by SUEWS.
EvapMethod
- 2 Y Internal fix parameter
OK: consistent with the offline version.
LAICalcYes
- 1 Y Internal fix parameter
OK: consistent with the offline version.
WaterUseMethod
(0,1) 0 Y Defines how external water use is calculated
OK: keep this fixed as 0
so SUEWS will model water use as nowhere can wu_m3
be set (i.e., currently infeasible to set this as a forcing).
from wrf-suews.
Fixed parameters related to irrigation (Internal Fixed)
Method Option values Current value is used? Explanation
wu_m3
- 0 Y External water use
OK: consistent with WaterUseMethod
.
Faut
- 0 Y Fraction of irrigated area using automatic irrigation
To change: release this at grid level to allow more controllable irrigation features.
InternalWaterUse_h
0 Y Internal water use [mm h-1]
@suegrimmond what is this? It seems to be pipe loss? this is insufficiently documented. can you provide an example please?
IrrFracConif
- 0 Y Fraction of evergreen trees which are irrigated
To change: release this at grid level to allow more controllable irrigation features.
IrrFracDecid
- 0 Y Fraction of deciduous trees which are irrigated
To change: release this at grid level to allow more controllable irrigation features.
IrrFracGrass
- 0 Y Fraction of grass which is irrigated
To change: release this at grid level to allow more controllable irrigation features.
DayWat
- 0 Y Days of watering allowed
To change: release this at grid level to allow more controllable irrigation features.
DayWatPer
- 0 Y % of houses following daily water
To change: release this at grid level to allow more controllable irrigation features.
from wrf-suews.
Fixed parameters related to snow (Internal Fixed)
Method Option values Current value is used? Explanation
CRWmax
- 0.2 Y Free water holding capacity of shallow SnowPack
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
CRWmin
- 0.05 Y Free water holding capacity of deep SnowPack
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
PrecipLimit
- 2.2 Y Temperature limit when precipitation occurs as snow
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
PrecipLimitAlb
- 2 Y Precipitation limit for albedo change (in mm)
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
RadMeltFact
- 0.001 Y Radiation melt factor
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
SnowAlbMax
- 0.8 Y Mximum snow albedo
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
SnowAlbMin
- 0.18 Y Minimum snow albedo
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
SnowDensMax
- 450 Y Minimum density of snow
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
SnowDensMin
- 100 Y Maximum density of snow
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
SnowLimBldg
- 100 Y Snow removal limits for roofs in mm)
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
SnowLimPaved
- 100 Y Snow removal limits for paved surfaces in mm)
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
tau_a
- 0.01 Y Time constans related to albedo change
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
tau_f
- 0.1 Y Time constans related to albedo change
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
tau_r
- 0.02 Y Time constans related to albedo change
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
TempMeltFact
- 0.12 Y Temperature melt factor
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
SnowPackLimit
- 0 Y TS note based on snow source code: threshold to determine snow coverage using depletion curves in Valeo and Ho (2004)
To change: release this at simulation/run level (i.e., changes via namelist.suews
) to consistent snow-related physics.
snowProf_24hr
- 0 Y Timing of snow removal (0 or 1) Hourly, WD/WE
To change: release this at grid level (i.e., changes via wrfinput
) to allow more controllable snow removal feature.
from wrf-suews.
Ok I will work on these. I think these are + the ones are released before all the methods right?
from wrf-suews.
I think these are + the ones are released before all the methods right?
I didn't get you for this.
let's have a chat you are in.
from wrf-suews.
@sunt05
snowProf_24hr
wouldn't this make sense to be released in namelist.suews
similar to other 24 hours profiles?
from wrf-suews.
@sunt05
snowProf_24hr
wouldn't this make sense to be released innamelist.suews
similar to other 24 hours profiles?
Yes, release it as other profile parameters.
Sorry, I might have confused myself when posting it.
from wrf-suews.
All the above are fixed (in test-dev
branch). I will merge it to master when the test is finished. The only one that I will fix after the test is NetRadiationMethod = 200
and cloud fraction
from wrf-suews.
@sunt05
I have a technical question. I am trying to put a checker on methods in module_sf_suews.F
. For example for EmissionsMethod, something like this:
opt = EmissionsMethod
IF ( .NOT.opt.EQ.1 .AND. .NOT.opt.EQ.2 .AND. .NOT.opt.EQ.3 .AND. .NOT.opt.EQ.4 ) THEN
CALL wrf_error_fatal( "Invalid EmissionsMethod option. It should be 1,2,3, or 4" )
ENDIF
It seems that no matter what the value of EmissionMethod is in namelist.suews
, it enters this IF statement
. I am a little bit confused. Do you have any idea? Maybe I am missing something her
from wrf-suews.
from wrf-suews.
from wrf-suews.
@suegrimmond It is a good option for this method, but for example for NetRadiationMethod which has values of 1,2,3,100,200,300 wouldn't be the most efficient I guess?
from wrf-suews.
mm, so .note. might apply to opt first? that is confusing. when I test this separately, it works!
from wrf-suews.
It just occurred to me that DLS issue is not resolved yet.
In module_sf_suews.F
:
INTEGER,PARAMETER::startDLS=85 !DOY when daylight saving starts
INTEGER,PARAMETER::endDLS=302 !DOY when daylight saving ends
they are still fixed.
Given the fact DLS policies are conducted at the regional/state level (http://www.webexhibits.org/daylightsaving/g.html), we may consider releasing these two via namelist.suews
.
How do you think?
from wrf-suews.
Yes, this is in my TODO list. I will release these ones.
from wrf-suews.
By adding the cloud fraction from WRF to SUEWS, I think all the aspects of this post is resolved. Therefore, I close it.
from wrf-suews.
Related Issues (20)
- Integrating pre-process scripts for inputs with automated scripts for building WRF-SUEWS source code HOT 2
- Representation of crops in WRF-SUEWS HOT 3
- New runs over London domain HOT 5
- Runs stop for Jan runs after beginning of 4 days HOT 4
- include `snowuse` method in the coupled version
- TODO: SUEWS fatal error needs to communicate with WRF fatal error HOT 3
- improve the re-gridding function HOT 3
- QF profile and time zone HOT 1
- Colombo initial runs HOT 9
- Different observation and forcing data for Swindon HOT 1
- T2 estimation HOT 2
- Two-way nesting WRF-SUEWS HOT 5
- Two-way Nesting HOT 26
- set up a workflow to pack coupled code as a release HOT 1
- WSPS, including text and code, needs to be revised to make the steps more general.
- What to do if someone is new to git and python?
- new function / fix a bug
- Description of variables in namelist.suews file
- WRF-SUEWS testings on Jasmin HOT 1
- How to load custom variables in `wrfinput` to runtime calculations?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wrf-suews.