User Tools

Site Tools


howtos:toolcoding:feedback_views

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
howtos:toolcoding:feedback_views [2011/02/07 17:47]
marcus.williams
howtos:toolcoding:feedback_views [2017/04/14 16:32] (current)
marcus.williams
Line 1: Line 1:
 ====== Feedback views ====== ====== Feedback views ======
  
-==== Declaring ​in views.samm ====+Feed back views are a way to run part of the model in a loop adjusting model inputs for each iteration and providing back to the view of the model outputs required. ​ The reasons for using feedback ​views include handling model feedback links, and trying to get model outputs to track on some know data.  There are many other ways of using feed back too.
  
-Declare ​the feedback ​view in views.samm:+There are a few built in tool variables that are available to the view writer to track the feedback process and terminate the loop when ready they are: 
 +  * **$fbViewIteration** - the iteration number of the loop 
 +  * **$fbViewMaxIters** - the maximum number of iterations requested by the user 
 +  * **$fbViewTolerance** - the convergence tolerance requested by the user 
 + 
 +Note: 
 +  * You can declare regular **local** variables ​in a feedback view, however be aware that local variables are wiped out at the start of each iterationIf you want to reuse you local variables for each iteration you need to declare it as **keep** variable, which remain available to the view for every iteration. ​ Usually you create keep variables on the first iteration inside an "if clause"​ as seen below: 
 +<​code>​ 
 +keep A[] 
 + 
 +if ($fbViewIteration) 
 +  A[] = create(...) 
 +endif 
 +</​code>​
  
-fbview trackEU compare trackEU.v trackEU.t ​ "​Tracking Energy Use“ 20 0.001 
  
-where the line contains the following parameters: 
  
-type of view (= fbview)\\ 
-view name\\ 
-model scope\\ 
-.v file name\\ 
-.t file name\\ 
-description\\ 
-default number of iterations \\ 
-convergence tolerance \\ 
  
-==== Template/​Examples ​====+==== Example feedback view files ====
  
-Here is an example of the .v and .t files for a simple feedback view that modifies a model input until the model output matches some given "​golden"​ value in the last time slice.+Here is the code for the .v and .t files for a simple feedback view that modifies a model input until the model output matches some given "​golden"​ value in the last time slice.
  
 viewName.v: viewName.v:
Line 83: Line 86:
  
  if ($numNotConv == 0) or ($fbViewIteration == $fbViewMaxIters)  if ($numNotConv == 0) or ($fbViewIteration == $fbViewMaxIters)
- if ( 
  mumble (" ​  ​numNotConv = ", $numNotConv,​ " at iteration ",​$fbViewIteration,​ " stopping due to ")  mumble (" ​  ​numNotConv = ", $numNotConv,​ " at iteration ",​$fbViewIteration,​ " stopping due to ")
  if ($numNotConv == 0)  if ($numNotConv == 0)
Line 97: Line 99:
 endif endif
 </​file>​ </​file>​
 +
 +==== Use of quit () ====
 +
 +''​quit (1)''​ exits the current iteration.
 +
 +''​quit (0)''​ exits the entire feedback view.
 +
 +==== Declaring in views.samm ====
 +
 +Declare the feedback view in views.samm:
 +
 +<​file>​
 +fbview trackEU compare trackEU.v trackEU.t ​ "​Tracking Energy Use“ 20 0.001
 +</​file>​
 +
 +where the line contains the following parameters:
 +
 +type of view (= fbview)\\
 +view name\\
 +model scope\\
 +.v file name\\
 +.t file name\\
 +description\\
 +default number of iterations \\
 +convergence tolerance \\
 +
 +==== Object Array Size and Contents ====
 +
 +Note that feedback views require a background scenario to run (i.e. $background must be true).
 +
 +Also, the "​current"​ instance identified in the table below refers to the instance of a use-type (U) object in a //fbview// which - in the first iterations contains the value for the background (or worksheet) scenario - and in subsequent scenarios contains the value corresponding to the most recent iteration. If the background value of such a variable is required in iterations greater than 1, the value should be persisted using a keep object during the first iteration.
 +
 +^ $history ^ Object Type ^ Object Array Contents ^ Value of $numScns ^
 +| true | U | object[][1] = history instance \\ object[][2] = current instance | 2 |
 +| true | F | object[][1] = history instance \\ object[][2] = background instance \\ object[][3] = new instance to be filled | 3 |
 +| false | U | object[][1] = current instance | 3 |
 +| false | F | object[][1] = background instance \\ object[][2] = new instance to be filled | 3 |
 +
  
  
  
  
howtos/toolcoding/feedback_views.1297100871.txt.gz · Last modified: 2011/02/07 17:47 by marcus.williams