Cyberinfrastructure Simulation Workbench
UNDER DEVELOPMENT
Objective
The objective of this repo is to implement a tiny "hello world" proof-of-concept of the envisioned system architecture for the WRENCH (re-?)implementation as part of the NSF-funded CSSI grant. The key ideas are:
Current Design
- A simulation consists of a "client" (in this repo a Python client) that interacts with a "WRENCH daemon" process.
- The "WRENCH daemon" process, when asked to run a simulation starts a 2-thread process:
- A "Simulation Daemon" thread that handles all communication with the client
- A simulation thread that runs the WRENCH simulation
- The reason for the two threads is that all SimGrid calls must be placed by the same thread. So the Simulation Daemon thread, which has to acts as an HTTP server, places "please do this" requests in some thread-safe data structure that the simulation thread will then execute via WRENCH calls.
- The client, simulation daemon, and the simulation thread operate in locked-step w.r.t. the simulation clock.
How to run it
-
Start the daemon:
./wrench-daemon/build/wrench-daemon(use--helpfor all options) -
Run the Python simulator:
./python-client-demo/simulator.py
Metadata
Release files for wrench-api 0.1
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 | Actions |
|---|---|---|---|---|
| wrench-api-0.1.tar.gz | 7.3 kB | Without provenance | Details for wrench-api-0.1.tar.gz |
Release files / wrench-api-0.1.tar.gz
| Download URL | wrench-api-0.1.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b840a0e2a2550efac51f95e7ec0bc31fae5d0bd5036b37cf12738cbbf5d05cd
|
|
BLAKE2b-256 checksum How to use checksums |
a2100bfdc21c92f244bb7c01c410cffc7d004de8f53cb730ded10097d008930d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.4.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.2
|
Security for wrench-api 0.1
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.