-Our protocol is declined into four versions: MuDiLCO-1,
- MuDiLCO-3, MuDiLCO-5, and MuDiLCO-7, corresponding respectively to $T=1,3,5,7$
- ($T$ the number of rounds in one sensing period). Since the time resolution
- may be prohibitive when the size of the problem increases, a time limit
- threshold has been fixed when solving large instances. In these cases, the
- solver returns the best solution found, which is not necessary the optimal
- one. In practice, we only set time limit values for $T=5$ and $T=7$. In fact,
- for $T=5$ we limited the time for 250~nodes, whereas for $T=7$ it was for the
- three largest network sizes. Therefore we used the following values (in
- second): 0.03 for 250~nodes when $T=5$, while for $T=7$ we chose 0.03, 0.06,
- and 0.08 for respectively 150, 200, and 250~nodes. These time limit
- thresholds have been set empirically. The basic idea is to consider the
- average execution time to solve the integer programs to optimality for 100
- nodes and then to adjust the time linearly according to the increasing network
- size. After that, this threshold value is increased if necessary so that the
- solver is able to deliver a feasible solution within the time limit. In fact,
- selecting the optimal values for the time limits will be investigated in the
- future.
+Our protocol is declined into four versions: MuDiLCO-1, MuDiLCO-3, MuDiLCO-5,
+and MuDiLCO-7, corresponding respectively to $T=1,3,5,7$ ($T$ the number of
+rounds in one sensing period). Since the time resolution may be prohibitive when
+the size of the problem increases, a time limit threshold has been fixed when
+solving large instances. In these cases, the solver returns the best solution
+found, which is not necessary the optimal one. In practice, we only set time
+limit values for $T=5$ and $T=7$. In fact, for $T=5$ we limited the time for
+250~nodes, whereas for $T=7$ it was for the three largest network sizes.
+Therefore we used the following values (in second): 0.03 for 250~nodes when
+$T=5$, while for $T=7$ we chose 0.03, 0.06, and 0.08 for respectively 150, 200,
+and 250~nodes. These time limit thresholds have been set empirically. The basic
+idea is to consider the average execution time to solve the integer programs to
+optimality for 100 nodes and then to adjust the time linearly according to the
+increasing network size. After that, this threshold value is increased if
+necessary so that the solver is able to deliver a feasible solution within the
+time limit. In fact, selecting the optimal values for the time limits will be
+investigated in the future.