Recent changes to Instances section

--- v2 
+++ v3 
@@ -1,50 +1,50 @@
 Instances Section
 ===
-In the instances part you tell the system which basic models you need for your calculation, instanciate them and name your elements. This is also the place to set the individual parameters of an instance of a [basic model](Basic_models).
-
-~~~~
-
+In the instances part you tell the system which basic models you need for your calculation, instanciate them and name your elements. This is also the place to set the individual parameters of an instance of a [basic model](Basic models).
+
+~~~~
+
   
     
       25.0
     
   
    ... 
   ...
 
 ~~~~
-In this fragment of an instancessection (formerly initialization or init section) an instance named __v1__ of the basic model __Volume__ should be used. The system looks up in the __bibpath__ directory, if a file called __Volume.xml__ exists, that contains a valid basic model. If that is ok it loads the file and sets parameter __#mu1__ in this volume influence by the value of 25.0. Of course you can also use arbitraty formulas using [variables](Variables), [processes](Process_section) or other instances for the definition of parameters.
-To check partial results of a model each instance can be [logged](Logging_instances).
+In this fragment of an instancessection (formerly initialization or init section) an instance named __v1__ of the basic model __Volume__ should be used. The system looks up in the __bibpath__ directory, if a file called __Volume.xml__ exists, that contains a valid basic model. If that is ok it loads the file and sets parameter __#mu1__ in this volume influence by the value of 25.0. Of course you can also use arbitraty formulas using [variables](Variables), [processes](Process section) or other instances for the definition of parameters.
+To check partial results of a model each instance can be [logged](Logging instances).
 
 == Static instances ==
 As the instances of basic models are initialized in the init section they can be used afterwards in different parts of your calculation, say subformulas. In the following figure you can see two possible constellations of shared instances.
 
 [[img src=staticinstances.jpg alt=foobar width=100%]]
 
 In part b) of the figure the values of the instances of the models __scale__ are recalculated everytime you ask for them for the Monte Carlo simulation. In part a) you expect a different behaviour, where instance __scale__ just generates values once and passes equivalent data to the referencing subformulas in the processes. To model this behaviour you can use the keyword __static__, which tells the simulation system, that you want the instance __scale__ to be calculated just once.
 
-_____Attention:____ If you use static instances, they are evaluated before any processes are calculated! This means that they can only depend on variables defined in the [calculation section](Calculation_section).
+_____Attention:____ If you use static instances, they are evaluated before any processes are calculated! This means that they can only depend on variables defined in the [calculation section](Calculation section).
 
 See the following code for an example of behaviour a):
 
 ~~~~
 
   
   
   ...
 
 
   
      ... scale1...scale2
   
   
     ...
      ... scale1...scale2
   
   ...
 
 ...
 ~~~~
 This means __scale1__ will generate different values for process __step1__ and __step2__. But __scale2__ will generate its values before the evaluation of the formulas and therefore deliver the same values for both processes.
 
-It is also possible to choose a part of a basic model, an [influence of a basic model as static](Basic_models).
+It is also possible to choose a part of a basic model, an [influence of a basic model as static](Basic models).

Marco Wolf — Mon, 06 Jun 2011 18:47:14 -0000

--- v2 
+++ v3 
@@ -1,50 +1,50 @@
 Instances Section
 ===
-In the instances part you tell the system which basic models you need for your calculation, instanciate them and name your elements. This is also the place to set the individual parameters of an instance of a [basic model](Basic_models).
-
-~~~~
-
+In the instances part you tell the system which basic models you need for your calculation, instanciate them and name your elements. This is also the place to set the individual parameters of an instance of a [basic model](Basic models).
+
+~~~~
+
   
     
       25.0
     
   
    ... 
   ...
 
 ~~~~
-In this fragment of an instancessection (formerly initialization or init section) an instance named __v1__ of the basic model __Volume__ should be used. The system looks up in the __bibpath__ directory, if a file called __Volume.xml__ exists, that contains a valid basic model. If that is ok it loads the file and sets parameter __#mu1__ in this volume influence by the value of 25.0. Of course you can also use arbitraty formulas using [variables](Variables), [processes](Process_section) or other instances for the definition of parameters.
-To check partial results of a model each instance can be [logged](Logging_instances).
+In this fragment of an instancessection (formerly initialization or init section) an instance named __v1__ of the basic model __Volume__ should be used. The system looks up in the __bibpath__ directory, if a file called __Volume.xml__ exists, that contains a valid basic model. If that is ok it loads the file and sets parameter __#mu1__ in this volume influence by the value of 25.0. Of course you can also use arbitraty formulas using [variables](Variables), [processes](Process section) or other instances for the definition of parameters.
+To check partial results of a model each instance can be [logged](Logging instances).
 
 == Static instances ==
 As the instances of basic models are initialized in the init section they can be used afterwards in different parts of your calculation, say subformulas. In the following figure you can see two possible constellations of shared instances.
 
 [[img src=staticinstances.jpg alt=foobar width=100%]]
 
 In part b) of the figure the values of the instances of the models __scale__ are recalculated everytime you ask for them for the Monte Carlo simulation. In part a) you expect a different behaviour, where instance __scale__ just generates values once and passes equivalent data to the referencing subformulas in the processes. To model this behaviour you can use the keyword __static__, which tells the simulation system, that you want the instance __scale__ to be calculated just once.
 
