Skip to main content
ConductScienceScienceDex
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.

62

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

62 results for “open source dataset”

Learn how ShareScore rates datasets ↗
zenodo40/100

5G Campus Network QoS Dataset for Open-Source gNB Implementations

<p>This 5G campus network dataset contains 6 distinct CSV files.<br>Three for each of the testbeds located at either the Norwegian University of Science and Technology(NTNU) or the University of Wuerzburg(WUE).<br>all_Packets: contains all One-Way-Delay measurement packets. Columns: &nbsp;src, Timestamp, SourceIPOuter, DestinationIPOuter, SourceIPInner, DestinationIPInner, PacketSize, SeqNum, iat, trel, gnb, sdr, bw, slots, ratio, pdist, piat, psize, pnpak, rep, scenario, direction<br>Packets_with_IATs: contains all One-Way-Delay measurement packets, with the Interarrival-times already calculated and added as column. Columns: src, Timestamp, SourceIPOuter, DestinationIPOuter, SourceIPInner, DestinationIPInner, PacketSize, SeqNum, iat, trel, gnb, sdr, bw, slots, ratio, pdist, piat, psize, pnpak, rep, scenario, direction<br>all_Throughput: contains all output information from the throughput measurements conducted with iperf3. Columns: &nbsp;mbpsactual_uplink, mbpsactual_downlink, meanjitterms_uplink, meanjitterms_downlink, meanloss_uplink, meanloss_downlink, gnb, sdr, bw, slots, ratio, mbpsoffered_uplink, mbpsoffered_downlink, rep, scenario</p> <p>src: Source Device<br>Timestamp: Timestamp from wireshark<br>SourceIPOuter: Source IP of the outer GTP packet<br>DestinationIPOuter: Destination IP of the outer GTP packet<br>SourceIPInner: Source IP of the inner GTP packet<br>DestinationIPInner: Destination IP of the inner GTP packet<br>PacketSize: Size of the packet<br>SeqNum: Sequence number injected during traffic generation<br>iat: Interarrival-time of the packet<br>trel: relative timestamp<br>gnb: gNB implementation used<br>sdr: SDR used<br>bw: configured bandwidth<br>slots: configured DL slots<br>ratio: configured DL:UL ratio<br>pdist: chosen distribution of the packet generation (deterministic/negative-exponential time between transmission of the generated packets)<br>piat: chosen interarrival -time during packet generation<br>psize: chosen packet size mode<br>pnpak: total amount of packets generated for this measurement run<br>rep: repetition of measurement<br>scenario: measurement scenario<br>direction: direction of traffic</p> <p>mbpsactual_uplink: actual uplink throughput in MBps<br>mbpsactual_downlink: actual downlink throughput in MBps<br>meanjitterms_uplink: actual uplink jitter in ms<br>meanjitterms_downlink: actual downlink jitter in ms<br>meanloss_uplink: mean loss in uplink<br>meanloss_downlink: mean loss in downlink<br>mbpsoffered_uplink: configured uplink throughput in MBps<br>mbpsoffered_downlink: configured downlink throughput in MBps</p> <p>This dataset stems from the Paper "Parameterizing 5G New Radio: A Comparative Measurement Study on Throughput and Delay"&nbsp;</p>

opencc-by-4.0Sep 2024View details →
zenodo40/100

Dataset of the paper "Self-Admitted Technical Debt Practices: A Comparison Between Industry and Open-Source"

<p>This repository contains the dataset of the manuscript &quot;Self-Admitted Technical Debt Practices: A Comparison Between Industry and Open-Source&quot; accepted in the Empirical Software Engineering Journal, edited by Springer</p>

opencc-by-4.0Jul 2021View details →
zenodo40/100

Dataset for "Open access books through open data sources: Assessing prevalence, providers, and preservation"

<p>This dataset contains the raw collected data reported on in the manuscript titled &quot;Open access books through open data sources:&nbsp; Assessing prevalence, providers, and preservation&quot; which is available here: https://doi.org/10.5281/zenodo.7305490</p> <p>One file contains the results of the digital object identifier queries, and the other data on which publication records were found to be included in which of the studied bibliometric data sources, and preservation services.</p> <p>The author is grateful to Alicia Wise and Ronald Snijder for assisting in the identification of available datasets and valuable feedback throughout the study.</p> <p>This research was commissioned by CLOCKSS, DOAB, and OAPEN.</p>

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

KeyNet: An Open Source Dataset of Key Bittings

<p>This repository introduces a dataset of obverse and reverse images of 319 unique Schlage SC1 keys, labeled with each key&#39;s bitting code.&nbsp;</p> <p>We make our data accessible in an HDF5 format, through arrays aligned where the Nth index of each array represents the Nth key, with keys sorted ascending by bitting code:</p> <ul> <li><code>/bittings</code>: Each keys 1-9 bitting code, recorded from shoulder through the tip of the key,&nbsp;<code>uint8</code>&nbsp;of shape&nbsp;(319,5).</li> <li><code>/obverse</code>: Obverse image of each key,&nbsp;<code>uint8</code>&nbsp;of shape&nbsp;(319,512,512,3).</li> <li><code>/reverse</code>: Reverse image of each key,&nbsp;<code>uint8</code>&nbsp;of shape&nbsp;(319,512,512,3).</li> </ul> <p>Full dataset details available on <a href="https://github.com/alexxke/keynet">GitHub</a></p>

