Recent changes to Command line

Command line modified by Giovanni Squillero

Giovanni Squillero — Tue, 30 Jun 2015 08:35:51 -0000

--- v6
+++ v7
@@ -1,6 +1,6 @@
 # Command line options

-**Notez bien**: the behavior of `ugp3` is controlled by configuration files, not command line options. Our advice is to use command-line options only to override specific values in the configuration files.
+The behavior of `ugp3` is controlled by configuration files, not command line options. Command-line options should be used to tweak the execution, recover from an interrupted run, or temporary override specific values in the configuration files.

 ## Information

Command line modified by Jany Belluz

Jany Belluz — Thu, 27 Nov 2014 15:09:31 -0000

--- v5
+++ v6
@@ -68,3 +68,6 @@

 **--removeTempFiles**: Overrides the option with the same name for the first population. See Population's Settings.

+**--enableScanOperators**: Enable "scan" operators by default. These are stable and work well but since they perform an almost exhaustive search in the neighbourhood of a solution, they produce many children and require numerous evaluations. You can enable those if your evaluator runs fast.
+
+**--enableExperimentalOperators**: Enable experimental operators by default, that is, all the algorithms that sound great but never really worked. Could boost MicroGP's performance or erase your hard drive.

Command line modified by Giovanni Squillero

Giovanni Squillero — Sat, 11 Oct 2014 16:51:45 -0000

--- v4
+++ v5
@@ -1,6 +1,8 @@
 # Command line options

 **Notez bien**: the behavior of `ugp3` is controlled by configuration files, not command line options. Our advice is to use command-line options only to override specific values in the configuration files.
+
+## Information

 These options make µGP display different information and then exit.

Command line modified by Giovanni Squillero

Giovanni Squillero — Sat, 11 Oct 2014 16:51:18 -0000

--- v3
+++ v4
@@ -0,0 +1,68 @@
+# Command line options
+
+**Notez bien**: the behavior of `ugp3` is controlled by configuration files, not command line options. Our advice is to use command-line options only to override specific values in the configuration files.
+
+These options make µGP display different information and then exit.
+
+**--version**: Version and compilation information.
+
+**--license**: Additional details about µGP license, namely the GNU General Public License [1].
+
+**--help**: A laconic note suggesting to read this wiki.
+
+## Logging
+
+These options controls the amount of information that µGP produces during the execution.
+
+
+**--debug**: Show detailed information about every single operation performed. Yes, it means a lot of data. Indeed, this option is probably useless unless you are filling a bug report.
+
+**--verbose**: Show more information than usual. Useful when the fitness function is computationally expensive.
+
+**--info**: Show the standard amount of information. Indeed, this the default option. Also note that the nice progress bars are only used with this verbosity level.
+
+**--warning**: Only show warnings and errors.
+
+**--error**: Only show errors.
+
+**--silent**: Nothing is shown. Never. This option is deprecated and useless. Nevertheless, it has been advocated by Dr. Massimiliano Schillaci, and therefore cannot be removed.
+
+**--log FILE VERBOSITY FORMAT**: Add a log stream. Data are saved in FILE; the verbosity level can be debug, verbose, info, warning, or error; the FORMAT can be either brief or extended. See the discussion on the logging context in the main settings for details.
+
+**--statisticsPathName FIL**: Save detailed statistics about the evolution in FILE in CSV format. Useful to debug the performance of the algorithm. If FILE already exists, µGP tries not to overwrite it. See format of evolution statistics.
+
+## Exploiting a previous run
+
+These options are used to control how µGP use the results of previous runs, or recover an interrupted experiment.
+
+
+**--recoveryInput STATUS**: Load the full toolkit status from the XML file STATUS and continue. I.e., fully recover an interrupted experiments. Everything is restored, including the internal status of the random number generator.
+
+**--recoveryInputPopulations FILE**: Overrides the configuration file. Load a population from FILE and starts evolution.
+
+**--recoveryDiscardFitness**: After recovery, invalidate all fitness values. This option is useful if the fitness evaluator has been changed.
+
+**--population FILE**: Loads a population from FILE.
+
+**--merge destination source**: Merges a population inside another one. Populations are numbered starting from zero up to one less than the total number of populations, in the same order as they have been initially created. For instance, to merge population number 3 and 
+number 0, leaving **the resulting population in place 0: --merge 0 **: This option may be used more than once. A single merge will occur for every use of the switch.
+
+## Last minute tweaking
+
+
+**--randomSeed**: Overrides the option with the same name in Main Settings
+
+**--recoveryOutput**: Overrides the option with the same name in Main Settings
+
+**--evaluatorPathName**: Overrides the option with the same name for the first population. See Population's Settings.
+
+**--concurrentEvaluations**: Overrides the option with the same name for the first population. See Population's Settings.
+
+**--evaluatorInputPathName**: Overrides the option with the same name for the first population. See Population's Settings.
+
+**--evaluatorOutputPathName**: Overrides the option with the same name for the first population. See Population's Settings.
+
+**--fitnessParameters**: Overrides the option with the same name for the first population. See Population's Settings.
+
+**--removeTempFiles**: Overrides the option with the same name for the first population. See Population's Settings.
+

