next up previous index
Next: Introduction to XML-based Project Up: Introduction to the OPUS Previous: Introduction to the OPUS   Index

Main Features

The GUI is cross-platform compatible, and has been developed using the open source Qt4 library. Note that screenshots included in this section will be taken from all three platforms, to give a sense of the look and feel of the GUI on each platform. After launching the GUI from any of these platforms, the main Opus GUI window should be displayed as in Figure 3.1 or 3.2.

The organization of the GUI is based on an expectation that the work flow for developing and using models can be effectively organized into tasks that follow an ordering of data management, model management, scenario management, and results management. The main window of the GUI reflects this work flow expectation, by implementing four tabs in the left-hand panel of the main window labeled Data Manager, Model Manager, Scenario Manager, and Results Manager. Each tab provides a container for configuring and running a variety of tasks, organized into the main functional areas involved in developing and using a simulation model.

$ \bullet$
The Data Manager organizes the processes related to moving data between the Opus environment and, doing data processing both within Opus, and also remotely in a database or GIS environment. Opus can use Python to pass data and commands to a database system like Postgres or MS SQL Server, or to a GIS system like ArcGIS or PostGIS. Tasks can be organized in the Data Manager as scripts, and run as a batch, or alternatively, they may be run interactively.
$ \bullet$
The Model Manager organizes the work of developing, configuring, and estimating the parameters of models, and of combining models into a model system.
$ \bullet$
The Scenario Manager organizes the tasks related to configuring a scenario of input assumptions, and to interact with a run management system to actually run simulations on scenarios. Tools to monitor and interact with a running simulation are provided here.
$ \bullet$
The Results Manager provides the tools to explore results once one or more scenarios have been simulated. It integrates an Indicator Framework that makes it possible to generate a variety of indicators, for diagnostic and for evaluation purposes. It also provides functionality to visualize indicators as charts, maps, and tables, and to export results to other formats for use outside of Opus.

To launch the Opus GUI, you will need to run a python script called opus.py in the /opus/src/opus_gui directory.[*] If you have used the Windows installer to install Opus, then a Windows Start menu item has been added under the Opus menu item under programs, so launching Opus is a simple as selecting the OpusGUI Opus menu item. If you did not use the installer, for example, on OS X, or Linux, then open a command window or shell, change directory to the opus_gui directory and type python opus.py. In Windows, you can also double-click on the opus.py file in the /opus/src/opus_gui directory to launch the GUI.

However it is launched, it will start from a command shell, and this window remains active while Opus is running. Do not attempt to quit this window or Opus will close also.

Figure 3.1: Opus GUI Main Window - on Ubuntu Linux
Image opus-startup

Figure 3.2: Opus GUI Main Window - on Leopard
Image opus-startup-mac


next up previous index
Next: Introduction to XML-based Project Up: Introduction to the OPUS Previous: Introduction to the OPUS   Index
info (at) urbansim.org