Skip to main content
Powered by ShareScore

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.

57

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

57 results for “motion capture”

Learn how ShareScore rates datasets ↗
zenodo52/100

THÖR-MAGNI: A Large-scale Indoor Motion Capture Recording of Human Movement and Interaction

<h1>The TH&Ouml;R-MAGNI Dataset Tutorials</h1> <p>TH&Ouml;R-MAGNI datasets is a novel dataset of accurate human and robot navigation and interaction in diverse indoor contexts, building on the previous <a href="https://ieeexplore.ieee.org/abstract/document/8954833/">TH&Ouml;R dataset protocol</a>. We provide position and head orientation motion capture data, 3D LiDAR scans and gaze tracking. In total, TH&Ouml;R-MAGNI captures <strong>3.5 hours of motion of 40 participants on 5 recording days</strong>.</p> <p>This data collection is designed around systematic variation of factors in the environment to allow building cue-conditioned models of human motion and verifying hypotheses on factor impact. To that end, TH&Ouml;R-MAGNI encompasses 5 scenarios, in which some of them have different conditions (i.e., we vary some factor):</p> <ul> <li>Scenario 1 (plus conditions A and B): <ul> <li>&nbsp;Participants move in groups and individually;</li> <li>&nbsp;Robot as static obstacle;</li> <li>&nbsp;Environment with 3 obstacles and lane marking on the floor for <strong>condition B</strong>;</li> </ul> </li> </ul> <ul> <li>&nbsp;Scenario 2: <ul> <li>&nbsp;Participants move in groups, individually and transport objects with variable difficulty (i.e. bucket, boxes and a poster stand);</li> <li>&nbsp;Robot as static obstacle;</li> <li>&nbsp;Environment with 3 obstacles;</li> </ul> </li> </ul> <ul> <li>Scenario 3 (plus conditions A and B): <ul> <li>&nbsp;Participants move in groups, individually and transporting objects with variable difficulty (i.e. bucket, boxes and a poster stand). We denote each role as: <em>Visitors-Alone, Visitors-Group 2, Visitors-Group 3, Carrier-Bucket, Carrier-Box, Carrier-Large Object;</em></li> <li>&nbsp;Teleoperated robot as moving agent: in <strong>condition A</strong>, the robot moves with differential drive; in&nbsp;<strong>condition </strong>B, the robot moves with omni-directional drive;</li> <li>&nbsp;Environment with 2 obstacles;</li> </ul> </li> </ul> <ul> <li>Scenario 4 (plus conditions A and B): <ul> <li>&nbsp;All participants, denoted as <em>Visitors-Alone HRI</em>&nbsp;interacted with the teleoperated mobile robot;</li> <li>&nbsp;Robot interacted in two ways: in <strong>condition A</strong> (Verbal-Only), the Anthropomorphic Robot Mock Driver (ARMoD), a small humanoid NAO robot on top of the mobile platform, only used speech to communicate the next goal point to the participant; in <strong>condition B</strong> the ARMoD used speech, gestures and robotic gaze to convey the same message;</li> <li>&nbsp;Free space environment</li> </ul> </li> </ul> <ul> <li>Scenario 5: <ul> <li>&nbsp;Participants move alone (<em>Visitors-Alone</em>) and one of the participants, denoted as&nbsp;<em>Visitors-Alone HRI</em>, transport objects and interact with the robot;</li> <li>&nbsp;The ARMoD is remotely controlled by an experimenter and proactively offers help;</li> <li>&nbsp;Free space environment;</li> </ul> </li> </ul> <h2>Preliminary steps</h2> <p>Before proceeding, make sure to download the data from ZENODO</p> <h3>1. Directory Structure</h3> <p>├── CLiFF_Maps &lt;- Directory for CLiFF Maps for all files</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── Files &lt;- Directory for the csv files</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── Readme.md</p> <p>├── CSVs_Scenarios &lt;- Directory for aligned data for all scenarios</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── Scenario_1 &lt;- Directory for the csv files for Scenario 1</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── Scenario_2 &lt;- Directory for the csv files for Scenario 2</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── Scenario_3 &lt;- Directory for the csv files for Scenario 3</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── Scenario_4 &lt;- Directory for the csv files for Scenario 4</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── Scenario_5 &lt;- Directory for the csv files for Scenario 5</p> <p>├── docs</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── tutorials.md &lt;- Tutorials document on how to use the data</p> <p>├── Lidar_sample</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; ├── Files &lt;- Directory for sample files</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── 170522_SC3B_1 &lt;- Directory for the pcd files</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── 170522_SC3B_1.csv &lt;- Synchronization file with QTM</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── manual_view_point.json &lt;- json file with manual view point for visualization</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── requirements.txt &lt;- script pip requirements</p> <p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;├── visualize_pcd.py &lt;- script visualize the lidar data</p> <p>&nbsp; &nbsp; &nbsp; &nbsp;├── Readme.md</p> <p>├── maps &lt;- Directory for maps of the environment (PNG files) and offsets (json file)</p> <p>&nbsp; &nbsp; &nbsp; &nbsp;├── offsets.json &lt;- Offsets of the map with respect to the global coordinate frame origin</p> <p>&nbsp; &nbsp; &nbsp; &nbsp;├── {date}_SC{sc_id}_map.png &lt;- Maps for `date` in {1205, 1305, 1705, 1805} and `sc_id` in {1A, 1B, 2, 3}</p> <p>&nbsp; &nbsp; &nbsp; &nbsp;├── 3009_map.png &lt;- Map for the Scenarios 4A, 4B and 5</p> <p>├── MP4_Videos</p> <p>&nbsp; &nbsp; &nbsp; &nbsp;├── Files &lt;- Directory for the mp4 files</p> <p>&nbsp; &nbsp; &nbsp; &nbsp;├── pupil_scene_camera_instrinsics.json &lt;- json file with the intrinsics of pupil camera</p> <p>├── TSVs_RAWET &lt;- Directory for the TSV files for the Raw Eyetracking data for all Scenarios</p> <p>&nbsp; &nbsp; &nbsp; &nbsp;├── synch_info.csv &lt;- Event markers necessary to align motion capture with eyetracking data</p> <p>&nbsp; &nbsp; &nbsp; &nbsp;├── Files &lt;- Directory with all the raw eyetracking TSV files</p> <p>├── goals_positions.csv &lt;- File with the goals locations</p> <p>&nbsp;</p> <h3>2. Data Structure and Dataset Files</h3> <p>Withing each Scenario directory, each csv file contains:</p> <p><strong>2.1. Headers</strong></p> <p>The dataset metadata overview contains important information found in the CSV file headers. This reference is designed to help users understand and use the dataset effectively. The headers include details such as FILE_ID, which provides information on the date, scenario, condition, and run associated with each recording. The header of the document includes important quantities such as the number of frames recorded (N_FRAMES_QTM), the count of rigid bodies (N_BODIES), and the total number of markers (N_MARKERS).</p> <p>It also provides information about the order of the contiguous rotation matrix (CONTIGUOUS_ROTATION_MATRIX), modalities measured with units, and specified measurement units. The text presents details on the eyetracking devices used in each recording, including their infrared sensor and scene camera frequencies, as well as an indication of the presence of eyetracking data.</p> <p>The header provides specific information about rigid bodies, including their names (BODY_NAMES), role labels (BODY_ROLES), and the number of markers associated with each rigid body (BODY_NR_MARKERS). Finally, the table lists all marker names used in the file.</p> <p>This metadata provides researchers and practitioners with essential guidance on recording information, data quantities, and specifics about rigid bodies and markers. It is a valuable resource for understanding and effectively using the dataset in the CSV files.</p> <p><strong>2.2. Trajectory Data</strong></p> <p>The remaining portion of the CSV file integrates merged data from the motion capture system and eye tracking devices, organized based on participants' helmet rigid bodies. Columns within the dataset include XYZ coordinates of all markers, spatial centroid coordinates, 6DOF orientation of the object's local coordinate frame, and&nbsp;<em>if available</em> eye tracking data, encompassing 2D/3D gaze coordinates, scene recording frame numbers, eye movement types, and IMU data.</p> <p>Missing data is denoted by "N/A" or an empty cell. Temporal indexing is facilitated by the "Time" or "Frame" column, indicating timestamps or frame numbers. The motion capture system records at 100Hz, Tobii Glasses at 50Hz (Raw); 25 Hz (Camera), and Pupil Glasses at 100Hz (Raw); 30 Hz (Camera). The dataset is structured around motion capture recordings, and for each rigid body, such as "Helmet_1," details per frame include XYZ coordinates of markers, centroid coordinates, and a 9-element rotational matrix describing helmet orientation.</p> <table> <tbody> <tr> <td><strong>Header</strong></td> <td><strong>Explanation</strong></td> </tr> <tr> <td>Helmet_1 - 1 X</td> <td>X-Coordinate of Marker Number 1</td> </tr> <tr> <td>Helmet_1 - 1 Y</td> <td>Y-Coordinate of Marker Number 1</td> </tr> <tr> <td>Helmet_1 - 1 Z</td> <td>Z-Coordinate of Marker Number 1</td> </tr> <tr> <td>Helmet_1 - [...]</td> <td><em>Same for Marker 2 and 3 of Helmet_1</em></td> </tr> <tr> <td>Helmet_1 Centroid_X</td> <td>X-Coordinate of the Centroid</td> </tr> <tr> <td>Helmet_1 Centroid_Y</td> <td>Y-Coordinate of the Centroid</td> </tr> <tr> <td>Helmet_1 Centroid_Z</td> <td>Z-Coordinate of the Centroid</td> </tr> <tr> <td>Helmet_1 R0</td> <td>1st Element of the CONTIGUOUS_ROTATION_MATRIX</td> </tr> <tr> <td>Helmet_1 R[..]</td> <td>Same for R1- R7</td> </tr> <tr> <td>Helmet_1 R8</td> <td>9th Element of the CONTIGUOUS_ROTATION_MATRIX</td> </tr> </tbody> </table> <p>&nbsp;</p> <p><strong>2.3. Eyetracking Data</strong></p> <p>The eye tracking data in the dataset includes 16 participants, providing a comprehensive dataset of over 500 minutes of recorded data across the different activities and scenarios with three different eyetracking devices. Devices are denoted with a special "Tracker_ID" in the dataset, i.e.:</p> <table> <tbody> <tr> <td><strong>Tracker ID</strong></td> <td><strong>Eyetracking Device</strong></td> </tr> <tr> <td>TB2</td> <td>Tobii 2 Glasses</td> </tr> <tr> <td>TB3</td> <td>Tobii 3 Glasses</td> </tr> <tr> <td>PPL</td> <td>Pupil Insivisible Glasses</td> </tr> </tbody> </table> <p>Gaze points are classified into fixations and saccades using the Tobii I-VT Attention filter, which is specifically optimized for dynamic scenarios with a velocity threshold of 100&deg;. Eyetracking devices were systematically repeated after each 4-minute recording to account for natural variations in participants' eye shapes and to improve the gaze estimation algorithms. In addition, gaze estimation adjustments for the pupil invisible glasses were made after each 4-minute recording to mitigate potential drifts. It's worth noting that the scene cameras of the eye tracking glasses had different fields of view. The scene camera of the Pupil Invisible Glasses had a 1088x1080 image with both horizontal (HFOV) and vertical (VFOV) opening angles of 80&deg;, while the Tobii Glasses provided a 1920x1080 image with different opening angles for Tobii Glasses 3 (HFOV: 95&deg;, VFOV: 63&deg;) and Tobii Glasses 2 (HFOV: 82&deg;, VFOV: 52&deg;).</p> <p><strong>NOTE AS OF 2024:</strong>&nbsp;<strong>Videos are NOW part</strong> of the dataset</p> <p>For one participant, wearing the Tobii Glasses 3 and Helmet_6, the data would be denoted as:</p> <table> <tbody> <tr> <td><strong>Header</strong></td> <td><strong>Explanation</strong></td> </tr> <tr> <td><em>Helmet_6 - [...]</em></td> <td><em>*X,Y,Z Coordinates for 5 markers*</em></td> </tr> <tr> <td><em>Helmet_6 [...]</em></td> <td><em>X,Y,Z Coordinates for 1 Centroid*&nbsp;</em></td> </tr> <tr> <td><em>Helmet_6 R[...]</em></td> <td><em>9 Elements of the CONTIGUOUS_ROTATION_MATRIX</em></td> </tr> <tr> <td> <p>Helmet_6 TB3_Accelerometer_[...]</p> </td> <td>Accelerometer data along the X,Y,Z Axis</td> </tr> <tr> <td>Helmet_6 TB3_Gyroscope_[...]</td> <td>Gyroscope data along the X,Y,Z Axis</td> </tr> <tr> <td>Helmet_6 TB3_Magnetometer_[...]</td> <td>Magnetometer data along the X,Y,Z Axis</td> </tr> <tr> <td>Helmet_6 TB3_G2D_[...]</td> <td>2D Eye tracking data (X,Y)</td> </tr> <tr> <td>Helmet_6 TB3_G3D_[...]</td> <td>3D Cyclopic Eye gaze Vector (X,Y,Z)</td> </tr> <tr> <td>Helmet_6 TB3_Movement</td> <td>Eye movement type (N/A, Fixation or Saccade)</td> </tr> <tr> <td>Helmet_6 TB3_SceneFNr</td> <td>Frame number of the scene camera recording&nbsp;</td> </tr> </tbody> </table> <h2>How to use and tools</h2> <p><a href="https://github.com/tmralmeida/magni-dash/tree/dash-public">magni-dash</a></p> <p><a href="https://magni-dash.streamlit.app">This</a>&nbsp;is a dashboard to quickly visualize our data: trajectories, speeds, eye-tracking data and LiDAR visualization (for Scenario 3). If you cannot use the dashboard from the streamlit cloud service, just run it locally by following the <a href="https://github.com/tmralmeida/magni-dash/tree/dash-public">README File</a>.</p> <p><a href="https://github.com/tmralmeida/thor-magni-tools">thor-magni-tools</a></p> <p>To install and use the package, follow the instructions on the <a href="https://github.com/tmralmeida/thor-magni-tools/blob/main/README.md">README file</a> . This package comprises:</p> <ul> <li>3D trajectory restoration: agents in the scene wore an helmet. The helmet is equipped with markers, which are tracked by the Mocap system. 3D trajectory restoration stands for <a href="https://github.com/tmralmeida/thor-magni-tools/blob/main/thor_magni_tools/preprocessing/cfg.yaml#L3">two different ways</a> of aggregating the trackings of the various markers in each helmet: (1) <em>3D-restoration</em>&nbsp;and (2)&nbsp;<em>3D-best marker</em>. The former applies an average over the locations of all visible markers while the latter uses the marker with highest tracking duration.</li> <li>3D pre-processing of restored trajectories: interpolation, downsampling and smoothing. To run the 3D pre-processing, check <a href="https://github.com/tmralmeida/thor-magni-tools?tab=readme-ov-file#preprocessing#preprocessing">this</a>.</li> <li>trajectory analysis: trajectory-related metrics like tracking duration (in seconds), number of 8s&nbsp;<em>tracklets</em>, motion speed, path efficiency score, and minimal distance between people. To run the trajectory analysis, check <a href="https://github.com/tmralmeida/thor-magni-tools?tab=readme-ov-file#preprocessing#analysis">this</a>.</li> </ul>

