Free world simulation software for linux

World Domination is a Real Time Strategy game inspired by the board game Axis and Allies utilizing the Stratagus engine.
World Domination will emphasize strategy and not "see who can build the most units the fastest." Resources are not gathered like in other RTSs, rather they are distributed after a fixed interval of time based on how much land a player occupies.
Enhancements:
- Added support for AI.
- Fixed may bugs and desyncs so you should be able to finish a network game without it crashing.
- New Graphics.
- Some new Maps

The Noble Ape Simulation has been developed (as the Nervana Simulation) since 1996 and is a biological simulation software. The aim of the simulation is to create a detailed biological environment and a cognitive simulation.
The Simulation is intended as a palette for open source cross-platform development. It provides a stable means of simulating large-scale environments and cognitive processes on Windows, Mac and Linux.
The Simulation includes a detailed scripting language for user-implemented movement and cognitive-process development.
Enhancements:
- This release fixes a bug in displaying only the seen Noble Apes, and has code simplification towards OpenGL implementation.

GENESIS (short for GEneral NEural SImulation System) is a general purpose simulation platform that was developed to support the simulation of neural systems ranging from subcellular components and biochemical reactions to complex models of single neurons, simulations of large networks, and systems-level models.

GENESIS has provided the basis for laboratory courses in neural simulation at Caltech, the Marine Biological Laboratory, the Crete, Trieste, Bangalore, and Obidos short courses in Computational Neuroscience, and at least 49 universities of which we are aware.

Most current GENESIS applications involve realistic simulations of biological neural systems. Although the software can also model more abstract networks, other simulators are more suitable for backpropagation and similar connectionist modeling.

Installation

1. Pick the place where you want to install the "genesis" directory tree. If you are making a system-wide installation as "root" user, /usr/local is a good choice. For a personal installation, without root privileges, you can use your home directory ("~"). Change to this directory and extract the genesis directory from the archive file genesis2.2.1-linux-bin.tar.gz. For example,

cd /usr/local
tar xvzf /mnt/cdrom/genesis2.2.1-linux-bin.tar.gz

or from wherever you have it (e.g.~/downloads/genesis2.2.1-linux-bin.tar.gz).

2. Change to the "genesis" directory and run the setup script that creates the ".simrc" GENESIS initialization file". Then copy .simrc to your home directory.

cd genesis
./binsetup
cp .simrc ~

3. Finallly, add the genesis directory to your search path, so that "genesis" can be found from any directory that you are in. If your login shell is bash, you can do this by editing the .bashrc file in your home directory to add the line

PATH=$PATH:/usr/local/genesis

at the end of the file. If you are using tcsh or csh as your command shell, add

set path=($path /usr/local/genesis)

to your .tcsh or .csh file.

At this point, you are ready to try running GENESIS. Change into the directory genesis/Scripts and try some of the tutorials suggested in the README file.

Simulation::Sensitivity is a general-purpose sensitivity analysis tool for user-supplied calculations and parameters.

SYNOPSIS

use Simulation::Sensitivity;
$sim = Simulation::Sensitiviy->new(
calculation => sub { my $p = shift; return $p->{alpha} + $p->{beta} }
parameters => { alpha => 1.1, beta => 0.2 },
delta => 0.1 );
$result = $sim->run;
print $sim->text_report($result);

Simulation::Sensitivity is a general-purpose sensitivity analysis tool. Given a user-written calculating function, a "base-case" of parameters, and a requested input sensitivity delta, this module will carry out a sensitivity analysis, capturing the output of the calculating function while varying each parameter positively and negatively by the specified delta. The module also produces a simple text report showing the percentage impact of each parameter upon the output.

The user-written calculating function must follow a standard form, but may make any type of computations so long as the form is satisfied. It must take a single argument -- a hash reference of parameters for use in the calculation. It must return a single, numerical result.

CONSTRUCTORS

new

my $sim = Simulation::Sensitivity->new(
calculation => sub { my $p = shift; return $p->{alpha} + $p->{beta} }
parameters => { alpha => 1.1, beta => 0.2 },
delta => 0.1 );

new takes as its argument a hash with three required parameters. calculation must be a reference to a subroutine and is used for calculation. It must adhere to the usage guidelines above for such functions. parameters must be a reference to a hash that represents the initial starting parameters for the calculation. delta is a percentage that each parameter will be pertubed by during the analysis. Percentages should be expressed as a decimal (0.1 to indicate 10%).

As a constructor, new returns a Simulation::Sensitivity object.