opencc-by-4.0Mar 2023View details →
zenodo40/100

Quality Assurance Awareness in Open Source Software Projects on GitHub Analysis Dataset

<p>Dataset for the paper &quot;Quality Assurance Awareness in Open Source Software Projects on GitHub&quot;, submitted to the 23rd IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM), 2023.</p>

opencc-by-4.0Jul 2023View details →
zenodo36/100

Open-source software collaboration network mining dataset

<p>The resulting dataset of the <a href="https://github.com/gotec/git2net">git2net </a>and <a href="https://github.com/wschuell/repo_tools">repo_tools </a>mining process for randomly selected large open-source repositories.</p>

opencc-by-4.0Jun 2021View details →
zenodo36/100

Dataset: A continuous open source data collection platform for architectural technical debt assessment

<p>The dataset and replication package of the study &quot;A continuous open source data collection platform for architectural technical debt assessment&quot;.</p> <p>&nbsp;</p> <p>Abstract</p> <p>Architectural decisions are the most important source of technical debt.&nbsp; In recent years, researchers spent an increasing amount of effort investigating this specific category of technical debt, with quantitative methods, and in particular static analysis, being the most common approach to investigate such a topic.</p> <p>&nbsp;</p> <p>However, quantitative studies are susceptible, to varying degrees, to external validity threats, which hinder the generalisation of their findings.</p> <p>In response to this concern, researchers strive to expand the scope of their study by incorporating a larger number of projects into their analyses. This practice is typically executed on a case-by-case basis, necessitating substantial data collection efforts that have to be repeated for each new study.</p> <p>&nbsp;</p> <p>To address this issue, this paper presents our initial attempt at tackling this problem and enabling researchers to study architectural smells at large scale, a well-known indicator of architectural technical debt. Specifically, we introduce a novel approach to data collection pipeline that leverages Apache Airflow to continuously generate up-to-date, large-scale datasets using Arcan, a tool for architectural smells detection (or any other tool).</p> <p>Finally, we present the publicly-available dataset resulting from the first three months of execution of the pipeline, that includes over 30,000 analysed commits and releases from over 10,000 open source GitHub projects written in 5 different programming languages and amounting to over a billion of lines of code analysed.</p>

opencc-by-4.0Oct 2023View details →
zenodo36/100

GloHydroRes - a global dataset combining open-source hydropower plant and reservoir data

<div> <div> <div> <div>&nbsp;</div> </div> </div> </div> <div> <div> <div> <div> <div> <div> <p>Analyzing the impacts of drought and climate change on hydropower requires detailed data not only on hydropower attributes such as plant type, head, and installed capacity, but also on reservoir characteristics like area, depth, and volume. Current open-source hydropower datasets typically lack information on reservoirs, while reservoir datasets often omit hydropower details. GloHydroRes is a global dataset that integrates open-source hydropower and reservoir data, offering 29 attributes, including key information such as installed capacity, plant type, dam height, reservoir depth, area, volume, and river name. Overall, GloHydroRes provides data on 7,775 hydropower plants across 128 countries.</p> </div> </div> </div> </div> <div> <div> <div>&nbsp;</div> </div> </div> </div> </div>

opencc-by-4.0Sep 2024View details →
zenodo36/100

E2EGit: A Dataset of End-to-End Web Tests in Open Source Projects

