-
Notifications
You must be signed in to change notification settings - Fork 12
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
set_fire_params: fuel category out of bounds with WRF-CHEM #32
Comments
nfuel_cat is all zeros, never changed after module_alloc_space
|
namelist input has ifire = 0, 1 ,1 running the fire model on domain 2 and 3, but domain 2 did not have the data |
After changing namelist.input to ifire = 0,0,1 a segfault and it never gets to the fire code:
|
stock WRF4.2 /glade/p/univ/ucud0004/jmandel/WRF42-chem-debug at b353810 |
in /glade/p/univ/ucud0004/jmandel/WRF-SFIRE-chem/test/em_inv_chem with ifire=0, 0, 0 |
serial build with full debugging /glade/p/univ/ucud0004/jmandel/WRF-SFIRE-chem-debug: serial build with full debugging, unmodified WRF4.2 /glade/u/home/jmandel/p/WRF42-chem-debug |
/glade/u/home/jmandel/p/nochem-fire
with ifire=0,1,1 nfuel_cat and tign_g are zero in domain 2 |
in Registry/registry.fire |
watchpoint on zsf(1000,1000) address from print_2d_stats
|
branch develop-32 |
Also found that DZDXF = DZDYF = 0. Add a check for this in driver, and fix in geogrid table. |
The problem goes away with newly generated input files. Apparently files corrupt in some way. |
Was there any resolution to this other than the corrupted met_em files? Or was it the fuel files that were corrupt? I am running into exactly this issue with WRF-Fire and can't figure it out. |
@jtaylo41 would you like to provide more specific information? I can look into that if you still have the problem with current master branch from here, ifire=1, and WPS 4.4. There were some issues with support of fire data in previous versions of WPS. |
Hi Jan, I was able to fix this by using a different namelist.fire input file that included the S&B 25 fuel categories -- simple fix. The fuel categories did not line up with what I expected (121 and 141 for example) which is what confused me quite a lot, but that was just because I did not understand the S&B model. Thanks! |
copied to /glade/p/univ/ucud0004/jmandel/WRF-SFIRE-chem/test/em_inv_chem
SFIRE:git commit 60811b1
SFIRE:reading emissions table for 13 fuel categories
SFIRE:crash: set_fire_params: fuel category out of bounds
The text was updated successfully, but these errors were encountered: