| 1 | # Copyright 2006 by Sean Luke and George Mason University |
|---|
| 2 | # Licensed under the Academic Free License version 3.0 |
|---|
| 3 | # See the file "LICENSE" for more information |
|---|
| 4 | |
|---|
| 5 | # Note that the slave shares this file with the master, because they |
|---|
| 6 | # have a number of parameters held in common. See slave.params. |
|---|
| 7 | # You don't have to do this, but it's a convenient way to keep the |
|---|
| 8 | # master and slave consistent with one another. |
|---|
| 9 | |
|---|
| 10 | |
|---|
| 11 | |
|---|
| 12 | |
|---|
| 13 | # When eval.masterproblem is turned on, the system assumes |
|---|
| 14 | # use of the master/slave evaluator. |
|---|
| 15 | eval.masterproblem = ec.eval.MasterProblem |
|---|
| 16 | |
|---|
| 17 | |
|---|
| 18 | # Turning this on will provide synchronization |
|---|
| 19 | # information for debugging the master/slave evaluator |
|---|
| 20 | eval.masterproblem.debug-info = false |
|---|
| 21 | |
|---|
| 22 | |
|---|
| 23 | # How large should each slave's job queue be? ECJ will |
|---|
| 24 | # keep slaves' TCP/IP streams filled with jobs even if the |
|---|
| 25 | # slaves haven't processed them yet, which has a significant |
|---|
| 26 | # effect on network performance. Increasing this number is |
|---|
| 27 | # likely to be more efficient. Note that once a job is |
|---|
| 28 | # committed to a slave, a brand new slave coming on-line cannot |
|---|
| 29 | # take it -- it'll have to sit and wait, which isn't particularly |
|---|
| 30 | # efficient. At the very least, it's probably helpful to have 2 |
|---|
| 31 | # or 3 jobs in the queue. |
|---|
| 32 | eval.masterproblem.max-jobs-per-slave = 3 |
|---|
| 33 | |
|---|
| 34 | |
|---|
| 35 | # How large should our job be? If you're doing ordinary |
|---|
| 36 | # non-coevolutionary evolution, you can specify how many individuals |
|---|
| 37 | # should be placed into a job (maximum) and sent to the slave |
|---|
| 38 | # to be evaluated at one time, using the below parameter. |
|---|
| 39 | # If your individuals are small in size, this can significantly |
|---|
| 40 | # improve the network bandwidth. If the individuals are large |
|---|
| 41 | # in size, it'll have no real effect. Furthermore, if your |
|---|
| 42 | # slave is running in 'evolve' mode, this parameter will determine |
|---|
| 43 | # the maximum (and typical) size of the "population" the slave is |
|---|
| 44 | # evolving. This works for both steady-state and generational evolution, |
|---|
| 45 | # but if you're doing coevolution, the job size is ignored -- instead |
|---|
| 46 | # the job will consist of the individuals to be coevolved together. |
|---|
| 47 | eval.masterproblem.job-size = 100 |
|---|
| 48 | |
|---|
| 49 | |
|---|
| 50 | # This compresses the streams between the master and slaves. |
|---|
| 51 | # Compression requires the zlib library. |
|---|
| 52 | # See the ECJ main webpage or http://www.jcraft.com/jzlib/ |
|---|
| 53 | |
|---|
| 54 | eval.compression=true |
|---|
| 55 | |
|---|
| 56 | |
|---|
| 57 | # This defines the socket port that the master listens in |
|---|
| 58 | # for incomoing Slaves to connect. |
|---|
| 59 | eval.master.port = 15000 |
|---|
| 60 | |
|---|
| 61 | |
|---|
| 62 | # You do NOT want to set eval.i-am-slave=true in this file, |
|---|
| 63 | # because then the master will think it's a slave. Instead, set |
|---|
| 64 | # that parameter in the slave.params file. |
|---|
| 65 | |
|---|