<p><strong>ABSTRACT&nbsp;</strong><br>End-to-end (E2E) testing is a software validation&nbsp;approach that simulates realistic user scenarios throughout&nbsp;the entire workflow of an application. In the context of web<br>applications, E2E testing involves two activities: Graphic User&nbsp;Interface (GUI) testing, which simulates user interactions with&nbsp;the web app&rsquo;s GUI through web browsers, and performance&nbsp;testing, which evaluates system workload handling. Despite its&nbsp;recognized importance in delivering high-quality web applications, the availability of large-scale datasets featuring real-world&nbsp;E2E web tests remains limited, hindering research in the field.<br>To address this gap, we present E2EGit, a comprehensive&nbsp;dataset of non-trivial open-source web projects collected on&nbsp;GitHub that adopt E2E testing. By analyzing over 5,000 web repositories across popular programming languages (JAVA,&nbsp;JAVASCRIPT, TYPESCRIPT, and PYTHON), we identified 472 repositories implementing 43,670 automated Web GUI tests with&nbsp;popular browser automation frameworks (SELENIUM, PLAYWRIGHT, CYPRESS, PUPPETEER), and 84 repositories that featured 271 automated performance tests implemented leveraging&nbsp;the most popular open-source tools (JMETER, LOCUST). Among&nbsp;these, 13 repositories implemented both types of testing for a total&nbsp;of 786 Web GUI tests and 61 performance tests.</p> <p><br><strong>DATASET DESCRIPTION&nbsp;</strong><br>The dataset is provided as an SQLite database,&nbsp;whose structure is illustrated in Figure 3 (in the paper), which consists of&nbsp;five tables, each serving a specific purpose.<br>The <em>repository </em>table contains information on 1.5 million&nbsp;repositories collected using the SEART tool on May 4. It&nbsp;includes 34 fields detailing repository characteristics. The<br><em>non_trivial_repository</em> table is a subset of the previous one, listing repositories that passed the two filtering stages described in the pipeline. For each repository, it specifies whether it is a web repository using JAVA, JAVASCRIPT, TYPESCRIPT, or PYTHON frameworks. A repository may use multiple frameworks, with corresponding fields (e.g., is web java) set to true, and the field web dependencies listing the detected web&nbsp;frameworks. For Web GUI testing, the dataset includes two&nbsp;additional tables; <em>gui_testing_test _details</em>, where each row represents a test file, providing the file path, the browser&nbsp;automation framework used, the test engine employed, and the&nbsp;number of tests implemented in the file. <em>gui_testing_repo_details</em>, aggregating data from the previous table at the repository&nbsp;level. Each of the 472 repositories has a row summarizing<br>the number of test files using frameworks like SELENIUM or&nbsp;PLAYWRIGHT, test engines like JUNIT, and the total number&nbsp;of tests identified. For performance testing, the <em>performance_testing_test_details</em> table contains 410 rows, one for each test identified. Each row includes the file path, whether the test uses JMETER or LOCUST, and extracted details such as the number of thread groups, concurrent users, and requests. Notably, some fields may be absent&mdash;for instance, if external files (e.g., CSVs defining workloads) were unavailable, or in the case of Locust tests, where parameters like duration and concurrent users are specified via the command line.</p> <p><strong>To cite this article refer to this citation:</strong></p> <p>@inproceedings{di2025e2egit,<br>&nbsp; title={E2EGit: A Dataset of End-to-End Web Tests in Open Source Projects},<br>&nbsp; author={Di Meglio, Sergio and Starace, Luigi Libero Lucio and Pontillo, Valeria and Opdebeeck, Ruben and De Roover, Coen and Di Martino, Sergio},<br>&nbsp; booktitle={2025 IEEE/ACM 22nd International Conference on Mining Software Repositories (MSR)},<br>&nbsp; pages={10--15},<br>&nbsp; year={2025},<br>&nbsp; organization={IEEE/ACM}<br>}<br><br>This work has been partially supported by the Italian PNRR MUR project PE0000013-FAIR.&nbsp;</p>

opencc-by-4.0Nov 2024View details →
zenodo36/100

An Empirical Study on the Usage and Availability of Machine Learning Libraries in Open-Source Python Projects - Dataset

<p>This repository contains the dataset of the manuscript:</p> <p>&quot;An Empirical Study on the Usage and Availability of Machine Learning Libraries in Open-Source Python Projects&quot;</p>

opencc-by-4.0Dec 2021View details →
zenodo36/100

Dvoice : An open source dataset for Automatic Speech Recognition on African Languages and Dialects

<p>DVoice is a community initiative that aims to provide African languages and dialects with data and models to facilitate their use of voice technologies. The lack of data on these languages makes it necessary to collect data using methods that are specific to each language. Two different approaches are currently used: the DVoice platform, which is based on Mozilla Common Voice, for collecting authentic recordings from the community, and transfer learning techniques for automatically labeling the recordings. The DVoice platform currently manages 7 languages including Darija (Moroccan Arabic dialect) whose dataset appears on this version, Wolof, Mandingo, Serere, Pular, Diola and Soninke. The Swahili-labeled data present in this version was obtained after automatic labeling via the learning transfer of the Voxlingua107 dataset. For a first time, we also advocate for the increase of data given their small size that we currently have. Thus this version of the dataset contains easily identifiable augmented data.</p>

opencc-by-4.0Mar 2022View details →
zenodo36/100

Reproducible Evaluation of Open-Source Tools for Prostate Segmentation on Public Datasets

