Ticket #76 (assigned idea)

Opened 5 years ago

Last modified 3 years ago

add map factories

Reported by: mmckerns Owned by: mmckerns
Priority: minor Milestone: pathos-0.3a
Component: pyina Keywords:


add map factories

Change History

comment:1 Changed 5 years ago by mmckerns

  • Milestone changed from pathos-0.1a2 to pathos-0.1a3

comment:2 Changed 5 years ago by mmckerns

this interface was presented in the scipy conference paper...

from pathos.launchers import ipc 
from pathos.strategies import pool
from pathos.tools import mapFactory 
my_map = mapFactory(launcher=ipc, strategy=pool) 

from pyina.launchers import mpirun 
from pyina.strategies import carddealer as card 
from pyina.tools import mapFactory 
my_map = mapFactory(4, launcher=mpirun, strategy=card)

comment:3 Changed 3 years ago by mmckerns

  • Priority changed from major to minor
  • Milestone changed from pathos-0.3a to pathos-0.2a

moving... (primarily to show needs an update)

comment:4 Changed 3 years ago by mmckerns

migrating function-based "maps" to worker and scheduler classes in r467 is a better design than using map function factories as presented in the interface above.

needs integration to trunk

comment:5 Changed 3 years ago by mmckerns

  • Status changed from new to assigned

comment:6 Changed 3 years ago by mmckerns


I *might* be able to use a "mapFactory" after all. But something more like this:

from pyina.launchers import Mpi
from pyina.schedulers import Torque
from pyina.tools import mapFactory

my_worker_pool = mapFactory(4, launcher=Mpi, scheduler=Torque)

where the factory can build new launchers... (here duplicating pyina.launchers.TorqueMpi? with a default of 4 nodes).

comment:7 Changed 3 years ago by mmckerns

  • Type changed from task to idea
  • Component changed from pathos to pyina
  • Milestone changed from pathos-0.2a to pathos-0.3a

going to put this one back into the idea box... a little later in the pipe

Note: See TracTickets for help on using tickets.