Chambers glow when the running ad hoc world uses them. Every public class in core/include has a chamber; CI checks it.
Each chamber is a part of the core. Choose one to see its classes, what they do, and a link into the full API reference.
Run each command in your ns-3 setup and paste the output below. It is read here, in your browser; nothing is uploaded. No checkout? The release has a drop-in tarball for contrib/.
Every Lab number comes from one ns-3 program that runs several routing protocols on the same seeds, so each difference carries a confidence interval. You can run it on your own protocol: an ns-3 routing module, or a per-hop arm on the adaptive base in about 270 lines.
./ns3 run "routing-compare --scenario=paper --runs=10 --protocols=anthocnet,aodv,olsr --diag"Since v2.6.0 the harness is routing-bench, a module that names no protocol: your module registers its arm in one file and routing-compare finds it. anthocnet-compare still works.