<p>Segmentation of the prostate and surrounding regions is important for a variety of clinical and research applications. Our goal is to evaluate the generalizability of publicly available state-of-the-art AI models on publicly available datasets. To compare the AI generated segmentations to the available manually annotated ground-truth, quantitative measures such as Dice Coefficient and Hausdorff distance, along with shape radiomics features, were analyzed. Our study also aims to show how cloud-based tools can be used to analyze, store, and visualize evaluation results.<strong>&nbsp;</strong></p> <p>Three open-source pre-trained AI prostate segmentation tools were evaluated against expert annotations, on three publicly available MRI prostate collections, available in NCI Imaging Data Commons[1]. Two pre-trained models originate from the nnU-Net framework[2], the last pre-trained model originates from Prostate158 paper[4]. ProstateX[5], QIN-Prostate-Repeatability[6] and PROSTATE-MRI-US-Biopsy[7]. Expert annotations of the the whole prostate gland, peripheral zone (PZ) and transition zone (TZ) of the prostate&nbsp; are available for ProstateX collection, whole prostate gland and PZ for&nbsp; QIN-Prostate-Repeatability collection, and whole prostate gland for PROSTATE-MRI-US-Biopsy collection.</p> <p>We rely on the DICOM standard to encode our segmentation and radiomics results. The DICOM standard aims to achieve interoperability and FAIR[10] principles. Encoding our results in DICOM representation allows us to leverage DICOM-reliant tools, such as Google Cloud Computing tools for storage,computation, analysis and visualization. Open-source DICOM-based visualization tools such as OHIF[8] viewer can also be used to look qualitatively at the AI and expert annotations and the referenced images.. DICOM Segmentation objects are used to encode the AI models predictions, using dcmqi[11], DICOM Structured Reports on the other hand are used to encode radiomics features[3] extracted from the AI and expert annotations, using dcmqi and highdicom[12].&nbsp;&nbsp;</p> <p>This dataset is organized in three parts:&nbsp;</p> <p>AI_SEGMENTATIONS_DICOM.zip, AI_STRUCTURED_REPORTS_DICOM.zip and EXPERT_SRUCTURED_REPORTS_DICOM..zip. All zip files contain DICOM objects only, sorted based on DICOM attributes, following this pattern:</p> <p>PatientID/<br>&nbsp;&nbsp;&nbsp;&nbsp;└───Modality-%StudyInstanceUID/<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; └───%SeriesInstanceUID-%SeriesDescription.dcm.</p> <p>AI_SEGMENTATIONS_DICOM.zip contains all the pre-trained AI models evaluated segmentation results, encoded as DICOM Segmentation objects. AI_STRUCTURED_REPORTS_DICOM..zip contains firstorder and shape radiomics features extracted for the AI segmentation results, such as Segmentation Volume, encoded as DICOM Structured Reports. EXPERT_SRUCTURED_REPORTS_DICOM.zip contains firstorder and shape radiomics features extracted for the expert annotations (for ProstateX, QIN-Prostate-Repeatability and PROSTATE-MRI-US-Biopsy collections) stored a DICOM Structured Reports objects.</p> <p>Code repository containing evaluation cloud-based notebooks and results/metadata .csv tables is available here:<br><a href="https://github.com/ImagingDataCommons/idc-prostate-mri-analysis">https://github.com/ImagingDataCommons/idc-prostate-mri-analysis</a></p> <h2>Additional Notes</h2> <p><strong>&nbsp;</strong>This project has been funded in whole or in part with Federal funds from the NCI, NIH, under task order no. HHSN26110071 under contract no. HHSN261201500003l.<br>https://portal.imaging.datacommons.cancer.gov/</p> <p>nnU-Net: <a href="https://github.com/MIC-DKFZ/nnUNet">https://github.com/MIC-DKFZ/nnUNet</a> <br>Prostate158: <a href="https://github.com/Project-MONAI/model-zoo/tree/dev/models/prostate_mri_anatomy">https://github.com/Project-MONAI/model-zoo/tree/dev/models/prostate_mri_anatomy</a><br>Pyradiomics: <a href="https://github.com/AIM-Harvard/pyradiomics">https://github.com/AIM-Harvard/pyradiomics</a> <br>Highdicom: <a href="https://github.com/herrmannlab/highdicom">https://github.com/herrmannlab/highdicom</a> <br>DCMQI: <a href="https://github.com/QIICR/dcmqi">https://github.com/QIICR/dcmqi</a> <br>Github repo: <a href="https://github.com/ImagingDataCommons/idc-prostate-mri-analysis">https://github.com/ImagingDataCommons/idc-prostate-mri-analysis</a></p> <h2>Related information</h2> <p>ProstateX - <a href="https://doi.org/10.7937/K9TCIA.2017.MURS5CL">https://doi.org/10.7937/K9TCIA.2017.MURS5CL </a><br><br>QIN-Prostate-Repeatability - <a href="https://doi.org/10.7937/K9/TCIA.2018.MR1CKGND">https://doi.org/10.7937/K9/TCIA.2018.MR1CKGND</a><br><br>PROSTATE-MRI-US-BIOPSY -&nbsp;<a href="https://doi.org/10.7937/TCIA.2020.A61IOC1A">https://doi.org/10.7937/TCIA.2020.A61IOC1A</a></p> <h2>References&nbsp;</h2> <p>[1] Fedorov A, Longabaugh WJ, Pot D, Clunie DA, Pieper S, Aerts HJ, Homeyer A, Lewis R, Akbarzadeh A, Bontempi D, Clifford W. NCI imaging data commons. Cancer research. 2021 Aug 8;81(16):4188.</p> <p>[2] Isensee F, Jaeger PF, Kohl SA, Petersen J, Maier-Hein KH. nnU-Net: a self-configuring method for deep learning-based biomedical image segmentation. Nature methods. 2021 Feb;18(2):203-11.</p> <p>[3] Van Griethuysen JJ, Fedorov A, Parmar C, Hosny A, Aucoin N, Narayan V, Beets-Tan RG, Fillion-Robin JC, Pieper S, Aerts HJ. Computational radiomics system to decode the radiographic phenotype. Cancer research. 2017 Nov 1;77(21):e104-7.</p> <p>[4] Adams, Lisa C., Marcus R. Makowski, G&uuml;nther Engel, Maximilian Rattunde, Felix Busch, Patrick Asbach, Stefan M. Niehues, et al. 2022. &ldquo;Prostate158 - An Expert-Annotated 3T MRI Dataset and Algorithm for Prostate Cancer Detection.&rdquo; Computers in Biology and Medicine 148 (September): 105817.</p> <p>[5] Natarajan, S., Priester, A., Margolis, D., Huang, J., &amp; Marks, L. (2020). Prostate MRI and Ultrasound With Pathology and Coordinates of Tracked Biopsy (Prostate-MRI-US-Biopsy) (version 2) [Data set]. The Cancer Imaging Archive. DOI: 10.7937/TCIA.2020.A61IOC1A</p> <p>[6]&nbsp; Fedorov, A; Schwier, M; Clunie, D; Herz, C; Pieper, S; Kikinis, R; Tempany, C; Fennessy, F. (2018). Data From QIN-PROSTATE-Repeatability. The Cancer Imaging Archive. DOI: 10.7937/K9/TCIA.2018.MR1CKGND</p> <p>[7]&nbsp; Natarajan, S., Priester, A., Margolis, D., Huang, J., &amp; Marks, L. (2020). Prostate MRI and Ultrasound With Pathology and Coordinates of Tracked Biopsy (Prostate-MRI-US-Biopsy) (version 2) [Data set]. The Cancer Imaging Archive. DOI: 10.7937/TCIA.2020.A61IOC1A</p> <p>[8] Open Health Imaging Foundation Viewer: An Extensible Open-Source Framework for Building Web-Based Imaging Applications to Support Cancer Research. Erik Ziegler, Trinity Urban, Danny Brown, James Petts, Steve D. Pieper, Rob Lewis, Chris Hafey, and Gordon J. Harris</p> <p>[9] Clark K, Vendt B, Smith K, Freymann J, Kirby J, Koppel P, Moore S, Phillips S, Maffitt D, Pringle M, Tarbox L. The Cancer Imaging Archive (TCIA): maintaining and operating a public information repository. Journal of digital imaging. 2013 Dec;26(6):1045-57.</p> <p>[10] Wilkinson MD, Dumontier M, Aalbersberg IJ, Appleton G, Axton M, Baak A, Blomberg N, Boiten JW, da Silva Santos LB, Bourne PE, Bouwman J. The FAIR Guiding Principles for scientific data management and stewardship. Scientific data. 2016 Mar 15;3(1):1-9.</p> <p>[11] Herz C, Fillion-Robin JC, Onken M, Riesmeier J, Lasso A, Pinter C, Fichtinger G, Pieper S, Clunie D, Kikinis R, Fedorov A. DCMQI: an open source library for standardized communication of quantitative image analysis results using DICOM. Cancer research. 2017 Nov 1;77(21):e87-90.</p> <p>[12] Bridge CP, Gorman C, Pieper S, Doyle SW, Lennerz JK, Kalpathy-Cramer J, Clunie DA, Fedorov AY, Herrmann MD. Highdicom: A python library for standardized encoding of image annotations and machine learning model outputs in pathology and radiology. Journal of Digital Imaging. 2022 Aug 22:1-9.</p> <p>&nbsp;</p>