opencc-by-4.0Dec 2023View details →
zenodo48/100

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. &nbsp;<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>&nbsp;</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&nbsp; 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>

opencc-by-4.0May 2022View details →
zenodo44/100

IMU and marker-based optical motion capture from a humanoid robot

<p>The motion capture contains walking trials from the lower body of the humanoid robot&nbsp;Reem-C from Pal Robotics (Barcelona, Spain). Seven IMUs were attached on the foot, lower leg, upper leg and pelvis segments.&nbsp;IMU data was collected at 100 Hz. Moreover, the robot motion was captured with a marker-based optical system (Qualisys AB, Göteborg, Sweden) at 150 Hz. The focus of the dataset was mainly walking. There are three trials, each with a length of about 6.5 minutes.<br>The dataset contains the definition of the skeleton (segment lengths and coordinate locations), the actual IMU readings and the pose or kinematics from the optical system.</p>

opencc-by-4.0Dec 2023View details →
zenodo44/100

Full Body Motion Capture of Single Individuals Following External Perturbations from Different Directions

<p>This dataset is composed of C3D files corresponding to full body motion of participants undergoing external perturbation at shoulder height with different sensory conditions. The temporal force profiles of the perturbations are also available.</p> <p>The following experiment received ethical approval from an ethics committee and all participants signed an informed consent form relative to the processing of their data.&nbsp;<br>The experiments were carried on 21 healthy young adults (10 females, 11 males). All were between 20 and 38 yo with a mean age of 27.2 (std: 4.2). Mean mass was 70.2 (std: 12.1) kg and height was 1.74 (std: 0.08) m.&nbsp;</p> <p>Participants motion was recorded using 45 reflective markers and a 23 Qualisys camera system (200Hz).&nbsp;<br>The markers were placed on participants following standardised anatomical landmarks.&nbsp;<br>The output signal of the force sensor was processed using a Butterworth low pass filter with a 5Hz cutoff frequency without phase shift.&nbsp;<br>The force sensor was synchronised with the motion capture software.<br>Tree reflective markers were also placed along the pole in order to retrieve the exact direction of the perturbations.&nbsp;</p>

