Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
tutorial:using_subregions_in_a_simulation_model [2013/08/14 19:42]
admin
tutorial:using_subregions_in_a_simulation_model [2015/10/12 00:59]
admin ↷ Links adapted because of a move operation
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]]