opencc-by-4.0Jun 2024View details →
zenodo36/100

Ecosystem-Level Factors Affecting the Survival of Open-Source Projects: A Case Study of the PyPI Ecosystem - the dataset

<pre><em>Replication pack, FSE2018 submission #164: </em><em>------------------------------------------ </em></pre> <pre><strong>**</strong>Working title:<strong>** </strong>Ecosystem-Level Factors Affecting the Survival of Open-Source Projects: A Case Study of the PyPI Ecosystem <strong>**</strong>Note:<strong>** </strong>link to data artifacts is already included in the paper. Link to the code will be included in the Camera Ready version as well. <em>Content description </em><em>=================== </em> <strong>- **</strong>ghd-0.1.0.zip<strong>** </strong>- the code archive. This code produces the dataset files described below <strong>- **</strong>settings.py<strong>** </strong>- settings template for the code archive. <strong>- **</strong>dataset_minimal_Jan_2018.zip<strong>** </strong>- the minimally sufficient version of the dataset. This dataset only includes stats aggregated by the ecosystem (PyPI) <strong>- **</strong>dataset_full_Jan_2018.tgz<strong>** </strong>- full version of the dataset, including project-level statistics. It is ~34Gb unpacked. This dataset still doesn&#39;t include PyPI packages themselves, which take around 2TB. <strong>- **</strong>build_model.r, helpers.r<strong>** </strong>- R files to process the survival data (`survival_data.csv` in <strong>**</strong>dataset_minimal_Jan_2018.zip<strong>**</strong>, `common.cache/survival_data.pypi_2008_2017-12_6.csv` in <strong>**</strong>dataset_full_Jan_2018.tgz<strong>**</strong>) <strong>- **</strong>Interview protocol.pdf<strong>** </strong>- approximate protocol used for semistructured interviews. <strong>- </strong>LICENSE - text of GPL v3, under which this dataset is published <strong>- </strong>INSTALL.md - replication guide (~2 pages)</pre> <pre><em>Replication guide </em><em>================= </em> <em>Step 0 - prerequisites </em><em>---------------------- </em> <strong>- </strong>Unix-compatible OS (Linux or OS X) <strong>- </strong>Python interpreter (2.7 was used; Python 3 compatibility is highly likely) <strong>- </strong>R 3.4 or higher (3.4.4 was used, 3.2 is known to be incompatible) Depending on detalization level (see Step 2 for more details): <strong>- </strong>up to 2Tb of disk space (see Step 2 detalization levels) <strong>- </strong>at least 16Gb of RAM (64 preferable) <strong>- </strong>few hours to few month of processing time <em>Step 1 - software </em><em>---------------- </em> <strong>- </strong>unpack <strong>**</strong>ghd-0.1.0.zip<strong>**</strong>, or clone from gitlab: git clone https://gitlab.com/user2589/ghd.git git checkout 0.1.0 `cd` into the extracted folder. All commands below assume it as a current directory. <strong>- </strong>copy `settings.py` into the extracted folder. Edit the file: <strong> * </strong>set `DATASET_PATH` to some newly created folder path <strong> * </strong>add at least one GitHub API token to `SCRAPER_GITHUB_API_TOKENS` <strong>- </strong>install docker. For Ubuntu Linux, the command is `sudo apt-get install docker-compose` <strong>- </strong>install libarchive and headers: `sudo apt-get install libarchive-dev` <strong>- </strong>(optional) to replicate on NPM, install yajl: `sudo apt-get install yajl-tools` Without this dependency, you might get an error on the next step, but it&#39;s safe to ignore. <strong>- </strong>install Python libraries: `pip install --user -r requirements.txt` . <strong>- </strong>disable all APIs except GitHub (Bitbucket and Gitlab support were not yet implemented when this study was in progress): edit `scraper/init.py`, comment out everything except GitHub support in `PROVIDERS`. <em>Step 2 - obtaining the dataset </em><em>----------------------------- </em> The ultimate goal of this step is to get output of the Python function `common.utils.survival_data()` and save it into a CSV file: # copy and paste into a Python console from common import utils survival_data = utils.survival_data(&#39;pypi&#39;, &#39;2008&#39;, smoothing=6) survival_data.to_csv(&#39;survival_data.csv&#39;) Since full replication will take several months, here are some ways to speedup the process: <em>####Option 2.a, difficulty level: easiest </em> Just use the precomputed data. Step 1 is not necessary under this scenario. <strong>- </strong>extract <strong>**</strong>dataset_minimal_Jan_2018.zip<strong>** </strong><strong>- </strong>get `survival_data.csv`, go to the next step <em>####Option 2.b, difficulty level: easy </em> Use precomputed longitudinal feature values to build the final table. The whole process will take 15..30 minutes. <strong>- </strong>create a folder `&lt;DATASET_PATH&gt;/common.cache`, where `&lt;DATASET_PATH&gt;` is the value of the variable `DATASET_PATH` in `settings.py` <strong>- </strong>extract <strong>**</strong>dataset_minimal_Jan_2018<strong>** </strong>to the newly created folder <strong>- </strong>rename files: mv backporting.csv monthly_data.pypi_backporting.csv mv cc_degree.csv monthly_data.pypi_cc_degree.csv mv commercial.csv monthly_data.pypi_commercial.csv mv commits.csv monthly_data.pypi_commits.csv mv contributors.csv monthly_data.pypi_contributors.csv mv dc_katz.csv monthly_data.pypi_dc_katz.csv mv downstreams.csv monthly_data.pypi_downstreams.csv mv d_upstreams.csv monthly_data.pypi_d_upstreams.csv mv github_user_info.csv user_info.pypi.csv mv issues.csv monthly_data.pypi_issues.csv mv non_dev_issues.csv monthly_data.pypi_non_dev_issues.csv mv non_dev_submitters.csv monthly_data.pypi_non_dev_submitters mv package_urls.csv package_urls.pypi.csv mv q90.csv monthly_data.pypi_q90.csv # raw_dependencies.csv is not required # raw_packages_info.csv is not required # Feel free to read README.md for more details about the data mv submitters.csv monthly_data.pypi_submitters.csv # In this scenario we&#39;ll generate a new survival_data.csv mv university.csv monthly_data.pypi_university.csv mv upstreams.csv monthly_data.pypi_upstreams.csv <strong>- </strong>edit `common/decorators.py`, set `DEFAULT_EXPIRY` to some higher value, e.g. `DEFAULT_EXPIRY = float(&#39;inf&#39;) # cache never expires` Then, use the Python code above to obtain `survival_data.csv`. <em>####Option 2.c, difficulty level: medium </em> Use predownloaded raw data to build longitudinal feature values, and then the dataset. Despite most of the data is cached, some functions will pull up updates which might take anywhere from days to couple weeks to run. <strong>- </strong>Download <strong>**</strong>dataset_full_Jan_2018.tgz<strong>** </strong>from http://k.soberi.us/dataset_full_Jan_2018.tgz . This file is not included in this archive because of its size (5.4Gb compressed, 34Gb unpacked). <strong>- </strong>edit `common/decorators.py`, set `DEFAULT_EXPIRY` to some higher value, e.g. `DEFAULT_EXPIRY = float(&#39;inf&#39;) # cache never expires` <strong>- </strong>extract the content of this archive into `&lt;DATASET_PATH&gt;`. <strong>- </strong>clean up `&lt;DATASET_PATH&gt;/common.cache` (otherwise you&#39;ll get Step 2.a. You can reproduce Step 2.b by deleting only `survival_data.pypi_2008_2017-12_6.csv`) Run the Python code above to obtain `survival_data.csv`. <em>####Option 2.d, difficulty level: hard </em> Build the dataset from scratch. Although most of the processing is parallelized, it will take at least couple months on a reasonably powerful server (32 cores, 512G of RAM, 2Tb+ of HDD space in our setup). <strong>- </strong>ensure the `&lt;DATASET_PATH&gt;` is empty <strong>- </strong>add more GitHub tokens (borrow from your coworkers) to `settings.py`. Run the Python code above to obtain `survival_data.csv`. <em>Step 3 - run the regression </em><em>--------------------------- </em> install R libraries: install.packages(c(&quot;htmlTable&quot;, &quot;OIsurv&quot;, &quot;survival&quot;, &quot;car&quot;, &quot;survminer&quot;, &quot;ggplot2&quot;, &quot;sqldf&quot;, &quot;pscl&quot;, &quot;texreg&quot;, &quot;xtable&quot;)) Use `build_model.r` (e.g. in RStudio) and produced `survival_data.csv` to build the regressions used in the paper. This process takes at least 16Gb of RAM and takes few hours to run due to the gigantic size of the dataset. </pre>

