treesmoist.dat not 3D coming from FastFuels Python SDK #9
Unanswered
wxcutch
asked this question in
FastFuels Support
Replies: 1 comment 1 reply
|
@wxcutch I'll follow up with more details and a better plan to fix this on Friday. The export code will write things to 2D or 3D grids depending on what data is available. So you can fix this by changing your code to: tree_inventory = ff.inventories.Inventories.from_domain_id(
domain.id
).create_tree_inventory_from_treemap(
feature_masks=['road', 'water']
)
tree_inventory.wait_until_completed()
tree_grid = (
ff.grids.TreeGridBuilder(domain_id=domain.id)
.with_bulk_density_from_tree_inventory()
.with_uniform_fuel_moisture(100.)
.build()
)
tree_grid.wait_until_completed()Where I added the |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm generating fuel input files for a quicfire run using the FastFuels SDK and when I run QF I get an error about I/O being past the end of the record on treesmoist.dat. When I compare the input files I generated before using FastFuels I noticed treesmoist.dat is 3D (as QF seems to be expecting) but the ones I was generating today were 2D. Any insight on how to solve the problem?
treesfueldepth.datandtreesrhof.datboth come 3D andtopo.datis coming 2D.Surface grid generation code:
Tree grid generation code (run before sfc grid):
All reactions