Vehicular networks have various characteristics that can be helpful in their inter-relations identifications. Considering that two vehicles are moving at a certain speed and distance, it is important to know about their communication capability. The vehicles can communicate within their communication range. However, given previous data of a road segment, our dataset can identify the compatibility time between two selected vehicles. The compatibility time is defined as the time two vehicles will be within the communication range of each other.
Each row contains characteristic information related to two vehicles at time t. Data set feature set (column headings) are as follows:
- Euclidean Distance: The shortest distance between two vehicles in meters
- Relative Velocity: The velocity of 2nd vehicles as seen from 1st vehicle
- Direction Difference: Given the direction information of each vehicle, the direction difference feature identifies the angle both vehicles are moving towards. For instance, two vehicles going on the same road can have direction difference 0, whereas two vehicles moving in the opposite direction will have a difference of 180. we calculated direction difference using: |((Direction of i - Direction of j+ 180)%360 - 180)| .
- Direction Difference Label: To ease the process for the supervised learning model, we also included direction difference label information by identifying three possible directions ( 0 if difference < 60, 2 if difference >120 and 1 if none of above)
- Tendency: The Tendency is an interesting label that is required to differentiate between two vehicles which are moving in opposite directions, but either they are approaching each other or moving away from each other.
Target Label (Compatibility time): Our goal is to identify how long two vehicles will be in the communication range of each other. The predicted compatibility time label tells us five possible values:
L0 means Compatibility Time is 0
L1 means Compatibility Time is more than 2 seconds but less than 5 seconds
L2 means Compatibility Time is more than 5 seconds but less than 10 seconds
L3 means Compatibility Time is more than 10 seconds but less than 15 seconds
L4 means Compatibility Time is more than 15 seconds
Recognition and classification of currency is one of the important task. It is a very crucial task for visually impaired people. It helps them while doing day to day financial transactions with shopkeepers while traveling, exchanging money at banks, hospitals, etc. The main objectives to create this dataset were:
1) Create a dataset of old and new Indian currency.
2) Create a dataset of Thai Currency.
3) Dataset consists of high-quality images.
The dataset consists of 10 classes namely 10 New, 10 Old, 20, 50 New, 50 Old, 100 New, 100 Old, 200, 500, 2000 of Indian banknotes and 5 classes namely 20, 50, 100, 500, and 2000 for Thai bank notes.
INDIA is the second-largest fruit and vegetable exporter in the world after China. It ranked first in the production of Bananas, Papayas, and Mangoes. Public datasets of fruits are available but they are limited to general fruit classes and failed to classify the fruits according to the fruit quality. To overcome this problem, we have created a dataset named FruitsGB (Fruits Good/Bad) dataset.
The data set contains 12 classes of fruits namely Bad Apple, Good Apple, Bad Banana, Good Banana, Bad Guava, Good Guava, Bad Lime, Good Lime, Bad Orange, Good Orange, Bad Pomegranate, and Good Pomegranate.
Message Queuing Telemetry Transport (MQTT) protocol is one of the most used standards used in Internet of Things (IoT) machine to machine communication. The increase in the number of available IoT devices and used protocols reinforce the need for new and robust Intrusion Detection Systems (IDS). However, building IoT IDS requires the availability of datasets to process, train and evaluate these models. The dataset presented in this paper is the first to simulate an MQTT-based network. The dataset is generated using a simulated MQTT network architecture.
The dataset consists of 5 pcap files, namely, normal.pcap, sparta.pcap, scan_A.pcap, mqtt_bruteforce.pcap and scan_sU.pcap. Each file represents a recording of one scenario; normal operation, Sparta SSH brute-force, aggressive scan, MQTT brute-force and UDP scan respectively. The attack pcap files contain background normal operations. The attacker IP address is “192.168.2.5”. Basic packet features are extracted from the pcap files into CSV files with the same pcap file names. The features include flags, length, MQTT message parameters, etc. Later, unidirectional and bidirectional features are extracted. It is important to note that for the bidirectional flows, some features (pointed as *) have two values—one for forward flow and one for the backward flow. The two features are recorded and distinguished by a prefix “fwd_” for forward and “bwd_” for backward.
Dataset used for "A Machine Learning Approach for Wi-Fi RTT Ranging" paper (ION ITM 2019). The dataset includes almost 30,000 Wi-Fi RTT (FTM) raw channel measurements from real-life client and access points, from an office environment. This data can be used for Time of Arrival (ToA), ranging, positioning, navigation and other types of research in Wi-Fi indoor location. The zip file includes a README file, a CSV file with the dataset and several Matlab functions to help the user plot the data and demonstrate how to estimate the range.
Copyright (C) 2018 Intel Corporation
Welcome to the Intel WiFi RTT (FTM) 40MHz dataset.
The paper and the dataset can be downloaded from:
To cite the dataset and code, or for further details, please use:
Nir Dvorecki, Ofer Bar-Shalom, Leor Banin, and Yuval Amizur, "A Machine Learning Approach for Wi-Fi RTT Ranging," ION Technical Meeting ITM/PTTI 2019
For questions/comments contact:
The zip file contains the following files:
1) This README.txt file.
2) LICENSE.txt file.
3) RTT_data.csv - the dataset of FTM transactions
4) Helper Matlab files:
O mainFtmDatasetExample.m - main function to run in order to execute the Matlab example.
O PlotFTMchannel.m - plots the channels of a single FTM transaction.
O PlotFTMpositions.m - plots user and Access Point (AP) positions.
O ReadFtmMeasFile.m - reads the RTT_data.csv file to numeric Matlab matrix.
O SimpleFTMrangeEstimation.m - execute a simple range estimation on the entire dataset.
O Office1_40MHz_VenueFile.mat - contains a map of the office from which the dataset was gathered.
Running the Matlab example:
In order to run the Matlab simulation, extract the contents of the zip file and call the mainFtmDatasetExample() function from Matlab.
Contents of the dataset:
The RTT_data.csv file contains a header row, followed by 29581 rows of FTM transactions.
The first column of the header row includes an extra "%" in the begining, so that the entire csv file can be easily loaded to Matlab using the command: load('RTT_data.csv')
Indexing the csv columns from 1 (leftmost column) to 467 (rightmost column):
O column 1 - Timestamp of each measurement (sec)
O columns 2 to 4 - Ground truth (GT) position of the client at the time the measurement was taken (meters, in local frame)
O column 5 - Range, as estimated by the devices in real time (meters)
O columns 6 to 8 - Access Point (AP) position (meters, in local frame)
O column 9 - AP index/number, according the convention of the ION ITM 2019 paper
O column 10 - Ground truth range between the AP and client (meters)
O column 11 - Time of Departure (ToD) factor in meters, such that: TrueRange = (ToA_client + ToA_AP)*3e8/2 + ToD_factor (eq. 7 in the ION ITM paper, with "ToA" being tau_0 and the "ToD_factor" lumps up both nu initiator and nu responder)
O columns 12 to 467 - Complex channel estimates. Each channel contains 114 complex numbers denoting the frequency response of the channel at each WiFi tone:
O columns 12 to 125 - Complex channel estimates for first antenna from the client device
O columns 126 to 239 - Complex channel estimates for second antenna from the client device
O columns 240 to 353 - Complex channel estimates for first antenna from the AP device
O columns 354 to 467 - Complex channel estimates for second antenna from the AP device
The tone frequencies are given by: 312.5E3*[-58:-2, 2:58] Hz (e.g. column 12 of the csv contains the channel response at frequency fc-18.125MHz, where fc is the carrier wave frequency).
Note that the 3 tones around the baseband DC (i.e. around the frequency of the carrier wave), as well as the guard tones, are not included.
The aircraft fuel distribution system has two primary functions: storing fuel and distributing fuel to the engines. These functions are provided in refuelling and consumption phases, respectively. During refuelling, the fuel is first loaded in the Central Reservation Tank and then distributed to the Front and Rear Tanks. In the consumption phase, the two engines receive an adequate level of fuel from the appropriate tanks. For instance, the Port Engine (PE) will receive fuel from Front Tank and the Starboard Engine (SE) will receive fuel from Rear Tank.
You can easily read the CSV files and apply your method.The dataset has five parts, one normal and four abnormal scenarios.
The database contains the raw range-azimuth measurements obtained from mmWave MIMO radars (IWR1843BOOST http://www.ti.com/tool/IWR1843BOOST) deployed in different positions around a robotic manipulator.
The database that contains the raw range-azimuth measurements obtained from mmWave MIMO radars inside a Human-Robot (HR) workspace environment.
The database contains 5 data structures:
i) mmwave_data_test has dimension 900 x 256 x 63. Contains 900 FFT range-azimuth measurements of size 256 x 63: 256-point range samples corresponding to a max range of 11m (min range of 0.5m) and 63 angle bins, corresponding to DOA ranging from -75 to +75 degree. These data are used for testing (validation database). The corresponding labels are in label_test. Each label (from 0 to 5) corresponds to one of the 6 positions (from 1 to 6) of the operator as detailed in the image attached.
ii) mmwave_data_train has dimension 900 x 256 x 63. Contains 900 FFT range-azimuth measurements used for training. The corresponding labels are in label_train.
iii) label_test with dimension 900 x 1, contains the true labels for test data (mmwave_data_test), namely classes (true labels) correspond to integers from 0 to 5.
iv) label_train with dimension 900 x 1, contains the true labels for train data (mmwave_data_train), namely classes (true labels) correspond to integers from 0 to 5.
v) p (1 x 900) contains the chosen random permutation for data partition among nodes/device and federated learnig simulation (see python code).
We collected experimental field data with a prototype open-ended waveguide sensor (WR975) operating between 600 MHz - 1300 MHz. With our prototype sensor we collected reflection coefficient measurements at a total of 50 unique 1-ft^2 sites across two separate established cranberry beds in central Wisconsin. The sensor was placed directly on top of cranberry-crop bed canopies, and we obtained 12 independent reflection coefficient measurements (each defined as one S11 sweep across frequency) at each 1-ft^2 site by randomly rotating and/or translating the sensor aperture above each site. After