Skip to content
swarm-routingPublic

About

HOPNET (Wang, 2007) as a standalone swarm routing protocol for MANETs: ant-colony routing over routing zones, proactive inside a zone and reactive between zones. A simulator-agnostic C++ core and an ns-3 contrib module on swarm-core.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

HOPNET

Group Badges
Build CI Built on: ns3-dev
Quality codecov CodeRabbit Pull Request Reviews
Release Release DOI Cite Licence: GPL-2.0-only, core/ MIT OR GPL-2.0-only
Trust OpenSSF Scorecard OpenSSF Best Practices
Stack C++23 Runs on ns-3
Community & docs Colony Arena: HOPNET Open RCAPA Conventional Commits

HOPNET (Wang, 2007) as a standalone swarm routing protocol for MANETs: ant-colony routing over routing zones, ants hopping between zones. A simulator-agnostic core/ plus the ns-3 contrib module hopnet on swarm-core.

Status: core/ written, ns-3 module in (#5): the intra-zone half (internal ants, IntraRT, neighbour discovery), the inter-zone half (bordercasting, InterRT, data forwarding) and §4.3's local repair are written and tested, and the ns-3 module hopnet carries them out on swarm-core; its anchor against AntHocNet (the thesis's Fig. 5.11) is not reproduced: three pre-registered pilot rounds missed their threshold, so it is recorded as a written infeasibility verdict and HOPNET's numbers do not count in comparisons; the delivery smoke at ≥ 20 seeds is not run yet. Every reading follows the fidelity sheet. See AGENTS.md for the plan.

Release status: the first release, v0.1.0, comes before the comparator gates (maintainer decision 2026-11-10): it has not cleared them (org golden rule 6: fidelity sheet, per-PR delivery smoke, anchor). It ships core/ and docs/; the ns-3 module hopnet and the anchor are pending, so no number from v0.1.0 counts as a benchmark result. The gated release is proposed as v0.2.0; the ladder is in docs/roadmap.md. Releases are cut by release.yml and listed under Releases.

Releases & citing

Versions follow SemVer (CHANGELOG.md). Each release is listed under Releases, built by the org's release workflow and archived on Zenodo with its own DOI.

To cite this repository, use the “Cite this repository” button (from CITATION.cff):

DOI resolves to
10.5281/zenodo.24125265 concept DOI: always the latest release. This is the badge above, and the right citation when you mean this project.

Each release also has its own version DOI, listed on its Zenodo record: cite that one when you reproduce a number measured at that release.

Please also cite the work it builds on:

  • D. H. Joppi, ns3-swarm-core, 2026, doi:10.5281/zenodo.24138628. The shared primitives core/ builds on (pinned by release: swarm-core.lock).
  • J. Wang, HOPNET: a Hybrid ant colony OPtimization routing algorithm for mobile ad hoc NETwork, University of Manitoba, 2008, https://hdl.handle.net/1993/20935 (no DOI: none registered). The primary source this repository implements; docs/fidelity.md maps it to the code and marks the repository choices. Its title page is dated December 2007; the issued date in the University of Manitoba's MSpace record is 2008, the year given here.

What this implementation reproduces from its sources, and every deliberate deviation, is in docs/fidelity.md.

Using it in your work? Contributions are welcome, and citing the DOI helps just as much.

Develop

New here? docs/development.md is the developer guide: the tools to install, how to get the code and its dependencies, how to build, test, run and lint it, the Docker images, what CI checks and how to read a red run. How changes are proposed, reviewed and released is the org's CONTRIBUTING.md. Whether a regression here gets an RCAPA (root cause analysis with corrective and preventive actions), and how: docs/rcapa/README.md.

Epics

What is planned and in progress here: the issues labelled epic. An epic's open sub-issues carry a priority:* and a model:* label, so a contributor or an AI agent can pick one up (how issues work). The whole org's plan: the roadmap.

Epic Status Sub-issues closed
#3 HOPNET as a standalone hexagonal protocol (scheduled after Termite) In progress 2 / 3
#149 developer experience: a newcomer can build, test and contribute from the docs alone In progress 1 / 2

Licence

See LICENSING.md.

About

HOPNET (Wang, 2007) as a standalone swarm routing protocol for MANETs: ant-colony routing over routing zones, proactive inside a zone and reactive between zones. A simulator-agnostic C++ core and an ns-3 contrib module on swarm-core.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages