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.
8,924
datasets available to search
ShareScore release 0.9.0
Dataset results
8,924 results for “formation”
Dataset for article: Structure Formation in Tailor-Made Buriti Oil Emulsion During Simulated Digestion
<p><strong>Dataset for publication:</strong></p> <p>Structure Formation in Tailor-Made Buriti Oil Emulsion During Simulated Digestion<br> <em>Rafael V. M. Freire, Linda Hong, Miroslav Peterek, Stéphane Canarelli, Serge Rezzi, Stefan Salentinig</em><br> Advanced Funtional Materials 2023 (DOI 10.1002/adfm.202303854)</p> <p>Setup and conditions for the experiments are described in the experimental section of the published (open access) manuscript.</p> <p>Data description in README.txt file.</p>
Donor-acceptor complex formation by social self-sorting of polycyclic aromatic hydrocarbons and perylene bisimides
<p>Additional data to report <a href="https://doi.org/10.1039/D3CC03704E">https://doi.org/10.1039/D3CC03704E</a></p> <p>Self-assembly versus complexation with polycyclic aromatic hydrocarbon (PAH) guest molecules is studied for a series of perylene bisimides (PBIs). Bulky imide substituents at the PBI guide their self-assembly into dimer aggregates with null-type exciton coupling. Host-guest titration experiments with perylene and triphenylene PAHs afford 1:1 and 1:2 complexes whose properties are studied by single crystal X-ray analysis and UV/Vis and fluorescence spectroscopy.</p>
QUMPHY MIMIC IV Waveform Database PPG formatted
<p>Derivative of the <a href="https://physionet.org/content/mimic4wdb/0.1.0/">MIMIC IV Waveform Database</a> formatted to be suitable for machine learning.</p> <p><strong>Formatting</strong></p> <p>All records are split into intervals of roughly 60 seconds. The parameter values are averaged over each 60 second interval. The PPG signal data are unprocessed, i.e. as in the original dataset. Intervals with PPG signals containing missing data or large constant data are excluded. PPG signals and signal times are truncated to have the same amount of data points for all records.</p> <p>Formatted data are split into 3 different file types, namely <code>*_n.csv</code> containing the averaged parameter values, <code>*_s.npy</code> containing PPG signal data and <code>*_t.npy</code> containing the respective signal measurement times. Moreover, formatted data are split into <code>trainXX_*</code>, <code>validation_*</code> and <code>test_*</code> data files, where the training data <code>trainXX_*</code> are split into multiple files for easier handling.</p> <p>This dataset was created using the following code: <a href="https://gitlab.com/qumphy/wp1-benchmark-data-conversion">https://gitlab.com/qumphy/wp1-benchmark-data-conversion</a></p> <p><strong>Funding</strong></p> <p>The creation of this dataset has been supported by the European Partnership on Metrology programme 22HLT01 QUMPHY. This project (22HTL01 QUMPHY) has received funding from the EMPIR programme cofinanced by the Participating States and from the European Union’s Horizon 2020 research and innovation programme.</p>
Data Release: "LIGO-Virgo-KAGRA's Oldest Black Holes: Probing star formation at cosmic noon with GWTC-3"
<p>This repository contains the data behind the figures presented in v2 of "LIGO-Virgo-KAGRA's Oldest Black Holes: Probing star formation at cosmic noon with GWTC-3" (<a href="https://ui.adsabs.harvard.edu/link_gateway/2023arXiv230715824F/arxiv:2307.15824">arXiv:2307.15824</a>), to appear in ApJL.</p><p>The csv files (in Output.zip) and the h5 files contain the data products. The three Jupyter notebooks include code for plotting the figures and calculating the summary statistics that appear in the paper. </p><p> </p>
Wikibooks-Korpus: Korpusquellen von deutschsprachigen Wikibooks im TEI-Format
<p>Das <a href="https://www.dwds.de/d/korpora/wikibooks">Wikibooks-Korpus</a> auf <a href="http://www.dwds.de">dwds.de</a> enthält Volltexte aus deutschsprachigen Lehr-, Fach- und Sachbüchern von <a href="https://de.wikibooks.org/wiki/Hauptseite">Wikibooks</a> der Wikimedia Foundation auf der Basis des <a href="https://dumps.wikimedia.org/dewikibooks/20250701/">Datenbank-Abzugs vom 1. 7. 2025</a>. Texte aus anderen Seitenarten (Diskussionen etc.) wurden nicht aufgenommen.</p> <p>Das Wikibooks-Korpus wurde nach dem Vorbild des <a href="https://www.dwds.de/d/korpora/wikipedia">Wikipedia-Korpus</a> auf <a href="http://www.dwds.de">dwds.de</a> konzipiert. Es eignet sich damit insbesondere für die Recherche nach lexikographischen Belegen.</p> <p>Verfügbar sind hier die Quellen des Wikibooks-Korpus auf <a href="http://www.dwds.de">dwds.de</a> im XML/TEI-Format als teiCorpus-Datei. Wie die originalen Wikibooks-Artikel stehen sie unter der Lizenz <a href="https://creativecommons.org/licenses/by-sa/4.0/">"Creative Commons Attribution/Share Alike"</a>.</p>
Fungal traits associated with soil organic matter formation, Harvard Forest, Petersham MA, 2020-2023
Soil microbes are a major source of organic residues that accumulate as soil organic matter (SOM), the largest terrestrial reservoir of carbon on Earth. As such, there is growing interest in determining the microbial traits that drive SOM formation and stabilization; however, whether certain microbial traits consistently predict SOM accumulation across different functional pools (e.g., total vs. stable SOM) is unresolved. To address these uncertainties, we incubated individual species of fungi in SOM-free model soils, allowing us to directly relate the physiological, morphological, and biochemical traits of fungi to their SOM formation potentials. We find that the formation of different SOM functional pools is associated with distinct fungal traits, and that ‘multifunctional’ species with intermediate investment across this key grouping of traits (namely, carbon use efficiency, growth rate, turnover rate, and biomass protein and phenol contents) promote SOM formation, functional complexity, and stability. Our results highlight the limitations of categorical trait-based frameworks that describe binary (high/low) trade-offs between microbial traits, instead emphasizing the importance of synergies among microbial traits for the formation of functionally complex SOM.
Brainport, Platooning, platoon formation improvement
<p><strong>Scenario description</strong>:</p> <p>Platoon formation with live traffic light data included in planner.<br> - Enabled live traffic light data included in planner<br> - Not using the Android app<br> - Starting at default locations</p> <p><strong>Session description</strong>:</p> <p>Platoon formation improvement by traffic light data.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, formation improvement by traffic light data
<p><strong>Scenario description</strong>:</p> <p>Platoon formation with live traffic light data included in planner.<br> - Enabled live traffic light data included in planner<br> - Not using the Android app<br> - Starting at default locations<br> - This test was filmed, including the GUI.</p> <p><strong>Session description</strong>:</p> <p>Platoon formation improvement by traffic light data.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, platoon formation feasibility
<p><strong>Scenario description</strong>:</p> <p>Platoon formation only.<br> - Disabled live traffic light data included in planner<br> - Not using the Android app<br> - Starting at default locations</p> <p><strong>Session description</strong>:</p> <p>Platoon formation feasibility</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, formation and platooning without traffic
<p><strong>Scenario description</strong>:</p> <p>Platoon formation and platooning, from Helmond to Eindhoven and back to the Automotive Campus.<br> - Starting in urban area with speed limits of 15 and 30 km/h.<br> - Driving East on the Europaweg with speed limits of 50 and 70 km/h. This includes 3 crossings with traffic lights.<br> - Driving on the the N270, along the Automotive Campus. One crossing with traffic lights, just before the A270.<br> - Driving on the A270 (speed limit 100 km/h). Interrupted by one traffic light.<br> - U-turn at the fly-over or at the end of the A270, to return the same way to the Automotive Campus.</p> <p><strong>Session description</strong>:</p> <p>Platoon formation and platooning, without live traffic light data included in planner.<br> - No live traffic light data available for planner<br> - Driver uses the Android app<br> - Starting at default locations<br> - Platooning (CACC and lane keeping) on the A270 when possible.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, formation and platooning with speed advice
<p><strong>Scenario description</strong>:</p> <p>Platoon formation and platooning, from Helmond to Eindhoven and back to the Automotive Campus.<br> - Starting in urban area with speed limits of 15 and 30 km/h.<br> - Driving East on the Europaweg with speed limits of 50 and 70 km/h. This includes 3 crossings with traffic lights.<br> - Driving on the the N270, along the Automotive Campus. One crossing with traffic lights, just before the A270.<br> - Driving on the A270 (speed limit 100 km/h). Interrupted by one traffic light.<br> - U-turn at the fly-over or at the end of the A270, to return the same way to the Automotive Campus.</p> <p><strong>Session description</strong>:</p> <p>Platoon formation and platooning, without live traffic light data included in planner, but with automatic speed advice.<br> - No live traffic light data available for planner<br> - Driver uses the Android app if Technolution gives a flexible route<br> - Starting at default locations<br> - Platooning (CACC and lane keeping) on the A270 when possible.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, baseline platoon formation without IoT
<p><strong>Scenario description</strong>:</p> <p>Platoon formation and platooning, from Helmond to Eindhoven and back to the Automotive Campus.<br> - Starting in urban area with speed limits of 15 and 30 km/h.<br> - Driving East on the Europaweg with speed limits of 50 and 70 km/h. This includes 3 crossings with traffic lights.<br> - Driving on the the N270, along the Automotive Campus. One crossing with traffic lights, just before the A270.<br> - Driving on the A270 (speed limit 100 km/h). Interrupted by one traffic light.<br> - U-turn at the fly-over or at the end of the A270, to return the same way to the Automotive Campus.</p> <p><strong>Session description</strong>:</p> <p>Baseline of platoon formation and platooning, without any IoT, so no speed advices.<br> - No live traffic light data available for planner<br> - Starting at default locations<br> - Meeting at the location of vehicle2 on the Automotive Campus<br> - Platooning (CACC and lane keeping) on the A270 when possible.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Gini index mean score grain size estimates for Murray formation rocks (Gale crater, Mars) from ChemCam LIBS data (sols 766-1804)
<p>This repository includes main research results from the Journal of Geophysical Research: Planets manuscript entitled <em>"Grain Size Variations in the Murray Formation: Stratigraphic Evidence for Changing Depositional Environments in Gale Crater, Mars"</em>. These datasets were also included as Supplementary tables with the manuscript. Please find the plain language summary of the manuscript and the captions for these datasets below:</p> <p><strong><em>Plain language summary:</em></strong> The lowest exposed rocks of the Murray formation in Gale crater, Mars are interpreted as ancient lake deposits based on <em>Curiosity </em>rover data. However, the duration and temporal variability of this ancient lake is still an open question. Here we characterize the vertical distribution of deposits within the entire Murray formation using new grain size information. Characterizing grain size in rocks provides information about the speed of past fluid flows, which is crucial for interpreting depositional environments. However, measuring grain size in images is rarely possible for martian rocks. Thus, we estimate grain sizes with the Gini Index Mean Score (GIMS), a grain-size proxy that uses ChemCam Laser Induced Breakdown Spectroscopy data. GIMS results indicate that the Murray formation is dominated by rocks with mud-sized grains (i.e., mudstones), suggesting mud-sized grain settled in a low energy lake environment. Mud cracks occur in some of the mudstones, indicating drying periods in a lake. Rocks with sand-sized grains (i.e., sandstones) and cross bedding occur at specific intervals, suggesting episodes with stream channels and wind-blown sand dunes. The dominance of lake deposits interspersed with stream deposits suggests that liquid water was present in Gale crater for tens of thousands to millions of years.</p> <p><strong>Table captions:</strong></p> <p><em>Table S3. </em>All Murray formation targets used in the Gini mean index score (GIMS) analysis (sols 766-1804) with summary information, general grain size estimates from MAHLI and RMI images if known, and G<sub>MEAN </sub>values with associated standard deviation errors. For targets with N/A grain sizes, grains could not be resolved in any of the images, or images were not available. Protrusions in the rocks that are not grains are likely diagenetic nodules or concretions. Targets with G<sub>MEAN</sub>=0.07 have transitional GSRs, indicated by GSR1/GSR2. Targets names are merged in the same cell for those analyses that were taken on the same rock exposure. Next to the target names, the symbol * denotes that the ChemCam target was imaged by the MAHLI, the symbol ** denotes that the dust removal tool was used before the MAHLI image was taken, and ~ signifies that a location close to the ChemCam target was imaged by the MAHLI.</p> <p><em>Table S4</em>. The mean, median, minimum and maximum G<sub>MEAN</sub> and the minimum and maximum grain size regime (GSR) for each locality in the Murray formation.</p>
Brainport, Platooning, formation variation testing
<p><strong>Scenario description</strong>:</p> <p>Platoon formation, starting from different locations, with live traffic light data included in planner.<br> - Enabled live traffic light data included in planner<br> - Not using the Android app<br> - Starting at different locations</p> <p><strong>Session description</strong>:</p> <p>Platoon formation variation testing</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, Platoon formation improvement
<p><strong>Scenario description</strong>:</p> <p>Platoon formation with ONLY AVERAGE traffic light data included in planner.<br> - Disabled live traffic light data included in planner<br> - Planner advices are based on moving average of a certain amount of past traffic light cycles.<br> - Not using the Android app<br> - Starting at default locations</p> <p><strong>Session description</strong>:</p> <p>Platoon formation improvement by traffic light data.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, formation, platooning, speed advice
<p><strong>Scenario description</strong>:</p> <p>Platoon formation and platooning, from Helmond to Eindhoven and back to the Automotive Campus.<br> - Starting in urban area with speed limits of 15 and 30 km/h.<br> - Driving East on the Europaweg with speed limits of 50 and 70 km/h. This includes 3 crossings with traffic lights.<br> - Driving on the the N270, along the Automotive Campus. One crossing with traffic lights, just before the A270.<br> - Driving on the A270 (speed limit 100 km/h). Interrupted by one traffic light.<br> - U-turn at the fly-over or at the end of the A270, to return the same way to the Automotive Campus.</p> <p><strong>Session description</strong>:</p> <p>Platoon formation and platooning, without live traffic light data included in planner, but with automatic speed advice.<br> - No live traffic light data available for planner<br> - Driver uses the Android app if Technolution gives a flexible route<br> - Automatic speed advice also includes reaction to road-side camera-service objects (LDM closed loop)<br> - Automatic speed advice is turned on, so does actuate the vehicle<br> - Vehicle1 is starting at another location in Helmond (#2), vehicle2 at default location (Automotive Campus)<br> - Platooning (CACC and lane keeping) on the A270 when possible.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, platoon formation variation
<p><strong>Scenario description</strong>:</p> <p>Platoon formation with live traffic light data included in planner.<br> - Enabled live traffic light data included in planner<br> - Not using the Android app<br> - Starting at default locations<br> - Used for pieces of the film (to be made)</p> <p><strong>Session description</strong>:</p> <p>Platoon formation variation testing</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, formation and platooning from default locations
<p><strong>Scenario description</strong>:</p> <p>Platoon formation and platooning, from Helmond to Eindhoven and back to the Automotive Campus.<br> - Starting in urban area with speed limits of 15 and 30 km/h.<br> - Driving East on the Europaweg with speed limits of 50 and 70 km/h. This includes 3 crossings with traffic lights.<br> - Driving on the the N270, along the Automotive Campus. One crossing with traffic lights, just before the A270.<br> - Driving on the A270 (speed limit 100 km/h). Interrupted by one traffic light.<br> - U-turn at the fly-over or at the end of the A270, to return the same way to the Automotive Campus.</p> <p><strong>Session description</strong>:</p> <p>Platoon formation and platooning, without live traffic light data included in planner, but with automatic speed advice.<br> - No live traffic light data available for planner<br> - Driver uses the Android app if Technolution gives a flexible route<br> - Starting at default locations<br> - Platooning (CACC and lane keeping) on the A270 when possible.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Brainport, Platooning, formation and platooning, with speed advice
<p><strong>Scenario description</strong>:</p> <p>Platoon formation and platooning, from Helmond to Eindhoven and back to the Automotive Campus.<br> - Starting in urban area with speed limits of 15 and 30 km/h.<br> - Driving East on the Europaweg with speed limits of 50 and 70 km/h. This includes 3 crossings with traffic lights.<br> - Driving on the the N270, along the Automotive Campus. One crossing with traffic lights, just before the A270.<br> - Driving on the A270 (speed limit 100 km/h). Interrupted by one traffic light.<br> - U-turn at the fly-over or at the end of the A270, to return the same way to the Automotive Campus.</p> <p><strong>Session description</strong>:</p> <p>Platoon formation and platooning, without live traffic light data included in planner, but with automatic speed advice.<br> - No live traffic light data available for planner<br> - Driver uses the Android app if Technolution gives a flexible route<br> - Vehicle1 is starting at another location in Helmond (#2), vehicle2 at default location (Automotive Campus)<br> - Platooning (CACC and lane keeping) on the A270 when possible.</p> <p><strong>Datasets descriptions</strong>:</p> <p><strong>AUTOPILOT_BrainPort_Platooning_DriverVehicleInteraction</strong>: Data extracted from the CAN of the vehicle</p> <p>This dataset contains e.g. throttlestatus, clutchstatus, brakestatus, brakeforce, wipersstatus, steeringwheel for the vehicle</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsAbsolute</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with absolute coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_EnvironmentSensorsRelative</strong>: Data extracted from the vehicle environment sensors</p> <p>This dataset contains information about detected object, with relative coordinates</p> <p><strong>AUTOPILOT_BrainPort_Platooning_IotVehicleMessage</strong>: Data sent between all devices, vehicles and services</p> <p>Each sensor data submission is a Message. A Message has an Envelope, a Path, and optionally (but likely) Path Events and optionally Path Media. The envelope bears fundamental information about the individual sender (the vehicle) but not to a level that owner of the vehicle can be identified or different messages can be identified that originate from a single vehicle.</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonFormation</strong>: Data sent from PlatoonService to vehicle</p> <p>This dataset contains information about the route and speed for a specific vehicle for forming a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningAction</strong>: Data logged by vehicle</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatooningEvent</strong>: Data logged by vehicle</p> <p>This dataset contains information about the identifiers used for each specific platooning event</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PlatoonStatus</strong>: Data sent by vehicle to PlatoonService</p> <p>This dataset contains information about the current status of the platooning</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystem</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed, longitude, latitude, heading from the GPS</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PositioningSystemResample</strong>: Data from GPS on the vehicle</p> <p>This dataset contains speed,longitude,latitude,heading from the GPS, resampled to 100 milliseconds</p> <p><strong>AUTOPILOT_BrainPort_Platooning_PSInfo</strong>: Data sent by PlatoonService to the vehicle</p> <p>This dataset contains speed and route information for the vehicle to create a platoon</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Target</strong>: Data from sensors on the vehicle</p> <p>Target detection in the vicinity of the host vehicle, by a vehicle sensor or virtual sensor</p> <p><strong>AUTOPILOT_BrainPort_Platooning_Vehicle</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o temperature and battery state of the vehicles</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p> <p><strong>AUTOPILOT_BrainPort_Platooning_VehicleDynamics</strong>: Data from the CAN and sensors about the state of the vehicle</p> <p>This dataset contains a.o accelerations and speedlimit of the vehicle, as observed from the CAN and the external sensors</p>
Aerial view of part of the Bisti badlands from an elevation of approximately 8500 feet. Exposed here are the Upper Cretaceous Fruitland and Kirtland Formations. Photograph taken the morning of 13 April 1992. Copyright © Paul L. Sealey. 1992. in Stratigraphy, paleontology and age of the Fruitland and Kirtland Formations (upper Cretaceous), San Juan Basin, New Mexico
Aerial view of part of the Bisti badlands from an elevation of approximately 8500 feet. Exposed here are the Upper Cretaceous Fruitland and Kirtland Formations. Photograph taken the morning of 13 April 1992. Copyright © Paul L. Sealey. 1992.
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.