From 08684fa34826b15d91d7096eed24cc307d29634a Mon Sep 17 00:00:00 2001 From: Richard Whitehouse Date: Tue, 17 May 2011 14:31:38 +0100 Subject: [PATCH] Fix symbols used for representing links --- implementation.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/implementation.tex b/implementation.tex index d6ae326..851312f 100644 --- a/implementation.tex +++ b/implementation.tex @@ -110,7 +110,7 @@ The two trace file formats used are a ASCII format included with ns3, as describ \subsection{Topology Representation} -The topology is represented internally with a a std::map between hosts and bridges, since each host may only appear on one bridge, and a std::set of pairs which contains bridge to bridge links with a custom comparator. The custom comparator is designed in order to give a total order to links, without caring about order, as links are bidirectional. Thus <1,2> is treated equal to <2,1>. The order defined is that <1,2> < <1,3> < <4,1> < <3,4>, in other words, the lower number is used for the primary sort, and the larger one as a secondary sort. These provided adequate performance for the purpose. +The topology is represented internally with a a std::map between hosts and bridges, since each host may only appear on one bridge, and a std::set of pairs which contains bridge to bridge links with a custom comparator. The custom comparator is designed in order to give a total order to links, without caring about order, as links are bidirectional. Thus $<1,2>$ is treated equal to $<2,1>$. The order defined is that $<1,2>$ < $<1,3>$ < $<4,1>$ < $<3,4>$, in other words, the lower number is used for the primary sort, and the larger one as a secondary sort. These provided adequate performance for the purpose. \subsection{MOOSE State Tables} -- 2.34.1