concepts:how_it_s_organized
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
concepts:how_it_s_organized [2009/10/07 13:36] marcus.williams |
concepts:how_it_s_organized [2009/10/07 14:54] marcus.williams |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Modelbases, Model Families & Frameworks ====== | + | ====== How it's Organized: Of Modelbases, Model Families and Frameworks ====== |
| Content in the whatIf? Modelling Platform is organized into a hierarchy of //modelbases//, //model families// and //frameworks//: | Content in the whatIf? Modelling Platform is organized into a hierarchy of //modelbases//, //model families// and //frameworks//: | ||
| Line 7: | Line 7: | ||
| * **Framework** - a model family typically contains two frameworks - one for future simulation and another for historical calibration (though a model family may have only a simulation framework). Simulator and calibrator frameworks in the same model family are strongly connected by cross-framework variable links to maintain structural integrity between the historical and simulation time periods. | * **Framework** - a model family typically contains two frameworks - one for future simulation and another for historical calibration (though a model family may have only a simulation framework). Simulator and calibrator frameworks in the same model family are strongly connected by cross-framework variable links to maintain structural integrity between the historical and simulation time periods. | ||
| - | Here is an example hierarchy: | + | Here's an example modelbase which has three model families, of which two have both simulator and calibrator frameworks and one which has only a simulator framework: |
| * My Models (modelbase) | * My Models (modelbase) | ||
concepts/how_it_s_organized.txt · Last modified: 2009/10/08 17:40 by deryn.crockett
Page Tools
