Free to model software for linux

Misfit Model 3D is an OpenGL-based 3D model editor that works with triangle-based models. Misfit Model 3D supports multi-level undo, skeletal animations, simple texturing, scripting, command-line batch processing, and a plugin system for adding new model and image filters.
Complete online help is included. It is designed to be easy to use and easy to extend with plugins and scripts.
Misfit Model 3D was written and tested on Linux (2.4 and 2.6 kernels) and has been compiled and tested on most major Linux distributions.
It is not endian-safe so it is unlikely to run on non-x86 hardware platforms--this will probably not change soon unless I get requests for a version thats usable on big-endian archs.
Enhancements:
- The menus have been re-organized. There is a new command to make normals face outward. The texture coordinate window now has a rotate tool. Material support for COB has been improved. Many animation bugs have been fixed. A "File | Export" command has been added to indicate which formats have less reliable write support.

Config::Model provides a framework to help in validating the semantic content of configuration data. The project can also be used to provide a semantic check of options of a complex program like mplayer or transcode.
For most complex software, configuration upgrade is a difficult task for most people. By using Config::Model, a software can provide a smooth upgrade path for their users.
How does this work ?
Using this project, a typical configuration validation tool will be made of 3 parts :
The user interface
The validation engine which is in charge of validating all the configuration information provided by the user.
The storage facility that store the configuration information
Dont we already have some configuration validation tools ?
Youre probably thinking of tools like webmin. Yes, these tools exist and work fine, but they have their set of drawbacks.
Usually, the validation of configuration data is done with a script which performs semantic validation and often ends up being quite complex (e.g. 2500 lines for Debians xserver-xorg.config script which handles xorg.conf file).
In most cases, the configuration model is expressed in instructions (whatever programming language is used) and interspersed with a lot of processing to handle the actual configuration data.
Whats the advantage of this project ?
The Config::Model projects provide a way to get a validation engine where the configuration model is completely separated from the actual processing instruction.
The configuration model is expressed in a declarative form (i.e. a Perl data structure) which is always easier to maintain than a lot of code.
The declaration specifies:
the structure of the configuration data (which can be queried by generic user interfaces)
the properties of each element (boundaries, check, integer or string, enum like type ...)
the default values of parameters (if any)
mandatory parameters
the targeted audience (intermediate, advance, master)
on-line help (for ach parameter or value of parameter)
the level of expertise of each parameter (to hide expert parameters from newbie eyes)
So, in the end:
maintenance and evolution of the configuration content is easier
user will see a *common* interface for *all* programs using this project.
user will not see advanced parameters
upgrade of configuration data is easier and sanity check is performed
audit of configuration is possible to check what was modified by the user compated to default values
What about the user interface ?
Config::Model will also come with a Curses::UI interface that queries the users model and generate the relevant user screens.
What about data storage ?
Since the syntax of configuration files vary wildly form one program to another, most people who want to use this framework will have to provide a dedicated parser/writer.
Nevertheless, this project can also provide a writer/parser for most common format: like ini style file, or provide an interface to the Elektra or debconf projects. This point is open for discussion.
It is entirely possible for a single configuration model to use several parsers and writers so one model will ensure the consistency of several configuration files together.
Enhancements:
- The Xorg model was updated to Config::model version 0.609.
- Some bugs were fixed.

GO::Model::Term is a term or concept in an ontology.

SYNOPSIS

# From a file
use GO::Parser;
my $parser = new GO::Parser({handler=>obj}); # create parser object
$parser->parse("gene_ontology.obo"); # parse file -> objects
my $graph = $parser->handler->graph; # get L object
my $term = $graph->get_term("GO:0001303"); # fetch a term by ID
printf "Term %s %sn", $term->name, $term->acc;

# From a GO Database (requires go-db-perl)
my apph = GO::AppHandle->connect(-dbname=>$dbname);
my $term = $apph->get_term({acc=>00003677});
printf "Term:%s (%s)nDefinition:%snSynonyms:%sn",
$term->name,
$term->public_acc,
$term->definition,
join(", ", @{$term->synonym_list});

Represents an Ontology term; the same class is used for process, compartment and function
currently, a Term is not aware of its Relationships; to find out how a term is related to other terms, use the a GO::Model::Graph object, which will give you the GO::Model::Relationship objects; for example

$rels = $graph->get_parent_relationships($term->acc);

Model Builder is a graphical tool for designing, simulating, and analyzing mathematical models consisting of a system of ordinary differential equations (ODEs).
Main features:
- Equation-based model definition. No need to learn to program to define and run your models. Just type-in you differential equations
- Graphic output of simulation. You can save the graphics in the most common formats: png, svg, pdf, etc.
- Spreadsheet view of the results. From the spreadsheet you can make customized plots from your variables. You can also export your data to a .csv text file
- Latex rendering of your system of equations.
- Intuitive graphical interface.
- Uncertainty analysis module (coming soon!)

Vertex 3D Model Assembler project is a polygon-based live-end modeller.

The Vertex 3D Model Assembler is a 3D modeller geared towards making high performance models for games and other live-end requirements.

It uses the V3D format to maximize efficiency with OpenGL rendering, and can view/edit any V3D hybrid data.

PloneArticleModelEditor is a project that allows you to create dynamic models for PloneArticle.
This product allow you to create dynamic models for PloneArticle. A model is composed of blocks. There are many types of blocks :
Image
Text (from PloneArticle or not)
macro
You can use PloneArticleModelEditor in ZMI or PMI with a congilet.
PloneArticleModelEditor allows you to create dynamic models for PloneArticle Models are stored in portal_article_models tool in you Plone site.
All generated templates from models are stored in portal_skins/PloneArticleBlockModels.
Use portal_article tool, from PloneArticle, to detect it.
Enhancements:
- Initial release (0.2)
- Generate bloc models for PloneArticle product

JSBSim Flight Dynamics Model is an open source flight dynamics model (FDM) that compiles and runs under many operating systems, including Linux, Apple Macintosh, Microsoft Windows, Linux, IRIX, Cygwin (Unix on Windows), etc.
The FDM is essentially the physics/math model that defines the movement of an aircraft under the forces and moments applied to it using the various control mechanisms and from the forces of nature.
JSBSim has no native graphics. It can be run by itself as a standalone program, taking input from a script file and various aircraft configuration files; or, it can be run as an integrated part of a larger flight simulator implementation that includes a visual system.
The most notable example of the use of JSBSim is currently seen in the open source FlightGear simulator. JSBSim models the aerodynamic forces and moments by the classic coefficient buildup method.
JSBSim has seen the growth of a fairly large user base, with some of the more notable projects (of which I am aware) described on the Users page.
Main features:
- Fully configurable flight control system, aerodynamics, propulsion, landing gear arrangement, etc. through XML-based text file format.
- Rotational earth effects on the equations of motion (coriolis and centrifugal acceleration modeled).
- Configurable data output formats to screen, file, socket, or any combination of those.
Enhancements:
- This release includes new options for the standalone JSBSim executable, including improved real-time capability.
- This release also includes experimental (but tested) logic to reduce ground reactions jitter while on the ground.

Config::Model::WarpedThing is a base class for warped classes.

SYNOPSIS

use base qw/Config::Model::WarpedThing/ ;

This class must be inherited by all classes that can be warped by Config::Model::Value. This class provides a set of methods that are expected by a warp master from a warped class.

Currently this class is inherited by Config::Model::Value, Config::Model::AnyId and Config::Model::WarpedNode.

WarpThing does not provide a constructor.