opp_repl
An interactive Python REPL for OMNeT++ — run simulations, compare results, optimize parameters, and run a wide range of regression tests. Provides an MCP server for AI assistants. All features are accessible from both the interactive REPL and command-line tools. See the Overview for the full feature list.
Installation
Requires Python 3.10+.
pip install opp_repl
See Installation for details on optional extras and environment setup.
Quick Start
First, source the OMNeT++ environment:
. /path/to/omnetpp/setenv
Then launch the REPL using existing omnetpp installation:
opp_repl --load "opp/*.opp"
Then run simulations from the REPL:
In [1]: run_simulations(simulation_project=fifo_project)
See Getting started for a full walkthrough.
Documentation
- Overview — features, CLI options, command-line tools
- Installation — requirements, install, optional extras, environment setup
- Getting started — first launch, running simulations, next steps
- The REPL — launch options, namespace, autoreload, user module
- Concepts — core concepts and how they fit together
- OPP files —
.oppfile format, parameters, and examples - Simulation workspaces — project registry, loading, lookup, defaults
- OMNeT++ projects — OMNeT++ installations, executables, building
- Simulation projects — model projects, source layout, dependencies, building
- Simulation configs — INI file discovery, filtering, run counts
- Simulation tasks — task creation, runners, build modes, re-running
- Task results — result codes, inspection, filtering, re-running
- Running simulations — running simulations, building projects, cleaning
- Comparing simulations — simulation comparison
- Smoke tests — smoke tests
- Fingerprint tests — fingerprint tests
- Statistical tests — statistical tests
- Speed tests — speed tests
- Chart tests — chart tests
- Sanitizer tests — sanitizer tests
- Feature tests — feature tests, release tests, running all tests
- Bisecting — bisecting git commits for test failures
- Parameter optimization — parameter optimization
- Code coverage — coverage reports
- Profiling — performance profiling with perf and Hotspot
- Overlay builds — overlay builds
- Cluster — SSH cluster execution
- GitHub Actions — GitHub Actions integration
- MCP server — MCP server for AI assistants
Metadata
Release files for opp-repl 0.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 | |
|---|---|---|---|---|
| opp_repl-0.4.tar.gz | 182.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opp_repl-0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 340.3 kB
Release files / opp_repl-0.4.tar.gz
| Download URL | opp_repl-0.4.tar.gz |
|---|---|
| Size | 182.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b65364f8c91925ba3fb13cdbd61d405e9b702c14b06ea911687692eaa82cf1a7
|
|
BLAKE2b-256 checksum How to use checksums |
c1e66d134a89d3dd43936af8f08d90e8cb44b8fedaa4caabcf44878ac0e1f97b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logRelease files / opp_repl-0.4-py3-none-any.whl
| Download URL | opp_repl-0.4-py3-none-any.whl |
|---|---|
| Size | 157.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0906eed9850d52a8cd6866f3a606aee507b927e7015b33f269ec31f77361f5eb
|
|
BLAKE2b-256 checksum How to use checksums |
cd59fee268f671695f9c5112ae09bfd3487085d43c3bfd17b4154d39e82262db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logSecurity for opp-repl 0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for opp_repl-0.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 11, 2026.
Transparency logA 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.