opencc-by-4.0Jan 2024View details →
zenodo44/100

Kuopio gait dataset: motion capture, inertial measurement and video-based sagittal-plane keypoint data from walking trials

<p>This dataset contains motion capture (3D marker trajectories, ground reaction forces and moments), inertial measurement unit (wearable Movella Xsens MTw Awinda sensors on the pelvis, both thighs, both shanks, and both feet), and sagittal-plane video (anatomical keypoints identified with the OpenPose human pose estimation algorithm) data.<br>The data is from 51 willing participants and collected in the HUMEA laboratory in the University of Eastern Finland, Kuopio, Finland, between 2022 and 2023. All trials were conducted barefoot.</p> <p>The file structure contains an Excel file containing information of the participants, data folders under each subject (numbered 01 to 51), and a MATLAB script.</p> <p>The Excel file has the following data for the participants:</p> <ul> <li><strong>ID</strong>: ID of the participants from 1 to 51</li> <li><strong>Age</strong>: age of the participant in years</li> <li><strong>Gender</strong>: biological sex as M for male, F for female</li> <li><strong>Leg</strong>: the participant's dominant leg, identified by asking which foot the participant would use to kick a football; R for right, L for left</li> <li><strong>Height</strong>: height of the participant in centimeters</li> <li><strong>Invalid_trials</strong>: list of invalid trials in the motion capture data (MOCAP) data, usually classified as such because the participant did not properly step on the middle force plate</li> <li><strong>IAD</strong>: inter-asis distance in millimeters, the distance between palpated left and right anterior superior iliac spine, measured with a caliper</li> <li><strong>Left_knee_width</strong>: width of the left knee from medial epicondyle to lateral epicondyle in millimeters, palpated and measured with a caliper</li> <li><strong>Right_knee_width</strong>: same as above for the right knee</li> <li><strong>Left_ankle width</strong>: width of the left ankle from medial malleolus to lateral malleolus in millimeters, palpated and measured with a caliper</li> <li><strong>Right_ankle_width</strong>: same as above for the right ankle</li> <li><strong>Left_thigh_length</strong>: the distance between the greater trochanter of the left femur and the lateral epicondyle of the left femur in millimeters, palpated and measured with a measuring tape</li> <li><strong>Right_thigh_length</strong>: same as above for the right thigh</li> <li><strong>Left_shank_length</strong>: the distance between the medial epicondyle of the femur and the medial malleolus of the tibia in millimeters, palpated and measured with a measuring tape</li> <li><strong>Right_shank_length</strong>: same as above for the right shank</li> <li><strong>Mass</strong>: mass in kilograms, measured on a force plate just before the walking measurements</li> <li><strong>ICD</strong>: inter-condylar distance of the knee of the dominant leg, measured from low-field MRI</li> <li><strong>Left_knee_width_mocap</strong>: distance between reflective MOCAP markers on the medial and lateral epicondyles of the knee in millimeters, measured from a static standing trial; -1 for missing (subject did not have those markers)</li> <li><strong>Right_knee_width_mocap</strong>: same as above for the right knee</li> </ul> <p>The folders under each subject (folders numbered 01 to 51) are as follows:</p> <ul> <li><strong>imu</strong>: "Raw" inertial measurement unit (IMU) data files that can be read with Xsens Device API (included in Xsens MT Manager 4.6, which may be unavailable these days, not sure). You won't need this if you use the data in the imu_extracted folder.</li> <li><strong>imu_extracted</strong>: IMU data extracted from those data files using the Xsens Device API, so you don't have to. <ul> <li>The data is saved as MATLAB structs where the fields are named as a sensor ID (e.g., "B42D48"). The sensor IDs and their corresponding IMU locations are as follows: <ul> <li>pelvis IMU: B42DA3</li> <li>right femur IMU: B42DA2</li> <li>left femur IMU: B42D4D</li> <li>right tibia IMU: B42DAE</li> <li>left tibia IMU: B42D53</li> <li>right foot IMU: B42D48</li> <li>left foot IMU: B42D51 (except for subjects 01 and 02, where left foot IMU has the ID B42D4E)</li> </ul> </li> <li>Some of the data are just zeros as they couldn't be read from these sensors, but under each sensor, the fields "calibratedAcceleration", "freeAcceleration", "time", "rotationMatrix", and "quaternion" contain usable data. <ul> <li>time: Contains time stamps of the measurement at each frame recorded at 100 Hz, so if you remove the first value from all values in the time vector and divide the result by 100, you will get the time in seconds from the beginning of the walking trial.</li> <li>calibratedAcceleration and freeAcceleration: Contain triaxial acceleration data from the accelerometers of the IMU. freeAcceleration is just calibratedAcceleration without the effect of Earth's gravitational acceleration.</li> <li>rotationMatrix: Orientations of the IMU as rotation matrices.</li> <li>quaternion: Orientations of the IMU as quaternions.</li> </ul> </li> </ul> </li> <li><strong>openpose</strong>: Trajectories of the keypoints identified from sagittal plane video frames, saved as json files. <ul> <li>The keypoints are from the BODY_25 model of OpenPose (https://cmu-perceptual-computing-lab.github.io/openpose/web/html/doc/md_doc_02_output.html).</li> <li>Each frame in the video has its own json file.</li> <li>You can use the function in the script "OpenPose_to_keypoint_table.m" in the root folder to read the keypoint trajectories and confidences of all frames in a walking trial into MATLAB tables. The function takes as argument the path to the folder containing the json files of the walking trial.</li> </ul> </li> <li>Note that some subjects (11, 14, 37, 49) do not have keypoint and IMU data.</li> </ul> <p>The folders under each subject are divided into three ZIP archives with 17 subjects each.</p> <p>The script "OpenPose_to_keypoint_table.m" is a MATLAB script for extracting keypoint trajectories and confidences from JSON files into tables in MATLAB.</p> <p><br><strong>Publication in Data in Brief</strong>: <a href="https://doi.org/10.1016/j.dib.2024.110841" target="_blank" rel="noopener">https://doi.org/10.1016/j.dib.2024.110841</a></p> <p><br><strong>Contact</strong>: Jere Lavikainen, jere.lavikainen@uef.fi</p>

