Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
tutorial:using_subregions_in_a_simulation_model [2013/08/14 19:42] admin |
tutorial:using_subregions_in_a_simulation_model [2020/02/18 23:09] (current) argemiro |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| - | Load the model: ''simulate_deforestation_using_sub_regions.egoml'' from ''Examples\advanced\sub_regions\simulate_deforestation_using_sub_regions'' | + | Load the model: ''simulate_deforestation_using_sub_regions.egoml'' from ''\Guidebook_Dinamica_5\Models\additional_resources_lucc\sub_regions\simulate_deforestation_using_sub_regions'' |
| The Subregion set of functors are used to split a map into parts to process each subregion’s dataset separately, and then combine the results again (fig. 1). By making use of the subregion approach, you can define a sequence of operations that will be applied only to certain subregions or establish different parameters and coefficients for each subregion, modeling as a result the regional context that influences a particular phenomenon. | The Subregion set of functors are used to split a map into parts to process each subregion’s dataset separately, and then combine the results again (fig. 1). By making use of the subregion approach, you can define a sequence of operations that will be applied only to certain subregions or establish different parameters and coefficients for each subregion, modeling as a result the regional context that influences a particular phenomenon. | ||
| Line 13: | Line 13: | ||
| {{ :tutorial:advanced_4.jpg |}} | {{ :tutorial:advanced_4.jpg |}} | ||
| - | In order to this, you need to slightly modify the simulation model of lesson 7. First, a specific calibration for each subregion should be performed. In the example above, transition matrices and a set of weights of evidence coefficients were calculated for each one of the map subregions. See models for calibrating different subregions in ''Examples\advanced\sub_regions\calibration''. | + | In order to this, you need to slightly modify the simulation model of lesson 7. First, a specific calibration for each subregion should be performed. In the example above, transition matrices and a set of weights of evidence coefficients were calculated for each one of the map subregions. See models for calibrating different subregions in ''\Guidebook_Dinamica_5\Models\additional_resources_lucc\sub_regions\calibration''. |
| In the simulation model, one //[[:Load Categorical Map]]// must be added. It will be responsible for loading the map with the subregions. | In the simulation model, one //[[:Load Categorical Map]]// must be added. It will be responsible for loading the map with the subregions. | ||
| Line 40: | Line 40: | ||
| {{ :tutorial:advanced_10.jpg |}} | {{ :tutorial:advanced_10.jpg |}} | ||
| - | At the end of an iteration of //[[:For Each Category]]//, a functor //[[:Regional Categorical Map]]// stores the regional maps. Assign a **Global Map Name** to these maps. After //[[:For Each Category]]// runs, the regional maps can be merged into an updated landscape map. The functor //[[:Merge Regional Categorical Maps]]// is in charge of merging the regional maps. Its **Global Map Name** must be the same as //[[:Regional Categorical Map]]//. //[[:Merge Regional Categorical Maps]]// must be placed within //[[:Region Manager]]// and, in order to ensure a proper sequence of processing, you need to establish a dependence effect between this functor and the //[[:Regional Categorical Map]]//. A way to do this is by placing //[[:Merge Regional Categorical Maps]]// within a //[[:Group]]// and linking this //[[:Group]]// to //[[:For Each Category]]// using a functor //[[:Int]]// as a link. //[[:Int]]// simply passes an integer constant from //[[:For Each Category]]// to //[[:Group]]//, establishing as a result a time-dependence between the executions of both. | + | At the end of an iteration of //[[:For Each Category]]//, a functor //[[:Regional Categorical Map]]// stores the regional maps. Assign a **Global Map Name** to these maps. After //[[:For Each Category]]// runs, the regional maps can be merged into an updated landscape map. The functor //[[:Merge Regional Categorical Maps]]// is in charge of merging the regional maps. Its **Global Map Name** must be the same as //[[:Regional Categorical Map]]//. //[[:Merge Regional Categorical Maps]]// must be placed within //[[:Region Manager]]// and, in order to ensure a proper sequence of processing, you need to establish a dependence effect between this functor and the //[[:Regional Categorical Map]]//. A way to do this is by placing //[[:Merge Regional Categorical Maps]]// within a //[[:Group]]// and linking this //[[:Group]]// to //[[:For Each Category]]// using a functor //[[integer_value]]// as a link. //[[integer_value]]// simply passes an integer constant from //[[:For Each Category]]// to //[[:Group]]//, establishing as a result a time-dependence between the executions of both. |
| {{ :tutorial:advanced_11.jpg |}} | {{ :tutorial:advanced_11.jpg |}} | ||
| - | After the regional maps are merged, the model iterates and a new landscape map is fed back into// Mux Categorical Map// closing the loop. Therefore, the saved landscape map represents a mosaic of changed regional landscapes. | + | After the regional maps are merged, the model iterates and a new landscape map is fed back into //[[:Mux Categorical Map]]// closing the loop. Therefore, the saved landscape map represents a mosaic of changed regional landscapes. |
| [[tutorial:using_sojourn_time| Next Lesson]] | [[tutorial:using_sojourn_time| Next Lesson]] | ||