Command line modified by Giovanni Squillero

Giovanni Squillero — Sat, 11 Oct 2014 16:46:25 -0000

--- v2
+++ v3
@@ -1,174 +0,0 @@
-# Population's Constraints
-
-Basically, population's constraints describe the structure of an individual in the experiment you are trying to run. For example, if you are trying to find the highest point in an function with n variables, a work-in-progress individual in this problem will be a set of n real numbers; if you are trying to find an assembly program able to set apart between odd and even number, then your individual will be an assembly program.
-
-This is probably the most useful feature of µGP: thanks to the great flexibility of the constraints file, it is able to represent almost all kind of individuals, ranging from trivial to extremely complex. Note that `constraints.xml` is the default name for the file, but the effective name must be specified in the apposite option of your population's settings file (usually named population.settings.xml, but the effective name of the population file is specified in ugp3.settings.xml).
-
-Constraints strictly follow the internal structure of individuals (described here). The XML file defining constraints is composed of any number of type definitions, and one or more sections.
-
-~~~~ xml
-<constraints>
-    <typeDefinitions>
-        <item item_attributes="">
-            ... 
-        </item>
-        ...
-    </typeDefinitions> 
-
-    <prologue prologue_attributes="">
-        <expression>
-            ...
-        </expression>
-        <parameters>
-            ...
-        </parameters>
-    </prologue>
-    <epilogue epilogue_attributes="">
-        <expression>
-            ...
-        </expression>
-        <parameters>
-            ...
-        </parameters>
-    </epilogue>
-
-    <sections>
-        
-            ...
-        
-        
-            ...
-        
-        ...
-    </sections>
-</constraints>
-~~~~
-
-## The Section Element
-
-Each section contains a prologue, and epilogue and an arbitrary number of subsections. Prologue and epilogue are full fledged macros, see their definition later.
-
-~~~~ xml
-
-    <prologue prologue_attributes="">
-        <expression>
-            ...
-        </expression>
-        <parameters>
-            ...
-        </parameters>
-    </prologue>
-    <epilogue epilogue="" attributes="">
-        <expression>
-            ...
-        </expression>
-        <parameters>
-            ...
-        </parameters>
-    </epilogue>
-    <subSections>
-        <subSection subsection_attributes="">
-            ...
-        </subSection>
-        <subSection subsection_attributes="">
-            ...
-        </subSection>
-        ...
-    </subSections>
-
-~~~~ 
-
-More details can be found in the Section page, Prologue page, and Epilogue page.
-
-## The Subsection Element
-
-Each subsection contains a prologue, and epilogue and an arbitrary number of macros. Also prologue and epilogue are macros, see their definition later.
-
-~~~~ xml
-<subSection subsection_attributes="">
-    <prologue prologue_attributes="">
-        <expression>
-            ...
-        </expression>
-        <parameters>
-            ...
-        </parameters>
-    </prologue>
-    <epilogue epilogue_attributes="">
-        <expression>
-            ...
-        </expression>
-        <parameters>
-            ...
-        </parameters>
-    </epilogue>
-    <macros macros_attributes="">
-        <macro macro_attributes="">
-            ...
-        </macro>
-        <macro macro_attributes="">
-            ...
-        </macro>
-        ... 
-    <macros>
-</subSection>
-~~~~ 
-
-More details can be found in the Subsection page, Prologue page, and Epilogue page.
-
-## The Macro Element
-
-Macros are the building block of the individuals. A macro is composed of a fixed part (the expression) and a variable part (the parameters).
-
-~~~~ xml
-<macro macro_attributes="">
-    <expression>
-        ...
-    </expression>
-    <parameters>
-        <item item_attributes=""/>
-        <item item_attributes=""/>
-        ...
-    </parameters>
-</macro>
-~~~~ 
-
-More details can be found in the Macros page (the macro container) and the Macro page. Remember that also Prologue and Epilogue are macro.
-
-## Formats
-
-In each level of the hierarchy (section/subsection/macro) it is possible to change four formats. The expression is
-
-`<fooFormat>prefix<value/>postfix</fooFormat>`
-
-Value is the internal identifier for the object.
-
-**commentFormat**: Format used to add comments. Note that µGP may add notes in the form of comments inside the generated code.
-
-**identifierFormat**: How the internal identifier can be translated into a valid identifier. Remember that internal identifiers uses all letters and numbers allowed in the BASE32 encoding (ABCDEFGHIJKLMNOPQRSTUVWXYZ234567). Symbols can appear in every position, without syntactic restrictions. Many applications, like the generation of assembly language, require that identifiers start with a letter. For instance,
-
-~~~~ xml
-<identifierFormat>J_<value/></identifierFormat>
-~~~~ 
-
-may generate assembly code like
-
-~~~~ asm
-jmp J_2NS345
-~~~~ 
-
-**labelFormat**: How the identifier of a macro is dumped if that macro is the target of some reference. The identifier has already been patched according to identifierFormat. For instance,
-
-~~~~ xml
-<identifierFormat>J_<value/></identifierFormat>
-<labelFormat><value/>:</labelFormat>
-~~~~ 
-may generate assembly code like
-
-~~~~ asm
-J_2NS345: sub ax, 2  
-~~~~ 
-
-**uniqueTagFormat**:
-
-Format used for the unique tag parameter (see macro).

