simpy
Skill22 starsChanged 9 months agoMITView on GitHub
A process-based discrete-event simulation framework. Use for modeling queuing systems, supply chains, manufacturing processes, network simulation, project management, and any system where events occur at specific points in time. Load when working with discrete event simulation, process modeling, resource allocation, virtual time, simpy.Environment, simpy.Resource, or event-driven simulation.
- Installs packages
We split this skill into the rules it gives an agent
13 rules. 0 are common, 3 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 87
Set a random seed: - Always use random.seed(42) for reproducible simulations.
- Very specific: line 88
Pass the
envobject: - Every process and resource needs a reference to the environment to track time. - Very specific: line 89
Use
env.run(until=...): - Always define a stopping condition, otherwise a while True simulation will run forever. - Distinctive: line 96
Forget to yield: - If you don't yield an event inside a loop, you create an infinite loop at the same instant in virtual time, hanging the …
- Very specific: line 290
Avoid printing to the console in high-speed simulations.
- Very specific: line 296
If your code reaches a logic branch where no yield occurs in a while True loop, SimPy freezes.
- Very specific: line 317
Never mix objects (Resources, Processes) from different environments.
- Very specific: line 321
When interrupting a process, the interrupt happens at the current virtual time.
- Very specific: line 326
Set random seeds for reproducibility: - Use random.seed(42) at the start of simulations
- Very specific: line 328
Define clear stopping conditions: - Always use env.run(until=...) with a specific time limit
- Very specific: line 329
Use virtual time only: - Never mix time.sleep() or real-world time with SimPy
- Distinctive: line 330
Test with small simulations first: - Verify logic before running large-scale simulations
- Distinctive: line 332
Handle interruptions properly: - Use try/except blocks when processes can be interrupted
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SimPy - Discrete Event Simulation
SimPy allows you to model real-world processes as Python generators. Components in SimPy (like customers, cars, or data packets) are "processes" that interact with each other and with limited "resources" (like servers, parking spots, or bandwidth).
When to Use
- Modeling queuing systems (Bank tellers, call centers, hospital emergency rooms)
- Simulating supply chains and logistics (Warehouses, transport networks)
- Analyzing manufacturing processes (Assembly lines, machine maintenance)
- Network simulation (Packet routing, server load balancing)
- Project management (Task dependencies, resource allocation)
- Any system where "events" occur at specific points in time rather than continuously
Reference Documentation
Official docs: https://simpy.readthedocs.io/
GitHub: https://github.com/simpy/simpy
Search patterns: simpy.Environment, simpy.Resource, env.process, yield env.timeout
Core Principles
Virtual Time
SimPy uses an internal clock starting at 0. Time moves forward only when an event is processed. Between events, "nothing" happens, so simulating 100 years takes seconds if only a few events occur.
Processes as Generators
Processes are standard Python functions using yield. When a process yields an event, SimPy suspends it until that event occurs.
Resources
Three types of shared objects:
- Resource: Limited number of slots (e.g., a counter)
- Container: For bulk matter (e.g., a gas tank, RAM)
- Store: For distinct objects (e.g., a buffer of messages)
Quick Reference
Installation
pip install simpyStandard Imports
import simpy
import randomBasic Pattern - A Simple Process
import simpy
def clock(env, name, tick):
while True:
print(f"{name} at {env.now}")
# 'yield' tells SimPy to wait for this event
yield env.timeout(tick)
# 1. Create Environment
env = simpy.Environment()
# 2. Add Process
env.process(clock(env, 'Fast', 0.5))
env.process(clock(env, 'Slow', 1.0))
# 3. Run for 2 units of virtual time
env.run(until=2.1)Critical Rules
✅ DO
- Use
yield env.timeout(n)- This is the only way to advance time for a process. Never usetime.sleep(). - Use
with resource.request() as req:- This ensures a resource is automatically released even if the process is interrupted or fails. - Set a random seed - Always use
random.seed(42)for reproducible simulations. - Pass the
envobject - Every process and resource needs a reference to the environment to track time. - Use
env.run(until=...)- Always define a stopping condition, otherwise awhile Truesimulation will run forever. - Collect data in lists - Store timestamps and event details in external lists for post-simulation analysis (e.g., with Pandas).
❌ DON'T
- Use real-world time - simpy is for virtual time.
env.nowis your only clock. - Modify the environment directly - Interact with it only through processes and events.
- Forget to yield - If you don't yield an event inside a loop, you create an infinite loop at the same instant in virtual time, hanging the simulation.
- Block the event loop - Heavy CPU calculations inside a process should be rare; they "stop" the virtual clock of the entire simulation while the CPU works.
Anti-Patterns (NEVER)
import simpy
import time
# ❌ BAD: Using real sleep
def bad_process(env):
time.sleep(1) # This stops the REAL clock, but virtual time doesn't move!
yield env.timeout(1)
# ✅ GOOD: Use virtual timeout
def good_process(env):
yield env.timeout(1) # Moves virtual clock forward instantly
# ❌ BAD: Infinite loop without yielding
# def hang_forever(env):
# while True:
# x = 1 + 1 # No yield = simulation clock stuck at current env.now
# ❌ BAD: Manual resource release (Dangerous)
def risky_request(env, res):
req = res.request()
yield req
# If something fails here, the resource is never released
res.release(req)
# ✅ GOOD: Using context manager
def safe_request(env, res):
with res.request() as req:
yield req
# Resource automatically released when exiting 'with'Resources and Queues (simpy.Resource)
Managing Shared Capacity
def car(env, name, bcs, driving_time, charge_time):
# Simulate driving to the station
yield env.timeout(driving_time)
print(f'{name} arriving at {env.now}')
# Request one of the charging spots
with bcs.request() as req:
yield req
print(f'{name} starting to charge at {env.now}')
yield env.timeout(charge_time)
print(f'{name} leaving at {env.now}')
env = simpy.Environment()
# Battery Charging Station with 2 spots
bcs = simpy.Resource(env, capacity=2)
for i in range(4):
env.process(car(env, f'Car {i}', bcs, i*2, 5))
env.run()Advanced Resources: Containers and Stores
Containers (Liquids/Bulk)
# Modeling a gas station tank
gas_tank = simpy.Container(env, capacity=1000, init=500)
def refuel(env, gas_tank):
yield gas_tank.put(400) # Add fuel
def car(env, gas_tank):
yield gas_tank.get(40) # Consume fuelStores (Distinct Objects)
# Modeling a producer-consumer buffer
buffer = simpy.Store(env, capacity=10)
def producer(env, buffer):
yield buffer.put(f'Widget at {env.now}')
def consumer(env, buffer):
item = yield buffer.get()
print(f'Consumed {item}')Event Synchronization
Waiting for Multiple Events
# Wait for BOTH events
yield env.timeout(10) & other_process_event
# Wait for EITHER event
yield env.timeout(10) | other_process_eventPractical Workflows
1. Hospital Emergency Room Model
def patient(env, name, nurse, doctor):
arrival_time = env.now
# 1. Wait for Nurse (Triage)
with nurse.request() as req:
yield req
yield env.timeout(random.expovariate(1/5)) # 5 mins avg
# 2. Wait for Doctor (Treatment)
with doctor.request() as req:
yield req
yield env.timeout(random.normalvariate(20, 5)) # 20 mins avg
wait_times.append(env.now - arrival_time)
wait_times = []
env = simpy.Environment()
nurse = simpy.Resource(env, capacity=2)
doctor = simpy.Resource(env, capacity=1)
# ... launch processes ...2. Machine Failure and Repair
def machine(env, repairman):
while True:
try:
# Working phase
working_time = 100
yield env.timeout(working_time)
except simpy.Interrupt:
# Interrupted by failure
with repairman.request() as req:
yield req
yield env.timeout(10) # Repair time
def break_machine(env, machine_proc):
while True:
yield env.timeout(random.uniform(50, 200))
machine_proc.interrupt()3. Server Request Handling (Data Collection)
import pandas as pd
log = []
def request(env, server):
start_wait = env.now
with server.request() as req:
yield req
wait = env.now - start_wait
service_time = random.expovariate(1.0)
yield env.timeout(service_time)
log.append({
'arrival': start_wait,
'wait': wait,
'service': service_time,
'finish': env.now
})
# After simulation:
# df = pd.DataFrame(log)
# print(df['wait'].mean())Performance Optimization
Using simpy.PriorityResource
In systems where some events are more important (e.g., critical patients), use PriorityResource.
res = simpy.PriorityResource(env, capacity=1)
with res.request(priority=0) as req: # Lower number = higher priority
yield reqMonitoring Large Simulations
Avoid printing to the console in high-speed simulations. Instead, use a data collection list and process it with NumPy/Pandas after the env.run() finishes.
Common Pitfalls and Solutions
The "Stuck Process"
If your code reaches a logic branch where no yield occurs in a while True loop, SimPy freezes.
# ❌ Problem:
def logic_error(env):
while True:
if condition:
yield env.timeout(1)
# Else? If condition is false, we loop forever at same time point!
# ✅ Solution:
def logic_fixed(env):
while True:
if condition:
yield env.timeout(1)
else:
yield env.timeout(0.1) # Or some default waitMultiple Environments
Never mix objects (Resources, Processes) from different environments. Every component must belong to the same simpy.Environment() instance.
Interruption Timing
When interrupting a process, the interrupt happens at the current virtual time. Be careful with what the interrupted process was yielding (it will receive a simpy.Interrupt exception).
Best Practices
- Always use context managers for resources -
with resource.request() as req:ensures proper cleanup - Set random seeds for reproducibility - Use
random.seed(42)at the start of simulations - Collect data externally - Store event data in lists/dictionaries, not just print statements
- Define clear stopping conditions - Always use
env.run(until=...)with a specific time limit - Use virtual time only - Never mix
time.sleep()or real-world time with SimPy - Test with small simulations first - Verify logic before running large-scale simulations
- Document your processes - Clearly name processes and resources for debugging
- Handle interruptions properly - Use try/except blocks when processes can be interrupted
SimPy turns Python's generator syntax into a powerful engine for modeling time and scarcity. It allows scientists and engineers to experiment with "What if?" scenarios for complex systems without the cost or risk of physical trials.
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- LeonChaoX/qinyan-academic-skills★ 910same name
- qinyan-ai/qinyan-academic-skills★ 80same name
- BrightGold70/skills★ 1same name
- Luooops/skills★ 1same name
- uppifyagency/boilerplate-saas-2026★ 1same name
- yf8578/claude-skills-collection★ 1same name
- davidanthonyn/claude-skills★ 0same name
- patoangolano/bio-stack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use usfiscaldata, deeptools and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
yf8578Skillusfiscaldata
Query the U.S. Treasury Fiscal Data API for federal financial data including national debt, government spending, revenue, interest rates, exchange rates, and savings bonds. Access 54 datasets and 182 data tables with no API key required. Use when working with U.S. federal fiscal data, national debt tracking (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates on Treasury securities, foreign exchange rates, savings bonds, or any U.S. government financial statistics.
Also in 6 projects that use this
garri333Skilldeeptools
NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.
Also in 7 projects that use this
garri333Skilldnanexus-integration
DNAnexus cloud genomics platform. Build apps/applets, manage data (upload/download), dxpy Python SDK, run workflows, FASTQ/BAM/VCF, for genomics pipeline development and execution.
Also in 7 projects that use this
Hongyu-yuSkilltorch-geometric
Graph Neural Networks (PyG). Node/graph classification, link prediction, GCN, GAT, GraphSAGE, heterogeneous graphs, molecular property prediction, for geometric deep learning.
Also in 7 projects that use this
- +8 more from garri333
In this repository69 other files it gives its agents.
- aseSkill
- astropySkill
- biopythonSkill
- chempySkill
- cobrapySkill
- dask-optimizationSkill
- daskSkill
- dowhySkill
- duckdbSkill
- example-skillSkill
- fastapi-streamlitSkill
- geopandasSkill
- gmsh-meshioSkill
- h5pySkill
- jax-pdeSkill
- jaxSkill
- lifelinesSkill
- matplotlib-proSkill
- matplotlibSkill
- mdanalysisSkill
- mneSkill
- networkxSkill
- numbaSkill
- numpy-low-levelSkill
- numpySkill
- openbabelSkill
- opencvSkill
- ortoolsSkill
- pandas-performanceSkill
- pennylaneSkill
- photutilsSkill
- plotlySkill
- polarsSkill
- prodySkill
- pydicomSkill
- pymcSkill
- pyomoSkill
- pyprojSkill
- pysamSkill
- pyscfSkill
- pytorch-deploymentSkill
- pytorch-geometricSkill
- pytorch-researchSkill
- pytorchSkill
- qiskit-hardwareSkill
- qiskitSkill
- qutipSkill
- rasterioSkill
- rdkitSkill
- scanpySkill
- scikit-bioSkill
- scikit-imageSkill
- scikit-learnSkill
- scikit-videoSkill
- scipySkill
- seabornSkill
- shapelySkill
- sklearn-advancedSkill
- sklearn-explainabilitySkill
- sktime-tsfreshSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

