Main Page - Revision history

Carlo at 16:06, 15 November 2019

2019-11-15T16:06:47Z

Carlo at 08:22, 14 November 2019

2019-11-14T08:22:25Z

Carlo at 08:21, 14 November 2019

2019-11-14T08:21:42Z

Carlo at 11:42, 12 November 2019

2019-11-12T11:42:47Z

Carlo at 11:42, 12 November 2019

2019-11-12T11:42:36Z

Carlo at 11:32, 12 November 2019

2019-11-12T11:32:29Z

Carlo at 11:32, 12 November 2019

2019-11-12T11:32:20Z

Carlo at 11:32, 12 November 2019

2019-11-12T11:32:12Z

Carlo at 11:32, 12 November 2019

2019-11-12T11:32:01Z

Carlo at 09:25, 12 November 2019

2019-11-12T09:25:43Z

@@ Line 9: / Line 9: @@
 |[[File:Logo_dcube.png|395px|right]]
 |}
-Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for general the testing of low-power wireless protocols, but rather to evaluate protocol performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.
+Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for the general testing of low-power wireless protocols, but rather to evaluate protocol performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.
 Detailed performance results of individual test runs are only visible to the protocol developers. Nevertheless, D-Cube also allows developers to provide a binary file that is perpetually tested in a best-effort fashion on specific benchmark suites to accurately profile its performance. Such perpetual performance measurements are publicly available and serve as a reference for academics and companies alike about the performance of consolidated protocols.

@@ Line 10: / Line 10: @@
 |}
 Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for general the testing of low-power wireless protocols, but rather to evaluate protocol performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.
-Detailed performance results of individual test runs are only visible to the protocol developers. Nevertheless, D-Cube also allows developers to provide a binary file that is perpetually tested in a best-effort fashion to accurately profile its performance. Such perpetual performance measurements are publicly available and serve as a reference for academics and companies alike about the performance of consolidated protocols.
+Detailed performance results of individual test runs are only visible to the protocol developers. Nevertheless, D-Cube also allows developers to provide a binary file that is perpetually tested in a best-effort fashion on specific benchmark suites to accurately profile its performance. Such perpetual performance measurements are publicly available and serve as a reference for academics and companies alike about the performance of consolidated protocols.
 <br />

@@ Line 9: / Line 9: @@
 |[[File:Logo_dcube.png|395px|right]]
 |}
-Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for general the testing of low-power wireless protocols, but can only be used to evaluate protocol performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.
+Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for general the testing of low-power wireless protocols, but rather to evaluate protocol performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.
 Detailed performance results of individual test runs are only visible to the protocol developers. Nevertheless, D-Cube also allows developers to provide a binary file that is perpetually tested in a best-effort fashion to accurately profile its performance. Such perpetual performance measurements are publicly available and serve as a reference for academics and companies alike about the performance of consolidated protocols.

@@ Line 12: / Line 12: @@
 Detailed performance results of individual test runs are only visible to the protocol developers. Nevertheless, D-Cube also allows developers to provide a binary file that is perpetually tested in a best-effort fashion to accurately profile its performance. Such perpetual performance measurements are publicly available and serve as a reference for academics and companies alike about the performance of consolidated protocols.
 D-Cube currently supports two [[Supported Platforms|popular hardware platforms]]: the TelosB (Tmote Sky) mote and the Nordic Semiconductors nRF52840. Hence, D-Cube enables the benchmarking of solutions based on IEEE 802.15.4 and Bluetooth Low Energy technology.
 With about [[Observer Nodes|50 nodes]] for each available platform and the ability to [[Special Features|generate harsh RF conditions]], D-Cube is well-suited for testing the performance of mesh networking and multi-hop solutions in the presence of radio interference.

@@ Line 9: / Line 9: @@
 |[[File:Logo_dcube.png|395px|right]]
 |}
-Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for general testing, but can only be used to evaluate performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.
+Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for general the testing of low-power wireless protocols, but can only be used to evaluate protocol performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.
-Detailed performance results of individual test runs are only available to the protocol developers. Nevertheless, D-Cube also allows developers to provide a binary that is perpetually tested in a best-effort fashion to accurately profile its performance. Such perpetual performance measurements are publicly available and serve as a reference for academics and companies alike about the performance of consolidated protocols.
+Detailed performance results of individual test runs are only visible to the protocol developers. Nevertheless, D-Cube also allows developers to provide a binary file that is perpetually tested in a best-effort fashion to accurately profile its performance. Such perpetual performance measurements are publicly available and serve as a reference for academics and companies alike about the performance of consolidated protocols.
 D-Cube currently supports two [[Supported Platforms|popular hardware platforms]]: the TelosB (Tmote Sky) mote and the Nordic Semiconductors nRF52840. Hence, D-Cube enables the benchmarking of solutions based on IEEE 802.15.4 and Bluetooth Low Energy technology.

@@ Line 7: / Line 7: @@
 The primary audience of D-Cube are academic researchers and industry practitioners creating low-power wireless networking solutions that would like to quantitatively assess and compare their performance with that of other systems addressing the same class of applications.
 |[[File:empty.png|left|65px]]
-|[[File:Logo_dcube.png|325px|right]]
+|[[File:Logo_dcube.png|395px|right]]
 |}
 Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for general testing, but can only be used to evaluate performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.

@@ Line 6: / Line 6: @@
 Hosted at [https://www.tugraz.at/en/institutes/iti/home/ Graz University of Technology], D-Cube supports the automated testing of the reliability, timeliness, and energy consumption of low-power wireless communication protocols in a variety of settings.
 The primary audience of D-Cube are academic researchers and industry practitioners creating low-power wireless networking solutions that would like to quantitatively assess and compare their performance with that of other systems addressing the same class of applications.
-|[[File:empty.png|left|55px]]
+|[[File:empty.png|left|65px]]
-|[[File:Logo_dcube.png|345px|right]]
+|[[File:Logo_dcube.png|365px|right]]
 |}
 Differently from other public low-power wireless testbeds such as [https://gitlab.ethz.ch/tec/public/flocklab/wikis/home FlockLab], [https://indriya.comp.nus.edu.sg/ Indriya2], [https://www.iot-lab.info/ FIT IoT-Lab], and [https://www.twist.tu-berlin.de/ TWIST], D-Cube is not meant for general testing, but can only be used to evaluate performance in pre-defined scenarios. To this end, D-Cube allows developers to test and optimize their solutions for one or more [[Overview of Available Suites|benchmark suites]], i.e., for specific application scenarios and hardware platforms.