opencc-by-4.0Jan 2024View details →
zenodo44/100

Context-Aware Activity Recognition in Logistics (CAARL) – A optical marker-based Motion Capture Dataset

<p><strong>CAARL </strong>is a&nbsp;freely accessible logistics-dataset for human activity recognition, which contains human movement and context&nbsp;information from two subjects. The context information includes the positions of&nbsp;objects such as two picking carts, a packaging table, different racks, a base and three entrances.</p> <p>In the &rsquo;Innovationlab Hybrid Services in Logistics&rsquo; at TU Dortmund University, two picking and one packing scenarios were recorded using an optical marker based motion capture system. Each subject and object is equipped with several markers. 140&nbsp;minutes of human movements have been labelled and categorised into 8&nbsp;activity classes and 19&nbsp;binary coarse-semantic descriptions, also called attributes. The labelled human movements are synchronised with the context information. They have exactly the same sampling rate (same start and end).</p> <p>The oMoCap data is in csv format. Further formats (e.g. C3D) are available&nbsp;on&nbsp;request.</p> <p>CAARL is based on the set-up and scenarios&nbsp;of the LARa dataset, which contains only human movements. Information about LARa can be found in the dataset and the associated paper:</p> <ul> <li>Dataset: &ldquo;Logistic Activity Recognition Challenge (LARa) &ndash; A Motion Capture and Inertial Measurement Dataset&rdquo;,&nbsp;Zenodo&nbsp;2020,&nbsp;DOI:&nbsp;<a href="https://doi.org/10.5281/zenodo.3862782">10.5281/zenodo.3862782</a></li> <li>Paper: &ldquo;LARa: Creating a Dataset for Human Activity Recognition in Logistics Using Semantic Attributes&rdquo;,&nbsp;Sensors&nbsp;2020,&nbsp;DOI:&nbsp;<a href="https://doi.org/10.3390/s20154083">10.3390/s20154083</a></li> </ul> <p>&nbsp;</p> <p><strong>If you use the CAARL dataset&nbsp;for research, please&nbsp;cite the following paper: &ldquo;Context-Aware Human Activity Recognition in Industrial Processes&rdquo;,&nbsp;Sensors&nbsp;2021,&nbsp;DOI:&nbsp;<a href="https://doi.org/10.3390/s22010134">10.3390/s22010134</a></strong></p>

