AMAPstudio

User Tools


Fuel Manager Initial Dialog

Back to the Fuel Manager home page.

Several creation modes for generating a 3D vegetation scene of the Fuel Manager are currently available throughout this user interface. Back to Quick Start Guide.

Select the option and click on GENERATE THE SCENE. The seed value is used to parametrize the stochasticity of the Fuel Manager. When 0 (default value) or a another positive number is chosen, it will be used as a seed to initialize pseudo random number for the run. If the same number is used on different architecture, but on the same version of the software, a same sequence of action will produce exactly the same data. These is a useful property for run and study replicability. When a negative number is chosen, random number sequences will always be different so that runs will always produce slightly different results. This mode is useful for sensitivity analysis of the fuel manager, but also of the fire model (if one is used).

FROM FIELD PARAMETERS

This option is the most flexible. Several file examples can be found in capsis4/data/fireparadox/fromFieldParameters. The format definition is described below

Terrain definition (mandatory)

namecellWidth(m)altitude(m)xMinyMinxMaxyMax
Terrain010000200200
  • here a [0 200] x [0 200] m2.
  • the cellWidth is used to speed up Plant localization. It has to be a multiple of xMax-xMin and yMax-yMin.

Polygon (optional, used to define location for PlantGroups or for LayerSets)

Here below, polygon 1 is a square polygon of 50×50 m2.

PolygonIdlist of polygon summits
1{(0,0);(50,0);(50,50);(0,50)}

Plant format (optional, detailed inventory format)

Plant numberspecies x y z dbh h cbh cd liveLMC liveTMC deadTMC
1Pinus halepensis 100 100 0 50 20 10 10 100 80 10
2Pinus halepensis 150 150 0 10 5 5 10 100 80 10
  • Plant number: this number does not matter but is useful to organize in files when numerous Plants.
  • x, y, z: location of the plant base in m.
  • dbh: diameter at breast height in cm.
  • h, cbh, cd: height, crown base height, crown diameter (m)
  • liveMC, liveTMC, deadTMC: live/dead, Leaves/Twigs Moisture content (% of dry mass)

Plant with crown damage (optional, detailed inventory)

Example given in file capsis4/data/fireparadox/fromFieldParameters/Mixed_stand_with_fire_effects.txt