opengpl-2.0Jun 2018View details →
zenodo36/100

DeepPlastic: An Open Source Image Dataset for Epipelagic Marine Plastic Detection

<p>Deep Plastic</p> <ul> <li>Enhanced Object Detection for Epipelagic Plastic.</li> <li>This repository contains source code for the method developed in&nbsp;<a href="https://arxiv.org/pdf/2105.01882.pdf">DeepPlastic: Identifying Marine Plastic In The Epipelagic Zone using Computer Vision and Deep Learning</a></li> <li> <p>Information:</p> </li> <li>Paper: [Coming Soon]</li> <li>YouTube video of Results:&nbsp;<a href="https://youtu.be/8zBdFxaK4Os">https://youtu.be/8zBdFxaK4Os</a></li> <li> <p>Object Detection Model</p> </li> <li>Four models: YOLOv4, YOLOv5, MobileSSD, Faster RCNN Inception V2</li> <li>Small efficient and high precision models can be used for real-time object detection.</li> <li>Model architecture and implementation details:&nbsp;<a href="https://arxiv.org/">https://arxiv.org/</a></li> <li>Weights for YOLOv4 and YOLOv5 are provided in the model/ <ul> <li>YOLOv4: best. weights; use&nbsp;<a href="https://drive.google.com/file/d/1YOTtZ2cHbqgxHukzLp01OVsUoa2CwwXs/view?usp=sharing">best.weights</a></li> <li>YOLOv5: best.pt; use&nbsp;<a href="https://drive.google.com/file/d/14mBOhtLrE2d3hudqjwBZmawKAvTF4zxS/view?usp=sharing">best.pt</a></li> </ul> </li> <li> <p>Google Colab Links</p> <p>Note: Click on File and Save Copy in Drive. If you try to edit my file it&#39;ll ask you for permission and send me an email. Please make your own copy.</p> </li> <li>YOLOv5:&nbsp;<a href="https://colab.research.google.com/drive/1_qzbpBWkNfxQ0ny-DvsKicCeM0aFU4eW?usp=sharing">https://colab.research.google.com/drive/1_qzbpBWkNfxQ0ny-DvsKicCeM0aFU4eW?usp=sharing</a></li> <li> <p>DeepTrash DataSet</p> </li> <li>1900 training images, 637 test images, 637 validation images (60, 20, 20 split)</li> <li>Field images taken from Lake Tahoe, San Francisco Bay and Bodega Bay in CA.</li> <li>Deep Sea images are from JAMSTEK JEDI dataset:&nbsp;<a href="http://www.godac.jamstec.go.jp/">http://www.godac.jamstec.go.jp/</a></li> </ul>

