Free modeling agencies software for linux

QML (Quantity Modeling Language) is a "thing"-based language for scientific and mathematical data modeling.
Each "thing" is a quantity which may be associated with either a structure or physical phenomena.
Quantities, in turn, may hold other Quantities or values (numbers or strings). Higher-level data models, which associate or define meanings to various quantities (such as velocity or position), can be built from QML quantities.
The higher-level data model (XML) schema that inherits from QML may be understood, and its instance documents may be parsed into QML documents and objects by the QMLReader.
Enhancements:
- This release adds partial Xerces2 DOM support, and works with Java 1.4 and Java 1.5 (no JAXP DocumentBuilder/Factory support currently).
- The test procedure is a little less chatty.
- Support has been added for testing either/both Crimson/Xerces DOM support.
- (Note: Crimson support only works with Java 1.4, as Java 1.5 interfaces have DOM lvl 2 and 3, which crimson doesnt support).
- This release adds compilerargs, and better build support for different configurations to build.xml.

Online Recruitment Agency project is Web-based recruitment agency software.
You can manage all of your recruitment efforts on your Web site, and set up job locations, categories, departments, and job titles from the Web interface as an admin user.
Regular users can then add/edit/delete jobs. The public interface can be very easily customized to your site design using templates.
On the public page, potential employees can search the job listings or view by category or department.
Enhancements:
- Bugs in the common and database library files were fixed.

Config::Model::ValueComputer is a Perl module that provides configuration value computation.

SYNOPSIS

my $model = Config::Model->new() ;

$model ->create_config_class
(
name => "Master",
element
=> [
[qw/av bv/] => {type => leaf,
value_type => integer,
},
compute_int
=> { type => leaf,
value_type => integer,
compute => [ $a + $b, a => - av, b => - bv ],
min => -4,
max => 4,
},
[qw/sav sbv/] => {type => leaf,
value_type => string,
},
compute_string =>
=> { type => leaf,
value_type => string,
compute => [ meet $a and $b, a => - sav, b => - sbv ],
},
]
) ;

Molecular Workbench project is a piece of free, open-source modeling software specifically designed for use in education. Powered by a set of real-time molecular simulation engines that compute and visualize the motion of particles interacting through force fields, in both 2D and 3D, it provides a simulation platform for teaching and learning science.
Many abstract concepts in physics, chemistry and biology can be dynamically visualized, and virtual experiments based on molecular simulations can be designed, limited only to your imagination.
The MW software consists of:
- a set of model builders, simulators and their associated scripting environments.
- a word processor for creating hypertext.
- an authoring system for constructing your own graphical user interfaces for your own simulations.
- an embedded-assessment system that allows you to design your own questions and collects student data.
- a special browser for you to deliver and for the users to access stuff created using the above sub-systems.
- Web services for collaboration among authors, students and teachers.
All these sub-systems are seamlessly integrated behind an easy-to-use graphical user interface. The customizability of models through the authoring system allows you to design user interfaces appropriate to your audience, without having to get them involved in the complexity of the modeling engines.

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.

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.

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);

CoreLinux++ Function Load Library (libclfll++) takes advantage of the abstract Library Load framework in the CoreLinux libclfw++ library by providing management of loading Linux shared libraries.
Application developers define function objects as wrappers and can then dynamically load the functions. It is very useful for implementing a framework for plug-ins.
Main features:
- Enlist members ( for requirements, analysis, design, and development )
- Formalize conventions for Object Oriented Analysis (OOA) and Design (OOD).
- Formalize standards and conventions for C++ code style.
- Gather requirements. Perform OOA and OOD using UML as the modeling language.
- Implement designs and example drivers.
- Develop utilities and applications for Linux that are CoreLinux++ certified
- Showcase CoreLinux++ certified applications by others