-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend CNFireMethodMod with a FATESFireData class #991
Changes from 27 commits
51f3107
af1f812
4e7a95a
fb2119b
78fb2db
67b82a1
2fc0ede
49d2ee6
c6fdf8c
261a01c
35ec07f
9866d97
8446296
f530c99
754b1dc
3f643ef
e3c4bc7
d6c9b70
0629073
e542dfe
ffd5edb
e011c10
35c9b8a
ee8a91d
e125730
b583b4f
3a08127
4cd75f6
d1b7f16
f68ac40
89cdc67
8f3d430
4596717
4bed6e2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -822,7 +822,7 @@ sub make_env_run { | |
conopts=>"-phys clm4_0", | ||
}, | ||
"usespitfireButNOTFATES" =>{ options=>"-envxml_dir . -no-megan", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. does this allow use spitfire without FATES? The name suggests that to me... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @jkshuman this belongs to a list of options that trigger namelist FAILs. The specific one triggers a failure if |
||
namelst=>"use_fates_spitfire=.true.", | ||
namelst=>"fates_spitfire_mode>0", | ||
GLC_TWO_WAY_COUPLING=>"FALSE", | ||
conopts=>"-phys clm4_5", | ||
}, | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
use_fates_spitfire= .false. | ||
fates_spitfire_mode = 0 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
Testing capability to read/use lightning frequency & population density | ||
datasets. Calculates natural ignitions from lightning using the SPITFIRE | ||
formulation and anthropogenic ignitions using the Li et al. formulation | ||
copied from CTSM-CN's fire model. | ||
slevis-lmwg marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
Testing does not include a separate test for reading/using a successful | ||
ignitions dataset which uses the same format and units so handling | ||
is the same until you're in subroutine area_burnt_intensity where for | ||
"successful ignitions" the model selects | ||
currentSite%FDI = 1.0_r8 | ||
cloud_to_ground_strikes = 1.0_r8 | ||
while for lightning the model can use values < 1 for both. | ||
|
||
Lara Kueppers (UC-Berkeley) has access to a "successful ignitions" | ||
dataset for California that has not been placed in the repository of | ||
CTSM datasets as of 2020/6/6. That dataset can be used with the | ||
following settings: | ||
|
||
fire_method = 'spitfire' | ||
fates_spitfire_mode = 3 | ||
stream_fldfilename_lightng = '.../data_UCB/observed/CA_monthly_ignition_number_1980-2016/ignition_1980_to_2016_monthly_20190801.nc' | ||
stream_year_first_lightng = 1980 | ||
stream_year_last_lightng = 2016 | ||
model_year_align_lightng = 1980 | ||
|
||
where {...} = /fs/cgd/data0/slevis on izumi and /glade/work/slevis on cheyenne. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
fire_method = 'spitfire' | ||
fates_spitfire_mode = 4 | ||
hist_nhtfrq = 0 | ||
hist_mfilt = 1 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
use_fates_spitfire = .true. | ||
fates_spitfire_mode = 1 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New line 949 works
However, I wish the commented-out line above it would work because it would narrow things down, but it doesn't work. The run proceeds to the next else and sets
cnfireson = .false.
.@ekluzek do you see an obvious problem with new line 948?