Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
1,772
datasets available to search
ShareScore release 0.7.1
Dataset results
1,772 results for “Sensor”
Dataset of "Towards Artefact Aware Human Motion Capture using Inertial Sensors Integrated into Loose Clothing"
<p>This dataset was used in the publication:<br> <strong>Towards Artefact Aware Human Motion Capture using Inertial Sensors Integrated into Loose Clothing</strong><br> presented at the IEEE International Conference on Robotics and Automation 2022</p> <p><strong>Abstract:</strong><br> Inertial motion capture has become an attractive alternative to optical motion capture for human joint angle estimation outside the laboratory. Usually inertial sensors are assumed to be tightly fixed to the body segments, which can be cumbersome regarding setup-time and ease-of-use. However, integrating the sensors directly into clothing, usually, results in additional clothing motion relative to the motion of the underlying bones that should be captured.<br> In this work we propose the <em>Difference Mapping</em> distributions approach that corrects the segment orientations of a given inertial motion capture system that assumes tightly coupled sensors.<br> The approach allows to reduce the joint angle errors due to clothing artefacts by at least 77.2 percent for people with similar morphology performing a similar task as seen in the training data, including an ergonomic assessments scenario at work places with 10 participants. <br> Moreover, we show that the uncertainty of the distribution can be used to measure the reliability of the predicted map if e.g. the motion is further away from the training data to allow for an artefact aware inertial motion tracking approach.<br> The experimental data for this study is available online</p> <p> </p> <p><strong>Data structure:</strong><br> The data contains trials of 12 subjects for different motions, wearing at the same time a tight setup with inertial sensors and a loose working suit with integrated inertial sensors. It contains the raw IMU data, raw Magnetometer data and the estimated segment orientations using a Sensor Fusion engine provided by Sci-Track.<br> Please note, that in the publication only the first 10 subjects were used and the upper body information was used only. The Sternum sensor of the tight setup of subjects 11, 12 and 13 tilted slowly during the long-term measurements. For this reason only 10 subjects were included in the study. However all remaining sensor of the tight setup were not tilted during recording. In particular the lower body recordings of all subjects are not corrupted.<br> <br> Code samples, a visualizer and further useful information is provided under the following git repository:<br> https://github.com/lorenzcsunikl/Dataset-of-Artefact-Aware-Human-Motion-Capture-using-Inertial-Sensors-Integrated-into-Loose-Clothing</p>
Battery-less Environment Sensor Using Thermoelectric Energy Harvesting From Soil-Ambient Air Temperature Differences
<p>The data set contains the data collected from experiments sites in Belgium ( Campus Drie Eiken, University of Antwerp, 51.161° N, 4.408° W) and Iceland ( Forhot, 64.008° N, 21.178° W) for the research and evaluation of a battery-less environment sensor powered by energy harvesting. The device uses the temperature difference between soil and air to produce energy with the help of a Thermoelectric Generator (TEG) and powers a wireless sensor node. The data set includes data collected from 2 phases of the study. One during the initial evaluation phase where we collected soil temperatures at 15 cm and air temperature to evaluate the possibilities of producing energy from the temperature differences. Using these data, we estimated the energy production capacity for both sites. Further, a proof-of-concept device was developed, and its performance was evaluated with field experiments. During this process, we collected the voltage level of the storage unit, i.e, the capacitor, air and soil temperatures and the TEG output voltage. During both phases, the same methods were employed to collect data. The voltage values were measured with a 12-bit ADC and the temperature was measured with 1-Wire temperature sensor. Further, the collected data were transferred to cloud storage in real-time for further analysis and evaluation. </p> <ul> <li><strong>cde_mseasurements_oct2020-nov2020.csv</strong> <ul> <li> Soil temperature and air temperature data from the Campus Drie Eiken at the University of Antwerp, Belgium. The data were collected from 2 Oct 2020 to 17 Nov 2020.</li> </ul> </li> <li><strong>cde_teg_measurements.csv</strong> <ul> <li>Soil temperature, ambient temperature and the open-circuit voltage of TEG from Campus Drie Eiken at the University Antwerp, Belgium from 21 Apr 2021 to 25 Apr May 2021. Also includes the difference calculated between the two temperature values.</li> </ul> </li> <li><strong>cde_energy_simulated.csv</strong> <ul> <li>Energy production capacity estimated using the temperature data collected from Campus Drie Eiken at the University of Antwerp.</li> </ul> </li> <li><strong>aui_measurements_nov-2021.csv</strong> <ul> <li>Soil temperature and air temperature data from the Forhot research site in Iceland for the month of November 2021.</li> </ul> </li> <li><strong>aui_teg_measurements.csv</strong> <ul> <li>Soil temperature, ambient temperature and the open-circuit voltage of TEG collected from the Forhot research site in Iceland. Also includes the difference calculated between the two temperature values. The data were collected from 18 Nov 2021 to 30 Nov 2021</li> </ul> </li> <li><strong>aui_energy_simulated.csv</strong> <ul> <li>Energy production capacity estimated using the temperature data collected from the Forhot research site in Iceland.</li> </ul> </li> <li><strong>cde_capacitor_voltage.csv</strong> <ul> <li>The voltage level of the capacitor used by the battery-less device to buffer the harvested energy. The device was deployed at the Campus Drie Eiken and the data collection was carried out from 1 Mar 2022 to 12 Apr 2022. A 15 mF supercapacitor was used. </li> </ul> </li> </ul>
MSPB: a longitudinal multi-sensor dataset with phenotypic trait measurements from honey bees
<p>We present a one-year-long <strong>M</strong>ulti-<strong>S</strong>ensor dataset with <strong>P</strong>henotypic trait measurements from honey <strong>B</strong>ees (MSPB). Data were continuously collected between April-2020 and April-2021 from 53 hives located at two apiaries in Québec, Canada. The sensor data included audio features, temperature, and relative humidity. The phenotypic measurements contained beehive population, number of brood cells (eggs, larva and pupa), <em>Varroa</em> destructor infestation levels, defensive and hygienic behaviors, honey yield, and winter mortality. Our study is amongst the first to provide a wide variety of phenotypic trait measurements annotated by apicultural science experts, which facilitate a broader scope of analysis on honey bees, such as bee acoustics analysis, multi-modal hive monitoring, queen presence detection, <em>Varroa </em>infection detection, hive population estimation, biological analysis of bees, etc.</p> <h3>Related Info</h3> <p>The data collection process, feature pre-processing, preliminary data analysis, and usage notes can be found in our paper <a href="https://arxiv.org/abs/2311.10876">https://arxiv.org/abs/2311.10876</a></p> <p>Check the project webpage (<a href="https://zhu00121.github.io/MSPB-webpage/">https://zhu00121.github.io/MSPB-webpage/</a>) and Github repo (<a href="https://github.com/MuSAELab/MSPB">https://github.com/MuSAELab/MSPB</a>) for more information.</p> <h3>Citation</h3> <p>Kindly cite the following paper:</p> <p>@misc{zhu2023mspb,</p> <p> title={MSPB: a longitudinal multi-sensor dataset with phenotypic trait measurements from honey bees}, </p> <p> author={Yi Zhu and Mahsa Abdollahi and Ségolène Maucourt and Nico Coallier and Heitor R. Guimarães and Pierre Giovenazzo and Tiago H. Falk},</p> <p> year={2023},</p> <p> eprint={2311.10876},</p> <p> archivePrefix={arXiv},</p> <p> primaryClass={eess.AS}</p> <p>}</p> <h3>Contact</h3> <p>You can contact us at Yi.Zhu@inrs.ca, if you encounter any questions accessing the data.</p>
Smart Home Sensor and HVAC Control Dataset from the SHAL Demonsrtator of the Aegis Project
<p>The example dataset was produced within the Smart Home and Assisted Living demonstrator of the AEGIS project. IT contains measurements of indoor temperature and HVAC control actions (ON/OFF status and setpoint values), which were be used to extract comfort profiles.</p>
COMPAIR traffic and air quality sensor data
<p>Sensor data regarding traffic and air quality was gathered as part of the <a href="https://cordis.europa.eu/project/id/101036563">EU Horizon2020 COMPAIR project</a> in Europe. The pilot cities/regions are Berlin, Athens, Sofia, Plovdiv, and Flanders.<br><br>During the project, the data was published through an <a href="https://sensorthings.wecompair.eu/FROST-Server/v1.1/Things">OGC SensorThings API</a>. To persist after the project, the air quality related are available as CSV exports, with the retention of the API's structure (Location, Thing, Datastream, Sensor, ObservedProperty, and Observation). Observations about air quality contain sensor readings regarding nitrodioxide (NO2), black carbon (BC), particulate matter (PM1.0, PM2.5 and PM10), humidity and temperature. The NO2 observations are calibrated data streams.<br><br>The traffic observations remain available through the <a href="https://app.swaggerhub.com/apis-docs/telraam/Telraam-API/1.2.0">API of the Telraam platform</a>.<br><br><br></p>
Telraam sensor dataset API - www.telraam-api.net
<p>This dataset is a collection of publicly available API call methods that can be used to access Telraam (<a href="https://telraam.net/">https://telraam.net/</a>) data, connected to our server.</p> <p>The dataset includes all data collected with Telraam sensors, including the sensors deployed during the WeCount project, but also in scope of other projects or by private individuals.</p> <p>The data and API documentation is accessible via <a href="http://www.telraam-api.net">http://www.telraam-api.net</a></p>
The VAROS Synthetic Underwater Data Set: Towards realistic multi-sensor underwater data with ground truth
<p>Underwater visual perception requires being able to deal with bad and rapidly varying illumination and with reduced visibility due to water turbidity. The verification of such algorithms is crucial for safe and efficient underwater exploration and intervention operations. Ground truth data play an important role in evaluating vision algorithms. However, obtaining ground truth from real underwater environments is in general very hard, if possible at all. In a synthetic underwater 3D environment, however, (nearly) all parameters are known and controllable, and ground truth data can be absolutely accurate in terms of geometry. In this paper, we present the VAROS environment, our approach to generating highly realistic underwater video and auxiliary sensor data with precise ground truth, built around the Blender modeling and rendering environment. VAROS allows for physically realistic motion of the simulated underwater (UW) vehicle including moving illumination. Pose sequences are created by first defining way-points for the simulated underwater vehicle which are expanded into a smooth vehicle course sampled at IMU data rate (200Hz). This expansion uses a vehicle dynamics model and a discrete-time controller algorithm that simulates the sequential following of the way-points. The scenes are rendered using the raytracing method, which generates realistic images, integrating direct light, and indirect volumetric scattering. The VAROS dataset version 1 provides images, inertial measurement unit (IMU) and depth gauge data, as well as ground truth poses, depth images and surface normal images.</p>
Displacement measurements of the open-hardware sandbox using the AS5311 high-resolution magnetic sensor
<p>This dataset includes the experimental data from the AS5311 sensor for measuring the displacement of the Open-Hardware Geological Sandbox.</p> <p>These experiments are explained in the journal article: <a href="https://doi.org/10.1109/ACCESS.2023.3262617">Designing low-cost open-hardware electromechanical scientific equipment: A geological analogue modeling sandbox</a></p> <p>To understand this dataset, go to the Tectonic Open Hardware (TectOH) Sandbox project: <a href="https://github.com/URJCMakerGroup/TectOH">https://github.com/URJCMakerGroup/TectOH</a>. Then go to the <a href="https://github.com/URJCMakerGroup/TectOH/tree/main/optional">optional</a> folder and to the <a href="https://github.com/URJCMakerGroup/TectOH/tree/main/optional/as5311_magn_sens">magnetic sensor</a> folder.</p> <p>This data set contains two kind of files:</p> <ul> <li><strong>bin</strong>: raw binary files received from the AS5311 high resolution sensor. Although this sensor sends 12 bit data, we have truncated the most significant bits and receive only 8 bits (one byte). Therefore, each byte of these binary files is a measurement of the distance. Each distance increment corresponds to ~0.488nm (2mm/2048)</li> <li><strong>csv</strong>: csv files that can be opened with any spreadsheet app, such as Libreoffice Calc or Microsoft Excel, or even with a text editor. This file contains the processed data from the binary files. These files have been generated with the proc_magn_sensor.py Python script located in the <a href="https://github.com/URJCMakerGroup/TectOH">project repository</a>. There are some columns, which are: <ul> <li>index: measurement number</li> <li>time in milliseconds: each measurement is taken every 250 us</li> <li>median2: in micrometers, since the sensor may jitter, we have applied the median filter twice. All the data has been subtracted to the lowest value, making the lowest value equal to zero.</li> <li>median1: in micrometers, median filter only applied once. All the data has been subtracted to the lowest value, making the lowest value equal to zero.</li> <li>mean: in micrometers, mean filter. All the data has been subtracted to the lowest value, making the lowest value equal to zero.</li> <li>mean int: in micrometers, mean filter rounded to an integer value. All the data has been subtracted to the lowest value, making the lowest value equal to zero.</li> <li>orig_base: this is not in micrometers, but in the units of the sensor (~0.488nm). The only processing done is that when there is an overflow of 255 to 0, or from 0 to 255, it adds the overflow to continue the trend. All the data has been subtracted to the lowest value, making the lowest value equal to zero.</li> <li>original: this is the data received from the sensor with no processing, each value is ~0.488nm</li> <li>mean2: in micrometers, mean filter applied twice. All the data has been subtracted to the lowest value, making the lowest value equal to zero.</li> </ul> </li> </ul> <p>There are two set of experiments:</p> <ul> <li><strong>Experiments with no load</strong>. These files start with <em>noload_</em><br> In these experiments the gantry is moved 1 mm alternatively to the front and then reversing direction. Moving in this alternate way a few times. There are five experiments each of them with a different speed: v= 10 mm/h; 25 mm/h; 50 mm/h; 82 mm/h and 100 mm/h. The name of the file indicates the speed: <ol> <li>noload_100mmh_1mm: FBFBF: 1mm forth, 1mm back, 1mm forth, 1mm back, 1 mm forth</li> <li>noload_25mmh_1mm: FBFFBBFB</li> <li>noload_50mmh_1mm: FBFBFB</li> <li>noload_82mmh_1mm: FBFBFB</li> <li>noload_100mmh_1mm: FBFBFB</li> </ol> </li> <li><strong>Experiments pushing a 5kg sand load</strong>. These files start with <em>load5kg_</em> <ol> <li>load5kg_25mmh_5mm: moving 5kg at 25mm/h a distance of 5mm</li> <li>load5kg_25mmh_10mm: moving 5kg at 25mm/h a distance of 10mm</li> <li>load5kg_25mmh_20mm: moving 5kg at 25mm/h a distance of 20mm</li> <li>load5kg_75mmh_20mm: moving 5kg at 75mm/h a distance of 20mm</li> <li>load5kg_75mmh_50mm: moving 5kg at 75mm/h a distance of 50mm</li> <li>load5kg_100mmh_25mm: moving 5kg at 100mm/h a distance of 20mm</li> <li>load5kg_100mmh_50mm: moving 5kg at 100mm/h a distance of 50mm</li> </ol> </li> </ul> <p> </p> <p> </p> <p> </p>
Rainfall data monitored by acoustic sensors in Zurich and Milan during spring and summer 2022
<p>The database contains rainfall information obtained from acoustic sensors and rain gauges (meteoblue AG) in the cities of Zurich (Switzerland) and Milan (Italy) during field work conducted in spring and summer 2022.</p> <p>Zurich:</p> <p>Continuous rainfall data is provided at 15 min intervals for April 2022; data_acoustic_Zurich.csv - number of rain drops, data_meteoblue.csv - rainfall depth (mm).</p> <p>Milan:</p> <p>Data is provided for 5 rain events in June 2022 at 1 min intervals; data_acoustic_Milan.csv - number of rain drops, data_meteoblue.csv - rainfall depth (mm).</p> <p>The locations of the acoustic sensors and rain gauges can be find in the metadata files: Metadata_acoustic.xlsx and Metadata_meteoblue.xlsx</p> <p>The presented-data passed only a primilinary quality control.</p> <p>Further infromation about the senor networks in Milan and Zurich can be found here: https://doi.org/10.5194/nhess-2022-257</p>
Drone onboard multi-modal sensor dataset
<p><strong>Drone onboard multi-modal sensor dataset :</strong></p> <p>This dataset contains timeseries data from numerous drone flights. Each flight record has a unique identifier (uid) and a timestamp indicating when the flight occurred. The drone's position is represented by the coordinates (position_x, position_y, position_z) and altitude. The orientation of the drone is represented by the quaternion (orientation_x, orientation_y, orientation_z, orientation_w). The drone's velocity and angular velocity are represented by (velocity_x, velocity_y, velocity_z) and (angular_x, angular_y, angular_z) respectively. The linear acceleration of the drone is represented by (linear_acceleration_x, linear_acceleration_y, linear_acceleration_z).</p> <p>In addition to the above, the dataset also contains information about the battery voltage (battery_voltage) and current (battery_current) and the payload attached. The payload information indicates if the drone operated with an embdded device attached (nvidia jetson), various sensors, and a solid-state weather station (trisonica).</p> <p>The dataset also includes annotations for the current state of the drone, including IDLE_HOVER, ASCEND, TURN, HMSL and DESCEND. These states can be used for classification to identify the current state of the drone. Furthermore, the labeled dataset can be used for predicting the trajectory of the drone using multi-task learning.</p> <p>For the annotation, we look at the change in position_x, position_y, position_z and yaw. Specifically, if the position_x,<br> position_y changes, it means that the drone moves in a horizontal straight line, if the position_z changes, it means that the drone performs ascending or descending (depends on whether it increases or decreases), if the yaw changes, it means that the drone performs a turn and finally if any of the above features do not change, it means the drone is in idle or hover mode.</p> <p>In addition to the features already mentioned, this dataset also includes data from various sensors including a weather station and an Inertial Measurement Unit (IMU). The weather station provides information about the weather conditions during the flight. This information includes, wind speed, and wind angle. These weather variables could be important factors that could influence the flight of the drone and battery consumption. The IMU is a sensor that measures the drone's acceleration, angular velocity, and magnetic field. The accelerometer provides information about the drone's linear acceleration, while the gyroscope provides information about the drone's angular velocity. The magnetometer measures the Earth's magnetic field, which can be used to determine the drone's orientation.</p> <p>Field deployments were performed in order to collect empirical data using a specific type of drone, specifically a DJI Matrice 300 (M300). The M300 is equipped with advanced sensors and flight control systems, which can provide high-precision flight data. The flights were designed to cover a range of flight patterns, which include triangular flight patterns, square flight patterns, polygonal flight pattern, and random flight patterns. These flight patterns were chosen to represent a variety of different flight scenarios that could be encountered in real-world applications. The triangular flight pattern consists of the drone flying in a triangular path with a fixed altitude. The square flight pattern involves the drone flying in a square path with a fixed altitude. The polygonal flight pattern consists of the drone flying in a polygonal path with a fixed altitude, and the random flight pattern involves the drone flying in a random path with a fixed altitude. Overall, this dataset contains a rich set of flight data that can be used for various research purposes, including developing and testing algorithms for drone control, trajectory planning, and machine learning.</p> <p> </p>
Gaussian Process Model and Sensor Placement for Detroit Green Infrastructure: Datasets and Code
<ol> <li><strong>code.zip: </strong>Zip folder containing a folder titled "code" which holds: <ol> <li>csv file titled "MonitoredRainGardens.csv" containing the 14 monitored green infrastructure (GI) sites with their design and physiographic features;</li> <li>csv file titled "storm_constants.csv" which contain the computed decay constants for every storm in every GI during the measurement period;</li> <li>csv file titled "newGIsites_AllData.csv" which contain the other 130 GI sites in Detroit and their design and physiographic features;</li> <li>csv file titled "Detroit_Data_MeanDesignFeatures.csv" which contain the design and physiographic features for all of Detroit;</li> <li>Jupyter notebook titled "GI_GP_SensorPlacement.ipynb" which provides the code for training the GP models and displaying the sensor placement results;</li> <li>a folder titled "MATLAB" which contains the following: <ol> <li>folder titled "SFO" which contains the SFO toolbox for the sensor placement work</li> <li>file titled "sensor_placement.mlx" that contains the code for the sensor placement work</li> <li>several .mat files created in Python for importing into Matlab for the sensor placement work: "constants_sigma.mat", "constants_coords.mat", "GInew_sigma.mat", "GInew_coords.mat", and "R1_sensor.mat" through "R6_sensor.mat"</li> <li>several .mat files created in Matalb for importing into Python for visualizing the results: "MI_DETselectedGI.mat" and "DETselectedGI.mat"</li> </ol> </li> </ol> </li> </ol>
Vibration-based smart sensor for high flow dust measurement
<p><strong>Abstract:</strong> Drying process of aggregates needed for asphalt manufacturing involves a high quantity of dust or filler that needs to be heated and extracted with the aid of a baghouse. A sensor that is able to measure the amount of filler aspirated will be a relevant innovation as the current state of the art for drying of aggregates involves a high amount of energy to heat all the aggregates so the highest amount of dust or filler is extracted. The final step of asphalt production is to mix all the components like bitumen, aggregates and cold filler itself. In the context of European project CAPRI [1,2], it is presented a prototype for measurement of filler flow based on vibration analysis, inside the pipe with an accelerometer in the insulator of an existing thermocouple subjected to the hard conditions of temperature and pressure. The paper shows the laboratory prototype results together with preliminary onsite evaluation previously to final demonstration. The paper provides also open access to all the data and results used as part of the commitment of CAPRI project with open science.</p> <p><strong>Keywords:</strong> Sensors, Innovation, Process Industry, Automation, Industry 4.0, Digital Transformation, Industrial Plants, Filler, Dust, Vibration, Signal processing, Smart sensing.</p>
Water quality data from Talkpool sensor
<p>Talkpool installed water quality sensors measuring temperature, conductivity, pH and turbidity in recipients receiving wast water from construction sites to be able to monitor the influence of waste water from construction sites on water quality in those recipients. Sensors are installed both upstream and downstream from the discharge point to be able to measure the effect of the waste water.</p>
Soil moisture and climate data from SmartCityTrees sensors in Amersfoort
<p>Within the frame of the SCOREwater project, the City of Amersfoort commissioned <a href="https://hoefakker.com/boomspecialisten/smart-city-bodemvochtsensor/">Hoefakker</a> to install Teneo soil moisture and climate monitor sensors at several locations in the Schothorst neighbourhood and the Central Railway area. These sensors have been branded as "SmartCityTrees" by Hoefakker. The sensors measure soil moisture, temperature and humidity. Schothorst and the Central Railway area differ in groundwater levels. In Schothorst the groundwater levels are higher (average height: 0.7 meter to 1.0 meter below ground level) than in the Central Railway area (average height: lower than 1.6 meter below ground level). The lowest soil moisture sensors are placed on 1.2 meter below ground level. As a result, in the Schothorst area the sensors are located close to or in the groundwater during winter. In the Central Railway area they are located far above the groundwater level. This makes both areas interesting to include. What all soil moisture sensors have in common is that they are all located nearby trees and in public spaces. Locations differ in terms of: being in the sun or in the shade, being in a green setting (unpaved, such as parks) or being in a paved setting, and being near surface water or not. Because of the differences between the locations the sensors have been installed in, data from the sensors can be used to investigate questions such as:</p> <ul> <li>What is the influence of the type of surface on soil moisture levels?</li> <li>Does the nearby presence of surface water affect soil moisture?</li> <li>What is the influence of heat on soil moisture?</li> <li>What is the relation between groundwater levels fluctuance and soil moisture?</li> <li>Are adjustments on in public spaces (on street level) helpful to improve the soil situation for a more climate adaptive city?</li> </ul> <p>The soil moisture dataset contains soil moisture VWC (volumetric water content, the ratio of water volume to soil volume). This is a percentage represented as a number between 0 and 1. 0.73 for example is 73%.</p> <p>The climate dataset contains temperature in degrees Celsius and the relative humidity. Relative humidity is a percentage represented as a number between 0 and 1 as well.</p> <p>Time period: from 2021-01-01 to 2022-12-31.</p>
Dataset for 'Room-temperature monitoring of CH4 and CO2 using a metal-organic framework-based QCM sensor showing inherent analyte discrimination'
<p>Associated data for the manuscript 'Room-temperature monitoring of CH4 and CO2 using a metal-organic framework-based QCM sensor showing inherent analyte discrimination' (doi://10.26434/chemrxiv-2023-djhp2)</p> <p> </p> <p> </p>
Water quality data from s::can sensors in the Barcelona sewer system
<p>Within the frame of the SCOREwater project, BCASA and s::can installed water quality sensors in the sewer system in three neighbourhoods with different socio-economic characteristics (Poblenou, Sant Gervasi and Carmel) in the City Of Barcelona. To prevent vandalism, the exact location of the sensors cannot be disclosed. The sensors are monitoring physico-chemical parameters in the sewer network. These data can be used for multiple purposes, both related to predictive maintenance of the sewer network and life style analysis of inhabitants of Barcelona:</p> <ul> <li>a better operation and maintenance of the sewer network</li> <li>minimizing odor episodes and corrosion from H2S</li> <li>try to prevent blocking from sediments</li> <li>detect spills into the sewer system from a construction site or illegal discharge</li> <li>learn population habits from analyzing the waste water from the three different neighborhoods</li> <li>to learn about how the inhabitants use pharmaceuticals or other compounds (perhaps abusing of it).</li> </ul>
FRUC multiple sensor forest dataset including absolute, map-referenced localization
<p><strong>FRUC Datasets (Forest environment dataset)</strong></p> <p>This dataset was collected as part of the work conducted by the Forestry Robotics @ University of Coimbra team (<a href="https://www.youtube.com/@forestryroboticsuc">https://www.youtube.com/@forestryroboticsuc</a>; part of the Institute of Systems and Robotics, <a href="https://www.isr.uc.pt/">https://www.isr.uc.pt/</a>) within the scope of the Safety, Exploration and Maintenance of Forests with Ecological Robotics (SEMFIRE, ref. CENTRO-01-0247-FEDER-03269; <a href="http://semfire.ingeniarius.pt/">http://semfire.ingeniarius.pt/</a>) and the Semi-Autonomous Robotic System for Forest Cleaning and Fire Prevention (SafeForest, CENTRO-01-0247-FEDER-045931) research projects. Its purpose is to allow researchers in forestry robotics to have an in-depth analysis of a florests environment; obtain an a priori map for robot operations (e.g. path plannning, landscaping, etc…) and to train segmentation algorithms;</p> <p> </p> <p>The dataset in question includes data from multiple sensors and absolute, map-referenced localization which can be used to register the sensor data to a fixed coordinate system. It was collected at the <a href="https://www.google.com/maps/place/Mata+Nacional+do+Choupal/@40.2208522,-8.4429989,842m/data=!3m1!1e3!4m6!3m5!1s0xd22f91d7cec3b95:0xb02aedc4d8380d48!8m2!3d40.2222536!4d-8.4438944!16s%2Fm%2F026jw89?hl=pt-PT">Choupal National Woods, Coimbra, Portugal</a> (40<sup>◦</sup>13′13.3′′N;8<sup>◦</sup>26′38.1′′W). The dataset was collected during a partly clouded day in a forest environment by performing <strong>two circular loop</strong> laps amounting to a total distance of approximately <strong>800m,</strong> with a total duration of <strong>14 minutes and 22 seconds</strong>. The scenario is rich in features relevant to forestry robotics applications, including trees, bushes, tree trunks, etc. To better handle the multimodal nature of the acquired data, the dataset is bundled into <a href="http://wiki.ros.org/rosbag">rosbags</a>, a file format used by the <a href="http://wiki.ros.org/">ROS (Robot Operating System)</a> to record and play back data.</p> <p><strong>More specifically, the datasets include:</strong></p> <ul> <li><strong>RGB Images</strong> from an Intel Realsense D435i</li> <li>Aligned <strong>Depth Images</strong> from an Intel Realsense D435i</li> <li>Left and Right Mono Images from a Mynt Eye s1030</li> <li><strong>Point Clouds</strong> from a Livox Mid-70 LiDAR</li> <li>Unfiltered <strong>acceleration, gyroscopic and magnetic</strong> data from a Xsens MTi IMU</li> <li>Unfiltered <strong>acceleration, gyroscopic </strong>data from an Intel Realsense D435i</li> <li><strong>GNSS Fix data</strong> from a Xiaomi Mi Mix 3 device</li> </ul> <p><strong>Description of files:</strong></p> <ol> <li>The dataset is contain in <strong>choupal.bag</strong>.</li> <li>The <strong>rosbag_info.txt </strong>contains the information of each rosbag;</li> <li>The <strong>sensor_box.urdf </strong>contains all the required transforms;</li> <li>The <strong>sensor_box.stl</strong> contains the 3D model of the apparatus;</li> <li>The <strong>choupal.launch </strong>publishes the sensor transforms and plays the dataset;</li> <li>The <strong>localization.bag</strong> contains the final graph of poses extracted with Cartographer republished as nav_msgs/odom at 4.98Hz.</li> <li>The <strong>localization_15Hz.bag</strong> contains a map-referenced localization extracted with Cartographer at a higher frequency, but the poses are interpolated. If you don't require a high frame rate, please use the <strong>localization.bag</strong> instead.</li> </ol> <p><strong>Usage:</strong></p> <ol> <li>Extract the <em>fruc_dataset_choupal_launch.zip </em>into a catkin workspace</li> <li>Install the necessary dependencies of the package: <ol> <li> <pre><code class="language-bash">cd [/path/to/catkin_ws]</code></pre> <p> </p> </li> <li> <pre><code class="language-bash">rosdep install --from-paths src --ignore-src -y -r</code></pre> </li> </ol> </li> <li>Copy the <strong>rosbags </strong>into the <em>fruc_dataset_choupal_launch/rosbag/</em></li> <li>Edit the <em>fruc_dataset_choupal_launch/launch/choupal.launch </em>file to your use case: <ol> <li>Change the <em>file_path </em>argument if the rosbags are not in the default location;</li> <li>Set <em>localization_file</em> to <em> </em>the path of the desired localization bag, leave it empty to run the dataset without localization.</li> </ol> </li> <li>Compile the package and source the environment: <ol> <li> <pre><code class="language-bash">catkin_make [/your_catkin_workspace/]</code></pre> <p> </p> </li> <li> <pre><code class="language-bash">source [/your_catkin_workspace/devel/setup.bash]</code></pre> <p> </p> </li> </ol> </li> <li>Launch the files: <pre><code class="language-bash">roslaunch fruc_dataset_choupal_launch choupal.launch</code></pre> </li> </ol>
HRV-ACC: a dataset with R-R intervals and accelerometer data for the diagnosis of psychotic disorders using a Polar H10 wearable sensor
<p><strong>ABSTRACT</strong></p> <p>The issue of diagnosing psychotic diseases, including schizophrenia and bipolar disorder, in particular, the objectification of symptom severity assessment, is still a problem requiring the attention of researchers. Two measures that can be helpful in patient diagnosis are heart rate variability calculated based on electrocardiographic signal and accelerometer mobility data. The following dataset contains data from 30 psychiatric ward patients having schizophrenia or bipolar disorder and 30 healthy persons. The duration of the measurements for individuals was usually between 1.5 and 2 hours. R-R intervals necessary for heart rate variability calculation were collected simultaneously with accelerometer data using a wearable Polar H10 device. The Positive and Negative Syndrome Scale (PANSS) test was performed for each patient participating in the experiment, and its results were attached to the dataset. Furthermore, the code for loading and preprocessing data, as well as for statistical analysis, was included on the corresponding GitHub repository.</p> <p><strong>BACKGROUND</strong></p> <p>Heart rate variability (HRV), calculated based on electrocardiographic (ECG) recordings of R-R intervals stemming from the heart's electrical activity, may be used as a biomarker of mental illnesses, including schizophrenia and bipolar disorder (BD) [Benjamin et al]. The variations of R-R interval values correspond to the heart's autonomic regulation changes [Berntson et al, Stogios et al]. Moreover, the HRV measure reflects the activity of the sympathetic and parasympathetic parts of the autonomous nervous system (ANS) [Task Force of the European Society of Cardiology the North American Society of Pacing Electrophysiology, Matusik et al]. Patients with psychotic mental disorders show a tendency for a change in the centrally regulated ANS balance in the direction of less dynamic changes in the ANS activity in response to different environmental conditions [Stogios et al]. Larger sympathetic activity relative to the parasympathetic one leads to lower HRV, while, on the other hand, higher parasympathetic activity translates to higher HRV. This loss of dynamic response may be an indicator of mental health. Additional benefits may come from measuring the daily activity of patients using accelerometry. This may be used to register periods of physical activity and inactivity or withdrawal for further correlation with HRV values recorded at the same time.</p> <p><strong>EXPERIMENTS</strong></p> <p>In our experiment, the participants were 30 psychiatric ward patients with schizophrenia or BD and 30 healthy people. All measurements were performed using a Polar H10 wearable device. The sensor collects ECG recordings and accelerometer data and, additionally, prepares a detection of R wave peaks. Participants of the experiment had to wear the sensor for a given time. Basically, it was between 1.5 and 2 hours, but the shortest recording was 70 minutes. During this time, evaluated persons could perform any activity a few minutes after starting the measurement. Participants were encouraged to undertake physical activity and, more specifically, to take a walk. Due to patients being in the medical ward, they received instruction to take a walk in the corridors at the beginning of the experiment. They were to repeat the walk 30 minutes and 1 hour after the first walk. The subsequent walks were to be slightly longer (about 3, 5 and 7 minutes, respectively). We did not remind or supervise the command during the experiment, both in the treatment and the control group. Seven persons from the control group did not receive this order and their measurements correspond to freely selected activities with rest periods but at least three of them performed physical activities during this time. Nevertheless, at the start of the experiment, all participants were requested to rest in a sitting position for 5 minutes. Moreover, for each patient, the disease severity was assessed using the PANSS test and its scores are attached to the dataset.</p> <p>The data from sensors were collected using Polar Sensor Logger application [Happonen]. Such extracted measurements were then preprocessed and analyzed using the code prepared by the authors of the experiment. It is publicly available on the GitHub repository [Książek et al].</p> <p>Firstly, we performed a manual artifact detection to remove abnormal heartbeats due to non-sinus beats and technical issues of the device (e.g. temporary disconnections and inappropriate electrode readings). We also performed anomaly detection using Daubechies wavelet transform. Nevertheless, the dataset includes raw data, while a full code necessary to reproduce our anomaly detection approach is available in the repository. Optionally, it is also possible to perform cubic spline data interpolation. After that step, rolling windows of a particular size and time intervals between them are created. Then, a statistical analysis is prepared, e.g. mean HRV calculation using the RMSSD (Root Mean Square of Successive Differences) approach, measuring a relationship between mean HRV and PANSS scores, mobility coefficient calculation based on accelerometer data and verification of dependencies between HRV and mobility scores.</p> <p><strong>DATA DESCRIPTION</strong></p> <p>The structure of the dataset is as follows. One folder, called <em>HRV_anonymized_data</em> contains values of R-R intervals together with timestamps for each experiment participant. The data was properly anonymized, i.e. the day of the measurement was removed to prevent person identification. Files concerned with patients have the name <em>treatment_X.csv</em>, where <em>X</em> is the number of the person, while files related to the healthy controls are named <em>control_Y.csv</em>, where <em>Y</em> is the identification number of the person. Furthermore, for visualization purposes, an image of the raw RR intervals for each participant is presented. Its name is <em>raw_RR_{control,treatment}_N.png</em>, where <em>N</em> is the number of the person from the control/treatment group. The collected data are raw, i.e. before the anomaly removal. The code enabling reproducing the anomaly detection stage and removing suspicious heartbeats is publicly available in the repository [Książek et al]. The structure of consecutive files collecting R-R intervals is following:</p> <table> <tbody> <tr> <td><strong>Phone timestamp</strong></td> <td><strong>RR-interval [ms]</strong></td> </tr> <tr> <td>12:43:26.538000</td> <td>651</td> </tr> <tr> <td>12:43:27.189000</td> <td>632</td> </tr> <tr> <td>12:43:27.821000</td> <td>618</td> </tr> <tr> <td>12:43:28.439000</td> <td>621</td> </tr> <tr> <td>12:43:29.060000</td> <td>661</td> </tr> <tr> <td>...</td> <td>...</td> </tr> </tbody> </table> <p>The first column contains the timestamp for which the distance between two consecutive R peaks was registered. The corresponding R-R interval is presented in the second column of the file and is expressed in milliseconds. <br> The second folder, called <em>accelerometer_anonymized_data</em> contains values of accelerometer data collected at the same time as R-R intervals. The naming convention is similar to that of the R-R interval data: <em>treatment_X.csv </em>and <em>control_X.csv</em> represent the data coming from the persons from the treatment and control group, respectively, while <em>X </em>is the identification number of the selected participant. The numbers are exactly the same as for R-R intervals. The structure of the files with accelerometer recordings is as follows:</p> <table> <tbody> <tr> <td><strong>Phone timestamp</strong></td> <td><strong>X [mg]</strong></td> <td><strong>Y [mg]</strong></td> <td><strong>Z [mg]</strong></td> </tr> <tr> <td>13:00:17.196000</td> <td>-961</td> <td>-23</td> <td>182</td> </tr> <tr> <td>13:00:17.205000</td> <td>-965</td> <td>-21</td> <td>181</td> </tr> <tr> <td>13:00:17.215000</td> <td>-966</td> <td>-22</td> <td>187</td> </tr> <tr> <td>13:00:17.225000</td> <td>-967</td> <td>-26</td> <td>193</td> </tr> <tr> <td>13:00:17.235000</td> <td>-965</td> <td>-27</td> <td>191</td> </tr> <tr> <td>...</td> <td>...</td> <td>...</td> <td>...</td> </tr> </tbody> </table> <p>The first column contains a timestamp, while the next three columns correspond to the currently registered acceleration in three axes: X, Y and Z, in milli-g unit.</p> <p>We also attached a file with the PANSS test scores (<em>PANSS.csv</em>) for all patients participating in the measurement. The structure of this file is as follows:</p> <table> <tbody> <tr> <td><strong>no_of_person</strong></td> <td><strong>PANSS_P</strong></td> <td><strong>PANSS_N</strong></td> <td><strong>PANSS_G</strong></td> <td><strong>PANSS_total</strong></td> </tr> <tr> <td>1</td> <td>8</td> <td>13</td> <td>22</td> <td>43</td> </tr> <tr> <td>2</td> <td>11</td> <td>7</td> <td>18</td> <td>36</td> </tr> <tr> <td>3</td> <td>14</td> <td>30</td> <td>44</td> <td>88</td> </tr> <tr> <td>4</td> <td>18</td> <td>13</td> <td>27</td> <td>58</td> </tr> <tr> <td>...</td> <td>...</td> <td>...</td> <td>...</td> <td>..</td> </tr> </tbody> </table> <p><br> The first column contains the identification number of the patient, while the three following columns refer to the PANSS scores related to positive, negative and general symptoms, respectively.</p> <p><strong>USAGE NOTES</strong></p> <p>All the files necessary to run the HRV and/or accelerometer data analysis are available on the GitHub repository [Książek et al]. HRV data loading, preprocessing (i.e. anomaly detection and removal), as well as the calculation of mean HRV values in terms of the RMSSD, is performed in the <em>main.py</em> file. Also, Pearson's correlation coefficients between HRV values and PANSS scores and the statistical tests (Levene's and Mann-Whitney U tests) comparing the treatment and control groups are computed. By default, a sensitivity analysis is made, i.e. running the full pipeline for different settings of the window size for which the HRV is calculated and various time intervals between consecutive windows. Preparing the heatmaps of correlation coefficients and corresponding p-values can be done by running the <em>utils_advanced_plots.py</em> file after performing the sensitivity analysis. Furthermore, a detailed analysis for the one selected set of hyperparameters may be prepared (by setting <em>sensitivity_analysis = False</em>), i.e. for 15-minute window sizes, 1-minute time intervals between consecutive windows and without data interpolation method. Also, patients taking quetiapine may be excluded from further calculations by setting <em>exclude_quetiapine = True</em> because this medicine can have a strong impact on HRV [Hattori et al].</p> <p>The accelerometer data processing may be performed using the <em>utils_accelerometer.py</em> file. In this case, accelerometer recordings are downsampled to ensure the same timestamps as for R-R intervals and, for each participant, the mobility coefficient is calculated. Then, a correlation coefficient between mean HRV values and mobility coefficient is computed. The plotting of the pure accelerometer signal may be done by running the <em>utils_loading.py </em>file.</p> <p>The comparison of age distribution between the tested groups can be made by the histogram plotted with the use of the <em>utils_basic_plots.py</em> file.</p>
Time series of high-frequency sensors measuring water temperature and dissolved oxygen at discrete depths in Falling Creek Reservoir, Virginia, USA in 2012-2018
We measured water temperature and dissolved oxygen at multiple depths in Falling Creek Reservoir (Vinton, Virginia, USA) with high-frequency (10 to 15-minute) sensors for different durations during 2012 to 2018. Falling Creek Reservoir is owned and managed by the Western Virginia Water Authority as a primary drinking water source for Roanoke, Virginia. All measurements were collected at discrete depths at the deepest site of the reservoir adjacent to the dam. The sensors consisted of: 1) InsiteIG dissolved oxygen and water temperature sensors (Model 20 dissolved oxygen sensor) at both 1 m (November 2015 - December 2018) and 8 m (September 2012 - December 2018) and 2) HOBO (HOBO Pendant Temperature/Light 64K Data Logger) water temperature loggers deployed at 1, 2, 3, 4, 5, 6, 7, 8, and 9.3 m depths (September 2015 - January 2018).
High frequency limnological sensor data from three lakes in the Pocono Mountains region, Pennsylvania USA, 2016-2024
This dataset publication provides access to eight years of high-frequency sensor data from three lakes: Giles, Lacawac, and Waynewood. These lakes are located in the Pocono Mountains region of Pennsylvania, USA and have been the site of long-term monitoring and research. Lake Giles is a relatively clear-water low dissolved organic matter oligotrophic lake in a largely protected watershed. Lake Lacawac has higher dissolved organic matter concentrations and is considered a dystrophic brown-water system; it is also in a highly-protected watershed. Lake Waynewood is a relatively productive eutrophic lake with a larger watershed that is mixed agricultural, forested, and residential use. High-frequency sensors were deployed on sensor lines at the deepest point in each lake. Measurements included temperature and dissolved oxygen through the water column, fluorescent dissolved organic matter at the surface and bottom, and chlorophyll fluorescence at the surface of each lake. These data are collected at a frequency of 10 to 30 minutes and are available in the data packages GilesHighFrequencyData.csv, LacawacHighFrequencyData.csv, and WaynewoodHighFrequencyData.csv. Data from weather stations located adjacent to each lake can be found in the data package PoconosWeatherStationData.csv. Additional long-term limnological data (four decades) for Lakes Giles, Lacawac, and Waynewood are available in the data package edi.186.8.
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.