fema-team team mailing list archive

[James Newell <jameslnewell@xxxxxxxxx>]

> Would a job be considered finished if the generation or time limit is reached?

I don't think time limit would be a very good condition in our case because if we don't have many volunteers the time limit will quickly lapse.

A maximum number of generations would be OK for an absolute upper bound but will stop jobs regardless of whether a job is stuck or still progressing.

A maximum number of generations without improvement (a new best solution) is a better condition (but not sure if it can be applied in MOO).

Will everyone's termination conditions be the same and can be part of the framework as common code or is this algorithm or problem specific?

> Also, if there is an option for some of the problems to also submit an optimal solution file, that could be used as a reference for when the job needs to end.

The (partial) "islands" aka Client are going to send back all the evolved individuals (chromosome and fitness or objective values) from which the Server (assimilator) can check for a new best solution.


On 30/08/2011, at 11:18 PM, John Dunnet wrote:

> Would a job be considered finished if the generation or time limit is reached? Also, if there is an option for some of the problems to also submit an optimal solution file, that could be used as a reference for when the job needs to end.
> -John
> 
> On 30 August 2011 23:15, James Newell <jameslnewell@xxxxxxxxx> wrote:
> Just stepping through my use case… To know which jobs are running, the server will have to notify the UI when jobs are "finished" i.e. update a flag in the UI Jobs database.
> 
> By the way how will the server know when a job is "finished"?
> --
> Mailing list: https://launchpad.net/~fema-team
> Post to     : fema-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fema-team
> More help   : https://help.launchpad.net/ListHelp
>