distributed processing for eppyy
Free software: Mozilla Public License 2.0 (MPL-2.0)
Documentation: https://zeppy.readthedocs.io.
Vision
To run eppy on multiple nodes in parallel and collect the results.
So what is a node and why would you want to do this ?
A node can be any or all of the following:
- a process (such E+ running on a single core on a multi-core computer)
so we can do multi-processing and run it on many cores on a single computer
- a computer
so we can run it on multiple computers that are on the same network
- a group of computer in a local network
So we can run multiple groups of machines that may be at different locations on different local networks
This can also be computers at different cloud locations
a single computer in the local network may act as an access node
Features
Do the distributed processing with a single function call and get all the results back.
Sample code
import zeppy import ppipes
result = ppipes.ipc_parallelpipe(runfunction,
args_list,
nworkers=None)
# runfunction is a function you will write,
# that may run idf.run(),
# gather the total energy use and return it
# args_list = {args: [idf1, idf2, idf3, ...]}
# list of files to run
# if nworkers=None:
# it will start up as many nodes as there are items in args_list
# if you don't have enough nodes avaliable, you can set nworkers=n.
# it will start up n nodes and queue up the runs evenly on the nodes
For example the above code can do the following:
runfunction will run the idf file, and return the total energy usage
result will be a list total energy usage in the same order as the items in args_list
see the comments in the code for greater clarity
Credits
This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.
Metadata
Release files for zeppy 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| zeppy-0.1.4.tar.gz | 25.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zeppy-0.1.4-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 45.4 kB
Release files / zeppy-0.1.4.tar.gz
| Download URL | zeppy-0.1.4.tar.gz |
|---|---|
| Size | 25.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e71a0389364e43e745135560ce7031173ac3215d07a35d6f6902dde3739507b
|
|
BLAKE2b-256 checksum How to use checksums |
256d0fbea990517179a4d4b3e1140b69e1703e88ce35284d38da9e3cea0942e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Release files / zeppy-0.1.4-py2.py3-none-any.whl
| Download URL | zeppy-0.1.4-py2.py3-none-any.whl |
|---|---|
| Size | 20.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
9f8af5547caa3526ea4f86f4f61549bcbb34323221c6ba629cf87ec3e050a10a
|
|
BLAKE2b-256 checksum How to use checksums |
fc8cf27bf0ae7c49b1cfbd5d76462ce8559e4dc076a874e9d18bb4676055511e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Security for zeppy 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.