-
Notifications
You must be signed in to change notification settings - Fork 99
UsingGamaFlags
GAMA and some of its components (software libraries) make it possible to change some of the software behaviors by setting up "flags". Those are mainly for advanced users and should not be much of a concern for most users.
GAMA flags are flags that are build directly by GAMA developers, they have to be set in the Gama.ini
file as a new line item (or as a VM argument) like this -D<FLAGNAME>=true/false
. For example :
-Denable_logging=false
-
enable_debug
: Set totrue
by default, itenable
logging the debug messages (DEBUG.OUT(...), DEBUG.ERR(...) which will follow the declaration of DEBUG.ON() on the classes). Set to false to suppress all debug logging (but regular logging using DEBUG.LOG(...) or DEBUG.TIMER(...) will still operate). -
enable_logging
: Set totrue
by default, it enables simple logging activities using DEBUG.LOG(...), DEBUG.TIMER(...). Set tofalse
to prevent all logging activities (incl. debug ones) -
use_global_preference_store
: set totrue
by default, it saves the preferences in the global (managed by the JRE) preference store. Set tofalse
to save them in each GAMA instance preference store. -
read_only
: set tofalse
by default, set totrue
if you want the files in the gaml editor to be read-only (impossible to modify them)
GAMA 1.9.2 uses Eclipse 2022-12 as the based component for the IDE.
More precisely, GAMA uses the Eclipse Runtime which provides the foundational support for plug-ins, extension points and extensions (among other facilities), it's the application structure and is built on top of the OSGi framework.
GAMA also uses the Standard Widget Toolkit (or SWT for short). SWT is designed to provide efficient, portable access to the user-interface facilities of the operating systems on which it is implemented.
Both components can be tweaked thanks to the eclipse's Rich Client Platform interface using some flags and parameters documented in the official documentation for Eclipse 2022-12.
Here are some links to more detailed explanations about both components and their respective flags:
JOGL in addition with Glugen (both from JOGAMP) are the two libraries used in GAMA for 3D Graphics, Multimedia and Processing.
Most of them are documented on the official documentation website.
- Installation and Launching
- Workspace, Projects and Models
- Editing Models
- Running Experiments
- Running Headless
- Preferences
- Troubleshooting
- Introduction
- Manipulate basic Species
- Global Species
- Defining Advanced Species
- Defining GUI Experiment
- Exploring Models
- Optimizing Model Section
- Multi-Paradigm Modeling
- Manipulate OSM Data
- Diffusion
- Using Database
- Using FIPA ACL
- Using BDI with BEN
- Using Driving Skill
- Manipulate dates
- Manipulate lights
- Using comodel
- Save and restore Simulations
- Using network
- Headless mode
- Using Headless
- Writing Unit Tests
- Ensure model's reproducibility
- Going further with extensions
- Built-in Species
- Built-in Skills
- Built-in Architecture
- Statements
- Data Type
- File Type
- Expressions
- Exhaustive list of GAMA Keywords
- Installing the GIT version
- Developing Extensions
- Introduction to GAMA Java API
- Using GAMA flags
- Creating a release of GAMA
- Documentation generation