provide control of parallel and distributed jobs

[mmckerns]

provide control of parallel and distributed jobs

currently the handling mechanism fails

[mmckerns]

implementation of monitors, termination, and "condition" that are not as closely tied to solvers are being developed by Paul Kienzle in an  alternate branch of mystic

[mmckerns]

from ticket #70 -- "signal handler doesn't work in parallel DE solver. Regardless of whether signal handler is enabled or disabled, a Ctrl-C will kill the execution."

[mmckerns]

extending the Sow to log __call__(x, y, id=None) allows an automated way to 'id' each member of the map (for a particular iteration). Thus the call to StepMonitors? should take StepMonitor?(self.bestSolution[:], self.bestEnergy, self.id).

Solvers will have self.id = None by default... however for abstract_map_solvers (or abstract_nested_solvers ?), the self.id for a nested solver is set to the positional id within the map funciton. Hence, when an optimization is run on a particular node, the nested solver's self.id will log a unique id for all iterations of the nested solver (during the map).

This solution will impact the existing log readers as well (because "iteration" should be logged as the tuple of "iteration" and "id").

[mmckerns]

added solver.id and monitoring of solver.id in r296

need to modify "log_reader" to use solver.id

[mmckerns]

splitting "monitoring" off to ticket #125; this ticket will continue to focus on "control".