Class RuleSet
- All Implemented Interfaces:
Prototype,Setup,Serializable,Cloneable
Besides the Rules themselves, the only thing else a RuleSet contains is a pointer to a corresponding RuleSetConstraints object, which holds all of its modification parameters. See RuleSetConstraints for a description of these parameters.
In addition to serialization for checkpointing, RuleSets may read and write themselves to streams in three ways.
- writeRuleSet(...,DataOutput)/readRuleSet(...,DataInput) This method transmits or receives a RuleSet in binary. It is the most efficient approach to sending RuleSets over networks, etc. The default versions of writeRuleSet/readRuleSet reads/writes out the number of rules, then calls read/writeRule(...) on each Rule. Override this if you need more functionality.
- printRuleSet(...,PrintWriter)/readRuleSet(...,LineNumberReader) This approach transmits or receives a RuleSet in text encoded such that the RuleSet is largely readable by humans but can be read back in 100% by ECJ as well. To do this, these methods will typically encode numbers using the ec.util.Code class. These methods are mostly used to write out populations to files for inspection, slight modification, then reading back in later on. readRuleSet reads in the number of rules, then calls readRule(...) on each new Rule. printRuleSet writes out the number of rules, then calls printrule(...) on each new Rule. Again, override this if you need more functionality.
- printRuleSetForHumans(...,PrintWriter) This approach prints a RuleSet in a fashion intended for human consumption only. printRuleSetForHumans prints out the number of rules, then calles printRuleForHumans on each Rule in turn. You may wish to override this to provide more information instead. You should handle one of these methods properly to ensure RuleSets can be printed by ECJ.
Parameters
| base.constraints string |
(name of the rule set constraints) |
Default Base
rule.ruleset
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionbyteAn index to a RuleSetConstraintsstatic final StringThe message to appear when printing the rule setintHow many rules are there used in the rules arraystatic final StringThe constraint for the rule setstatic final StringRule[]The rules in the rule set -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoidaddRandomRule(EvolutionState state, int thread) Add a random rule to the rule setvoidAdd a rule directly to the rule set.clone()Creates a new individual cloned from a prototype, and suitable to begin use in its own evolutionary context.final RuleSetConstraintsconstraints(RuleInitializer initializer) voidcopyNoClone(RuleSet other) Clears out existing rules, and loads the rules from the other ruleset without cloning them.Returns the default base for this prototype.booleaninthashCode()The hash code for the rule set.voidMakes a copy of the rules in another RuleSet and adds the rule copies.voidmutate(EvolutionState state, int thread) Mutates rules in the RuleSet independently with the given probability.intnumRules()How many rules are there used in the rules arrayvoidpostprocessRules(EvolutionState state, int thread) Should be called by pipelines to "fix up" the rulesets after they have been mutated or crossed over.voidpreprocessRules(EvolutionState state, int thread) Should be called by pipelines to "fix up" the rulesets before they have been mutated or crossed over.voidprintRuleSet(EvolutionState state, int log) Prints the rule set such that the computer can read it latervoidprintRuleSet(EvolutionState state, int log, int verbosity) Prints the rule set such that the computer can read it latervoidprintRuleSet(EvolutionState state, PrintWriter writer) Prints the rule set such that the computer can read it latervoidprintRuleSetForHumans(EvolutionState state, int log) Prints out the rule set in a readable fashion.voidprintRuleSetForHumans(EvolutionState state, int log, int verbosity) Prints out the rule set in a readable fashion.voidrandomizeRulesOrder(EvolutionState state, int thread) Randomizes the order of the rules in the rule set.voidreadRuleSet(EvolutionState state, DataInput dataInput) Reads RuleSets in from a binary streamvoidreadRuleSet(EvolutionState state, LineNumberReader reader) Reads the rule setremoveRandomRule(EvolutionState state, int thread) Removes a randomly-chosen rule from the rule set and returns it.removeRule(int index) Removes a rule from the rule set and returns it.voidreset(EvolutionState state, int thread) A reset method for randomly reinitializing the RuleSetvoidsetup(EvolutionState state, Parameter base) Sets up the object by reading it from the parameters stored in state, built off of the parameter base base.RuleSet[]Splits the rule set into n pieces, according to points, which *must* be sorted.RuleSet[]split(EvolutionState state, int thread, RuleSet[] sets) Splits the rule set into a number of disjoint rule sets, copying the rules and adding them to the sets as appropriate.RuleSet[]splitIntoTwo(EvolutionState state, int thread, RuleSet[] sets, double prob) Splits the rule set into a two disjoint rule sets, copying the rules and adding them to the sets as appropriate.voidwriteRuleSet(EvolutionState state, DataOutput dataOutput) Writes RuleSets out to a binary stream
-
Field Details
-
N_RULES
The message to appear when printing the rule set- See Also:
-
P_RULESET
- See Also:
-
P_CONSTRAINTS
The constraint for the rule set- See Also:
-
constraints
public byte constraintsAn index to a RuleSetConstraints -
rules
The rules in the rule set -
numRules
public int numRulesHow many rules are there used in the rules array
-
-
Constructor Details
-
RuleSet
public RuleSet()
-
-
Method Details
-
constraints
-
clone
Description copied from interface:PrototypeCreates a new individual cloned from a prototype, and suitable to begin use in its own evolutionary context.Typically this should be a full "deep" clone. However, you may share certain elements with other objects rather than clone hem, depending on the situation:
- If you hold objects which are shared with other instances, don't clone them.
- If you hold objects which must be unique, clone them.
- If you hold objects which were given to you as a gesture of kindness, and aren't owned by you, you probably shouldn't clone them.
- DON'T attempt to clone: Singletons, Cliques, or Populations, or Subpopulation.
- Arrays are not cloned automatically; you may need to clone an array if you're not sharing it with other instances. Arrays have the nice feature of being copyable by calling clone() on them.
Implementations.
- If no ancestor of yours implements clone(), and you have no need to do clone deeply, and you are abstract, then you should not declare clone().
- If no ancestor of yours implements clone(),
and you have no need to do clone deeply,
and you are not abstract, then you should implement
it as follows:
public Object clone() { try { return super.clone(); } catch ((CloneNotSupportedException e) { throw new InternalError(); } // never happens } - If no ancestor of yours implements clone(), but you
need to deep-clone some things, then you should implement it
as follows:
public Object clone() { try { MyObject myobj = (MyObject) (super.clone()); // put your deep-cloning code here... } catch ((CloneNotSupportedException e) { throw new InternalError(); } // never happens return myobj; } - If an ancestor has implemented clone(), and you also need
to deep clone some things, then you should implement it as follows:
public Object clone() { MyObject myobj = (MyObject) (super.clone()); // put your deep-cloning code here... return myobj; }
-
numRules
public int numRules()How many rules are there used in the rules array -
reset
A reset method for randomly reinitializing the RuleSet -
mutate
Mutates rules in the RuleSet independently with the given probability. -
preprocessRules
Should be called by pipelines to "fix up" the rulesets before they have been mutated or crossed over. Override this method to do so. -
postprocessRules
Should be called by pipelines to "fix up" the rulesets after they have been mutated or crossed over. Override this method to do so. -
randomizeRulesOrder
Randomizes the order of the rules in the rule set. It is helpful when the order of rule is important for the conflict resolution. -
addRandomRule
Add a random rule to the rule set -
addRule
Add a rule directly to the rule set. Does not copy the rule. -
removeRule
Removes a rule from the rule set and returns it. If index is out of bounds, then this method returns null. The rules are shifted down --- thus this is O(n). -
removeRandomRule
Removes a randomly-chosen rule from the rule set and returns it. If there are no rules to remove, this method returns null. -
join
Makes a copy of the rules in another RuleSet and adds the rule copies. -
copyNoClone
Clears out existing rules, and loads the rules from the other ruleset without cloning them. Mostly for use if you create temporary rulesets (see for example RuleCrossoverPipeline) -
split
Splits the rule set into n pieces, according to points, which *must* be sorted. The rules in each piece are cloned and added to the equivalent set. Sets must be already allocated. sets.length must be 1+ points.length. Comment: This function appends the split rulesets to the existing rulesets already in sets. -
split
Splits the rule set into a number of disjoint rule sets, copying the rules and adding them to the sets as appropriate. Each rule independently throws a die to determine which ruleset it will go into. Sets must be already allocated. Comment: This function appends the split rulesets to the existing rulesets already in sets. -
splitIntoTwo
Splits the rule set into a two disjoint rule sets, copying the rules and adding them to the sets as appropriate. The value prob is the probability that an element will land in the first set. Sets must be already allocated. Comment: This function appends the split rulesets to the existing rulesets already in sets. -
printRuleSetForHumans
Prints out the rule set in a readable fashion. -
printRuleSetForHumans
Prints out the rule set in a readable fashion. -
printRuleSet
Prints the rule set such that the computer can read it later -
printRuleSet
Prints the rule set such that the computer can read it later -
printRuleSet
Prints the rule set such that the computer can read it later -
readRuleSet
Reads the rule set- Throws:
IOException
-
writeRuleSet
Writes RuleSets out to a binary stream- Throws:
IOException
-
readRuleSet
Reads RuleSets in from a binary stream- Throws:
IOException
-
defaultBase
Description copied from interface:PrototypeReturns the default base for this prototype. This should generally be implemented by building off of the static base() method on the DefaultsForm object for the prototype's package. This should be callable during setup(...).- Specified by:
defaultBasein interfacePrototype
-
setup
Description copied from interface:PrototypeSets up the object by reading it from the parameters stored in state, built off of the parameter base base. If an ancestor implements this method, be sure to call super.setup(state,base); before you do anything else.For prototypes, setup(...) is typically called once for the prototype instance; cloned instances do not receive the setup(...) call. setup(...) may be called more than once; the only guarantee is that it will get called at least once on an instance or some "parent" object from which it was ultimately cloned.
-
hashCode
public int hashCode()The hash code for the rule set. This isn't a very good hash code, but it has the benefit of not being O(n lg n) -- otherwise, we'd have to do something like sort the rules in the individual first and then do an ordered hash code of some sort, ick. -
equals
-