Multi-Simulator Interface, in shrot MSI, is a simulation interconnection engine. In other words it is a program that connects simulations together by synchronizing their clocks and data. Multi-Simulation Interface serves the same purpose as HLA and supports most of HLAs functionality (and more).
The MSI is an HLA alternative. The major motivating factors in the design of the MSI are speed, interoperability, and ease of use.
The MSI was written as a cutting edge distributed simulation component to connect multiple instances of ATLs premiere simulation software, CSIM, and it can be used to interface any compatible simulations.
How does the MSI compare to HLA?
The MSI was originally created to be just a light weight HLA RTI. However, as it was written, limitations in HLA were discovered. The MSI is an improvement on both the design and implementation of HLA. Some highlights include:
A 1,536 to 1 reduction in size over the publicly available (until late 2002) HLA RTI.
At least one order of magnitude of bandwidth consumption less than the publicly available (until late 2002) HLA RTI.
The ability to subscribe to an object name in addition to a type.
Time synchronization that allows for proper causality when used with discrete event simulators.
Support for systems-of-systems (SoS) and hierarchically organized simulations.
Availability for many platforms.
MSI Concept - A Synchronized Data Broker
The concept behind MSI is the synchronized data broker. There are many connected software systems that posses state data that changes over the life of that system. In the case where these systems need to exchange this changing data with other systems and the other systems will exhibit the effects of this data on their own state, the synchronization of this data may need to be managed.
Historically the management of this data has been as simple as tagging it with the time of its release. If there is any conflict in the data the most recent version of the data is used. If the data is late an extrapolation can potentially be used. In SQL relational databases transactions and locking are used to ensure data integrity. Most data brokering services offer little or no sychronization, only delivery.
MSI Setup and Use
The MSI uses a XML stream through a direct socket connection for communications. This enables the MSI to be used from any programming language that can use sockets (C, C++, Java, Ada, Lisp, Perl, etc.). Also, the MSI was written with cross-platform libraries that make it portable to all the major OS platforms (Linux, Solaris, Mac OS X, Microsoft Windows, IRIX, HPUX, etc.).
The MSI is a single executable file and is distributed with example code for the simulator/federate side interface.
MSI Time Synchronization
The MSI time synchronizer can mix unconstrained with time constrained simulations. Each constrained simulation reports the time of the next event that will occur in that simulation/federate. This time may be artificially inflated to cause loose synchronization (less overhead but less guarantee of accuracy). The simulations/federates will advance to the announced time.
MSI Data Synchronization
The MSI implements a publish/subscribe data broker. The MSI is presently not validating, therefore it does not require a separate data format specification (like the HLA FOM). When data format validation is implemented, it will be an optional feature and not written in Lisp. This greatly reduces MSIs setup time. Also, not being locked to a predetermined data format allows for dynamic data types.
There are five commands associated with the MSI data broker: publish, subscribe, update, unsubscribe, destroy (destroy is not implemented yet). Simulations/federates may subscribe to object names in addition to object types. This allows simulations to subscribe to specific objects of a type without needing to receive updates of all objects of that type. The update command is both an incoming and outgoing command. When a simulation/federate receives an update command, it is expected to reflect the new values of that object.
The MSI has a very flexible publish and subscribe system. A federate may subscribe to an object type or an object name. In addition a federate may specify particular attributes of an object or object type. For example, if an object has attributes name, x, y, and z, a federate that only considers two dimensions may choose to subscribe only to name, x, and y.
The MSI also supports systems of systems and object hierarchy in simulations. A publishing federate may designate a parent object. Subscribers may then subscribe to the objects children.
MSI Messaging
The MSI allows simulations/federates to send messages (interactions in HLA) to each other. These messages can contain multiple attributes and be multicast to a specific group of simulations.
Recently Added Features
Removed external library dependencies to improve the portability and fragility of the MSI.
Added a better client library.
Improved documentation.
Enhancements:
- An XML parsing bug in the utilities library was fixed.
- The socket library was enhanced with more protocols, Win32 tricks, and the ability to key off of addresses as well as names.
- The --wait-for command line argument was added.
- Several internal bugs were fixed.
- More of the client library and the CSIM interface were flushed out.
- All standard functionality was tested.

breve is a free, open-source software package which makes it easy to build 3D simulations of decentralized systems and artificial life.
Users define the behaviors of agents in a 3D world and observe how they interact. breve includes physical simulation and collision detection so you can simulate realistic creatures, and an OpenGL display engine so you can visualize your simulated worlds.
breve simulations are written in an easy to use language called steve. The language is object-oriented and borrows many features from languages such as C, Perl and Objective C, but even users without previous programming experience will find it easy to jump in. More information on the steve language can be found in the documentation section.
breve features an extensible plugin architecture which allows you to write your own plugins and interact with your own code. Writing plugins is simple and allows you to expand breve to work with existing projects. Plugins have been written in breve to generate MIDI music, download web pages, interact with a Lisp environment and interact with the "push" language.
Enhancements:
- An experimental Python language bridge is now available.
- There were also fixes related to Push language support and fixes for broken demos.

Vamos Automotive Simulator project, as the name suggest is an automotive simulation framework with an emphasis on thorough physical modeling and good C++ design. Vamos includes a real-time, first-person, 3D driving application.

Vamos is young and its goals are only partially met. I invite anyone whos interested to contribute.

Thorough physical modeling

Vamos models most major systems of a car. The drivetrain includes a simulation of the engine, clutch, transmission and a limited-slip differential. Tires and suspension are also modeled. If I missed something, let me know.

Good C++ Design

The geometry, track, car and world modules are in their own namespaces. Care has been taken to avoid cyclic dependencies. Standard Library components like strings, vectors and maps are favored over arrays. Some of the modules and classes have aged more gracefully than others. If you see a design area that needs improvement, feel free to pitch in.