opencc-by-nc-4.0Nov 2021View details →
zenodo44/100

Motion Capture Benchmark of Industrial Tasks for Ergonomic Assessment and European Historic Crafts

<p><strong>General Info:</strong></p> <p>This benchmark provides motion capture (MoCap) files in .bvh form. The recordings were done in the span of May 2019 to January 2020 for the needs of the&nbsp;<a href="https://collaborate-project.eu/"><strong>CoLLaboratE</strong></a>&nbsp;and <a href="http://www.mingei-project.eu/"><strong>MINGEI</strong></a>&nbsp;H2020 projects<strong>&nbsp;</strong>funded by the European Commission. The tasks included are:</p> <ul> <li>TV assembling</li> <li>Airplane component manufacturing</li> <li>High ergonomic hazard motions&nbsp;</li> <li>Silk-Weaving</li> <li>Glassblowing</li> <li>Mastic Cultivation</li> </ul> <p>The TV assembly and airplane component manufacturing tasks were recorded in real-world conditions inside the factory during the actual production of the items. The high ergonomic hazard motions were recorded in a controlled lab environment and serve as baseline/prototype motions for ergonomic risk assessment.</p> <p>The silk-weaving, glassblowing, and mastic cultivation data sets were created, corresponding to movements performed by skilled craftsmen and mastic farmers. These data sets were produced in order to extract the expert&#39;s gestural knowledge and analyze their dexterity while doing their crafts.</p> <p><strong>Naming Convention:</strong></p> <p>All files in this benchmark follow a strict naming convention to allow for easier parsing by scripts. The names have a total of 12 or 13&nbsp;characters that convey the following information:</p> <ul> <li>The first three or fours&nbsp;characters label the&nbsp;<strong>recording session </strong>(e.g., LAB, PLN, GBBC, MCSN, etc.)</li> <li>The next three characters label the&nbsp;<strong>subject number&nbsp;</strong>(e.g., S01, S02, S03, etc.)</li> <li>The next three characters label the&nbsp;<strong>posture or gesture&nbsp;number&nbsp;</strong>(e.g., P01, P02, G01, G02, etc.)</li> <li>The final three characters label the&nbsp;<strong>repetition number&nbsp;</strong>(e.g., R01, R02, R03, etc.)</li> </ul> <p>For example, LABS02P03R01 denotes a lab recording of the second subject, performing the third posture for the first time.</p> <p><strong>Recording Sessions:</strong></p> <p>There are six recording sessions in this benchmark, the ergonomic risk motion recorded in the lab (denoted as &quot;<strong>LAB</strong>&quot;), the construction of an airplane component (denoted as &quot;<strong>PLN</strong>&quot;), and the assembling and packaging of TVs (denoted as &quot;<strong>TV*</strong>&quot;), the silk weaving&nbsp;(denoted as &quot;<strong>SW*</strong>&quot;), glassblowing&nbsp;(denoted as &quot;<strong>GB*</strong>&quot;), and mastic cultivation&nbsp;(denoted as &quot;<strong>MC*</strong>&quot;).</p> <p>The postures are the following:</p> <p><strong>LAB:</strong></p> <ul> <li><strong>Standing:</strong> <ul> <li><strong>P01</strong>: The subject stays in I-pose</li> <li><strong>P02:</strong>&nbsp;The subject rotates his/her torso to the left as far the person can</li> <li><strong>P03:&nbsp;</strong>The subject will laterally bend his/her torso to the left for 6 seconds</li> <li><strong>P04</strong>: The subject bends more than 20&deg; but less than 60&deg;</li> <li><strong>P05:</strong>&nbsp;The subject bends more than 20&deg; but less than 60&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P06:&nbsp;</strong>The subject stretches his/her arms, and bends forward more than 20&deg; but less than 60&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P07</strong>: The subject bends more than 60&deg;</li> <li><strong>P08:</strong>&nbsp;The subject bends more than 60&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P09:&nbsp;</strong>The subject stretches his/her arms, and bends forward more than 60&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P10:</strong>&nbsp;The subject upright, raises the elbows above the shoulder level with the forearms bent 90&deg; (</li> <li><strong>P11</strong>: The subject raises the elbows above the shoulder level with the forearms bent 90&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P12:</strong>&nbsp;The subject raises the elbows above the shoulder level with the arms stretched while rotating and laterally bending the torso to the left</li> <li><strong>P13:</strong>&nbsp;The subject upright, raises the hands above the head</li> <li><strong>P14:&nbsp;</strong>The subject raises the hands above the head with the arms stretched while rotating and laterally bending the torso to the left</li> </ul> </li> <li><strong>Sitting on a chair:</strong> <ul> <li><strong>P15:&nbsp;</strong>The subject sits upright</li> <li><strong>P16:</strong>&nbsp;The subject bends forward more than 60&deg;</li> <li><strong>P17:</strong>&nbsp;The subject bends forward more than 60&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P18:</strong>&nbsp;The subject stretches the arms, and bends forward more than 60&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P19:</strong>&nbsp;The subject raises the hands above the head with arms stretched</li> <li><strong>P20:</strong>&nbsp;The subject raises the hands above the head with the arms stretched while rotating and laterally bending the torso to the left</li> </ul> </li> <li><strong>Kneeling:</strong> <ul> <li><strong>P21:</strong>&nbsp;The subject stays upright</li> <li><strong>P22:</strong>&nbsp;The subject rotates the torso to the left as far he/she can</li> <li><strong>P23:&nbsp;</strong>The subject will laterally bend the torso to the left for 6 seconds</li> <li><strong>P24:</strong>&nbsp;The subject bends more than 60&deg;</li> <li><strong>P25:</strong>&nbsp;The subject bends more than 60&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P26:</strong>&nbsp;The subject stretches the arms, and bends forward more than 60&deg; while rotating and laterally bending the torso to the left</li> <li><strong>P27:&nbsp;</strong>The subject upright, raises the elbows to the shoulder level with the arms stretched</li> <li><strong>P28:</strong>&nbsp;The subject raises the elbows to the shoulder level with the arms stretched while rotating and laterally bending the torso to the left</li> </ul> </li> </ul> <p>The TV assembling tasks are further divided. The subtasks are: packing the TVs on a stack for shipping (denoted as &quot;<strong>TVP</strong>&quot; for medium-sized TVs and &quot;<strong>TVL</strong>&quot; for larger TVs), placing assembling and placing electronic circuit boards on the chassis (denoted as &quot;<strong>TVB</strong>&quot;), and screwing the boards on the TV chassis (denoted as &quot;<strong>TV_</strong>&quot;). Each task is comprised of a number of postures.&nbsp;&nbsp;</p> <p><strong>TV Assembling:</strong></p> <ul> <li><strong>Assembling the board and placing it on the TV chassis (TVB):</strong> <ul> <li><strong>P01:&nbsp;</strong>Reaching high, above the shoulder level, to pick one component</li> <li><strong>P02:&nbsp;</strong>Reaching low, below the knee level, to pick up the second component</li> <li><strong>P03:&nbsp;</strong>Connecting the components and placing the board on the chassis to be screwed</li> </ul> </li> <li><strong>Screwing an electrical circuit board on the TV chassis (TV_) :</strong> <ul> <li><strong>P01:&nbsp;</strong>A screw is placed on a power tool and it is being screwed on the chassis. The process is repeated four times</li> </ul> </li> <li><strong>Preparing TVs for Shipping (TVP &amp; TVL):</strong> <ul> <li><strong>P01:&nbsp;</strong>Placing TVs on a wooden pallet (bottom level)</li> <li><strong>P02:</strong>&nbsp;Preparing to wrap the bottom level with a membrane</li> <li><strong>P03:</strong>&nbsp;Wrapping the bottom level</li> <li><strong>P04:</strong>&nbsp;Placing TVs on top of the bottom level (second level)</li> <li><strong>P05:</strong>&nbsp;Placing TVs on top of the second level (third level)</li> <li><strong>P06:&nbsp;</strong>Wrapping the second level with a plastic membrane</li> <li><strong>P07:</strong>&nbsp;Wrapping the third level with a plastic membrane</li> <li><strong>P08:</strong>&nbsp;Placing TVs on top of the third level (fourth level)</li> <li><strong>P09:</strong>&nbsp;Wrapping the fourth level with a plastic membrane</li> </ul> </li> </ul> <p><strong>Riveting of an airplane floater (PLN):</strong></p> <ul> <li><strong>P01:</strong> Rivet with the pneumatic hammer.</li> <li><strong>P02:</strong> Prepare the pneumatic hammer and grab rivets.&nbsp;</li> <li><strong>P03:</strong> Place the bucking bar to counteract the incoming rivet.</li> </ul> <p>The tasks recorded for silk weaving, glassblowing, and mastic cultivation data sets were segmented by gestures (e.g., G01, G02, etc.) . The tasks recorded for these three data sets are the following:</p> <p><strong>Silk weaving (SW*):</strong></p> <ul> <li>The creation of the punch cards <strong>(SWPC)</strong>.</li> <li>Preparation of the beam <strong>(SWPB)</strong>.</li> <li>Wrapping of the beam <strong>(SWWB)</strong>.</li> <li>Jacquard weaving with small&nbsp;loom <strong>(SWSL)</strong>.</li> <li>Jacquard weaving with medium size loom <strong>(SWML)</strong>.</li> <li>Jacquard weaving with large loom <strong>(SWLL)</strong>.</li> </ul> <p><strong>Glassblowing (GB*):</strong></p> <ul> <li>Beak cutting <strong>(GBBC)</strong>.</li> <li>Blowing and shaping <strong>(GBBS)</strong>.</li> <li>Cervix refining <strong>(GBCR)</strong>.</li> <li>Cord laying&nbsp;<strong>(GBCL)</strong>.</li> <li>Finish details <strong>(GBFD)</strong>.</li> <li>Handle laying <strong>(GBHL)</strong>.</li> <li>Transfer to punty <strong>(GBTP)</strong>.</li> <li>Leg and foot laying&nbsp;<strong>(GBLF)</strong>.</li> </ul> <p><strong>Mastic Cultivation&nbsp;(MC*):</strong></p> <ul> <li>Scrapping with new tool&nbsp;<strong>(MCSN)</strong>.</li> <li>Scrapping with old tool&nbsp;<strong>(MCSO)</strong>.</li> <li>Sweeping <strong>(MCSW)</strong>.</li> <li>Dusting <strong>(MCDU)</strong>.</li> <li>Embroidery&nbsp;A&nbsp;<strong>(MCEA)</strong>.</li> <li>Embroidery&nbsp;B&nbsp;<strong>(MCEB)</strong>.</li> <li>Embroidery with an axe&nbsp;<strong>(MCEX)</strong>.</li> <li>Gathering&nbsp;<strong>(MCGA)</strong>.</li> <li>Harvesting&nbsp;<strong>(MCHA)</strong>.</li> <li>Wiping&nbsp;<strong>(MCWI)</strong>.</li> <li>Shifting A&nbsp;<strong>(MCSA)</strong>.</li> <li>Shifting B&nbsp;<strong>(MCSB)</strong>.</li> <li>Cleaning with the wind&nbsp;<strong>(MCCW).</strong></li> </ul> <p>The motion capture files were processed and segmented with a&nbsp;3D character animation software (MotionBuilder, Autodesk Inc., San Rafael, CA. USA) and&nbsp;exported to Biovision Hierarchy (BVH) files.</p>

