Open zli867 opened 1 year ago
Hi Zongrun. Thanks for reporting this. I'll talk to Robert, who may be more familiar with the feps_plumerise
code.
Hi Zongrun. Sorry for the delayed response. The FEPS plumerise code hardcodes a maximum time window of 32 days and encounters a segmentation fault if you exceed 32 days. Ideally, FEPS should be updated to support any time window. Alternatively, bluesky could be updated to split up long activity windows into shorter ones, run each separately through FEPS plumerise, and then merge the outputs. We probably won't have time to work on this any time soon. If you'd like to, please issue a pull request with your fix.
Hi Joel, I am trying to run BlueSky for long-lasting wildfires in New Mexico. I found some problems due to the
start
andend
setting in BlueSky. I run two cases with the same fire information exceptstart
andend
settings. The first case starts on2022-05-01T00:00:00
ends on2022-06-09T00:00:00
(WF_Bear_Trap_real.json). The plumerise model (FEPS with auto plume top behavior) reports following error:In the other case, I just changed
end
from2022-06-09T00:00:00
to2022-05-09T00:00:00
(WF_Bear_Trap_shorter.json). BlueSky can be finished without errors. Do you know what happens in this error? Or BlueSky currently cannot support long-lasting wildfire simulation.All inputs and settings can be found at: https://drive.google.com/drive/folders/1LQlD031WZaO330P8uyH1f1B8Qz0t6_Lu?usp=sharing.
Thanks, Zongrun