close
Warning:
BrowserModule failed with ConfigurationError: Look in the Trac log for more information.
- Timestamp:
-
Apr 28, 2009, 2:09:14 PM (16 years ago)
- Author:
-
heep
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v22
|
v23
|
|
626 | 626 | }}} |
627 | 627 | |
628 | | Like modules, configurations can also use inheritance. A configuration that inherits from a parent configuration receives all the parameters that were set there, but can change them if needed. For example, let's make two configurations that inherit from ExampleConf: |
| 628 | Like modules, configurations can also use inheritance. A configuration that inherits from a parent configuration receives all the parameters that were set there, but can change them if needed. For example, let's make two configurations that inherit from !ExampleConf: |
629 | 629 | |
630 | 630 | {{{ |
… |
… |
|
643 | 643 | Now, we see that both configurations are equal except for their different values for dropChance and sendPeriod. What happens if we need more simulations that have different values for both parameters, but retain the rest? For that, we can use runs. |
644 | 644 | |
645 | | Let's, for example, create a configuration from ExampleConf, but where dropChance takes the values of 0.1, 0.3, 0.5, and 0.7. |
| 645 | Let's, for example, create a configuration from !ExampleConf, but where dropChance takes the values of 0.1, 0.3, 0.5, and 0.7. |
646 | 646 | |
647 | 647 | {{{ |