Message Passing Interface: Difference between revisions

Revision as of 02:42, 6 October 2006

Revision as of 02:51, 6 October 2006

Line 5:

===[[Python (programming language)|Python]]===

There are at least three known attempts to implement MPI for Python: [http://datamining.anu.edu.au/~ole/pypar/ PyPar], [http://pympi.sourceforge.net/ PyMPI], [http://peloton.sdsc.edu/~tkaiser/mympi/ MYMPI], and [http://starship.python.net/~hinsen/ScientificPython/ The MPI submodule of ScientificPython]. PyParPyMPI (andis possiblynotable ScientificPython'sbecause module as well?)it is designed to work like ''a typicalvariant modulepython usedinterpreter'' withmaking nothingthe butmulti-node anapplication importthe statementinterpreter (anditself, coversrather athan subsetthe ofcode the spec)interpreter runs. while PyMPI is ''a variant python interpreter'' which implements moremost of the MPI spec and automagically works with compiled code that needs to make MPI calls. [https://geodoc PyPar, MYMPI, and ScientificPython's module all are designed to work like a typical module used with nothing but an import statement.uchicago.edu/climatewiki/DiscussPythonMPI Source] They make it the coder's job to decide when and where they call to MPI_Init belongs.

===[[OCaml]]===