Command line modified by Giovanni Squillero

Giovanni Squillero — Sat, 11 Oct 2014 16:46:05 -0000

--- v1
+++ v2
@@ -3,10 +3,6 @@
 Basically, population's constraints describe the structure of an individual in the experiment you are trying to run. For example, if you are trying to find the highest point in an function with n variables, a work-in-progress individual in this problem will be a set of n real numbers; if you are trying to find an assembly program able to set apart between odd and even number, then your individual will be an assembly program.

 This is probably the most useful feature of µGP: thanks to the great flexibility of the constraints file, it is able to represent almost all kind of individuals, ranging from trivial to extremely complex. Note that `constraints.xml` is the default name for the file, but the effective name must be specified in the apposite option of your population's settings file (usually named population.settings.xml, but the effective name of the population file is specified in ugp3.settings.xml).
-
-## Hierarchical Overview
-
-You may prefer the Population's Constraints Flat Overview.

 Constraints strictly follow the internal structure of individuals (described here). The XML file defining constraints is composed of any number of type definitions, and one or more sections.

@@ -135,8 +131,9 @@
         ...
     </parameters>
 </macro>
+~~~~ 
+
 More details can be found in the Macros page (the macro container) and the Macro page. Remember that also Prologue and Epilogue are macro.
-~~~~ 

 ## Formats

Command line modified by Giovanni Squillero

Giovanni Squillero — Sat, 11 Oct 2014 16:44:54 -0000

Population's Constraints

Basically, population's constraints describe the structure of an individual in the experiment you are trying to run. For example, if you are trying to find the highest point in an function with n variables, a work-in-progress individual in this problem will be a set of n real numbers; if you are trying to find an assembly program able to set apart between odd and even number, then your individual will be an assembly program.

