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.
42
datasets available to search
ShareScore release 0.7.1
Dataset results
42 results for “data artifacts”
A Systematic Survey of Datacenter Scheduling: Data Artifacts
<p>This release contains the raw search results of the survey conducted in the paper <em>A Systematic Survey of Datacenter Scheduling</em>. </p>
Data Artifact: Rebasing Microarchitectural Research with Industry Traces
<p>Data Artifact of the paper "Rebasing Microarchitectural Research with Industry Traces", published at the 2023 IEEE International Symposium on Workload Characterization. It includes the original CVP-1 traces used in the paper.</p><p><i>Note</i>: the improved converted traces used in the paper are available at https://doi.org/10.5281/zenodo.10199624.</p><p><i>Abstract</i>: Microarchitecture research relies on performance models with various degrees of accuracy and speed. In the past few years, one such model, ChampSim, has started to gain significant traction by coupling ease of use with a reasonable level of detail and simulation speed. At the same time, datacenter class workloads, which are not trivial to set up and benchmark, have become easier to study via the release of hundreds of industry traces following the first Championship Value Prediction (CVP-1) in 2018. A tool was quickly created to port the CVP-1 traces to the ChampSim format, which, as a result, have been used in many recent works. We revisit this conversion tool and find that several key aspects of the CVP-1 traces are not preserved by the conversion. We therefore propose an improved converter that addresses most conversion issues as well as patches known limitations of the CVP-1 traces themselves. We evaluate the impact of our changes on two commits of ChampSim, with one used for the first Instruction Championship Prefetching (IPC-1) in 2020. We find that the performance variation stemming from higher accuracy conversion is significant.</p>
Forensic Exchange Analysis of Contact Artifacts on Data Hiding Timestamps-ADS Experiment Supplementary Files
<p>Da-Yu Kao is an Associate Professor at the Department of Information Management, Central Police University, Taiwan. He was a detective and forensic police officer at Taiwan's Criminal Investigation Bureau (under the National Police Administration). With a Master's degree in Information Management and a Ph.D. degree in Crime Prevention and Correction, he had led several investigations in cooperation with police agencies from other countries for the past 20 years. He is now the director of Computer Crime Investigation Lab at Central Police University and the webmaster of Cybercrime Investigation and Digital Forensics in the Facebook Group.</p>
A Study of Real-world Data Races in Golang (Artifact)
<p>The concurrent programming literature is rich with tools and techniques for data race detection. Less, however, has been known about real-world, industry-scale deployment, experience, and insights about data races. Golang (Go for short) is a modern programming language that makes concurrency a first-class citizen. Go offers both message passing and shared memory for communicating among concurrent threads. Go is gaining popularity in modern microservice-based systems. Data races in Go stand in the face of its emerging popularity.</p> <p>In this paper, using our industrial codebase as an example, we demonstrate that Go developers embrace concurrency and show how the abundance of concurrency alongside language idioms and nuances make Go programs highly susceptible to data races. <br> Google's Go distribution ships with a built-in dynamic data race detector based on ThreadSanitizer. Dynamic race detectors pose scalability and flakiness challenges; we discuss various software engineering trade-offs to scale this detector to work effectively at scale.</p> <p>We have deployed this detector in our 50-million lines of Go codebase hosting 2100 distinct microservices, found over 2000 data races, fixed over 1000 data races, spanning 790 distinct code patches submitted by 210 unique developers over a six-month period. Based on a detailed investigation of these data race patterns in Go, we make seven high-level observations relating to the complex interplay between the Go language paradigm and data races. </p>
Supporting data for the article "Charge-Induced Artifacts in Nonlocal Spin-Transport Measurements: How to Prevent Spurious Voltage Signals"
<p>Supporting data for the article "Charge-Induced Artifacts in Nonlocal Spin-Transport Measurements: How to Prevent Spurious Voltage Signals"</p> <p>If the design files are used to reproduce the current source, we ask to cite the peer-reviewed publication of our work in any publication in which the adjustable virtual ground feature is used for measurements.</p> <p>We provide the following data and design files:</p> <p>1.) Data used to create each figure both in the main manuscript and the supplementary material in the zip-folder "Data presented in figures".<br> The data is provided in two formats:<br> I.) Raw data in freely accessible file formats such as .dat, .txt, or .csv.<br> II.) Graphically processed data (figures as shown in the publication) in the proprietary file format .opju. Used program: OriginPro 2019</p> <p>2.) LTspice models in the zip-folder "LTspice models". The simulations were conducted with LTspice version XVII(x64).</p> <p>3.) Altium Designer files of the current source in the zip-folder "Altium Designer files".</p> <p>4.) Gerber X2 and NC drill files (dimensions in millimeters) for the manufacturing of the PCB that is used in our project in the zip-folder "Fabrication files". See the readme file in the directory for more information on the fabrication process.</p> <p>5.) A bill of materials.</p>
OpenAlex Topic Classification v1 Model Artifacts and Training Data
<p>This is all data used to train the topic classification model and also the model artifacts to deploy the model. Please see the github repo for more information:</p> <p>https://github.com/ourresearch/openalex-topic-classification</p>
Research data, sources and documents for thesis on Exploring Complexity Metrics for Artifact-Centric Business Process Models
<p>Research data, sources and documents for thesis on Exploring Complexity Metrics for Artifact-Centric Business Process Models This repository contains the supplemental material for the <a href="https://pqdtopen.proquest.com/pubnum/10759956.html">thesis "Exploring Complexity Metrics for Artifact-Centric Business Process Models" by Marin, Mike A., Ph.D., University of South Africa (South Africa), 2017.</a></p>
[opendc-sc18-dataset] A Reference Architecture for Datacenter Scheduling: Data Artifacts
<p>This release contains the data artifacts of the paper A Reference Architecture for Datacenter Scheduling presented at <a href="https://sc18.supercomputing.org/">Supercomputing 2018</a></p> <p>For the paper, experiments have been run on the following traces:</p> <ul> <li><strong>Askalon (W-Eng)</strong> - <code>askalon_workload_ee</code></li> <li><strong>Chronos (W-Ind)</strong> - <code>chronos_exp_noscaler_ca</code></li> </ul> <p>Each of the directories for the traces have the following structure:</p> <ul> <li><strong>/setup.txt</strong><br> This text file describes the trace used for the experiment in addition to the amount of times the experiment was repeated and the amount of warm-up experiments.</li> <li><strong>/setup.json</strong><br> This JSON file describes the topology of the datacenter used in the experiments. Each item represents the identifiers of the resource (here, CPU type) to use in the machine. The available CPU types are (1) Intel i7 (4 cores, 4100 MHz) and (2) Intel i5 (2 cores, 3500 MHz).</li> <li><strong>/trace</strong><br> This directory contains the trace used in the simulation. The trace is stored in the Grid Workload Format. See the <a href="http://gwa.ewi.tudelft.nl/">Grid Workload Archive</a> for more information.</li> <li><strong>/data/experiments.csv</strong><br> A CSV file containing information of all simulations that have been run on the OpenDC platform for this experiment.</li> <li><strong>/data/job_metrics.csv</strong><br> A CSV file containing metrics (NSL, JMS, etc.) for each job that ran during the simulations.</li> <li><strong>/data/stage_measurements.csv</strong><br> A CSV file containing timing measurements for the scheduling stages that ran during the simulations.</li> <li><strong>/data/task_metrics.csv</strong><br> A CSV file containing metrics for each task that ran during the simulations.</li> <li> <p><strong>/data/tasks.csv</strong><br> A CSV file containing information about the tasks (submit time, runtime, etc.) that ran during the simulations as extracted from the traces.</p> <p>Additionally, we describe the format of each data file in the associated metadata file.</p> </li> </ul> <p><strong>Hardware</strong></p> <p>The hardware used for running the experiments is a MacBook Pro with a 2,9 GHz Intel Core i7 processor and 16 GB 2133 MHz LPDDR3 internal memory.</p> <p><strong>Reproduction</strong></p> <p>This section describes the instructions for reproducing the paper results using a provided Docker image. Please make sure you have <a href="https://www.docker.com/">Docker</a> installed and running.</p> <p>For reproduction, you will run the following experiments:</p> <ul> <li><code>askalon_workload_ee</code><br> This is the large experiment of the paper and will take approximately 4 hours to complete similar hardware.</li> <li><code>chronos_exp_noscaler_ca</code><br> This is the smaller experiment of the paper and will take approximately 5 minutes to complete on similar hardware.</li> </ul> <p>The Docker image <a href="https://hub.docker.com/r/atlargeresearch/sc18-experiment-runner/"><code>atlargeresearch/sc18-experiment-runner</code></a> can be used for running the experiments. A volume can be attached to the directory <code>/home/gradle/simulator/data</code> to capture the results of the experiments.</p> <p>Make sure you have, in your current working directory, the following files:</p> <ul> <li><strong>/setup.json</strong><br> This JSON file describes the topology of the datacenter and can be found in this archive at <code>askalon_workload_ee/setup.json</code>.</li> <li><strong>/askalon_workload_ee.gwf</strong><br> This file contains the trace for the Askalon workload. This file can be found in the archive at <code>askalon_workload_ee/trace/askalon_workload_ee.gwf</code>.</li> <li><strong>/chronos_exp_noscaler_ca.gwf</strong><br> This file contains the trace for the Chronos workload. This file can be found in the archive at <code>chronos_exp_noscaler_ca/trace/chronos_exp_noscaler_ca.gwf</code>.</li> </ul> <p>Then, you can start the Askalon experiments as follows:</p> <pre><code>$ docker run -it --rm -v $(pwd):/home/gradle/simulator/data atlargeresearch/sc18-experiment-runner -r 32 -w 4 -s data/setup.json data/askalon_workload_ee.gwf </code></pre> <p>The experiment runner can be configured with the following options</p> <ul> <li><strong>-r</strong>, <strong>--repeat</strong><br> The amount of times to repeat an experiment for each scheduler.</li> <li><strong>-w</strong>, <strong>--warm-up</strong><br> The amount of times to warm-up the simulator for each scheduler.</li> <li><strong>-p</strong>, <strong>--parallelism</strong><br> The number of experiments to run in parallel.</li> <li><strong>--schedulers</strong><br> The list of schedulers to test, separated by spaces. The following schedulers are available: <code>SRTF-BESTFIT</code>, <code>SRTF-FIRSTFIT</code>, <code>SRTF-WORSTFIT</code>, <code>FIFO-BESTFIT</code>, <code>FIFO-FIRSTFIT</code>, <code>FIFO-WORSTFIT</code>, <code>RANDOM-BESTFIT</code>, <code>RANDOM-FIRSTFIT</code>, <code>RANDOM-WORSTFIT</code>.</li> </ul> <p>After the Askalon experiments have been finished, you can start the Chronos experiments. <strong>Make sure</strong> you have a copy of the result files in your directory as the result files will be overwritten.</p> <pre><code>$ docker run -it --rm -v $(pwd):/home/gradle/simulator/data atlargeresearch/sc18-experiment-runner -r 32 -w 4 -s data/setup.json data/chronos_exp_noscaler_ca.gwf </code></pre>
Doctoral Thesis Artifact "User-Centered Tool Design for Data-Flow Analysis"
<p>This artifact contains the evaluation data and source code accompanying the doctoral thesis "User-Centered Tool Design for Data-Flow Analysis" by Lisa Nguyen Quang Do. The artifact contains (1) the survey questions and anonymized answers of the surveys conducted during the thesis, (2) the user study questionnaires, results, and test applications of the user studies conducted for the thesis, (3) the source code of the research prototypes and video demonstrations of their interfaces, and (4) the benchmark suites used for the empirical evaluation of those prototypes.</p>
Companion data artifacts: Technical framework demonstration for deep learning-based wood species classification with advanced sub-μ-CT imaging
<p>This is the companion data artifact collection for the IWAWA paper manuscript by Jannik Stebani, Tim Lewandrowski, Kilian Dremel, Simon Zabler and Volker Haag.It is generally to be used with the visualization and prediction showcases implemented in the Binder notebooks launched from this <a href="https://github.com/stebix/woodnet-showcase" target="_blank" rel="noopener">woodnet-showcase</a> GitHub repository.</p> <p>The artifacts amount to the following:</p> <ol> <li><code>acer-artifact.hdf5</code> : Exemplary <code>(256, 256, 256)</code> subvolume from a <em>Acer pseudoplatanus</em> sub-μ-CT scan</li> <li><code>pinus-artifact.hdf5</code> : Exemplary <code>(256, 256, 256)</code> subvolume from a <em>Pinus sylvestris </em>sub-μ-CT scan</li> <li><code>weights-artifact.pth</code> : Exemplary PyTorch trained weights for a woodnet/deep neural network to demonstrate classification of the above samples</li> </ol>
Fluorescence correlation spectroscopy TCSPC data with and without peak artifacts - PEX5 applied experiment
<p>This is a dataset of Fluorescence Correlation Spectroscopy (FCS) Time-Correlated Single Photon Counting (TCSPC) data with and without peak artifacts. The provenance of the data is recorded in <a href="https://github.com/aseltmann/fluotracify/blob/data/data/exp-220120-correlate-ptu/LabBook-exp-220120-correlate-ptu.org">this file</a> (see a rendered version <a href="https://aseltmann.github.io/fluotracify/data/LabBook-all.html#sec-2-5">here</a>). This parent project (<a href="https://github.com/aseltmann/fluotracify">https://github.com/aseltmann/fluotracify</a>) also contains examples of how to use these models and related Python code.</p> <p>The following connected paper is currently under review and should be cited together with these model versions: <em>Seltmann, A.; Carravilla, P.; Reglinski, K.; Eggeling, E.; Waithe, D. Neural Network Informed Photon Filtering Reduces Artifacts in Fluorescence Correlation Spectroscopy Data. 2023 (currently under review)</em></p> <p><strong>Note on the file formats and notation:</strong></p> <p>"Primary data" refers to the <code>.ptu</code> files, so the actual TCSPC data. "Secondary data" refers to the <code>.pqres</code> files, which are derived files by the proprietary PicoQuant software.</p> <p><strong>Note on sample preparation (from the Supplementary Note of the paper above):</strong></p> <p>The peak artifacts measurements were produced by 20 nM Trypanosoma brucei-PEX5 N-term fused to eGFP in solution, and the corresponding control measurements by 5 nM Homo sapiens-PEX5 N-term fused to eGFP in solution. The detailed sample preparation is described elsewhere. We prepared the samples on #1.5 coverslips mounted on Attofluor Cell Chambers (Thermo Fisher Scientific). We acquired the data on a MicroTime 200 microscope (PicoQuant) equipped with an Olympus UPlanSApo 60× 1.2NA water immersion objective lens and a HydraHarp 400 TCSPC module (PicoQuant). Excitation was achieved with a 488 nm pulsed laser (PicoQuant) with a power of 5 mW measured at the sample plane. We used a 20 nM solution of Alexa Fluor for calibrating the correction collar. One TCSPC measurement had a length of 20 s for PEX5 experiments.</p>
Fluorescence correlation spectroscopy TCSPC data with and without peak artifacts - AlexaFluor 488 applied experiment
<p>This is a dataset of Fluorescence Correlation Spectroscopy (FCS) Time-Correlated Single Photon Counting (TCSPC) data with and without peak artifacts. The provenance of the data is recorded in <a href="https://github.com/aseltmann/fluotracify/blob/data/data/exp-220120-correlate-ptu/LabBook-exp-220120-correlate-ptu.org">this file</a> (see a rendered version <a href="https://aseltmann.github.io/fluotracify/data/LabBook-all.html#sec-2-5">here</a>). This parent project (<a href="https://github.com/aseltmann/fluotracify">https://github.com/aseltmann/fluotracify</a>]) also contains examples of how to use these models and related Python code.</p> <p>The following connected paper is currently under review and should be cited together with these model versions: <em>Seltmann, A.; Carravilla, P.; Reglinski, K.; Eggeling, E.; Waithe, D. Neural Network Informed Photon Filtering Reduces Artifacts in Fluorescence Correlation Spectroscopy Data. 2023 (currently under review)</em></p> <p><strong>Note on the file formats and notation:</strong></p> <p>"Primary data" refers to the <code>.ptu</code> files, so the actual TCSPC data. "Secondary data" refers to the <code>.pqres</code> files, which are derived files by the proprietary PicoQuant software.</p> <p><strong>Note on sample preparation (from the Supplementary Note of the paper above):</strong></p> <p>The peak artifact measurements were produced by mixing 20 nM of the small dye Alexa Fluor 488 (Thermo Fisher Scientific) with 10 μM of slow, large (100 nm) unilamellar vesicles (LUVs) labelled with DiO in the membrane (0.1 % mol lipid:dye). The corresponding control measurements were 20 nM Alexa Fluor 488 in solution. We prepared the LUVs by the extrusion method: 1−palmitoyl−2−oleoyl−glycero−3−phosphocholine (POPC, Avanti Polar Lipids) was vacuum dried on a glass vial for 1 h and resuspended on phosphate buffered saline to form lipid vesicles. The vesicles were extruded 30 times through 100 nm pore size polycarbonate membranes using a Mini-Extruder (Avanti Polar Lipids). We prepared the samples on #1.5 coverslips mounted on Attofluor Cell Chambers (Thermo Fisher Scientific). We acquired the data on a MicroTime 200 microscope (PicoQuant) equipped with an Olympus UPlanSApo 60× 1.2NA water immersion objective lens and a HydraHarp 400 TCSPC module (PicoQuant). Excitation was achieved with a 488 nm pulsed laser (PicoQuant) with a power of 5 mW measured at the sample plane. We used a 20 nM solution of Alexa Fluor for calibrating the correction collar. One TCSPC measurement had a length of 10 s for AF488 experiments.</p>
Fluorescence correlation spectroscopy time-series data with and without peak artifacts - simulated data
<p>This is a dataset of FCS time-series with and without peak artifacts. It was created by 2D Monte Carlo simulations of diffusing particles. The provenance of the data is recorded in <a href="https://github.com/aseltmann/fluotracify/blob/data/data/exp-201231-clustsim/LabBook-exp-201231-clustsim.org">this file</a> (see a rendered version <a href="https://aseltmann.github.io/fluotracify/data/LabBook-all.html#sec-2-2">here</a>). This parent project (<a href="https://github.com/aseltmann/fluotracify">https://github.com/aseltmann/fluotracify</a>]) also contains examples of how to use this data and related Python code to load it.</p> <p>The following connected paper is currently under review and should be cited together with this dataset: Seltmann, A.; Carravilla, P.; Reglinski, K.; Eggeling, E.; Waithe, D. Neural Network Informed Photon Filtering Reduces Artifacts in Fluorescence Correlation Spectroscopy Data. 2023 (currently under review)</p> Data structure inside each .csv file <table><tbody> <tr> <td><header></td> <td> <p>10 to 12 lines, contains metadata</p> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td>...</td> <td>...</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td><source_1></td> <td><target_1a></td> <td><target_1b></td> <td><source_2></td> <td><target_2a></td> <td><target_2b></td> <td>...</td> </tr> <tr> <td> <p>FCS time-series with artifact</p> </td> <td>Artifact time series</td> <td> <p>FCS time series without artifact</p> </td> <td> <p>FCS time series with artifact</p> </td> <td>Artifact time series</td> <td> <p>FCS time-series without artifact</p> </td> <td>...</td> </tr> <tr> <td>...</td> <td>...</td> <td>...</td> <td>...</td> <td>...</td> <td>...</td> <td>...</td> </tr> </tbody> </table> <p> </p>
Raw trace data for GVARP artifact
<p>Raw trace containing ANT-MOC tracing data with 128 GPUs.</p> <div> <div>One should install the gvarp artifact before analyzing this raw trace: <a href="../records/10975567">GVARP-artifact (zenodo.org)</a></div> <div> </div> <div>To analysis the performance variance in this raw trace, one can use the following commands:</div> <div> <pre><code>GVARP_HOME=/path/to/gvarp-artifact VERSION=500_stream_2024_02_15_03_08_20 variance_analysis -i measurement_${VERSION} -o variance_${VERSION} -f python3 ${GVARP_HOME}/scripts/analysis/variance/heatmap.py --input variance_${VERSION} --output heatmap_${VERSION}</code></pre> <p>The analysis results should be presented as a figure (e.g., comm.png) located in the folder heatmap_${VERSION}.</p> </div> </div>
Tomographic data for testing, demonstrating, and developing methods of removing ring artifacts
<p>These tomographic data were used for demonstrating our methods of eliminating ring artifacts published in Optics Express, <em>Nghia T. Vo, Robert C. Atwood, and Michael Drakopoulos, "Superior techniques for eliminating ring artifacts in X-ray micro-tomography," <strong>26</strong>, 28396-28412 (2018)</em><em>. </em>In sinogram, the artifacts appear as straight lines or stripe artifacts. The data have many types of stripe artifacts: full stripes, partial stripes, unresponsive stripes, fluctuating stripes, and blurry stripes. They are very useful for testing and developing methods of removing ring artifacts.</p> <p>Documentation: <a href="https://sarepy.readthedocs.io/">https://sarepy.readthedocs.io/</a></p> <p>Python implementations of these methods:</p> <p><a href="https://github.com/nghia-vo/sarepy">https://github.com/nghia-vo/sarepy</a></p> <p>In Tomopy:</p> <p><a href="https://tomopy.readthedocs.io/en/latest/api/tomopy.prep.stripe.html">https://tomopy.readthedocs.io/en/latest/api/tomopy.prep.stripe.html</a></p> <p>In Savu:</p> <p><a href="http://github.com/DiamondLightSource/Savu/tree/master/savu/plugins/ring_removal">https://github.com/DiamondLightSource/Savu/tree/master/savu/plugins/ring_removal</a></p> <p>In Algotom:</p> <p><a href="https://github.com/algotom/algotom/blob/master/algotom/prep/removal.py">https://github.com/algotom/algotom/blob/master/algotom/prep/removal.py</a> </p>
Data and Analysis Artifacts for Service-Based Evolvability Patterns (Experiment and Metrics)
<p>Two functionally equivalent service-based web-shop systems (one version with selected service-based patterns, one without) were analyzed with a controlled experiment as well as with structural maintainability metrics. This repo contains all analysis artifacts.</p>
Sampling time-dependent artifacts in single-cell genomics studies: scRNA-seq data
<p>Robust protocols and automation now enable large-scale single-cell RNA and ATAC sequencing experiments and their application on biobank and clinical cohorts. However, technical biases introduced during sample acquisition can hinder solid, reproducible results, and a systematic benchmarking is required before entering large-scale data production. Here, we report the existence and extent of gene expression and chromatin accessibility artifacts introduced during sampling and identify experimental and computational solutions for their prevention.</p> <p>This repository contains the expression matrices and Seurat objects associated with the scRNA-seq data of the manuscript: "Sampling time-dependent artifacts in single-cell genomics studies" published in Genome Biology in 2020. The purpose of this repo is to share processed files and metadata for immediate access and reproducibility. The code to analyze it is thoroughly documented at the associated Github repository (https://github.com/massonix/sampling_artifacts).</p>
CoCon: A Data Set on Combined Contextualized Research Artifact Use
<p>CoCon is a large graph data set reflecting the combined use of research artifacts, contextualized in academic publications’ full-text. It comprises 35 k artifacts (data sets, methods, models, and tasks) and 340 k publications.</p> <p>The data set is generated from <a href="https://github.com/paperswithcode/paperswithcode-data">Papers With Code</a> and <a href="https://github.com/IllDepence/unarXive">unarXive</a>.</p> <p>You can find a Python package for loading the data as a NetworkX or Pytorch Geometric graph <a href="https://github.com/IllDepence/contextgraph">in this GitHub repository</a><br> </p>
Data from: Equine leukocyte storage artifacts
Open the record for dataset details and reuse information.
Data from: Application of a 1H brain MRS benchmark dataset to deep learning for out-of-voxel artifacts
Open the record for dataset details and reuse information.
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.