|
|
|
|
|
|
|
|
|
|
|
|
Unattended runs
With GeneXproServer you can create a job that starts different runs at regular
intervals producing different models and evaluating them against different
training and testing datasets. The duration of each run can be set in minutes,
hours, or generations.
|
|
|
|
|
|
|
Console and desktop applications
Use the desktop mode to test your job definitions before committing them to
long runs in your cluster using the console mode application. The two modes
complement each other and can also be used independently.
|
|
|
|
|
|
|
Open job definition and reporting
The job definition is an XML file with a simple and human readable schema that lists
how many runs you want and what are the conditions for each run. The job results
are a GeneXproTools file per run and several XML files with the run details, including
a report with the best models over the training and testing sets.
|
|
|
|
|
|
|
Multiple datasets
Training and testing datasets can be loaded from any database using SQL
or from external files. Or they can even be embedded into the job definition
file. This is a huge time saver as you can automate the generation and
refreshing of models using real time data.
|
|
|
|
|
|
|
Adjustable settings
You can change several run settings including its duration, the number of chromosomes and genes, the program size, the linking function, the fitness function, the type and number of numerical constants, the function set, the genetic operators, and so forth.
|
|
|
|
|
|
|
Drive external systems
The job definition can fire notifications before and after the job and before
and after each run. All the notifications are totally configurable and can
be used to trigger completion emails or to drive a model upload mechanism.
|
|
|
|
|
|