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 | ||
|
concepts:how_it_s_organized [2009/10/07 12:48] marcus.williams |
concepts:how_it_s_organized [2009/10/08 17:40] (current) deryn.crockett |
||
|---|---|---|---|
| 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//: | ||
| - | * A **Modelbase** can be thought of as a model "library" - it contains a collection of independent model families. [Any other comments on what organizational benefit/function the modelbase provides?] FIXME | + | * A **Modelbase** can be thought of as a model "library" - a collection of independent model families. |
| - | * A **Model family** contains the logic and all related scenario and historical data for a particular model. When users refer to 'the model' they are usually referring to a particular model family. [discuss ownership, permissions and any other relevant functionality of the model family level of organization] FIXME | + | * A **Model family** contains the logic and all related scenario and historical data for a particular model. When users refer to 'the model' they are usually referring to a particular model family. |
| - | * **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 FIXME. | + | * **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. |
| - | A example hierarchy is shown below: | + | 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: |
| - | + | ||
| - | + | ||
| - | <file> | + | |
| - | myModels (modelbase) | + | |
| - | North American Energy Model (model family) | + | |
| - | simulator (framework) | + | |
| - | calibrator (framework) | + | |
| - | Melbourne Land Use Model (model family) | + | |
| - | simulator (framework) | + | |
| - | calibrator (framework) | + | |
| - | Activity Based Costing Model (model family) | + | |
| - | simulator (framework) | + | |
| - | + | ||
| - | </file> | + | |
| + | * myModels (modelbase) | ||
| + | * North American Energy Model (model family) | ||
| + | * simulator (framework) | ||
| + | * calibrator (framework) | ||
| + | * Melbourne Land Use Model (model family) | ||
| + | * simulator (framework) | ||
| + | * calibrator (framework) | ||
| + | * Activity Based Costing Model (model family) | ||
| + | * simulator (framework) | ||
concepts/how_it_s_organized.1254919702.txt.gz · Last modified: 2009/10/07 12:48 by marcus.williams
Page Tools
