pdf: 600KB - Potsdam Institute for Climate Impact Research
pdf: 600KB - Potsdam Institute for Climate Impact Research
pdf: 600KB - Potsdam Institute for Climate Impact Research
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
78<br />
integrated simulations. ... MODCOM provides a series of pre-built components implementing<br />
these interfaces that manage many aspects of simulations – high-level simulation services,<br />
numerical integration of differential equations, data management, data analysis, and visual<br />
representation of simulation components and outputs. MODCOM is language neutral, and is built<br />
on top of Microsoft’s COM specification; any language that supports COM can take advantage of<br />
MODCOM’s modeling services. ... The central concept of MODCOM is that a simulation model<br />
is best constructed as a collection of simulation objects (SimObjs) that are organized and<br />
managed by a simulation environment (SimEnv) that provide a range of high-level services<br />
common to most simulations. MODCOM provides a general-purpose simulation framework by<br />
which this can occur. By creating models as well-defined components, the opportunities <strong>for</strong><br />
reusing the components in other simulations are greatly increased. Similarly, by handling general<br />
simulation services in a generic manner, the modeller is relieved of having to provide these<br />
services in each simulation; he/she simply takes advantage of the services offered by the<br />
framework, and can concentrate instead on defining the details of the component of interest."<br />
There are several things to note about MODCOM. The first is that it is a rare example of the<br />
development of a modelling framework by groups from different institutions collaborating<br />
together on an equal footing, and with the primary purpose of developing the framework. Other<br />
initiatives are usually led by one particular group, operating within the context of a specific<br />
modelling project. The second is that the emphasis given to the component (module): the aim is<br />
to enable multiple components to be glued together to make a model, rather than to support the<br />
development of the components themselves. Third, MODCOM is based on a programming<br />
approach: in its current <strong>for</strong>m, you need to be a programmer to make a module, and you need to be<br />
a programmer to make a model out of several components. There is an intention to develop<br />
visual modelling environments <strong>for</strong> both tasks, but that is in the future.<br />
A1.3 IMA: Integrating Modelling Architecture<br />
The IMA is a very ambitious project aimed at developing a generic framework capable of<br />
bringing together a wide variety of modelling paradigms in a single model (Villa, 2001). The<br />
paradigms include not only conventional simulation models based on differential/difference<br />
equations, but also agent-based models, cellular automata, optimisations models, statistical<br />
models, and so on. It is motivated by the recognition that a given problem - say, one involving<br />
land use planning with complex environmental and sociological aspects, requires a variety of<br />
approaches <strong>for</strong> its solution.<br />
IMA is heavily predicated on a declarative modelling approach. The primary role <strong>for</strong> this is to<br />
define the characteristics of the interface that individual modules present to the rest of the system.<br />
In order to allow modules to talk to each other, to the model manager, and to tools <strong>for</strong> input,<br />
output and analysis, they have metadata attached to them defining their characteristics with<br />
respect to time, space and behaviour. The time aspect relates to the when a module is called<br />
during the simulation time cycle. Space relates to attributes such as grid/polygon/point<br />
representation, spatial granularity and spatial extent. Behaviour defines the type of modelling<br />
paradigm <strong>for</strong> that module: System Dynamics, event-based, or whatever. These characteristics are<br />
defined in XML, and are independent of the actual implementation of the module, which can<br />
either be programmed or represented declaratively.<br />
The IMA vision is a sweeping one. It does share quite a lot in common with standard<br />
component-based approaches (modules, a simulation object hierarchy, as simulation controller,<br />
etc), though is distinguished by its total commitment to a declarative, ontologically-rich language<br />
<strong>for</strong> characterising modules in general, and XML in particular. At the time of writing, IMT (the<br />
Integrating Modelling Toolkit - the implemented prototype of IMA) is still under development,<br />
and it remains to be seen how realisable the vision is in practice.