akrause2014 / dispel4py Goto Github PK

I am just wondering if the difference between spelling of the package name and name of the modules, might case some confusion and if it should not be unified.

https://github.com/akrause2014/dispel4py/blob/master/setup.py#L12

Hi, would you mind documenting which versions of Python are supported? Maybe in the README file, so it is obvious at first sight.

I am trying to understand how to integrate the idispel4py script into a package manager (MacPorts). However, I do not really understand its purpose. In general if it was a pythons script one probably could add it as entry point in setup.py.

So why this needs to be a shell script, or could the same task be done with python itself?

This file is currently not installed, so what should be done with this. It could be provided as example or template. But probably the ideal solution would be to create it, when it is not yet present for each user which is using the respective script for the first time.

Wrap PE execution in processes so that PE instances can be moved around and assigned to another process if necessary, or a new instance can be assigned to a process when it becomes available.
Processes should be available as a pool processing whatever PEs they've been assigned.

The input mappings of a composite map an input name to one target (PE, input_name). It should be a set of targets so that an external input can be connected to many PEs in the subworkflow (functioning as a Tee).

Align the input structure for worker_mpi with what has been implemented for simple_process. The development branch currently has an incomplete version (doesn't work for -s).

Currently dispel4py installs into test as top level in the namespace of modules. I'd say this is pretty to generic and should be (a) either moved to dispel4py.test or (b) be provides as examples only. I guess (a) is okay.

[radegast:python2.7/site-packages/test] petr% pwd
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/test
[radegast:python2.7/site-packages/test] petr% ls -la
total 88
drwxr-xr-x   23 root  wheel    782  5 Aug 18:13 .
drwxr-xr-x  448 root  wheel  15232  5 Aug 18:13 ..
-rw-r--r--    1 root  wheel    599  4 Aug 15:05 __init__.py
-rw-r--r--    1 root  wheel    191  5 Aug 18:10 __init__.pyc
drwxr-xr-x   28 root  wheel    952  5 Aug 18:13 graph_testing
-rw-r--r--    1 root  wheel   1181  4 Aug 15:05 multi_process_test.py
-rw-r--r--    1 root  wheel   1239  5 Aug 18:10 multi_process_test.pyc
-rw-r--r--    1 root  wheel   1208  4 Aug 15:05 registry_test.py
-rw-r--r--    1 root  wheel    970  5 Aug 18:10 registry_test.pyc
-rw-r--r--    1 root  wheel   1685  4 Aug 15:05 setup_tests.py
-rw-r--r--    1 root  wheel   1311  5 Aug 18:10 setup_tests.pyc
-rw-r--r--    1 root  wheel   3929  4 Aug 15:05 simple_process_test.py
-rw-r--r--    1 root  wheel   5369  5 Aug 18:10 simple_process_test.pyc
-rw-r--r--    1 root  wheel   2220  4 Aug 15:05 testing.py
-rw-r--r--    1 root  wheel   3247  5 Aug 18:10 testing.pyc
-rw-r--r--    1 root  wheel    894  4 Aug 15:05 word_count.py
-rw-r--r--    1 root  wheel    558  5 Aug 18:10 word_count.pyc
-rw-r--r--    1 root  wheel   4007  4 Aug 15:05 worker_mpi_test.py
-rw-r--r--    1 root  wheel   5878  5 Aug 18:10 worker_mpi_test.pyc
-rw-r--r--    1 root  wheel    912  4 Aug 15:05 workflow_client.py
-rw-r--r--    1 root  wheel    608  5 Aug 18:10 workflow_client.pyc
-rw-r--r--    1 root  wheel    997  4 Aug 15:05 workflow_client_group.py
-rw-r--r--    1 root  wheel    657  5 Aug 18:10 workflow_client_group.pyc

Introduce data types for PE inputs and outputs. This may be used by a graphical user interface when creating graphs, or for validation of graphs before execution. Currently a runtime error occurs if the data type that one PE produces does not match the input type that the connected PE consumes.

Fix the project documentation and add its build to Travis so that it updates automatically when an updated is pushed to github.