20,741
edits
FlightGear wiki talk:Instant-Refs: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear wiki talk:Instant-Refs (view source)
Revision as of 17:02, 17 December 2016
, 17 December 2016→Genetic Expression solver
m (Hooray moved page FlightGear wiki talk:Instant-Cquotes to FlightGear wiki talk:Instant-Refs: its mainly about creating refs these days ...) |
|||
| Line 254: | Line 254: | ||
Some of the metrics that can be used by the fitness function to determine if an expression is "fit", are: | Some of the metrics that can be used by the fitness function to determine if an expression is "fit", are: | ||
* valid expression | * valid expression (i.e. not throwing an exception) | ||
* relative offset/excess bytes in matches string | * relative offset/excess bytes in matches string (matching percentage of string found) | ||
* number of examples it can successfully extract | * number of examples it can partially/successfully extract | ||
* length of the expression | * length of the expression | ||
* runtime of the expression | * runtime of the expression (favoring less complex expressions) | ||
The search space, and runtime, can be significantly reduced by looking at similarities between all examples and coming up with a subset string that contains all identical components (e.g. the <code>From:</code> part in the author regex) and use that for seeding the initial generations. | The search space, and runtime, can be significantly reduced by looking at similarities between all examples and coming up with a subset string that contains all identical components (e.g. the <code>From:</code> part in the author regex) and use that for seeding the initial generations. | ||