OpenScience - User contributions [en]

OLQ one week

2015-12-10T15:41:47Z

Till: /* Datasets */

=== Description ===

The data set contains OLSR link quality over one week.

=== Contact contributors ===

* [[User:Thm|Thomas Mundt]]

=== Datasets ===

{| {{Prettytable}}
!Data
!Description
!Format
|-
|https://opsci.informatik.uni-rostock.de/repos/datasets/olsr/samples.dat
|Link quality (LQ) as collected at one node's OLSR daemon describing the entire network.
|Tabulator separated list, each line contains: Timestamp NodeA NodeB LinkQuality (received OLSR packets divided by sent OLSR packets - from A to B) NeighborLinkquality (from B to A). Links are asymmetric.
|}

=== Publications ===

=== Software ===

[[thmONAG]]

=== Comments ===

https://console.developers.google.com/datastore/indexes?project=thmonaga

Network quality measurements

2015-04-29T12:26:03Z

Till: Publications: TVCG paper added

=== Description ===
Data from a performance measurement study carried out in a 802.11 wireless mesh network. The network uses the OLSR protocol in conjunction with the ETX metric. The study was conducted to evaluate the quality of service in terms of throughput, packet loss, latency, and jitter and the dependency of these parameters on the routing metric.

=== Contact to contributors ===
* [[User:Till|Till Wollenberg]]