opencc-by-4.0Aug 2021View details →
zenodo44/100

Motion Capture Data for Hand Motion Embodiment

<h1>Dataset</h1> <p>A dataset of human manipulation actions recorded with a motion capture system.</p> <p>A Qualisys motion capture system was used to record the data. We tracked individual finger movements as well as the position and orientation of the right hand. Some recordings contain additional markers at the back, shoulder, and elbow. The motion capture setup is explained&nbsp;<a href="https://dfki-ric.github.io/hand_embodiment/motion_capture_setup.html">here</a>.</p> <p>The dataset contains the original recordings of manipulation actions as well as metadata with annotations of relevant parts of the recordings (labels, start, end). Recordings are exported from the Qualisys Track Manager (QTM) as tab-separated value (TSV) files. Metadata is provided in JSON format. Related software is available at <a href="https://github.com/dfki-ric/hand_embodiment">github.com/dfki-ric/hand_embodiment</a>, which also contains code to load and use the dataset.</p> <h1>Publication</h1> <p>This dataset was introduced in the following paper:</p> <p>Alexander Fabisch, Manuela Uliano, Dennis Marschner, Melvin Laux, Johannes Brust, Marco Controzzi: "A Modular Approach to the Embodiment of Hand Motions from Human Demonstrations", Proceedings of IEEE-RAS International Conference on Humanoid Robots 2022.</p> <p>It is available from <a href="https://arxiv.org/abs/2203.02778">arxiv.org</a> as a preprint or from&nbsp;<a href="https://ieeexplore.ieee.org/document/10000165">IEEE</a>.</p> <p>If you use the dataset, please cite the paper as:</p> <blockquote> <p>@INPROCEEDINGS{Fabisch2022,<br>&nbsp; author={Fabisch, Alexander and Uliano, Manuela and Marschner, Dennis and Laux, Melvin and Brust, Johannes and Controzzi, Marco},<br>&nbsp; booktitle={2022 IEEE-RAS 21st International Conference on Humanoid Robots (Humanoids)},&nbsp;<br>&nbsp; title={A Modular Approach to the Embodiment of Hand Motions from Human Demonstrations},&nbsp;<br>&nbsp; year={2022},<br>&nbsp; pages={801--808},<br>&nbsp; doi={10.1109/Humanoids53995.2022.10000165}<br>}</p> </blockquote> <h1>Ethics Approval</h1> <p>Experimental protocols were approved by the ethics committee of the University of Bremen. Written informed consent was obtained from all participants for participation in the study and to publish this dataset.</p> <h1>Origin and Funding</h1> <p>This dataset is provided by the Robotics Innovation Center, DFKI GmbH.</p> <p>This work was supported by the European Commission under the Horizon 2020 framework program for Research and Innovation (project acronym:&nbsp;APRIL, project number: 870142).</p>

