pDESy: Discrete Time-Event Simulation in Python
What is it?
pDESy is a Python package for Discrete Time-Event Simulation (DES). It aims to be the fundamental high-level building block for practical, real-world engineering project management by using DES and other DES modeling tools. pDESy focuses on Discrete Time-Event Simulation and does not include visual modeling tools.
Where to get it
The source code is currently hosted on GitHub at: https://github.com/pDESy/pDESy
Install the latest released version from the Python Package Index (PyPI):
pip install pDESy
# pip install git+ssh://git@github.com/pDESy/pDESy.git # INSTALL FROM GITHUB
Optional Dependencies
Visualization (matplotlib, plotly): If you want to use visualization features (Gantt charts, network diagrams), install with:
pip install pDESy[vis]
or install the visualization libraries separately (kaleido is required for static image export in plotly):
pip install matplotlib plotly kaleido networkx
Note: Starting from v0.8.0, visualization dependencies (matplotlib, plotly, kaleido, networkx) are optional to avoid mandatory dependency on kaleido, which requires Chrome for v1.0.0+. This keeps the core pDESy package lightweight for CI/CD and production environments.
Documentation
API documentation is available at: https://pDESy.github.io/pDESy/index.html.
License
How to use pDESy?
Example code of pDESy is here.
If you want to implement more complex models for describing real engineering projects, you can create new models by inheriting the base models.
Background
pDESy is developed as part of the next-generation DES tool pDES.
Citation
Mitsuyuki, T., & Okubo, Y. (2024). pDESy: A Python Package for Discrete Time-Event Simulation to Engineering Project. Software Impacts, 19(100621). https://doi.org/10.1016/j.simpa.2024.100621
@article{Mitsuyuki_pDESy_A_Python_2024,
author = {Mitsuyuki, Taiga and Okubo, Yui},
doi = {10.1016/j.simpa.2024.100621},
journal = {Software Impacts},
month = mar,
number = {100621},
title = {pDESy: A Python Package for Discrete Time-Event Simulation to Engineering Project},
volume = {19},
year = {2024}
}
Contribution
- Fork it ( http://github.com/pDESy/pDESy/fork )
- Create your feature branch (git checkout -b my-new-feature)
- Commit your changes (git commit -am 'Add some feature')
- Push to the branch (git push origin my-new-feature)
- Create new Pull Request
If you want to join this project as a researcher, please contact me.
Metadata
Release files for pdesy 0.8.0
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 |
|---|---|---|---|---|
| pdesy-0.8.0.tar.gz | 79.2 kB | Without provenance | Details for pdesy-0.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pdesy-0.8.0-py3-none-any.whl | Python 3 | none | any | Details for pdesy-0.8.0-py3-none-any.whl |
Total release size: 175.6 kB
Release files / pdesy-0.8.0.tar.gz
| Download URL | pdesy-0.8.0.tar.gz |
|---|---|
| Size | 79.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c76c22f461239d79f8ad3285f80c3ec4c61396b279e704783ba799f5ae640cc
|
|
BLAKE2b-256 checksum How to use checksums |
bbaad903393e6e9b89948f4a1e16621688799089e31a60b53e66442d4a356f7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.2 CPython/3.13.2 Darwin/25.3.0
|
Release files / pdesy-0.8.0-py3-none-any.whl
| Download URL | pdesy-0.8.0-py3-none-any.whl |
|---|---|
| Size | 96.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
462adf5afd37e4db2f1e38ae14943ed56ab21e3180f99587ba88ddbff7c16f86
|
|
BLAKE2b-256 checksum How to use checksums |
28952e2994163e48726d5ca2bbc6fb23b6384080906d6977a8b0171d6ec9bd04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.2 CPython/3.13.2 Darwin/25.3.0
|
Security for pdesy 0.8.0
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.