CRAWDAD uoi/haggle

This dataset contains seven connectivity traces that have been derived from the cambridge/haggle/imote traceset (v. 2009-05-29). These connectivity traces can be used for network simulations with the Opportunistic Network Environment (ONE) simulator, since they are in accordance with the syntax of the StandardEventsReader format. The Python scripts that generated these connectivity traces are also provided.last modified : 2016-08-28nickname : haggleinstitution : University of Ioanninarelease date : 2016-08-28date/time of measurement start : 2005-01-06date/time of measurement end : 2006-04-27collection environment : See cambridge/haggle (v. 2009-05-29)network configuration : See cambridge/haggle (v. 2009-05-29)data collection methodology : See cambridge/haggle (v. 2009-05-29)sanitization : See cambridge/haggle (v. 2009-05-29)Tracesetuoi/haggle/oneConnectivity traces for the ONE simulator that have been derived from the cambridge/haggle/imote traceset (v. 2009-05-29).files: haggle-one-intel.zip, haggle-one-computer-lab.zip, haggle-one-infocom2005.zip, haggle-one-cambridge-city-complete.zip, haggle-one-cambridge-city-students.zip, haggle-one-infocom2006-complete.zip, haggle-one-infocom2006-short-range.zipdescription: Seven connectivity traces were generated from the Bluetooth encounters of the cambridge/haggle dataset (v. 2009-05-29). The scripts that generated these connectivity traces were written in Python and are also available to download along with the respective trace. These Python scripts differ only slightly from each other, since most of the original trace files have a similar format.measurement purpose: Content Distribution Evaluation, Network Performance Analysis, Network Simulation, Opportunistic Connectivity, Routing Protocol for DTNs (Disruption Tolerant Networks), Social Network Analysis, User Mobility Characterizationmethodology: See cambridge/haggle/imote (v. 2009-05-29)sanitization: See cambridge/haggle/imote (v. 2009-05-29)uoi/haggle/one Tracesintel: Bluetooth encounters between 9 mobile and stationary nodes from the cambridge/haggle/imote/intel trace (v. 2009‑05‑29) have been converted into the StandardEventsReader format for use in the ONE simulator.configuration: See cambridge/haggle/imote/intel (v. 2009-05-29)format:The "haggle-one-intel.tsv" file stores tab-separated values of connection events, in accordance with the syntax of the StandardEventsReader format, which can be used for network simulations with the ONE simulator.Each line of this file describes a connection event and has the following five fields:[time] [action] [first_node] [second_node] [type]The first field corresponds to the simulation time at which the event occurred.The second field is always equal to "CONN" since all the events in the connectivity trace are either connection-up or connection-down events.The values of the third and fourth fields correspond to the IDs of two nodes.The fifth field is either "up" when two nodes connect with each other or "down" when two nodes disconnect with each other.computer-lab: Bluetooth encounters between 12 mobile nodes from the cambridge/haggle/imote/cambridge trace (v. 2009‑05‑29) have been converted into the StandardEventsReader format for use in the ONE simulator.configuration: See cambridge/haggle/imote/cambridge (v. 2009-05-29)format:The "haggle-one-computer-lab.tsv" file stores tab-separated values of connection events, in accordance with the syntax of the StandardEventsReader format, which can be used for network simulations with the ONE simulator.Each line of this file describes a connection event and has the following five fields:[time] [action] [first_node] [second_node] [type]The first field corresponds to the simulation time at which the event occurred.The second field is always equal to "CONN" since all the events in the connectivity trace are either connection-up or connection-down events.The values of the third and fourth fields correspond to the IDs of two nodes.The fifth field is either "up" when two nodes connect with each other or "down" when two nodes disconnect with each other.infocom2005: Bluetooth encounters between 41 mobile nodes from the cambridge/haggle/imote/infocom trace (v. 2009‑05‑29) have been converted into the StandardEventsReader format for use in the ONE simulator.configuration: See cambridge/haggle/imote/infocom (v. 2009-05-29)format:The "haggle-one-infocom2005.tsv" file stores tab-separated values of connection events, in accordance with the syntax of the StandardEventsReader format, which can be used for network simulations with the ONE simulator.Each line of this file describes a connection event and has the following five fields:[time] [action] [first_node] [second_node] [type]The first field corresponds to the simulation time at which the event occurred.The second field is always equal to "CONN" since all the events in the connectivity trace are either connection-up or connection-down events.The values of the third and fourth fields correspond to the IDs of two nodes.The fifth field is either "up" when two nodes connect with each other or "down" when two nodes disconnect with each other.cambridge-city-complete: Bluetooth encounters between 52 mobile and stationary nodes from the cambridge/haggle/imote/content trace (v. 2009‑05‑29) have been converted into the StandardEventsReader format for use in the ONE simulator.configuration: See cambridge/haggle/imote/content (v. 2009-05-29)format:The "haggle-one-cambridge-city-complete.tsv" file stores tab-separated values of connection events, in accordance with the syntax of the StandardEventsReader format, which can be used for network simulations with the ONE simulator.Each line of this file describes a connection event and has the following five fields:[time] [action] [first_node] [second_node] [type]The first field corresponds to the simulation time at which the event occurred.The second field is always equal to "CONN" since all the events in the connectivity trace are either connection-up or connection-down events.The values of the third and fourth fields correspond to the IDs of two nodes.The fifth field is either "up" when two nodes connect with each other or "down" when two nodes disconnect with each other.cambridge-city-students: Bluetooth encounters between 36 mobile nodes from the cambridge/haggle/imote/content trace (v. 2009‑05‑29) have been converted into the StandardEventsReader format for use in the ONE simulator.configuration: See cambridge/haggle/imote/content (v. 2009-05-29)format:The "haggle-one-cambridge-city-students.tsv" file stores tab-separated values of connection events, in accordance with the syntax of the StandardEventsReader format, which can be used for network simulations with the ONE simulator.Each line of this file describes a connection event and has the following five fields:[time] [action] [first_node] [second_node] [type]The first field corresponds to the simulation time at which the event occurred.The second field is always equal to "CONN" since all the events in the connectivity trace are either connection-up or connection-down events.The values of the third and fourth fields correspond to the IDs of two nodes.The fifth field is either "up" when two nodes connect with each other or "down" when two nodes disconnect with each other.infocom2006-complete: Bluetooth encounters between 98 short range and long range nodes from the cambridge/haggle/imote/infocom2006 trace (v. 2009‑05‑29) have been converted into the StandardEventsReader format for use in the ONE simulator.configuration: See cambridge/haggle/imote/infocom2006 (v. 2009-05-29)format:The "haggle-one-infocom2006-complete.tsv" file stores tab-separated values of connection events, in accordance with the syntax of the StandardEventsReader format, which can be used for network simulations with the ONE simulator.Each line of this file describes a connection event and has the following five fields:[time] [action] [first_node] [second_node] [type]The first field corresponds to the simulation time at which the event occurred.The second field is always equal to "CONN" since all the events in the connectivity trace are either connection-up or connection-down events.The values of the third and fourth fields correspond to the IDs of two nodes.The fifth field is either "up" when two nodes connect with each other or "down" when two nodes disconnect with each other.infocom2006-short-range: Bluetooth encounters between 78 short range nodes from the cambridge/haggle/imote/infocom2006 trace (v. 2009‑05‑29) have been converted into the StandardEventsReader format for use in the ONE simulator.configuration: See cambridge/haggle/imote/infocom2006 (v. 2009-05-29)format:The "haggle-one-infocom2006-short-range.tsv" file stores tab-separated values of connection events, in accordance with the syntax of the StandardEventsReader format, which can be used for network simulations with the ONE simulator.Each line of this file describes a connection event and has the following five fields:[time] [action] [first_node] [second_node] [type]The first field corresponds to the simulation time at which the event occurred.The second field is always equal to "CONN" since all the events in the connectivity trace are either connection-up or connection-down events.The values of the third and fourth fields correspond to the IDs of two nodes.The fifth field is either "up" when two nodes connect with each other or "down" when two nodes disconnect with each other.