-_____Attention:____ If you use static instances, they are evaluated before any processes are calculated! This means that they can only depend on variables defined in the [calculation section](Calculation_section).
+_____Attention:____ If you use static instances, they are evaluated before any processes are calculated! This means that they can only depend on variables defined in the [calculation section](Calculation section).
 
 See the following code for an example of behaviour a):
 
 ~~~~
 
   
   
   ...
 
 
   
      ... scale1...scale2
   
   
     ...
      ... scale1...scale2
   
   ...
 
 ...
 ~~~~
 This means __scale1__ will generate different values for process __step1__ and __step2__. But __scale2__ will generate its values before the evaluation of the formulas and therefore deliver the same values for both processes.
 
-It is also possible to choose a part of a basic model, an [influence of a basic model as static](Basic_models).
+It is also possible to choose a part of a basic model, an [influence of a basic model as static](Basic models).

Marco Wolf — Mon, 06 Jun 2011 18:46:01 -0000

Instances Section === In the instances part you tell the system which basic models you need for your calculation, instanciate them and name your elements. This is also the place to set the individual parameters of an instance of a [basic model](Basic_models). 25.0 ... ... In this fragment of an instancessection (formerly initialization or init section) an instance named v1 of the basic model Volume should be used. The system looks up in the bibpath directory, if a file called Volume.xml exists, that contains a valid basic model. If that is ok it loads the file and sets parameter #mu1 in this volume influence by the value of 25.0. Of course you can also use arbitraty formulas using [variables](Variables), [processes](Process_section) or other instances for the definition of parameters. To check partial results of a model each instance can be [logged](Logging_instances). == Static instances == As the instances of basic models are initialized in the init section they can be used afterwards in different parts of your calculation, say subformulas. In the following figure you can see two possible constellations of shared instances. [[img src=staticinstances.jpg alt=foobar width=100%]] In part b) of the figure the values of the instances of the models scale are recalculated everytime you ask for them for the Monte Carlo simulation. In part a) you expect a different behaviour, where instance scale just generates values once and passes equivalent data to the referencing subformulas in the processes. To model this behaviour you can use the keyword static, which tells the simulation system, that you want the instance scale to be calculated just once. _Attention: If you use static instances, they are evaluated before any processes are calculated! This means that they can only depend on variables defined in the [calculation section](Calculation_section). See the following code for an example of behaviour a): ... ... scale1...scale2 ... ... scale1...scale2 ... ... This means scale1 will generate different values for process step1 and step2. But scale2 will generate its values before the evaluation of the formulas and therefore deliver the same values for both processes. It is also possible to choose a part of a basic model, an [influence of a basic model as static](Basic_models).

Marco Wolf — Mon, 06 Jun 2011 18:45:11 -0000

Instances Section === In the instances part you tell the system which basic models you need for your calculation, instanciate them and name your elements. This is also the place to set the individual parameters of an instance of a [basic model](Basic_models). ~~~~ 25.0 ... ... ~~~~ In this fragment of an instancessection (formerly initialization or init section) an instance named __v1__ of the basic model __Volume__ should be used. The system looks up in the __bibpath__ directory, if a file called __Volume.xml__ exists, that contains a valid basic model. If that is ok it loads the file and sets parameter __#mu1__ in this volume influence by the value of 25.0. Of course you can also use arbitraty formulas using [variables](Variables), [processes](Process_section) or other instances for the definition of parameters. To check partial results of a model each instance can be [logged](Logging_instances). == Static instances == As the instances of basic models are initialized in the init section they can be used afterwards in different parts of your calculation, say subformulas. In the following figure you can see two possible constellations of shared instances. [[img src=staticinstances.jpg alt=foobar width=100%]] In part b) of the figure the values of the instances of the models __scale__ are recalculated everytime you ask for them for the Monte Carlo simulation. In part a) you expect a different behaviour, where instance __scale__ just generates values once and passes equivalent data to the referencing subformulas in the processes. To model this behaviour you can use the keyword __static__, which tells the simulation system, that you want the instance __scale__ to be calculated just once. _____Attention:____ If you use static instances, they are evaluated before any processes are calculated! This means that they can only depend on variables defined in the [calculation section](Calculation_section). See the following code for an example of behaviour a): ~~~~ ... ... scale1...scale2 ... ... scale1...scale2 ... ... ~~~~ This means __scale1__ will generate different values for process __step1__ and __step2__. But __scale2__ will generate its values before the evaluation of the formulas and therefore deliver the same values for both processes. It is also possible to choose a part of a basic model, an [influence of a basic model as static](Basic_models).