opencc-by-4.0Sep 2022View details →
zenodo44/100

DeepDance: Motion capture data of improvised dance (2019)

<p><em>When using this resource, please cite Wallace, B., Nymoen, K., Martin, C.P &amp; T&oslash;ressen, J. DeepDance: Motion capture data of improvised dance (2019) (version 2.0). Zenodo&nbsp;10.5281/zenodo.5838178</em></p> <p><strong>Abstract</strong></p> <p>This dataset comprises full-body motion capture of improvised dance as well as corresponding audio files. 30 dancers were recorded individually, improvising to six different audio files. The motion was captured in units of mm at 240Hz using a Qualisys infra-red optical system. The experiment was carried out at the University of Oslo in October 2019. For each dancer, 3 performances are recorded for each musical piece, resulting in 540 1-minute motion capture files. The dataset was collected for use as training data in deep learning for motion generation. This dataset also includes MATLAB code to visualize the motion capture files.</p> <p>&nbsp;</p> <p><strong>Music</strong></p> <ul> <li>Skarphedinsson, M. Wallace, B. (2019). &ldquo;Song a&rdquo;</li> <li>Skarphedinsson, M. Wallace, B. (2019). &ldquo;Song b&rdquo;</li> <li>Skarphedinsson, M. Wallace, B. (2019). &ldquo;Song c&rdquo;</li> <li>Skarphedinsson, M. Wallace, B. (2019). &ldquo;Song d&rdquo;</li> <li>Skarphedinsson, M. Wallace, B. (2019). &ldquo;Song f&rdquo;</li> <li>LaClair, J. Bounce. Jesse LaClair, (2018) <em>Referenced here as &ldquo;Song e&rdquo;</em></li> </ul> <p>&nbsp;</p> <p><strong>Data Description</strong></p> <p>The following data types are provided:</p> <ul> <li>Motion (marker position): Recorded with Qualisys Track Manager and saved as tab-separated .tsv files.</li> <li>Stimuli: audio .wav files containing 1 minute of the tracks described above.</li> <li>MATLAB script for animating the tsv files. (requires the MoCap Toolbox)</li> </ul> <p>Note: Recordings which contained errors such as missing markers have been replaced by subject 001.&nbsp;</p> <p><strong>Acknowledgements</strong></p> <p>This work was partially supported by the Research Council of Norway through its&nbsp;Centres of Excellence scheme, project number 262762.</p> <p>&nbsp;</p> <p><strong>Conflicts of Interest</strong></p> <p>The authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p> <p>&nbsp;</p>

opencc-by-4.0Jan 2022View details →
zenodo40/100

Evaluating 3D Human Motion Capture using Apple ARKit against the Vicon System: A Dataset

<p><strong>A journal paper which was&nbsp;published in Applied Sciences gives detailed information about the dataset.</strong></p> <p>Reimer, L.M.; Kapsecker, M.; Fukushima, T.; Jonas, S.M. Evaluating 3D Human Motion Capture on Mobile Devices. Appl. Sci. <em>(2022)</em></p> <p><a href="https://www.mdpi.com/2076-3417/12/10/4806">https://www.mdpi.com/2076-3417/12/10/4806</a></p> <p>Please cite the corresponding paper when using the dataset.</p> <p>&nbsp;</p> <p>A dataset containing anonymized exercise data for eight exercises from ten subject. The exercise data was recorded with two iPads 11&quot; (2021 version, Apple Inc., Cupertino, CA, USA) and a Vicon system. The two iPads were positioned frontal and in a 30&deg; angle to the left side of the subject. The Vicon system used 14 cameras and captured the motion using the Full-body Plug-in-gait model.</p> <p>The dataset contains 220 files, 22 per subject. The structure of the dataset contains 10 folders, one per subject. Each folder contains two subfolders: ARKit and Vicon. Each ARKit folder holds two CSV files. Each Vicon folder holds 16 files, two per exercise: a .csv file with the motion data and a .xcp file containing meta data about the recording, including the camera setup and start/stop timestamps.</p> <p>Du to export problems, the ARKit files for the Side View do not always contain all joint data. The upper body joints are only available for three out of the ten subjects for the Side View.</p>

opencc-by-4.0May 2022View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-Figure 11. Accuracy of different method for unseen faces

