This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
concepts:how_it_s_organized [2009/10/08 17:32] deryn.crockett |
concepts:how_it_s_organized [2009/10/08 17:39] deryn.crockett |
||
---|---|---|---|
Line 4: | Line 4: | ||
* A **Modelbase** can be thought of as a model "library" - a collection of independent model families. | * 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). 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. | ||