=== Datasets ===
{| {{Prettytable}}
!Dataset
!Size
!Description
|-
|[http://www.informatik.uni-rostock.de/~till/olqm2b/report.csv.gz report.csv]
|27.4k lines, 1.1 MiB
|Results of ping, wget, and computed ETX and path LQ values (main table).
|-
|[http://www.informatik.uni-rostock.de/~till/olqm2b/traceroute.csv.gz traceroute.csv]
|101k lines, 346 KiB
|Traceroute information (list of hops) per report (if available).
|-
|[http://www.informatik.uni-rostock.de/~till/olqm2b/topology.csv.gz topology.csv]
|3.1M lines, 19 MiB
|Topology information (entire OLSR network graph as list of unidirectional links).
|}

==== report ====
{| {{Prettytable}}
!Column
!Description
!Range
!Special values
|-
|id
|Unique ID per report
|1…27463
| None
|-
|epoch
|Unix time of the point when the measurement cycle started (usually 15 minutes after the full hour). Since all tests within a cycle were run sequentially, this is usually not the time of the actual test. The time of the actual test has not been recorded.
|1293837301…1306876501
| None
|-
|timestamp
|Start time of measurement cycle in local time (see ''epoch'' and ''timezone'').
|"2011-01-01 00:15:01"…"2011-05-31 23:15:01"
| None
|-
|timezone
|Timezone for ''timestamp''.
|"CET, "CEST"
| None
|-
|timeindex
|"Hour of year" starting at 2011-01-01 00:00 (local time). Used to connect report table to topology table.
|0…3623
| None
|-
|node_id
|Network node that was tested (ID is alias for IP address of the node and therefore may not be unique per node for nodes with multiple IP addresses).
|"n1"…"n353"
| None
|-
|duplicate
|For some measurement cycles, a particular node was select twice for test. ''duplicate'' is "yes" for the second test of this node and "no" in all other cases.
|"no", "yes"
| None
|-
|validity
|"valid" for all reports were the initial "up" tests succeeded, all ping commands, traceroute, and wget were executed successfully, and wget finished downloading 1 MiB of data. "incomplete" otherwise.
|"valid", "incomplete"
| None
|-
|test_status
|0 if the initial "up" test succeeded, 1 if the test failed. In the latter case, all further tests were skipped and a new node was selected for test.
|0, 1
| None
|-
|ping*_status
|0 if ping command was executed successfully. 1 if ping command returned an error. A packet loss of 100% is considered to be an error (see ''ping_loss'').
| -1, 0, 1
| -1 if ping test was not executed (see ''test_status'')
|-
|traceroute_status
|0 if traceroute command was executed successfully. 1 if traceroute command returned an error. The latter never happened in the current data set.
| -1, 0
| -1 if traceroute was not executed (see ''test_status'')
|-
|wget_status
|0 if wget command was executed successfully. Other status codes according to wget man page: 4=Network failure, 6=Username/password authentication failure, 8=Server issued an error response. Codes 6 and 8 may be caused by nodes which were not compatible with our testing method.
| -1, 0, 4, 6, 8
| -1 if wget was not executed (see ''test_status'')
|-
|ping*_loss
|Number of lost packets (a total of 100 packets were sent for each test). Note: for cases with 100% packet loss ping reports an error. For these cases you will find ''ping_loss'' to be -1 and ''ping_status' to be 1.
| -1,0…99
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|ping*_rttmin
|Minimum round trip time (in ms) found in all received replies.
| -1, 0.178…28783.935
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|ping*_rttavg
|Average round trip time (in ms) of all received replies.
| -1, 0.229…29296.789
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|ping*_rttmax
|Maximum round trip time (in ms) found in all received replies.
| -1, 0.320…36032.101
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|ping*_rttmdev
|Standard deviation of round trip time over all received replies.
| -1, 0.000…12348.795
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|wget_transfer
|"aborted" if wget reported a "read error" during the download. "completed" if the download finished successfully.
|"aborted", "completed"
| None
|-
|wget_bytes
|Number of bytes transferred by wget until wget exited. The wget download may have stopped either because the download was complete or because it was interrupted (e.g. timed out). See ''wget_transfer''.
| -1, 40…1048576
| -1 if wget command was not executed successfully (i.e. ''wget_status'' is not 0)
|-
|wget_rate
|Download data rate as reported by wget (bytes per second). Note: wget reports only three significant digits ("180 B/s", "1.18 MB/s"), the number is converted to bytes per second herein.
| -1.00, 160.00…419430400.00
| -1 if wget command was not executed successfully (i.e. ''wget_status'' is not 0)
|-
|traceroute_hops
|Number of "hops" (on IP level) between measurement node and tested node.
| -1, 1…19
| -1 if traceroute information is missing or incomplete
|-
|traceroute_pathlq
|Product of all LQ values along the path reported by traceroute. This is the probability of a successful packet transmission from the tested node to the measurement node (from OLSR's point of view).
| -1, 0.000…1.000
| -1 if LQ product could not be computed (e.g. missing information)
|-
|traceroute_pathnlq
|Product of all NLQ values along the path reported by traceroute. This is the probability of a successful packet transmission from the measurement node to the tested node (from OLSR's point of view).
| -1, 0.000…1.000
| -1 if NLQ product could not be computed (e.g. missing information)
|-
|traceroute_etx
|Computed ETX value for the path between tested node and measurement node.
| -1, 1.000…99.792, 999.000
| -1 if ETX could not be computed (e.g. missing information), 999 if either LQ or NLQ is 0 for at least one link ("infinity").
|}

Note: ping was executed three times (IP packet size 84, 532, and 1500 bytes). Therefore, each ping-related variable exists three times with the prefixes "ping_", "ping512_", and "ping1k5_". In the above tables, "ping*_" is used to indicate that.

==== traceroute ====
{| {{Prettytable}}
!Column
!Description
!Range
!Special values
|-
|report_id
|Unique ID of the report to which this route belongs.
|2…27200
|None
|-
|hop_id
|Hop index within route.
|0…18
|None
|-
|from_node
|Node from which this hop originates. Note: for hop=0 this is always the measurement node.
|"n1"…"n353"
|None
|-
|to_node
|Node at which this hop terminates. Note: for the last hop within a particular route this is always the tested node.
|"n1"…"n353"
|None
|}

==== topology ====
{| {{Prettytable}}
!Column
!Description
!Range
!Special values
|-
|time
|Time when the snapshot of the network graph was taken. (Always 14 minutes after the full hour, i.e. 1 minute before the measurement cycle started.) <span style="color:#FF0000">TODO: Add timezone information</span>
|"2011-01-01 00:14:01"…"2011-05-31 23:14:01"
|None
|-
|timeindex
|"Hour of year" starting at 2011-01-01 00:00 (local time). Used to connect report table to topology table.
|0…3623
|None
|-
|this_node
|Node ID of the "local end" of the link.
|"n1"…"n353"
|None
|-
|other_node
|Node ID of the "remote end" of the link.
|"n1"…"n353"
|None
|-
|lq
|OLSR link quality for the link from ''other_node'' to ''this_node''.
|0.000…1.000
|None
|-
|nlq
|OLSR link quality for the link from ''this_node'' to ''other_node''.
|0.000…1.000
|None
|}

=== Publications ===
* Till Wollenberg: '''Performance Measurement Study in a Wireless OLSR-ETX Mesh Network'''. IFIP Wireless Days. Dublin, Ireland. November 2012. DOI: [http://dx.doi.org/10.1109/WD.2012.6402882 10.1109/WD.2012.6402882]. This paper at [http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=6402882 IEEE Xplore]
* Steffen Hadlak, Heidrun Schumann, Clemens H. Cap, Till Wollenberg: '''Supporting the Visual Analysis of Dynamic Networks by Clustering associated Temporal Attributes'''. Accepted for publication in: Special Issue of IEEE Transactions on Visualization and Computer Graphics (TVCG), 2013. [http://www.informatik.uni-rostock.de/~hadlak/pub_files/2013Hadlak-TempClustering.pdf PDF version] (5.1 MB) Please visit [http://www.informatik.uni-rostock.de/~hadlak/ Steffen's website] for more information.

=== Software ===
To be published.

=== Comments ===
None.

Network quality measurements

2015-04-29T12:23:07Z

Till: Download-Links vorrübergehed nach ox-Abschaltung auf public_html umgebogen, Paper eingefügt.

=== Description ===
Data from a performance measurement study carried out in a 802.11 wireless mesh network. The network uses the OLSR protocol in conjunction with the ETX metric. The study was conducted to evaluate the quality of service in terms of throughput, packet loss, latency, and jitter and the dependency of these parameters on the routing metric.

=== Contact to contributors ===
* [[User:Till|Till Wollenberg]]

=== Datasets ===
{| {{Prettytable}}
!Dataset
!Size
!Description
|-
|[http://www.informatik.uni-rostock.de/~till/olqm2b/report.csv.gz report.csv]
|27.4k lines, 1.1 MiB
|Results of ping, wget, and computed ETX and path LQ values (main table).
|-
|[http://www.informatik.uni-rostock.de/~till/olqm2b/traceroute.csv.gz traceroute.csv]
|101k lines, 346 KiB
|Traceroute information (list of hops) per report (if available).
|-
|[http://www.informatik.uni-rostock.de/~till/olqm2b/topology.csv.gz topology.csv]
|3.1M lines, 19 MiB
|Topology information (entire OLSR network graph as list of unidirectional links).
|}

==== report ====
{| {{Prettytable}}
!Column
!Description
!Range
!Special values
|-
|id
|Unique ID per report
|1…27463
| None
|-
|epoch
|Unix time of the point when the measurement cycle started (usually 15 minutes after the full hour). Since all tests within a cycle were run sequentially, this is usually not the time of the actual test. The time of the actual test has not been recorded.
|1293837301…1306876501
| None
|-
|timestamp
|Start time of measurement cycle in local time (see ''epoch'' and ''timezone'').
|"2011-01-01 00:15:01"…"2011-05-31 23:15:01"
| None
|-
|timezone
|Timezone for ''timestamp''.
|"CET, "CEST"
| None
|-
|timeindex
|"Hour of year" starting at 2011-01-01 00:00 (local time). Used to connect report table to topology table.
|0…3623
| None
|-
|node_id
|Network node that was tested (ID is alias for IP address of the node and therefore may not be unique per node for nodes with multiple IP addresses).
|"n1"…"n353"
| None
|-
|duplicate
|For some measurement cycles, a particular node was select twice for test. ''duplicate'' is "yes" for the second test of this node and "no" in all other cases.
|"no", "yes"
| None
|-
|validity
|"valid" for all reports were the initial "up" tests succeeded, all ping commands, traceroute, and wget were executed successfully, and wget finished downloading 1 MiB of data. "incomplete" otherwise.
|"valid", "incomplete"
| None
|-
|test_status
|0 if the initial "up" test succeeded, 1 if the test failed. In the latter case, all further tests were skipped and a new node was selected for test.
|0, 1
| None
|-
|ping*_status
|0 if ping command was executed successfully. 1 if ping command returned an error. A packet loss of 100% is considered to be an error (see ''ping_loss'').
| -1, 0, 1
| -1 if ping test was not executed (see ''test_status'')
|-
|traceroute_status
|0 if traceroute command was executed successfully. 1 if traceroute command returned an error. The latter never happened in the current data set.
| -1, 0
| -1 if traceroute was not executed (see ''test_status'')
|-
|wget_status
|0 if wget command was executed successfully. Other status codes according to wget man page: 4=Network failure, 6=Username/password authentication failure, 8=Server issued an error response. Codes 6 and 8 may be caused by nodes which were not compatible with our testing method.
| -1, 0, 4, 6, 8
| -1 if wget was not executed (see ''test_status'')
|-
|ping*_loss
|Number of lost packets (a total of 100 packets were sent for each test). Note: for cases with 100% packet loss ping reports an error. For these cases you will find ''ping_loss'' to be -1 and ''ping_status' to be 1.
| -1,0…99
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|ping*_rttmin
|Minimum round trip time (in ms) found in all received replies.
| -1, 0.178…28783.935
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|ping*_rttavg
|Average round trip time (in ms) of all received replies.
| -1, 0.229…29296.789
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|ping*_rttmax
|Maximum round trip time (in ms) found in all received replies.
| -1, 0.320…36032.101
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|ping*_rttmdev
|Standard deviation of round trip time over all received replies.
| -1, 0.000…12348.795
| -1 if ping* was not executed or returned an error (see ''ping*_status'')
|-
|wget_transfer
|"aborted" if wget reported a "read error" during the download. "completed" if the download finished successfully.
|"aborted", "completed"
| None
|-
|wget_bytes
|Number of bytes transferred by wget until wget exited. The wget download may have stopped either because the download was complete or because it was interrupted (e.g. timed out). See ''wget_transfer''.
| -1, 40…1048576
| -1 if wget command was not executed successfully (i.e. ''wget_status'' is not 0)
|-
|wget_rate
|Download data rate as reported by wget (bytes per second). Note: wget reports only three significant digits ("180 B/s", "1.18 MB/s"), the number is converted to bytes per second herein.
| -1.00, 160.00…419430400.00
| -1 if wget command was not executed successfully (i.e. ''wget_status'' is not 0)
|-
|traceroute_hops
|Number of "hops" (on IP level) between measurement node and tested node.
| -1, 1…19
| -1 if traceroute information is missing or incomplete
|-
|traceroute_pathlq
|Product of all LQ values along the path reported by traceroute. This is the probability of a successful packet transmission from the tested node to the measurement node (from OLSR's point of view).
| -1, 0.000…1.000
| -1 if LQ product could not be computed (e.g. missing information)
|-
|traceroute_pathnlq
|Product of all NLQ values along the path reported by traceroute. This is the probability of a successful packet transmission from the measurement node to the tested node (from OLSR's point of view).
| -1, 0.000…1.000
| -1 if NLQ product could not be computed (e.g. missing information)
|-
|traceroute_etx
|Computed ETX value for the path between tested node and measurement node.
| -1, 1.000…99.792, 999.000
| -1 if ETX could not be computed (e.g. missing information), 999 if either LQ or NLQ is 0 for at least one link ("infinity").
|}

Note: ping was executed three times (IP packet size 84, 532, and 1500 bytes). Therefore, each ping-related variable exists three times with the prefixes "ping_", "ping512_", and "ping1k5_". In the above tables, "ping*_" is used to indicate that.

==== traceroute ====
{| {{Prettytable}}
!Column
!Description
!Range
!Special values
|-
|report_id
|Unique ID of the report to which this route belongs.
|2…27200
|None
|-
|hop_id
|Hop index within route.
|0…18
|None
|-
|from_node
|Node from which this hop originates. Note: for hop=0 this is always the measurement node.
|"n1"…"n353"
|None
|-
|to_node
|Node at which this hop terminates. Note: for the last hop within a particular route this is always the tested node.
|"n1"…"n353"
|None
|}

==== topology ====
{| {{Prettytable}}
!Column
!Description
!Range
!Special values
|-
|time
|Time when the snapshot of the network graph was taken. (Always 14 minutes after the full hour, i.e. 1 minute before the measurement cycle started.) <span style="color:#FF0000">TODO: Add timezone information</span>
|"2011-01-01 00:14:01"…"2011-05-31 23:14:01"
|None
|-
|timeindex
|"Hour of year" starting at 2011-01-01 00:00 (local time). Used to connect report table to topology table.
|0…3623
|None
|-
|this_node
|Node ID of the "local end" of the link.
|"n1"…"n353"
|None
|-
|other_node
|Node ID of the "remote end" of the link.
|"n1"…"n353"
|None
|-
|lq
|OLSR link quality for the link from ''other_node'' to ''this_node''.
|0.000…1.000
|None
|-
|nlq
|OLSR link quality for the link from ''this_node'' to ''other_node''.
|0.000…1.000
|None
|}

=== Publications ===
* Till Wollenberg: '''Performance Measurement Study in a Wireless OLSR-ETX Mesh Network'''. IFIP Wireless Days. Dublin, Ireland. November 2012. DOI: [http://dx.doi.org/10.1109/WD.2012.6402882 10.1109/WD.2012.6402882]. This paper at [http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=6402882 IEEE Xplore]

=== Software ===
To be published.

=== Comments ===
None.

Open Science Repository at the Information and Communication Services Group at the University of Rostock

2012-09-13T10:45:24Z