Plant numberspeciesxyzdbhhcbhcdminBLCmaxBLCmeanBLCCSHCVSstatus
1Pinus pinea01.5015.48.32.72.5800.10.052.811
  • x, y, z: location of the tree trunk base in m.
  • dbh: diameter at breast height in cm.
  • h, cbh, cd: height, crown base height, crown diameter (m)
  • minBLC, maxBLC, meanBLC: min, max and mean Bole Length Charred (m)
  • CSH, CVS: crown scortch height (m), crown volume scorched (%)
  • status: 0:dead, 1: alive, -1 unknown (will be computed from damage by empirical fire effect models

Note: the “pattern sketcher” render for tree should be selected (with the option “by fire damage”) to visualized damage with the 3D Editor.

Plant group format (optional, observed plant distribution)

Stem density with a range of DBH of pinus banksiana in polygon with PolygonId=2

Plant group numberspeciespolygonIdlDBHuDBHageNliveLMCliveTMCdeadTMC
1Pinus banksiana2203005078.473.09.8
  • Plant group number: this number does not matter but is useful to organize in files when numerous plant groups.
  • lDBH,uDBH: lower and upper boundary for diameter at breast height in cm.
  • age : in year. Only matters when allometric equations for this species account for age (eg, Pinus pinaster).
  • N: stem density in polygon (stem/hectare), hectare = 10000 m2.
  • liveMC, liveTMC, deadTMC: live/dead, Leaves/Twigs Moisture content (% of dry mass).

Plant group 2 format (optional, simulated plant distribution, for Aleppo pine only)

Within a polygon as a function of stand parameters.

Plant Group numberspeciespolygonIdhDom50ageNgHaET FactorGibbsliveLMCliveTMCdeadTMC
1Pinus halepensis1164080005.01008010
  • Plant group number: this number does not matter but is useful to organize in files when numerous plant groups.
  • Age : stand age in year
  • N: stem density in polygon (stem/hectare), hectare = 10000 m2
  • Gibbs: parameter for aggregation. 0=random
  • gHaETfactor: st deviation for basal area (m<sub>2</sup>ha<sub>-1</sup>) computation from tree space index (from -2 to 2..)

LayerSet (optional, collection of fuel layer within a polygon)

Eg, LayerSet 1 is attached polygon 1

LayerSet NumberpolygonIdColor(RGV)
11100,255,0
  • A polygon can be attached to several layerSets.
  • When the RGB is not correct (typically -1,-1,-1), a RGB will be computed for the LayerSet according to the load of water available inside (from yellow for dry and low fuel load to green for wet and high fuel load).

Layer definition (optional, a LayerSet should be defined if used)

LayerSet NumberspecieshcbhCdspatial GrouplMCdMClBDdBDmvrsvr
1Quercus coccifera0.750.00.702.0070.010.01.00.1500.05000.0
1Brachypodium ramosum0.250.00.200.5110.00.00.40.0500.010000.0
  • h, cbh, d: height, crown base height, characteristicSize of clump (m).
  • spatialGroup:
    • when same spatialGroup number in a LayerSet: layer horizontal distributions are independent (one to the other).
    • when different spatialGroup number in a LayerSet: layer horizontal distribution are dependent (the two fuel type will be at different locations).
  • liveMC, liveTMC, deadTMC: live/dead, Leaves/Twigs Moisture content (% of dry mass).

Succession model for layerSet (Optional)

e.g. in file data/fireparadox/fromFieldParameters/Dynamic_stand.txt

Succession model layerSet characteristics

LayerSetagefertilitylastClearingTypetreatmentEffect
1101.510.0
221.510.0
  • age: LayerSet age since last clearing.
  • fertility: from 0 (best) to 3.
  • treatmentEffect: unused yet.

Succession model layer characteristics

layerSetshrubCShrubDshrubLiveFractionherbCherbDliveMCDeadMC
10.804.00.80.301.07010.0
20.504.00.80.301.07010.0
  • shrubC, shrubD: shrub cover fraction and clump size (m).
  • shrubLiveFraction: fraction of live fuel in shrub mass (between 0 and 1).
  • herbC, herbD: herb cover fraction and clump size (m).
  • liveMC, deadTMC: live/dead Moisture content (% of dry mass).

FROM A DETAILLED INVENTORY FILE

A detailed inventory file can be loaded: it describes each vegetation object in details throughout its species, crown dimensions and location. It doesn’t require an access to the EUROFORESTFUELS database because it doesn’t contain vegetation object “ID” of the database.

  • For Viewing Only

This sub option is planned when user doesn’t need to run an export of the vegetation scene to be able to run the fire behaviour model. It enables to display on the vegetation scene a wider range of vegetation objects than those stored in the EUROFORESTFUELS database.

As example, an inventory file “Lamanon_Mixed.scene” is available in the given CAPSIS archive and precisely in the “capsis4_fireparadox\data\fireparadox” directory. The file describes 48 trees.

  • From POP COV files
  • From POP COV files full dialog
  • For Matching with Database

This sub option is not available yet. It will be necessary when user will finally need to create an export of the vegetation scene to be able to run the fire behaviour model. As the inventory file doesn’t contain vegetation object “ID” of the EUROFORESTFUELS database, the loading procedure will match each vegetation object with the most similar object present in the database.

FROM SCRATCH

An empty scene can be generated by giving the dimensions of the terrain.

FROM A SAVED SCENE

CAPSIS can save scene in a special format that can be re open later for further modifications.

====FROM SVS MODEL====

Not operational, see Standfire.

====FROM A DATABASE INVENTORY====

This option enables to generate a vegetation scene by loading an inventory file which contains only vegetation objects known in the EUROFORESTFUELS database. The inventory file describes each vegetation object throughout its “ID” in the EUROFORESTFUELS database, and location. This option requires a connection with the remote database since species, height and crown dimensions are read for each fuel in the database before generating the scene. The inventory file contains also a line describing the dimensions of the terrain. Using this option to generate a vegetation scene will make possible the creation of export files necessary to run the fire propagation model.

As example, an inventory file “dataBaseFile_fc.scene” is available in the given CAPSIS archive and precisely in the “capsis4_fireparadox\data\fireparadox” directory. The file describes 48 trees.

help_en/fireparadox/gui/fminitialdialog.txt · Last modified: 2015/11/19 15:55 by pimont