Two answer changing fixes (fire, DWT_SLASH) and fix for urban streams for Clm45#802
Conversation
…latfirefix This is a fix for ESCOMP#787 for DWT_SLASH
New clm5 paramsfile that has the bad date of 631 changed to 701. Along with some simple bit for bit changes. Removing some problematic options. Making Dynamic Vegetation a deprecated option that requires you to use -ignore_warnings with it.
Move hobart tests to izumi
ekluzek
added
priority: high
|
Strangely I'm getting two unexpected fails: ERS_Ly3.f10_f10_musgs.I1850Clm50BgcCropCmip6.cheyenne_intel.clm-basic I'm rerunning them on ctsm1.0.dev062, to make sure it is indeed a new fail. I think the problem must be in the DWT_SLASH change. |
… since it's now gridcell only
ekluzek
changed the title
|
The list of test that changes answers: DAE_N2_D_Lh12.f10_f10_musgs.I2000Clm50BgcCropGs.cheyenne_intel.clm-DA_multidrv ERI_D_Ld9_P48x1.f10_f10_musgs.I2000Clm50BgcCruGs.izumi_nag.clm-reduceOutput |
samsrabin
added
bug
2 participants
Description of changes
Fire bug fix and DWT_SLASH change and fix urban stream years for clm4_5.
Specific notes
Contributors other than yourself, if any: @lawrencepj1 @olyson
CTSM Issues Fixed (include github issue #): #175, #787, #780
fixes #175 urban stream years for clm4_5
fixes #787 DWT_SLASH field
fixes #780 Bug in CN Fire Li 2016 which used latitude in degrees rather than radians
Are answers expected to change (and if so in what way)? Yes
clm5_0 BGC simulations fire ignition changes due to difference in cosine(lat) with
latitude properly in radian's rather than in degrees
A few fields associated with DWT_SLASH change by a small amount due to the averaging
difference for a few cases
Any User Interface Changes (namelist or namelist defaults changes)? N
Testing performed, if any: regular
Running standard testing on cheyenne and izumi