User Tools

Site Tools


concepts:how_it_s_organized

This is an old revision of the document!


Modelbases, Model Families & 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 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
  • 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.

A example hierarchy is shown below:

  • 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)
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.1254920079.txt.gz · Last modified: 2009/10/07 12:54 by marcus.williams