<p>Table 3 shows the mode detection accuracy of the proposed method and its combination with two other methods (uniform LBP and circular LBP) for different people. The overall accuracy of the proposed procedure is calculated as this way one video is chosen as input, and after mode detection the three aforementioned steps are applied on this video. The obtained feature vectors are given to the neural network and the corresponding labels to each frame are regarded as output. Afterwards, the overall accuracy is calculated from the confusion matrix. However, it should be noted that the expression detection criteria are the observation of a certain number of subsequent similar labels and in the case of observing a limited or sparse number of different labels the final label would not change. Figure 10 and 11 show result of different methods for seen and unseen data respectively. Table 4 shows results for seen data with proposed method and uniform LBP.</p>

opencc-by-4.0Apr 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-

<p>Table 3 shows the mode detection accuracy of the proposed method and its combination with two other methods (uniform LBP and circular LBP) for different people. The overall accuracy of the proposed procedure is calculated as this way one video is chosen as input, and after mode detection the three aforementioned steps are applied on this video. The obtained feature vectors are given to the neural network and the corresponding labels to each frame are regarded as output. Afterwards, the overall accuracy is calculated from the confusion matrix. However, it should be noted that the expression detection criteria are the observation of a certain number of subsequent similar labels and in the case of observing a limited or sparse number of different labels the final label would not change. Figure 10 and 11 show result of different methods for seen and unseen data respectively. Table 4 shows results for seen data with proposed method and uniform LBP.</p>

opencc-by-4.0Apr 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-Figure 9. Results of our facial motion capture system(a,b,c,d)

<p>In test procedures, single video feature vectors consisting of different expressions are given to the neural network and the network produces the corresponding labels for each frame as output. If there is a mode in a video which is not available in the data base, the nearest available mode&#39;s label to this mode is produced. For example, in test3 and test6 videos, the surprise expression (that have been showed with number 7) is recognized as open mouth expression. At the end, considering the certain numbers of subsequent similar labels (at least 10 frames, because the minimum number of one modes&#39; frames is related to &ldquo;rising the eyebrow&rdquo; mode that takes 10 frames), the expressions are detected, and a 3D show of these expressions are represented. For instance, in test8 videos that have been obtained from unseen face, the &ldquo;smiling&rdquo; and &ldquo;open mouth&rdquo; expressions are well recognized, but expressions related to rising the eyebrows are not detected properly and all the corresponding frames to this expression are regarded as normal expression. Figure 9 shows example of generated 3D models.</p>

opencc-by-4.0Apr 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-Figure 8. 3D model of some facial expressions

<p>Face region is separated precisely from video frames by using a segmentation method based on skin color. The depth data corresponding to this separated area is taken for a 3D representation from depth data corresponding to each frame. At the end, a file is prepared for each frame consisting of face points with 6 features: X, Y, depth, red, green and blue color. These data are used for producing a 3D model and a graphical avatar for each frame (Figure 7). Figure 8 shows 3D model of some facial expressions.</p>

opencc-by-4.0May 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-Figure 6. Proposed feed-forward neural network classifier

<p>After the feature extraction stage, neural network is used for classifying the modes. In this study, the utilized expressions are normal, smiling, open mouth, rising the eyebrows, anger and pursing modes. In fact, they are some selective modes for face movements. It should be noted that the modes can be increased but in this case we work with these six modes. This paper used three layers feed-forward neural network (Figure 6). The proposed neural network includes 800 nodes for the input layer (400 nodes for U matrix and 400 nodes for V matrix), 100 nodes for the hidden layer and 6-nodes for output layer. From the collected data 70% are used for training, 15% for validation and the last 15% are used to evaluate the neural network.</p>

opencc-by-4.0Apr 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-Figure 5. Examples of the circular LBP (Huang et al., 2011)

<p>One limitation of the basic LBP operator is that its small 3x3 neighborhood cannot capture dominant features with large scale structures. To deal with the texture at different scales the operator was later generalized to use neighborhoods of different sizes. A local neighborhood is defined as a set of sampling points evenly spaced on a circle which is centered at the pixel to be labeled. The sampling points that do not fall within the pixels are interpolated using bilinear interpolation, thus allowing for any radius and any number of sampling points in the neighborhood. Figure 5 shows some examples of the extended LBP operator where the notation (P, R) denotes a neighborhood of P sampling points on a circle of radius of R.</p>

opencc-by-4.0Apr 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB- Figure 4. An example of the uniform LBP operator (Huang et al., 2011)

<p>The original LBP operator labels the pixels of an image by means of decimal numbers called Local Binary Patterns or LBP codes, which encode the local structure around each pixel. It proceeds thus as illustrated in figure 4: Each pixel is compared with its eight neighbors in a 3x3 neighborhood by subtracting the center pixel value. The resulting strictly negative values are encoded with 0 and the others with 1. A binary number is obtained by concatenating all these binary codes in a clockwise direction starting from the top-left one and its corresponding decimal value is used for labeling. The derived binary numbers are referred to as Local Binary Patterns or LBP codes.</p>

opencc-by-4.0Apr 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-Figure 7. Avatar 3D model generation

<p>Face region is separated precisely from video frames by using a segmentation method based on skin color. The depth data corresponding to this separated area is taken for a 3D representation from depth data corresponding to each frame. At the end, a file is prepared for each frame consisting of face points with 6 features: X, Y, depth, red, green and blue color. These data are used for producing a 3D model and a graphical avatar for each frame (Figure 7). Figure 8 shows 3D model of some facial expressions.</p>

opencc-by-4.0Apr 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-Figure 3. Feature vectors of facial expression in database

<p>&nbsp;Figure 3 shows feature vectors of facial expression of our database. Matrices &lsquo;U&rsquo; and &lsquo;V&rsquo; values that are obtained from this algorithm are used as feature vectors. The &lsquo;U&rsquo; matrix represents the position and the &lsquo;V&rsquo; matrix represents the change of direction. In the following, the proposed method is combined with some other feature extraction methods (LBP uniform approach and LBP circular approach) and the obtained results will be mentioned.</p>

opencc-by-4.0Apr 2018View details →
zenodo40/100

A Facial Motion Capture System Based on Neural Network Classifier Using RGB-D Data-Figure 2. Facial expression recognition in proposed method

<p>In this stage, a video is prepared using the color data captured from Kinect camera. The face region in each frame is obtained from the video using Viola-Jones algorithm (Figure 2). Because of different distance from the Kinect camera, the obtained images from the face must be re-sized, in order to have the same size. At the end, the colored images are converted to gray-scaled images.</p>

opencc-by-4.0Apr 2018View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated 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.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

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.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

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.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

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.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

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.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record