A template for creating discrete-event simulation (DES) models in Python
within a reproducible analytical pipeline (RAP).
Click on Use this template to initialise new repository.
A README
template is provided at the end of this file.
Table of contents:
- πΒ Β Introduction
- π§ What are we modelling?
- π οΈ Using this template
- β How does the model work?
- π Repository structure
- β° Run time and machine specification
- π Citation
- π Licence
- π° Funding
- π Template README for your project
This repository provides a template for building discrete-event simulation (DES) models in Python.
π Simple: Easy-to-follow code structure using SimPy. Implements a simple M/M/s queueing model in which patients arrive, wait to see a nurse, have a consultation with the nurse and then leave. Follows a modular structure: uses object-oriented programming, with the simulation implemented through classes.
β»οΈ Reproducible: This template is designed to function as a RAP. It adheres to reproducibility recommendations from:
- "Levels of RAP" framework from the NHS RAP Community of Practice (
docs/nhs_rap.md
). - Recommendations from Heather et al. 2025 "On the reproducibility of discrete-event simulation studies in health research: an empirical study using open models" (
docs/heather_2025.md
).
π Extendable: This template adapts from Sammi Rosser and Dan Chalk (2024) "HSMA - the little book of DES". The book includes additional advanced features that can be used to extend the model in this template, including:
- Multiple activities
- Branching paths
- Priority-based queueing
- Reneging, blaking and jockeying
- Variable arrival rates
- Appointment booking
For clarity, changes from the DES book in this template are explained in docs/hsma_changes.md
.
β¨ Style: The coding style is based on the Google Python Style Guide. Linting is implemented using flake8
and pylint
for .py
files, and pycodestyle
for .ipynb
files.
𧱠Package structure: In Python, a package can simply be defined as a directory with an __init__.py
file in it. In this repository, the scripts for model (within simulation/
) are treated as a little local package. This keeps the code model code isolated from our experiments and analysis. It is installed as an editable (-e
) local import - with -e
meaning it will update with changes to the local files in simulation/
. As it is installed in our environment, it can then easily be used anywhere else in the directory - here, in notebooks/
and tests/
- without needing any additional code (e.g. no need to modify sys.path
, or have additional __init__.py
files).
A simulation is a computer model that mimics a real-world system. It allows us to test different scenarios and see how the system behaves. One of the most common simulation types in healthcare is DES.
In DES models, time progresses only when specific events happen (e.g., a patient arriving or finishing treatment). Unlike a continuous system where time flows smoothly, DES jumps forward in steps between events. For example, when people (or tasks) arrive, wait for service, get served, and then leave.
Simple model animation created using web app developed by Sammi Rosser (2024) available at https://github.com/hsma-programme/Teaching_DES_Concepts_Streamlit and shared under an MIT Licence.
One simple example of a DES model is the M/M/s queueing model, which is implemented in this template. In a DES model, we use well-known statistical distributions to describe the behaviour of real-world processes. In an M/M/s model we use:
- Poisson distribution to model patient arrivals - and so, equivalently, use an exponential distribution to model the inter-arrival times (time from one arrival to the next)
- Exponential distribution to model server times.
These can be referred to as Markovian assumptions (hence "M/M"), and "s" refers to the number of parallel servers available.
For this M/M/s model, you only need three inputs:
- Average arrival rate: How often people typically arrive (e.g. patient arriving to clinic).
- Average service duration: How long it takes to serve one person (e.g. doctor consultation time).
- Number of servers: How many service points are available (e.g. number of doctors).
This model could be applied to a range of contexts, including:
Queue | Server/Resource |
---|---|
Patients in a waiting room | Doctor's consultation |
Patients waiting for an ICU bed | Available ICU beds |
Prescriptions waiting to be processed | Pharmacists preparing and dispensing medications |
For further information on M/M/s models, see:
- Ganesh, A. (2012). Simple queueing models. University of Bristol. https://people.maths.bris.ac.uk/~maajg/teaching/iqn/queues.pdf.
- Green, L. (2011). Queueing theory and modeling. In Handbook of Healthcare Delivery Systems. Taylor & Francis. https://business.columbia.edu/faculty/research/queueing-theory-and-modeling.
- Click on Use this template.
- Provide a name and description for your new project repository.
- Clone the repository locally:
git clone https://github.com/username/repo
cd repo
Use the provided environment.yaml
file to set up a reproducible Python environment with conda
:
conda env create --file environment.yaml
conda activate
The provided environment.yaml file is a snapshot of the environment used when creating the template, including specific package versions. You can update this file if necessary, but be sure to test that everything continues to work as expected after any updates. Also note that some dependencies are not required for modelling, but instead served other purposes, like running .ipynb
files and linting.
As an alternative, a requirements.txt
file is provided which can be used to set up the environment with virtualenv
. This is used by GitHub actions, which run much faster with a virtual environment than a conda environment. However, we recommend locally installing the environment using conda, as it will also manage the Python version for you. If using virtualenv
, it won't fetch a specific version of Python - so please note the version listed in environment.yaml
.
π Choose your desired licence (e.g. https://choosealicense.com/). If keeping an MIT licence, just modify the copyright holder in LICENSE
.
π Review the example DES implementation in simulation
and notebooks
. Modify and extend the code as needed for your specific use case.
π Check you still fulfil the criteria in docs/nhs_rap.md
and docs/heather_2025.md
.
π Adapt the template README
provided at the end of this file.
π Create your own CITATION.cff
file using cff-init.
π Replace pyproject.toml
and entries in the current CHANGELOG.md
with your own versions, and create GitHub releases.
π Archive your repository (e.g. Zenodo).
π Complete the Strengthening The Reporting of Empirical Simulation Studies (STRESS) checklist (stress_des.md
) and use this to support writing publication/report, and attach as an appendice to report.
π Tests
To run tests, ensure environment is active and located in main directory (i.e. parent of tests/
) and then run the following command. The tests may take around one minute to run. As they run, you will see '.' if the test passes and 'F' if it fails (e.g. tests/test_backtest.py ..F..
). When it finishes, you will see the final result (e.g. ==== 1 failed, 4 passed in 51s ====
)
pytest
To run tests in parallel -
pytest -n auto
The repository contains a GitHub action tests.yaml
which will automatically run tests with new commits to GitHub. This is continuous integration, helping to catch bugs early and keep the code stable. It will run the tests on three operating systems: Ubuntu, Windows and Mac.
If you have changed the model behaviour, you may wish to amend, remove or write new tests.
π Linting
You can lint the .py
files by running either of this commands from the terminal:
flake8 simulation/model.py
pylint simulation/model.py
The first commands in the .ipynb
files will lint the notebooks using pycodestyle
when executed:
%load_ext pycodestyle_magic
%pycodestyle_on
This section describes the purposes of each class in the simulation.
Model Run Process:
-
Set Parameters: Create a
Defaults
instance and modify it with desired model parameters. -
Initialise Model: Instantiate
Model
using the parameters. During setup,Model
createsExponential
instances for each distribution. -
Run Simulation: Call
model.run()
to execute the simulation within the SimPy environment, running two processes:generate_patient_arrivals()
to handle patient creation, then sending them on toattend_clinic()
.interval_audit()
to record utilisation and wait times at specified intervals during the simulation.
Runner Class Usage:
Having set up experiment = Runner()
...
- Single Run: Use
experiment.run_single()
to execute a single model run. - Multiple Runs: Use
experiment.run_reps()
to perform multiple replications of the model.
Illustration of model structure created using draw.io.
repo/
βββ .github/workflows/ # GitHub actions
βββ docs/ # Documentation
βββ images/ # Image files and GIFs
βββ inputs/ # Folder to store any input data
βββ notebooks/ # Run DES model and analyse results
βββ outputs/ # Folder to save any outputs from model
βββ simulation/ # Local package containing code for the DES model
βββ tests/ # Unit and back testing of the DES model
βββ .gitignore # Untracked files
βββ .pylintrc # Pylint settings
βββ CHANGELOG.md # Describes changes between releases
βββ CITATION.cff # How to cite the repository
βββ CONTRIBUTING.md # Contribution instructions
βββ environment.yaml # Conda environment (includes Python version)
βββ LICENSE # Licence file
βββ pyproject.toml # Metadata for local `simulation/` package
βββ README.md # This file! Describes the repository
βββ requirements.txt # Virtual environment (used by GitHub actions)
The overall run time will vary depending on how the template model is used. A few example implementations are provided in notebooks/
and the run times for these were:
analysis.ipynb
- 23schoosing_parameters.ipynb
- 22sgenerate_exp_results.ipynb
- 0s
These times were obtained on an Intel Core i7-12700H with 32GB RAM running Ubuntu 24.04.1 Linux.
If you use this template, please cite the archived repository:
Heather, A. (2025). Simple Reproducible Python Discrete-Event Simulation (DES) Template. Zenodo. https://doi.org/10.5281/zenodo.14622466
You can also cite the GitHub repository:
Heather, A. (2025). Simple Reproducible Python Discrete-Event Simulation (DES) Template. GitHub. https://github.com/pythonhealthdatascience/rap_template_python_des.
Researcher details:
Contributor | ORCID | GitHub |
---|---|---|
Amy Heather | https://github.com/amyheather |
This template is licensed under the MIT License.
MIT License
Copyright (c) 2025 STARS Project Team
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
This project was developed as part of the project STARS: Sharing Tools and Artefacts for Reproducible Simulations. It is supported by the Medical Research Council [grant number MR/Z503915/1].
Delete everything from this line and above, and use the following structure as the starting point for your project README:
Provide a concise description of your project.
Provide instructions for installing dependencies and setting up the environment.
Provide step-by-step instructions and examples.
Clearly indicate which files will create each figure in the paper. Hypothetical example:
- To generate Figures 1 and 2, execute
notebooks/base_case.ipynb
- To generate Table 1 and Figures 3 to 5, execute
notebooks/scenario_analysis.ipynb
State the run time, and give the specification of the machine used (which achieved that run time).
Example: Intel Core i7-12700H with 32GB RAM running Ubuntu 24.04.1 Linux.
To find this information:
- Linux: Run
neofetch
on the terminal and record your CPU, memory and operating system. - Windows: Open "Task Manager" (Ctrl + Shift + Esc), go to the "Performance" tab, then select "CPU" and "Memory" for relevant information.
- Mac: Click the "Apple Menu", select "About This Mac", then window will display the details.
Explain how to cite your project and include correct attribution for this template.