opencc-by-4.0Apr 2021View details →
zenodo36/100

Open-source Software Governance Documentation Dataset on GitHub

<p>This dataset contains 710 GitHub-hosted OSS projects, which contain a governance file in the root directory of the project. It also contains commits, issues, and comments on each project.</p>

opencc-by-4.0Jan 2023View details →
dryad36/100

MALDI-MS dataset for use with open-source untargeted metabolomic workflow for complex biological samples

<p class="MsoNormal">Untargeted metabolomics is a powerful tool for measuring and understanding complex biological chemistries. However, employment, bioinformatics and downstream analysis of mass spectrometry (MS) data can be daunting for inexperienced users. Numerous open-source and free to-use data processing and analysis tools exist for various untargeted MS approaches, but choosing the 'correct' pipeline isn't straight-forward. This data set can be used in conjunction with a user-friendly online guide which presents a workflow for connecting these tools to process, analyse and annotate various untargeted MS datasets. The workflow is intended to guide exploratory analysis in order to inform decision-making regarding costly and time-consuming downstream targeted MS approaches. The workflow provides practical advice concerning experimental design, organisation of data and downstream analysis, and offers details on sharing and storing valuable MS data for posterity. The workflow is editable and modular, allowing flexibility for updated/ changing methodologies and increased clarity and detail as user participation becomes more common allowing contributions and improvements to the workflow via the online repository. </p>

