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.
3,225
datasets available to search
ShareScore release 0.9.0
Dataset results
3,225 results for “Case of study”
Dataset for: On the estimation of body mass in temnospondyls: A case study using the large-bodied Eryops and Paracyclotosaurus
Open the record for dataset details and reuse information.
Data for: The role of ecdysis in repair of an attachment system: a case study using geckos
Open the record for dataset details and reuse information.
Data from: Does migration promote or inhibit diversification? A case study involving the dominant radiation of temperate Southern Hemisphere freshwater fishes
Open the record for dataset details and reuse information.
Can sexual selection promote within-species divergence of male genitalia? A study case with a male-dimorphic arachnid
Open the record for dataset details and reuse information.
Do ecological specialization and functional traits explain the abundance–frequency relationship? Arable weeds as a case study
Open the record for dataset details and reuse information.
Obuasi case study data: Performance of neutral SNP barcodes to determine genetic diversity and structure of Plasmodium falciparum in Africa
Open the record for dataset details and reuse information.
Reconstructing locomotor ecology of extinct avialans: a case study of Ichthyornis comparing sternum morphology and skeletal proportions
Open the record for dataset details and reuse information.
Improving metabarcoding taxonomic assignment: A case study of fishes in a large marine ecosystem
Open the record for dataset details and reuse information.
Data from: The utility of information flow in formulating discharge forecast models: a case study from an arid snow-dominated catchment
Open the record for dataset details and reuse information.
Cryptic behaviour and activity cycles of a small mammal keystone species revealed through accelerometry: a case study of Merriam’s kangaroo rats
Open the record for dataset details and reuse information.
Snowmelt periods as hot moments for soil N dynamics: A case study in Maine, USA
This is the data archive for the corresponding publication with the same title (doi: 0.1007/s10661-020-08733-0). The vernal transition represents the seasonal transition to spring, occurring as temperatures rise at the end of winter. With rapid snowmelt, microbial community turnover, and accelerated nutrient cycling, this is a critical but relatively under-studied period of ecosystem function. We conducted a study over two consecutive winters (2015-2016) at the Bear Brook Watershed in Maine to examine how changing winter conditions (warming winters, reduced snow accumulation) altered soil nitrogen availability and stream N export during winter and the vernal transition, and how these patterns were influenced by ecosystem N status (N-enriched vs. N-limited). Of the two study years, 2016 had a warmer winter with substantially less snow accumulation and a discontinuous snowpack — and as a result, had a longer vernal transition and a snowpack that thawed before the vernal transition began. Across both years, snowmelt triggered a transition, signaled by increased ammonium concentrations in soil, decreased soil nitrate concentrations due to flushing by meltwater, and increased stream nitrate exports. Despite the contrasting winter conditions, both years showed similar patterns in N availability and export, differing only in the timing of these transitions. The vernal transition has conventionally been considered a critical period for biogeochemical cycling, because the associated snowmelt event triggers physicochemical and biochemical changes in soil systems. This was consistent with our results in 2015, but our data for 2016 show that this may not always hold true, and instead, that warmer, low-snow winters may demonstrate a temporal asynchrony between snowmelt and the vernal transition. We also show that ecosystem N status is a strong driver of the seasonal N pattern, and the interaction of N status and changing climate must be further investigated to understand ecosyst
Information Based Behavioural Intervention Study (Guildford case)
<p>iSCAPE Dataset Reference No. = DS_PD_014, DS_PD_019</p> <p>Following datasets are acquired/generated during the implementation of behavioural intervention study in Guildford:</p> <ol> <li>Participant's detailed activity-travel diary </li> <li>Introductory and Followup questionnaire responses</li> </ol>
Does Unit-Tested Code Crash? A Case Study of Eclipse: Replication Package
<p><strong>Does Unit-Tested Code Crash? A Case Study of Eclipse: Replication Package</strong></p> <p>This is a replication package associated with the paper titled “Does Unit-Tested Code Crash? A Case Study of Eclipse”. Below is a description of the package’s contents.</p> <p><strong>Data</strong></p> <p>Data files associated with the paper are provided in the <code>data</code> directory.</p> <p><strong>Text file <code>tested-crashed.txt</code></strong></p> <p>Data specifying whether methods were tested and whether they crashed (according to the criteria adopted in the study). Extracted from <code>matches.xlsx</code>. The data are used as input for Fisher’s test (RQ1).</p> <p><strong>Spreadsheet <code>matches.xlsx</code></strong></p> <p>Test coverage data and calculations associated with failed methods, class coverage, and matching method coverage results are provided in an Excel spreadsheet. Below is the description of the spreadsheet’s contents.</p> <p>Worksheet <em>Test Coverage</em></p> <p>Contains the data regarding the JaCoCo test code coverage analysis.</p> <ul> <li>Class: The name of the class in which a method appears in JVM internal form notation</li> <li>Method: The method’s name</li> <li>Parameters: The method’s arguments in JVM parameter descriptor format; required to handle Java’s {} polymporphism</li> <li>Class Has Unit Test: Whether the corresponding class has associated unit test code</li> <li>Class Unit-Test Line Density: The ratio of lines in class’s test code over those in the class’s implementation code</li> <li>Covered Instructions / Branches / Lines: As reported by JaCoCo</li> <li>Total Instructions / Branches / Lines: As reported by JaCoCo</li> <li>Covered Instructions / Branches / Lines ratio: The ratio between the two preceding values; 1 for methods without any branches</li> <li>Top-1 / Top-6 / Top-10 : In how many stack traces the method appears within; the top-10 / top-6 / the very first stack frame(s)</li> <li>Tested: TRUE if the method is considered tested by having a test code coverage above the median (0.966) and an associated test class</li> <li>Crashed: TRUE if the method has crashed as evidenced by its appearance on the topmost stack frame</li> <li>Stack trace file names: in which the method appeared</li> </ul> <p>Worksheet <em>Test Existence</em></p> <p>Contains the data of the analysis regarding the existence of test code.</p> <ul> <li>Class: Class containing implementation code</li> <li>TestClassNames: Classes that contain tests for the above</li> <li>Number of relevant tests</li> <li>Lines in class test code</li> <li>Lines of class</li> <li>Class Unit-Test Line Density: The ratio between the two above</li> </ul> <p>Worksheet <em>Metrics</em></p> <p>Contains the derivation of metrics reported in the paper. In the cases of tables these are formatted in LaTeX for direct incorporation into the text.</p> <p><strong>Spreadsheet <code>jacoco.xlsx</code></strong></p> <p>Complete test coverage data obtained from JaCoCo are provided in an Excel spreadsheet. Below is the description of the spreadsheet’s contents.</p> <p>Worksheet <em>Data</em></p> <p>Contains the following method code coverage fields as reported by JaCoCo, as well as the calculated percentages.</p> <ul> <li>Class</li> <li>Method</li> <li>Parameters</li> <li>Covered Instructions</li> <li>Total Instructions</li> <li>% Covered Instructions</li> <li>Covered Branches</li> <li>Total Branches</li> <li>% Covered Branches</li> <li>Covered Lines</li> <li>Total Lines</li> <li>% Covered Lines</li> </ul> <p>Worksheet <em>Metrics</em></p> <p>Contains the derivation of numbers reported in the preliminary quantitative analysis and Figure 2.</p> <p>Compressed tar archive <code>eclipse-src.tar.gz</code></p> <p>Contains the Eclipse source code used for running the Eclipse tests with JaCoCo code coverage analysis. It was obtained from the Eclipse source code repositories as follows.</p> <ul> <li>Clone the Eclipse aggreagator repository into a directory named z by running: <code>git clone -b master --recursive git://git.eclipse.org/gitroot/platform/eclipse.platform.releng.aggregator.git z</code></li> <li>In the <code>z</code> directory, checking out the used release by running <code>cd z && git submodule foreach git checkout M20160212-1500</code></li> <li>Checking out the release for the main repository by running: <code>git checkout M20160212-1500</code></li> <li>Applying the patch <code>eclipse-src.diff</code></li> </ul> <p><strong>Patch file <code>eclipse-src.diff</code></strong></p> <p>See above.</p> <p><strong>Zip file <code>incidents.zip</code></strong></p> <p>Contains the 126,026 incidents (crash report stack traces and meta-data) associated with <em>EclipseProduct</em> <code>org.eclipse.epp.package.java.product</code> and <em>BuildID</em> <code>4.5.2.M20160212-1500</code>. This is a subset from the two million incidents available as the <a href="http://software-data.org/datasets/aeri-stacktraces/downloads/incidents_full.tar.bz2">AERI stack traces data set</a>.</p> <p>The subset of incidents was extracted from the full AERI data set with the following command.</p> <pre><code class="language-bash">for f in *; do grep -q org.eclipse.epp.package.java.product $f && grep -q 4.5.2.M20160212-1500 $f && mv $f selected-files/ done</code></pre> <p><br> <strong>Compressed file <code>jacoco.xml.gz</code></strong></p> <p>Contains the results of the JaCoCo code coverage analysis over the Eclipse testing.</p> <p><strong>Code</strong></p> <p>The following scripts are provided in the <code>src</code> directory</p> <ul> <li><code>extract.py</code>: script for extracting crash (incidents) and coverage (JaCoCo) data</li> <li><code>unit-tested-classes.py</code>: script for finding the classes with associated unit test code</li> <li><code>merge.py</code>: script for matching crash (incidents) with coverage (JaCoCo) data</li> <li><code>fisher.r</code>: R script for running Fisher’s test</li> </ul>
A Process for Evaluating the Energy Efficiency of Software - Case Study A
<p>This laboratory package includes the data of the case study carried out in this work.</p> <p> </p> <p> </p>
Linking individual physiological indicators to the productivity of fish populations: A case study of Atlantic herring
<p>Raw data for i) heart rate measurements of Atlantic herring larvae reared at three different temperatures (7, 11 and 15°C); ii) compilation of Baltic herring larval growth rates measured in the field and in the laboratory; and iii) time series of thermal estimates (derived from satellite sea surface temperatures) in Greifswald Bay (Baltic Sea) between 1992 and 2017, as well as three herring productivity proxies in the area: weekly larval abundance in Greifswald Bay (one of the major spawning grounds), 1 yr-old juvenile abundance in the western Baltic basin, and the recruitment estimate from the International Council for the Exploration of the Sea (ICES) Herring Assessment Working Group for the Area South of 62°N.</p>
Crowdsourcing public perceptions of urban green space quality: A case study of Rembrandt park in Amsterdam
<p><strong><em>City-dwellers are realizing the benefits of green spaces and are flocking to urban parks. City planners face the challenge of ensuring that urban green spaces are functional for all citizens. To make informed choices they need the right information and that is where the Mijn Park app can help. </em></strong></p> <p>Research shows that when considering the social functions of urban green spaces, quality is just as important as quantity. It is easy enough to map how much green spaces there are, but how do we measure their quality? How do city planners ensure that the city’s green areas are attractive, accessible and inclusive – for everyone? The Vrije Universiteit Amsterdam in collaboration with the International Institute for Applied Systems Analysis developed Mijn Park, a mobile application that will help city planners do just that. As part of the LandSense Citizen Observatory, the ‘Mijn Park’ (My Park) app asks respondents to go to several locations in a park and give subjective responses to those locations. They are then further questioned about how they use the whole park and how much they would like to see certain changes made in the park. This information provides information that can help to inform decisions about any renovations or improvements to the park.</p> <p>A pilot campaign was conducted in the summer of 2018 in Rembrandt park in Amsterdam and insights from the citizen-driven observations were shared with the Department of Planning and Sustainability of Amsterdam.</p> <p>This dataset includes responses and photographs collected by 129 unique volunteers providing 377 observations in select locations across Rembrandt Park. The following files are available:</p> <ul> <li>_Preview MijnPark-Amsterdam-LandSense.png</li> <li>Attributes-MijnPark-Amsterdam-LandSense.csv</li> <li>MijnPark-Amsterdam-LandSense.csv</li> <li>MijnPark-Amsterdam-LandSense.geoJSON</li> <li>README.txt</li> </ul> <p> </p> <p>This dataset is licensed under a Creative Commons Attribution 4.0 International. It is attributed to the <a href="https://landsense.eu/">LandSense Citizen Observatory</a>, <a href="https://www.vu.nl/">Vrije Universiteit</a> (VU), Amsterdam and the <a href="https://iiasa.ac.at/">International Institute for Applied Systems Analysis</a> (IIASA).</p> <p>This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement no 689812.</p>
PUFFIN Application Case Study Data
<p>This contains the Probabilistic Urban Flash Flood Information Nexus (PUFFIN) application and its output data from the October 11th, 2018 and February 6th, 2020 Case Study events</p>
Supporting material for: A multi-batch design to deliver robust estimates of efficacy and reduce animal use – a syngeneic tumour case study
<p>Underlying data, R scripts and subsequent figures are presented to deliver a replicable and transparent analysis for the manuscript "A multi-batch design to deliver robust estimates of efficacy and reduce animal use – a syngeneic tumour case study"</p> <p>Published in Scientific Reports</p> <p>See: <a href="https://protect-de.mimecast.com/s/kCQLCgpRGySlzOwmCNma6d?domain=rdcu.be">https://rdcu.be/b3vj2</a> </p> <p> </p> <p>This is version 2 of this data. This differs from version 1 in the following</p> <p>1. The number of simulation has increased from 300 to 2000 in each simulation cycle</p> <p>2. Script has been added to generate publication level figures</p> <p> </p> <p> </p> <p> </p>
Could dementia be detected from UK primary care patients' records by simple automated methods earlier than by the treating physician? A retrospective case-control study - Extended Data
<p>Extended data for Article published in Wellcome Open Research (Appendices 1,2 & 3). </p> <p>Abstract of Article: </p> <p><strong>Background:</strong> Timely diagnosis of dementia is a policy priority in the United Kingdom (UK). Primary care physicians receive incentives to diagnose dementia; however, 33% of patients are still not receiving a diagnosis. We explored automating early detection of dementia using data from patients’ electronic health records (EHRs). We investigated: a) how early a machine-learning model could accurately identify dementia before the physician; b) if models could be tuned for dementia subtype; and c) what the best clinical features were for achieving detection.</p> <p><strong>Methods:</strong> Using EHRs from Clinical Practice Research Datalink in a case-control design, we selected patients aged >65y with a diagnosis of dementia recorded 2000-2012 (cases) and matched them 1:1 to controls; we also identified subsets of Alzheimer’s and vascular dementia patients. Using 77 coded concepts recorded in the 5 years before diagnosis, we trained random forest classifiers, and evaluated models using Area Under the Receiver Operating Characteristic Curve (AUC). We examined models by year prior to diagnosis, subtype, and the most important features contributing to classification.</p> <p><strong>Results:</strong> 95,202 patients (median age 83y; 64.8% female) were included (50% dementia cases). Classification of dementia cases and controls was poor 2-5 years prior to physician-recorded diagnosis (AUC range 0.55-0.65) but good in the year before (AUC: 0.84). Features indicating increasing cognitive and physical frailty dominated models 2-5 years before diagnosis; in the final year, initiation of the dementia diagnostic pathway (symptoms, screening and referral) explained the sudden increase in accuracy. No substantial differences were seen between all-cause dementia and subtypes.</p> <p><strong>Conclusions:</strong> Automated detection of dementia earlier than the treating physician may be problematic, if using only primary care data. Future work should investigate more complex modelling, benefits of linking multiple sources of healthcare data and monitoring devices, or contextualising the algorithm to those cases that the GP would need to investigate.</p>
Complete tag loss in capture-recapture studies affects abundance estimates: an elephant seal case study
<p>1. In capture-recapture studies, recycled individuals occur when individuals lose all of their tags and are recaptured as though they were new individuals. Typically, the effect of these recycled individuals is assumed negligible.</p> <p>2. Through a simulation-based study of double tagging experiments, we examined the effect of recycled individuals on parameter estimates in the Jolly-Seber model with tag loss (Cowen & Schwarz, 2006). We validated the simulation framework using long-term census data of elephant seals.</p> <p>3. Including recycled individuals did not affect estimates of capture, survival, and tag-retention probabilities. However, with low tag-retention rates, high capture rates, and high survival rates, recycled individuals produced over estimates of population size. For the elephant seal case study, we found population size estimates to be between 8 and 53% larger when recycled individuals were ignored.</p> <p>4. Ignoring the effects of recycled individuals can cause large biases in population size estimates. These results are particularly noticeable in longer studies.</p>
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.