This is probably the most useful feature of µGP: thanks to the great flexibility of the constraints file, it is able to represent almost all kind of individuals, ranging from trivial to extremely complex. Note that constraints.xml is the default name for the file, but the effective name must be specified in the apposite option of your population's settings file (usually named population.settings.xml, but the effective name of the population file is specified in ugp3.settings.xml).

Hierarchical Overview

You may prefer the Population's Constraints Flat Overview.

Constraints strictly follow the internal structure of individuals (described here). The XML file defining constraints is composed of any number of type definitions, and one or more sections.

<constraints>
    <typeDefinitions>
        <item item_attributes>
            ... 
        </item>
        ...
    </typeDefinitions> 

    <prologue prologue_attributes>
        <expression>
            ...
        </expression>
        <parameters>
            ...
        </parameters>
    </prologue>
    <epilogue epilogue_attributes>
        <expression>
            ...
        </expression>
        <parameters>
            ...
        </parameters>
    </epilogue>

    <sections>
        <section section_attributes>
            ...
        </section>
        <section section_attributes>
            ...
        </section>
        ...
    </sections>
</constraints>

The Section Element

Each section contains a prologue, and epilogue and an arbitrary number of subsections. Prologue and epilogue are full fledged macros, see their definition later.

<section section_attributes>
    <prologue prologue_attributes>
        <expression>
            ...
        </expression>
        <parameters>
            ...
        </parameters>
    </prologue>
    <epilogue epilogue attributes >
        <expression>
            ...
        </expression>
        <parameters>
            ...
        </parameters>
    </epilogue>
    <subSections>
        <subSection subsection_attributes>
            ...
        </subSection>
        <subSection subsection_attributes>
            ...
        </subSection>
        ...
    </subSections>
</section>

More details can be found in the Section page, Prologue page, and Epilogue page.

The Subsection Element

Each subsection contains a prologue, and epilogue and an arbitrary number of macros. Also prologue and epilogue are macros, see their definition later.

<subSection subsection_attributes>
    <prologue prologue_attributes>
        <expression>
            ...
        </expression>
        <parameters>
            ...
        </parameters>
    </prologue>
    <epilogue epilogue_attributes>
        <expression>
            ...
        </expression>
        <parameters>
            ...
        </parameters>
    </epilogue>
    <macros macros_attributes>
        <macro macro_attributes>
            ...
        </macro>
        <macro macro_attributes>
            ...
        </macro>
        ... 
    <macros>
</subSection>

More details can be found in the Subsection page, Prologue page, and Epilogue page.

The Macro Element

Macros are the building block of the individuals. A macro is composed of a fixed part (the expression) and a variable part (the parameters).

<macro macro_attributes>
    <expression>
        ...
    </expression>
    <parameters>
        <item item_attributes />
        <item item_attributes />
        ...
    </parameters>
</macro>
More details can be found in the Macros page (the macro container) and the Macro page. Remember that also Prologue and Epilogue are macro.

Formats

In each level of the hierarchy (section/subsection/macro) it is possible to change four formats. The expression is

<fooFormat>prefix<value/>postfix</fooFormat>

Value is the internal identifier for the object.

commentFormat: Format used to add comments. Note that µGP may add notes in the form of comments inside the generated code.

identifierFormat: How the internal identifier can be translated into a valid identifier. Remember that internal identifiers uses all letters and numbers allowed in the BASE32 encoding (ABCDEFGHIJKLMNOPQRSTUVWXYZ234567). Symbols can appear in every position, without syntactic restrictions. Many applications, like the generation of assembly language, require that identifiers start with a letter. For instance,

<identifierFormat>J_<value/></identifierFormat>

may generate assembly code like

jmp J_2NS345

labelFormat: How the identifier of a macro is dumped if that macro is the target of some reference. The identifier has already been patched according to identifierFormat. For instance,

<identifierFormat>J_<value/></identifierFormat>
<labelFormat><value/>:</labelFormat>

may generate assembly code like

J_2NS345: sub ax, 2

uniqueTagFormat:

Format used for the unique tag parameter (see macro).