opencc-zeroFeb 2023View details →
zenodo36/100

Dataset to publication: ''Magnetstein: An open source tool for quantitative NMR mixture analysis robust to low resolution, distorted lineshapes and peak shifts''

<p>MANIQ (plugin for Mnova 14.3.1 software (Mestrelab Research, S. L., Spain)) and&nbsp; ACD/TP (Targeted Profiling tool for ACD/Spectrus 2020.1.1 (Advanced Chemistry Development, Inc., ACD/Labs Ontario, Toronto, ON, Canada)) project files and raw experimental NMR data to:</p> <table> <caption>Experiments obtained to Magnetstein with optimized parameters, Magnetstein with default parameters, ACD/TP and MANIQ.</caption> <tbody> <tr> <td>Exp. no.</td> <td>Problem</td> <td>Ingredients</td> </tr> <tr> <td>1</td> <td>large intensity differences<br> between peaks</td> <td>&alpha;-pinene<br> benzyl benzoate<br> (in CDCl<sub>3</sub>)</td> </tr> <tr> <td>2</td> <td>peak overlap<br> &amp; contamination (extra peaks)</td> <td>imonene<br> &alpha;-pinene<br> (in CDCl<sub>3</sub>)</td> </tr> <tr> <td>3</td> <td>low resolution (43 MHz<br> benchtop NMR spectrometer)</td> <td>benzyl benzoate<br> isopropyl myristate<br> limonene<br> pinene</td> </tr> <tr> <td>4</td> <td>lineshape distortion<br> (shim z1 &amp; z2)</td> <td>actate<br> alanine<br> creatine<br> creatinine<br> choline chloride<br> (in D<sub>2</sub>O)</td> </tr> <tr> <td>5</td> <td>peak position<br> mismatch<br> between library<br> and mixture<br> (different<br> temperatures)</td> <td>actate<br> alanine<br> creatine<br> creatinine<br> choline chloride<br> (in D<sub>2</sub>O)</td> </tr> <tr> <td>6</td> <td>test sample</td> <td>&alpha;-pinene<br> benzyl benzoate<br> (in CDCl<sub>3</sub>)</td> </tr> <tr> <td>7</td> <td>large intensity<br> differences<br> &amp; peak overlap</td> <td><br> benzyl benzoate<br> m-anisaldehyde<br> (in CDCl<sub>3</sub>)</td> </tr> <tr> <td>8</td> <td><br> peak overlap &amp;<br> different solvents<br> for single<br> ingredients (in CDCl<sub>3</sub>)<br> and mixture (DMSO-d<sub>6</sub>)</td> <td>benzyl benzoate<br> m-anisaldehyde</td> </tr> <tr> <td>9</td> <td>ineshape<br> distortion<br> (shim z2)</td> <td>actate<br> alanine<br> creatine<br> creatinine<br> choline chloride<br> (in D<sub>2</sub>O)</td> </tr> </tbody> </table> <p>&nbsp;</p>

opencc-by-4.0Jul 2023View details →
dryad36/100

MALDI-MS dataset for use with open-source untargeted metabolomic workflow for complex biological samples

Open the record for dataset details and reuse information.

publicFeb 2023View details →
zenodo32/100

Dataset and scripts for "Sentiment Analysis over Collaborative Relationships in Open Source Software Projects"

<p>Dataset and scripts for &quot;Sentiment Analysis over Collaborative Relationships in Open Source Software Projects&quot;.</p> <p>README is included in the files</p>

opencc-by-4.0Jul 2019View details →
zenodo32/100

Dataset and Code for "Mining and Predicting Micro-Process Patterns of Issue Resolution for Open Source Software Projects"

<p>Dataset and Code for &quot;Mining and Predicting Micro-Process Patterns of Issue Resolution for Open Source Software Projects&quot; with README included</p>

opencc-by-4.0Jan 2020View 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

ScienceDex for faculty

Your academic CV and NIH biosketch

Make your CV in your school's format and your NIH biosketch from it, then download both as Word files.